Partial delievery - Purchase Order

Hi gurus,
Anybody please provide document to make Purchase order with partial delivery.
I want to order 40000m quantity of pipe, agreed with vendor for accepting partial deliveries i.e(4 slots). So while issuing PO need to mention partial delivery to make invoice at that time of goods receival.
Searched in SDN, mentioned set partial del. indicator in PO, but i dont find that. please guide.
Thanks in advance,
Raksh,

Hi,
Kindly check the over delivery tolerance field in the delivery tab of the po line item.The partial delivery/item field will only be shown for your stock transfer order. please refer the link below.hope it helps.
http://help.sap.com/saphelp_crm40/helpdata/en/dd/5607f4545a11d1a7020000e829fd11/content.htm
http://help.sap.com/saphelp_45b/helpdata/en/a5/63343943a211d189410000e829fbbd/frameset.htm

Similar Messages

  • How to create partially received Purchase Order using PDOI?

    Hello All,
    We are using 12.1.3
    We have requirement to create PO with partially received quantity. Can it be possible through Purchase Order Import Interface program? I can not see any column there in po_line_location_interface table for quantity that has been received or shipped. So can anybody tried this scenario. If please revert back with the answer this is very urgent.
    Thanks in Advance...!!!
    Amol

    Thanks Sandeep,
    But PDOI allows us to enter quantity_billed on the PO. Have you ever faced such scenarios. Because I am doing conversion and I got stuck at the partial receiving.
    Also I have to do a drop ship POs conversion, do you have any code snippet for drop shipment. If yes please share it or else any metalink doc id.
    Thanks In Advance......!!!

  • RE: Auto-close all OPEN/Partially open Purchase Order

    Hi,
    Is there a standard program that will perform auto-closing of all open or partially open PO whcih does not have GR for the past 3 months?
    if no, if I need to customize an ABAP to close it off, which are the tables needed to be changed?
    EKKO, EKPO, EKET and what other tables?
    Thanks
    bye

    Hi,
    i think there is a exit to close POs by defined criterias.
    Manually u could use transaction mass (bus2012) and set the delivered mark in the ekpo table.
    regards, Paul.

  • Urgent :Doubt on open Purchase orders

    Hi friends,
    i will be more help full if anybody can help me on below issue how to find open PO and partially open PO.
    Only “open” purchase orders will be extracted for conversion into Destination Server. An “open” purchase order is defined as any unshipped, non-cancelled with “open quantities”. In regards to, partially “open” purchase orders, we will only convert “open” units (i.e. Original ordered qty was 300; 70 have shipped, 230 remain open…Target Server sales order will have an original order qty of 230).
    also where to find that Sub Contracting orders and Sample orders.
    • Orders not considered for migration because they will have either shipped in full or deleted prior to data migration as a part of data clean-up: ALL subcontracting orders; sample orders
    please help me on the above two issues.
    thanks and Regards,
    Gokul.

    Hi
    First take the ALL Po's from EKKO and EKPO tables and check for the different GR's and GI's qty's from MKPF and MSEG tables and you have to compare the PO qty with the total GR/GI qty's and to find the OPEN po's
    see the sample report
    *& Report  ZMM_PO_REPORT
    REPORT  ZMM_PO_REPORT message-Id yb
           NO STANDARD PAGE HEADING
           LINE-COUNT 60(1)
           LINE-SIZE 230.
           D A T A B A S E  T A B L E S   D E C L A R A T I O N
    TABLES: lfa1,           " Vendor Master
            t161,           " PO Doc Types
            t024,           " Purchase Groups
            ekko.           " PO Header
                   T Y P E S  D E C L A R A T I O N S
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_po,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bukrs TYPE bukrs,           " Company Code
            bsart TYPE bbsrt,           " PO Type
            lifnr TYPE lifnr,           " Vendor No
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
           END OF s_po.
    Purchase Orders History Structure
    TYPES: BEGIN OF s_account,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            gjahr TYPE mjahr,           " Fiscal Year
            belnr TYPE mblnr,           " PO Invoice No
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Local Currency
            dmbtr TYPE dmbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
            shkzg TYPE shkzg,           " Dr/Cr Indicator
           END OF s_account.
    Purchase Orders History Structure(Item Sum)
    TYPES: BEGIN OF s_inv_sum,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
           END OF s_inv_sum.
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_rep,
            lifnr TYPE lifnr,           " Vendor No
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bsart TYPE bbsrt,           " PO Type
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
            name1 TYPE name1,           " Plant
            orewr TYPE netpr,           " To be Invoiced Price
            curr  TYPE waers,           " Inv Doc Currency
           END OF s_rep.
               D A T A  D E C L A R A T I O N S
    DATA: gv_title1 TYPE sylisel,            " Report title
          gv_dial.                           " Color flag
                C O N S T A N T S  D E C L A R A T I O N S
    CONSTANTS: c_x                VALUE 'X',   " Flag X
               c_h                VALUE 'H',   " Debit
               c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
         I N T E R N A L  T A B L E S  D E C L A R A T I O N S
    DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                                 " Purchase Order
          i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                         " PO Invoice Values
          i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                     " PO Invoice Values
          i_ekbe  TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                               " PO Invoice Values
                     S E L E C T I O N  S C R E E N                      *
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                    s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                    s_bsart FOR t161-bsart,
                    s_ekgrp FOR t024-ekgrp,
                    s_bedat FOR ekko-bedat.
    SELECTION-SCREEN END OF BLOCK b1.
                      I N I T I A L I Z A T I O N                        *
    INITIALIZATION.
                  A T  S E L E C T I O N - S C R E E N                   *
    AT SELECTION-SCREEN.
    Validate the screen fields
      PERFORM validate_screen.
                   S T A R T - O F - S E L E C T I O N                   *
    START-OF-SELECTION.
    Fetch main data
      PERFORM fetch_data.
                   T O P - O F - P A G E                                 *
    TOP-OF-PAGE.
    Header of the List
      PERFORM header.
                   E N D - O F - P A G E                                 *
    Footer
    END-OF-PAGE.
      ULINE.
                   E N D - O F - S E L E C T I O N                       *
    END-OF-SELECTION.
    Display the Report Output data
      PERFORM display_data.
    At Line-Selection
    AT LINE-SELECTION.
    When double clicked on EBELN display the details of Purchase Doc
      PERFORM line_sel.
    *&      Form  validate_screen
    Validation of Selection Screen fields
    FORM validate_screen .
    Validation of Vendor Number
      CLEAR lfa1-lifnr.
      IF NOT s_lifnr[] IS INITIAL.
        SELECT lifnr UP TO 1 ROWS
            INTO lfa1-lifnr
            FROM lfa1
            WHERE lifnr IN s_lifnr.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Vendor'(002).
        ENDIF.
      ENDIF.
    Validation of PO Number
      CLEAR ekko-ebeln.
      IF NOT s_ebeln[] IS INITIAL.
        SELECT ebeln UP TO 1 ROWS
            INTO ekko-ebeln
            FROM ekko
            WHERE ebeln IN s_ebeln.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Document Number'(003).
        ENDIF.
      ENDIF.
    Validation of PO Document Type
      CLEAR t161-bsart.
      IF NOT s_bsart[] IS INITIAL.
        SELECT bsart UP TO 1 ROWS
            INTO t161-bsart
            FROM t161
            WHERE bsart IN s_bsart.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
        ENDIF.
      ENDIF.
    Validation of Purchasing Group
      CLEAR t024-ekgrp.
      IF NOT s_ekgrp[] IS INITIAL.
        SELECT ekgrp UP TO 1 ROWS
            INTO t024-ekgrp
            FROM t024
            WHERE ekgrp IN s_ekgrp.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
        ENDIF.
      ENDIF.
    ENDFORM.                    " validate_screen
    *&      Form  fetch_data
    Fetching the PO related data from Database Tables
    FORM fetch_data .
      CLEAR i_po.
      REFRESH i_po.
      SELECT a~ebeln            " PO No.
             b~ebelp            " PO Item
             a~bstyp            " PO Category
             a~bukrs            " Company Code
             a~bsart            " PO Type
             a~lifnr            " Vendor No
             a~ekgrp            " Purchase Group
             a~waers            " Currency
             a~bedat            " PO Date
             b~txz01            " Material Text
             b~werks            " Plant
             b~lgort            " Storage Location
             b~matkl            " Material Group
             b~menge            " PR Quantity
             b~meins            " UOM
             b~bprme            " Price Unit
             b~netpr            " Net price
             b~peinh            " Price Unit UOM
             b~pstyp            " Item Category
             b~knttp            " Account Assignment Category
        INTO TABLE i_po
        FROM ekko AS a JOIN ekpo AS b
        ON a~ebeln = b~ebeln
        WHERE a~ebeln IN s_ebeln AND
              a~lifnr IN s_lifnr AND
              a~ekgrp IN s_ekgrp AND
              a~bsart IN s_bsart AND
              a~bedat IN s_bedat.
      SORT i_po BY ebeln ebelp.
      break-point.
      IF NOT i_po[] IS INITIAL.
    Fetch the PO History/Invoice Details from EKBE Table
        CLEAR i_ekbe.
        REFRESH i_ekbe.
        SELECT ebeln           " PO No.
               ebelp           " PO Item
               gjahr           " Fiscal Year
               belnr           " PO Invoice No
               menge           " PR Quantity
               wrbtr           " Price in Local Currency
               dmbtr           " Price in Foreign Currency
               waers           " Currency
               shkzg           " Dr/Cr Indicator
         INTO TABLE i_ekbe
         FROM ekbe
         FOR ALL ENTRIES IN i_po
         WHERE ebeln = i_po-ebeln AND
               ebelp = i_po-ebelp AND
               vgabe = c_vgabe.
      break-point.
        IF sy-subrc = 0.
          SORT i_ekbe BY ebeln ebelp.
          LOOP AT i_ekbe.
            IF i_ekbe-shkzg = c_h.
              i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
            ENDIF.
            MODIFY i_ekbe.
          ENDLOOP.
      break-point.
    Sum up the Item wise Invoice totals
          LOOP AT i_ekbe.
            AT END OF ebelp.
              READ TABLE i_ekbe INDEX sy-tabix.
              SUM.
              MOVE-CORRESPONDING i_ekbe TO i_inv.
              APPEND i_inv.
            ENDAT.
            CLEAR i_inv.
          ENDLOOP.
          SORT i_inv BY ebeln ebelp.
            break-point.
        ENDIF.
      ENDIF.
    Move the Vendor Name and Invoice Values to I_rep Internal Table
      LOOP AT i_po.
        MOVE-CORRESPONDING i_po TO i_rep.
        CLEAR i_inv.
        READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                                  ebelp = i_po-ebelp.
        IF sy-subrc = 0.
          i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
          i_rep-curr  = i_inv-waers.
        ELSE.
          i_rep-orewr = i_po-menge * i_po-netpr.
          i_rep-curr  = i_po-waers.
        ENDIF.
      break-point.
    Get the Vendor Name
        CLEAR lfa1-name1.
        SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
          WHERE lifnr = i_po-lifnr.
        IF sy-subrc = 0.
          i_rep-name1  = lfa1-name1.
        ENDIF.
        APPEND i_rep.
        CLEAR  i_rep.
          break-point.
      ENDLOOP.
      SORT i_rep BY lifnr ebeln ebelp.
      DELETE i_rep WHERE orewr LE 0.
      break-point.
    ENDFORM.                    " fetch_data
    *&      Form  display_data
    Display the Report Output data
    FORM display_data .
      DATA: lv_flag,               " New Flag
            lv_rec TYPE i.         " No of Records
      CLEAR lv_rec.
      IF i_rep[] IS INITIAL.
        MESSAGE e000 WITH 'No Data found'(022).
      ELSE.
        LOOP AT i_rep.
    Toggle Color
          PERFORM toggle_color.
          IF lv_flag <> space.
            NEW-LINE.
          ENDIF.
    At New Purchase Document
          AT NEW ebeln.
            WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
            lv_flag = c_x.
            lv_rec = lv_rec + 1.
          ENDAT.
          WRITE: 1 sy-vline,
                12 sy-vline,13(4)   i_rep-bsart,
                17 sy-vline,18(10)  i_rep-lifnr,
                28 sy-vline,29(35)  i_rep-name1,
                64 sy-vline,65(4)   i_rep-ekgrp,
                69 sy-vline,70(10)  i_rep-bedat,
                80 sy-vline,81(5)   i_rep-ebelp,
                86 sy-vline,87(40)  i_rep-txz01,
               127 sy-vline,128(9)  i_rep-matkl,
               137 sy-vline,138(1)  i_rep-pstyp,
               139 sy-vline,140(1)  i_rep-knttp,
               141 sy-vline,142(4)  i_rep-werks,
               146 sy-vline,147(4)  i_rep-lgort,
               151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
               165 sy-vline,166(3)  i_rep-meins,
               169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
               185 sy-vline,186(4)  i_rep-waers,
               190 sy-vline,191(5)  i_rep-peinh,
               196 sy-vline,197(4)  i_rep-bprme,
               201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
               217 sy-vline,218(4)  i_rep-curr,
               222 sy-vline,223(7)  i_rep-bstyp centered,
               230 sy-vline.
          NEW-LINE.
          hide: i_rep-ebeln.
        ENDLOOP.
        ULINE.
        FORMAT COLOR OFF.
        WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                    lv_rec COLOR 3.
      ENDIF.
    ENDFORM.                    " display_data
    *&      Form  header
    Write the Report Header
    FORM header .
      FORMAT RESET.
    header
      WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
      SKIP.
      FORMAT COLOR COL_HEADING.
      ULINE.
      WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
            12 sy-vline,13(4)   'Type'(007),
            17 sy-vline,18(10)  'Vendor'(008) CENTERED,
            28 sy-vline,29(35)  'Name'(009) CENTERED,
            64 sy-vline,65(4)   'PGrp'(010) CENTERED,
            69 sy-vline,70(10)  'Doc.Date'(012) CENTERED,
            80 sy-vline,81(5)   'Item'(011),
            86 sy-vline,87(40)  'Material Short Text'(024) CENTERED,
           127 sy-vline,128(9)  'Mat.Group'(013),
           137 sy-vline,138(1)  'I',
           139 sy-vline,140(1)  'A',
           141 sy-vline,142(4)  'Plnt'(014),
           146 sy-vline,147(4)  'SLoc'(015),
           151 sy-vline,152(13) 'Quantity'(016) CENTERED,
           165 sy-vline,166(3)  'UoM'(017),
           169 sy-vline,170(15) 'Net Value'(018) CENTERED,
           185 sy-vline,186(4)  'Curr'(019),
           190 sy-vline,191(5)  'Per'(020),
           196 sy-vline,197(4)  'Unit'(021),
           201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
           217 sy-vline,218(4)  'Curr'(019),
           222 sy-vline,223(7)  'Doc.Cat'(026),
           230 sy-vline.
      ULINE.
    ENDFORM.                    " header
    *&      Form  toggle_color
    This routine alters the color of the records in the list
    FORM toggle_color.
      IF gv_dial = space.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        gv_dial = c_x.
      ELSE.
        FORMAT COLOR 1 INTENSIFIED OFF.
        CLEAR gv_dial.
      ENDIF.
    ENDFORM.                    " toggle_color
    *&      Form  LINE_SEL
    *When double clicked on EBELN field display the details of Purchase Doc
    FORM line_sel.
      CASE sy-lsind.
        WHEN '1'.
          DATA: lv_field(20),
                lv_value(10),
                lv_bstyp like i_rep-bstyp.
          clear: lv_bstyp,lv_value, lv_field.
          GET CURSOR FIELD lv_field VALUE lv_value.
          IF lv_field = 'I_REP-EBELN'.
            IF NOT lv_value IS INITIAL.
              READ LINE sy-index FIELD VALUE i_rep-bstyp
                                       INTO  lv_bstyp.
             READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
              if lv_bstyp = 'F'.
                SET PARAMETER ID 'BES' FIELD lv_value.
                CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
              elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
                SET PARAMETER ID 'VRT' FIELD lv_value.
                CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
              elseif lv_bstyp = 'A'.
                SET PARAMETER ID 'ANF' FIELD lv_value.
                CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
              endif.
            ENDIF.
          ENDIF.
      ENDCASE.
    ENDFORM.                    " line_sel
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Reg: Open Purchase order

    Hi Guru,
    as per the Budget change,
    One of the tasks that has to be done as a part of the change in budget is the updation of info-record condition records in open purchase orders.
    In terms of open purchase orders there are two scenarios..
    Fully Open and Partially open.
    For Fully open purchase orders -  In the Purchase orer we have to change manually or what i will do.
    For Partially Open Purchase orders - Business will take responsibility.
    thanks
    kannan somasundaram

    Hi All,
    the budget change date is 07.12.2008. but we create some purchase order before the 07.12.2008. for these purchase order also we need to get 10% instead of 14%.
    how can i have to change that details.
    please give me the solution on this issue.
    thanks

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

  • Purchase order can not partial receipt

    HI Experts,
    When i am make gr for Account assigned (K) purchase order.i am getting below error msg
    already the made the GR for 200 quantity
    Po is created without material no
    Item 000010 is not relevant for goods receipt; increase quantity to 2,000.000 EA
    Message no. BORGR634
    Diagnosis
    This item is not relevant for goods receipt. The quantity to be posted has to be the same as the delivery quantity.
    It is not possible to post a partial quantity for this item.
    Procedure
    Increase the quantity of this item until it equals the delivery quantity.
    Please suggest
    Regards
    VR

    Hi,
    Already Goods reciept is over against this PO.
    You can check this by
    me23n -> Item level -> Purchase order history -> click on Material doc.
    Regards
    R

  • Unable to update purchase order after partial delivery

    bold Issue:
    After upgrading from v2005 > v2007:
    1) We created a PO with two different purchase items :
    row 1: 10 pcs Item x
    row 2: 15 pcs item Y
    2) create a Goods Receipt PO based on the PO row 2 (15 pcs Item Y) so this row will be closed in the PO.
    3) after saving the GRPO item Y is set as a non purchase item (deselected  the tick box "Purchase Item" on the Item master), because the supplier will not be able to deliver this item again.
    4) After changing item Y, we want to update the amount of Item X to for example 11 (instead of 10). This item is still a purchase item > while updating the PO the following error appears:
    [Purchase Order - Rows - Item No.][line: 2] , 'The item is not a purchase item (2)'  [Message 131-10]
    In v2005 it was possible to follow the above procedure, however since the upgrade of v2007 the error appears.
    The problem is that that it happens very often that the suppliers change the items, so they cannot be delivered anymore.
    bold  Below the response of SAP Support:
    Line: -
    Yes, I understand what you mean that the item you want to deliver is the other item PQ which is still a purchase item. However, the system does the checking based on document level, and not filtering only per Open rows. Hence, even if the item for B8 is fully closed, the system still detects that there is a non-purchase item in an open document (B8).
    In order to update the other item PQ, please set the item B8 back to Purchase Item. Once the Sales Order is updated, you may update B8 again to Non Purchase.
    If the possibility of using the 'Active/Inactive' button is not possible, another workaround is to use a User Define Field to flag the item. For example, you can set it as 'Y', when the supplier stopp ed selling the item. Then, in the Item Search window, you can filter the records to group those items that are set as 'Y' and the rest as 'N'. Only those 'N' items can be used when placing orders.
    As an added procedure, you can generate an approval procedure that will be triggered when an item that is set as 'Y' in the User Defined field is added in the Purchase Order. When the approval is trig gered, the user can then re-verify the items added and make the necessary changes before saving the purchase document.
    I hope the above workaround is suitable. I agree with the expected logic, but per Note937297, the stock status of an item is not meant to be changed after documents are added in the system. It seems a limitation in the current system.
    Line: -
    bold Solution:
    The system should check if the open row can be delivered, since it still is a purchase item.
    The provided workarounds are not an option for our customer, so we are looking forward to a positive reaction!
    Kind regards,
    Charlotte

    Unable to update purchase order after partial delivery
    Issue:
    After upgrading from v2005 > v2007:
    1) We created a PO with two different purchase items :
    row 1: 10 pcs Item x
    row 2: 15 pcs item Y
    2) create a Goods Receipt PO based on the PO row 2 (15 pcs Item Y) so this row will be closed in the PO.
    3) after saving the GRPO item Y is set as a non purchase item (deselected  the tick box "Purchase Item" on the Item master), because the supplier will not be able to deliver this item again.
    4) After changing item Y, we want to update the amount of Item X to for example 11 (instead of 10). This item is still a purchase item > while updating the PO the following error appears:
    [Purchase Order - Rows - Item No.][line: 2] , 'The item is not a purchase item (2)'  [Message 131-10]
    In v2005 it was possible to follow the above procedure, however since the upgrade of v2007 the error appears.
    The problem is that that it happens very often that the suppliers change the items, so they cannot be delivered anymore.
    Below the response of SAP Support:
    Yes, I understand what you mean that the item you want to deliver is the other item PQ which is still a purchase item. However, the system does the checking based on document level, and not filtering only per Open rows. Hence, even if the item for B8 is fully closed, the system still detects that there is a non-purchase item in an open document (B8).
    In order to update the other item PQ, please set the item B8 back to Purchase Item. Once the Sales Order is updated, you may update B8 again to Non Purchase.
    If the possibility of using the 'Active/Inactive' button is not possible, another workaround is to use a User Define Field to flag the item. For example, you can set it as 'Y', when the supplier stopp ed selling the item. Then, in the Item Search window, you can filter the records to group those items that are set as 'Y' and the rest as 'N'. Only those 'N' items can be used when placing orders.
    As an added procedure, you can generate an approval procedure that will be triggered when an item that is set as 'Y' in the User Defined field is added in the Purchase Order. When the approval is trig gered, the user can then re-verify the items added and make the necessary changes before saving the purchase document.
    I hope the above workaround is suitable. I agree with the expected logic, but per Note937297, the stock status of an item is not meant to be changed after documents are added in the system. It seems a limitation in the current system.
    Solution:
    The system should check if the open row can be delivered, since it still is a purchase item.
    The provided workarounds are not an option for our customer, so we are looking forward to a positive reaction!
    Kind regards,
    Charlotte

  • Partial Invoice from Purchase Order

    Hi Experts
    I did a Purchase order for 10,000 and invoiced for 5,000 but when I try to do the incoice for the balance amount the sytem does not have any open purchase orders.
    My question is if we do invoice for partial amount can we have the purchase order still open or how to go further
    please help
    thanks and regards
    vinodh

    Hi Vinor,
    In your scenario, you shold have used an AR downpayment Invoice to bill partial amount.
    In SBO, as long as you have copied all quantities from 1 document to the next (In your case, you have copied all qty which is 1 to the next document), hence your Purchase Order was closed. This is a normal behaviour.
    To bill partial payment, do use AR downpayment invoice.
    Hope it helps.
    Warmest Regards,
    Chinho

  • Raising Partial Production and purchase order from MRP.?

    Hi Experts,
    How to raise partial production order and purchase order from MRP..
    Karthik

    Karthi,
    I believe you should go through both of these topics relating to Production Orders and MRP.
    https://websmp105.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000321882005E&_SCENARIO=01100035870000000183&_ADDINC=
    https://websmp105.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001061692007E&_SCENARIO=01100035870000000183&_ADDINC=
    Best wishes
    Suda

  • Configure partial invoice distribution for SRM Purchase Order

    Hello Experts,
    We are on SRM 5.0 SP12 and ERP 6.0 SP13.  When a split accounting purchase order is created in SRM and transfers over into SAP, partial invoices are automatically posting with the distribution of "Distribute to following row".  In ME23N under account assignment, there are three options for partial invoice postings:
    1) Derive from account assignment category
    2) Distribute to following row
    3) Distribute proportionally
    We would like to default the third selection, "Distribute proportionally".  Does anyone know where this setting can be changed or how to do this?
    Thanks,
    Brett

    SAP was able to provide assistance on the issue. Here are the details:
    The SRM always sends to ECC the "Distribute to Following Row" selected,
    and sometimes configuration changes in tcode OME9 have not effect,
    possibly due to the Support Package.
    To specify the correct option "Distribute Proportionally", it is necessary to use the Badi BBP_PO_INBOUND_BADI...
    The partial invoice indicator is set to '1' by default in SRM, it is
    standard behaviour, you can check it in the LBBP_BD_DRIVER_46AF15
    program. The functionality that allow has the value ´2´ to partial
    invoice indicator is exclusive to MM - R3 system.
    You have two possible solution to create from EBP to backend some PO
    documents with multiple account assignment and partial invoice
    indicator = 2 (Distribute Proportionally):
    a) To use the Badi BBP_ECS_PO_OUT_BADI to create the PO this way.
    ls_ct_bapi_poitem-PART_INV = '2'
    Effectively, this solution change the setting in the backend
    to 'Distribute Proportionally'.
    b) Partial invoice indicator can either be set in OME9 in the Backend
    for the posted account assignment category (e.g. K - cost center)
    or default using Backend Badi:
    BBP_PO_INBOUND_BADI
    BBP_POITEM-PART_INV
    -> Part_INV is a field of BBP_POITEM. In the backend BADI, if you
    look at the field of BBP_POITEM, you will find PART_INV. You
    have to use the BADI to set this field.
    OME9 was the tcode in MM to specify the partial invoice settings for each account assignment. According to SAP, sometimes this works with SRM (since the default setting sent to ECC from SRM is "Distribute to following row") and sometimes it doesn't. We ended up changing the partial invoice flag upon creation of the purchase order through the BADI mentioned above since the configuration changes did not remedy the issue. Now the partial invoices are posting proportionally which has resolved all of our split accounting posting issues.
    Thanks,
    Brett

  • Status of Purchase Order should be "Fully Invoice" / "Partially Invoiced"

    Hi SAP,
    Purchase Order is made and goods receipt (MIGO) is done against the particular
    line item of that Purchase Order, For some reasons the FI entry is entered in the system.
    The Purchase Order Line Item is blocked in ME22N for avoiding booking of MIRO Transaction
    The Requirement is to change the status of Purchase Order as “Fully Invoiced”
    as the same is showing as "Not Invoice" in Purchase Order Header > Status Tab
    Advance Thanks,
    Bhaskar Reddy.S

    Go to ME22N..
    Just tick the Final invoice in Invoice tab..

  • Partial Payments on Purchase Orders - IDOC Scenario

    Hi all,
    I have been asked to look into an integration scenario where a purchase order is set up in ECC 6.0 and payments are called off against this over the financial year.
    Payment files are generated in another system and the idea is that we pick up these files with PI and create payment documents in SAP that are associated with this purchase order.
    I have previously used FIDDCP2 to create payment/invoice documents in SAP - but these had no link or association with purchase orders.
    Anyone had this scenario before? Can I use FIDDCP2 to call off payments against a purchase order like this?
    Or are there other, better (easier?) ways to achieve this?
    Advice and thoughts welcome...
    Regards
    Ian

    Hi Ian,
    I guess that if you post this question in an R3/ECC (ABAP) forum you could get more help, because they should know more about Idoc types for different purposes.
    Regards, 
      Juan.

  • Open Purchase Order report

    Hello All,
    Anyone know how I can get the list of Open Purchase orders?
    Currently we are pulling all those POs with the following characteristics:
    PO item where
            all schedules have received qty zero.
    Open Schedules (EKET) - Don’t want fully or partially received
         Received Quantity (wemng) = zero
    The performance is not the greatest.
    Just curious to know how others are arriving at the list of Open Purchase Orders.
    Ideas / Thoughts???
    Thanks for any input.

    Why not checking for Final Invoice indicator EKPO-EREKZ = 'X'
    or/and Delivery Completed Indicator EKPO-ELIKZ = 'X'.
    select *
    from ekpo
    into table it_ekpo
    where delkz ne space and (erekz = 'X'
       or elikz = 'X').
    Regards,
    ravi

  • Open Purchase Order Documents

    Using the DI API, how can I query the PO documents that have neither followup "Goods Receipt" nor "A/P Invoice" documents? That is, I'm looking for the open Purchase Orders.
    Thank you,
    Miklos

    You can use the recordset object to query for open PO's.
    This can be a simple query, or it can get more complex, depending on your needs.
    Something like this...
    SELECT * FROM OPOR WHERE DOCSTATUS = 'O' AND CANCELED <> 'Y'
    ... will get you a list of all of the currently open PO headers.  However, an open PO may have been partially paid, or partially  received.  The PO header remains open until all line items have been closed.
    If you're looking for a way to find PO's that have not had any partial receipts, invoices, or rtv's against them then the solution will need to consider the LineStatus field on the POR1 table as well.
    Regards,
    Demetree

Maybe you are looking for

  • AP Line Item Audit

    Hello all. I am attempting to pull data out of SAP. My end goal is to obtain all AP line items paid in 2009. My desired fields are company code BUKRS, document cleared date AUGDT, vendor ID LIFNR, GL code HKONT, cost center KOSTL1, amount DMBTR, curr

  • Problem in using jmsConnectionFactory

    Hi All, I'm new to j2ee. i have problem in message driven bean - "jmsConnectionFactory" . where this is intialize to use in message driven bean. please let me help on this.

  • Create library (swc) in Flash Builder 4 / Flex Project (not in a Library Project)

    I want to create a swc file to use it in an other project. I can't use the Flash 4 Library Project to do this, because in a Library Project I haven't the possibility to use data/services, which I need for my library. After click on "data / services"

  • Auto Advance bug with changing labels in grid

    If Auto Advance is checked in the menu {Photos}{Auto Advance} and the user is in the grid view viewing images with colored labels. Changing the label on one selected image using the tool bar label icons causes the selected image to be unlabeled. The

  • Photoshop Elements 12 on DVD download to Windows Tablet

    I purchased Photoshop Elements 12 on DVD but I now have a Windows Tablet computer without a DVD drive.  Where can I downlaod the software to my Tablet?