PA – Importing Total Accrued Revenue (PATACRV) – taPAMiscLogHdrInsert
Renee asked 7 years ago
Hello!
I am attempting to use SmartConnect to import into PA Miscellaneous Logs. These transactions do not have any cost associated with them – only revenue. Unfortunately, the core GP window does not allow you to manually enter a revenue amount by line item. However, there is a read only field in the window that displays the Total Accrued Revenue.
I was hoping to import into that same field (PATACRV) since it is referenced in the taPAMiscLogHdrInsert stored procedure.
However, whenever I import the records, everything imports perfectly except these values. They continue to default from the PA setup. I this on Microsof’t website: https://msdn.microsoft.com/en-us/library/jj193381.aspx
Pay particular attention to this line: Always use the default value. The amount of accrued revenue is always calculated. If you specify a value other than the default, an error will occur.
That sounds like it is not possible to import into this field. However, then why is it part of the eConnect stored procedure?
Any ideas or suggestions on how to (safely) accomplish my end result?
Thank you!
I am attempting to use SmartConnect to import into PA Miscellaneous Logs. These transactions do not have any cost associated with them – only revenue. Unfortunately, the core GP window does not allow you to manually enter a revenue amount by line item. However, there is a read only field in the window that displays the Total Accrued Revenue.
I was hoping to import into that same field (PATACRV) since it is referenced in the taPAMiscLogHdrInsert stored procedure.
However, whenever I import the records, everything imports perfectly except these values. They continue to default from the PA setup. I this on Microsof’t website: https://msdn.microsoft.com/en-us/library/jj193381.aspx
Pay particular attention to this line: Always use the default value. The amount of accrued revenue is always calculated. If you specify a value other than the default, an error will occur.
That sounds like it is not possible to import into this field. However, then why is it part of the eConnect stored procedure?
Any ideas or suggestions on how to (safely) accomplish my end result?
Thank you!
Answers
Patrick Roth Staff answered 7 years ago
Renee,
“Unfortunately, the core GP window does not allow you to manually enter a revenue amount by line item. “
I wouldn’t expect that eConnect would allow you to do something that the GP UI doesn’t. There are a few places that this differs however – this might be that spot. However based on your next point –
“However, whenever I import the records, everything imports perfectly except these values.”
It doesn’t look that that it does work.
“The amount of accrued revenue is always calculated. If you specify a value other than the default, an error will occur.
That sounds like it is not possible to import into this field. “
I would agree with you.
“However, then why is it part of the eConnect stored procedure?”
I agree – that does sound stupid. My only guess is is that maybe it used to do somethng (perhaps wrong) and they just left it there but give an edit check error instead. You’d have to ask Microsoft why on this one.
All in all, you’d have to run the entire thing by Microsoft since the proc is encrypted so we don’t know the business logic.
“Unfortunately, the core GP window does not allow you to manually enter a revenue amount by line item. “
I wouldn’t expect that eConnect would allow you to do something that the GP UI doesn’t. There are a few places that this differs however – this might be that spot. However based on your next point –
“However, whenever I import the records, everything imports perfectly except these values.”
It doesn’t look that that it does work.
“The amount of accrued revenue is always calculated. If you specify a value other than the default, an error will occur.
That sounds like it is not possible to import into this field. “
I would agree with you.
“However, then why is it part of the eConnect stored procedure?”
I agree – that does sound stupid. My only guess is is that maybe it used to do somethng (perhaps wrong) and they just left it there but give an edit check error instead. You’d have to ask Microsoft why on this one.
All in all, you’d have to run the entire thing by Microsoft since the proc is encrypted so we don’t know the business logic.
Renee replied 7 years ago Thank you for the collaboration Patrick. I will do as you suggested and run this by Microsoft.