ABP run time error in cash sales

Dear All,
In the cash sales,when I am going to save the invoice through T.code VF01 ,it is showing an error that is "ABAP runtime errors,GETWA_NOT_ASSIGNED_RANGE,field symbol has not been assigned.Can anybody tell how can I solve this problem ??
with regards,
Rana

Hi,
This is an ABAP dump stating that no values are assigned to a particular variable. This could be because of missing values either that should flow via config or manual entry.
May be re-try one more time and taking help from any ABAPer who can look at the dump is the easiest way to narrow down the issue.
Thanks,
Vasanth

Similar Messages

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 saving sales order

Hi all,
i am working on IDES ECC 6.0, when i am saving an sales order(OR) i am getting run time error in the table CRMPAROLTP, program SAPMV45A.
i am using 4 GB RAM, still having a space of 30 GB for only IDES to save the data.
so, how to solve it.

Hello,
I doubt the runtime error (I am assuming you mean that you got a short dump) you mentioned in your original post has anything to do with the warning messages you see when doing a check (Ctrl+F2) on table CRMPAROLTP and program SAPMV45A. These warnings should not cause a short dump or runtime error.
The warning message for the table has the following long text:
Table CRMPAROLTP: Key length > 120 (Restricted functionality)
Message no. DT214
Diagnosis
The key length, i.e. the sum of the field lengths of all the key fields of the table, is more than 120 bytes.
System response
This is a warning.
Procedure
Note the following restricted fuctionality for this table:
- Table contents cannot be transported by specifying key values, at
best by specifying generic key values with a maximum length of 120
bytes.
- The table may not be used as the base table of a lock object.
The warnings in SE38 for program SAPMV45A are mostly related to Unicode and have no reference to the table CRMPAROLTP.
If you haven't already done so, please check the SAP Note referenced in my first reply since this does provide a solution for short dumps related to table CRMPAROLTP.
Of course, since I don't know specifically what the short dump message is that you received, I could be basing my assessment on false assumptions. If you have those details it is better for the SDN community as a whole if you include the information in this thread instead of sending it to me offline.
Best Regards,
Jamie

Run Time Error on Saving Sales Order

Hello,
We are facing problem when saving sales order. When order is created and save button is pressed, it saves sales order and gives Order Number. But while saving the order during update it gives dump due to Data duplication in VBFA while inserting data to VBFA table
Looking at ST22 log this error is in form VBFA_BEARBEATEN
Kindly guide.
Thanx in advance.
Regards

Check the Sales Order Number Range.
It seems either the Number Range is exhausted (completed) or a document with same number is already created in system in past...
Hope this helps,
Thanks,
Jignesh Mehta

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 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 Entering Quantity in Sales Order

Dear All,
Iam getting Run time Error while iam entering material quantity in sales order.Please find the screenshot of the same.
kindly Help Me.Me. Plz note that we had done a system copy two days back to our new server.
Rgds
Thomson
ST22 Screenshot

Dear All
Its Resolved Thanks For your Valuable time Support
INCLUDE LV03VFB4 inside below code trigger error.
PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                    WA_AVBBD-APOMOBILE
                                    DA_SUBRC
                                    DA_UPDKZ
                                    DA_VVBBD_TABIX
                                    0.
This Was the Error some how 0 was there we are removed the 0 now it is working fine
Rgds
Thomson

*FBCJ - CASH JOURNAL POSTING - ABAP RUN TIME ERROR*.

Hai,
My problem is, while FBCJ cash journal posting, Error message comes as Programme terminated, short dump is beeing formatted. The screen is quitting out to ABAP RUN TIME ERRORS. Short text of error message- For object, CAJO_DOC2 101, numer range interval 01 does not exist.( I have given the number range, but result is same.) - Pls advice, document type for cash journal is DZ ?.expecting valued support- Iam working on SAP R/3 4.7 enterprise.- TITUS GEORGE.

Hi,
GOto SNUM, Input CAJO_DOC2...
Click on change and click on document number ranges.
Maintain the document number ranges for your company code..
That should solve the problem.
Good Luck
Cheers,
Redoxcube

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 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: .#

While doing SO, im getting run time error - reg;

