Results for “gl_aloc_inp_efc”

24 results




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

Overview

GL_ALOC_INP_EFC is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a shadow table of GL_ALOC_INP, created specifically for Economic and Monetary Union (EMU) and Euro Financial Conversion (EFC) migration. During a Euro conversion project, monetary values recorded in legacy national currencies must be re-expressed in Euro. Rather than overwriting the original figures, Oracle preserves the pre-conversion values in a dedicated shadow table so that reconciliation, audit trails, and rollback remain possible. GL_ALOC_INP_EFC serves precisely that purpose for allocation input amounts.

The table stores the primary key columns of GL_ALOC_INP together with the original (pre-Euro) values of the columns that are flagged for conversion. This design allows the conversion program to compare original and converted amounts and provides a retained audit record of the source data. From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone; a practical modeling suggestion would be to treat it as a satellite of the GL_ALOC_INP hub, since it carries descriptive, conversion-relevant attributes keyed to the parent allocation input row rather than defining new business entities or relationships.

Key Information Stored

The documented physical schema for GL_ALOC_INP_EFC in ETRM 12.2.2 contains three columns:

  • GL_ALOC_INP_ID — The identifier that links this shadow row to its parent row in GL_ALOC_INP. It is the foreign-key column and the principal business-key candidate for joining back to the source allocation input record.
  • AMOUNT — The original monetary amount from GL_ALOC_INP prior to Euro conversion. This is the converted-value column whose pre-EFC figure is preserved here.
  • SET_OF_BOOKS_ID — The accounting set of books under which the allocation input was recorded, providing the currency and ledger context required to interpret the stored amount.

No surrogate primary key column beyond the referenced GL_ALOC_INP_ID is documented; the stored columns align with the primary key of the parent table plus the convertible amount. Because the column list is limited, the table should be regarded as a narrow, purpose-built companion rather than a full mirror of GL_ALOC_INP.

Common Use Cases and Queries

Typical scenarios center on Euro conversion validation and post-conversion auditing:

  • Reconciliation before and after EFC: Compare preserved original amounts in GL_ALOC_INP_EFC against converted amounts in GL_ALOC_INP to confirm correct application of the fixed conversion rate and rounding rules.
  • Audit and rollback support: Retrieve the pre-conversion amount for a given allocation input if the conversion must be reversed or investigated.
  • Ledger-specific reporting: Group preserved amounts by SET_OF_BOOKS_ID to assess the monetary impact of conversion across sets of books.

A representative reconciliation query:

  • SELECT e.GL_ALOC_INP_ID, e.SET_OF_BOOKS_ID, e.AMOUNT AS ORIGINAL_AMOUNT, a.AMOUNT AS CONVERTED_AMOUNT FROM GMF.GL_ALOC_INP_EFC e JOIN GMF.GL_ALOC_INP a ON a.GL_ALOC_INP_ID = e.GL_ALOC_INP_ID WHERE e.SET_OF_BOOKS_ID = :set_of_books_id;

This pattern isolates rows where the converted amount diverges from the preserved original, which is the core control test for an EFC migration.

Related Objects

The table's relationships are deliberately narrow. The principal objects are:

  • GL_ALOC_INP — The parent allocation input table. The foreign key GL_ALOC_INP_EFC.GL_ALOC_INP_ID references GL_ALOC_INP, and this is the primary join path.
  • GL_ALOC_INP_EFC (self as shadow) — Conceptually paired with GL_ALOC_INP for all EFC comparisons.
  • GL sets of books / GL_SETS_OF_BOOKS — Provides the ledger and currency context referenced by SET_OF_BOOKS_ID.
  • GMF allocation and costing tables — Allocation processing and cost rollup objects that consume GL_ALOC_INP amounts and are indirectly affected by EFC conversion.

No additional foreign keys or dependent views are documented beyond the GL_ALOC_INP reference, reinforcing its role as a standalone EFC shadow artifact rather than a central transactional table.