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.

Similar Messages

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

  • 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

  • In MIGO against Scheduling agreement for Consignment error

    Dear SAP Gurus,
    I m getting abn error in MIGO for SA
    "Maintain pricing conditions for the material for the excise invoice date"
    vinod

    >
    GSMY Volvo wrote:
    > Hello,
    >
    > We want to receive material against delivery schedules of Scheduling agreement.
    >
    > Our setting are.
    > No MRP
    > Delivery schedules are created manually.
    > No confirmatin control.
    >
    > Issue is, delivery schedules are future date but i want to make MIGO today without changing the delivery schedules in ME38.
    > Is it standard SAP setting that we will not be able to receive the material for future dates ? or is there some setting in background ?
    >
    > Sundar
    Its standard SAP setting that migo cannot be done with delivery in future dates. To do migo, change the delivery schedule to today's date and then do the GR against the SA.

  • Consignment Error

    Dear All,
    I am posting goods issue in T.Code MB1A given 201K M.Type , initially i got an error as Acct. Det. for entry INT GBB RHII VBR IIII not possible in OBYC T.code i cleared it & saved the changes.
    Now in T.Code MB1A i have given the details & iam getting the below error when saving it:
    "Document Number 0IIL 101 2008 was already assigned"
    How to clear this error?
    Would be very much thankful to you all if this is solved.
    Vineeth.

    dear ramesh,
    I know that the T.code is OMWN. As far as i know here we should not do any changes because their are no new entries & no provision to copy. Here for M.Type 101 special stock indicator "K" is not maintained. How do i proceed further.
    regards
    vineeth

  • Error of Excise Invoice in Consignment Issue billing document

    The usual process of billing from excisable unit (with CIN) is as follows:
    1. VA01 >2.  VL01N(PGI)> 3. VF01 (Proforma Inv) --> 4. J1IIN (Excise Inv) --> 5. VF01 (Comm Inv)
    While in non-Excisable unit the 3 & 4 steps are not required.
    In Consignment Fill-up- The process is only upto Generation of Excise Invoice and order processing is complete. Excise Invoice in this case works as Excise Gate pass- just to let the material out of factory gates and no sales is booked.
    Further, In consignment issue- the process should be like non-exciseable unit i.e. 1, 2 & 5 step only. While we are getting the error is coming at step no 5 (Excise Invoice no is missing !)
    One more thing I want to ask:
    During Consignment fill-up, movement type 631 is used - which removes the stock from storage location and put it in 'Consignment stock in the same plant. Now since the plant is declared as excisabel, probably it is asking for 'Excise invoice'. It means, there is one more step of material movement, before 'Issue' order- what could be it ??
    Please help.
    Praveen Singh

    The correct process in consignment fillup process is
    a)  Create fillup Order (order type KB)
    b)  Create fillup Delivery  (movement type 631)
    c)  Create F8 proforma
    d)  Create Excise Invoice referencing Proforma
    a)  Create Consignment Issue Order (Order type KE)
    b)  Create Issue Delivery (movement type 633)
    c)  Create Commercial Invoice (billing type F2)
    In the second stage only, you need to create commercial invoice and not  in the first stage as indicated by you.
    thanks
    G. Lakshmipathi

  • Error while creating Consignment PO

    Dear Gurus,
    I am getting error message as 'Account assignment is mandatory for a material' while creating consignment PO with item category 'K'.Could you please address the problem?
    Note:I have created Material master record and Consignment info record for that material
    Thanks in advance
    Regards,
    Babu

    HI,
    1. Create a Material - MM01(Use stockable material types like ROH,HALB,FERT, HAWA, etc, Do not use consumable Material which is NLAG mat type)
    2. Create a Vendor - XK01
    3.. Create a Consignment Inforecord - ME11
    4. Create a a PR with Item Category K - Consignment
    5. Then assign PR to PO - ME57(PO Creation) Or directly create a PO with reference to PR - ME21N
    6. Release the PO with any release stratergy is there
    7. Recieve the material in MIGO
    8. Transfer material from vendor consignment stock to own stock - MB1B 411 K mvt te.
    9. Consignment Liabilities settlement - MRKO
    This error comes into picture when you use Non-stock material... Avoid using it.
    Or in case if u have to use Non stock material try giving Cost center and GL account in account assignment tab in item details
    Thanks & Regards,
    Kiran
    Edited by: Kiran. V on May 1, 2008 3:50 AM

  • 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 while issuing goods for costcenter from consignment stock

    Hi Experts,
    material is available as consignment stock. Now while trying to issue the consignemtn stock to Cost-center by 201-P, i'm getting the below error,
    pls explain to solve the same
    Fld selectn for mvmt type 201 / acct 40200000 differs for Vendor goods movement (014)
    Message no. M7093
    Diagnosis
    Comparison of the field selection strings from movement type 201 and G/L account 40200000 has revealed that there is an incompatible field selection combination at one or more points.

    Hi
    Please change the Special stock indicator to K & still if you get the error then do as below
    Please do as below
    T.code SE38 Program RM07CUFA,Execute
    Enter movemnt type 201,
    Company code
    G/L account - 40200000
    Execute
    Now change the filed selection from required to optional for the field Vendor goods movement, this field is under field group Materials management.
    This will Make the Movement type & G/L account compatible.

  • Error " M7 185 " consignment stock does not exists with Customer/vendor

    Dear SDN Team,
    The system is throwing the error "Special stock at customer/vendor 3000000001 does not exist (Notification E M7 185) .
    The consignment Process has been sucessfully maintained correctly with the customer/vendor in ECC system ,but the CRM system is but not able to recognize that the stock is available and throwing the error "Special stock at customer/vendor 3000000001 does not exist (Notification E M7 185).
    kindly suggest.
    Regards
    M.R.Reddy

    Hi Mirja,
    have you gaines any solution for this issue. I am currently facing the same problem and have no idea how to solve it
    Thanks
    Matthias

  • 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

  • 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

  • GRN error for Consignment PO

    Hi,
    I have created consignment info record and created consignment PO.
    but at the time of GRN I am getting the error " the purchasing info record not created for Purchase organisation"
    message no M7 165..
    Why I am getting the error even after maintaining the Info record.
    thanks in Advance

    also check whether the Consignment info record is created for Standard Purchase organisation ?
    If not created the same under Standard Purchase organisation .

  • Error in Vendor consignment return PO.

    Dear MM experts,
    I'm creating a vendor consignment return PO but there's an error message " Return with SD delivery not possible for consignment items". Kindly assist which config that I'm missing out.
    Regards,
    DSingh.

    Hi,
    If you want to return the material without using the SD delivery but still use return PO then in OME0 maintain the message 640 appl area ME to warning message or switch off.
    Then you will be able to create the return PO.
    Then go normal GR against This PO.
    If you need to create the delivery in SD module then you have to use Return delivery process (MBRL)
    Please refer these links too.
    Return Consignment with return PO
    Return with SD delivery not possible for consignment items
    Please let me know if you have any issues.
    Regards
    Shalesh

Maybe you are looking for

  • Video playback on pc

    Can anyone let me know how to convert my videos on my 6300 to playback on pc/facebook

  • MRNB- Revaluation with Logistics Invoice Verification Vendor wise

    Dear Experts, As per SAP standard MRNB transaction is vailable for Revaluation of Purchase Order Price changes. My requirement as below: We are manitaining Purchasing Info Records compulsory. when purchasing rate changes, we are changing Info Records

  • SOL10-6-06 Jumpstart question

    Adding 10-6-06 to our existing Sol10 JS server, have mounted all .iso's lofi and run add_to_install_server for iso's 2-5 to the correct directory, but the jumpstart still stops and asks me: Starting Solaris Install Launcher in Command Line Mode. Plea

  • IAS Policy with Pix

    I have a pix 501, with vpn users authenticating off of MS 2000 IAS. Works great although I want to filter a few users to only be able access a couple PC's when they come in through the pix. I created a new group on NT called Vendors, added the users

  • SSM 7.0 End User Guides

    Are there any SSM end user guides out there?  I've seen the installation and configuration guides, but are there any other documents out there geared more towards the functional components of SSM (e.g., home page functionality, navigating through sco