Results for “xml_tmplt_code”

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

Overview

OKL_PROCESS_TMPLTS_ALL_B is a Lease and Finance Management (OKL) transactional table that functions as an intersection, or cross-reference, entity between two unrelated master data sources: JTF_AMV_ITEMS_B, which stores Fulfillment Master Documents, and FND_LOOKUPS, which supplies the OKL Process codes. In practical terms, the table records which fulfillment document template is associated with a given lease or finance process, for a defined recipient type, within a defined operating unit, and over a defined effective-date range. This makes it the configuration bridge that connects document generation infrastructure (Oracle Marketing/AMV fulfillment) to the lease management business flow.

The ETRM metadata classifies OKL_PROCESS_TMPLTS_ALL_B heuristically as satellite-leaning under a Data Vault modeling lens. This classification is a suggestion rather than a functional property: the table carries descriptive and reference attributes (template code, recipient type, effective dates) that are dependent on a defined business key, while its relationship to JTF_AMV_ITEMS_B is treated as a foreign-key reference rather than a true hub. Modelers implementing a Data Vault layer on top of EBS should treat the business unique key as the natural key of the satellite and JTF_AMV_ITEM_ID as a link to the fulfillment document hub.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

• ID — surrogate primary key (OKL_PROCESS_TMPLTS_ALL_B_PK); system-generated, carries no business meaning.
• PTM_CODE — the OKL Process code, sourced conceptually from FND_LOOKUPS; identifies the lease/finance process the template belongs to.
• JTF_AMV_ITEM_ID — foreign key to JTF_AMV_ITEMS_B; identifies the fulfillment master document (template) used for the process.
• XML_TMPLT_CODE — the XML template code driving document rendering.
• RECIPIENT_TYPE_CODE — the recipient category the template applies to (for example customer, dealer, or internal party).
• START_DATE / END_DATE — effective-dating window controlling when an association is active.
• ORG_ID — operating unit, enforcing multi-org partitioning of the configuration.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit lineage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension block, allowing client-specific configuration without schema change.

Two unique indexes are documented. OKL_PROCESS_TMPLTS_ALL_B_U1 covers ID alone (the surrogate key). OKL_PROCESS_TMPLTS_ALL_B_U2 covers PTM_CODE, XML_TMPLT_CODE, RECIPIENT_TYPE_CODE, START_DATE, ORG_ID, JTF_AMV_ITEM_ID together and is the true business-key candidate: no two rows may share the same process, template, recipient, effective start, operating unit, and fulfillment document combination.

Common Use Cases and Queries

Typical uses include resolving which document template a lease process should invoke, auditing template assignments after a configuration migration, and diagnosing missing or expired template mappings that cause document generation failures.

A representative lookup for active templates for a process and operating unit:

• SELECT ptm.XML_TMPLT_CODE, ptm.RECIPIENT_TYPE_CODE, ptm.JTF_AMV_ITEM_ID
• FROM OKL_PROCESS_TMPLTS_ALL_B ptm
• WHERE ptm.PTM_CODE = :ptm_code
• AND ptm.ORG_ID = :org_id
• AND TRUNC(SYSDATE) BETWEEN ptm.START_DATE AND NVL(ptm.END_DATE, SYSDATE);

Joining back to the fulfillment document master validates that the referenced template still exists:

• SELECT i.ITEM_NAME, ptm.PTM_CODE, ptm.START_DATE, ptm.END_DATE
• FROM OKL_PROCESS_TMPLTS_ALL_B ptm, JTF_AMV_ITEMS_B i
• WHERE ptm.JTF_AMV_ITEM_ID = i.AMV_ITEM_ID;

Reporting scenarios commonly group by PTM_CODE and RECIPIENT_TYPE_CODE to inventory template coverage per process, or filter on END_DATE to find expired assignments that should be retired.

Related Objects

• JTF_AMV_ITEMS_B — the fulfillment master document table; joined on JTF_AMV_ITEM_ID. This is the only foreign key documented and the primary dependency.
• FND_LOOKUPS — supplies OKL Process codes conceptually used in PTM_CODE; join on LOOKUP_CODE with LOOKUP_TYPE identifying the OKL process lookup, typically in reporting only.
• FND_LOOKUP_VALUES — the language-sensitive view over FND_LOOKUPS; used to retrieve process descriptions alongside PTM_CODE in inquiries.
• JTF_AMV_ITEM_VL / JTF_AMV_ITEMS_TL — translated and view layers of the fulfillment item master, commonly joined for item names in reports.
• OKL_PROCESS_TMPLTS_ALL_TL — where present, the translated counterpart providing language-dependent template text.
• OKL lease/fulfillment APIs — the OKL process execution code that reads this table at runtime to select the correct template for a lease transaction.
• FND_ATTACHED_DOCUMENTS / FND_DOCUMENTS — indirectly related via the fulfillment framework when the selected template produces an output document.

The table carries no foreign key to OKL transaction tables directly; its reach is through the process code and fulfillment item, which is why accurate maintenance of PTM_CODE and JTF_AMV_ITEM_ID is critical.