Run time error while Creating IDN and Inbound Delivery

Hi All,
I am getting Run time error while creating Inbound Delivery Notification from Inbound Queue and Inbound Delivery from IDN
After debugging i come to know that system is looking for Patch Level SAPKNA7026 but in my system Patch is upto SAPKNA7022
Is there any OSS notes available to deactivate/resolve this run time error ? I tried 0001798794 Deactivation of hierarchical access functionality but system is still giving me run time error
Regards,
P@M

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Similar Messages

Run time error while creating a sales order by va01

hi ,
while i am creating a sales order a runtime error occurs as i fill entry for sole to party and then material and quantity and as i press enter. the run time error is:
error in current abap program "saplv61z" had to be terminated because it has come across the statement that unfortunately can not be executed.
kindly solve my problem.
thanks.

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Run time Error while Creating Expense request

Dear Friends ,
In   E-Payment ( Expense Claim )   creation , While clicking on Enter Receipts application is going to run time error for only one user.
Run time Error Info :
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Exception              CX_SY_REF_IS_INITIAL
Short text
     Access via 'NULL' object reference not possible.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_WDR_P13N_UTILITIES=========CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
   The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
   procedure "PRESET" "(METHOD)", nor was it propagated by a RAISING clause.
   Since the caller of the procedure could not have anticipated that the
   exception would occur, the current program is terminated.
   The reason for the exception is:
   You attempted to use a 'NULL' object reference (points to 'nothing')
   access a component (variable: "LR_CONTEXT_ELEMENT").
   An object reference must point to an object (an instance of a class)
   before it can be used to access components.
   Either the reference was never set or it was set to 'NULL' using the
   CLEAR statement.
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
   If the error occures in a non-modified SAP program, you may be able to
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the following
   keywords:
   "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
   "CL_WDR_P13N_UTILITIES=========CP" or "CL_WDR_P13N_UTILITIES=========CM002"
   "PRESET"
