Discover 8 fields that allow you to pull subledger information into a GL Transaction report.
Have you ever wanted to pull some subledger information into a GL Transaction report? There are a bunch of “Originating ____” fields found under the Account Transactions SmartList (under Financial) and in certain circumstances, you will be able to extract *some* of that information from your G/L to supplement your account analysis.
Here are some of the fields and what they may contain.
|
Field |
Description |
|
Originating Company ID |
For intercompany transactions |
|
Originating Debit & Credit |
When using multi-currency, these are going to be the transaction debits and credits in the original currency of the transaction. In comparison, the regular “Debit” and “Credit” fields will always be the functional currency amounts. |
|
Originating Source |
This is usually the original Batch Number if Posting Setup is set to Post Thru. |
|
Originating Posted Date |
This is “the date on which the original transaction was posted”, as in the system date. |
|
Originating TRX Source |
This is the Audit Trail code for the original batch from the originating transaction. |
|
Originating Control Number |
This can be the original doc number but not always, especially when the original module has both a doc number field and a sequential transaction number (like PM trx voucher numbers). |
|
Originating Document Number |
In comparison to the above field, Originating Control Number, this field is pretty consistently the actual original Doc Number.
|
|
Originating Master ID & Name |
For most modules this is the ID and Name from the transaction, i.e. Customer or Vendor ID/Name. For Bank module, the ID is the chequebook and the Name is the name on the transaction (i.e. Paid to/Received from). On Bank Transfers, interestingly enough, the ID is “Transfer From:” and the chequebook and the Name is “Transfer To:” and the chequebook. |
