Update characteristics configuration using BAPI_CUSTOMERQUOTATION_CHANGE

[amarjit_yanglem]

Hi Experts,

I have a program which uploads excel and updates Sales Quotatoin Items and its characteristics through the BAPI - BAPI_CUSTOMERQUOTATION_CHANGE. The process is mostly Quotation Item Insertion, deletion and updation of its characteristics.

During updation of its characteristics, most of the configurations value can be updated, whose values are stored as characters data type. Whereas characteristics like eg. Height, Width, Depth, Price, etc are unable to update.

Here, WA_INPUT is the line read from the internal table of excel upload, where we have around 10 columns for characteristics values.

Here particular characteristics like Height, Width, etc values are not getting updated, which maybe because their values are stored as floating points and I am passing it as character.

Please help how or where I can pass the value for it to update.

PF BAPI.

[Raghavendran_Mohandoss]

Did you solve this yet?

Few suggestions and possibly one of them may be the answer to your question,

First thing I noticed was the CONFIG_ID field being filled with ITEM_NO which is wrong. Config ID values different and its internally generated with the increment of 1 starting from 000001 for each line item. So, first read the existing configuration using read BAPI and try to find the relevant CONFIG_ID for the given line item using CFGS_REF structure, then use that CONFIG_ID to update specific characteristic.

Next, VC values are always stored in character format with the length of 40 characters. You can cross check this in the BAPI structures BAPICUVAL, where the VALUE field has CHAR 40. So, floating point conversion doesn't seem to be relevant here.

Also, I see you have filled "VKEY" field for "QUOTATION_CFGS_VK" table. What is the reason behind this? Because VKEY is only used create dependencies between characteristic values and the price of the configurable product. If you are only trying to update the VC characteristic "HM_HEIGHT", this VKEY field does not have to be filled. Does this field update also has pricing dependency?

In the BAPI call, you have uncommented many configuration related structures, but are you filling and using all of them? if not I would suggest to comment unnecessary structures and only enable the QUOTATION_CFGS_VALUE since that is the one you need to update the VC value.

After the BAPI call, any messages on the RETURN structure. If so, post that here to see what it returned. Hope you have added BAPI_TRANSACTION_COMMIT after the BAPI call based on LT_RETURN, if not do add it. 

For more in depth analysis, before running the report, turn on the VC configuration trace using T-Code "CUTRC" and once the report is completed, turn the trace off and see the results. It will capture all the update happened to VC during that time. And it might show whether the characteristic value was accepted by VC or if there is any error.