Results for “cstfv_manufacturing_gl_batch”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSTFV_MANUFACTURING_GL_BATCH is an APPS-owned read-only view in Oracle E-Business Suite that exposes manufacturing general ledger batch information for cost and accounting reporting. It is delivered under the BOM (Bills of Material) product family and carries the ETRM status "Retrofitted," indicating it was carried forward from an earlier release into the 11i/R12 architecture without a redesign of its underlying structure. The view presents one row per GL batch identified within an inventory organization and its associated accounting period, joined to organization and period descriptive attributes for reporting convenience.
Because the view is declared WITH READ ONLY, it is intended exclusively for query and reporting use. It does not support DML and should not be targeted by interfaces performing inserts or updates. Its principal role is to provide a denormalized, security-aware projection of GL batch data so that cost accountants, period-close analysts, and reporting tools can retrieve batch identifiers, dates, and organizational context without joining the base cost tables manually. The embedded '_SEC:OGB.ORGANIZATION_ID' IS NOT NULL predicate integrates the view with Oracle's organization-level security (MOAC) framework, so rows are filtered according to the organization access granted to the invoking responsibility.
Underlying Base Objects
The view is defined over four documented base objects, all referenced through APPS synonyms:
- ORG_GL_BATCHES (OGB) — the driving table, supplying the organization, GL batch identifier, description, accounting period, GL batch date, and WHO audit columns.
- ORG_ACCT_PERIODS (OAP) — joined on ORGANIZATION_ID and ACCT_PERIOD_ID to supply the accounting period name and to validate that the batch period belongs to the organization.
- MTL_PARAMETERS (MP) — joined on ORGANIZATION_ID to provide the inventory organization code.
- HR_ALL_ORGANIZATION_UNITS (HAOU) — joined on ORGANIZATION_ID to provide the organization name.
The joins are equijoins on ORGANIZATION_ID (and ACCT_PERIOD_ID for ORG_ACCT_PERIODS), producing a single consolidated row per batch. The BOM product assignment reflects that GL batch creation for manufacturing is driven by the cost management and manufacturing accounting process, where resource and overhead transactions are grouped into batch headers before transfer to the general ledger.
Key Columns
- ORGANIZATION_ID — Inventory organization identifier; the MOAC security key for the view.
- ORGANIZATION_CODE — From MTL_PARAMETERS; the short code used in operational reporting.
- ORGANIZATION_NAME — From HR_ALL_ORGANIZATION_UNITS; the descriptive organization name.
- GL_BATCH_ID — Surrogate identifier of the GL batch within the organization.
- DESCRIPTION — Free-text description of the batch.
- ACCT_PERIOD_ID — Foreign key to the accounting period.
- ACCOUNT_PERIOD_NAME — From ORG_ACCT_PERIODS; the human-readable period (for example, JAN-24).
- GL_BATCH_DATE — The date assigned to the GL batch; this is the column most commonly searched by users seeking batches by accounting date.
- CREATED_DATE, CREATED_BY, UPDATED_DATE, UPDATED_BY — WHO audit columns inherited from ORG_GL_BATCHES.
Common Use Cases and Queries
Typical usage centers on period-close reconciliation and audit. Analysts list all batches for an organization and period, compare batch dates against period boundaries, and verify that every manufacturing batch has been transferred to the GL. A representative query filtering on the commonly searched date column is:
SELECT organization_code, organization_name, gl_batch_id, description, account_period_name, gl_batch_date FROM apps.cstfv_manufacturing_gl_batch WHERE gl_batch_date BETWEEN :p_from_date AND :p_to_date ORDER BY organization_code, gl_batch_date;
Additional scenarios include listing batches for a specific accounting period by name or ID, and auditing creation and update metadata to determine who generated a batch and when. Because MOAC is enforced, results automatically reflect the organization access of the connected responsibility, making the view suitable for both ad hoc SQL and embedded use in concurrent programs and BI Publisher reports.
-
- Retrofitted
APPS.CSTFV_MANUFACTURING_GL_BATCH·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ ORG_ACCT_PERIODS·Explore BOM module →
-
- Retrofitted
APPS.CSTFV_MANUFACTURING_GL_BATCH·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ ORG_ACCT_PERIODS·Explore BOM module →
-
SYNONYM: APPS.ORG_GL_BATCHES 12.1.1
-
SYNONYM: APPS.ORG_GL_BATCHES 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.