R12: Is There an Automated Way to Update Custom SLA Code (AADs) After Patch Application?
(Doc ID 1399612.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Receivables - Version 12 and later
Information in this document applies to any platform.
EXECUTABLE:XLAALIMP - Import Application Accounting Definitions
EXECUTABLE:XLAAADUL - Upload Application Accounting Definitions
EXECUTABLE:XLAABACR - Validate Application Accounting Definitions
FORM:XLAABPAD.FMB - Application Accounting Definitions
FORM:XLAABJLD.FMB - Journal Lines Definitions
FORM:XLAABADR.FMB - Account Derivation Rules
Customer is using Accounts Receivables application. Is there an automated way to update custom sla setup after seeded code (ARXLAAAD.ldt) is updated by by patch?
Customer has created a custom SLAM, custom AAD for Receivables applied and 6 of the 12 AR event types are customized. They have made numerous customizations to these 5 journal line definitions (JLD).
Customized JLD event types : Invoices, receipts, misc. receipts, credit memos, debit memos, adjustments
Customer is still using the Oracle seeded JLD for event types: Guarantee, Deposit, Bills Receivables, Chargesbacks,Factoring Collection Occurrence Documents, Collection Occurrence Documents
Customer doesn't have the resources required to rebuild and copy after each
patch upgrade of file: ARXLAAAD.ldt. It is requiring too much testing and
setup time to do this each and everytime a new patch is applied which affects SLA setups.
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