Search Results get_accounts

Overview

GMF_TRANSACTION_ACCOUNTS_PUB is a public PL/SQL API package in the APPS schema that belongs to the Oracle Process Manufacturing (OPM/GMF) financial integration layer. Its business purpose is to resolve the correct General Ledger account (the accounting flexfield combination, or CCID) for a given manufacturing transaction, based on a defined set of context attributes such as organization, item, ledger, legal entity, subinventory, locator, lot, and vendor information. It acts as the account derivation engine used when OPM transactions must be translated into Subledger Accounting (XLA) events and ultimately posted to the General Ledger.

The package exposes a single documented public entry point, GET_ACCOUNTS, and a set of public record types used to pass transaction data in and receive the derived account back out. This design makes the API a callable, reusable account-determination service for OPM costing and accounting flows rather than a standalone user-facing program.

Key Procedures and Functions

• GET_ACCOUNTS — The sole documented public procedure. It accepts a standard EBS API header including the API version, an initialization flag for the message list, and a source indicator, and it returns the standard API status triple: return status, message data, and message count. Its core function is to derive the target accounting flexfield for a transaction. The parameters that drive that derivation are not passed as a flat argument list on the procedure itself; instead they are supplied through the public record types declared in the package specification.
• t_rec_gmf_xla_tab_PUR — A public record type representing a purchasing-oriented transaction line. It carries a set of source distribution identifiers and an account_type_code (INV, EXP, or AAP, mandatory) along with a source attribute list covering organization, inventory item, item type, ledger, legal entity, operating unit, subinventory, locator, lot number, vendor, and vendor site. It returns the resolved target_ccid, the concatenated_segments, and message count/data outputs.
• t_rec_gmf_xla_tab_CTO — A public record type representing a configure-to-order/ATO-oriented transaction line. It mirrors the PUR structure with source distribution identifiers and the same mandatory account_type_code, but its source list includes an ato_flag in place of the PUR-specific attributes, reflecting the different inputs required to derive accounts for ATO transactions.

Tables Accessed

• MTL_PARAMETERS — The inventory organization parameters table. It is read to obtain organization-level defaults, such as the default account set and costing/valuation context, that influence account derivation.
• FND_LOG_MESSAGES — Used by the FND logging framework to record diagnostic and error messages generated during account resolution, supporting the x_msg_data and message-count outputs.
• DBMS_UTILITY — A supplied PL/SQL package, not an application table, invoked to format and manage the message stack used by the standard API error-handling conventions.
• PLITBLM — The PL/SQL table handling package, used for message list management consistent with the EBS API framework.

Usage Notes

GET_ACCOUNTS is a programmatic API and is not intended for direct end-user invocation. It is typically called from custom PL/SQL routines, from OPM costing and accounting concurrent programs, and from other integration packages that need to translate a manufacturing transaction into its accounting flexfield combination before creating XLA events. ETRM records the package as referenced by one other package, confirming it functions as a dependent service inside a larger accounting integration chain.

Callers must populate the relevant public record type (PUR for purchase-related lines, CTO for ATO lines), including the mandatory account_type_code, before calling GET_ACCOUNTS, and must inspect x_return_status together with x_msg_data and x_msg_count to detect derivation failures. Because account determination depends on the accounting configuration defined in the ledger, legal entity, and inventory organization setup, results reflect the configuration effective at the time of the call, and any change to accounting rules or organization defaults can alter the returned CCID.