Dump occured in standard program SAPMV45A (order creation)

hi,
In order creation, a dump is occured in standard program SAPMV45A. Because of in FM "Pricing_Dialog_Tabstrips" is incorrect and TAXI_TABSTRIP_C and TAXI_TABSTRIP_ITEM" specified here is a different field type.This is standard program we can not change field type. Kindly provide any OSS notes for this or any other solution.
STANDARD PROGAM - SAPMV45A
INCLUDE PROGRAM - MV45AF0F_FCODE_PKO4
ERROR - Runtime Error CALL_FUNCTION_CONFLICT_TYPE has occurred
Kindly help me, Its very uigent
thanks in advance.

hi
Please note SAP  redesigned the condition screen and it's
underlaying logic completely starting with release 4.6A.
Hence you should not use the function codes PKON and KKON any longer.
Furthermore screen 6201 and all includes stored in program pool SAPMV61A
are not used by the standard any more. The new condition sub-screen
is placed in program pool SAPLV69A and triggered by function
codes KKO1 (= jump into header condition screen) or PKO1 (= jump into
item condition screen). Further details you can find in the SAP
note 360942.
So, In release 470 & above , function code PKON to display the conditions in a
sales order via VA01, VA02 and VA03 may lead this short dump. To avoid
this short dump, I recommend you to use the function code PK01 instead
Hope this helps
Paul Quinn

