Status of a purchase order

hi
  i want to know status of a purchase order (i.e. a PO is pendding , closed, invoice pending , complete like this).
there is report (t.code ME2N) which gives details of PO's
by giving INPUT to 4th SELECT-OPTIONS (tittled as SELECTION PARAMETERS), here in this many options are available .
         i searched for these options , these get stored in table T160S ,But i am not able to under how corresponding to these values program is picking all related data from other tables like EKKO,EKPO.
         how it is relating these tables.
plz help.

Hi sachin,
           IN PO in item details screen you will find delivery tab. In that if delivery completed is checked then it means that item is closed.In the similar way if all the items of PO are delivery completed PO can treated as closed.This info may be helpful to you.
Reward if helpful.
Regards,
Kalyan.

Similar Messages

  • Status Change for Purchase order in Process Purchase order

    Hi All,
    We have implemented SRM 4.0 with Extended Classic scenario.
    SRM does provide standard status for Process Purchase order worklist (such as Ordered, Held, Error in Process etc.). Is there any BADI i can use to overright my own status message for the PO.
    To give brief background of the requirement. Client wanted status to be changed to "Cancel" For POs whose all the line items we have deleted or "Close" when Last delivery or Final Invoice check is ticked.
    I am aware that i can use BBP_DOC_SAVE_BADI as structure BBP_PDS_ITEM i can get items deletion indicator. But will i able to change the standard Status message?
    Presently even though all line items marked delete still shows PO as "Ordered" status.
    Kindly let me know if i can acheive with anyway.
    Thank you
    Ritesh

    Hi Masa,
    Thank you for your response. I have few doubts about the configuration which you have suggested.
    - Define Status schema for User status will create a status Profile in which i have to include my own status. In the document of Define Status Schema it specifies that After creating User profile you have to assign same profile to transaction types. (I.e. BUS2201 or BUS2121 etc).
    My concern is will my own status profile over-write the standard status which is coming? such as Ordered, Created, Transmission fail etc.
    If so then do i have to create status profile to include all the Standard Status message in it as well?
    - Other thing i found that Ordering PO goes through many standard status message (COMP, CRTD, CTRA, DCOM, ORDR) and always the last status in the Hearder will display on  ITS level. Is my understanding right?
    - I found that there is a standard system status message I1045 (BECN Cancel) Can i use this through BADI?
    Kindly let me know.
    Thank you once again.
    Regards
    Ritesh

  • Status table for purchase orders

    Hi experts,
    When a purchase order is accepted by someone it changes its status. Is there any table that i can select from it to obtain the worker who changed the status of a purchase order?
    Thank you all,
    Artur.

    hi,
    Try to check the table EKBE (History per Purchasing Document).
    and also check CDPOS and CDHDR table
    I guess her you find the all the required details

  • Define status for backend purchase order in SRM7.02

    Hi,
    i am working in SRM 7.02 classic scenario using PI.
    When the SC is converted to Backend PO, some PO XML are failed due to various reason. Instead i need to create a PO in held status.
    For the same, we have settings 'Define status for Backend purchase order' in SPRO. If we maintain the information in this setting that is enough..??It will work??
    1.I heard there is some enhancement need to done for the same to work ...??if it is what is the enhancement ???
    2. if it is work, then all PO will be created in Held status or only error PO will be created in Held status?? remaining in released status ???
    Kindly advice me ..
    Thanks

    As far as,  BAPI_PO_CREATE1, you need to pass
    MEMORY_UNCOMPLETE = abap_true
    MEMORY_COMPLETE   =  abap_false
    for POHEADER, pass,
    MEMORY = 'X'
    MEMORYTYPE = 'H'
    for POHEADERX, pass,
    MEMORY = 'X'
    MEMORYTYPE = 'X'
    Though you will be using ESOA for this, this knowledge would help.
    Regards,
    Ganapathi

  • PTP - Change to stock type field status configuration in Purchase Order

    When creating or changing a PO for direct material - or even during goods receipt, the stock type field which by default is "X - Quality Inspection" can be changed to "Unrestricted Use" by the purchasing personnel.  This is not in line with QA requirements where the change from QI to Unrestricted use can only be done by QA personnel.
    Need to configure the system not to allow purchasing personnel to change the status.
    Please tell me  where i need to configure the above requirement.
    Regards
    Sreekanth

    HI,
    You will need to change screen layout at document level in ME21N and ME22N. Follow below steps
    SPRO -> Mateial Management -> Purchasing -> Purchase Order -> Define Screen Layout at Document levle -> ME21N -> Look for Quality Inspection (I believe this is the field, I did not test it) and make it Display only. By default it comes as Optional entry.
    Regards,

  • 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

  • Workflow statuses of a purchase order

    Hi
    I'm looking to get the workflow statuses for some of the steps(Task items) for a purchase order...
    Basically I want to know how to get the data shown in SWI1 for a specific workitem in a report...?
    Can anyone help..
    Thanks
    Geetha

    Hi .
    check out the below link for workflow of purchase order.
    [http://help.sap.com/saphelp_srm30/helpdata/en/5a/c5173f5ff48443e10000000a114084/content.htm]
    Thanks
    Ankul

  • Status codes in Purchase Order Response screen

    Hello,
       I still relatively new to SRM and have a question on how the status codes on the purchase order response screen works.
    Specifically what is the logic / selection criteria for "Variance in Purchase order Response"? My initial analysis is that this displays variance against the Original PO values rather than the current PO values if they have been updated to matched the POR.
    Thanks
    Gary

    Thanks Ravi but I belive that we do not use SUS. Suppliers interface with SRM via a web portal.
    Any suggestions where I can find detailed user / functional documentation on what each of the search parameters mean ?
    Thanks again
    Gary

  • User Status Profile for Purchase order

    hi
    Can any one help me how to created user statuses other than system status for Purchase order? where to assign it to PO document type.
    Rajendra

    Dear Rajendra,
    I'm not sure there a standard field for user status in PO, you have to custom it, but it's not recommended.Perhaps u should check what if the critical use for this user status before u    continue to custom.
    regards

  • Status Tab in Purchase order header

    Hi All,
    The status tab in the PO header is not getting updated properly. This issue is not coming for all the PO's & not a repetitive issue.
    In some of the PO's the invoice quantity & value is shown less, but the PO has been completely invoiced.
    All the PO's are account assigned PO's
    I am not able to find the reason for such behaviour.Please let me know if any of you have a solution.
    Thanks & Regards
    Kishore Kumar

    Hi
    I have already specified the PO's have been completely invoiced.
    Thansk & Regards
    KIshore

  • Status in purchase order

    1.Where do i see the workflow for a purchase order.
    2. There are 6 status in purchase order, can someone give me the link or document about the status?
    Regards
    Sudharshan

    1. Workflow for a PO can be seen from the navigation given below.
    Purchasning > Purchase Orders > Purchase Order Summary > Inquire (M) > View Approval through workflow.
    2. Use the Control Documents window to control requisitions and requisition lines as well as purchase orders, purchase order lines, releases, and shipments. For requisitions, the only available actions are Cancel and Finally Close. Only control options appropriate for the selected requisition or purchase order are displayed in the Actions field. The following control actions are available in this window:
    Cancel - If you use on-line requisitions, and you cancel a purchase order you did not receive or pay at all, Purchasing cancels the requisition lines associated with the purchase order if the Cancel Requisitions check box is selected. If the Cancel Requisitions check box is not selected, the requisition lines are not cancelled and are returned to the pool of available requisitions. You can then assign these requisition lines to new purchase orders to fulfill your requestors' needs. See: Defining Control Options.
    If you use on-line requisitions with quantity or amount based line types, and you cancel a partially received purchase order line, Purchasing recreates requisition lines for the remainder of the maximum of the billed or received quantity you have not received. You can assign these requisition lines to a new purchase order line to fulfill the requestor's needs. See: Autocreate Document Options. If you have implemented Oracle Services Procurement and use on-line requisitions with rate or fixed price line types, no requisition lines are recreated.
    If you are using encumbrance or budgetary control, Purchasing automatically creates negative debit entries in your general ledger system to cancel the encumbrance that corresponds to the purchase order header, lines, or shipments you are cancelling, using the action date you specify in Action Date. Purchasing recreates requisition encumbrances for the requisition lines you used to create the purchase order if the Cancel Requisitions check box is not selected. Purchasing uses the distributions from your cancelled purchase order to recreate the encumbrance for your requisition. See: Budgetary Control and Online Funds Checking.
    After you partially or completely cancel a purchase order, you need to inform your supplier of the cancellation. You can communicate purchase orders or releases you partially or completely cancelled. Purchasing automatically inserts a cancellation message on the purchase order, purchase order line, purchase order shipment, or release you cancelled.
    You can source a requisition line from a line in the Prior Purchases region of the Supplier Item Catalog window. (A line in the Prior Purchases region corresponds to a purchase order line.) However, Purchasing does not automatically update the corresponding sourcing information if you cancel a blanket agreement or agreement line with which you source requisition lines. If you cancel a blanket agreement or agreement line, be sure to update the corresponding information in the Requisition Templates or the Sourcing Rules window. See: Defining Requisition Templates. See: Automatic Sourcing.
    Close - You can close at the header, release, line, and shipment levels.
    Close for Invoicing - You can close for invoicing at the header, release, line, and shipment levels. Note that if you close for invoicing a purchase order header that is currently open, Purchasing sets the status of all purchase order shipments to Closed for Invoicing, but the purchase order lines and header remain open. This status will not prevent you from matching an invoice to the purchase order or to the receipt.
    Close for Receiving - You can close for receiving at the header, release, line, and shipment levels. Note that if you close for receiving a purchase order header that is currently open, Purchasing sets the status of all purchase order shipments to Closed for Receiving, but the purchase order lines and header remain open.
    Finally Close - You can final close at the header, release, line, and shipment levels. Purchasing automatically closes fully billed and received purchase orders. However, to prevent further actions on the purchase order, you should use this window to final close purchase orders. Finally Close prevents modifications to the purchase order. Also, if you are using encumbrance or budgetary control, Finally Close automatically creates credit encumbrance journal entries in your general ledger system to reverse the encumbrance that corresponds to the purchase order header, lines, or shipments you are closing, using the action date you specify in Action Date. See: Budgetary Control and Online Funds Checking.
    Freeze - You can freeze only at the header and release level. You freeze a purchase order when you want to prevent any future modifications to the purchase order. When you freeze a purchase order, you can still receive and pay for goods you already ordered. If you want to prevent future receipt or matching invoices against this purchase order, cancel or final close the purchase order instead.
    On Hold - You can place a purchase order on hold only at the header level. This unapproves the purchase order while preventing printing, receiving, invoicing, and future approval until you remove the hold.
    Open - You can open at the header, line, and shipment levels.
    Open for Invoicing - You can reopen for invoicing at the header, line, and shipment level.
    Open for Receiving - You can reopen for receiving at the header, line, and shipment level.
    Release Hold - You can release a hold only at the header level.
    Unfreeze - You can unfreeze only at the header and release levels.

  • VKM1 Status and Purchase Order Fields

    Hi Everyone,
    I'm new with SD and not familiar with transaction VKM1. I have a task that needs to get the corresponding Status field and Purchase Order field for a corresponding VBELN. To what table can I map these data?
    Please help.
    Many Thanks!

    Hi
    Kindly use the belwo  tables and fields
    VBAK--BSTKD --POurchase order
    VBUP-GBSTAOverall processing status of the SD document item
    Regards
    Damu

  • Purchase Order

    Hi all,
    i have two doubts related to the purchase order.
    1. How to know the Status of the purchase order
    ex: Open , Closed
    2. How to get the Purchasing Quantity (KOMV-KAWRT)
    Please Advice me..
    Many thanks for all of your help.
    Regards,
    Lakshma.

    Hi
    Here is the code to find out the open purchase order.
    List of open purchase orders for a given plant/delivery period      *
      A purchase order is open when the delivery completed indicator = ' '*(field elikz.ekpo = space)
    Tables
    TABLES: EKKO,                          "Purchase order - header"
            EKPO,                          "Purchase order - lines"
            EKET,                          "Purchase order - delivery date"
            EKBE,                          "Purchase order - history
            LFA1,                          "Supplier - general info"
            STXH,                          "Text table - header info"
            T001W,                         "Plant description table
            MARA,                          "Material master
            MAKT,                          "Material description table
            T163X.
    DATA: BEGIN OF TXTF_HEADER.            "Purchase order header texts
            INCLUDE STRUCTURE THEAD.
    DATA: END OF TXTF_HEADER.
    DATA: BEGIN OF TXTF_LINES OCCURS 2.    "Purchase order header texts
            INCLUDE STRUCTURE TLINE.
    DATA: END OF TXTF_LINES.
    DATA: WNAME(70),
          WLPEIN(1),
          WEINDT(10),
          WMENGE LIKE EKET-MENGE,
          WBISMT LIKE MARA-BISMT,
          W_HISTORY(1).
    SELECT-OPTIONS : S-EINDT FOR EKET-EINDT.
    SELECT-OPTIONS : S-WAERS FOR EKKO-WAERS.
    FIELD-GROUPS : HEADER, GROUP1.
    INSERT EKPO-WERKS
           EKET-LPEIN
           EKET-EINDT
           EKPO-EBELN
           EKPO-EBELP
           EKPO-MATNR
           EKKO-WAERS
           EKKO-WKURS
           EKKO-KUFIX
           EKKO-BEDAT INTO HEADER.
    INSERT EKKO-SPRAS
           EKKO-EKGRP
           T163X-EPSTP
           EKPO-TXZ01
           EKPO-KONNR
           EKPO-KTPNR
           EKET-MENGE
           EKPO-MEINS
           EKPO-LGORT
           EKET-WEMNG
           EKPO-NETPR
           EKPO-PEINH
           EKPO-BPRME
           EKPO-NETWR
           EKKO-LIFNR
           W_HISTORY  INTO GROUP1.
    General data
    INITIALIZATION.
    EM_SELKB = 'X'.
    EM_SELKK = ' '.
    EM_SELKL = ' '.
    EM_SELKA = ' '.
    Start of program
    START-OF-SELECTION.
    Read purchase order items for this plant with delivery completed
    indicator = space
    GET EKPO.
      SELECT * FROM T163X WHERE SPRAS EQ SY-LANGU
                          AND   PSTYP EQ EKPO-PSTYP.
        EXIT.
      ENDSELECT.
      IF SY-SUBRC NE 0.
        T163X-EPSTP = EKPO-PSTYP.
      ENDIF.
      CHECK S-WAERS.
    GET EKET.
      CHECK S-EINDT.
      IF EKPO-ELIKZ = ' ' AND EKPO-LOEKZ = ' '.
       if eket-wemng = 0 and eket-wamng = 0.
            CLEAR : W_HISTORY.
            SELECT * FROM EKBE WHERE EBELN = EKPO-EBELN
                               AND   EBELP = EKPO-EBELP.
               EXIT.
            ENDSELECT.
            IF SY-SUBRC = 0.
               MOVE '*' TO W_HISTORY.
            ENDIF.
            EXTRACT GROUP1.
       endif.
      ENDIF.
    END-OF-SELECTION.
    Sort by plant - delivery date
      SORT.
      FORMAT INTENSIFIED OFF.                      "PPL26041995
      LOOP.
      read vendor
        SELECT SINGLE * FROM  LFA1
               WHERE  LIFNR       = EKKO-LIFNR.
        IF SY-SUBRC <> 0.
          MOVE '???' TO LFA1-NAME1.
        ENDIF.
      search old materialnumber if needed
        SELECT SINGLE * FROM  MARA
               WHERE  MATNR       = EKPO-MATNR.
        IF SY-SUBRC <> 0.
          MOVE '???' TO WBISMT.
        ELSE.
          MOVE MARA-BISMT TO WBISMT.
        ENDIF.
      read purchase order header text - first 2 lines of delivery text
        CLEAR TXTF_LINES.
        CLEAR TXTF_HEADER.
        REFRESH TXTF_LINES.
        MOVE EKPO-EBELN TO WNAME.
        MOVE EKPO-EBELP TO WNAME+10.
        SELECT SINGLE * FROM STXH
             WHERE TDID     = 'F04' AND
                   TDOBJECT = 'EKPO' AND
                   TDNAME   = WNAME AND
                   TDSPRAS  = EKKO-SPRAS.
        IF SY-SUBRC = 0.
          CALL FUNCTION 'READ_TEXT'
               EXPORTING
                    ID              = 'F04 '
                    LANGUAGE        = EKKO-SPRAS
                    OBJECT          = 'EKPO      '
                    NAME            = WNAME
               IMPORTING
                    HEADER          = TXTF_HEADER
               TABLES
                    LINES           = TXTF_LINES
               EXCEPTIONS
                    ID              = 01
                    LANGUAGE        = 02
                    NAME            = 03
                    NOT_FOUND       = 04
                    OBJECT          = 05
                    REFERENCE_CHECK = 06.
        ENDIF.
        READ TABLE TXTF_LINES INDEX 1.
    print list
        RESERVE 3 LINES.
        AT NEW EKPO-WERKS.
          SELECT SINGLE * FROM T001W WHERE WERKS = EKPO-WERKS.
          IF SY-SUBRC NE 0. CLEAR T001W. ENDIF.
          NEW-PAGE.
        ENDAT.
        CLEAR WEINDT.
        CLEAR WLPEIN.
        AT NEW EKET-EINDT.
          CALL FUNCTION 'PERIOD_AND_DATE_CONVERT_OUTPUT'
               EXPORTING
                    INTERNAL_DATE   = EKET-EINDT
                    INTERNAL_PERIOD = EKET-LPEIN
               IMPORTING
                    EXTERNAL_DATE   = WEINDT
                    EXTERNAL_PERIOD = WLPEIN.
        ENDAT.
        WRITE: /    WLPEIN,
                  3 WEINDT,
                 13 SY-VLINE(1),
                 14 EKPO-EBELN,
                 25 EKPO-EBELP+3(2),
                 28 T163X-EPSTP,
                 31 EKPO-MATNR,
    add old material number
               52 wbismt,
                 62 EKET-MENGE,
                 80 EKPO-MEINS,
                 85 EKKO-LIFNR,
                116 SY-VLINE(1),
              127 txtf_lines-tdline(40),
                118 EKKO-WAERS,
                122 EKPO-NETPR,
                142 EKPO-PEINH,
                152 EKPO-BPRME,
                157 EKPO-NETWR,
                177 EKKO-WKURS,
                190 EKKO-KUFIX,
                193 EKKO-BEDAT,
                206 EKKO-EKGRP,
                211 SY-VLINE,
                216 W_HISTORY.
    add storage location
              171 sy-vline, ekpo-lgort,
              178 sy-vline.
        READ TABLE TXTF_LINES INDEX 2.
        SELECT SINGLE * FROM MAKT WHERE MATNR = EKPO-MATNR
                                  AND   SPRAS = SY-LANGU.
        IF SY-SUBRC NE 0.
          MOVE EKPO-TXZ01 TO MAKT-MAKTX.
        ENDIF.
        WMENGE = EKET-MENGE - EKET-WEMNG.
        IF EKPO-KONNR = SPACE.
          WRITE:/13 SY-VLINE(1),
                  MAKT-MAKTX(30) UNDER EKPO-MATNR,
                  WMENGE     UNDER EKET-MENGE,
                  LFA1-NAME1 UNDER EKKO-LIFNR,
            126 sy-vline(1),
                txtf_lines-tdline(40) under txtf_lines-tdline,
              116 SY-VLINE(1),
            171 sy-vline(1),
              211 SY-VLINE(1).
        ELSE.
          WRITE:/13 SY-VLINE(1),
                ekpo-konnr under ekpo-ebeln,
                ekpo-ktpnr+3(2) under ekpo-ebelp,
                  MAKT-MAKTX(30) UNDER EKPO-MATNR,
                  WMENGE     UNDER EKET-MENGE,
                  LFA1-NAME1 UNDER EKKO-LIFNR,
            126 sy-vline(1),
                txtf_lines-tdline(40) under txtf_lines-tdline,
            167 sy-vline(1),
              116 SY-VLINE(1),
              211 SY-VLINE(1).
        ENDIF.
        ULINE /13(207).
        AT END OF EKET-EINDT.
           ULINE 1(12).
        ENDAT.
      ENDLOOP.
    print delivery date with first line.
    TOP-OF-PAGE.
       CALL FUNCTION 'PERIOD_AND_DATE_CONVERT_OUTPUT'
            EXPORTING
                 INTERNAL_DATE   = EKET-EINDT
                 INTERNAL_PERIOD = EKET-LPEIN
            IMPORTING
                 EXTERNAL_DATE   = WEINDT
                 EXTERNAL_PERIOD = WLPEIN.
      CALL FUNCTION 'Z_PRINT_TITEL'               "PPL24041995
           EXPORTING PROGNAME = 'ZMCH0089'         "PPL24041995
                     TEXTTYPE = 'T'                "PPL24041995
                     ORG_PROGNAME = ' '
                     PARAM_1  = EKPO-WERKS                "PPL24041995
                     PARAM_2  = T001W-NAME2                "PPL24041995
                     PARAM_3  = ' '                "PPL24041995
                     PARAM_4  = ' '                "PPL24041995
                     PARAM_5  = ' '.               "PPL24041995
    Reward if helpful.
    Chandralekha

  • 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

  • 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

Maybe you are looking for

  • Complete newbie looking for direction

    C# developer for Windows - have been doing Outlook-based addins for a while. Looking to port something similar to Mac. Need plug-in (or something similar) integration into Ical, mail and the contact address database. Can this be done? Want to a) add

  • Service Endpoint Interface and RemoteException question on the server

    Hello, I would like to be able to log and track RemoteExceptions when the network goes down when an attempt to send a response back to the client. I understand that Weblogic will handle the RemoteException but especially on a network failure I would

  • Migration of Authorisation from bw 3.5 to bw 7.0

    Hi All, Plaese provide me how does migration of authorisation takes place from bw 3.5 to bw 7.0. Please provide me the material its needed urgently. :Points will be rewarded

  • Chart Computed Items info

    Is there anyway to know via Java Script which Facts in a Chart are computed items?

  • Too many recipients

    After initially posting this question in the wrong forum and declaring myself a forum muppet, I have decided to post this question in the correct forum. Here goes. I have up until a week ago been able to send mail to multiple recipients. However, in