Information on where terminated
    Termination occurred in the ABAP program "CL_WDR_P13N_UTILITIES=========CP" -
     in "PRESET".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 60
    of the (Include) program "CL_WDR_P13N_UTILITIES=========CM002".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "PRESET" "(METHOD)", but it was neither handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_WDR_P13N_UTILITIES=========CP "; its source
     code begins in line
    1 of the (Include program "CL_WDR_P13N_UTILITIES=========CM002 ".
Regards,
Suresh .

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Run time error while creating sales order

hi all,
im working on ECC 4.7. normally when i create a sales order (VA01) and use incompletion log, it shows no errors. but when i start to save the same order . it shows a RUN TIME ERROR of ABAP . so plz help me to solve out this error
thanks\

Hi Tarun,
When you get a run time error, you can see the error analysis on the left hand side. Check what the analysis is saying and you may need an ABAPer to find out the exact reason for the dump. I am just guessing it could be due to number range.. just a guess.
Regards,
Raghav

Run time error while creating billing doc.

Hi all,
While saving a billing document I am facing runtime error every time. Can any one help me what are the possible reasons and possible solution to overcome this. Since it is on high priority, expecting response at the earliest.
Sunanda.P

Dear Sunanda,
Since it is on high priority, expecting response at the earliest.
You must get in-touch with your BASIS-Admin, for earliest resolution of the error, as he is the only one, who may find the reason and fix the same, at earliest.
Or,
If, you could provide System error-log, at the time of Run-time Error, then, some work arounf could be suggested.
Otherwise, It would be like Hit-n-Trail.
Best Regards,
Amit
Note: This is, what I feel and suggest, in such cases:
[ABAP/ Runtime Error|Re: update control terminated error]

Run time error while creating Ecommerce Order

Dear Friends,
we are using ECC 6.0, Ecommerce 5.0 applications run internet sales.
After selecting the requried products from the product catalog while trying to save the order I am getting a Run time error and also my session is getting logged out of the web shop.
I have searched the threads on similar issue, but found no clue yet..
Any help is highly appreciated.
Regards
Sadhu Kishore

#1.5 #005056A31282001C0000000400001AD800047FB93365B5C7#1266333314895#/Applications/BusinessLogic#sap.com/crmentitlementinquiry#com.sap.isa.core.jmx.ext.ExtBootstrapper#Viw~t0yxJv!nzcjy*!6#67##n/a##157475101b0e11dfb011005056a31282#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/BusinessLogic#Java###Error in CCMS reporting: #1#unable to register MBeans#
24309   #1.5 #005056A3128200280000000000001AD800047FB938DA2ACD#1266333406410#/Applications/BusinessLogic#sap.com/crm~b2c#com.sap.isa.core.init.InitDescription.getInitializable#Guest#0##n/a##4c1152a01b0e11df8c0b005056a31282#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.advisor.backend.tst.AdvisorBackendTST#
24310   #1.5 #005056A31282002A0000000000001AD800047FB93AB6F382#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Administrator#129##n/a##5eb1b1c01b0e11df9db4005056a31282#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24311   #1.5 #005056A31282002B0000000000001AD800047FB93AB6FCE4#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c11b0e11dfb98f005056a31282#Thread[Thread-129,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24312   #1.5 #005056A31282002C0000000000001AD800047FB93AB6FF9E#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c21b0e11dfa58b005056a31282#Thread[Thread-130,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24313   #1.5 #005056A31282002F0000000000001AD800047FB93BC6D909#1266333455473#/Applications/BusinessLogic#sap.com/crm~cviews#com.sap.isa.core.init.InitDescription.getInitializable#Administrator#133##n/a##694fbe101b0e11dfcc96005056a31282#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.useradmin.handler.UseradminInitHandler#
24314   #1.5 #005056A3128200330000000000001AD800047FB93DD62A70#1266333490035#/Applications/Common/Infrastructure#sap.com/crmicss_b2c#org.apache.commons.digester.Digester#Guest#0##n/a##7de97c301b0e11df9146005056a31282#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#org.apache.commons.digester.Digester#Java###system.forward.info#1#com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crmicss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)(:main:, row=0, col=0) -> com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crm~icss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)#
24315   #1.5 #005056A3128200220000001000001AD800047FB961D04BAD#1266334093676#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.maintenanceobject.backend.MaintenanceObjectHelper#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/Applications/Common/Infrastructure#Plain###Cache already initialized#
24316   #1.5 #005056A3128200220000001200001AD800047FB961F0F65E#1266334095816#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24317   #1.5 #005056A3128200220000001300001AD800047FB961F1C37B#1266334095879#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24318   #1.5 #005056A3128200220000001400001AD800047FB961F25A6B#1266334095910#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24319   #1.5 #005056A3128200220000001500001AD800047FB961F2E857#1266334095941#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24320   #1.5 #005056A3128200220000001600001AD800047FB961F403B4#1266334096019#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24321   #1.5 #005056A3128200220000001700001AD800047FB961F43A81#1266334096035#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24322   #1.5 #005056A3128200220000001800001AD800047FB961F46D0E#1266334096051#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24323   #1.5 #005056A3128200220000001900001AD800047FB961F49D86#1266334096066#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24324   #1.5 #005056A3128200340000000000001AD800047FB962954A0E#1266334106598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.DocumentHandler#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.isa.isacore.DocumentHandler#Plain###b2b.dochandler.warn.notontop#
24325   #1.5 #005056A3128200290000004400001AD800047FB962D270BC#1266334110598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24326   #1.5 #005056A3128200350000000000001AD800047FB963A12DA7#1266334124145#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_5##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24327   #1.5 #005056A3128200320000000100001AD800047FB963FE1C13#1266334130239#/Applications/BusinessLogic#sap.com/crm~b2b#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: 'CMRCV'
24328   null
24329   #parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
24330   Properties: {lang=en, passwd=?, sysnr=00, client=020, user=uname, ashost=hostXX, jco.client.type=A, maxcon=100, codepage=1100}
24331   Client not connected#
24332   #1.5 #005056A3128200320000000300001AD800047FB963FE781C#1266334130271#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.action.order.MaintainBasketSimulateAction#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###A runtime exception occurred on the highest level#
24333   #1.5 #005056A3128200320000000500001AD800047FB963FEEFEB#1266334130302#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.core.util.MessageListDisplayer#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###An exception has occurred: .#

Run time error while create Vendor master via MK01

Dear Experts,
when i try to create vendor master by MK01.....system throws run time error as below:
"The exception 'CX_BADI_MULTIPLY_IMPLEMENTED' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CVI_MAP_TITLE=================CP' has to be
terminated."
My current system is ECC 6 along with DBM. Business partner configuration is activated in the current system. I am getting this error after BP configuration. Could you please help me to fix this issue?.......Is it due to configuration or a dump from abap program?
Regards
Vetrivelan

Hii,
please search sdn before posting the threads.
check these links, it may help u............
Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
CX_BADI_NOT_IMPLEMENTED
thanks.

Run time error while creating sales order in VA01

Dear all,
In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
application patch level for both production and development is same.
can any one suggest the solution please
Moderator message - Cross post locked
Edited by: Rob Burbank on Jan 7, 2010 10:03 AM

ths

Run time error while creating new user??????

HI Gurus,
when i am creating a user in crm 7.0 server it s going into dump.
DESCRIPTION:
Category               Internal Kernel Error
Runtime Errors         DDIC_TYPE_REF_ACCESS_ERROR
Application Component BC-ABA-LA
Date and Time          23.02.2012 22:36:02
What happened?
Error in the SAP kernel.
The current ABAP "SAPLBUPA_INTERFACE_OUTBOUND" program had to be terminated
because the ABAP processor detected an internal system error.
Short text
    Internal error in DDIC structure description
Error analysis
    There is an error in the structure description of the Dictionary type
    "BUS_EI_BUPA_CENTRAL". The type references the type "BUS_EI_BUPA_CENTRAL_DATA".
    Error type: "abap type or abap length inconsistent"
Information on where terminated
    The termination occurred during generation of the ABAP/4 program
     "SAPLBUPA_INTERFACE_OUTBOUND".
    The termination occurred in line 13
    of the source code of program "LBUPA_INTERFACE_OUTBOUND$06" (when calling the
     editor 130).
Source Code Extract
Line SourceCde
    1 *******************************************************************
    2 *   THIS FILE IS GENERATED BY THE FUNCTION LIBRARY.               *
    3 *   NEVER CHANGE IT MANUALLY, PLEASE!                             *
    4 *******************************************************************
    5 FUNCTION $$UNIT$$ BUPA_OUTBOUND_BPS_FILL_CENTRAL
    6
    7     IMPORTING
    8        REFERENCE(IV_MODE) TYPE !CHAR1 OPTIONAL
    9     TABLES
   10        !IT_IDLIST STRUCTURE !BUS_EI_INSTANCE OPTIONAL
   11        !IT_FRAGMENTS TYPE !BUS_EI_FRAGMENT_T OPTIONAL
   12     CHANGING
>>>>>        REFERENCE(CT_BP_EXTERN) TYPE !BUS_EI_EXTERN_T .
REgards,
Rajesh.

Following is the text from Note for Custom Password Validation logic:
Customers who wish to use their own password validation logic may do
so by writing their own Java classes that implement the
oracle.apps.fnd.security.PasswordValidation Java interface. The
interface requires 3 methods to be implemented:
1) public boolean validate(String user, String password)
    - This method takes a username and password, and then returns true
