Search Results update_header_status

Overview

The APPS.IGIGITCH package body supports the Oracle E-Business Suite intercompany cross-charge processing flow, a component of the Oracle Intercompany (IGI) product family. Its business purpose is to maintain the status integrity of intercompany transfer pricing charge headers (IGI_ITR_CHARGE_HEADERS) by reconciling them against the individual service charge lines (IGI_ITR_CHARGE_LINES) they contain. When every constituent service line has reached a terminal state — either approved or cancelled — the associated header is considered finished, and the package promotes the header to a "Complete" status. This package serves as the finalization logic for the cross-charge transfer pricing workflow, ensuring that a header is not marked complete prematurely while dependent service lines remain open.

Key Procedures and Functions

The package exposes one documented procedure:

• UPDATE_HEADER_STATUS — Accepts an intercompany transfer pricing header identifier and evaluates whether the header should be closed. The procedure counts the total number of charge lines associated with the given header, then counts the subset of those lines whose status flag indicates approval or cancellation. When the two counts are equal, the procedure updates the corresponding record in IGI_ITR_CHARGE_HEADERS, setting the submit flag to the completion value. The documented parameter list is not reproduced here; the procedure is driven by a single header identifier input.

No additional public or private procedures or functions are documented for this package.

Tables Accessed

• IGI_ITR_CHARGE_HEADERS — The master charge header table. The package performs an UPDATE against this table, writing the submit flag value of 'C' (Complete) to the header row identified by the passed header ID. This write occurs only when all associated lines are in a terminal state.
• IGI_ITR_CHARGE_LINES — The detail charge line table. The package performs two read operations (COUNT queries) against this table: one returning the total line count for the header, and one returning the count of lines whose status flag is either 'L' (cancelled) or 'A' (approved). These reads determine whether the header is eligible for completion.

Both tables are referenced through APPS synonyms, consistent with standard Oracle EBS schema access conventions.

Usage Notes

Because the API classification is OTHER and the package header is dated 2007, this is an internally invoked support package rather than a published, externally callable API. It is referenced by two other packages, indicating that it is called within the intercompany transfer pricing processing chain rather than directly by end users. Typical invocation paths include:

• Workflow or concurrent processing — Status transitions on charge lines trigger reevaluation of the parent header, allowing the header to close automatically once the last line is approved or cancelled.
• Forms-driven transactions — Approval or cancellation actions performed through the intercompany transfer pricing forms may indirectly cause the calling package to invoke this procedure.
• Custom extensions — Sites integrating with the IGI cross-charge flow may call this procedure when programmatically applying status changes to charge lines.

Because the procedure only updates the header when counts match, repeated invocation is effectively idempotent for an already-completed header. Implementers modifying downstream status logic should account for the fact that the package recognizes only the 'L' and 'A' flags as terminal states; any newly introduced line status not included in that set will prevent header completion.