Results for “acceptance_required”

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

Overview

PO_SGD_MOD_HEADERS_V is an Oracle E-Business Suite (EBS) PL/SQL view owned by the APPS schema and classified under the PO – Purchasing product family. It is part of the Supplier Gateway (SGD) modification framework, which supports the sourcing and procurement flows that feed supplier-facing documents such as purchase orders, sourcing agreements, and CLM (Contract Lifecycle Management) contract records. The view does not represent a transactional table in its own right; instead, it denormalizes modified header-level attributes held in the PO_HEADERS_DRAFT_ALL drafting table, converting stored lookup codes, foreign-key identifiers, and person IDs into their human-readable descriptions.

This descriptive, flattened presentation makes the view suitable for concurrent-program extracts, Oracle BI Publisher reports, OAF-based supplier gateway pages, and integration payloads where downstream systems require meaningful labels rather than IDs. The view is validated and documented in ETRM 12.2.2, and is compatible with both 12.1.1 and 12.2.2 EBS releases.

Underlying Base Objects

ETRM documents the following base objects referenced by the view: AP_TERMS (synonym), FND_GLOBAL (package), FND_LOOKUPS (view), HR_LOCATIONS_ALL (synonym), ORG_FREIGHT_TL (synonym), PER_ALL_PEOPLE_F (synonym), PO_DATATEMPLATE_PKG (package), PO_GEN_DIFF_PKG (package), PO_HEADERS_DRAFT_ALL (synonym), PO_LOOKUP_CODES (view), PO_SUPPLIER_CONTACTS_VAL_V (view), and PO_VENDOR_SITES_ALL (view).

The primary driving object is PO_HEADERS_DRAFT_ALL, which stores the draft header records keyed by PH_PO_HEADER_ID and PH_DRAFT_ID. The view emits each modified header attribute as a row, decoding COL_NAME and COL_VALUE via a DECODE expression into display semantics. Reference data is resolved against PO_LOOKUP_CODES (acceptance required, user document status, supplier notification method, freight terms), FND_LOOKUPS (confirming order flag), AP_TERMS (payment terms), HR_LOCATIONS_ALL (ship-to location), PO_VENDOR_SITES_ALL (vendor site code), PER_ALL_PEOPLE_F (buyer agent, contract officer, award administrator), and PO_SUPPLIER_CONTACTS_VAL_V (supplier contact). The packages PO_DATATEMPLATE_PKG and PO_GEN_DIFF_PKG and FND_GLOBAL are supporting PL/SQL constructs used in the surrounding Supplier Gateway logic.

Key Columns

• PK1_VALUE / PK2_VALUE – Composite primary key of the draft header record (PO_HEADER_ID and DRAFT_ID); PK3_VALUE through PK5_VALUE are NULL, reserving positional placeholders.
• COL_NAME – Name of the modified header attribute (for example ACCEPTANCE_REQUIRED_FLAG, CLM_CONTRACT_OFFICER, AGENT_ID, TERMS_ID, VENDOR_SITE_ID).
• COL_VALUE – Stored code, ID, or flag value for that attribute, before decoding.
• Decoded display values – The DECODE expression resolves CLM_CONTRACT_OFFICER, CLM_AWARD_ADMINISTRATOR, and AGENT_ID to FULL_NAME from PER_ALL_PEOPLE_F (restricted to currently effective rows), CLM-related contact lookups to descriptive names, and vendor/terms/location attributes to their descriptive equivalents.

The user search term "clm_contract_officer" directly corresponds to a decoded COL_NAME value, returning the contract officer's full name for the associated draft.

Common Use Cases and Queries

Typical usage retrieves modified header attributes for a draft PO or contract, often to display them in a review or approval page. To isolate the CLM contract officer for a given draft:

• SELECT PK1_VALUE, PK2_VALUE, COL_VALUE FROM APPS.PO_SGD_MOD_HEADERS_V WHERE COL_NAME = 'CLM_CONTRACT_OFFICER';
• SELECT COL_NAME, COL_VALUE FROM APPS.PO_SGD_MOD_HEADERS_V WHERE PK1_VALUE = :po_header_id AND PK2_VALUE = :draft_id;
• Join the view to PO_HEADERS_DRAFT_ALL on PK1_VALUE/PK2_VALUE to reconcile decoded attributes against the originating draft header row.

Because the view drives the Supplier Gateway modification display, it is commonly consumed in extract programs and integration interfaces that synchronize draft changes to suppliers. Bind by primary key wherever possible, as the DECODE subqueries against PER_ALL_PEOPLE_F and lookup tables can impose performance cost at scale.