Purchase doc not released

Hi all,
I have created a Purchase order with reference to Purchase requisition and no when i go and try do the MIGO for goods reciept, the system throws an error saying "Purchase Document not yet released ". ow to release it and get going from there.

Hi,
Transactions:
ME28 Release Purchase Order
ME29N Release purchase order
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 not yet released.
Purchase Order with Release Strategy has a tab at the end of the Header. This allows the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 or ME29N to release the Purchase Order.
Also, visit [Configuring the PO Release Strategy|http://www.sap-basis-abap.com/sapmo017.htm]
Regards,
Srilatha.

Similar Messages

Purchase Doc. Release Procedure - Reg.

Dear Experts
In my release procedure, i need to include one status say C-Need to be clarified. Means, approver should have the option of selecting C as code, in case he needs to get some clarification from purchasing doc. creator.
Also, this C is nothing but just status is hold(Neither blocked nor rejected). How to attain this?
Please suggest.
Thanks & Regards,
Kumar

Hi,
Along with the store head and plant head, you shd create one more code for the person who create this PO..
And make him the first approver, let it be A...then only after the approval of A, it shd go to B ie. store head and after his approcal it will atlast move to C...
Now in your case, suppose C rejects the doc. then Document will again go A for the release(n will not be released untill again full above process is done)...
For this you make the entries at the release strategy as below...
A - X
B - X X(Shd be first approved by A)
C - X X X (shd be approved by A and B)
SPRO >> MM >> Purchasing >> PO >> Release strategy >> Rel. strat. w/o classification >> maintain release strategy..
Regards
Priyanka.P

Purchasing Doc. Release Procedure - Reg.

Dear Experts
In my release procedure, i need to include one status say C-Need to be clarified. Means, approver should have the option of selecting C as code, in case he needs to get some clarification from purchasing doc. creator.
Also, this C is nothing but just status is hold(Neither blocked nor rejected). How to attain this?
Please suggest.
Thanks & Regards,
Kumar

Dear Experts,
Expecting your suggestions.
Thanks & Regards,
Kumar
Edited by: KUMAR LP on Nov 30, 2010 8:53 AM
Edited by: KUMAR LP on Dec 1, 2010 6:58 AM

Object Link to DMS document - does not allow to link to docs not released

Hi Folks,
I am trying to create an object link from cProjects 4.5 to a DMS document. When I select a document in DMS I am getting the message "26 223 Document <doc_number> has not been released". If I set the status of the DMS document to a released status I am allowed to create the object link.
My question is - why am I only allowed to object link to released DMS documents? I want link to a DMS document regardless of the status.
Thanks,
Lashan

Hi Lashan,
Not sure whether this works, but do check in CFC01 and see "Document Type Dependent Data'
Regards,
Aby

Billing doc not released to accounting

Hi !
What can be the reasons that a billing document is not automatically released to accounting?
I know one reason - that is when there is a posting block assigned to the billing document type .
Plz correct me if I am wrong with the above reason,and plz provide if there can be other reasons as well.
Thanks.
Edited by: Shamik Sengupta on Feb 25, 2008 4:43 PM

Go to FS00 (Edit G/L Account) and assign a cost element to it in Edit Cost Element tab. Based on the name given to this G/L account you could correctly determine which category under which you could create it as a cost element.
Go to VF02, try clicking on the green flag and the system would throw an error.
Anaylze the error and try out transactions OKB9, VKOA to find out whether you have correctly maintained your entries.
Try running transaction FS00 and see whether the G/L accnt used for determination is valid in that particulat Company Code.
Sometimes the error could also be because the G/L accnt might required to be created as a cost element.
Let me know what is the error that you are getting. We can then propose a solution.
Reward if helpful
Regards
Ravi

Purchase order yet not released

Hi sap gurus,
i have done purchse order .then i am creating goods receipt for that purchase order but i am getting these error purchase order yet not released.plz tell me how can i solve these problem

Hi Prasad
Its simple prasad ur PO is suject to release strategy (Approval process) so the authorized person has to release the PO through the following process -
Just go to Transaction ME29N or ME28, enter ur PO no.
If u follow ME28 give ur release grp / code enetr PO no. and execute ur PO will be reflected in the list put the cursor there and press Release+Save Iconit will release the PO and then u will able make the GR.
If u follow ME29N then give ur PO no. and go to release tab at the header level and press release icon.
Best regards
Vineet Baweja

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.

No Purchase order to be create if WBS is not released

Hi,
We are using the PS system and we create a purchase order with account assignment Q, and we enter the WBS in to the purchase order.
Now the requirement is if WBS is not release system should stop to create a PO. System should allow to create a PO if wbs is fully released.
Pl advise how to do this.
Thanks,
Samir Bhatt

Please go through CJ02-Edit-Status-Lock fictionally.
It will not allow you to create a PO if the WBS is under released and locked. Hope this functionality guide/help you...
Regards
Vikrant

I bought a team license for two computers, the purchase was recorded on the credit card and the amount recorded in the making, but was unable to validate the association staff . I received an email stating that Adobe could not release the payment and that

I bought a team license for two computers, the purchase was recorded on the credit card and the amount recorded in the making, but was unable to validate the association staff .
I received an email stating that Adobe could not release the payment and that I should validate the method of payment , tried to insert another card number but the system does not accept the security VAT reporting error message. How do I validate my license with association staff and confirm the payment card?

Hi Daniel,
For any sort of payment related matter, kindly contact our support team via: http://helpx.adobe.com/in/contact.html?step=CCSN_adobe-id-signing-in_stillNeedHelp
If you are unable to use chat option kindly try below mentioned steps.
Try different browser.
Delete cookies and cache
If you are still not able to chat, Kindly reply with the below mentioned information.
OS version:
Browser Version:
You can also try: http://helpx.adobe.com/x-productkb/global/phone-support-orders.html
Thanks,
Atul Saini

Purchase requisition not subject to a release strategy

Hi All,
When I will release PR, appears Error: "Purchase requisition not subject to a release strategy". I've check the configuration, but it was appropriate. Can anyone help me to find the solution?
Regards,
MamaRara

hi
In our case also we have faced this problem
Usually when you are executing ME54N the system displays the latest viewed / modified PR.
Hope in your case the latest PR viewd / modified is not subjected to release. Hence it is showing the message
Go to ME22N open your PR - Press save button. Then try to open the same in ME54N.
Hope this will help you
SAS

Purchasing document not subject to release strategy

Hi
I created Scheduling Agreement using BAPI ' BAPI_SAG_CREATE ' . Document number created successfully but when go to release release strategy in
ME33L then it gives information 'Purchasing document not subject to release strategy ' . How i resolve this issue using BAPI .
Regards,
Suvakant

Yes it is created by using same input for ME31L .
report zsa_creation_test.
data:   poheader     type bapimeoutheader,
        poheaderx    type bapimeoutheaderx,
        poitem       type bapimeoutitem occurs 0 with header line,
        poitemx      type bapimeoutitemx occurs 0 with header line,
        i_bapireturn type bapiret2 occurs 0 with header line.
data : i_bapireturn1 type bapiret2 occurs 0 with header line .
data: l_ebeln type ebeln.
poheader-comp_code   = 'ABC'.
poheader-doc_type     = 'ZPA2'.
poheader-creat_date    = '20140507'.
poheader-created_by     = 'ABAP'.
poheader-ITEM_INTVL = '00010' .
poheader-vendor       = '0000100176'.
poheader-purch_org = 'AB01'.
poheader-pur_group = 'RR1'.
poheader-currency    = 'INR'.
poheader-doc_date    = '20140520'.
poheader-vper_start    = '20140520'.
poheader-vper_end     = '20200507'.
poheader-incoterms1    = '1'.
poheader-pmnttrms     = 'YP04'.
poheaderx-comp_code    = 'X'.
poheaderx-doc_type   = 'X'.
poheaderx-creat_date = 'X'.
poheaderx-created_by = 'X'.
poheaderx-ITEM_INTVL = 'X' .
poheaderx-vendor = 'X'.
poheaderx-purch_org     = 'X'.
poheaderx-pur_group     = 'X'.
poheaderx-currency = 'X'.
poheaderx-doc_date = 'X'.
poheaderx-vper_start = 'X'.
poheaderx-vper_end = 'X'.
poheaderx-pmnttrms = 'X'.
poitem-item_no = '00010' .
poitem-material    = 'RT010006'.
poitem-plant = 'PL02'.
poitem-stge_loc     = 'ST01'.
poitem-trackingno    = 'F'.
poitem-rel_create_profile    = 'ZAB1'.
poitem-jit_relvt = '1'.
poitem-target_qty    = '10.000'.
poitem-po_unit = 'EA'.
poitem-orderpr_un    = 'EA'.
poitem-conv_num1 = '1'.
poitem-conv_den1 = '1'.
poitem-net_price = '10.000000000'.
poitem-price_unit    = '1'.
poitem-tax_code    = '00'.
poitem-info_upd    = 'C'.
poitem-item_cat =   '0'.
poitem-acctasscat     = ''   .
poitem-apo_planning     = '1'.
append poitem .
poitemx-item_no = '00010'.
poitemx-item_nox = 'X'.
poitemx-material = 'X'.
poitemx-plant      = 'X'.
poitemx-stge_loc    = 'X'.
poitemx-trackingno = 'X'.
poitemx-rel_create_profile = 'X'.
poitemx-jit_relvt      = 'X'.
poitemx-target_qty    = 'X'.
poitemx-po_unit        = 'X'.
poitemx-orderpr_un    = 'X'.
poitemx-conv_num1        = 'X'.
poitemx-conv_den1      = 'X'.
poitemx-net_price       = 'X'.
poitemx-price_unit    = 'X'.
poitemx-tax_code    = 'X'.
poitemx-info_upd    = 'X'.
poitemx-item_cat    = 'X'.
poitemx-acctasscat = 'X'.
poitemx-apo_planning = 'X'.
append poitemx.
call function 'BAPI_SAG_CREATE'
exporting
    header             = poheader
    headerx            = poheaderx
importing
    purchasingdocument = l_ebeln
*   EXP_HEADER         =
tables
    return             = i_bapireturn
    item               = poitem
    itemx              = poitemx.
call function 'BAPI_TRANSACTION_COMMIT' .

Inbound delivery created for not released purchase order

Scenario from an IS-Retail system:
We have created purchase orders (from vendor to DC) and allocation store order (type AL - an STO from DC to stores) through the allocation table (WA02).
After GR was posted for the PO, we then delivery do the merchandise distribution through WF50 (i.e. create inbound deliveries fro the SO).
The issue is even though the store order (allocation order type AL) is not yet released, we are able to create deliveries through WF50 for those store orders.
We are able to create deliveries even though the purchase order (store order) is not released through WF50.
But using VL10B or D, it works fine, we are able to create inbound deliveries only after release of the purchase order.
Any idea what could be wrong?

Hi Roselyne,
What you experienced is standard system behavior. Inbound delivery type is uniquely assigned to confirmation control key. You can only specify confirmation control key on item level in PO. The assignment of Delivery type can be seen in the following table:
T163D
IBTYP EBTYP LFART RETDLV
1        AB                      X
2        LA        EL           X
3        GW       EG
The field T163D-IBTYP is checked in different programms. For example in programm RM06ENAB (TA: ME92F). If you insist to customize the determination of delivery type by PO type, I strongly suggest you discuss with the Application consultants before making the modifications to ensure it won't impact other areas.

I had purchased Imovie today I can find the icon movie it click it but it will not open. Its shows up in docs and purchased but not apps? how do i add it to my bar and open it?!

I had purchased Imovie today I can find the icon movie it click it but it will not open. Its shows up in docs and purchased but not apps? how do i add it to my bar and open it?!

Exactly where are you clicking, you need to be specific. For example, are you using the Dock, the Applications folder, Launchpad, etc. to attempt to start teh app? Also IOS 7.1.2 does not run on a Mac, what version of OS X is installed on your computer?

Problem in creation of any purchasing doc against plant 0001

Hi MM Experts,
I am facing problem in creation of any purchasing doc (i.e: PR or PO) against plant 0001.This is available in the system and assigned to company code. I can create Material master with this plant 0001 and copy to create new plant. But Can't create any pur doc? also in plant list in pur doc showing the rest of the plant except plant 0001.
I m working on ECC 6.0.
Regards,

Dear Sairam/Steve,
I got solution for my problem. The problem is that address number not maintained for 0001 plant.This solution available from the following note. please go thro...
Note 433997 introduced a new logic for the F4 help for plants.
solution proposed in note 433997 :
To maintain the address number of a plant subsequently, startTransaction OX10 for the affected plant ('Change plants') view. Click the 'Address' pushbutton (envelope) or (shiftF5). In the subsequent screen ('Change address'), press Enter or click the 'Copy' pushbutton and save using the 'Save' pushbutton (disk) or (CtrlS).
Then the plant should have an address number and should also be displayed in the search help.
Thank you all
Regards,

Purchase doc not released

Similar Messages

Maybe you are looking for