Search Results interorg_expense_account

Overview

APPS.CST_XLA_INTERORG_PARAMS_REF_V is an internal Oracle E-Business Suite view, owned by the APPS schema and registered under FND Design Data as BOM.CST_XLA_INTERORG_PARAMS_REF_V. It is flagged Oracle Internal Use Only, meaning Oracle does not support direct access except from standard Oracle Applications programs. The view is VALID in both 12.1.1 and 12.2.2.

Its purpose is to resolve the general ledger account assignments used by Subledger Accounting (XLA) when generating accounting entries for inter-organization transfers in Oracle Inventory and Cost Management. Because inter-organization accounting depends on shipping and receiving organization combinations, the view returns the debit, credit, receivables, payables, variance, profit, bridging, expense, and revenue accounts applicable to a given organization pair, together with the associated XLA EVENT_ID.

This view is the primary reference for the search term interorg_txfr_credit_account: the column INTERORG_TXFR_CREDIT_ACCOUNT exposes the account identifier credited when inventory is transferred out of a shipping organization.

Underlying Base Objects

Per the documented dependency information, the view references the following objects:

• CSTPSCHK (PACKAGE) — a Cost Management package whose routine(s) are invoked in the view definition to derive or validate account parameters for the organization pair.
• CST_XLA_INV_HEADERS_V (VIEW) — the Subledger Accounting inventory headers view that supplies the XLA event context (including EVENT_ID).
• MTL_INTERORG_PARAMETERS (SYNONYM) — the inter-organization parameters table (synonym resolving to MTL_INTERORG_PARAMETERS), which stores the account assignments for the from/to organization relationship.
• XLA_EVENTS_GT (SYNONYM) — the global temporary table holding XLA event information used during accounting program execution.

Conceptually, the view joins the inter-organization parameter setup (the organization-pair account assignments) to the XLA inventory header context and event data, applying the CSTPSCHK logic to return a single row of resolved account identifiers for each FROM/TO organization and event combination.

Key Columns

• FROM_ORGANIZATION_ID (NUMBER) — shipping organization identifier.
• TO_ORGANIZATION_ID (NUMBER) — receiving organization identifier.
• INTERORG_TXFR_DEBIT_ACCOUNT (NUMBER) — inter-organization transfer debit account.
• INTERORG_TXFR_CREDIT_ACCOUNT (NUMBER) — inter-organization transfer credit account; this is the column matched by the user's search.
• INTERORG_RECEIVABLES_ACCOUNT (NUMBER), INTERORG_PAYABLES_ACCOUNT (NUMBER) — receivables and payables accounts used when the transfer is modeled as an internal sale/purchase.
• INTERORG_PRICE_VAR_ACCOUNT (NUMBER) — price variance account for the transfer.
• PROFIT_IN_INV_ACCOUNT (NUMBER) — profit in inventory account.
• INTERORG_PROFIT_ACCOUNT (NUMBER) — inter-organization profit account.
• INTERORG_BRIDGING_ACCOUNT (NUMBER) — inter-organization bridging account.
• INTERORG_EXPENSE_ACCOUNT (NUMBER) and INTERORG_REVENUE_ACCOUNT (NUMBER) — expense and revenue accounts.
• EVENT_ID (NUMBER, length 15) — XLA event identifier linking the account set to a specific subledger event.

All account columns are numeric identifiers referencing GL_CODE_COMBINATIONS.CODE_COMBINATION_ID; they are not concatenated flexfield strings.

Common Use Cases and Queries

The view is used primarily for diagnostics and reconciliation of inter-organization accounting in Subledger Accounting. Because it is unsupported for direct access, it should be used read-only, preferably against a clone or with Oracle Support guidance.

Use case 1 — verify the credit account configured for a shipping/receiving organization pair:

SELECT from_organization_id,
       to_organization_id,
       interorg_txfr_credit_account
  FROM apps.cst_xla_interorg_params_ref_v
 WHERE from_organization_id = :p_from_org
   AND to_organization_id  = :p_to_org;

Use case 2 — resolve the full account set for a specific XLA event:

SELECT v.from_organization_id,
       v.to_organization_id,
       v.interorg_txfr_debit_account,
       v.interorg_txfr_credit_account,
       v.interorg_bridging_account,
       gcc.concatenated_segments
  FROM apps.cst_xla_interorg_params_ref_v v,
       apps.gl_code_combinations_kfv gcc
 WHERE v.event_id = :p_event_id
   AND gcc.code_combination_id = v.interorg_txfr_credit_account;

Use case 3 — compare configured accounts against the accounts actually used in XLA_AE_LINES for inter-organization events, isolating mismatches in the credit or bridging accounts. This is a standard technique for investigating cost distribution and inventory transfer accounting discrepancies.