Results for “po_revision_num”

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

Overview

JAI_RCV_ACCT_DIST_V is an APPS-owned database view shipped with the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. It exposes receiving accounting distribution information by joining Receiving (RCV) and Purchasing (PO) base objects with General Ledger and Human Resources reference data. The view is designed primarily to support the accounting distribution requirements of Asia/Pacific localizations, most notably the receipt accounting and subledger extraction processes that feed regional statutory reporting such as excise, VAT, and customs documentation.

Because it presents receiving transaction data alongside GL code combination identifiers, currency conversion attributes, destination/transaction lookup meanings, and Work in Process (WIP) references, the view serves as a consolidated reporting and integration source. It is commonly consulted by localized reporting programs, reconciliation routines, and custom extracts rather than by the standard receiving transaction forms themselves.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and packages. Documented referenced base objects include:

• Table synonyms: RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, PO_HEADERS, PO_LINES, PO_REQUISITION_LINES, GL_CODE_COMBINATIONS, and JAI_RCV_SUBLED_ENTRIES.
• Views: HR_LOCATIONS and PO_LOOKUP_CODES (aliased twice as PLC1 and PLC2 for destination type and transaction type meanings).
• Packages: FND_GLOBAL and HR_GENERAL, typically used for session context such as organization and security resolution.

The primary driving table is RCV_TRANSACTIONS (aliased RCT), which supplies the receiving transaction quantities, currency conversion details, and WIP references. It joins to RCV_SHIPMENT_HEADERS (RSH) and RCV_SHIPMENT_LINES (RSL) for receipt number, shipment number, packing slip, vendor, item description, and revision. Purchasing context is obtained through PO_HEADERS, PO_LINES, and PO_REQUISITION_LINES. The localization synonym JAI_RCV_SUBLED_ENTRIES (RRSL) supplies accounting dates, entered debit/credit amounts, currency codes, and source document quantities. GL distribution is linked through GL_CODE_COMBINATIONS.

Key Columns

• PO_NUMBER, LINE_NUMBER, REQUISITION_LINE_NUMBER, RECEIPT_NUMBER, SHIPMENT_NUMBER, PACKING_SLIP — purchasing and receipt identification.
• TRANSACTION_ID, ACCOUNTING_DATE, QUANTITY, PRIMARY_QUANTITY, PRIMARY_UOM, SOURCE_DOC_UNIT_OF_MEASURE, SOURCE_DOC_QUANTITY — receiving transaction and quantity details.
• CODE_COMBINATION_ID — the GL accounting flexfield combination for the distribution.
• ENTERED_DR, ENTERED_CR — debit and credit amounts captured in the entered currency for the subledger entry.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, PO_UNIT_PRICE — currency and valuation attributes.
• VENDOR_ID, LOCATION_ID, DELIVER_TO_LOCATION, ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID — vendor and receiving location context.
• ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION, CATEGORY_ID — item identification.
• DESTINATION_TYPE, TRANSACTION_TYPE — decoded lookup meanings from PO_LOOKUP_CODES.
• WIP_ENTITY_ID, WIP_LINE_ID, WIP_REPETITIVE_SCHEDULE_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, BOM_RESOURCE_ID — the Work in Process references. WIP_REPETITIVE_SCHEDULE_ID identifies the repetitive manufacturing schedule when a receipt is directed to a repetitive WIP job.

Common Use Cases and Queries

Typical scenarios include regional receiving accounting reconciliation, statutory receipt-based reporting, and tracing receipts to WIP or GL distributions. A representative query retrieving distributions for a specific receipt is:

SELECT po_number, receipt_number, transaction_id,
       accounting_date, quantity, currency_code,
       entered_dr, entered_credit_or_cr,
       wip_entity_id, wip_repetitive_schedule_id
FROM   apps.jai_rcv_acct_dist_v
WHERE  receipt_number = :receipt_number;

A query isolating receipts linked to repetitive schedules would filter on WIP_REPETITIVE_SCHEDULE_ID IS NOT NULL and join the resulting identifier to the WIP repetitive schedule tables. In practice, the view is consumed by localized subledger and tax reporting programs, and by custom extracts requiring a single denormalized source combining receiving, purchasing, currency, and accounting distribution attributes.