Similar Messages

  • Runtime error in Standard program "SAPMV45A"

    Hi Expert,
    i am getting problem in BDC , While creating the (sales order) VAO1 ,dump is occurs in standard program SAPMV45A. Because of in FM "Pricing_Dialog_Tabstrips" is incorrect and TAXI_TABSTRIP_C and TAXI_TABSTRIP_ITEM" specified here is a different field type.This is standard program we can not change field type. Kindly provide any OSS notes for this or any other solution.
    STANDARD PROGAM - SAPMV45A
    INCLUDE PROGRAM     - MV45AF0F_FCODE_PKO4
    ERROR  - Runtime Error CALL_FUNCTION_CONFLICT_TYPE has occurred
    Kindly help me, Its very uigent
    Thanks & Regards
    Md.MahaboobKhan

    Hi Archana ,
    Check is there any Inactive Versions in ur Systems ?
    useful tcodes are SPAU /SPDD for tables
    Regards
    prabhu

  • To find error message in the standard program sapmv45a

    Hi friends,
    I have a following senario.
    Iam getting the following error mesage.
    INFO RECORD FOR VENDOR 'ABC' AND MATERIAL '00000678' DOES NOT EXIST.
    now my requirment is i should find from were this error message is being triggered.
    actualy my problem is its in production server i dont have the acess to debug it.
    even i dont have the mesage classs and mesage number also.
    How can i catch this error mesasge from the program code
    ie :  by checking the code of the program SAPMV45A
    Regards
    Priyanka.

    I got that mesage from ME13 tcode.
    now my requirement is
    in the line item i have material number '000000678'.
    now the end user is chaning tht material number ie : he is chaning from '000000678' to ' 000000600'.
    now for the ist material 000000678' the info record is maintained .
    but for the changed material  000000600' the info record is not maintained. so iam getting the error mesage as below.
    INFO RECORD FOR VENDOR 'ABC' AND MATERIAL '000000600' DOES NOT EXIST.
    Now my reuiremnt is i should skip this error mesage even when the material is changed ( ie if the info record is not maintained )  .
    ie :  it sholud allow me to process the flow of va01 tcode
    How can i do that.
    or is there any other solution for that.
    Regards,
    priyanka.

  • Bapi or standard program

    helllo
      can anybody help me out in  finding a bapi or a standard program for the creation of actual assessment cycle (i.e. transaction:ksu1/ksu2)
    regards
    anik

    Hi,
           Hi,
    There are couple of RFC for the creation of allocation cycle :-
    KGAL_RFC_CREATE_CYCLE
    KGAL_CREATE_CYCLE
    Cehck out they use same table T811c.
    might be useful.
    or else if possible use user exit..
    SAPLKAL1
    SAPMKAL1
    SAPMKGA2
    <b>Reward points</b>
    Regards

  • Getting dump error in Sales order creation mode while going to item texts

    Hi,
    I'm getting an ABAP dump error while going to item text tab in the creation mode of a sales order. This issue is happening only when we make a manual entry in the item text field for a particular text type Y011 in the preceding document of the sales order. Otherwise everything is working fine.
    When I checked the settings in SPRO under SD - Text Control - Sales Doc - Item, the definition and assignment for the TEXT type Y011 is maintained correctly. Not sure why the issue is happening only with this text type.
    Please assist. Thank you
    Taiseer

    Thank you for the reply.
    We had tried this already. However, since the error is with standard program with many function modules. They are finding it difficult.
    There is strange side also for this error that I missed to update. When I replace the Text Id Y011 with a new one it is taking me to the line item text tab with out any error even though I'm using the same access sequence and other settings. However, after saving the order and displaying the order number, immediately it is going to dump again.

  • Short dump in standard program

    Hi Friends,
    below description is short dump for standard program.
    Please see the below and help me how to correct the program.
    The current application triggered a termination with a short dump.            
    What happened?
    The current application program detected a situation which really             
    should not occur. Therefore, a termination with a short dump was              
    triggered on purpose by the key word MESSAGE (type X).                      
    Error analysis
    Short text of error message:                                                  
    Internal error: Program   , include   , form   .                                                                               
    Technical information about the message:                                      
    Diagnosis                                                                    
         An unexpected error has occurred.                                        
    Procedure                                                                    
         If you can reproduce the error, contact the SAP Hotline quoting the      
         error number.                                                            
    Message classe...... "GR"                                                     
    Number.............. 214   
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.       
                                                                                    You may able to find an interim solution to the problem                       
    in the SAP note system. If you have access to the note system yourself,       
    use the following search criteria:                                                                               
    "MESSAGE_TYPE_X" C                                                            
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"                                     
    "F80_FILL_COL_TAB"                                                            
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                               
    Thanks & Regards,
    Sree
    Edited by: adepus on Oct 7, 2009 12:39 PM
    Edited by: adepus on Oct 7, 2009 12:39 PM

    Hi Clemens,
    I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
    Runtime Error MESSAGE_TYPE_X
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Internal error: Program , include , form .
    Technical information about the message:
    Diagnosis
    An unexpected error has occurred.
    Procedure
    If you can reproduce the error, contact the SAP Hotline quoting the
    error number.
    Message classe...... "GR"
    Number.............. 214
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
    "F80_FILL_COL_TAB"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    Source Code
    79 MESSAGE x214.
    80 ENDIF.
    81 PERFORM e08_read_object_index(sapfgsb0)
    82 USING fcolumns-dim_index.
    83 IF c-subrc 0. MESSAGE x214. ENDIF.
    84 c_dsentry = c-tval-from.
    85 IF c_dsentry '='.
    86 READ TABLE data_fields BINARY SEARCH
    87 WITH KEY tab = rep_table
    88 dsentry = c_dsentry.
    >>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
    90 ENDIF.
    91 WHEN OTHERS.
    92 c_dsentry = '*'.
    93 ENDCASE.
    94 ENDIF.
    Regards,
    Pavan

  • Error in Standard Program for Purchase Order

    Hello Everyone,
    I am getting an ABAP Dump Error while Displaying & Printing Purchase Order using TCODE : ME9F & ME23N.
    We have applied new Patches.
    for Logistics it is 26 & ABAP it is 58.
    I am getting Error in standard INCLUDE
    Program : LMEDRUCKF1K at line 64.
    The Error is :- "Field "ENJPREVIEW" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement."
    Declaration for "ENJPREVIEW" is also available in
    include LMEDRUCKTOP. still it gives an error.
    These lines of code is included by SAP note 855263.
    Before applying these Patches it was working properly, but now it gives an error.
    Please , Can anyone give solution for this.
    Regard's
    Archana.

    Hi Archana ,
    Check is there any Inactive Versions in ur Systems ?
    useful tcodes are SPAU /SPDD for tables
    Regards
    prabhu

  • Standard form for payment order creation

    Hi,
    I got a requiremnt to create a form for payment order creation,
    can one plzzz guide me, do v hav any standard form available in sap, n also let me know the program for it.
    Regards
    ashwini

    Hi Aswini,
               FPY1_CH_DTA_EZAG
    FPY1_CH_DTA_LSV
    FPY1_DE_DTA
    FPY1_DE_DTA
    FPY1_DE_DTAZV
    FPY1_DE_DTA_ZZV
    FPY1_DE_DTA_ZZV
    FPY1_DE_EURO
    FPY1_DE_EURO
    FPY1_FR_BANQUE
    FPY1_NL_DTA
    FPY1_NL_DTA
    FPY1_NZ_MTS
    FPY1_NZ_MTS
    check these forms
    Regards,
    Venkat

  • Sales order creation, standard event trigger is taking long time .

    We have a requirement where we are sending data to CRM system using RFC function module. This data is sent while sales order creation or change. We have used standard event BUS2032.CREATED to trigger CRM FM in sales order creation mode. In sales order change mode, we are using custom event. In production system, our custom change event is getting triggered fine and data is sent to CRM system with small time lag of around 1 minute. But, while sales order creation, standard event trigger is taking long time ( sometimes about 20 minutes) in production system.
    We tried triggering same custom event at the time of sales order creation using FM u2018SWE_EVENT_CREATE_IN_UPD_TASKu2019 as well but, still we are not able to improve performance of the event trigger at sales order creation.
    Regards,
    Sushee Joshi

    HI,
    we have written SWE_EVENT_CREATE in update task
    I think instead of calling in update task simply call to function module CALL FUNCTION "SWE_EVENT_CREATE" might trigger the event immediately.. Did you try to check in this way..
    OR
    And I also suggest you to check the entry in SWE2 txn with respect to your workflow tempalte, may be you have enable the option ENABLE EVENT QUEUE, this could be one of the reasons.. If it is enabled please disable it (uncheck)
    Please check..
    Regards
    Pavan

  • Standard program for unbilled  sales orders and purchase order items

    Can anyone advice,  is there any standard program which gives the unbilled sales order and purchase order items.

    Hi,
    Use the T.Code VA05/VA05n for list of all the sales order s which are open.
    Take T.Code:VA05N
    Select the option "Open Sales Orders".
    Execute.
    It will give you all the orders which are open.
    The standard program for this is:"SD_SALES_ORDERS_VIEW".
    The same you can also get by using the T.Code VF04.
    In this if your scenario is "Order related",then select the option "Order related".
    Else if it is "Delivery related",then select "Delivery-related".
    Execute.
    The standatd program for this is:"SDBILLDL".
    T.Code:VF05/VF05n is for list of billing documents.
    Regards,
    Krishna.
    Note:Pls search the forum.

  • Error while submitting standard import purchase order program

    Hi,
    iam submitting Standard import purchase order concurrent program, iam getting
    error in view - output like
    Enter value for 12: EXEC FND_CONC_STAT.COLLECT;
    Enter value for 14:
    in view-log like
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 10451963
    can any one help me?
    Regards
    Bhaskar

    Please paste the code here.. there may be some parameter issue while submission.

  • Purchase order need to add to Standard program

    Hi Folks,
    i have standard program RFDEPL00, i have to copy this one into Zprogram and need to add the purchase order number and text into the output display(purchase order number will take from VBAK-BSTNK),
    could any one help me how to bild the logic for this and where to build?
    thanks in advance

    In include program FDEPL00_SHOW line 18, call the alv function module.The out put internal table is gt_data.I think you can debug the program and add find the right position to add new field to the gt_data table.
    But i found include program FDEPL00_READ use LDB method to get the vendor information.So i think it is not very easy to add code in FDEPL00_READ.
    Maybe you can add code before call alv function.
    Regards Chris.

  • Standard print program for order confirmation

    Hi All,
    I have created smartform for sales order confirmation,now i want to attach it to output type i need standard print program for order confirmation.Do we have any standard program for the same ?
    Thanks in advance
    Shrila

    Hi Shrila,
       refer to the thread below:
    Order confirmation  smartform
    With luck,
    Pritam.

  • Dump on running copied standard program ( FAGL_FC_TRANSLATION )

    Dear Gurus,
    i copied everything form the standard program ( FAGL_FC_TRANSLATION ) without changing anything in the same client. when i ran the z program it gave me dump.
    Thanks in advance.
    Regards,

    Hi Devendra Sharma,
    What error/dump you are getting ? please be more specific about the problem.
    For me it's working fine.
    Do as below.
    Go to SE80
    Repository Browser
    Programs
    FAGL_FC_TRANSLATION
    Now right click here(on FAGL_FC_TRANSLATION Folder) and select COPY.
    give it a name like ZFAGL_FC_TRANSLATION.
    Select all Check boxes.
    Press Enter.
    Save it in local object or Package.
    Right click there and press Activate there and make sure all the object are activated under the program.
    Hope it will solve your problem..
    Thanks & Regards
    ilesh 24x7
    ilesh Nandaniya

  • Dump during sales order creation for a config material (uding order BOM)

    Dear all,
    I am getting the following error during sales order creation for a configurable material
    When I click on 'Engineering' tab in the characteristics value assignment for the parent material i.e. sales order material I get dump with following message,
                                   'Field symbol has not yet been assigned'
    Thanks,
    Yogesh

    Yogesh,
    what was the problem ?
    Thanks,
    Pavan Verma
    Edited by: Pavan Verma on May 11, 2010 9:31 AM

Maybe you are looking for