Search Results gmf_ar_get_invoice_lines_id

Overview

APPS.GMF_AR_GET_INVOICE_LINES_ID is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is classified as a utility/query API (API classification: OTHER) rather than a standard interface or business event API. The package is designed to resolve or retrieve the identifier of invoice lines associated with Oracle Receivables transactions. Its name follows the Process Manufacturing (GMF) naming convention, indicating that it was created in support of the Oracle Process Manufacturing financials integration with Oracle Receivables. In this role, the package bridges transaction header data (RA_CUSTOMER_TRX_ALL) with transaction line data (RA_CUSTOMER_TRX_LINES_ALL) so that callers can obtain the surrogate key of one or more receivable invoice lines given defined selection criteria.

The package status is documented as VALID in the ETRM repository, confirming that the stored package specification and body compile cleanly against the referenced objects in Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM documentation records a single documented program unit within this package:

• GET_INVOICE_LINES_ID — The package's sole documented procedure or function. As the name implies, its purpose is to return the invoice line identifier (line ID) for a Receivables transaction line based on the input criteria supplied by the caller. Because the ETRM metadata does not expose the formal parameter list, no specific arguments, datatypes, or return modes should be assumed; integrators must inspect the package specification directly in the database to determine the exact signature before invoking it from custom code.

No additional procedures or functions are documented for this package. Practitioners should treat this as a focused, single-purpose retrieval utility.

Tables Accessed

The dependency listing identifies three APPS synonym-based tables referenced by this package:

• RA_CUSTOMER_TRX_ALL — The Receivables transaction header table. The package uses this to identify the parent transaction (invoice/credit memo/debit memo) from which line IDs are to be retrieved.
• RA_CUSTOMER_TRX_LINES_ALL — The transaction line table. This is the primary source of the invoice line identifiers the package returns, joined to the header through the customer transaction identifier.
• RA_CUST_TRX_TYPES_ALL — The transaction type definition table. It provides the classification metadata (for example, invoice versus credit memo) that constrains which transaction types are considered eligible when resolving line IDs.

All three are standard Oracle Receivables tables accessed through APPS synonyms. The dependency list does not indicate references to Process Manufacturing tables directly, suggesting the GMF context is expressed through the caller rather than through the query itself.

Usage Notes

The ETRM repository shows that GMF_AR_GET_INVOICE_LINES_ID is not referenced by any other documented package (zero inbound dependencies) and references only standard Receivables tables. The object appears in the dependency tree as both a referencing and referenced entry for its own package name, which is characteristic of recursive or self-referential compilation entries rather than external callers.

In practice, a package of this shape is typically invoked from one of the following contexts:

• Process Manufacturing customizations or extensions that must translate an approved transaction into its corresponding Receivables line identifier before downstream processing.
• Custom PL/SQL routines that need a normalized lookup of RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID without embedding the join logic in every caller.
• Data conversion or reconciliation scripts that align GMF financial records with Receivables transactions.

Because the package exposes no documented public interface details, developers integrating with it in EBS 12.1.1 or 12.2.2 should query ALL_OBJECTS and ALL_ARGUMENTS for the package specification, verify the signature, and grant execute privileges as required. Direct modification of the package is not supported; it is shipped as part of the APPS schema and should be treated as Oracle-owned code.