Results for “ame_transaction_type”

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

Overview

The PO_DOCUMENT_TYPES_V view is a Purchasing (PO) module database object owned by the APPS schema in Oracle E-Business Suite. It exposes the configuration of the document types supported by the purchasing and sourcing workflow — requisitions, RFQs, quotations, and purchase orders — enriching the code-level configuration stored in the base table with human-readable lookup descriptions and default approval-path names. The metadata records the view as "VALID" with the description "- Retrofitted," indicating it was carried forward into the 12.1.1 / 12.2.2 code line, with the 12.2.2 documentation listing its referenced base objects as FND_GLOBAL (package), PER_POSITION_STRUCTURES (synonym), PO_DOCUMENT_TYPES (synonym), and PO_LOOKUP_CODES (view).

Because it decodes the internal lookup codes into displayed field values, the view serves as the standard reporting and integration surface for document-type setup: any custom report, concurrent program, or interface that needs the effective document type behavior, security level, approval path, and workflow item type can read this view rather than joining the raw lookup table itself.

Underlying Base Objects

The view is defined over the following documented objects:

• PO_DOCUMENT_TYPES (synonym to PO.PO_DOCUMENT_TYPES) — the driving table, aliased DT, supplying every configuration attribute plus the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and so on).
• PO_LOOKUP_CODES (view over the lookup tables) — aliased seven times (LC1 through LC7) to resolve lookup codes into DISPLAYED_FIELD values for the document type, subtype, security level, quotation class, archive external revision code, access level, and forwarding mode. Lookups include DOCUMENT TYPE, REQUISITION TYPE, RFQ SUBTYPE, QUOTATION SUBTYPE, and a general DOCUMENT SUBTYPE type selected by a DECODE on the document type code.
• PER_POSITION_STRUCTURES (synonym) — aliased PPS, joined on DEFAULT_APPROVAL_PATH_ID to return the approval-path name.
• FND_GLOBAL (package) — referenced for session context such as ORG_ID, consistent with a multi-org security predicate.

Note that several lookup joins (for example LC3) are outer joins ((+)), so rows are retained even where a lookup description is missing.

Key Columns

• ROW_ID, DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE — the identifying codes for each configured document type.
• TYPE_NAME, DISABLED_FLAG — the user-facing name and enablement status.
• DISPLAYED_FIELD — the decoded description returned for each associated lookup code.
• SECURITY_LEVEL_CODE, ACCESS_LEVEL_CODE — security and access designations.
• DEFAULT_APPROVAL_PATH_ID and PPS.NAME — the default approval path and its descriptive name.
• CAN_PREPARER_APPROVE_FLAG, CAN_APPROVER_MODIFY_DOC_FLAG, and the related CAN_CHANGE_* flags — behavior controls for the approval process.
• WF_APPROVAL_ITEMTYPE, WF_APPROVAL_PROCESS, WF_CREATEDOC_ITEMTYPE, WF_CREATEDOC_PROCESS — Oracle Workflow item types and processes used in document approval and creation.
• AME_TRANSACTION_TYPE — the Approvals Management Engine transaction type.
• DOCUMENT_TEMPLATE_CODE, CONTRACT_TEMPLATE_CODE, USE_CONTRACT_FOR_SOURCING_FLAG, INCLUDE_NONCATALOG_FLAG — template and sourcing behaviors.
• ORG_ID — the operating unit context of the configuration row.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include auditing document-type setup, driving approval configuration reports, and feeding interfaces that must replicate purchasing behavior. A query listing the named approval paths per document type might read:

• SELECT document_type_code, type_name, displayed_field, name FROM po_document_types_v WHERE disabled_flag = 'N' ORDER BY document_type_code;
• Reviewing workflow bindings: SELECT document_type_code, wf_approval_itemtype, wf_approval_process, ame_transaction_type FROM po_document_types_v;
• Filtering by operating unit: SELECT * FROM po_document_types_v WHERE org_id = :p_org_id;

Because lookup joins are outer, reports should anticipate null DISPLAYED_FIELD values where a lookup has not been seeded.