Search Results xla_update_inval_ccid_api

Overview

The APPS.XLA_UPDATE_INVAL_CCID package is a Subledger Accounting (XLA) maintenance utility whose stated purpose is to support the "Update Invalid CCIDs" program. It exists to resolve accounting entries that were queued with invalid code combinations (CCIDs) during subledger accounting processing. When Subledger Accounting generates accounting entries, the combination of the accounting flexfield segments on each line is validated against the Chart of Accounts. If a code combination cannot be resolved at the time the entry is created, the entry is placed in a pending or invalid state rather than being rejected outright. XLA_UPDATE_INVAL_CCID provides the programmatic mechanism by which those previously invalid code combinations are re-evaluated and the affected accounting entries are corrected.

The package header comment states explicitly that the API "will be called from the Java Layer once the BPEL returns the invalid ccids," and that the "java cp will call this API to Update Accounting Entries with the invalid status." This identifies the package as part of an external integration flow rather than an end-user-facing concurrent program in the traditional sense. The package source is versioned under the filename xlaudccid.pkh and was created in 2008 by Jagan Koduri, consistent with the XLA architecture introduced in Release 11i and carried forward into Release 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package.

• XLA_UPDATE_INVAL_CCID_API — The sole documented entry point. Its declared parameters (as shown in the package specification excerpt) are p_accounting_batch_id, p_ledger_id, p_application_id, p_ccid (a table of code combination identifiers), p_status, and p_err_msg. The procedure accepts a batch of invalid code combinations for a given accounting batch, ledger, and application, and updates the corresponding accounting entries to reflect the corrected combination and status. The p_err_msg parameter carries error context back to the calling layer when the update cannot be completed. The package also declares a private collection type, t_array_ccid, indexed by BINARY_INTEGER, used to pass the set of code combinations into the procedure.

Tables Accessed

The documented tables referenced through APPS synonyms are the core Subledger Accounting tables and the standard PL/SQL message table:

• XLA_AE_HEADERS — The accounting entry header table. The package reads and updates headers associated with the identified accounting batch so that header-level code combination references are corrected.
• XLA_AE_LINES — The accounting entry line table. Line-level code combinations are the primary target of the update, since invalid CCIDs are recorded at line granularity.
• XLA_EVENTS — The subledger event table. Events whose accounting was deferred due to invalid combinations may be revisited so that accounting can be completed or reprocessed.
• PLITBLM — The legacy PL/SQL table/index-by table used internally for message or rowset handling.

Usage Notes

Because the package is classified as OTHER and is referenced by no other packaged objects, it is not part of the normal Subledger Accounting call stack. It is expected to be invoked from the Java integration layer after an external BPEL process has determined which code combinations are invalid, passing the results back through XLA_UPDATE_INVAL_CCID_API. In Oracle E-Business Suite 12.1.1 and 12.2.2 this pattern supports environments where code combination validation is delegated to an external service or middleware component.

Custom code should call the procedure through the APPS schema with the AUTHID CURRENT_USER privilege model in mind, supplying a properly populated collection of CCIDs, the target accounting batch, ledger, and application identifiers. Because the package writes directly to Subledger Accounting tables, it should be invoked only for genuinely invalid combinations that have been validated externally, and always within a controlled transaction so that failed batches can be rolled back.