Results for “okl_process_tmplts_v”

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

Overview

OKL_PROCESS_TMPLTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Leasing and Finance Management) product family. Its documented purpose is to act as an intersection between JTF_AMV_ITEMS_B, which stores Fulfillment Master Documents, and FND_LOOKUPS, which stores OKL Process codes. The view therefore surfaces the mapping between an OKL business process template and the fulfillment document that supports it, so that notification, correspondence, and fulfillment generation logic in Lease and Finance Management can resolve the correct master document for a given process code.

Because the view is defined as a join between a base (non-translated) table and a translation table filtered by the session language, it presents a single-language, user-facing projection of process template data. This makes it suitable for direct use in reports, concurrent program data sources, and integration extracts without requiring callers to manage language joins themselves.

Underlying Base Objects

The documented view text is defined over two synonyms: OKL_PROCESS_TMPLTS_ALL_B, the base table holding language-independent template attributes, and OKL_PROCESS_TMPLTS_TL, the translation table holding language-dependent attributes such as the email subject line and the "send for workflow task" (SFWT) flag. The join is on ID, with the additional predicate that PTMT.LANGUAGE equals USERENV('LANG'), restricting rows to the current session language.

• OKL_PROCESS_TMPLTS_ALL_B — source of the majority of the view columns, including ID, ORG_ID, PTM_CODE, JTF_AMV_ITEM_ID, XML_TMPLT_CODE, RECIPIENT_TYPE_CODE, the date ranges, the descriptive flexfield attributes, and the standard WHO audit columns.
• OKL_PROCESS_TMPLTS_TL — contributes the translated columns SFWT_FLAG and EMAIL_SUBJECT_LINE.
• JTF_AMV_ITEMS_B — indirectly referenced through the stored JTF_AMV_ITEM_ID value, which links the template to its Fulfillment Master Document.
• FND_LOOKUPS — indirectly referenced through PTM_CODE and RECIPIENT_TYPE_CODE, which are validated against lookup types maintained in the FND_LOOKUPS table.

Key Columns

• ID — primary identifier of the process template; the join key between the base and translation tables.
• PTM_CODE — the OKL process code that identifies which business process the template applies to.
• JTF_AMV_ITEM_ID — foreign key to the Fulfillment Master Document in JTF_AMV_ITEMS_B that the process template uses.
• XML_TMPLT_CODE — the XML template code driving document generation for the process.
• RECIPIENT_TYPE_CODE — indicates the intended recipient category for the generated correspondence.
• EMAIL_SUBJECT_LINE — translated subject line used when the template produces an email.
• SFWT_FLAG — indicates whether the fulfillment is sent for workflow task processing.
• ORG_ID — operating unit context, supporting multi-org security in queries.
• START_DATE / END_DATE — effective date range controlling when the template is active.
• ROW_ID, OBJECT_VERSION_NUMBER, ATTRIBUTE_CATEGORY, ATTRIBUTE1–15, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard row identity, optimistic locking, descriptive flexfield, and audit columns.

Common Use Cases and Queries

Typical uses include resolving which fulfillment document and XML template are configured for a process code, auditing template coverage across operating units, and extracting active templates for correspondence configuration reviews.

• Inventory templates by process: SELECT ptm_code, jtf_amv_item_id, xml_tmplt_code FROM okl_process_tmplts_v ORDER BY ptm_code;
• Active templates for an operating unit: SELECT ptm_code, email_subject_line FROM okl_process_tmplts_v WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
• Workflow-enabled templates: SELECT ptm_code, jtf_amv_item_id FROM okl_process_tmplts_v WHERE sfwt_flag = 'Y';
• Joining to the master document: link on jtf_amv_item_id = jtf_amv_items_b.jtf_amv_item_id to retrieve document names alongside process codes.
• Looking up valid process codes: join PTM_CODE to FND_LOOKUPS with the appropriate lookup type to validate configuration completeness.

Because the view depends on USERENV('LANG'), queries executed under different language sessions may return different SFWT_FLAG and EMAIL_SUBJECT_LINE values; report authors should set the runtime language explicitly when consistency across environments is required.