Results for “validate_osa_flag”

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

Overview

APPS.JMF_SHIKYU_GRP is the group package body for the Charge Based SHIKYU project. SHIKYU is the Japanese term for payment or disbursement, and in this context the package supports Oracle's Financials Globalization requirements by providing shared PL/SQL entry points for charge-based payment processing within the Oracle E-Business Suite. The body file, JMFGSHKB.pls, carries the source control header that identifies revision 120.14 dated 27-JUL-2010, originally created in April 2005.

The package's stated purpose is to serve as a central group (GRP) package that other modules — Costing (CST), Receiving (RCV), Purchasing (PO), Order Management, and Financials Globalization — call into to support SHIKYU processing. By centralizing the SHIKYU validation and attribute-retrieval logic, the package establishes a single point of definition for rules that determine whether a given transaction, invoice, shipment, or sales order line is eligible for charge-based payment treatment.

Key Procedures and Functions

The ETRM documentation records nine documented procedures and functions in this group package:

• GET_SHIKYU_VARIANCE_ACCOUNT — Returns the variance account associated with SHIKYU charge processing, allowing callers to resolve the correct accounting distribution.
• GET_PO_SHIPMENT_OSA_FLAG — Retrieves the OSA (Order Shipment Advice) flag for a purchase order shipment.
• IS_TP_ORGANIZATION — Determines whether an organization is a third-party trading partner organization for SHIKYU purposes.
• IS_AP_INVOICE_SHIKYU_NETTABLE — Evaluates whether an AP invoice qualifies for SHIKYU netting.
• IS_AP_INV_SHIKYU_NETTABLE_FUNC — A function variant of the netting test, added in September 2005 at the request of Financials Globalization for their local development and testing environments.
• IS_SO_LINE_SHIKYU_ENABLED — Reports whether a given sales order line is enabled for SHIKYU; the history notes a May 2006 performance fix (bug 5212998) that removed a full table scan from this query.
• VALIDATE_OSA_FLAG — Validates the OSA flag value supplied by a caller.
• GET_SHIKYU_ATTRIBUTES — Returns the SHIKYU attributes needed by external callers.
• GET_SUBCONTRACTING_TYPE — Returns the subcontracting type relevant to SHIKYU charge determination.

Tables Accessed

The package reads and writes through APPS synonyms into the following base tables:

• AP_INVOICE_DISTRIBUTIONS_ALL — invoice distribution data supporting the SHIKYU netting evaluations.
• HR_ORGANIZATION_INFORMATION — organization classification data used by IS_TP_ORGANIZATION.
• JMF_SHIKYU_REPLENISHMENTS — the SHIKYU replenishment records central to the charge-based payment process.
• JMF_SUBCONTRACT_ORDERS — subcontract order data supporting GET_SUBCONTRACTING_TYPE.
• MTL_INTERORG_PARAMETERS and MTL_PARAMETERS — inventory organization parameters used for organizational context.
• MTL_SYSTEM_ITEMS_B — item master data referenced during attribute retrieval.
• OE_ORDER_LINES_ALL — sales order line data behind IS_SO_LINE_SHIKYU_ENABLED.
• PO_ASL_ATTRIBUTES, PO_DISTRIBUTIONS_ALL, and PO_LINE_LOCATIONS_ALL — purchasing data used for shipment OSA flags and charge validation.
• DUAL — used for single-row PL/SQL evaluations.

Usage Notes

The package is referenced by five other packages, confirming its role as a shared dependency across the Charge Based SHIKYU integration surface. Callers in Costing, Receiving, Purchasing, Order Management, and Financials Globalization invoke its procedures and functions rather than reimplementing SHIKYU rules locally. Because the implementation history records deliberate stubbing and leapfrogging of procedures to control dependency uptake, customizations should call the public procedures only and avoid depending on internal package state. Performance-sensitive callers should note the documented fix in IS_SO_LINE_SHIKYU_ENABLED that eliminated a full table scan, and should treat the package as the authoritative source for SHIKYU enablement, netting, and attribute decisions. No form or concurrent program bindings are documented in the ETRM metadata; invocation is therefore presumed to occur from the referencing PL/SQL packages and from custom code.