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

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

Error while saving sales order

Hi I am encountering below error message while saving sales order:
Warehouse
Specify export data in material master
Then I go to material master to check foreign trade export tab, and I had maintained commodity code export group, country of origin and region of origin, what did I miss? Help.

Hi,
Check whether you have activated legal control data for the Sales Order type configuration in Foreign Trade.
If the Order type is activated then the following error message can pop up unless you maintain in material master.
See whether export legal control data is activated or not for the order type.
In IMG Sales and Distribution>Foreign trade>Legal control section
Regards,
Saju.S

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

After CIn configuration when i raise the sales order i cannot save it. when i click on the save icon the following runtime error message x302 (v3) with the short dump.. pls guide..
thanks...

Hi sanjitdutta,
Please get in touch with your ABAP team to know wat exactly is teh cause for the short dump. Please post the error description completely.
Thanks
Arun
Edited by: arun subramani on May 16, 2011 7:06 AM

RUn time error while saving po    Field symbol has not yet been assigned.

Hi Experts,
I am getting abap dump while saving PO in ME21N plz seee the below dump plzzzzzzzzzzzzzzzzzzzzz help me
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          19.06.2009 11:24:46
Short dump has not been completely stored (too big)
Short text
     Field symbol has not yet been assigned.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLKKBL" 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
     You attempted to access an unassigned field symbol
     (data segment 106).
     This error may occur if
     - You address a typed field symbol before it has been set with
       ASSIGN
     - You address a field symbol that pointed to the line of an
       internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
How to correct the error
    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:
    "GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
    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.
em environment
SAP-Release 700
Application server... "gplqty"
Network address...... "128.12.0.19"
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... "GPLQTY"
Database type..... "MSSQL"
Database name..... "GPQ"
Database user ID.. "gpq"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 4 2008 02:33:25"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 172
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...... 16759360
Heap.... 0
Page.... 237568
MM Used. 12036016
MM Free. 530432
er and Transaction
Client.............. 410
User................ "SAP_SUPPORT"
Language key........ "E"
Transaction......... "ME21N "
Transactions ID..... "9E955CDE97CBF1648B4C001A64C7B85A"
Program............. "SAPLKKBL"
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where terminated
    Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
    The main program was "RM_MEPO_GUI ".
    In the source code you have the termination point in line 2908
    of the (Include) program "LKKBLF99".
Source Code Extract
Line SourceCde
2878       else.
2879         assign <fs11> to <field>.
2880         gs_fc = gs_sfc11.
2881       endif.
2882     when 012.
2883       if gs_out_flags-slave ne 'X'.
2884         assign <fm12> to <field>.
2885         gs_fc = gs_mfc12.
2886       else.
2887         assign <fs12> to <field>.
2888         gs_fc = gs_sfc12.
2889       endif.
2890     when 013.
2891       if gs_out_flags-slave ne 'X'.
2892         assign <fm13> to <field>.
2893         gs_fc = gs_mfc13.
2894       else.
2895         assign <fs13> to <field>.
2896         gs_fc = gs_sfc13.
2897       endif.
2898     when 014.
2899       if gs_out_flags-slave ne 'X'.

Hi,
this error occurs when you try to address a field-symbol before it has been assigned to a field or
the assignment has failed.
Use following code to remove this dump
Assign <mara-matnr> to <fs>.
if sy-subrc <> 0.
Error Message.
Endif.
Hope it helps,
Raj

Mobile Sales - Error while Saving Sales Order

