Purchase Requisitions stuck in CIf with message 181

Hi All,
We have purchase requisitions created in APO on transportation lanes based on external procurement relationships. We have noticed that the requisitions are created in ECC but get stuck on their way back to APO. They appear in /sapapo/ccr with message 181.
Any ideas where we could be going wrong?
Regards,
Zeeshan.

you need to push this Orders in APO through CCR .
some times schedule line are not created/updated in APO so we need to push it through CCR report.
On CCR report screen select all the PO and click on arrow button  send to APO .
Than click on iteration icon .
this will push all PO to APO and will not appear in next CCR run.
If it didn't help please check OSS note :
Note 1152934 - DELTAREPORT:confirmation-error 181 for after return delivery
Note 1131469 - DELTAREPORT: unjustified error 181/183 for confirmation

Similar Messages

  • Purchase requisition still contains items with errors

    DER SIR / MEDAM
    PLEAE PROVIDE ANSWER
    Purchase requisition still contains items with errors
    Edited by: Csaba Szommer on May 1, 2011 6:56 PM

    Hi
    The error message ZPSMSG003    seams to be customized
    Please check for User exit for material compnents COZF*

  • Purchase Requisition Overall Release problem with several CostCenter

    Hello Gurus!!
    I need your comments!!! 
    I define the Purchase requisition as Overall Release, and woks !!  but I have a Issue.
    I have an entry in the CL24N txn as follow:
    AccAssgCat = K
    Plant              = CC01
    CostCenters = 10001
                            10002
                            10003
    totalAmt        = 1USD to 1000US
    So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
    But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
    I assume that as both are into the release strategy the system will take both CC and ask for release!!
    What I can do to fix this situation??

    Dear Marco Antonio,
    I have never faced your issue, but have an idea of what you can do.
    Activate Enhancement M06B0005   EXIT_SAPLEBND_004
    Then in the program zxm06u31 put the following code line:
    e_ceban = i_ceban.
    and also  a breakpoint so that it stops automatically upon PR verification or saving.
    Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
    Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
    I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
    Well, tell me what happens
    Best Regards,
    Sebastián Ligueros

  • Purchase requisition must be create with material codes only

    Hi gays,
    Can u solve my problem.
    We are having  "3 " document types to create purchase requisition.
    3 types are using different depts.
    I need to restrict the 1 document type with material code only they should raise the purchase requisition.
    other 2 types can raise the purchase requisition with or with out material code.
    Please explain how to restrict.

    First check the field selection key assigned for the Document type at
    Spro > MM > Purchasing > PR > Define document types..
    Then Go to
    Spro > MM > Purchasing > PR > Define Screen lay out, here Select the above field selection key & copy it as and make the
    Description field as Display..
    Again go to Spro > MM > Purchasing > PR > Define document types..
    and assign the field selection key for the Document type for which you want the Description field as Display..
    Then Create PR & Check

  • Account assignement category for purchase requisition - error message

    Hi All!
    I created a new Item category in service order (IW31) "O" with the account assignment category "O". If I don't set the Consumption posting indicator to V for this category, when I set the account assignment category "O" to the purchase requisition in <i>Plant Maintenance and Customer Service-Maintenance and Service Processing-Maintenance and Service Orders-General Data-Define Account Assignment Category/Document Type for Purchase Requisitions</i>, I receive the message:
    <b>"Acct. assign. cat. "O" for purchase req. does not exist.
    Message no. CS 075"</b>
    The client request is not to charge immediately for the goods receipt with the relevant costs the service order. The client wants to create the goods receipt in a storage location for the plant and then confirm the components and charge the costs after the component confirmation (movement type 261) - similar to stock material.
    Any idea about what should I do?
    Thank you.

    Hi Everyone,
    The problem is solved now. The cause was that the test requisition that I was making was satisfying more than one rules and hence I end dated the remaining rules which solved the problem.
    Thanks!

  • Purchase requisition with Item Category – L creation via Maintenance orders (Plant Maintenance)

    Hi Guru’s,
    I have a scenario where purchase requisition with Item Category – L (subcontract External) for Repair items (Storeroom Process) need to get generated with Item category-L.This requirement is to MAP in my system.
    I am aware that purchase requisition can be created with reference to maintenance orders.
    Can anybody through some light on the integration between PM and MM.
    If creation of purchase requisition is possible via maintenance orders then please explain me with detailed steps both configurations and master data so that I can able to replicate the same as per business requirement.
    I look forward to the expert’s response.
    Regards,
    Kumar

    Hi Kumar.S
    You have to installed DIMP 6.0, and activated the business function Refurbishment and Subcontracting (LOG_EAM_ROTSUB) and Serial Numbers in Purchasing (LOG_MM_SERNO) .
    Please check the below link:
    http://scn.sap.com/thread/1956895
    Hope it will help you to resolve your issue.
    Regards,
    Ritesh

  • Purchase requisition : problem with check release Strategies

    Hi all,
    i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
    But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
    Is there a special value to give the release indicator 'released' ?
    Thanks for your help.
    Edited by: ToraTora on Mar 31, 2011 5:46 PM

    Hi,
    Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
    select release indicator
    by default, you will be having the following release indicators in the system,
    1     Request for quotation
    2     RFQ/purchase order
    3     RFQ/PO no change of date
    4     RFQ/PO no changes
    A     Fixed RFQ
    B     Fixed RFQ/purchase order
    X     Blocked
    please check whether you have got these or else create and then assign them to the release strategies.

  • Purchase requisition with MRP controller

    Hi everybody, I need support because I have to control during purchase requisition to block users with specific MRP controller.
    I mean, user A only have permission to create purchase requisition with MRP controller Z and user B only have permission to create purchase requisition with MRP controller Y.
    Thanks for all the ASAP cooperation.
    Regards.

    Hi Mitra,
    You will find your answer here.
    MRP controller for PR document type
    Do let me know if it helped, as I might have to explore this option for an upcoming requirement.
    Thanks
    Shailesh

  • ME59N .PO with Purchase requisitions

    Hi MM Experts,
    I am trying to create PO with Purchase requisitions  Document Type ZNB  with using T -code Document Type ZNB the Purchase order not creating with ZNB type PO.  its creating with standard NB  type PO. my requirement is to be created with ZNB.
    is there any customizing to do this.
    Thanksin Advance,
    Anthyodaya.

    Hi, thank u very much..  Danken......
    for u more 10 points...  
    i posted another question about the  . 
    as u posted u r ideas but i can not reach my client requirements.
    is there any CHICK MARK for the all the PO  for all the line iteams  for CONFORMED.
    2,   is there any single date for the PO all item levels
    3,how to enter alll the item level conformation date automaticalley (when we have same date for all item levels)
    When the purchase having 40 to 50 line items its dificult to enter each one line item conformation date.
    is it possible any option for all the PO with one CHICK mark for conformation. or any option for one date for all the PO LINE ITEMs . is there standard customizing or any BADI or USER EXIT
    Regards,
    Anthyodaya.

  • Doc. type/item cat.not picking from Purchase Requisition

    Hi,
    While making purchase order from link with Purchase Requisition, system provides the error message :-
         Doc. type/item cat. ZSUP/ (requisition) <-> ZSUP/ (purch. order)
         Message no. 06054
         Diagnosis
         Purchase requisitions of document_type ZSUP or item category  may not be assigned to purchase orders of document type ZSUP or item category .
         Procedure
         Check your input.
         If the problem cannot be resolved in this way, contact your system administrator.
         The latter can make the necessary settings using the Implementation Guide (IMG)
    Kindly provide your suggestion how to make PO without account assignment.
    Regards,
    Satheesh K

    Go to the path OLME-Purchase Order-Define Document Types
    Here select the document type ZSUP and press Allowed item categories
    Check here the standard item category is allowed or not. If allowed, then select the standard item category and press Link purchase requisition - document type
    Then click new entry, Select document type ZSUP and then press enter
    You will see the below screen
    Then save your entry and try again create PO.

  • AME for Purchase Requisitions

    Hello All
    I am in the process of setting up AME in R12.1.2 for purchase requisitions and got struck with an issue
    My requirement is to route the requisition to a particular job based on the item category and the requisition total. I setup conditions, action types and approval groups and then the rule.
    When I used static in my Approval Group setup it works fine with out issues however we do not want to use static as employees keep changing and want my approval driven out of the job hence updated the approval group to use Dynamic usage type and used the below query to pick the name of the employee based on the job.
    select papf.full_name from per_all_assignments_f paaf, per_all_people_f papf, per_jobs pej where
    paaf.person_id = papf.person_id
    and sysdate between paaf.effective_start_date and paaf.effective_end_date
    and paaf.job_id = pej.job_id
    and pej.name like 'IT.Group IT Operations Manager.Staff'
    Now when trying to create a requisition it shows up a message that "Approval List could not be generated. Please contact your System Administrator to review AME rules setup."
    When validated the above query it says query is valid but still not working. I even tried with person_id but still no luck
    Thanks a ton in advance
    Regards
    Dilip

    Hi Dilip,
    Pl. visit following links.
    AME for iProcurement requisitions
    Re: AME-Hierarchy Deciding Feature ?
    HTH
    Sanjay

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Release approval procedure and purchase requisition

    Hello gurus,
    just now I discovered a strange behaviour (in my view) in one of our client's system:
    There is a release strategy for certain purchase requisitions. When I create one of those, the release strategy is applied and the Requisition Processing State is set to "In release" automatically.
    But now comes the strange part: I can create a PO and copy that same purchase requisition item into it and save the PO! I.e. I can order the item, even though there was no prior release of the purchase requisition.
    Unfortunately I cannot try myself right now, but this is not standard behaviour, or is it? Where is the sense in having a release strategy when the item can be ordered anyway, even without release?
    Thanks in advance
    Alicia

    Hi Alicia,
    Go to transaction OLME -> Purchase Requisition -> Release Procedure         
    -> Procedure with Classification -> Set Up Procedure with                   
    Classification -> press button 'RELEASE INDICATOR', make                    
    'double click' in your last release indicator and check if the flag         
    'REL.FOR ORDENING' is set or not.                                                                               
    Go to transaction OLME -> Environment Data -> Define Attributes of          
    System Messages, and see if you have defined the message                    
    06 055 as warning or error?                                                 
    Please check additionally if you have in EBAN (for the requisition) the fields FRGKZ, FRGZU, FRGST filled with entries.
    Also deactivate your user exits and check the behaviour again (see note 365604).
    Regards,
    Edit

  • Purchase requisition is not being displayed in FM area, CJIA

    Hi
    Project cash management is activated in our system, when creating purchase requisition from project builder with account assignment 'Q' system does not generating any document in FM area (CJIA). Contradicting to this, system generating document in FM area when creating purchase requisition through ME51N transaction with account assignment Q and setting project WBS to account assignment object.
    Later, comparing both purchase requisitions using ME5J, field committed item showing different values (default layout do not display this field, need to added from change layout settings). Can any one help us to find the settings which derives the committed item field in purchase requisition?
    Screen shots are attached for detailed understanding.
    Thanks

    Sanjeev,
    In EBAN table both records are present with special stock indicator Q.  But these documents are not available in second table COOI.
    In customizing, KOAB for order category 20 (network) don't have indicator commitment management, whereas different order category having this indicator. Possibly, this would be causing the issue?? if so please help us in this direction. One more point that component with item category L (non-stock) are displayed in CJIA report.
    Checked OPSV and found both the check boxes are ticked for order category 20.
    Thanks

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

Maybe you are looking for