Search Results get_attribute_control

Overview

APPS.CTO_UPDATE_ITEMS_PK is a Configure-to-Order (CTO) technical package body in Oracle E-Business Suite that supports the transformation and maintenance of configured items after a model configuration has been matched or upgraded. Its principal business role is to propagate attribute, sourcing, cost, and cross-reference data from a model (or a matched configuration) to the resulting configuration item, thereby keeping item masters, bills of material, sourcing rules, and cost records consistent across the enterprise. The package header carries a source version identifier indicating an R12 baseline ("120.6.12000000.2"), and the header comments show a history of defect fixes spanning 2003 through 2005 that touched matched-config upgrades, revision population, cost organization validation, and the R12 cross-reference data model split.

Key Procedures and Functions

Eight documented procedures and functions make up the public surface of the package body:

• UPDATE_ITEMS_AND_SOURCING — the primary driver routine; it coordinates the updates to configured items and their associated sourcing definitions.
• UPDATE_BCSO — updates buyer/company/sourcing organization data (BCSO) for items, consistent with the historical fix that ensured matched configurations were correctly transformed to BCMO records.
• UPDATE_ACC_ITEMS — handles updates to accumulate (ACC) items, propagating model-derived attributes to accumulated configuration items.
• GET_ATTRIBUTE_CONTROL — the function most commonly searched for; it returns the attribute control setting used to determine whether a given item attribute should be copied or controlled during the CTO update process.
• GET_COST_GROUP — retrieves the cost group applicable to the item being processed, used when inserting or validating cost records.
• UPDATE_ITEM_DATA — performs the attribute-level updates on the item master, including revision and revision-label population.
• UPDATE_PC_ITEMS — updates purchased-configuration or pricing-related (PC) items in line with model sourcing.
• WRITETOLOG — a diagnostic utility that writes trace messages so the transformation progress and errors can be reviewed.

Tables Accessed

The package reads and writes a defined set of CTO, BOM, cost, and item tables through APPS synonyms. BOM_CTO_MODEL_ORGS, BOM_CTO_ORDER_LINES_UPG, and BOM_CTO_SRC_ORGS_B hold the model organization, upgrade order line, and sourcing organization data that drive the update rules. Cost processing touches CST_COST_TYPES, CST_ITEM_COSTS, CST_ITEM_COST_DETAILS, and CST_QUANTITY_LAYERS, where cost groups and validation-organization costs are validated and copied to configuration items. Item master and categorization data are accessed through MTL_CROSS_REFERENCES and its R12 companions MTL_CROSS_REFERENCES_B, MTL_CROSS_REFERENCES_B_S, and MTL_CROSS_REFERENCES_TL, reflecting the R12 split of the cross-reference model. MTL_CATEGORY_SETS_B and MTL_DEFAULT_CATEGORY_SETS support category set assignment, while FND_ATTACHED_DOCUMENTS and FND_LANGUAGES provide attachment and language context.

Usage Notes

CTO_UPDATE_ITEMS_PK is invoked during CTO configuration processing rather than by end users directly. It is typically called from CTO concurrent programs and from other CTO packages; the ETRM metadata records it as referenced by one other package. The GET_ATTRIBUTE_CONTROL function is of particular interest to developers who need to determine, at runtime, whether an attribute is under CTO control before writing custom extensions. Because the package performs direct DML against cost and cross-reference tables, custom code should invoke the documented procedures instead of reimplementing that logic, and any extension points should respect the existing revision and cost-organization validation behavior established by the historical bug fixes documented in the package header.