Hi,
While doing sales order and whenever im doing save its getting runtime error.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          14.12.2011 10:55:26
Short dump has not been completely stored (too big)
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    Short text of error message:
    Maintain the current CRM release (table CRMPAROLTP)
    Long text of error message:
     Diagnosis
         Various transfer errors occur when transferring SAP sales orders to
         CRM or there is no status update or the status update has errors
         when transferring from CRM to the SAP system. This is caused by an
         incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
         no entry is maintained at all.
     System Response
         To avoid data inconsistencies, this message causes a short dump.
     Procedure
         Maintain table CRMPAROLTP in your SAP system as is described in SAP
         Note 691710 and then repeat the process again.
     Procedure for System Administration
    Technical information about the message:
    Message class....... "V3"
    Number.............. 302
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
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.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          14.12.2011 10:55:26
hort dump has not been completely stored (too big)
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
    "BAPIDATEN_ERMITTELN"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP-Release 700
    Application server... "personal"
    Network address...... "192.168.2.11"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 80686"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "PERSONAL"
    Database type..... "ORACLE"
    Database name..... "GCU"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Aug 29 2006 00:18:21"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 75
    Patch text.. " "
Runtime Errors         MESSAGE_TYPE_X
Date and Time          14.12.2011 10:55:26
hort dump has not been completely stored (too big)
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 30311496
    Heap.... 0
    Page.... 139264
    MM Used. 14538320
    MM Free. 91952
User and Transaction
    Client.............. 100
    User................ "INFO_SD"
    Language key........ "E"
    Transaction......... "VA01 "
    Program............. "SAPMV45A"
    Screen.............. "SAPMV45A 4001"
    Screen line......... 65
Information on where terminated
    Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
    The main program was "SAPMV45A ".
    In the source code you have the termination point in line 338
    of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
Edited by: kiran35086 on Dec 14, 2011 6:30 AM

Dear kiran,
This might be many reasons.If you have not done configuration properly system will take you to dump(Run time error).
Try read the diagnosis possibly you may understand the problem.
If not You coordinate with your technical team.
Thanks&Regards
Raghu.k

Run Time Error in Account Determination

Dear Friends
In my system using std one for account det then it posting to FI.
Now I created my own Table, Access Seq, Condition Type and Procedures after all assignment when I assign my procedures to F2 .
Then I done sales cycle upto billing, but when I am trying to save it it shows Run time Error. if assigning the Std Procedure KOFI00 to F2 then it is ok.
give me solution
Thanking You
Arun

Dear Arun,
Can you provide in detail !!
What is the error you are getting when you save the invoice
Check the settings at all these steps with compare to the standard setings.
SPRO>IMG>Sales and Distribution>Basic Functions>Account Assignment/Costing-->Revenue Account Determination.
-->Check Master Data Relevant For Account Assignment
-->Define Dependencies Of Revenue Account Determination
-->Define Access Sequences And Account Determination Types
-->Define And Assign Account Determination Procedures
-->Define And Assign Account Keys
-->Assign G/L Accounts.
I hope this will help you,
Regards,
Murali.

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

ABAP run time error

Dear ALL,
When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
we are getting following run time error
Hoe to resolve this?
Runtime Errors         SAPSQL_INVALID_FIELDNAME
Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS
Date and Time          15.01.2009 16:04:19
Short dump has not been completely stored (too big)
Short text
A dynamically specified column name is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLV61Z" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
    administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
     not caught in
procedure "SEL_KONDTAB" "(FORM)", 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:
    An Open SQL clause was specified dynamically. The contained field name
    "ALAND" does not exist in any of the database tables from the FROM clause.
How to correct the error
Check the field name in the SELECT clause.
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:
"SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"
    "SAPLV61Z" or "LV61ZU01"
    "SEL_KONDTAB"
If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
    (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
The exception must either be prevented, caught within proedure
    "SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "slgsap-prd"
    Network address...... "10.140.1.11"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "8x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
Database server... "SLGSAP-PRD"
    Database type..... "MSSQL"
    Database name..... "PRD"
    Database user ID.. "prd"
Terminal................. "SD0123l"
Char.set.... "C"
SAP kernel....... 700
    created (date)... "May 6 2008 00:13:21"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
Patch level. 159
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0"
Memory consumption
Roll.... 16192
EM...... 20949200
Heap.... 0
Page.... 196608
MM Used. 15928048
MM Free. 828016
User and Transaction
Client.............. 900
    User................ "ADMIN"
    Language key........ "E"
    Transaction......... "VA01 "
    Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"
Program............. "SAPLV61Z"
    Screen.............. "SAPMV45A 4900"
    Screen line......... 930
Information on where terminated
    Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".
    The main program was "SAPMV45A ".
In the source code you have the termination point in line 672
    of the (Include) program "LV61ZU01".
    The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
     occurred in
procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor
     declared
in the RAISING clause of its signature.
The procedure is in program "SAPLV61Z "; its source code begins in line
    260 of the (Include program "LV61ZU01 ".
Source Code Extract
Line SourceCde
642     if se_prestep              = yes or
643        se_read_only_one_record = yes.
644       if t681-ksdat is initial.
645         if se_read_all_prestep is initial.
646           select * from (t681-kotab) appending table <cond_tab>
647                  up to 1 rows
648                  where kappl = se_kappl
649                  and   kschl = se_kschl
650                  and   (coding_tab).
651           h_subrc = sy-subrc.
652         else.
653           select * from (t681-kotab) appending table <cond_tab>
654                  where kappl = se_kappl
655                  and   kschl = se_kschl
656                  and   (coding_tab).
657         endif.
658
659 * it is enough to find one record in prestep
660 * (care must be taken with pool tables - depending on database this
661 * will cost performance instead of saving)
662         if select_split ne 0 and h_subrc ne 0.
663           modify coding_tab from coding_alter index select_split.
664           select * from (t681-kotab) appending table <cond_tab>
665                  up to 1 rows
666                  where kappl = se_kappl
667                  and   kschl = se_kschl
668                  and   (coding_tab).
669         endif.
670       else.
671         if se_read_all_prestep is initial.
>>>>>           select * from (t681-kotab) appending table <cond_tab>
673                  up to 1 rows
674                  where kappl = se_kappl
Regards,
Akshay
Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
Edited by: Akshay Dalal on Jan 17, 2009 6:30 AM

Dear Akshay,
We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely.

How to debug a run time error encountered while executing ZFunction Module

Hi all,
My requirement is to create a ZFunction Module that Generated a sales order
for multiple line items and works for both Variant Configurable material and a Normal Material.
I am using BAPI_SLSTRANSACT_CREATEMULTI in my Zfunction Module to create a
Sales order
My ZFunction Module works well if I give normal material as input.
It also works well and generates a sales order if I give all Variant Configurable materials as input.
But if I give both Variant Configurable material and a normal material it throws a run time error.
Can some one tell me what is wrong? can some one suggest me how to debug this run time error
Termination occurred in the ABAP program "SAPLCRM_CONFIG_OW" - in
"CONFIG_TO_CBASE".
The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 63
of the (Include) program "LCRM_CONFIG_OWF02".
Source Code Extract
Line SourceCde
|   33|                                       LT_CUXI_CUPRT
|   34|                                       LT_CUXI_CUVAL
|   35|                                       LT_CUXI_CUVK
|   36|                                       LS_CUXI_CUCFG.
37
|   38| PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.
39
|   40|* set config to cbase
|   41| CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'
|   42|       EXPORTING
|   43|            I_CFG_HEADER          = LS_CUXI_CUCFG
|   44|            I_ROOT_INSTANCE       = CV_INT_OBJ_NO
|   45|            I_LOGSYS              = LV_LOGSYS
|   46|       IMPORTING
|   47|            E_ROOT_INSTANCE       = CV_INT_OBJ_NO
|   48|       TABLES
|   49|            I_TAB_INSTANCES       = LT_CUXI_CUINS
|   50|            I_TAB_PART_OF         = LT_CUXI_CUPRT
|   51|            I_TAB_VALUES          = LT_CUXI_CUVAL
|   52|            I_TAB_VAR_KEYS        = LT_CUXI_CUVK
|   53|            I_TAB_RESTRICTIONS    = LT_CUXI_CURES
|   54|       EXCEPTIONS
|   55|            INVALID_INSTANCE      = 1
|   56|            INTERNAL_ERROR        = 2
57
OTHERS                = 3.                                                        58
|   59| IF SY-SUBRC <> 0.
|   60|    if sy-msgno is initial.
|   61|      MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
|   62|    else.
|>>>>>|      MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
|   64|              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
|   65|    endif.
|   66| ENDIF.
67
|   68|ENDFORM.                               " CONFIG_TO_CBASE

Hey Amit...
Can I Create a Sales order for VC and Non VC items using BAPI_SLSTRANSACT_CREATEMULTI
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
Some one please help me u2026I am just stuggling to get this doneu2026
I dint find any posts that gives me information about this error.
CUX1 034 u201CNo root instance found in header datau201D
In the source code you have the termination point in line 63                                   of the (Include) program "LCRM_CONFIG_OWF02".

ABP run time error in cash sales

Similar Messages

Maybe you are looking for