Short Dump in PS BAPI : BAPI_BUS2002_ACT_CREATE_MULTI

[Former Member]

Hi,

I'm trying to use the BAPI BAPI_BUS2002_ACT_CREATE_MULTI to create an Activity in a Network. I have a custom table, with many work order numbers,which will create the network with internal number ranges, and also create many activities in the network based on certain condition. This is a batch program.

The problem is, when I have an Error (few cases) in the creation of one Activity (the error returns at the return table of the BAPI_PS_PRECOMMIT ), the program finish with a short dump "ILLEGAL_TEMP_OBJNR" , but this is not happening all the time(the error is not coming during the debugging).

Can any body help me out.

Regards,

Sudipta

[Sathya_Gunasekaran]

Have you tried introducing wait statement in the loop?

Sathya

[Former Member]

Yes, after every BAPI_TRANSACTION_COMMIT , there is 'wait up to 1 Seconds' inside the loop, but problem is in this case the short dump is coming from the BAPI_PS_PRECOMMIT, so the Commit work & the 'wait up to 1 Seconds' statement is not triggering.

[NTeunckens]

Could you try the following :

• See if SAP-KBA 1940255 "Dump encountered on executing BAPI_PS_PRECOMMIT and performance bottleneck identified" applies?
• If not : I saw a previous Question that sounds quite the same. There, only solution was using another BAPI "BAPI_NETWORK_MAINTAIN" in conjunction with BAPI "BAPI_PS_PRECOMMIT" ...

Hope these suggestions help you in solving the issue

Nic T.

[Former Member]

Dear Nic Teunckens,

Thanks for your reply.

The issue is that we are not getting error all the time, the issue "ILLEGAL_TEMP_OBJNR ("TM0000000696NV" " " " ") " is coming in an interval of 20-30 days, but on the very next day it issue is not coming. I've tried to replicate the issue many time during debugging but unable. As per my understanding the issue is not with BAPI : BAPI_BUS2002_ACT_CREATE_MULTI but with FM: BAPI_PS_PRECOMMIT.

As per ST22 : Termination occurred in the ABAP program "SAPLKKCK" - in "CO_OBJECT_SWITCH_NUMBER".

Which is basically called inside: BAPI_PS_PRECOMMIT -> CN2002_NETWORK_PRECOMMIT-> CO_ZV_ORDER_POST-> VB_CHECK_OPR_SEQ - > CO_BO_OPR_SEQ_VB_CHECK-> CK_F_CO_OBJECT_NUMBER_SWITCH-> CO_OBJECT_NUMBER_SWITCH -> KKCK_CO_OBJECT_NUMBER_SWITCH.

Regards,

Sudipta Chakraborty

[NTeunckens]

OK, can you evaluate the following SAP-KBA :

• 777934 : "Short DUMP: ILLEGAL_TEMPORARY_OBJNR,when saving"
• 2104866 : "CJV4: Termination with runtime error 'ILLEGAL_TEMPORARY_OBJNR' in subroutine CO_OBJECT_UPDATE_ON_DB"

Check is the Oldest KBA is in your system as this should fix the issue ...

[Former Member]

Hi,

I have gone through the above KBAs and these are already in our system as we using release 604(SP level- 16). Anyway thanks for your kind support.

Regards,
Sudipta

[NTeunckens]

Sorry to hear that didn't help ...

Any UserExits / BAdI's implemented that could interfere the use of the BAPI?

Maybe you can de-activate these in DEV and do a test?

[Former Member]

There is no such UserExits / BAdI implemented which can interrupt the process, and also the short dump "ILLEGAL_TEMP_OBJNR ("TM0000000696NV" " " " ") " from BAPI_PS_PRECOMMIT is not coming all the time.

Regards,

Sudipta