or false, indicating whether the user's password is valid or invalid,
respectively.
2) public String getErrorStackMessageName()
    - This method returns the name of the message to display when the
user's password is deemed invalid (i.e., the validate() method returns
false).
3) public String getErrorStackApplicationName()
    - This method returns the application shortname for the
aforementioned error message.
After writing the Java class to perform customized password
validation, the customer must then set the value of the profile option
SIGNON_PASSWORD_CUSTOM to be the full name of the class. If, for
example, the name of the Java class is
oracle.apps.fnd.security.AppsPasswordValidation, then the value of the
SIGNON_PASSWORD_CUSTOM profile option must be
oracle.apps.fnd.security.AppsPasswordValidation. Note that AOL/J
will attempt to load this class dynamically. Hence it is necessary to
make the class accessible by AOL/J. This means that in Forms, the
class must first be loaded into the database using the loadjava
command.
You will need to apply the following patches for 11.5.1:
   1344802
   1363919
   1472974
   1351004
   1377615
You will need to apply the following patches for 11.5.2:
   1377615

Run time Error while creating Network Activity.

Getting Runtime -
> Runtime error: ILLEGAL_TEMPORARY_OBJNR ("TM0000000008NV" " " " ")
While trying to create the Network activity in the following sequence.
CALL FUNCTION 'BAPI_PS_INITIALIZATION'.
*--> Create the Network Activity
CALL FUNCTION 'BAPI_BUS2002_ACT_CREATE_MULTI'
    EXPORTING
      i_number     = i_number
    TABLES
      it_activity = t_activity
      et_return    = it_preturn.
     extensionin = extensionin
     extensionout = extensionout.
