Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Getting dump while PO save after release. (T-Code. ME29N)

Former Member
0 Likes
1,259

In a perticula PO type i m getting DUMP after release and save Purchase order.


Update was terminated

System ID....   SRD
Client.......   300
User.....   SBRABAP
Transaction..   ME29N
Update key...   D15A70E30653F121960F3440B582FB16
Generated....   29.12.2013, 12:58:50
Completed....   29.12.2013, 12:58:53
Error Info...   Internal session terminated with runtime error RAISE_EXCEPTION (see ST22)



Error analysis

    A RAISE statement in the program "CL_GUI_FRONTEND_SERVICES======CP" raised the

     exception

    condition "CNTL_ERROR".


This error occured for one perticular PO type.

But if i remove driver program and Smartform from NACE then error resolved.


why error occured only for perticular type.

In a perticula PO type i m getting DUMP after release and save Purchase order.


Update was terminated

System ID....   SRD
Client.......   300
User.....   SBRABAP
Transaction..   ME29N
Update key...   D15A70E30653F121960F3440B582FB16
Generated....   29.12.2013, 12:58:50
Completed....   29.12.2013, 12:58:53
Error Info...   Internal session terminated with runtime error RAISE_EXCEPTION (see ST22)



Error analysis

    A RAISE statement in the program "CL_GUI_FRONTEND_SERVICES======CP" raised the

     exception

    condition "CNTL_ERROR".


This error occured for one perticular PO type.

But if i remove driver program and Smartform from NACE then error resolved.


why error occured only for perticular type.

2 REPLIES 2
Read only

nabheetscn
SAP Champion
SAP Champion
0 Likes
744

Hi Parag

Is that output type used for printing or does it save some local pdf file...? If yes please check in case of print you are passing the correct peinter value. The reason this is happening is because output type are processed in update mode in which no screen etc shall come as they triiger implicit commit.

Please check it no front end interaction is their neither for entering printer etc.

Nabheet

Read only

Former Member
0 Likes
744

Thanks for ur responce.

problem is resolved after change condition record for date/time for that perticular PO type.