Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Group pricing condtions not fully processed in Save_document_prepare

Former Member
0 Kudos

We have a piece of code in save_document_prepare, that loops against XKOMV and if there's and EDI1, customer expected price, it compare and either added a delivey block or just sends an email.

We added a new group condition and at the time this code is executed, it doesn't appear that all the group condition processing has finished and we are getting mixed results. If I move the code to save_document all is fine, but then I can't set the delivery block.

Any ideas? Kind of sounds like a bug to me. The group condition processing that is.

Thanks

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Cathy,

we are also dealing with XKOMV in SAVEDOC_PREPARE and group conditions are in the game.

And it works fine from 46C up to ECC60.

Sounds like a bug. Did you check OSS? Many notes out there regarding group conditions.

Worst case: How about changing your logik from XKOMV to VBAP-CEPOC (which is set for EDI in Formula 009) ??

Cheers

carsten

2 REPLIES 2

Former Member
0 Kudos

Cathy,

we are also dealing with XKOMV in SAVEDOC_PREPARE and group conditions are in the game.

And it works fine from 46C up to ECC60.

Sounds like a bug. Did you check OSS? Many notes out there regarding group conditions.

Worst case: How about changing your logik from XKOMV to VBAP-CEPOC (which is set for EDI in Formula 009) ??

Cheers

carsten

Former Member
0 Kudos

Carsten,

thanks for your reply. I did check around OSS and I think I may put something on there.

I don't know if the problem has to do with the fact that the group condition also has a quantity scale and it's grouped by product hierarchy or what. I did get around it a bit. Not maybe in the best way, but my problem seems to be gone.

I moved the same logic to USEREXIT_NUMBER_RANGE! Not the proper place for it, but everything seems to be ok.

Cathy