LOOP AT it_preturn INTO wa_preturn.
    IF wa_preturn-type EQ c_error OR
       wa_preturn-type EQ c_termination OR
       wa_preturn-type EQ c_exit.
      l_error = c_yes.
    ENDIF.
ENDLOOP.
IF l_error IS NOT INITIAL.
    ROLLBACK WORK. " satish 09/02/2008
    EXIT.
ENDIF.
CALL FUNCTION 'BAPI_BUS2002_SET_STATUS'
    EXPORTING
      number                   = i_number
      set_system_status        = 'CRTD'         " changed 'REL' to 'CRTD' satish 11/04/2008
    IMPORTING
      return                   = lwa_ret1
    TABLES
      i_activity_system_status = lt_act_status_set
      e_result                 = lt_stat_ret.
IF lwa_ret1-type EQ c_error OR
     lwa_ret1-type EQ c_termination OR
     lwa_ret1-type EQ c_exit.
         call function 'BAPI_TRANSACTION_ROLLBACK'.
    EXIT.
    endif.
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
    TABLES
      et_return = lt_return.
   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
Help really appriciated.
Thanks
Mani

Hi,
Go through the SAP NOTES 777934
Symptom
When a new network activity is created using BAPI, BAPI_BUS2002_ACT_CREATE_MULTI and then the newly created activities are
reverted by using BAPI BAPI_TRANSACTION_ROLLBACK,the control objects of newly created activities are not reverted, therefore when you perform a
commit of the transaction by using BAPI_TRANSACTION_COMMIT, a short dump'ILLEGAL_TEMPORARY_OBJNR' occurs.
Other terms
short dump 'ILLEGAL_TEMPORARY_OBJNR', CKCOUEB, Costing Sheet, Posting Date, Overhead key, CK_F_CO_OBJECT_ALL_REFRESH, BAPI_PS_INITIALIZATION.
Reason and Prerequisites
This is caused by program error. This note references SPC 770601 and created for corrections to be included in support package.
Solution
Implement the source code corrections.
Regards,
Dwaraka.S

REG:RUN TIME ERROR WHILE CREATING USERS

HI ALL,
When i am trying to crreate a new user in sap system ecc6.0 with mssql.
an sysntax error is accuring in the system
Syntax error in program "SAPLBUPA_INTERFACE_SERVICE ".
The current ABAP program "SAPLBUPA_INTERFACE_OUTBOUND" had to be terminatedbecause it has
The following syntax error occurred in program "SAPLBUPA_INTERFACE_SERVICE " in
include "LBUPA_INTERFACE_SERVICETOP " in
"The type "BUPA_INBOUND" is unknown."
i also changed the parameter to zero
login/no_automatic_user_sapstar = 0
so that we can login using sap*, which is not possible
please help me in solving this issue.
Thanks!
Vardhan.
Edited by: vardhan197 on Mar 29, 2011 9:59 AM

