Regd: Purchase Order ME28 & ME29N

Hi All,
We have a scenario that once when the Purchase orders are set to release in T-code ME28 or ME29N the details of those particular P.O should be converted into XML file.
Currently we have developed to logic to create XML file but we need the exact User Exit or the BADI where we can use this logic.The main issue is how to capture the value of the Check Box Field "Set Release", b'cas based on the value only we have to get the data of those P.O.'s
Help and Suggestions will be much appreciated.
Thanks & Regds.
Ramesh.

Hello ,
The BADI me_proces_po_cust can be used for this purpose .
The BADI has a method called check , which is called by the me21n , me22n , me23n and me29n transactions upon check or save .
The method is called in me29n save and you can use the if_purchase_order_mm object : im_header , to extract any data you need about the PO .
According to the t-code you can call upon your own xml generating function when needed.
Best Regards ,
Hope that this information helps you .

Similar Messages

Regd : purchase order list in SAP

hi,
Is there standard purchase order list available in SAP.
<b><REMOVED BY MODERATOR></b>
Message was edited by:
        Alvaro Tejada Galindo

Hi
execute the following Std Tcodes for PO lists
ME2B                 POs by Requirement Tracking Number
ME2C                 Purchase Orders by Material Group
ME2J                  Purchase Orders for Project
ME2K                 Purch. Orders by Account Assignment
ME2L                  Purchase Orders by Vendor
ME2M                 Purchase Orders by Material
ME2N                 Purchase Orders by PO Number
Regards
Anji

Regd:Purchase Order

Hi All,
My require ment is to Calculate the Vendor Performance Based on Change in Delivery Date (Item Level), Open Qty(Item Level) and Statistics-relevant delivery date (Header Level).
For that the field Open Qty - OBMNG is relevant.
Pls do suggest me in which DB table should i search and retreive the data's for this feild.
Thanks & Regds.
Ramesh.

Hi Max Bianchi,
Any idea how to get the field value of OBMNG(Open Qty), B'cas u told it is calculated at runtime, then is it possible for to retrevive it or store in any other DB.
Pls do suggest me.
Thanks and Regds.
Ramesh.

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

Purchase Order Printout only after po release

Dear All,
Plz help me with the below mention problem :
i donot want the purchase order to get printed untill the po get released completely, plz suggest me required configuration need to be done regarding this
regds
joy

Hi Joy,
You can adopt a release procedure where in you can block a PO for printing unlease its release strategy is fulfilled.
Please go though below documents and grant me points if it works for you.
Release Purchase Orders (MM-PUR)
Technical name: SAP_MM_PUR_PO_RELEASE
Tasks
You can use this role to release (approve) purchase orders.
A purchase order may be blocked via a release procedure (if its total value exceeds a predefined value - say $10,000 - for instance). Before this purchase order can be outputted (printed out or transmitted directly to the vendor), it must be approved (i.e. released).
Activities in Materials Management
Activity
Transaction
Release purchase order
ME28
Regards,
Subha

Viewing purchase requisitions/purchase orders

Hi Every body,
Can anybody guide me any transactions to view purchase requisitions/purchase orders/planned orders at a glance for the selected materials
Regards,
Manish

Hi check with this
ME52N     Change Purchase Requisition
MEMASSRQ     Mass-Changing of Purch. Requisitions
ME53N     Display Purchase Requisition
ME51N     Create Purchase Requisition
ME56     Assign Source to Purch. Requisition
ME57     Assign and Process Requisitions
ZPRPRINT
ME54N     Release Purchase Requisition
ME55     Collective Release of Purchase Reqs.
ME5F     Release Reminder: Purch. Requisition
ME5A     Purchase Requisitions: List Display
ME5K     Requisitions by Account Assignment
ME26     Display PO Supplement (IR)
ME24     Maintain Purchase Order Supplement
MEPO     Purchase Order
ME23N     Display Purchase Order
ME22N     Change Purchase Order
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Z
ME9F     Message Output: Purchase Orders
ME2W     Purchase Orders for Supplying Plant
ME2M     Purchase Orders by Material
ME2K     Purch. Orders by Account Assignment
ME2B     POs by Requirement Tracking Number
MELB     Purch. Transactions by Tracking No.
ME2C     Purchase Orders by Material Group
ME2N     Purchase Orders by PO Number
ME2A     Monitor Confirmations
ME80FN     General Analyses (F)
ME81N     Analysis of Order Values
ME2L     Purchase Orders by Vendor
ME1P     Purchase Order Price History
ME22N     Change Purchase Order
MEPO     Purchase Order
ME23N     Display Purchase Order
ME24     Maintain Purchase Order Supplement
ME22N     Change Purchase Order
ME26     Display PO Supplement (IR)
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Z
ME9F     Message Output: Purchase Orders
MELB     Purch. Transactions by Tracking No.
ME2N     Purchase Orders by PO Number
ME2M     Purchase Orders by Material
ME2K     Purch. Orders by Account Assignment
ME2C     Purchase Orders by Material Group
ME2B     POs by Requirement Tracking Number
ME2W     Purchase Orders for Supplying Plant
ME2A     Monitor Confirmations
ME80FN     General Analyses (F)
ME81N     Analysis of Order Values
ME2L     Purchase Orders by Vendor
ME1P     Purchase Order Price History
ME22N     Change Purchase Order
ME26     Display PO Supplement (IR)
MEPO     Purchase Order
ME22N     Change Purchase Order
ME23N     Display Purchase Order
ME24     Maintain Purchase Order Supplement
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Thanks & Regards
Mangal

