Error in PR, RFQ & PO

Hi,
When I create either PR or RFQ or PO and save it, I am getting an error "Express document Update was terminated received from author SAPUSER" and the PR or RFQ or PO is not getting created.
The complete details of the error is:
Update was terminated
System ID.. ECC
Client.. 001
User.. SAPUSER
Transaction.. ME21N
Update Key..18118D8C85EA4E83A8A8D38E736DE0AD
Error Info.. B2 001: Local logical system is not defined.
Please help me to fix this issue.
Thanks in advance

Hi,
Consult with your basis consultant & check assignment Client to Logical System.
For more check SAP Note:614774 & 210919
Regards,
Biju K

Similar Messages

  • Item Category D and Account Assignment F error message in RFQ

    Hi gurus,
    Am experiencing a strange error message creating an RFQ from a Purchase requisition generated by a maintenance order : "Combination item category D/account assignment category not defined".
    The combination Service D/ Order F is actually defined in customizing step : "Define Combination of Item Categories/Account Assignment Categories": The Purchase requisition in indeed created without any problems with this combination of item category / account assignment which is pretty confusing, Is there an specific step for RFQ somewhere ?
    Thks for your feedback !
    Olivier

    Hi
    Check the configuration in the following menu path:
    IMG - MM - Purchasing - RFQ/Quotation - Define document types
    Check the item categories allowed & then select the item category D & check whether you have combination of PR with item category defined.
    Other than this I do not think there is any other specific combination.
    Remember that in RFQ you don't see the account assignment catgory.
    Regards
    Prasad

  • RFQ Print Out Error

    Hi
    am getting the follwoing error log in RFQ print our
    How to resolve this?
    ABSA     502     Output ignored (requirement 104 not fulfilled)
    MAHN     502     Output ignored (requirement 103 not fulfilled)
    NEU     541     Output found
    Vijay

    Vijay,
    did you try looking up the access sequence for ABSA and MAHN, the condition tables associated with the access sequence and the fields in the condition tables? Are all the fields that are required for the message to be fulfilled being available during message processing?

  • Printing PO

    Hi,
    When I try to run Printed Purchase Order(Landscape)Report to get the Printout, it ends in Error.
    When checked log file it says
    ERR REP-0450: Unhandled exception ORA-01403: no data found
    which was raised in a statement starting at line 4 of BEFOREREPORT.
    Program exited with status 1
    The same error occurs for RFQ(Lanscape. Whereas Portrait runs succusfully.
    How to rectify the problem?
    Thanks & Regards
    Sri

    kd

  • Getting error when creating a RFQ in MM module" create rfq item overview"

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue.
    This error i am getting when creating a RFQ in MM module and when trying to save the screen "create rfq item overview" then it gives me a pop up box message " SAP SYSTEM MANAGER: WORK PROCESS RESTARTED, SESSION TERMINATED".
    Here are the details of teh system
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which 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.                                                                               
    Error analysis
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    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.                                                                               
    System environment
    SAP Release.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi Mudessir,
    With the help of ABAP'er try the following.
    1. open the program 'LCLSCF2G' from SE38.
    2. Keep a break point at line no: 131.
    There is 'END SELECT' statement which is getting failed at line no 131 in the program.
    Try to analyse the SY-SUBRC at that point.
    If your technical consultant can't solve this, write to SAP OSS (service.sap.com).
    I have searched SAP OSS, there are other situations, but your case is not there. So write to SAP if technical consultant can't solve it by debugging the program.
    Regards,
    Madhu.

  • At the time of RFQ creation dump error

    Dear All,
                        At the time of RFQ creation one Dump error is coiming... please advise to solve this issue...
    the error message is :
    Runtime errors         SYNTAX_ERROR
           Occurred on     09.09.2009 at   12:10:27
    Syntax error in program "SAPLV61A ".
    What happened?
    The following syntax error occurred in the program SAPLV61A :
    "Incorrect logical expression: Instead of "X" a field, a function or "("
    Error in ABAP application program.
    The current ABAP program "SAPLMEVA" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLV61A ".
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    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.
    Error analysis
    The following syntax error was found in the program SAPLV61A :
    "Incorrect logical expression: Instead of "X" a field, a function or "("
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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.
    System environment
    SAP Release.............. "620"
    Application server....... "ARCHIVAL"
    Network address.......... "172.26.2.145"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 80686"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "ARCHIVAL"
    Database type............ "MSSQL"
    Database name............ "EDP"
    Database owner........... "dbo"
    Terminal................. "cheeid92corit"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Mar 9 2009 22:54:07"
    Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version......... "SQL_Server_9.00 "
    Patch level.............. "274"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 777
    User................ "MMCORE"
    Language key........ "E"
    Transaction......... "ME47 "
    Program............. "SAPLMEVA"
    Screen.............. "SAPMM06E 0311"
    Screen line......... 54
    Information on where terminated
    The termination occurred in the ABAP program "SAPLMEVA" in
    "ME_LOAD_VARIANTS_PRICING".
    The main program was "SAPMM06E ".
    The termination occurred in line 55 of the source code of the (Include)
    program "LMEVAU08"
    of the source code of program "LMEVAU08" (when calling the editor 550).
    Source code extract
    000250       ENDIF.
    000260   *--> Initialisieren
    000270   *--> not necessary anymore (Raimond Buchholz)
    000280   *   CALL FUNCTION 'CUD0_CONFIGURATION_INITIALIZER'.
    000290   *--> Preisteile der Varianten besorgen
    000300       CALL FUNCTION 'CEI0_GET_CONDITIONS'
    000310            EXPORTING
    000320                 INSTANCE    = I_CUOBJ
    000330                 APPLICATION = 'MM'
    000340            TABLES
    000350   *              CONDITIONS  = T_VCKEY.                 "del 194053
    000360                 CONDITIONS  = T_VCKEY                   "ins 194053
    000370            exceptions                                   "ins 194053
    000380                 error_message  = 01                     "ins 194053
    000390                 others         = 02.                    "ins 194053
    000400   *--> Preisteile der Varianten mit Belegnummer versorgen
    000410       LOOP AT T_VCKEY.
    000420         T_VCKEY-KAPPL = 'M '.
    000430         T_VCKEY-VBELN = I_EBELN.
    000440         T_VCKEY-POSNR = I_EBELP.
    000450         MODIFY T_VCKEY.
    000460       ENDLOOP.
    000470     ENDIF.
    000480
    000490   *--> Preisteile der Varianten an Preisfindung übergeben
    000500   *- pricing_load_variant_key muß auch bei Positionen ohne Konfiguration
    000510   *- laufen, da die Logik im PRICING zu 4.0 umgestellt wurde
    000520     IF I_NO_LOAD IS INITIAL.
    000530       DATA: I_POSNR LIKE VBAP-POSNR.
    000540       I_POSNR = I_EBELP.
          CALL FUNCTION 'PRICING_LOAD_VARIANT_KEYS'
    000560            EXPORTING
    000570                 APPLICATION = 'M '
    000580                 VBELN       = I_EBELN
    000590                 POSNR       = I_POSNR
    000600            TABLES
    000610                 TVCKEY      = T_VCKEY
    000620            EXCEPTIONS
    000630                 OTHERS      = 1.
    000640     ENDIF.
    000650
    000660   ENDFUNCTION.
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 1
    SY-FDPOS 1                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY GVP
    SY-UCOMM
    SY-TITLE Maintain Quotation : Item 00001
    SY-MSGTY E                             SY-MSGID AIPLOC
    SY-MSGNO 002                           SY-MSGV1 303632
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Kind regards
    P.Anandhakumar

    Hi Anandhakumar,
    Debugg the transaction with help of ABAPER.
    System will show you the reason for the above error.
    Hope this should solve your problem.
    Thanks and regards 
    Gitesh

  • Error in clicking  preview button in RFQ's

    Hi All,
    Encountered error in clicking preview button in RFQ's.
          Request Failed!
         APP-FND-00296: Cannot submit concurrent request for program SEZCPORFQ
    Check if the concurrent program is registered with Application Object Library.
    Check if you specified the correct application short name for your concurrent program.We define SEZCPORFQ in executable and define in program under concurrent.
    But still, error occur.
    We dont know what to do, any help pls.
    Version EBS: 12.1.3
    Thanks,
    alex

    Hi Alex,
    Encountered error in clicking preview button in RFQ's.
    Request Failed!
    APP-FND-00296: Cannot submit concurrent request for program SEZCPORFQ
    Check if the concurrent program is registered with Application Object Library.
    Check if you specified the correct application short name for your concurrent program.We define SEZCPORFQ in executable and define in program under concurrent.
    But still, error occur.
    We dont know what to do, any help pls.
    Version EBS: 12.1.3
    Thanks,
    alexIs the issue with this specific concurrent program? If yes, what is the difference between this program and other ones which work properly?
    Have you tried to enable trace/debug and see if you get more details about the error?
    Thanks,
    Hussein

  • RFQ Consignment error

    Hi Gurs,
    I am creating RFQ with reference to PR for Vendor Consignment Stock(i.e. Item Category as 'K'), i am getting an error as Field selection PT2A not defined . Can any one can guide me why i am getting this error.
    Thanks in advance..
    Regards
    Jayachandra Prasad.V

    Hi Prasad,
    Do one thing Go to field selection for RFQ through -> SPRO->Material Management->Purchasing->RFQ/Quotation->Define Screen Layout at Document Level.
    Here Select Field selection PT5A or any other available in your system, Press 'F6' or Click on Copy As icon, New screen appears, Change the Name of field selection to 'PT2A' & Description as ' Consignment' & press Enter, you will again come on the main screen,
    Now you do your process of making RFQ through ME41.

  • RFQ Message Error " Not Processed"

    HI
    If the message was processed successfully, the status is set to '1' and if an error occurs, the status is set to '2'. Status '0' usually means that the processing program has not yet been started (if the message is to be processed manually, for example).
    In my RFQ the processing status is "0" means " Not Processed"
    In the msg status a "traingle button" is thr instead of the "Green Button"
    So that we can not able take print out in ME9A also not able see print preview thro ME9A
    How to make this processsed...
    Vijay

    check if the RFQ contain release strategy and alrady released for output.
    you can check the print preivew in ME4N.

  • Error when saving the RFQ

    HI all,
    Iam creating a standard RFQ manually through purchasing>RFQ's and quotations>RFQ.
    But when iam saving the RFQ, iam getting an error like,
    Please enter the required value for the Purchaser's Phone Number segment in the PO Headers flexfield.
    Please help me to get rid of this error.
    with regards
    vijay

    HI sandeep,
    Your reply solved my purpose. Can you also please tell where That particular Flex field is located in PURCHASE ORDERS window.
    Thank you,
    vijay

  • RFQ Message Error

    HI
    I recv the below error when i select a particluar RFQ msg line and i selected the processing log button....
    How to resolve this
    No processing log exists
    Message no. VN052
    Diagnosis
    A processing log could not be found for the selected output.
    Procedure
    Possible reasons are as follows:
    The selected output has not yet been processed
    The processing program did not write a log
    System logging has been de-activated for the selected output type (use settings in Customizing for current application for the selected output type)
    Vijay

    Hi
    All Nace setting were ok here.. we compared the same with diff client server
    But the error i dont know is
    The selected output has not yet been processed
    The processing program did not write a log
    System logging has been de-activated for the selected output type (use settings in Customizing for current application for the selected output type)
    Vijay

  • Runtime errors during RFQ creation

    Hello experts,
    I am trying to create a RFQ for my client. I have provided all necessary information needs to create a RFQ but when I try to execute, I get Runtime error "DYNPRO_NOT_FOUND"
    Can anyone tell me how can I solve this problem. I belive this error related to ABAP program.
    Regards,
    Atul Kumbhani

    Raf,
    Termination occurred in the ABAP program "SAPLXM06" - in "EXIT_SAPLEINM_013".                                   
    The main program was "SAPMM06E ".                                   
    In the source code you have the termination point in line 10                                   
    of the (Include) program "MM06EO0C_CUSTSCR1_HEAD_SET_DAT".                                   
    Regards,
    Atul Kumbhani

  • RFQ error

    Hi Guru,
    I have created an RFQ with status send immediately (when saving the application).  After saving the RFQ, RFQ number was generated, but there's an error in sending fax the error is "
    Error in OPEN_FORM for document 6000000112".
    Please advice it's urgent..
    Thanks in advance.
    Mike

    Dear,
    is SGD is your Currency, if yes then Go to OBBS and maintain M type Currency Convertion then go to the OB08 and maintain Currency Convertion.
    just check it out.
    all the best
    Regards:-
    Poision

  • Release strategy error in RFQ

    Dear MM gurus
    I have maintained all the steps for release strategy for RFQ, while clicking on release flag in ME42 it is giving following error. please guide
    Purchasing document 6000000015 not subject to
    release strategy
    Thanks in advance
    kailash N. thakkar
    9869171090

    Hai,
          Release strategy gets effected when all the characteristics mentioned for the release strategy are complied otherwise the strategy will not affect the RFQ.You might have given any value not relevant to the characteristic.For eg you might have given alower value than the value mentioned for the characteristic RFQ value.
    Regards,
    Gangadhar

  • Error in RFQ Printing

    Hi Friends,
    I am creating a RFQ (ME41) and wants to give print through ME9A, in development server its working fine and i am able to take a print out. But in quality server system is not generating a spool request in ME9A. I have checked all setting in Dev and in Quality server, its same a both places, then why system is not generating a spool in quality.
    Please advice. I have checked Print related config., NACE settings are correct.
    Shrinivas

    Hi
    Please check whether you have Ticked "Print Immediately" in the Q server. If you maintain this, you will get printout.
    Pls Revert and Reward
    Regards
    Vijay

Maybe you are looking for