Hello,
i have checked my system (ERP6.0) and the type is BUPA_INBOUND is available. So please check this in your system:
call transaction se38 and look at the source code of Report SAPLBUPA_INTERFACE_SERVICE
double click at the INCLUDE LBUPA_INTERFACE_SERVICETOP
scroll down to line 147 where the BUPA_INBOUND is referended
double click at BUPA_INBOUND
If it is available and displayed, activate it and try again to create a new user.
Please also check what authorizations you have.
Good luck
Christian

Run time error while doing VL10B transaction for STO

Dear All,
We are facing problem of run time error while creating Delivery (VL10B) for STO .We have two company codes .For one company code its working fine .But we are trying for another company code ,this error coming.error detals
Error in the ABAP Application Program
The current ABAP program "SAPLV05I" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not cau
     in
    procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAI
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
Kindly suggest as to how to resolve this asap.
regards
umesh

These Kind of Errors Generally Occor for the wrong maitnaince of the partner functions. If you are using any user exits to detremine the partner functions. check the logic in that routine.
Because we do frequently get this error, but only if we hae not maintained as per the rule written in the user exit..
The USer exits for partner Determiantion to check is Function Module EXIT_SAPLV09A_003. THis gets activated, if you have give the source parner function as "X/Y/Z" in your partenr determiantion procedures.

System is giving ABAP run time error while perform LT06 or create TO with r

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
Short dump has not been completely stored. It is too big.
P_MENGA = P_MENGE.
007940 P_UMREZ = 1.
007950 P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

Hi,
Go to Tcode ST22 and mentione the dump code there and check.
Also take help[ of Abapers to fix it.
Thanks
Utsav

ABAP run time error while perform LT06 or create TO with respect to posting

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
>> Short dump has not been completely stored. It is too big.
>       P_MENGA = P_MENGE.
007940       P_UMREZ = 1.
007950       P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

This part is just the place in the program where the error occured, but why the error occured is mentioned earlier in the dump.
Maybe you have a too big number in the field and hence a field overflow, maybe you have a character instead of a number in the field.
Read the dump from the beginning. if you dont know how to read a dump,then try to get help from any local Abaper.

Run-time error while executing alv grid report

Hi everyone
I m trying to run a alv grid report it is giving a run time error while executing the statement CALL METHOD V_ALV->SET_TOOLBAR_INTERACTIVE.
Actually i added 2 buttons in the toolbar.after that when i execute the report i m getting errors.
<b>Error Analysis</b>
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "TOOLBAR_MENUS_INIT" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "ME->M_CL_MENU_BUTTON_VARIANT").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.

Hi Dinesh,
Seems you have not initialised ( Instantiated in OO ) the object and / or the parent container.
Check if you have create object for both the parent as well as the alv object.
So when you instatntiate the object of ALV you pass the object ( instantiated before hand ) in the parent container position.
Also you would have to register the events to the object using method. Then only the buttons will finction.
eg :
IF G_CUSTOM_CONTAINER IS INITIAL.
    CREATE OBJECT CUSTOM_CONTAINER_1
           EXPORTING CONTAINER_NAME = CONTAINER_1.
    CREATE OBJECT GRID1
           EXPORTING I_PARENT = CUSTOM_CONTAINER_1.
    CALL METHOD ALV_GRID1->SET_TABLE_FOR_FIRST_DISPLAY
         EXPORTING I_STRUCTURE_NAME = 'VBAK
         CHANGING IT_OUTTAB        = IT_VBAK.
Reward points if useful.

Run time error while Creating IDN and Inbound Delivery

Similar Messages

Maybe you are looking for