Results for “update_header_status”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGIGITCH is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite Treasury and intercompany invoicing infrastructure. In the standard EBS data dictionary the package is classified as OTHER rather than as a public API, indicating that it is an internal utility rather than a supported integration entry point. Its declared signature — AUTHID CURRENT_USER — confirms that it executes with the privileges of the calling schema, so any user or program unit invoking it must already hold the necessary object grants.

The package originates from the Oracle Intercompany Invoicing (IGI) product family, a subset of the Treasury module used to generate and reconcile intercompany charge documents between internal organizations, business units, and balancing segments. The package name follows the IGI intercompany naming convention and the source header reference igiitros.pls places it in the intercompany transaction reconciliation area of the product. Its single exposed entry point governs the lifecycle state of an intercompany charge document header, making it the control point through which downstream processing, validation, and accounting events are gated.

Functionally, IGIGITCH encapsulates header status transition logic so that multiple callers apply the same state changes consistently rather than issuing direct DML against the underlying tables. This centralization is what allows the package to be reused by other program units without duplicating business rules.

Key Procedures and Functions

The documented specification exposes a single procedure.

  • UPDATE_HEADER_STATUS — Updates the status attribute of an intercompany charge document header identified by its header identifier. The procedure accepts the header identifier as its input and performs the status transition for that document. By isolating this operation, the package ensures that any change to a header's processing state is applied through one controlled path, which is significant because header status typically drives whether downstream charge lines, accounting entries, and reconciliation steps are permitted to progress. No parameter list beyond the header identifier is invented here; the specification documents only the header ID input.

No functions are declared in the package specification, and no additional procedures are listed in the ETRM metadata for release 12.2.2.

Tables Accessed

The package operates against two documented base tables via APPS synonyms.

  • IGI_ITR_CHARGE_HEADERS — The header table for intercompany charge documents. This is the primary target of the status update, holding the document-level status flag that the procedure modifies.
  • IGI_ITR_CHARGE_LINES — The corresponding line-level detail table. Access to the lines is typically required to evaluate or cascade the effects of a header status change, for example to determine whether lines exist that still require processing before a header may be advanced or closed.

Both tables belong to the intercompany transaction reconciliation data model and are referenced through APPS synonyms, which is consistent with the AUTHID CURRENT_USER declaration.

Usage Notes

IGIGITCH is an internal package and is not intended for direct customer invocation. It is referenced by two other packages within the EBS code base, which indicates that it is called from higher-level intercompany processing logic rather than from the user interface directly. Typical invocation paths include concurrent programs that batch-process intercompany charge documents and forms-based flows that finalize or reverse a charge document, where the calling program delegates the header status transition to this package.

Because the package is classified as OTHER in the ETRM dictionary, Oracle does not guarantee its signature across releases or patches; customizations should not call it directly. Where custom code must influence header status, the supported approach is to use documented APIs or to allow the standard intercompany concurrent processes to drive the transition. Implementations upgrading from 12.1.1 to 12.2.2 should verify that the package remains present and that dependent packages are recompiled as part of the standard patch cycle, since an invalidated IGIGITCH will block the calling intercompany programs.