Search Results validate_decision_factor




Overview
Explore in AI Chat

Overview

AS_DECISION_FACTOR_PVT is a private PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Sales / TeleSales Foundation (AS) module. Its purpose is to encapsulate the internal business logic required to create, modify, delete, and validate decision factors for sales leads. In Oracle EBS, a decision factor represents a qualifier or criterion used during lead qualification and opportunity assessment, allowing sales organizations to score and prioritise leads according to predefined business rules. The package is classified as a "PVT" (private) API, meaning it is not intended for direct external invocation but rather serves as the internal implementation layer of the public decision factor API. The private layer isolates the heavy validation and DML processing so that the corresponding public package (AS_OPPORTUNITY_PUB) can expose a stable, versioned interface while delegating the detailed work to this body. The source file is identified as asxvdfcb.pls, and the header comment reflects a source version dated 2005, consistent with the code lineage carried forward through EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twelve documented procedures and functions organized around three functional areas: DML operations, field-level validation, and record-level validation.

  • CREATE_DECISION_FACTORS — Creates one or more decision factor records. It receives API version information, initialization flags, validation level, access and administrative flags, identity and party identifiers, profile information, and a decision factor table. It returns the created records, return status, message count, and message data.
  • UPDATE_DECISION_FACTORS — Updates existing decision factor records using the same API pattern and error handling conventions.
  • DELETE_DECISION_FACTORS — Removes decision factor records, applying the standard API return status and message list.
  • VALIDATE_REQUEST_ID — Confirms that a supplied request identifier is valid before processing continues.
  • VALIDATE_DECISION_RANK — Validates the rank or ordering value assigned to a decision factor.
  • VALIDATE_DECISION_PRIOR_CODE — Verifies the decision priority code against its lookup definition.
  • VALIDATE_DECISION_FACTOR_CODE — Checks that the decision factor code is properly defined and unique where required.
  • VALIDATE_L_DECISION_FACTOR_ID — Validates the internal decision factor identifier used by the local layer.
  • VALIDATE_LEAD_LINE_ID — Ensures the associated lead line identifier exists and is accessible, using a cursor over AS_LEAD_LINES_ALL to resolve the parent lead.
  • VALIDATE_CREATE_BY — Validates the creator identity against the identity or salesforce context.
  • VALIDATE_DECISION_FACTOR_REC — Performs record-level validation across all fields of a single decision factor record.
  • VALIDATE_DECISION_FACTOR — The top-level validation routine that orchestrates the individual field-level validations for a decision factor, corresponding to the user's search term "validate_decision_factor".

Tables Accessed

The package references three tables through APPS synonyms:

  • AS_LEAD_DECISION_FACTORS — The primary transactional table holding decision factor records for leads. It is the target of the create, update, and delete operations.
  • AS_LEAD_LINES_ALL — The lead line table, queried via a cursor to resolve the parent lead identifier from a given lead line identifier. This supports validation of the lead context in which a decision factor is being created.
  • PLITBLM — A standard EBS message handling table used by the FND message dictionary infrastructure to retrieve and translate error and warning messages returned through the API message list.

Usage Notes

Because this package is classified as private (PVT), it is not designed to be called directly from forms, concurrent programs, or customer-written code. Instead, it is invoked by its companion public API, which is in turn referenced by the Oracle Sales Foundation forms and business flows that manage lead qualification. The package is also referenced by one other package within the AS module, confirming its role as a shared internal utility. Customizations or extensions that need to manipulate decision factors should always go through the public API to preserve validation rules, access control, and the standard FND message list contract. Developers inspecting this body in 12.1.1 or 12.2.2 should note that the internal signatures and cursor logic are subject to change between releases and must not be relied upon as a stable interface.