topic Re: Runtime error costcenter creation in Application Development and Automation Discussions

Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 21:37:24 GMT

Hi folks

while iam creating cost center ( KS01) iam getting the runtime error

001210 CASE icsksp-xxdbaction.

001220 WHEN equ-dbins.

001230 INSERT csks.

001240 vb_check.

001250 IF NOT cskt-ktext IS INITIAL.

001260 INSERT cskt.

> vb_check.

001280 ENDIF.

001290

001300 LOOP AT lt_cskt_txt.

001310 MOVE-CORRESPONDING lt_cskt_txt TO cskt.

i put the breakpoint in the prgoram.

and i create the transaction KS01. the programing not stoping at breakpoint.

but an error mesaage (short dump) going to sap inbox

please tell me how to solve the issue

regards

sri

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 21:42:42 GMT

But what runtime error are you getting in the short dump?

Jonathan

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 21:43:47 GMT

Use transaction SM13 to examine failed updates. there may also some information in the system log (SM21) and dump analysis (ST22).

Rob

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 21:58:25 GMT

thanks for your reply please find the procedure.

enter--KS01

---do updateds

---save

then an message is coming that "cost center has been updated".

then immidiately an notification popup coming that

"express document " update was teriminated recived from the author "

an email is going to sap inbox

iam unable to debug the program is not stoping at breakpoint.

pls help me

its urgent

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 22:02:44 GMT

but did u try to check if the cost center has been created or not?

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 22:05:22 GMT

You don't have to debug (at least not yet). Use the transactions I suggested to see what happenned.

rob

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 22:30:27 GMT

In checked the dump analysis (ST22).

Error analysis

Short text of error message:

VB_ERROR

Technical information about the message:

Message classe...... 00

Number.............. 208

Variable 1.......... "VB_ERROR"

and if the check the table CSKT the cost center has created.

but once i click 'master data' button in KS01. the popup box is coming with error message

please clarify

regards

sri

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 22:39:16 GMT

Seems like there is an workflow designed on it for an action to be performed after the cost center is created and this looks like is giving an error. Try to find out more details about it otherwise an express document email woudn't be sent to INBOX.

Re: Runtime error costcenter creation

Former Member — Mon, 24 Sep 2007 23:00:41 GMT

could you please explain in more details.i think the workflow is created to send message ( error or sucess) to the user inbox, but the error could be related to the sourse code because in st22 it dipalying the sourse code where the error is

001250 IF NOT cskt-ktext IS INITIAL.

001260 INSERT cskt.

> vb_check.

001280 ENDIF.

001290

i guess i can check this in debugging but my programing is not styoping at breakpoint.

please tell me anybody how to solve it

regards

sri

Re: Runtime error costcenter creation

Former Member — Tue, 25 Sep 2007 00:40:20 GMT

You may want to create an OSS message about this.

Rob

Re: Runtime error costcenter creation

Former Member — Tue, 25 Sep 2007 00:50:47 GMT

Hi Rob ,

Thanks for your reply. i find some solution ,now iam going to apply and test it.

if it doesnt work out, i will go for OSS note.

Regards

sri

Re: Runtime error costcenter creation

Former Member — Tue, 25 Sep 2007 02:35:14 GMT

Just to clarify, are you getting the abend in your current session or is there a separate session that is getting the abend... i.e. if you look in the ST22 abend, is it showing your userid and the date & time that you were using the cost centre create, or is it a few seconds later, which would indicate that it is a triggered task that is hitting the problem (which would explain why you don't hit the breakpoint). Do you have ALE master data distribution turned on, or something else triggered from change documents, for example?

Jonathan