Release purchase order issue

hi expert ,
when i use tcode me21n create a purchase number and use the tcode me29n to
release the purchase order but return the systmen message , i can't be relase
does anyone know what's the matter ?
i create the purchase order without any error message .
thansk in advance

hi,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Regards,
Balakumar.

Similar Messages

Report for released purchase order

Hai guru's
this is second time but i did't get any good replay please consider this, i want any standard report for released purchase order,means(i released two backdated po today next day i verify the report ME2n,those po are not display, the system take only document date not released date, now i am using CDHDR through this i got the report. but it is big process, so once check this and send your valuable solution.
Prasad

Hi Krishna,
You could use Me2N with the dynamic selection coupled with normal selection screen.
In Dynamic selection(3rd icon in screen).....you can select for which company code, release indicator as released....and save it as default variant.
hope this should solve your query
Sk.

Error release purchase order using transaction code me29n

i have warning error this purchasing document number cannot be released.
while i enter me29n t code.why?
then how to release purchase order using me29n t code?
can anyone answer this two questions.

hi
i have warning error this purchasing document number cannot be released. while i enter me29n t code.why?
is the release strategy is triggred for the po ?? check thisin P order in me23n ,in header level check release strategy tab ,
then how to release purchase order using me29n t code? can anyone answer this two questions.
just go to me29n >release strategy tab here just click on the release button in front of the release code

Z Report of Transaction ME28.(Release Purchase Order)

Dear all,
               I want to make Z Report for the Transaction ME28 (Release Purchase Order).
I am facing problem of GUI status in my Z Report. Actually Report is not displaying like ME28.
and all the menu and function keys are also not coming properly.
So, pls suggest me good solution.
Thanks & Regards,
Sandip Sonar.

I am attaching a copy of ME28. Please give it to your ABAP consultant.
He should be able to do the needful:
REPORT RM06EF00 NO STANDARD PAGE HEADING MESSAGE-ID ME.
       Anzeigen Einkaufsbelege zur Belegnummer                       *
Tabellen                                                            *
INCLUDE FM06LTO1.
INCLUDE FM06LCFR.
**table added t16fc - SAPBY     6 Feb 98
TABLES: T16FG, T16FS, T16FV, T16FE, RM06B, T160B, T16FC.
DATA: BEGIN OF XEKPO OCCURS 100.
        INCLUDE STRUCTURE EKPO.
DATA: END OF XEKPO.
*- Interne Tabelle der Zustände -
DATA: BEGIN OF ZUS OCCURS 10.
        INCLUDE STRUCTURE T16FV.
DATA: END OF ZUS.
DATA: BEGIN OF ZUSKEY,
         MANDT LIKE EKKO-MANDT,
         FRGGR LIKE EKKO-FRGGR,
         FRGSX LIKE EKKO-FRGSX,
      END OF ZUSKEY.
Parameter und Select-Options                                        *
PARAMETERS:     P_FRGCO LIKE T16FC-FRGCO OBLIGATORY.
SELECT-OPTIONS: S_FRGGR FOR EKKO-FRGGR.
PARAMETERS:     P_FRGSE LIKE RM06A-P_FRGSE DEFAULT 'X',
                P_FRGRS LIKE RM06A-P_FRGRS,
                P_FRGVO LIKE RM06A-P_FRGVO DEFAULT 'X',
set default to 'X' to show items as well - SAPBY
                P_MITPOS AS CHECKBOX DEFAULT 'X',
set default to 'DEFAULT' - SAPBY
                LISTU LIKE T160O-LISTU DEFAULT 'DEFAULT'.
SELECT-OPTIONS: S_BSTYP FOR EKKO-BSTYP,
                S_EKORG FOR EKKO-EKORG,
                S_EBELN FOR EKKO-EBELN MATCHCODE OBJECT MEKK
                                       MEMORY ID BES,
                S_BSART FOR EKKO-BSART,
                S_EKGRP FOR EKKO-EKGRP,
                S_LIFNR FOR EKKO-LIFNR MATCHCODE OBJECT KRED,
                S_RESWK FOR EKKO-RESWK,
                S_BEDAT FOR EKKO-BEDAT.
Hilfsfelder                                                         *
INCLUDE FM06LCEK.
DATA: XFRG1 LIKE EKKO-FRGZU,
      XFRG2 LIKE EKKO-FRGZU.
