Search Results vst_code

Overview

ZOKL_CSE_PTY_VISITS_V is a reporting and integration view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents party visit information recorded in the Lease and Finance Management application, exposing a flattened, language-resolved projection of the underlying transactional data. The view combines base row attributes with translated descriptive text, producing a single logical row per party visit that is suitable for concurrent program output, OBIEE/BI Publisher reporting, and inbound/outbound interface extracts.

The view is particularly relevant when reporting on dealer or customer visit activity and the associated quotation values. As indicated by the presence of the QUOTE_AMOUNT column, the view captures the monetary quotation associated with a visit, making it a useful source for pipeline, opportunity, and quotation-tracking reports. The view is multi-organization aware through ORG_ID, and carries the standard EBS audit and concurrent-manager columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, and related fields).

Note that the source documentation records this object as "Not implemented in this database" for the referenced environment, meaning the object definition exists in the ETRM data dictionary but the physical view is not present in the queried schema. Validation against a specific instance is therefore advised before use.

Underlying Base Objects

Although the ETRM metadata does not enumerate the referenced base objects in a structured list, the view text provides the authoritative definition. The view is defined over two base tables joined on the visit identifier:

• ZOKL_CSE_PTY_VISITS_B — the base table (alias CPEB) holding the primary transactional columns: identifiers, quote amount and date, status, flexfield attributes, and the standard WHO/audit columns.
• ZOKL_CSE_PTY_VISITS_TL — the translation table (alias CPET) supplying language-dependent descriptive text.

The join condition is CPEB.ID = CPET.ID, filtered by CPET.LANGUAGE = USERENV('LANG'). This pattern is the standard EBS translated-table model: the _B table stores language-independent data, while the _TL table stores translated descriptions. The USERENV('LANG') predicate restricts the result to the session's current language, so a single row is returned per visit rather than one row per installed language. Because the filter depends on session language, report output for descriptive columns such as QUOTE_DESCRIPTION will vary by the language setting of the executing user or concurrent request.

Key Columns

The view exposes the following significant columns:

• ROW_ID — the ROWID of the base _B record, useful for identifying the physical row.
• ID — the primary visit identifier, shared by both base and translation tables.
• OBJECT_VERSION_NUMBER — optimistic locking version, used by OAF-based update flows.
• QUOTE_AMOUNT — the monetary value quoted for the visit; central to quotation and pipeline reporting and the column referenced in the originating search.
• QUOTE_DATE and QUOTE_DESCRIPTION — the date of the quote and its translated narrative text.
• SEQUENCE_NUMBER — ordering value for the visit or its associated quote lines.
• CAC_ID — foreign key to the related party/customer account context.
• VISIT_STATUS — the workflow or lifecycle state of the visit.
• SFWT_FLAG, SNM_CODE, VST_CODE, VST_ID — status, method, and visit-type reference information.
• NOTE_SUBMISSION_METHOD — the channel by which the visit note was submitted.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns available for customer-specific extensions.
• ORG_ID — operating unit, supporting Multi-Org access control (MOAC).
• Audit and concurrency columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include quotation pipeline reports grouped by quote date, visit status monitoring, and integration extracts feeding downstream CRM or analytics platforms. A representative query totals quotation values by organization and status:

• SELECT org_id, visit_status, SUM(quote_amount) total_value, COUNT(*) visit_count FROM zokl_cse_pty_visits_v GROUP BY org_id, visit_status;
• SELECT id, cac_id, quote_amount, quote_date, quote_description FROM zokl_cse_pty_visits_v WHERE quote_date >= :p_from_date AND org_id = :p_org_id ORDER BY quote_date DESC;
• SELECT id, vst_code, snm_code, note_submission_method, attribute1, attribute2 FROM zokl_cse_pty_visits_v WHERE visit_status = 'APPROVED';

Because the view is documented as not implemented in the source database, deployments should confirm its presence via ALL_VIEWS prior to reliance, and join to CAC/party tables for customer names as required.