on 01-18-2018 6:01 PM
Aftre posting delivery using LT03 and trying to create TO:
the system message is: "0 transfer orders has created".
When I check the material flow document in VL03n, there is a TO number but this transfer order number is not exists in LTAK table!!! TO only has created in VBFA.
(No Error log in ST22 or SM13)
any idea?
Thanks
Bahman
If memory serves, the only time when I saw something similar to what you described, it was caused by custom development.
Is the case reproducible?
I suppose that the document can be corrected with WS_CORR_VBFA_LTAP and (maybe) RVDELSTA afterwards, but on finding out what has caused this (if you cannot reproduce the example and if you use only SAP standard) I really have no idea.
And I do not know how wise it is to correct the document and ruin the example (unless this delivery is in a production system).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Veselina,
thank you and Yes, the issue happens for all OBDs. It is probably caused by custom development. just not sure in which part LTAK is updated during this process. any User exit or Enhancement?
Regards
Bahman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you want to do with a user exit or enhancement?
Just have your ABAPer or you team find out what has been developed before it started to work wrong. There must be a requirement from the business, a function design spec, documentation to the functional test and regression test. Probably a workflow with approval to transport changes to a production system.
Use transaction ANST and redo the transaction which causes the problem, it will tell you if there are OSS notes which might be applied and will also show you which exits are used.
User | Count |
---|---|
95 | |
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.