we want to collect all pricing conditions for a sales order into BW.
In 2lis_11_vaitm only the subtotals are included, how can I collect all the condition fields?
Are there any standard extractors or do I have to build a generic one?
Thank you,
Simon
Answer:
Hi,
As we see pricing conditions are stored in cluster table so I think it will be hard to take, if possible create generic one as long as i know theres no direct approach.
if you find one pls let me know.
thanks
Rav
we want to collect all pricing conditions for a sales order into BW.
In 2lis_11_vaitm only the subtotals are included, how can I collect all the condition fields?
Are there any standard extractors or do I have to build a generic one?
Thank you,
Simon
Answer:
check out note 387625
Although SAP advises you not to, we have implemented solution 2 (read condition tables during extraction to BW and append the fileds for DS 2LIS_11_VAITM (or SCL). It's not very performant, but we can live with that. However, it takes quite some time to develop/test so think about it carefully !
Good luck
T.
Answer:
Hallo,
I have the same question as Simon, and I do not know what is the best to do.
I had a look at the note 387625.
One question, why didn't you use the workaround proposed in the SaP note ? Can you suggest me the better solution?
The solution 2 you used is ok?
We have to transfer different prices condition in BW, and after that we do have to use those prices for calculation in BEX reporting....
Thanks
Sara
Answer:
A couple of points why we chose for solution 2:
- - this way you don't interfere directly in the SD-user exit ... problems with coding via solution 2 will only cause your loads to fail, while via solution 1, your whole sales-order-saving process could dump..
- only way to get your pricing conditions over for "historical" data (if you do it in the SD exit, you can off course only do this for nwew orders, not for already existing ones)
- similar to point 1 : safety reasons ! The R3 guys rarther keep us out of "their" user exit
- and very important : some fields are not always yet filled in in related R3 tables when the SD-user exit is processed. The vbap/vbak/konv fields are all available but some others (like for example the VBPA i think) are not. Not very relevant for the pricing conditions extraction, but something to keep in mind for adding other fields in the code like partner functions
I probably oversaw some points, someone has anything to add?
T.
Answer:
A client of mine has been using pricing conditions read direct from table KONV without problem. The coding must be in the RSAP001 exit as pricing conditions are not available at the time the MCS1001 (sales documents) and MCS60001 (invoicing) exits are run. The volumes are relatively small (600,000 init load) a few thousand per day delta. We are picking up 35 different pricing conditions, so the subtotal method would not have been appropriate.
Ken PJ
Answer:
Hallo,
at the moment I'm using the solution proposed in the note 387625 ( using fileds KZWIx and not theuser exit ) and it works.
And because we have only a few prices condition the subtotal method seems appropriate.
Thanks a lot for your answers
Zara
Answer:
I am using the 2nd solution not recommended by SAP, i.e., adding fields and filling in RSAP001.
Problem arises when quantity changes, because it changes conditions, and delta does not work because I have not the old condition value to invert the sign.
Could be possible to leave this solution and in extract process to delete records that are cancellations (rocancel = 'X') and then, use an ODS in BW?
So, delta won't be controlled by LO extractor, but by ODS change log.
What is your opinion??
Regards.