Purchase order don't be release,

Dear all,
I create a purchase order  and use ME29N to release it ,
But system come out a message
"Purchasing document 7083000082 cannot be released.
Message no. MEPO823"
Can you help me how to deal with this issue ?
Thanks,
Alex

You need to check two thing:
Firstly go to ME23n and check wheather Po has the release tab at header level If yes then what is the status.
Secondly, I  hope release strategh has alreadybeen configured in your system check the charecteristics that you have taken and match it wuth your PO. Then GO to CL24n and check whether you have maintain the same data against your strategy or not
If not maintain then main the data in CL24n
Then go to the POand make a small change releated to your charecteristics.
regards
Anamika

Similar Messages

  • Purchase Order not subject to release strategy

    Good day everyone!
    I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
    After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
    My question is: How to assign purchasing document to release strategy?
    Please help. Thank you in advance.
    Anisah

    hi
    yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
    now below i am giving u one by one steps , follow and let me know .
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order.  There is only one characteristic created in this example.  For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic   e.g.  NETVALUE
    Click Additional data Table name CEKKO      Field name  GNETW    and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X    Mutliple values
    X    Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group   Rel. Object   Class                 Description
      02                                 REL_PUR        Rel. Strategy for PO
    Release codes - New entries
    Grp         Code
    02           01
    Release indicators
    Release indicators           Release        Description
          0                                                        Blocked
          1                                     X                Release
    Release Strategy
    Release group   02
    Rel.strategy    01
    Release codes   01
    Release status   0
                            1
    Classification   Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header.  This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order. 
    regards
    ravikant dewangan

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

  • Disabling selected Purchase Order field(s) after released/approved

    Hi Experts,
    I have a requirement to disable specific Purchase Order fields after released via ME29N.
    For example, in Purchase Requisition - I can "Release Indicator - Field Selection Key" to control Purchase Requisition screen layout. However, for Purchase Order - the configuration for "Release Indicator" consist only standard default "Chgable" options.
    Question:
    Is there a way to customize the Purchase Order "Release Indicator" for screen layout based on customer requirements other that using the default as mentioned above?
    Thank you.
    Steven

    Hi Padmasri,
    I understand your explanation on the standard SAP behavior.
    Nevertheless, I'm looking for some flexibility to meet customer requirement. Like in Purchase Requisition, there is option to further customize the screen layout by linking it to the "Release Indicator".
    Therefore, apart from the standard 6 options given by standard SAP, can we add/customize the options? For example, my customer may one to change a field in the Purchase Order even after released.
    Thank you.
    Steven

  • Purchase Order E-mailing with Release Strategy

    Hello,
        We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
      We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
      SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
      Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
    Print Programs:
    /SMB11/FM06P
    /SMB40/FM06P
    SAPFM06P (Sapscript Only)
    Forms:
    /SMB11/BL_MMPO_L
    /SMB11/MMPO_L
    /SMB40/MMPO_L

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • Purchase order print out before release of p.o.

    Dear Experts,
    At present the process is as follows.
    Client prepares a purchase order. The purchase order is then released by 4 authorities.
    Clients requirement is that after release of P.O. if any modifications has to be done then system should not ask for revoking of the release indicators. Sytem shold allow to change the quantity and price to the 1st release authority and at the same time the system also allow to take the print of the Purchase order.
    Please guide me how the same can happen in sap mm.
    Thanks & Regards,
    Aaditya

    Hi aaditya..
    You need to define a routine program
    Follow the path: SPRO--> MM --> Purchasing --> Messages --> Output control --> Maintain Requirements for Message Control.
    Kindly make changes in the routine relevant for the Purchase Order Application with the help of a technical guy and make it as per your requirement.
    Then Go to: Message Determination Schema --> Define message schema for Purchase Order
    Thanks,
    Ankur

  • Create a purchase order strategy with four release steps.

    Hi all,
    how can I create a purchase order release strategy with 4 release steps?
    The steps have to be the following:
    AC (Buyer);
    CO (Controller);
    FI (Finance);
    AD (CEO).
    I couldn't configure and add entries in "Release prerequisites" (trx.OMGS).
    Best regards

    Hi ,
    The implemantation steps as follows ;
    Materials Management -- Purchasing -- Purchase Order --Release Procedure for Purchase Orders
    1 . Edit Characteristic ; You must create characteristics that related your strategy first . IN additonal data screen use "CEKKO " as table and appropriate field as field name .
    2.  Edit Class ; Create your class with class type - 032 . And enter your characteristics that created first step .
    3. Define Release Procedure for Purchase Orders
                    a.Create Release Groups and enter your class
                    b.Create release codes related with Buyer , controller etc.
                    c.Create Release indicator
                    d. Create Release Strategies ; Enter your release codes and in classificaiton area , you must enter your values that related with characteristics that created step 1.

  • Send purchase order e-mail with release strategy

    Hi!!
    I have a problem with sending e-mails in purchase order that are blocked with release strategy.
    I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
    Somebody knows what is happening?
    I would like to send e-mails without previous modification of the purchase order.
    Thanks for your help.

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • 100% Deleted Purchase Orders appearing on ME28 release screen

    Scenario 1 - No problems!!
    >   I create a PO (ME21N) which appears on the release screen (ME28)
    >   I select all line items, click the trash can & save (ME22N).
    >>The PO no longer appears on the release screen
    Scenario 2 - Problems....
    >   I create a PO (ME21N) which appears on the release screen (ME28)
    >   I flag the "Final Invoice" indicator (field EKPO-EREKZ), select all line items, click the trash can & save (ME22N).
    >>The PO remains on the release screen.
    Can anyone assist?
    I have set breakpoints in executed exits...couldn't find any problems
    *I have traced Scenario 1 & 2 via the runtime analyser, downloaded the results & compared in excel with a vlookup...No differences of interest found

    hi Trafford,
    This is a good finding. Infact the system behaves in this way that if the Final Invoice is ticked and if the PO item is deleted, it still appears in ME28.
    I think this is standard functionality, that system expects an invoice when the final invoice is ticked so it is still active in ME28. But when you try to post invoice it will certainly not allow as the items will be deleted.
    Iooks like its a bug in SAP and you may want to contact SAP for this.
    Regards
    Seema

  • Create custom data when releasing a Purchase Order

    Hello people,
    The customer uses ME28 to release the Purchase Order.
    They have, for instance, two release estrategies: W1/01 and W2/02, that differ about the price.
    The scenario is:
    When the customer releases a Purchase order from W2/02 strategy using ME28 transaction, we need to do some verifications in Z tables and create a record in another Z table. If for some reason the purchase order will not be released, this Z data does not have be saved.
    And if some error occurs and the data don´t be saved, the estrategy must remain blocked (not released).
    In which EXIT is the best point to do this?
    Thanks a lot!

    hey
    try these 2 user exits
    MM06E005 - ZXM06U43 which is called from exit EXIT_SAPMM06E_012. This code is hit at the time you check or save.
    M06E0004 - Changes to communication structure for release purch. doc - EXIT_SAPLEBND_002

  • Purchase order release strategy report

    Dear Gurus,
    We are using purchase order release strategy with classification.
    We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
    How to get it ?
    Please provide ur help for the same
    Rgds,
    Saurabh

    Hi,
    Basically in EKKO table there is a field name FRGZU  -
        Release status based on that we can write a logic take the report.
    for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
    Just tell him the logic to ABAP person they will develop
    Rehgards
    Murugan J

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

  • Release Tab in purchase order disappear after release using ME29n

    Hi there,
    We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem.  When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy.  Using the older ME28 transaction to release this purchase order, everything is fine.  We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order).  When we use transaction ME29n the release tab in the purchase order just simply disappears after saving.  In the purchase order header changes, the release change is visible, but the release tab is missing.  This purchase order is now not subject for release, and a goods receipt is possible without release.  I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
    Has anybody had a similar experience?  Any advise would be greatly appreciated.
    Regards
    Christo Vermeulen

    Hi Christo Vermeulen,
    I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
    Thanks in advanced,
    Eder Nicoleti

  • Logic required to findout "Release To Date" of the Purchase order

    Hi
    We are developing a custom program to release purchase orders as per clients requirements. In that, in the output, we need to display the "Release To Date" of the purchase order. Consider the release codes are R1,R2& R3, and currently the PO is released by R1, then we need to show "Release To Date" as R1. Simillerly once R2 also released the PO, we need to show "R1 R2" in the Release To Date field. This you can see in the Release Tab of the PO.
    Now we need to adopt the same logic in our custom program also. Which table i can find the release to date details. The latest release code of the PO also good enough to build the logic to findout the "Release To Date"
    Any pointers would be of great help.
    Thanks
    Venkat.

    Hi Venkat,
    Check up these tables
    T16FC, T16FD, T16FG, V_T16FC
    Regards,
    Hareesha
    If it's help's reward the pts

  • Purchase Order Un release Process

    Dear All,
    We have created three level for releasing the Purchase order. When Purchase order release by third level then we are not allowing to modify the PO.
    Now if any body want to modify then PO should be unrelease by three level then only modification should be allowed.
    Please suggest how i should do it.
    Thanks in advance.........
    Sanjay

    Hello,
    Firstly release can be reset by setting the changeability as 4 for release indicator. Like if release happens once then any change is made in terms or Quantity or Value New release strategy will be triggered. Also you can activate a Message:
    00     06     684     Releases already effected are liable to be reset     E.
    But is your requirement only to restrict someone from Changing Purchase order once it is released?
    regards,
    Prashant Rathore.

Maybe you are looking for

  • OIM 9.1.0 Available

    Hi, Just checkout oracle download and found that 9.1 available. cheers, Ankit

  • Why are my brand new KRK monitors crackling?

    I just got a pair of KRK RokIt5's. I only used them once.. to test out my tracks, adjusting the mix, and playing with the volume knobs. I barely went full volume, but now they're cracking. It's faint, but there. I tested four diff. cables - that wasn

  • Capture One comparison

    I have been using Lightroom for the last couple of months, and recently tried an output comparison with C1. I have taken one raw file, output from both programs and view the tiffs with photoshop. At the settings I tried C1 was way better, less noise

  • Error checking

    i have made one small program where i m connecting to timesten and creating one table but the problem is m not able to check wheather m connected to timesten and created the table there. There is no error and neither table got created in the database

  • Flash Player 10.2 latest brings BSOD

    Just upgraded this AM.  Received email from friend with 4 links to youtube vids. Clicked link 1, browser opens, vid plays. Click link 2, browser changes page ... BSOD nv4_disp.dll is the identified culprit on BSOD Happens every time. Uninstall Flash