DATA: XSELKB LIKE EKKO-BSTYP,
      XSELKK LIKE EKKO-BSTYP,
      XSELKL LIKE EKKO-BSTYP,
      XSELKA LIKE EKKO-BSTYP.
FIELD-SYMBOLS: .
DATA: HFDPOS LIKE SY-FDPOS.
**workflow line added for workflow
DATA : LAST_USER_COMMAND LIKE SY-UCOMM.
Intitialisierung                                                    *
INITIALIZATION.
PERFORM ANFORDERUNGSBILD(SAPFM06L) USING XSELKB XSELKK
                                           XSELKL XSELKA.
lines 67, 70 and 73 commented out -SAPBY
**listu = t160b-listu.
S_BSTYP-SIGN = 'I'.
S_BSTYP-OPTION = 'EQ'.
**if xselkb ne space.
S_BSTYP-LOW = 'F'.
APPEND S_BSTYP.
**endif.
IF XSELKK NE SPACE.
    S_BSTYP-LOW = 'K'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKL NE SPACE.
    S_BSTYP-LOW = 'L'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKA NE SPACE.
    S_BSTYP-LOW = 'A'.
    APPEND S_BSTYP.
ENDIF.
next two lines added to default the release code
IMPORT T16FC-FRGCO FROM MEMORY.
get parameter id 'ZRC' field t16fc-frgco.
P_FRGCO = T16FC-FRGCO.
Seketionsbild                                                       *
AT SELECTION-SCREEN ON LISTU.
PERFORM LISTUMFANG(SAPFM06L) USING LISTU.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FRGCO.
CALL FUNCTION 'HELP_VALUES_FRGAB'
       EXPORTING
            I_FRGOT = '2'
       IMPORTING
            E_FRGAB = P_FRGCO
       EXCEPTIONS
            OTHERS = 1.
AT SELECTION-SCREEN.
CALL FUNCTION 'ME_REL_CHECK_MANY'
       EXPORTING
            I_FRGOT = '2'
            I_FRGCO = P_FRGCO
       TABLES
            T_FRGGR = S_FRGGR
            T_T16FV = ZUS.
Beginn der Selektion                                                *
START-OF-SELECTION.
NOT_FOUND = 'X'.
SET PF-STATUS 'FREI'.
SET TITLEBAR '001' WITH P_FRGCO.
PERFORM FRG_INIT(SAPFM06L) USING P_FRGCO P_MITPOS.
*- Lesen Belegköpfe -
SELECT * FROM EKKO APPENDING TABLE XEKKO
                     FOR ALL ENTRIES IN ZUS
                     WHERE FRGRL EQ 'X'
                       AND FRGGR EQ ZUS-FRGGR
                       AND FRGSX EQ ZUS-FRGSX
                       AND EBELN IN S_EBELN
                       AND BSTYP IN S_BSTYP
                       AND EKORG IN S_EKORG
                       AND LIFNR IN S_LIFNR
                       AND RESWK IN S_RESWK
                       AND BEDAT IN S_BEDAT
                       AND BSART IN S_BSART
                       AND EKGRP IN S_EKGRP
                       AND LOEKZ EQ SPACE.
IF P_FRGRS NE SPACE.
    SELECT * FROM EKKO APPENDING TABLE XEKKO
                       FOR ALL ENTRIES IN ZUS
                       WHERE FRGRL EQ SPACE
                         AND FRGGR EQ ZUS-FRGGR
                         AND FRGSX EQ ZUS-FRGSX
                         AND EBELN IN S_EBELN
                         AND BSTYP IN S_BSTYP
                         AND EKORG IN S_EKORG
                         AND LIFNR IN S_LIFNR
                         AND RESWK IN S_RESWK
                         AND BEDAT IN S_BEDAT
                         AND BSART IN S_BSART
                         AND EKGRP IN S_EKGRP
                         AND LOEKZ EQ SPACE.
ENDIF.
SORT XEKKO.
*- Prüfen Freigabevoraussetzungen -
LOOP AT XEKKO.
    MOVE-CORRESPONDING XEKKO TO ZUSKEY.
    READ TABLE ZUS WITH KEY ZUSKEY BINARY SEARCH.
    CHECK SY-SUBRC EQ 0.
    XFRG1 = ZUS+9(8).
    XFRG2 = XEKKO-FRGZU.
    TRANSLATE XFRG2 USING 'X +'.
    OVERLAY XFRG1 WITH XFRG2 ONLY '+'.
    SEARCH XFRG1 FOR 'X'.
