Search Results pjm_organization_id

Overview

CST_XLA_PJM_ORG_PARAMS_REF_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, documented as a VALID database object. It presents organization-level Project Manufacturing (PJM) parameters in a stable, denormalized form suitable for consumption by subledger accounting (XLA), cost management, and external reporting logic. The view name reflects its principal purpose: it acts as a reference (the suffix _REF_V) for PJM organization parameters, supplying the values that the Subledger Accounting and Costing engines need when determining how material transactions are accounted and whether they are eligible for transfer to Oracle Projects.

Although the object is catalogued under the BOM — Bills of Material product grouping within ETRM, its columns are entirely organizational-parameter driven rather than bill-of-material driven. The view is a thin projection over a single source table, with no joins, aggregations, or filtering logic. Its value lies in three characteristics: the renaming of columns to more descriptive aliases, the substitution of a default value for null flags, and the uniform exposure of a DFF attribute block. This makes it a dependable interface for code that must not be affected by null flag handling in the base table.

Underlying Base Objects

The view is defined exclusively over the referenced base object PJM_ORG_PARAMETERS, accessed in the APPS schema through a synonym. PJM_ORG_PARAMETERS stores one row per inventory organization for which Project Manufacturing is enabled, holding the operational flags and descriptive flexfield segments that govern project-related transaction behavior. Because the view performs no joins, it introduces no cardinality change: it returns exactly one row per row in PJM_ORG_PARAMETERS, keyed by ORGANIZATION_ID. The view is purely a read-only projection; it cannot be used for DML against the underlying parameters, and any change to PJM organization setup must be made through the corresponding setup form or the base table itself.

Key Columns

• PJM_ORGANIZATION_ID — the inventory organization identifier, aliased from ORGANIZATION_ID. This is the primary join key to organizational reporting.
• ALLOW_CROSS_PROJECT_ISSUES — indicates whether material may be issued across project boundaries; defaults to 'N' where null.
• PA_POSTING_FLAG — the parameter most directly associated with this object in user searches. It controls whether project-related transactions for the organization are eligible for posting to Oracle Projects. A value of 'Y' enables Project Accounting posting; 'N' suppresses it. The view applies NVL(..., 'N'), so a null in the base table is always reported as 'N'.
• PA_AUTO_ACCOUNTING_FLAG — controls automatic accounting for project transactions, exposed as PA_AUTO_ACCOUNTING_FLAG and defaulting to 'N'.
• WIP_AS_STRAIGHT_TIME_FLAG — governs treatment of work in process as straight time, defaulting to 'N'.
• ORG_PJM_ATTRIBUTE_CATEGORY and ORG_PJM_ATTRIBUTE1 through ORG_PJM_ATTRIBUTE15 — the descriptive flexfield context and segments for the organization's PJM parameters, renamed with the ORG_PJM_ prefix to distinguish them from other DFF blocks.

Common Use Cases and Queries

The view is typically queried to confirm whether an organization posts to Projects before running accounting or transfer processes, and to drive conditional logic in custom cost or interface programs. A frequent check resolves the PA posting behavior for a given organization:

• SELECT PJM_ORGANIZATION_ID, PA_POSTING_FLAG, PA_AUTO_ACCOUNTING_FLAG FROM CST_XLA_PJM_ORG_PARAMS_REF_V WHERE PJM_ORGANIZATION_ID = :org_id;
• SELECT PJM_ORGANIZATION_ID FROM CST_XLA_PJM_ORG_PARAMS_REF_V WHERE PA_POSTING_FLAG = 'Y';
• SELECT PJM_ORGANIZATION_ID, ALLOW_CROSS_PROJECT_ISSUES, ORG_PJM_ATTRIBUTE1 FROM CST_XLA_PJM_ORG_PARAMS_REF_V ORDER BY PJM_ORGANIZATION_ID;

Because nulls are coerced to 'N', queries testing equality against 'Y' or 'N' behave predictably without additional NVL handling.