Skip to Content
0

group condition issue

Nov 24, 2016 at 11:43 AM

129

avatar image

Hi experts,

I had an issue about group condition, or it might not be, so I wanted to discuss it out there,

I created a condition type, it is requested to set up at header level, but it needs to have access sequence (sales org/vendor) to set it up , so I have to set it as header condition as well as item condition.

And this condition also needs to have a header fixed amount no matter how many items it has in the sales order, so I set it as group condition, group condition routine is 1, I also ticked rounddiffcomp, it is working well except for below;

Let's say the amount of header is 100 USD. When I was entering the order, this 100 USD did not be showed up in initial value field, it was only showed after I went to header and click the condition tab and get back, OR save the order. But I was trying to go to item condition and clicked analysis button, the condition is showing green. It's weird. so my question is:

why it was only showed after I went to header and click the condition tab and get back, OR save the order. is it supposed to be showing at first place (when I was entering the order , so it should be adding this 100 USD in initial value field , right? )

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

G Lakshmipathi
Nov 24, 2016 at 12:40 PM
0

It would have been ideal had you shared the screen shot of condition tab how it looks at item level before and after. Since you have set the header condition type as also an item condition, hope you would have maintained condition record for 100 USD. So once you key in the material code and hit enter button, were you getting any message ? How it looks like in item condition tab?

Share
10 |10000 characters needed characters left characters exceeded
Allen Qiu Nov 25, 2016 at 07:05 AM
0

Sure Lakshmipathi,

The condition type is ZS38, BEFORE saving the order, the condition value is 0 which had not been distributed from header, AFTER I save the order, it was working correctly and the item condition value gets split from its header, OR I went to header and click condition tab and get back, it was also working. Is it weird? Do you have any ideas?

before

after


before-2.png (25.6 kB)
after-1.png (24.5 kB)
after-2.png (28.2 kB)
Share
10 |10000 characters needed characters left characters exceeded
Surya Sarathi Lahiri Nov 25, 2016 at 12:28 PM
0

Hi Qiu ,

I am not clear about your requirement ,

I have a question do u want the condition ZS38 to be a header condition and auto popullate in the so?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

It's a header group condition , what the issue is that the value didn't get displayed unless I went to header and click condition tab or save the order,. Say zs38 is 75 dollar, net price of item 10 is 10, so it should be showed 85 at the value field when entering the order , but it showed 10 instead , but it will show 85 after I went to header clicking condition tab and get back or save the order , could you figure it out ?

0
Surya Sarathi Lahiri Nov 30, 2016 at 07:35 AM
0

Hi Qui ,

IF zs38 is a header condition you have to maintain the value it manually , automatic condition value determination not possible.

I request you to maintain it only as header or item condition.

For item conditions i hope you have maintained the condition record and the correct acess sequence.

Regards

SSL

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi,

Actually it's a group condition, so it pops up at header and it does has access sequence, say it has 75 USD in its header , it is split up to its items by the quantity and value, but the issue is that 75 amount does not show when placing the order at initial screen , it has to go to the condition tab of header , then get it back and save . Or it will be showed after saving the order.

0
Veselina Peykova
Dec 09, 2016 at 08:24 PM
0

I have seen something similar a few years ago.

If I remember correctly, the cause was a bug in a VOFM routine.

Share
10 |10000 characters needed characters left characters exceeded