*---- Keine Freigabezuständigkeit -
    IF SY-SUBRC NE 0.
      DELETE XEKKO.
    ELSE.
*---- Freigabestelle merken -
      HFDPOS = SY-FDPOS.
      ASSIGN XFRG2+SY-FDPOS(1) TO .
*---- Freigabe bereits erfolgt -
      IF P_FRGRS EQ SPACE AND
          EQ SPACE.
        DELETE XEKKO.
      ELSE.
*---- Freigabe noch nicht erfolgt -
        IF P_FRGSE EQ SPACE AND
            NE SPACE.
          DELETE XEKKO.
        ELSE.
*---- Freigabevoraussetzung fehlt -
          IF XFRG1 CA '+' AND
             P_FRGVO NE SPACE.
            DELETE XEKKO.
          ELSE.
            EKKO = XEKKO.
            PERFORM FRG_FEKKO_AUFBAUEN(SAPFM06L) USING HFDPOS.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
SORT XEKKO.
*- Lesen Belegpositionen -
IF P_MITPOS NE SPACE.
    SELECT * FROM EKPO APPENDING TABLE XEKPO
                       FOR ALL ENTRIES IN XEKKO
                       WHERE EBELN EQ XEKKO-EBELN.
ENDIF.
*- Ausgabe -
LOOP AT XEKKO.
    EKKO = XEKKO.
    PERFORM EKKO_ANSCHRIFT(SAPFM06L).
    PERFORM EKKO_AUSGABE(SAPFM06L).
    IF P_MITPOS NE SPACE.
      LOOP AT XEKPO WHERE EBELN EQ EKKO-EBELN.
        EKPO = XEKPO.
        PERFORM FC_ME_READ_HISTORY(SAPFM06L).
        PERFORM EKPO_AUSGABE(SAPFM06L).
      ENDLOOP.
    ENDIF.
ENDLOOP.
Ende der Selektion                                                  *
END-OF-SELECTION.
IF NOT_FOUND NE SPACE.
    MESSAGE S260.
    IF SY-CALLD NE SPACE.
      LEAVE.
    ELSE.
      LEAVE TO TRANSACTION SY-TCODE.
    ENDIF.
ENDIF.
WRITE: /(81) SY-ULINE.
OK-Code-Eingabe                                                     *
AT USER-COMMAND.
**workflow inserted 6 Feb 98 by SAPBY
    PERFORM WORKFLOW_AT_USER_COMMAND.
INS GSB 18/02/2004 - check user approving is not user that create
PO
if sy-ucomm = 'FRGU' or sy-ucomm = 'FRGS'.
loop at xekko.
if xekko-ERNAM = sy-uname.
     CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
       EXPORTING
         TITEL              = 'Error'
TEXTLINE1 = 'As the creator of this pruchase order you cannot approve it
as well !'
    leave program.
endif.
endloop.
endif.
PERFORM USER_COMMAND(SAPFM06L).
Seitenueberschrift                                                  *
TOP-OF-PAGE.
PERFORM TOP(SAPFM06L).
TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM TOP(SAPFM06L).
**& form workflow_at_user_command
TEXT
---> p1 text
<-- p2 text
FORM WORKFLOW_AT_USER_COMMAND.
IF LAST_USER_COMMAND IS INITIAL.
    LAST_USER_COMMAND = SY-UCOMM.
ENDIF.
IF SY-UCOMM EQ 'ZURU'.
     PERFORM TRIGGER_WORKFLOW.
ENDIF.
CASE SY-UCOMM.
    WHEN 'BU'.
      IF P_MITPOS EQ 'X'.
        CHECK LAST_USER_COMMAND <> 'FRGR'.
        PERFORM TRIGGER_WORKFLOW.
      ELSE.
        CHECK LAST_USER_COMMAND = 'FRGS'.
        PERFORM TRIGGER_WORKFLOW.
      ENDIF.
    WHEN 'FRGU'.
      PERFORM TRIGGER_WORKFLOW.
