Results for “jmf_shikyu_grp”

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

Overview

JMF_SHIKYU_GRP is the group package for the Charge Based SHIKYU project within Oracle E-Business Suite. SHIKYU is the Japanese consignment and subcontracting settlement model in which a supplier (or subcontractor) is compensated not for material content but for value-added processing charges, with title to material flowing to the buying enterprise. The package centralizes the shared PL/SQL logic that other products — including Costing (CST), Receiving (RCV), Purchasing (PO), and Financials Globalization — invoke to support SHIKYU processing. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, an important consideration where APPS-owned synonyms are referenced.

The package was created on 20-APR-2005, extended in September 2005 with the AP invoice nettable function, and revised in 2007 for the 12.1 Buy/Sell subcontracting changes and for Bug 6679369, which required the subcontracting type to be passed to Costing for outside processing receipts in standard costing organizations.

Key Procedures and Functions

• GET_SHIKYU_VARIANCE_ACCOUNT — Returns the variance account to be used for a given PO shipment. Its signature was modified by Bug 6679369 to also return the subcontracting type, so that Costing posts outside processing (OSA) receipts to the correct account in standard costing organizations.
• GET_PO_SHIPMENT_OSA_FLAG — Determines whether a PO shipment is associated with outside processing / OSA activity, returning the flag to the caller.
• IS_TP_ORGANIZATION — Validates whether a given organization is a third-party (trading partner) organization, used to qualify SHIKYU-eligible transactions.
• IS_AP_INVOICE_SHIKYU_NETTABLE and IS_AP_INV_SHIKYU_NETTABLE_FUNC — Determine whether an AP invoice is eligible for SHIKYU netting. The function variant was added in September 2005 to provide the same test in a callable SQL context.
• IS_SO_LINE_SHIKYU_ENABLED — Tests whether a given order management sales order line participates in SHIKYU processing.
• VALIDATE_OSA_FLAG — Validates the consistency of the OSA flag before downstream processing proceeds.
• GET_SHIKYU_ATTRIBUTES — Retrieves the SHIKYU attribute set applicable to the transaction under evaluation.
• GET_SUBCONTRACTING_TYPE — Returns the subcontracting type for the supplied context, supporting the 12.1 Buy/Sell changes.

Tables Accessed

The package reads and writes through APPS synonyms across several product schemas. Purchasing and receiving data is drawn from PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and PO_ASL_ATTRIBUTES. Payables netting logic references AP_INVOICE_DISTRIBUTIONS_ALL. Inventory and organization context comes from MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B, MTL_INTERORG_PARAMETERS, and HR_ORGANIZATION_INFORMATION. Order Management participation is checked via OE_ORDER_LINES_ALL. SHIKYU-specific state is held in JMF_SHIKYU_REPLENISHMENTS and JMF_SUBCONTRACT_ORDERS, with DUAL used for scalar evaluations.

Usage Notes

JMF_SHIKYU_GRP is not intended as an end-user interface; it is a shared services layer. It is referenced by five other packages, and standard EBS flows — receiving and inspection, outside processing receipt, invoice validation, and cost processing — call into it to determine SHIKYU eligibility, netting status, and account derivation. Customizations that must behave consistently with seeded SHIKYU logic should call these APIs rather than reimplementing the checks against the underlying tables, since the logic accounts for organization type, subcontracting type, and shipment-level nuances that are not obvious from the base data alone.