on 08-24-2011 10:11 PM
Hello,
We have a scenario where we are create return to vendor PO's utilizing deliveries. We have two different document types, one of which we need a custom movement type to satisfy financial requirements.
I have created a new schedule line and mapped it to the delivery type. When I create a return PO and generate an outbound delivery, the delivery shows the correct, custom, movement type. However, when I post goods issue, it utilizes the standard 161 movement type.
Looking in OMJJ at movement type 101, there is an entry under follow-on movement for function code WERE which specifies 161 should be used (if i change 161 it will post to what is specified).
This is causing our mat.doc to post with the wrong movement type. Has anyone else come across this? How can this be handled? Is is possible to specifiy a new function code within the delivery (table V_156N_VC let me create new ones tied to a movement, but I am unable to trigger their use).
Thanks,
Matt
Return PO will use Mvt 161, this is standard process.
What do you expect?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.