ENDCASE.
LAST_USER_COMMAND = SY-UCOMM.
ENDFORM.
**& form TRIGGER_WORKFLOW.
TEXT
---> p1 text
<-- p2 text
FORM TRIGGER_WORKFLOW.
DATA : BEGIN OF ZEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF ZEKKO.
DATA : BEGIN OF YEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF YEKKO.
DATA : WFBAN LIKE EKKO-EBELN,
       WFERN LIKE EKKO-ERNAM.
CLEAR : WFBAN, WFERN.
MOVE-CORRESPONDING XEKKO TO YEKKO.
CONCATENATE YEKKO-FRGZU 'X' INTO YEKKO-FRGZU.
APPEND YEKKO.
MOVE-CORRESPONDING XEKKO TO ZEKKO.
*XEKKO-KZ = 'F'.
APPEND ZEKKO.
SELECT SINGLE KOKRS KOSTL
     INTO (EKKN-KOKRS, EKKN-KOSTL)
     FROM EKKN
     WHERE EBELN = XEKKO-EBELN
     AND EBELP   = '00010'.
if sy-subrc <> 0.                  " Cost centres not mandatory at XXX
exit.
endif.
CALL FUNCTION 'Z_ME_REL_EVENT_EKKO'
     EXPORTING
          I_CALL_UPDKZ = 'F'
          I_WFBAN      = EKKO-EBELN
          I_FRGCO      = T16FC-FRGCO
          I_ERNAM      = SY-UNAME
          I_UCOMM      = SY-UCOMM
     TABLES
          I_EKKO_NEW   = YEKKO
          I_EKKO_OLD   = ZEKKO.
ENDFORM.

Need Message On change of Released Purchase order

Hi
I need to display message On Edit of released purchase order through ME22N or on click of edit in ME23N
Kindly suggest exits for the same.

Hi Arun,
Create implementation for BADI: ME_PROCESS_PO_CUST. In this get the release status of PO and raise a message.
Regards,
Vijay

Unprinted released purchase orders

Hello forum,
Is there any way from standard SAP (report) to watch, which purchase orders are released but they are NOT printed ?
Thanks in advance.

Hi Stratos,
You can achieve this through Standard SAP. I am assuming that you have the print output, not set, as "send immediately when saving the application"
Please provide the list of P.O's which you are investigating in ME9F, provide the application as EF and Processing Status as 0 (Not processed)
This way, you will get the whole list of P.O's which have not been printed out, please note that outputs can only be processed on successfully released Purchase Orders.
Regards
Shailesh

Issue with ME28 - Release Purchase Order

Dear All,
One of our user is unable to release a purchase order through Transaction code ME28.
The role is assigned only with the Transaction Code ME28 with the correct Release code and Group.
We have tested from our end and see that the Auth Objects M_BEST_BSA and M_BEST_EKO are missing based on SU53. When we have added back it worked.
When i check in Su24 the Auth Obj M_BEST_BSA and M_BEST_EKO are not set to CHECK -> Value "NO".
I dont understand how this Transaction is working, when the behaviour of the Transaction ME28 is to release the purchase order why is the system asking for additional Auth Objects.
please advice.
Regards

Hi
M_BEST_BSA and M_BEST_EKO are not set to CHECK -> Value "NO".
If the check is not set to the standard delivered SAP what is the value in SU24 ? Has it been changed to CHECK > YES or DO NOT CHECK ?
I am sure you are aware that SAP does not deliver all objects coded in the programme under AUTHORITY-CHECK Statement in the SU24 Indicators with a CHECK > YES that are in transaction ME28. SAP only deliver a fraction of the values in the proposal as YES and the rest must be maintianed by the security team as they are discovered to be relevant to your organisations need of the particular functions within the transaction.This will then keep PFCG updated with all the CHECK YES objects the next time you add transaction ME28.
In other words all the objects listed in SU24 ( that are CHECK ) for ME28 will all be coded in the programme somewhere but it depends on which bits of the functionality within ME28 you are using that determines if they are called.

Release Purchase Order

Hi,
we are facing problem in TCode ME29N when print the Purchase Order where we are using Output Type Developed ZBTM.Message Show You are not authorized to change release document. How to solve this problem.
aman

Hi,
When you get the error, access transaction SU53, or direct via /nsu53. This will show execatly what the problem is and what authorisation object is causing the issue.
Thanks.

Final Invoice not releasing purchase order commitments

