Purchasing Document cannot be released Urgent ?????

hi
when i try to unrelease the PO thru Txn ME29N
the system gives the said message
Purchasing document 4800003821 cannot be released
Message no. MEPO823
even when i enter the po no it on starts give the message
wat may be the reason
its urgent

may be missing of Authorizations ?
check ur SU53.
regards
Prabhu

Similar Messages

Purchasing document **** cannot be released

Dear exports,when I implement the Enhancement M06E0004, the Release strategy EKKO-FRGSX is null ,so i can't release Purchasing document, can anybody help me, and tell me why?

>
Chandralekha wrote:
> Hi,
>
> Check the entry EKKO and cehck the status for that FRGSX field. If it is null then try to update the entry using the UPDATE <<TABLE>> set frgsx ='<<value>>' where ebeln = '<<valkue>>.
>
> Pls try to udpate statement and try to set the entry and try to run the exit.
>
>
> Reward if helpful.
>
> Best Wishes,
> Chandralekha
NO, you do NOT do a direct table update on EKKO to fix a little problem like this - or to fix any problem.
The release strategy for your POs is set up for each PO order type in config. Ask your functional consultant why this is not set in the way you expect.

Purcahse document cannot be released after PO reject using ME29N

Hi gurus/experts,
is it SAP standard behaviour that once PO was rejected using ME9N, the PO document cannot be release anymore ?
if that is tha case, how can an approval reject the approval so that the release status can go back to previous release code ?
TQ

Hi,
It is possible to go back into ME29N and cancel the rejection, then the purchase order is available for approval again. The reject icon will change to a reverse rejection button after the rejection is done..
Normal process is after rejection the buyer will cancel the rejection, make any necessary changes and save. This will return the purchase order for approval. The buyers changes may reset the entire approval process if they exceed the conditions configured for resetting the approvals.
James

Purchase Requisition Cannot be released

Dear SAP Gurus,
While doing ME54N to release PR. System showing the Error 'Purchase requisition cannot be released'.
PR created on 23.04.2009 then PO Created against it , again PR was dereleased now again when going for release of PR system is providing the error as mentioned above.
Message no. MEPO822
<< Moderator message - Everyone's problem is important >>
Thanks and Regards.
Anil Thakur
Edited by: Rob Burbank on Nov 10, 2010 3:52 PM

Hello Anil
During this period any release stratergies changed for pr ? after de release the pr just modified small value and make it same again this is nothing but refresh.
then check the pr release
Laxman

Purchase |Order cannot be released Message BL001

Dear Friends,
I am new to this forum. I am facing a problem with Purchase Document release.
Two release codes GC and PH are assigned to same PO Class. Charecteristics for release are different for each codes. for release code GC is purchasing document type and Plant. For PH is again Purchasing document type, purchase order value and Purchase group. All have been put together in one class and i am not able to add a new class in release group. Request you to provide a solution for this.
rgds...KM

can you give some more details that you assigned the two release codes in same release strategy or different release strategy.
if it is assigned to same release strategy then the Charecteristics for release should be same.
for ex: you have two plants A & B
now you want to get a approval from a Asst.Manager, if the po price is more than Rs.200000. (for Plant A)
and you want to get a approval from a Manager, if the po price is more than Rs.400000.
in this case, you have to create two release code one is for Asst.Manager & another one is for Manager.
But the characteristics should be same that is your plant & doc type.

Changeability of Purchasing Document During/After Release

Dear All
I want that whenever there is any kind of change in PR/PO after start of release process the PR/PO should get de-released.I mean if PR/PO quantity is increased or decreased by 1 ea or price is increased or decreased by even 1 Re or any kind of change(e.g payment terms) then also the PR/PO should get dereleased if it has been approved for some level.
How can I achieve this?? What should be the changeability status for release indicator or is there any other way out?

Hi Satish,
Either u maintain 4 or 6 in release indicator, system is not revoking ur relaese strategy its own after change in price or Qty
The only solution is that in version tab if u check the complete check box, then it will revoke and u have to release it again.
but problem is that user usually forget to check that complete check box and save and relaese strategy not revoke.
Solution is as i think and applied that u must have make some fields mandatory in version so that user has to go in version tab to filled that mandatory field with that and ask the user to check the complete check box.
2nd solution is set message MEDCM 014 as Error in Configuration. This will prevent GR for the changed quantity (even if it is not released).
this may help u !
Regards,
Pardeep Malik

