Search Results curreny_code

Overview

APPS.ITG_REQ_HEADERS_V is a public Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as ITG.ITG_REQ_HEADERS_V. It presents a header-level projection of purchasing requisition data, constructed primarily for the generation of XML payloads at the requisition header level. The view is marked VALID in the ETRM repository and is classified as a public view, meaning Oracle documents it as potentially useful for custom reporting or other data requirements rather than as part of a strictly internal processing path.

Because its stated purpose is XML generation for requisitions, the view serves as a denormalized, integration-friendly representation of requisition headers. It flattens selected header attributes, pre-computes requisition line counts, and exposes user-defined attribute columns suitable for outbound interface structures. The presence of a misspelled currency column, CURRENY_CODE, is significant: the search term "curreny_code" matches the actual column name as defined in the database, and consumers must reference the column exactly as spelled.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies the following referenced base objects: GL_SETS_OF_BOOKS (VIEW), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), ITG_X_UTILS (PACKAGE), ORG_ORGANIZATION_DEFINITIONS (VIEW), PER_PEOPLE_F (VIEW), and PO_REQUISITION_HEADERS_ALL (SYNONYM).

• PO_REQUISITION_HEADERS_ALL is the principal transactional source, supplying requisition header identifiers, approval state, description, status, preparer, and related attributes.
• GL_SETS_OF_BOOKS and ORG_ORGANIZATION_DEFINITIONS provide the ledger and organization context used to resolve operating unit and entity values exposed through the POENTITY column.
• PER_PEOPLE_F, together with the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, resolve the requester name and enforce person-level security filtering.
• ITG_X_UTILS is an ITG utility package that supports the view's XML-oriented derivations, including the header user-attribute columns.

Key Columns

The view exposes a compact set of header identifiers and descriptive attributes alongside fifteen user-attribute columns.

• REQ_HEADER_ID — primary key of the underlying requisition header.
• CREATION_DATE — creation timestamp of the header record.
• SUM_REQLINES — aggregated requisition line count for the header.
• CURRENY_CODE — currency code (VARCHAR2(15)); note the non-standard spelling that must be used verbatim in queries.
• REQUISITNID — the requisition number as displayed to users (VARCHAR2(20)).
• APPROVED and HDRSTATUS — numeric and descriptive indicators of the header approval and workflow status.
• DESCRIPTN — header description (VARCHAR2(240)).
• POENTITY — purchasing entity / operating unit reference.
• REQUESTER — the requisition preparer name.
• HEADER_UA_ATTRIBUTE1 through HEADER_UA_ATTRIBUTE15 — header-level user attributes, each VARCHAR2(150).
• TO_PO_INTERNAL, TO_MISC, TO_APPROVER, TO_BUYER, TO_PAYABLES, TO_RECEIVER, TO_SUPPLIER — flag or indicator columns driving XML routing targets.

Common Use Cases and Queries

Typical usage includes custom reporting on requisition approval status, extraction of header user attributes for downstream integration, and diagnostics of currency assignment at the header level. The following query lists requisition headers with their currency and approval state:

SELECT REQ_HEADER_ID, REQUISITNID, CURRENY_CODE, HDRSTATUS, APPROVED, REQUESTER, SUM_REQLINES FROM APPS.ITG_REQ_HEADERS_V WHERE HDRSTATUS IS NOT NULL ORDER BY CREATION_DATE DESC;

To isolate headers for a single currency, filter directly on the misspelled column: SELECT REQUISITNID, CURRENY_CODE, REQUESTER FROM APPS.ITG_REQ_HEADERS_V WHERE CURRENY_CODE = 'USD';

For integration work, a join back to PO_REQUISITION_HEADERS_ALL on REQ_HEADER_ID links the XML-facing attributes to the authoritative transactional record. Because the view enforces person security through HR_SECURITY, results are restricted to requesters visible to the connecting user, which should be accounted for when reconciling totals against unfiltered base table counts.