Search Results get_expenses

Overview

GMF_ALLOC_PROC is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an OTHER API within the Process Manufacturing (GMF) family of modules. Its principal business function is the allocation of expenses across cost allocation codes. Operating under AUTHID CURRENT_USER, the package provides the server-side engine that executes cost allocation processing for a given legal entity, calendar, period, and cost type. The header comment identifies COST_ALLOC_PROC as the main entry point that "allocates the expenses," accepting a from/to allocation code pair and a refresh directive that determines whether the interface table is repopulated. Audit WHO columns are seeded from FND_GLOBAL (user_id, login_id, prog_appl_id, conc_program_id, conc_request_id) and fiscal policy context is held in a row type anchored to GMF_FISCAL_POLICIES, confirming the package is designed for concurrent request execution within the standard EBS security and audit model.

Key Procedures and Functions

The package exposes ten documented procedures. COST_ALLOC_PROC is the main driver, orchestrating expense allocation for a specified fiscal policy context (legal entity, calendar, period, cost type, fiscal year, period number) and range of allocation codes. DELETE_ALLOCATIONS removes existing allocation records for a given allocation code, supporting reruns and correction cycles. GET_LEGAL_ENTITY_DETAILS retrieves legal entity attributes needed to establish processing context. COST_ALLOCATE performs the core allocation computation and posting logic. GET_EXPENSES retrieves the expense amounts to be distributed. INSERT_ALLOC_INP is the procedure that inserts allocation input rows into the interface table — the object most commonly sought by users searching for "insert_alloc_inp" — and is invoked as part of the allocation pipeline rather than directly by end users. PUT_ALLOC_EXPENSES writes allocated expense results. GET_ALLOC_BASIS retrieves the allocation basis (driver) definitions used to prorate expenses. REFRESH_FIXED rebuilds or refreshes fixed allocation data. PROCESS_ALLOC_DTL processes allocation detail records to complete the allocation cycle. Together these procedures form a sequential pipeline: gather context and expenses, compute the basis, allocate, persist input and expense rows, and optionally refresh interface data.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. GL_ALOC_MST and GL_ALOC_DTL supply allocation master and detail definitions, while GL_ALOC_BAS provides allocation basis (driver) information. GL_ALOC_EXP holds expense amounts and GL_ALOC_INP is the allocation input/interface table populated by INSERT_ALLOC_INP. GMF_FISCAL_POLICIES supplies fiscal policy context, and CM_CLDR_HDR / CM_CLDR_DTL provide calendar header and detail rows for period validation. CM_MTHD_MST holds cost method information. FND_APPLICATION, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS support concurrent program and request context lookups, and FND_ID_FLEX_STRUCTURES supports key flexfield structure resolution, consistent with the package's use of account key flexfield segment and delimiter variables. Sequences GEM5_ALLOCDTL_ID_S and GEM5_GL_ALOC_INP_ID_S generate surrogate keys for allocation detail and allocation input rows, respectively.

Usage Notes

GMF_ALLOC_PROC is not referenced by any other documented package, indicating it is a top-level API invoked from concurrent programs, Oracle Forms, or custom code rather than from peer PL/SQL packages. The standard invocation path is a concurrent program submitting COST_ALLOC_PROC with the legal entity, calendar, period, cost type, fiscal year, period number, from/to allocation codes, and the refresh interface flag; errbuf and retcode follow the standard concurrent program signature so errors surface in the request log. The v_refresh_interface parameter (0 = do not refresh, 1 = refresh the interface table) governs whether existing interface rows are cleared before insertion. Custom integrations requiring the allocation input table to be populated should call the package through its documented entry points rather than invoking INSERT_ALLOC_INP directly, since it depends on context established by earlier procedures in the pipeline. Because the package relies on FND_GLOBAL values for WHO columns, it should execute within a concurrent request or an initialized EBS session. The C_MODULE constant ('gmf.plsql.cost_alloc_proc') and log file constants indicate integrated message logging for diagnostics across versions 12.1.1 and 12.2.2.