Last updated on DECEMBER 07, 2016
Applies to:Oracle Configure to Order - Version 12.1.3 and later
Information in this document applies to any platform.
When the configured item is created, expect that the component 'item sequence' of the configured item is in the same order as it was in the Model Bill structure.
The behavior of 'item sequence' of configured item is inconsistent.
Use the configured item, item sequence to be used for ordering of values from Descriptive element, while building the Configured item description.
For example: Model Mx has Option Class - OCy, and OCy has Components C1, C2 ... Cn. The OCy is non-mutually exclusive OC, where the item sequence of C1 ... Cn is 10, 20, 30 .... uniform increment of 10.
When Config-item for Model Mx is created, say CITz - and it contains m selections from OCy, the expected 'item sequence' of selected components (say C2, C3, C5 and C7) can be anything, but in order it was in Model-OC bill structure.
The component's item sequence is random, say for a sample it could be C5, C7, C3, and C2.
Due to the unpredictable nature of item sequence, the descriptive element want to use from the selected component does not help generate uniform item description.
Why doesn't the component's 'item sequence' of configured item honor the order as in the Model Bill structure?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms