on 09-19-2017 8:57 AM
Dear community,
I am trying to deal with an incorrect partner functions determination in a sales order.
I have a Customer with different partners per sales area - As you see in the capture, en IT31-10-10 each partner function has different numbers while in IT31-10-20 all partner functions have the same number as the sold-to.
When I create a sales order with header IT31-10-10 the resulting SHIP-TO partner's functions at header level is incorrect - :
The log says that the "partner was defined manually" (!) but I can tell you that it wasn't so something's going wrong or I'm missing something in customizing which I doubt as I am using the standard procedures.
Would you have any idea of why is that happening?
Best Regards,
David
In your KNVP screenshot actually the ship-to parties are different than the sold-to, but this is not important for now.
If I understood you correctly, the order is created without reference and this was done after the master data was changed and it is indeed for IT31-10-10.
Could you also post screenshots of your VOPAN setup for sales order header? I am mainly interested in V_TPAER_VK, because it is possible to have additional custom logic for partner determination via exit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your VOPAN setup looks absolutely normal to me and with standard configuration it should determine ship-to from the sold-to party (no x, y,z in origin and nothing specific in the source for SH) .
Is there any chance for another user exit interfering with partner determination? Normally one would expect this to be done done via some of the V09A* enhancements, but I would not eliminate the possibility of other points where this might occur.
This is probably a stupid thing to ask, but are you using common distribution channels or divisions? Such a thing could explain some illogical messages in the determination log and unexpected partner found.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.