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

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

Runtime 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

Please note the error details
Runtime Errors         SYNTAX_ERROR
Date and Time          07.01.2010 17:43:06
Short text
Syntax error in program "RK2LSFOC ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RK2LSFOC " in include "RK2LSFOC
" in
line 128:
"No component exists with the name "KWBRUM". ."
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 "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RK2LSFOC ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program RK2LSFOC :
"No component exists with the name "KWBRUM". ."
|    " "

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

Error while create sales order

Hi,
Please help.
I am facing error while create sales order.
No item category available (Table T184 OR VERP )
Message no. V1320
Diagnosis
No item category could be determined for the combination OR VERP .
System Response
The system does not allow further processing of this item.
Procedure
Check the entries in table T184 by means of which item category determination is controlled.
If you do not have the authorization to do this yourself, contact your system administrator.

Hi,
Check in spro whether Item categorygroup VERP is assigned to sales document type.if not assign.
Path
SPRO-SD-sales-sales douments-sales document item-assign item categories.

End of Valid Logistic Calender error while creating Sales Order

Hi,
While creating Sales order in VA01 the following error message comes for particular material code for a particular site only:
24.01.2202 date comes after end of valid logistics calendar. (Please
correct)
Message no. 61062
Can anyone suggest on the same.
Regards
Nilofer

Hi,
The input value given in Sales order is " Req Delivery date: 31.03.2012", but the error comes with the below date such as
"24.01.2202 date comes after end of valid logistics calendar.(Please correct)"
We also face one more error such as
" Incorrect index structure for table XMVERF_POS/0000224110/000040 ".
From where system is taking 24.01.2202 date?

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Hi error while creating sales order

hi
i am getting 'not able to save' message while i am creating sales order.
how should i proceed to know where is the problem???
i tried debugging but it is taking lots of time, is there any other way i can know the reason for this error in standard code.
there is no wrong data entry while creating sales order.
i just want to know what are the ways to know where is the problem in the standard code.
thanx
rocky

hi ,
try too create a sales order after that check transaction code ST22 U WILL FIND AN SHORT DUMP then check in the source code extract an pointer will be visible where the error is coming and it will also show the program name , please read the dump analysis care fully
srinivas

Error while creating sales order

while creating sales order for a particular plant there is error coming
NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
PLANTXVBAK-VKBUR.
Intailly I have check the no series we have internal no series for all plant,the
number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
kindly guide me for the same.

Hi Sanjay
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key Start Number range End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0
The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
Regards
Naren

While creating Sales order in Va01 runtime error

Hi friends,
While i am creating sales order in VA01 i am getting runtime error
Thanks in advance
venuprasad

This could be due to some recent code changes in SAPMV45A...may be some user exits...
The Dump which is obtained can be analysed by an ABAP person and could lead you tot he right issue.
Hope this helps
Regards
Biju

Error while creating sales order in ECC 6.0

Hi All,
I am creating sales order through VA01.
Error comes As "Repairs processing with cost management only for the main item"
The material which i am using is finished goods.

Dear Akilesh,
Just check whether the material - in MM - material type whether the Qty and value update has been ticked.
What order type you are using and what is the item category you are using?
Kindly let me know that also
Regards,
Sudhir

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 in VA01

Similar Messages

Maybe you are looking for