Inconsistency/Incomplete Error in mass upload of Configuration

Question

Hi All,
I will need your expert help on the issue I am facing in my project.
We have sales order items having more than 300 characteristics. So we have a small program which takes the sales order number, item number, characteristic name, and value from an xls sheet and update the configuration in sales order.
We also have lot of constraints, procedures, etc... in the profile of this item, due to which we dont get the configuration as Green always. In many cases, we get inconsistency or incompletion in the configuration.
However we are not able to read these reasons in the program. Reasons for inconsistency or incompletion are not feasible to read by the program as these are mostly coming from interpretation of rules by the VC engine.
Do we have a method for handling the following scenarios.
1. Even if configuration is incomplete or inconsistent, I want to update the VC values as provided in the xls sheet in the sales order and lock the configuration and save sales order.
2. After saving sales order, I want the program to get the reasons for inconsistency (the inconsistency messages we see in the sales order) and present them at the end.
I will be grateful for any useful thoughts (programs used, technical inputs, alternative methods) on this.

Answer 1

Navaneetha Krishnan,
The problem i see here is standard behaviour of not accepting incosistant data in configuration is obstacle. Which is preaty logical, ex, user want to assign a characterstic value which doesnt exist or which is not valid due to selection of another value for another characterstic. There can be many other reasons and examples.
My suggestion is break down your program 2 part , creation & error handling.
During creation read and record all the data in excel sheet into a internal table
process data line by line
for every sucess message delete the processed line
for every error record , copy the data in Z table which can be used later by error handling part
record error or inconsitance message generated in 2nd Z table
once trnsaction reaches last data line , show list of sales order created and a option to review inconsitance messages generated.
Run error handling trnsaction which looks into 2nd Z table and display list of inconsistnaces generated.
correct the error manualy and reprocess the data saved in 1st Z table
In VA01 or VA02 if there is inconsistance you can proceed furthe r, but check with your programer while using BAPI is it possible to save incomplete configuration , if he/she find a way , you can save this incomplete sales orderline item  number  in 1st Z table , which can later useful while error processing.
Its just a abbrupt thought , which hope can be useful for you while creating FS.
Thanks
Ritesh