Search Results validate_category_id

Overview

AS_SALES_LEAD_LINES_PVT is a private PL/SQL package in the APPS schema that implements the line-level business logic for the Oracle EBS Sales Leads (Oracle TeleSales / Sales Foundation) module. It is the internal engine that the public API AS_SALES_LEADS_PUB calls to create, modify, and remove individual lead lines associated with a sales lead header. Lead lines capture the specific products or interest areas that a prospect has expressed interest in, together with quantities, units of measure, inventory organizations, and budget information. By segregating this logic into a PVT (private) package, Oracle enforces the API boundary: direct table manipulation is discouraged, and all validated, multi-org-aware processing flows through the published interface. The package is classified as VALID in both 12.1.1 and 12.2.2 and carries 14 documented procedures and functions.

Key Procedures and Functions

The documented callable units divide naturally into low-level validation helpers and the three DML drivers.

• VALIDATE_INTEREST_TYPE_ID — confirms the supplied interest type is a valid, active value in the interest type reference data.
• VALIDATE_PRIM_INT_CODE_ID / VALIDATE_SEC_INT_CODE_ID — verify the primary and secondary interest codes supplied for the lead line.
• VALIDATE_INTRST_TYPE_SEC_CODE — checks consistency between the interest type and the secondary interest code.
• VALIDATE_INV_ORG_ID — ensures the inventory organization is valid and accessible in the current operating unit context.
• VALIDATE_UOM_CODE / VALIDATE_INVENT_INTRST — confirm the unit of measure and that the inventory interest combination is meaningful.
• VALIDATE_CATEGORY_ID / VALIDATE_CATEGORY_SET_ID — validate item category and its category set against the item master.
• VALIDATE_BUDGET_AMOUNTS — checks budget-related amounts carried on the lead line.
• VALIDATE_SALES_LEAD_LINE — the umbrella routine that invokes the individual validators to fully qualify a lead line record.
• CREATE_SALES_LEAD_LINES / UPDATE_SALES_LEAD_LINES / DELETE_SALES_LEAD_LINES — the transactional drivers that insert, amend, and remove rows in the lead lines table after validation succeeds.

Tables Accessed

The package reads reference and master data and writes the lead line transaction table.

• AS_SALES_LEADS — header record that owns each line; read to confirm the lead exists and to inherit attributes.
• AS_SALES_LEAD_LINES — the primary target of the create, update, and delete procedures.
• AS_INTEREST_TYPES_B and AS_INTEREST_CODES_B — reference tables used by the interest type and interest code validators.
• MTL_SYSTEM_ITEMS, MTL_ITEM_CATEGORIES, MTL_UNITS_OF_MEASURE — item, category, and UOM validation.
• PLITBLM — the standard multi-lingual / multi-org security table used for organization access checks.

Usage Notes

AS_SALES_LEAD_LINES_PVT is never invoked directly by end users or custom integrations. Oracle's supported entry point is AS_SALES_LEADS_PUB, which delegates line processing here; the TeleSales and Sales Foundation forms likewise call the public API. The dependency metadata shows the package references AS_SALES_LEADS_PUB, AS_UTILITY_PUB, and FND_API, and is itself referenced by AS_SALES_LEADS_PUB, AS_SALES_LEADS_PVT, and recursively by AS_SALES_LEAD_LINES_PVT. Because it is private and unsupported for direct calls, any modification risks breaking the public API contract. Custom code should use AS_SALES_LEADS_PUB, respecting FND_API conventions for initialization, error handling, and commit control.