Logical problem in Purchase Order Release (urgent)

Hai Guys ,
                        I am defining a workflow for PO release and i did the release procedure for 3 levels of approve. My workflow running successfully. the workitem send to the appropriate users and they release the workitem as very well. I used the standard workflow. my logic was
           Release Code      =            Approver
                  01         =            user1
                  02         =            user2
                  03         =            user3
when i create the PO the workitem was send to the user1 for release. he execute the workitem it will go to the release screen and he is able to release. after releasing and before saving user1 is able to release the user2 and user3 releases also. that was the logical mistake happening. the user1 should not allow to release the user2 and user3 releases. how it can be done?
              Thanks in Advance.
Regards,
R.Sathis Kumar.

Your rel strategy has to be fixed, some extract from standard doco.........
                                                                                o   Release code
         Via the release code, you specify the release codes with which the
         user may release purchasing documents.
Examples
For user Miller, the following values have been defined in the
     authorization object:
o   Release group: 01 and 02 (see example b)
o   Release code: 01 and 02
The user Miller may thus release POs and RFQs using the release codes 01
     and 02.
Hope this helps, also what version are you on?

Re: Purchasing document 13000040 not subject to release strategy

Dear all
i am create PO some qty it's showing release indicates,but some PO's as 0 qty ,that po's not showing release indicates below error is showing,
Purchasing document 13000040 not subject to release strategy

hi..
please check your release strategy characteristics ..whether it is net value or quantity...
bcz..i think u have taken quantity as one of ur characteristics and given cond that..quantity should not greater than zero.
Please chk this setting and let me know..
Thanks

Purchasing document 13000040 not subject to release strategy

Dear all
iam create Po
30 or 30+ qty it is showing Release code but less-then 30 qty its showing bellow error
how rectify this error
Purchasing document 13000040 not subject to release strategy

