on 04-17-2013 9:31 AM
Can you check your PO number range , some times The P.O number would have been exausted and there
are chances that you get error message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jaheer,
you can analyse the termination in SM13 tcode, I had faced same issue some time back while posting MIGO, you will get the ideas in SM13 what is causing the update termination.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The purchase order number is shown to the user prior to the physical update in the database.
The failure notice tells you that your update failed, your PO is lost and has to be created again.
You have to use SM13 to analyze why you got this update failure, there you can see the error and if needed you can create a dump for further analysis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Did you have custom purchase order output type (message type) for your purchase order layout?
For your error check your purchase order output type (message type) which cause concern.Use t.code: NACE and find Program, Routine and Form or PDF/Smartform. Now discuss with ABAPer and check did any message text creating issue to save/update purchase order number purchase order table.
Also cross check purchase order number range and your user ID authorisation to create purchase order!
Regards,
Biju K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
10 | |
5 | |
5 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.