In Oracle Payables, a payment has a functional dependency on invoice, i.e. the payment needs to be accounted to same liability account as the invoice has been accounted for. In such a scenario, invoice is referred to as the upstream transaction and the payment as the downstream transaction.
In a business flow prior entry application, the upstream accounting is mandatory for the downstream transaction accounting to go through. The accounting journals must be created in each ledger (primary, ALC and secondary) for all upstream transactions to have the accounting to be created in all the related ledgers of primary ledger for the downstream transaction.
Similar dependencies are there for other transactions also like Invoice Cancellation, Prepayment Application, Payment Cancellation, Payment unclearing etc.
Business flow failures generally have the error:
- Error 0 : This line cannot be accounted until the accounting event for the application Payables that it references has been fully accounted.
In order to resolve this situation, users needs to identify and account all upstream
transactions before accounting the downstream transactions. This was more complex for transactions that referenced one or more 11i transactions as the upstream transaction and in some cases it was
mandatory to have Hot Patch applied or SLA: Upgrade Historical Subledger
Transaction Accounting Program ran to cover the period related to the
upstream transaction. This was required even for accounting a single downstream transaction.
With the exciting enhancement delivered via Patch 19568225, downstream transactions failing business flow for an
upgraded upstream transaction can be successfully accounted using
ON-LINE accounting of the downstream transaction.
With on-the-fly upgrade, a new profile option SLA: On-the-fly Upgrade of Historical Subledger Accounting Distributions is introduced which when set to Yes will cause a dedicated procedure to identify the few upstream
transactions missing XDL and populate them on the fly, prior to
accounting the downstream transaction, and this is transparent to the user.
Thus the volume of transactions which "require" upgrade is reduced from
a huge number (across multiple years and applications) to just a few
upstream transactions which are related to the current downstream
Key benefits of this enhancement:
- Prior to the enhancement, even if there
is a single upstream transaction in payables which is missing
distribution links, users would be required to apply the hot patch for
the entire non-upgraded date range, till the period containing the
upstream transaction. e.g. consider the earliest upgraded period is
JAN-14. If user pays an upgraded invoice from 11i which has a GL date as
JAN-2000, then when using hot patch or the On-Demand distribution links
upgrade users would need to upgrade the transactions for around 13
years of invoices and payment both. Hence, accounting a single
transaction required upgrade for all of the transactions for over 13
years, which due to data volume and complexities of upgrade be very time
- Also, hot patch required that all the
data be upgraded for 'all' applications (not just payables), which adds
to the time and complexity of upgrade.
- Also, even if there is a single
transaction in the overall time duration which when upgraded (to create
XLA_DISTRIBUTION_LINKS records for the upstream transactions) which
would cause the Hot patch or On Demand XDL upgrade to error out
(XLA_DISTRIBUTION_LINKS_U1 violation), the entire concurrent process
would fail. Scanning the entire time duration for corruptions causing
failure in XDL population, fixing the same, and restarting the upgrade
is often complicated and requires development intervention over bugs,
which causes delays with accounting the downstream transactions.
Please review R12: Important Enhancement ON-THE-FLY Upgrade of Historical SLA Distributions (Doc ID 1938253.1) for full details.
If you have any questions or comments on this new functionality please post in the dedicated Payables Community thread.