Search Results ax_mtl_interorg_parameters_v1

Overview

The view AX_MTL_INTERORG_PARAMETERS_V1 belongs to the AX - Global Accounting Engine product family and presents a focused subset of columns drawn from the MTL_INTERORG_PARAMETERS base table. Its purpose within Oracle E-Business Suite 12.1.1 and 12.2.2 is to expose the inter-organization transfer setup parameters that drive accounting, pricing, and in-transit inventory behavior between a shipping ("from") organization and a receiving ("to") organization. Because the view is a subset rather than a full mirror, it is commonly used for reporting, integration, and validation logic where only the accounting-relevant and location-relevant attributes of an inter-org relationship are required.

The columns exposed by the view are the inter-org identifiers, audit columns, in-transit and distance attributes, transfer characteristics, and the four accounting accounts that govern inter-org financial flow, including the INTERORG_RECEIVABLES_ACCOUNT that users frequently search for. The documentation notes that the view is "Not implemented in this database," meaning it may not be present in every environment and should be validated against the target instance before being referenced in custom code.

Underlying Base Objects

The view is defined entirely over a single base object: MTL_INTERORG_PARAMETERS. The documented view text is a straightforward projection:

• Base table: MTL_INTERORG_PARAMETERS
• Documented referenced base objects: none listed beyond the base table in the ETRM metadata
• Owner: not documented in the supplied metadata

Because the view is a subset of the base table, any column present in the view carries the same datatype, precision, and semantics as the corresponding column in MTL_INTERORG_PARAMETERS. There is no join, filter, or aggregation applied in the view text, so row cardinality matches the base table exactly. Consequently, the view can be treated as a convenient, stable projection for consumers that should not depend on the full width of the base table.

Key Columns

The most functionally significant columns exposed by the view are:

• FROM_ORGANIZATION_ID / TO_ORGANIZATION_ID: Identify the shipping and receiving organizations and together form the logical key of an inter-org parameter record.
• INTRANSIT_TYPE: Determines how in-transit inventory is accounted for (for example, whether goods remain in the shipping organization's inventory or are held in a separate in-transit account).
• INTRANSIT_INV_ACCOUNT: The inventory account used while material is in transit.
• INTERORG_RECEIVABLES_ACCOUNT: The account used to record the receivable that the shipping organization establishes against the receiving organization for the inter-org transfer.
• INTERORG_PAYABLES_ACCOUNT: The corresponding payable account recorded by the receiving organization.
• INTERORG_TRANSFER_CR_ACCOUNT: The transfer credit account used in inter-org accounting entries.
• INTERORG_PRICE_VAR_ACCOUNT: The account used to capture price variance between transferred value and receipt value.
• INTERORG_TRNSFR_CHARGE_PERCENT: The percentage charge applied to inter-org transfers.
• MATL_INTERORG_TRANSFER_CODE, FOB_POINT, ROUTING_HEADER_ID: Control transfer method, title transfer point, and routing.
• DISTANCE_UOM_CODE / TO_ORGANIZATION_DISTANCE: Capture distance information for transfer costing.
• INTERNAL_ORDER_REQUIRED_FLAG: Indicates whether an internal order is mandatory.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15: Descriptive flexfield columns for extensible data.

Common Use Cases and Queries

A frequent use case is reporting on the inter-org receivables account configured for a given organization pair. A representative query is:

SELECT FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, INTERORG_RECEIVABLES_ACCOUNT, INTERORG_PAYABLES_ACCOUNT, INTRANSIT_TYPE FROM AX_MTL_INTERORG_PARAMETERS_V1 WHERE FROM_ORGANIZATION_ID = :from_org AND TO_ORGANIZATION_ID = :to_org;

Other scenarios include auditing all organization pairs that use a particular in-transit account, verifying that inter-org accounting setups are complete before enabling transfers, and feeding downstream integrations with the subset of accounting attributes required to build inter-org journal entries. Because the view does not add filters, consumers should still apply appropriate organization security and effective-date considerations when querying production data.