HI
you are creating two thread for same requirement
check your following thread
[how to set Release indicator ,ofter quantity change PO release cancel;
as qty change your value will get change in PO
as you are changing qty now try following
keep qty less than 30 and change price increase it you will get Po for release,means your release procedure set for value of PO
Regards
Kailas Ugale

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

FAGLB03 - cannot display asset no and purchasing document

When I used FAGLB03 to view balance (G/L account group is "Assets accounts") and drill into details, then I go to change layout and choose asset, purchasing document fields.
I find that the report cannot diaplay asset no and purchasing document value (all value is empty, but I can see asset no and purchasing at fi doc line item by T-Code FB03).
Please advice any solution.
Thanks!
Edited by: Eric Yang on Jan 30, 2008 11:40 AM

Hi,
Thanks for your reply,
But I can find asset no, purchase order no and Internal order no In T-Code FB03 display document line item for account type "ASSETS ACCOUNTS".
Beside, I use se11 to query table bseg for fi document, if account type = 'A', I can find asset no in fields ANLN1, ANLN2 and purchasing no in fields EBELN, EBELP.

Regarding releasing external purchase documents using workflows

Hi,
i am working on "releasing external purchase documents" scenario. For this i am having STANDARD workflow which is "WS20000075" and using "RELEASE STEP CREATED" event in object type BUS2012 . I have created release strategies for all POs. But whenver i create a PO the event RELEASE STEP CREATED is not getting activated. So, can anyone tell me do i need to anything in configuration part. tell me when this event will get triggered and how to do it..
Thanks and regards,
Ravi varma

YOu have to some configurations like:
Specify whether each release code is relevant to workflow
Assign a release point to workflow-relevant release codes
Activate your workflow.
Have you done all those things or do you need input for that?
Thanks,
Shweta

Release Procedure for every Purchasing documents

Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
Thanks

Why you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24     Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1     Creation of Characteristics
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
Transaction Code     CT04
2.     On the Characteristic screen, make the following entries.
3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name     Description     User action and values     Note
Select Addnl Data tab
Table Name     Table Name     CEKKO
Field Name     Field Name     GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description     Description     Total net order value
Status     Status     Released
Data Type     Data type     Currency format     Selected by system
Number of characters     Number of characters     15
Decimal places     Decimal places     2
Currency     Currency     INR
Interval vals allowed     Interval values allowed     Check this tick box
Multiple Values     Multiple values allowed     Select this radio button
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2     Creation of Class
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
Transaction Code     CL02
2.     On the Class screen, make the following entries:
Field name     Description     User action and values     Note
Class     Class     PORELPROC
Class Type     Class Type     032
Choose Create icon or white paper icon to create new class.
Description     Description     Purchase Order Release Procedure
Status     Status     Released
Choose Char. Tab to input characteristic name.
Characteristic     Characteristic     POVAL     Created in above step
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3     Configuration of Release Procedure
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
Transaction Code     SPRO
2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Rel. Group     Release Group     02
Class     Class Name      PORELPROC     Created in above step
Description     Description     PO Release Procedure
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the entries.
6.     Choose yellow arrow to go back to popup screen.
7.     Choose Release Codes to select.
8.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Grp     Release group     02     Created in above step
Code     Release Code     01
Workflow     Workflow     Leave it blank
Description     Description     Purchase Officer
Grp     Release group     02     Created in above step
Code     Release Code     02
Workflow     Workflow     Leave it blank
Description     Description     Materials Manager
9.     Choose Enter to complete the entries
10.     Choose Save icon or Ctrl + S to save the entries.
11.     Choose yellow arrow to go back to popup screen.
12.     Choose Release indicator to select.
13.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Release ind.     Release Indicator     1
Released     Released     Leave it blank
Chgable     Changeability     4
Value change %     Change of value     10%
Description     Description     Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind.     Release Indicator     2
Released     Released     Select Check box
Changeable     Changeability     6
Description     Description     Purchase Order Released
14.     Choose Enter to complete the entries
15.     Choose Save icon or Ctrl + S to save the entries.
16.     Choose yellow arrow to go back to popup screen.
17.     Choose Release Strategies to select.
18.     Choose New Entries icon and make the following entries:
19.     System will give new screen New Entries: Details of Added Entries
Field name     Description     User action and values     Note
Release Group     Release group     02
Rel. Stategy     Release Strategy     S1
          Capital Items Release
Release Code     Release Code 1     01
Release Code     Release Code 2     02
20.     Choose Enter to complete the entries.
21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24.     Choose Next Screen icon or choose F8 to continue.
25.     If you want to simulate the release procedure you can choose Release Simulation icon.
26.     Choose Enter to complete the entries.
27.     To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4     Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
Transaction Code     CL20N
2.     On the Class screen, make the following entries:
Field name     Description          User action and values     Note
Class Type     Class Type          032
Choose Enter to Assign values.
Release group     Release Group          02
Rel. Strategy     Release strategy          S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.

Release Procedure for Service Entry Sheet Wr to the Purchasing document

Hi,
I have configured the Service entry sheet release procedure on the basis of Purchase order document type by creating Characteristic With table -field (CESSR - BSART) and also class is maintained where the defined characteristic has been assigned.Release group is assigned to the class and all necessary customizing activities carried over. I assigned release group n Strategy thru Cl20n and also checked in Cl30n for the document type where system is exactly proposing only one value for the document type. But when i create Service entry sheet thru ML81N after saving the document i checked for release strategy through Goto-> Service entry sheet -> Release Strategy which is grey mode.
I tried thru ML85 System says that no suitable purchasing document is available for release.
thank u
Nagarjuna
Edited by: yalamanchi nagarjuna on May 31, 2009 1:33 PM

the same configuration is not working in DEV environment but working fine in Quality and PRD

How to release Purchasing document

HI ALL :
can anyone help me ? thanks a lot

Hi,
Release Purchasing Documents on following T.codes:
For PR :ME54N,ME55,
For RFQ:ME45,
For PO:ME28,ME29N
Regards,
Biju K

Purchasing Document cannot be released Urgent ?????

Similar Messages

Maybe you are looking for