Smartform in Purchase Order ME21N

Hi guys.
I'm working in SAP 6.0 ECC. I am developing a sapscript for purchase order and it is working well, but i wanna do the same in smartform, i checked on the web that sap 6.0 ecc has some standard smartform for Purchase Order, but mine doesnt have it. In addition, i tried to convert my sapscript to smartform, but the only thing that converts are the windows, no tables or variables, so it doesnt work.
how can i do it? somebody did a smartform for ME21N??? what are the parameters that i need to use? the idea is that this smartform will be trigged at the moment of release the purchase order throught ME29N.
Regards
it will be super usefull that somebody could send me a smartform

Sending attachments by mail is not really compliant with forum rules (because other people won't get the information).
The good answer would have been to look at SDN "smart forms" home page, then look at section "preconfigured smart forms".
It says that it must be downloaded from SWDC (SAP software download center), choose Installations and Upgrades -> ...Entry by Application Group -> SAP Best Practices -> SAP BP BASELINE PACKAGE ...

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

ME28 Cancel release of purchase order

Hello,
when I try to perform a cancellation of a release of a PO I get an error message:
ME 175 Document already treated. Function not possible
It should be possible to cancel the release of alll released purchase orders. Can you help me?
Thanks a lot!

Hi,
please read the following:
                                                                                Note 493900 /12. Question :
Is it possible to cancel a release strategy when the purchase order has
been printed out ?
Answer :
With ME29N you cannot cancel a release strategy once the document has
been printed out. This behaviour constitutes a new design. Regarding
ME28 it has been decided to keep the old behaviour and you can cancel
the release if there is at least one message type which has not been
printed out.
Please note AT LEAST ONE message type has NOT been printed out with
ME28.
Alternatively, you can try the following:
- Transaction: SPRO
->MM->Purchasing->PO->Release procedure for PO
->Define relesae procedure for PO
->Release Strategies
->Release Status
- choose the button release indicator and
5   Changeable, new release if new strategy/outputted
6   Changeable, new rel. if new strat. or value change/outputted
- go into transaction ME22(N)
- you will get the warning message 06 684 stating
'Releases already effected are liable to be reset'
- change the price and save the p.o.. Now a change message will be
created and will be send to the vendor again.
- Please note that the release strategy will only be reset if the price
is increased. When it is decreased it won't be reset. But in both
cases a change message will be created and send to the vendor.
- after the change of the p.o. you will have to release it again. After
the release the change message will be printed.
Hope this will help to solve the issue,
regards,
Edit

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.

Printing for ME28 (Purchase Order Release)

Hello all,
I have a question regarding ME28. When we execute the release function for a list of Purchase Orders, the output type - NEU gets print out automatically. I would like to ask is this a standard function of SAP MM module. Or do we have to do configuration in order to have this?
In case configuration is required, can anyone tell me where it is in SPRO.
Thanks.

Hi,
Check Dispatch time maintaioned in t.code: MN06 for your output type( message type).Also chcek in NACE t.code for application EF with output type{ by double clicki} for default values segment which dispatch time maintaioned.
For more on Dispatch time , check the link:
Re: Message Types in PO
Regards,
Biju K

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.

ME28- purchase order is proposed althoght items are deleted

hi
i have the following problem:
A purchase order in our production system is proposed again for release after all items were deleted.
I want to know why its happend and a way to resolve this problem
Thanks in advance for your help
Enzo
Message was edited by:
        enzo francescoli

thanks for your soon answer.
I dont understand what you are proposing me. What i want to know because the PO continues appearing to be released if the same one were deleted.
Some of this PO before being deleted, they were released, but know still apearing.
thanks for your help, and if you can explain to me with more datail i will thank for it.
Best regards
Enzo
Message was edited by:
        enzo francescoli
Message was edited by:
        enzo francescoli

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

Email on the release of purchase order

hi,
the requirement is that, when the purchase order is released and saved in me28/me29n .then a email should be triggered to the concernd vendor .
is there any standard procedure for this.
As in NACE tcode,there is output type(NEU) for purchase order(EF),in the processing routines view- there is a processing routine with the row.
External send SAPFM06P ENTRY_NEU MEDRUCK
what does this signify.
plz help
regards,
johnson
Edited by: johnson george on May 30, 2008 3:01 PM
Edited by: johnson george on May 30, 2008 3:04 PM

SAP marketplace - notice 191470 - Purchase order as an e-mail -
regards Jörg

Regd: Purchase Order ME28 & ME29N

Similar Messages

Maybe you are looking for