Hi,
When I try to create and save a sales order in the Mobile Sales, the error message UI_CONT_STATUSBAR_ICON_TT is displayed, blocking the saving process and the new order is not saved.
I tried to debug the SAP Mobile Application Studio(Visual Basic) side and I didn`t find any error there.
Does anyone knows what could be happening?
Thanks for any help.
Regards,
Andrew

I reinstaled the Mobile studio and then it worked.

Run time error while saving migo

Dear All,
I am doing the subcontracting process. and while saving the MIGO it shows Runtime Error.
Error analysis
    Short text of error message:
    No taxes on sales/purch.are allowed for account 428304 BS70, V0 is not a
    llowed
    Technical information about the message:
    Message classe...... "FS"
    Number.............. 217
    Variable 1.......... 428304
    Variable 2.......... "BS70"
    Variable 3.......... "V0"
    Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name                             MB_POST_GOODS_MOVEMENT
BS70 is a company code.
Please help me out.
Thanks & Regards,
Sandeep Patil.

Dear All,
i have done that but now another error is coming as
Error analysis
    Short text of error message:
    Balance in transaction currency
    Technical information about the message:
    Message classe...... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 5.000,000"
    Variable 3.......... "INR"
    Variable 4.......... " "
5.000,000 is my po value.
Thanks & Regards,
Sandeep.

Run time error while saving values in File (Tcode)

Hi,
I am using FM   call function 'FILE_GET_NAME'
       exporting
            logical_filename = logical_filename
            parameter_1      = program_name
            parameter_2      = file_id_param
       importing
            file_name        = physical_filename
       exceptions
            file_not_found   = 1
            others           = 2.
for this I am trying to maintain dynamic values(field symbols) in Tcode FILE Logical file name definition , physical path as.
Physical file   =<PARAM_1>.<PARAM_2>
But while saving it dumps, saying filed symbol assinment to substring is not allowed.
Physical path for the same is /<V=Z_DIR_MAIN>/<SYSID>/<V=Z_DIR_OUT>/<FILENAME>.<CLIENT>.<DATE><TIME>.
Regards
Mohinder Singh Chauhan

Hello Mohinder,
the better way to analyse these kind of things is by entering the function module in se37 and providing the required test data.
In your scenarion as you say its throwing a runtime dump related to field symbols better you concatenate the data param1 and param2 into a new variable and then pass that value into the function module.
Thanks,
M.Naveen kumar

Run time error while saving the production order in CO02

HI Experts,
While i am releasing and saving the production order the system is giving the runtime error. Please help.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SLD_API_EXCEPTION
Error analysis is
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SLD_API_EXCEPTION', was not
caught in
procedure "GET_ACCESS_DATA" "(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:
Internal error in method
A Quick response is required.
Regards
Dinakar Sarma

Hi,
Please check below link for your issue , it may useful
http://forums.sdn.sap.com/thread.jspa?messageID=10815298#10815298
Regards,
Ram

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

Run time error while closing the CRM Order using BAPI

Hi Experts,
Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
For the custom program we will give input as the order number and execute it, this will close the order.
Here close the order means assigning it to Close status as well assign the reason code.
We have created some reason codes for closed status.
So when the program is run the Order moves from resolved status to closed status along with reason code.
But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
Please find my code which have used in the custom program
Closing the resolved SOs in the system
    CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
        EXPORTING
          objnr                     = iv_guid
          user_status          = lc_status_closed
       EXCEPTIONS
         object_not_found          = 1
         status_inconsistent       = 2
         status_not_allowed       = 3
         OTHERS                        = 4.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining status'.
    ENDIF.
Set reason code
build lt_subject
    ls_subject-ref_guid = iv_guid.
    ls_subject-katalogart = 'A2'.
    ls_subject-codegruppe = 'ZR000003'.
    ls_subject-code       = 'ZR33'.                      " Reason code
    ls_subject-mode       = 'A'.
    APPEND ls_subject TO lt_subject.
build lt_ossset
    ls_osset-ref_guid        = iv_guid.
    ls_osset-subject_profile = 'ZREASON03'.
    ls_osset-profile_type    = 'G'.
    ls_osset-subject         = lt_subject.
    APPEND ls_osset TO lt_osset.
build lt_service_os
    ls_service_os-ref_guid = iv_guid.
    ls_service_os-ref_kind = 'A'.
    ls_service_os-osset     = lt_osset.
    APPEND ls_service_os TO lt_service_os.
build lt_input_fields
    REFRESH: lt_input_fields, lt_field_names.
    CLEAR : ls_input_fields, ls_field_names.
    ls_field_names-fieldname    = 'CODE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'CODEGRUPPE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'KATALOGART'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'SERVICE_PROFILE'.
    APPEND ls_field_names TO lt_field_names.
    ls_input_fields-ref_guid    = iv_guid.
    ls_input_fields-ref_kind    = 'A'.
    ls_input_fields-objectname = 'SERVICE_OS'.
    ls_input_fields-field_names = lt_field_names.
    APPEND ls_input_fields TO lt_input_fields.
     CALL FUNCTION 'CRM_ORDER_MAINTAIN'
      EXPORTING
        it_service_os     = lt_service_os
      CHANGING
        ct_input_fields   = lt_input_fields
      EXCEPTIONS
        error_occurred    = 1
        document_locked   = 2
        no_change_allowed = 3
        no_authority      = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining reason'.
    ENDIF.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        it_objects_to_save   = lt_header_guid
        iv_update_task_local = lv_update_task_local
      IMPORTING
        et_saved_objects     = lt_saved_objects
      EXCEPTIONS
        document_not_saved   = 1
        OTHERS               = 2.
    IF sy-subrc <> 0.
      WRITE : 'Error at saving'.
    ELSE.
      WRITE : 'Successfully Closed'.
      COMMIT WORK AND WAIT.
    ENDIF.
Run time error is coming at COMMIT WORK AND WAIT statement.
Please let me know any corrections are required in the above program.
When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
Kindly provide your feedback.

Hi Dinakar,
You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
Regards - Pawan

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

Run time error while saving sales order

Similar Messages

Maybe you are looking for