Hi Experts,
We recently upgraded from 4.6C to ECC6 and have had reports of commitments not longer being released when the Final Invoice is flagged on Service purchase orders. This is causing many issues since they can no longer flag the last service entry as "Final" because the invoice has already paid.
Out User's have become dependent on this process so please help. I have looked in OSS but cannot find anything referring to this issue.
Any help is greatly appreciated.
Thank you in advance,
Stella Cook
Tesoro Companies Inc.

Hi Kiran,
I think that there is some user exit getting called in place where you have issues. Ideally the final invoice should never check the order as the order can be in teco during invoicing.
I suggest you to debug it using your ABAPer as the signs are of some code inconsistency. The results are different when you directly click the final invoice and click after once seeing the account assignment,
Regards
Vivek Singh

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.

Problem in releasing Purchase order(ZCAP and ZREP)

Hi,
I had made a purchase order and now i want to release in the tcode ME29N but the when i execute this tcode and fill the PO it gives the message that it cannot be released.
can any body provide me guideliens for it to solve this problem.

First Go to ME23N Purchase ORder Display and In Header tab Check Whether Release Strategy tab is there.
If its there Check whether all the Charecteristics values you defined are meeting the Release strategy.
Then go to ME29N and Put tick mark on Set Release Option and Try again.
Regards,
Ashok

Report of Released Purchase Orders

I am looking for a report that will give me all purchase orders that was released, and the person that released it.
Thank you.

Go to "ME2C" (List Display of Purchasing Documents for Material Group). Press "Shift + F4" (show dynamic selections). Open folder "Purchasing Document Header". Scroll to item "Release indicator" and double-click on the item. The item will appear on the right and can now be used as selection criteria in the list display.
Alternatively
You may use 'ME28' to display and consequently release PO's that are subject for release. You need to indicate a particular release code and release group. Once this is executed, all PO's that are still pending for release by that release code will be displayed

Purchase Order - Issue storage location set mandatory entry

Hello All,
When create subcontracting PO, want to set the field of Issue storage location as mandatory.
I tried to find configuration "Materials Management>Purchasing>Purchase Order-->Define Screen Layout at Document Level", but there is not entry "Issue storage location" to set the screen layout field.
I searched previous threads, but only find some to mention issue storage location for STO. Now, I just use subcontracting PO that is same as NB document type.
Please your kind suggestion or any method to set Issue storage location as mandatory in PO.
Thanks very much!
Mag

Hi ,
Please, could you re-check it again, I have found storage location and issue storage location fields under define fields for fields selection group.
Under Field selection group NBF Purchase order
Selection group                    supplying plant
Issue storage location required entry chose
Under Field selection group NBF Purchase order
Selection group                    Basic data item
Storage location   required entry chose
After this setting, I can be find this storage location fields as Mandatory.
Regards,
Thiru

Change message status after release purchase order

Hi,
I'm a newbie in MM...
When a purchase order is created, the message status is not processed (yellow light) until the purchase order is released. Then the message is printed and the status changes to green light.
As far as I see, I can't find in the spro where is this customizing set or if there is a user-exit or badi for changing the message status depending on the release indicator.
Thanks in advance!
Jen

Hi Jen,
Complete the condition record, for example, like this:
- Transaction: MN04
- Output Type: NEU
- Choose third option: Purchasing Output Determination Document Type
- Document Type: NB
- Function: VN (Vendor)
- Medium: 1 (Print output)
- Date/Time: 4 (Send immediately (when saving the application))
Select the line and press button "Communication". Complete the output device and mark the option "Print immediately"
So, when the PO is created the system generates the message with yellow status. Then, when the PO is released, the message status will be green
Regards,
Fernando

Authority mail while releasing purchase order

Hello Experts,
My requirement is when the person release the purchase order(SAP-MM) of certain amount then email will trigger to the authorized person and once he approves then only PO will get released.
Is there any work of ABAP in this, If yes, How this functionality can be achieved through abap and what are the user exits I need to apply.
Please help.

Yes It is possible. You have to write an enhancement in Program LMEGUICJI after get PO has been saved (committed) .
her you will get all the info about the PO after being Commit Work executed After ->POST.
You will also get the release strategy information using the FM "BAPI_PO_GETRELINFO ". Based on The release strategy and amount in PO you can send mail using the FM "SO_NEW_DOCUMENT_ATT_SEND_API1".
Hope this will solve your purpose.

Release purchase order issue

Similar Messages

Maybe you are looking for