Item is marked as not being configuration part
[be marked with] [BOM] [configuration] [CONFIG_DATA] [Engine] [explosion] [IPC] [IS_CONFIG_PART] [items] [marked] [marked for death] [marked up] [multilevel] [part] [SPC_CHANGE_ITEMS] [SPC_CREATE_ITEMS] [sub-item]
Related:
- Performance improvement for the configuration creationSymptom Configurations are created for configurable items in a sales...
- All Offsetting accounts should be displayed in GL reportSymptom All GL offsetting account or counter account should be...
Symptom
Sales document items that are inferred by a multilevel configuration are marked as created by configuration. When a sales document is loaded in CRM, all items are created. Thus the items that were derived by configuration have to be marked accordingly. A new flag within function modules SPC_CREATE_ITEMS and SPC_CHANGE_ITEMS was introduced, that can be filled with ‘T’ if the item is to be marked as inferred by configuration.
If the item is neither marked as ‘T’ nor ‘F’ the item’s falg is set to false nevertheless. This causes a lot of follow up problems:
the item instantiates an own configuration if configurable,the item cannot be deleted afterwards if the BOM explosion is done anew,pricing keys are removed from the item.
There are other possible follow up problems that may be caused by this.
Other terms
IPC, Configuration Engine, Items, SPC_CREATE_ITEMS, SPC_CHANGE_ITEMS, IS_CONFIG_PART, CONFIG_DATA, sub-item, configuration part, BOM explosion, multilevel configuration
Reason and Prerequisites
Reason for the error is, that the new parameter is used but not filled, becasue the follow up notes from the order were not implemented.
The second reason for the error is, that if the newly introduced flag is not filled with ‘T’ or ‘F’ at all, it is internally interpreted as ‘F’.
Solution
The interpretation of the flag as ‘F’ is removed. In the case that nothing is specified, the setting on item level simply stays as it is. This code correction will be available for SP10 to SP17 as a patch that can be downloaded and implemented from SAP Service Marketplace. From SP18 the correction is contained in the standard.