Search Results jtf_amv_items_b

Overview

The table OKL_PROCESS_TMPLTS_ALL_B is a core intersection entity within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its primary function is to establish and manage the relationship between fulfillment master documents and specific leasing processes. It serves as a mapping table, linking document templates stored in the JTF_AMV_ITEMS_B table with process codes defined as lookups in the FND_LOOKUPS table. This relationship is fundamental for automating and controlling document generation workflows, such as creating invoices, notices, or agreements, based on defined business processes within the leasing lifecycle. The table supports multi-organization architecture, as indicated by the ALL_B suffix and the ORG_ID column.

Key Information Stored

The table's structure is designed to enforce unique mappings and track validity. Key columns include the surrogate primary key ID and a composite unique key that defines the relationship's business rules. The critical foreign key JTF_AMV_ITEM_ID links to a specific document template in JTF_AMV_ITEMS_B. The process code, likely stored in a column such as PTM_CODE, references a value in FND_LOOKUPS where the lookup type is an OKL Process code. Additional columns provide context for the mapping: XML_TMPLT_CODE may specify a sub-template or format, RECIPIENT_TYPE_CODE defines the intended recipient (e.g., lessor, lessee), and START_DATE (often paired with an implied END_DATE) manages the effective period of the template-process association. The ORG_ID column partitions the data by operating unit.

Common Use Cases and Queries

This table is central to queries that determine which document template to use for a given business process. A common use case is during the execution of a lease process, such as billing or termination, where the application queries this table to find the active document template configured for that process, recipient, and organization. A typical SQL pattern would join to JTF_AMV_ITEMS_B to retrieve the template details and to FND_LOOKUPS to resolve the process code meaning.

• Finding Active Templates for a Process: SELECT amv.item_id, amv.item_title, pt.* FROM OKL_PROCESS_TMPLTS_ALL_B pt, JTF_AMV_ITEMS_B amv, FND_LOOKUPS_VL l WHERE pt.JTF_AMV_ITEM_ID = amv.ITEM_ID AND pt.PTM_CODE = l.LOOKUP_CODE AND l.LOOKUP_TYPE = 'OKL_PROCESS_CODE' AND pt.ORG_ID = :org_id AND SYSDATE BETWEEN pt.START_DATE AND NVL(pt.END_DATE, SYSDATE+1);
• Reporting on Process-Template Mappings: Reports can be built to audit all configured document generation rules across processes and operating units, ensuring correct templates are assigned.

Related Objects

The table has direct dependencies on two primary EBS foundation objects. The foreign key to JTF_AMV_ITEMS_B provides access to the fulfillment master document metadata, such as the template file and descriptive information. The relationship to FND_LOOKUPS, enforced via the process code column, provides the valid list of OKL process codes (e.g., 'LEASE_BILLING', 'ASSET_RETURN'). This table is also referenced by the OKL_PROCESS_TMPLTS_ALL_B_PK and UK1 constraints. In application logic, it is likely accessed through OKL-specific PL/SQL APIs or views that abstract the direct table access for template retrieval during process execution.