SLA SETUP: ADR using source TRANSACTION IDENTIFIER (TRX_CUSTOMER_TRX_ID) not working
(Doc ID 1554851.1)
Last updated on SEPTEMBER 22, 2024
Applies to:
Oracle Receivables - Version 12.1.3 and laterInformation in this document applies to any platform.
FORM:XLAABDSS.FMB - Custom Sources
FORM:XLAABADR.FMB - Account Derivation Rules
FORM:XLAABJLD.FMB - Journal Lines Definitions
Goal
Sign into Accounts receivable responsibility.
You have a business requirement to generate an ADR (Account Derivation Rule) which references source: transaction identifier (TRX_CUSTOMER_TRX_ID) for JLT: Credit Memo Receivable.
On the custom sources form , you create a custom function which references input source: transaction identifier (TRX_CUSTOMER_TRX_ID).
On the Account Derivation Rules form , you create a custom ADR which references the newly generated custom function.
You run create accounting and the accounting is created but the ADR does not create the anticipated accounting for your JLT: Credit Memo Receivable.
Interestingly, this seeded source: transaction identifier (TRX_CUSTOMER_TRX_ID) works for all invoice JLTs successfully , including JLT: Invoice Receivable.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |