Run time error in VA01 after entering material at item

Syntax error in program "SAPFV45V ".
Error in the ABAP Application Program
The current ABAP program "SAPMV45A" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPFV45V " in include
  "FV45VF0A_ADD_ATP_DATA_TO_VBAP " in
line 38:
"The data object "XVBAP_LOC" does not have a component called "STOCKLOC
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPMV45A" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Can you please let me know the reason for this error.
we have completed configuration in DEV and moved all the requests into QAS
and at the first transaction of [VA01] immediately after entering material and qty
it is throwing the run time error.
please let me know, whether this error is from functional side, or from technical
(BASIS).
Please also let me know, what can be done immediately.
Thanks
Maheshoe

You need to apply SAP Note to fix this.
find the note below:
[NOTE 1072316|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1072316]
Take assistance from your Basis.

Similar Messages

  • Run time error in FMBB after execution of RGZZGLUX GETWA_NOT_ASSIGNED FM

    Hello Experts,
    We have activated funds management in Development it is working fine without any issues. Transported same changes to Quality system and executed Program RGZZGLUX.
    Issue: Run time error in FMBB transaction code even after execution of program RGZZGLUX. similar error in funds center group also.
    Category               ABAP Programming Error
    Runtime Errors         GETWA_NOT_ASSIGNED
    ABAP Program           SAPLFMBD_DATABASE_ACCESS
    Application Component  PSM-FM-BCS-BU
    Date and Time          10.06.2014 13:28:36
    Short text
        Field symbol has not yet been assigned.
    Requirement:  Please let us know how to solve this issue
    we have checked note:0000939958 - and changed Inactive status for tables FMIT, FMIP and FMIA, but no use, when we run program RGZZGLUX, it has deactivated this tables again.
    Regards,
    Chalapathi

    Hello Shyam / Javed,
    Thank you for your inputs.
    I have solved issue, now it is working fine.
    Activated EA-PS and included into transport request. executed program RGZZGLUX.
    Note used to solve issue :0000908007
    Regards,
    Chalapathi

  • Run time error in MIGO after maintaining tax code

    Hello Experts,
    I had configured the new tax code ,which is working fine for the PO document ZLOC domestic and the account category Z.
    While doing the MIGO for purchase document type ZGEN general purchase , I am getting run time error:
      "Division by 0 (type P) in program "SAPLJ1IEX".
    When I debugged the code i found that inside FM: 'J_1IEX_DEFAULT_EXCISE_DUTY'
    one another FM is being called: 'J_1I6_UNIT_CONVERSION' which is returning the value "ls_ekpo-menge" as 0(Zero).
    later in the code when "ls_ekpo-menge" used in calculation then divide by 0 runtime error is coming.
    Please suggest what need to be done.
    Is there anything related to tax code? How should I correct it?

    Hi,
            There is not value in that field for PO quantity / Value it is missing while doing MIGO. Check whether you have maintained values for all required fields.
    Kiran

  • Run-time error "ASSERTION_FAILED" occurred after BPC install

    When I try to connect through the gui, it gives me a dump in the netweaver system.
    Run-time error "ASSERTION_FAILED" occurred
    Dump -
    The ASSERT condition was violated.
    http://localhost:1080/osoft/

    Hi David,
    We are running into the same issue too. Can you please provide more details as to how you fixed this?
    We are on SAP EHP 1 for SAP NetWeaver 7.0, SAP_BW: SAPKW70103, CPMBPC: SAPK-70002INCPMBPC.
    Thanks,
    Shalin Shah

  • Run time error after starting eclipse

    Hello,
    after installation of the SAP Eclipse Theme Editor the following run time error is reported after each restart of eclipse:
    java.lang.ClassCastException: com.sap.ur.plugins.ThemeEditor32Input cannot be cast to com.sap.ur.plugins.ThemeEditorInput
         at com.sap.ur.plugins.ThemeEditor.init(ThemeEditor.java:188)
         at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
         at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647)
         at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
         at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
         at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)
         at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1429)
         at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942)
         at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
         at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
         at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
         at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
         at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
         at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567)
         at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
         at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
         at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
         at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548)
         at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
         at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
         at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
         at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
         at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
         at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
    I can work with this editor anyway after choosing the project. But I still have a problem because the preview will not change when I choose a different UI element. The preview alway shows the text "welcome to the SAP ThemeEditor!".  When I modify style parameters for the UI element Text the preview is modified in the right way. I already set the Internet Options for the Internet Explorer as suggested. Is it possible that the reported run time error is the reason for the preview problems? The external preview works fine.

    Hi,
    I would suggest you to remove NWDS, then ensure that nothing left on the disk related to NWDS, and then try a fresh install.
    Best Regards,
    Ervin

  • 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

  • Break execution after custom run-time error handler callback

    I am using Teststand 2010 SP1 and have written a custom runtime error handler based on the ErrorHandlerExample example that ships with TestStand. It has been implemented as a StationPostStepRuntimeError callback in my Station Callbacks folder.  I have modified the example as follows:
    (1) Added code to turn off the UUT transmitter if it was on.
    (2) Added a call to an executable that sends an email to the currently logged in user.
    (3) Calls the standard TestStand run-time error dialog using the Engine DisplayRunTimeErrorDialog method.
    (4) Processes the user's selection, then turns on the UUT transmitter for any option other then Abort.
    The callback also checks the status of the Break and "Don't Show again for this execution" options selected by the user.  If the user selects Break then the only option I can find is to call the API Execution.Break() method which breaks the execution right there in my callback. The user then has to single step there way out of the callback.   Is there a way of instructing TestStand to complete the callback execution and break immediately after completing the callback (i.e.at the step following the error)?  I've zipped up and attached my modified sequence.
    Alternatively, is there a better way of doing this?
    Regards,
    David
    Solved!
    Go to Solution.
    Attachments:
    StationCallbacks.7z ‏13 KB

    Didn't have a chance to try it yet but maybe StepOut is your solution?
    From the TS Help:
    StepOut Method
    Syntax
    Execution.StepOut
    Purpose
    Resumes the execution from a suspended state and then suspends the execution again after execution of the current sequence completes.
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Run-Time Error '6' Overflow within BEx Analyzer after copy/paste query

    Hi all,
    User is getting a "Run-time error '6' overflow" message which is caused after copying any query in a 'query pack' to any free row/column within the same sheet (BEx Analyzer). This "query pack" has multiple queries within one sheet and covers 1800 rows so there is enough free space left for copying one of the queries to another position in the same sheet.
    Microsoft Office Excel SP2 is used which is part of MS Office professional edition 2003. The BW version is 3.0.
    Please let me know if more details are required or above mentioned error message is recognized and can be explained.
    Thanks and kind regards,
    Raymond Flaton

    Hi VRV,
      This error is caused whenever there is memory issue. If your query is built on a cube which has a BWA index then this problem can be related to the issue with the BWA server. Check your BASIS team to check if there is memory issue presently in the BWA server.
    Sometimes the issue is temporary, where the several users accesing the reports to fetch data from BWA lead to this type of error as the BWA gets overloaded. Try exiting the report and run it after some time again.
    Alternatively you can also try restricitng the selection for fetching the data in the report as suggested.
    Thanks

  • After updating my itunes per the update notice I received a run-time error R6034 message. Now I am unable to use iTunes. What can I do to repair this error?

    After updating my iTunes per the update notice I received a run-time error R6034. Now I am unable to access iTunes at all.
    Can someone tell me how to correct this problem?

    Uninstall your existing copy of iTunes. Delete any copies of the iTunesSetup.exe (or iTunes64Setup.exe) installer files from your downloads areas for your web browsers and download a fresh copy of the iTunes installer from the Apple website:
    http://www.apple.com/itunes/download/
    (The current build of the 11.1.4.62 installer was changed a few days ago, which fixed the bulk of the reports of MSVCR80.dll/R6034/APSDaemon.exe/Error-7/AMDS-could-not-start trouble ... but the build number on the installer was not changed. So we're trying to make sure you do the reinstall using a "new good" 11.1.4.62 installer instead of an "old bad".)
    Does the install with the new copy of the installer go through properly? If so, does that clear up the error message?
    If you still have the same error messages cropping up, then try the procedures from the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • After migration EP 5.0 to EP 6.0 SR1 Run Time Error Occured

    Hi,
    After all migration processes (except the post-migration steps ) we bounced the portal and got a run time error. We checked the error log and it was : cannot get user management factory class. We already reviewed two oss notes which were 728075, 713210 and couldn't fix our problem. Here is the error message and the information about our system.
    From   EP 5.0 SP6 P1 HF8   to   EP 6.0 SP9 Patch 8
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    The exception was logged. Inform your system administrator..
    Exception id: 04:10_08/09/05_0002_9436550
    See the details for the exception ID in the log file
    Does anyone have any idea? please let me know.
    Thanks
    Serkan
    Message was edited by: Serkan Tumer

    Hi Serkan
    Please Check the log file for the exact nature of the error. You can find the log file in this location on your server.
    <Directory>:\usr\sap\CP1\JC00\j2ee\cluster\server0\log\DefaultTrace
    Do let us know what error you are facing.
    Warm Regards
    Priya

  • I am getting run time error 6034 after updating iTunes to new version.Any help?

    I am getting run time error 6034 after updating iTunes to new version.Any help?
    I tried different ways to resolve it like uninstall/install itunes
    I am also getting error message on iTunes helper.exe

    Hi isush!
    I have an article for you that will help you troubleshoot this issue:
    iTunes 11.1.4 for Windows: Unable to install or open
    http://support.apple.com/kb/TS5376
    Thanks for coming to the Apple Support Communities!
    Cheers,
    Braden

  • Portal Run time error after deploying custom logon page par file in portal

    Hi Experts,
       We have customized the standard portal logon par file for client XYZ and imported it with the same name (com.sap.portal.runtime.logon.par)  in portal.
       It is working fine for XYZ . And another client ABC wants the same customization for them also. So we took the par file from XYZ and imported it in ABC system. But in ABC system, we are getting Portal Run time Error. When we checked the logs, it is showing error in LogonBean class.Wwe have included the necesary jar files. Could anyone help us in identifying what is missing?
    Thanks
    VJ

    Hello Vijay,
    Please paste or attach the error log.
    Regards,
    Haseena

  • 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.

  • 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

Maybe you are looking for