Skip to Content

Output type YGTA in PO is taking to a dump screen.

Hi Experts,

I have a situation where a custom output type (YGTA) when added in Messages (Purchase order) and trying to save the PO is dumping out. As in if we give another output type its fine but only when the user inputs this, is taking the user to screen dump by getting the PO saving terminated,.

And when the user checks the inbox

"Update was terminated".

Error Info... Internal session terminated with a runtime error CONVT_CODEPAGE (see ST22)

Now how do we tackle this issue, do we need to an ABAPer to work our way into it?. I deleted the Condition recs before making sure the test client gets it ok but whenever we try to add again we are back to square one, could you folks please gimme a heads up of how to tackle this issue if you will?

Look forward to hearing from you folks!



SCN Upload.jpg (27.4 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Jul 12, 2016 at 01:32 PM

    How shall we know what YGTA is, how the customizing is different from other output types and whether you still use the SAP given print program or an own print program which dumps.

    did you even follow what the error wanted from you? have you been in ST22? Did you read the dump in detail?

    Add a comment
    10|10000 characters needed characters exceeded

    • Yes Juergen, you are right,this had nothing to do with Print program. What I found strange was when I clicked on the check button while saving the PO the termination stopped. not sure what was causing this issue but yes now the user isn't getting that as well:-) May be it has got something to do with cache and will be investigated by the ABAP team. Anyway this got rectified (not the termination but a workaround ) a while ago, just didn't occur to me to thank you for your inputs! So thank you sir!

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.