Interactive Backorder Processing on Replenishment Purchase Orders

Hi Team,
Can you please let me know if Interactive Backorder Processing be performed on Replenishment POs as per the standard SAP design?
When I try to perform BOPI on a Replenishment PO it gives me a dump. The dump resulted because the "First Sales Order" field was missing.
Please let me know what this "First Sales Order" means with respect to a Replenishment PO.
Thanks in advance for the help and for your time.
Thanks & Regards,
Srikanth.

Hi Babu Kilari,
Thanks for the help.
Yes. Replenishment POs means STO documents. I checked the SAP Service Marketplace for this. But, couldn't get a solution.
There is a SAP note(1294888) released for a dump that occurred when changing the quantity of STO. But, this is a different case as that of my scenario.
If there is any SAP note BOPI on Replenishment POs kindly let me know.
Thanks & Regards,
Srikanth.

Similar Messages

I Need interactive report to list the purchase orders details for a vendor

I Need interactive report to list the purchase orders details for a vendor that has interactive drill down options to give the detail of vendor from vendor master.

Hi
see this sample report
this is Customer wise sales orders
just make similar report just using LFA1, EKKO and EKPO tables instead of KNA1,VBAK,VBAP
REPORT ZTEJ_INTAB1 LINE-SIZE 103 LINE-COUNT 35(5) NO STANDARD PAGE
HEADING.
*TABLES DECLARATION
TABLES : KNA1, VBAK, VBAP.
*SELECT OPTIONS
SELECT-OPTIONS: CUST_NO FOR KNA1-KUNNR.
*INITIALIZATION
INITIALIZATION.
CUST_NO-LOW = '01'.
CUST_NO-HIGH = '5000'.
CUST_NO-SIGN = 'I'.
CUST_NO-OPTION = 'BT'.
APPEND CUST_NO.
*SELECTION SCREEN VALIDATION
AT SELECTION-SCREEN ON CUST_NO.
LOOP AT SCREEN.
IF CUST_NO-LOW < 1 OR CUST_NO-HIGH > 5000.
MESSAGE E001(ZTJ1).
ENDIF.
ENDLOOP.
*BASIC LIST SELECTION
START-OF-SELECTION.
SELECT KUNNR NAME1 ORT01 LAND1 INTO
(KNA1-KUNNR, KNA1-NAME1,KNA1-ORT01,KNA1-LAND1)
FROM KNA1
WHERE KUNNR IN CUST_NO.
WRITE:/1 SY-VLINE,
KNA1-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
KNA1-NAME1 UNDER 'NAME',
61 SY-VLINE,
KNA1-ORT01 UNDER 'CITY',
86 SY-VLINE,
KNA1-LAND1 UNDER 'COUNTRY',
103 SY-VLINE.
HIDE: KNA1-KUNNR.
ENDSELECT.
ULINE.
*SECONDARY LIST ACCESS
AT user-command.
IF SY-UCOMM = 'IONE'.
PERFORM SALES_ORD.
ENDIF.
IF SY-UCOMM = 'ITWO'.
PERFORM ITEM_DET.
ENDIF.
*TOP OF PAGE
TOP-OF-PAGE.
FORMAT COLOR 1.
WRITE : 'CUSTOMER DETAILS'.
FORMAT COLOR 1 OFF.
ULINE.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'NAME',
61 SY-VLINE,
63 'CITY',
86 SY-VLINE,
88 'COUNTRY',
103 SY-VLINE.
ULINE.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR SECONDARY LISTS
TOP-OF-PAGE DURING LINE-SELECTION.
*TOP OF PAGE FOR 1ST SECONDARY LIST
IF SY-UCOMM = 'IONE'.
ULINE.
FORMAT COLOR 1.
WRITE : 'SALES ORDER DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'SALES ORDER NO.',
40 SY-VLINE,
42 'DATE',
60 SY-VLINE,
62 'CREATOR',
85 SY-VLINE,
87 'DOC DATE',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR 2ND SECONDARY LIST
IF SY-UCOMM = 'ITWO'.
ULINE.
FORMAT COLOR 1.
WRITE : 'ITEM DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'SALES ORDER NO.',
40 SY-VLINE,
42 'SALES ITEM NO.',
60 SY-VLINE,
62 'ORDER QUANTITY',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*END OF PAGE
END-OF-PAGE.
ULINE.
WRITE :'USER :',SY-UNAME,/,'DATE :', SY-DATUM, 85 'END OF PAGE:',
SY-PAGNO.
SKIP.
*& Form SALES_ORD
*& FIRST SECONDARY LIST FORM
FORM SALES_ORD .
SELECT KUNNR VBELN ERDAT ERNAM AUDAT INTO
(VBAK-KUNNR, VBAK-VBELN, VBAK-ERDAT, VBAK-ERNAM, VBAK-AUDAT)
FROM VBAK
WHERE KUNNR = KNA1-KUNNR.
WRITE:/1 SY-VLINE,
VBAK-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
VBAK-VBELN UNDER 'SALES ORDER NO.' HOTSPOT ON,
40 SY-VLINE,
VBAK-ERDAT UNDER 'DATE',
60 SY-VLINE,
VBAK-ERNAM UNDER 'CREATOR',
85 SY-VLINE,
VBAK-AUDAT UNDER 'DOC DATE',
103 SY-VLINE.
HIDE : VBAK-VBELN.
ENDSELECT.
ULINE.
ENDFORM. " SALES_ORD
*& Form ITEM_DET
*& SECOND SECONDARY LIST FORM
FORM ITEM_DET .
SELECT VBELN POSNR KWMENG INTO
(VBAP-VBELN, VBAP-POSNR, VBAP-KWMENG)
FROM VBAP
WHERE VBELN = VBAK-VBELN.
WRITE : /1 SY-VLINE,
VBAP-VBELN UNDER 'SALES ORDER NO.',
40 SY-VLINE,
VBAP-POSNR UNDER 'SALES ITEM NO.',
60 SY-VLINE,
VBAP-KWMENG UNDER 'ORDER QUANTITY',
103 SY-VLINE.
ENDSELECT.
ULINE.
ENDFORM. " ITEM_DET
REPORT demo_list_at_pf.
START-OF-SELECTION.
WRITE 'Basic List, Press PF5, PF6, PF7, or PF8'.
AT pf5.
PERFORM out.
AT pf6.
PERFORM out.
AT pf7.
PERFORM out.
AT pf8.
PERFORM out.
FORM out.
WRITE: 'Secondary List by PF-Key Selection',
/ 'SY-LSIND =', sy-lsind,
/ 'SY-UCOMM =', sy-ucomm.
ENDFORM.
After executing the program, the system displays the basic list. The user can press the function keys F5 , F6 , F7 , and F8 to create secondary lists. If, for example, the 14th key the user presses is F6 , the output on the displayed secondary list looks as follows:
Secondary List by PF-Key Selection
SY-LSIND = 14
SY-UCOMM = PF06
Example for AT USER-COMMAND.
REPORT demo_list_at_user_command NO STANDARD PAGE HEADING.
START-OF-SELECTION.
WRITE: 'Basic List',
/ 'SY-LSIND:', sy-lsind.
TOP-OF-PAGE.
WRITE 'Top-of-Page'.
ULINE.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE sy-pfkey.
WHEN 'TEST'.
WRITE 'Self-defined GUI for Function Codes'.
ULINE.
ENDCASE.
AT LINE-SELECTION.
SET PF-STATUS 'TEST' EXCLUDING 'PICK'.
PERFORM out.
sy-lsind = sy-lsind - 1.
AT USER-COMMAND.
CASE sy-ucomm.
WHEN 'FC1'.
PERFORM out.
WRITE / 'Button FUN 1 was pressed'.
WHEN 'FC2'.
PERFORM out.
WRITE / 'Button FUN 2 was pressed'.
WHEN 'FC3'.
PERFORM out.
WRITE / 'Button FUN 3 was pressed'.
WHEN 'FC4'.
PERFORM out.
WRITE / 'Button FUN 4 was pressed'.
WHEN 'FC5'.
PERFORM out.
WRITE / 'Button FUN 5 was pressed'.
ENDCASE.
sy-lsind = sy-lsind - 1.
FORM out.
WRITE: 'Secondary List',
/ 'SY-LSIND:', sy-lsind,
/ 'SY-PFKEY:', sy-pfkey.
ENDFORM.
When you run the program, the system displays the following basic list with a the page header defined in the program:
You can trigger the AT LINE-SELECTION event by double-clicking a line. The system sets the status TEST and deactivates the function code PICK. The status TEST contains function codes FC1 to FC5. These are assigned to pushbuttons in the application toolbar. The page header of the detail list depends on the status.
Here, double-clicking a line no longer triggers an event. However, there is now an application toolbar containing five user-defined pushbuttons. You can use these to trigger the AT USER-COMMAND event. The CASE statement contains a different reaction for each pushbutton.
For each interactive event, the system decreases the SY-LSIND system field by one, thus canceling out the automatic increase. All detail lists now have the same level as the basic list and thus overwrite it. While the detail list is being created, SY-LSIND still has the value 1.
Regards
Anji

How to process a Blanket Purchase order?

Hi,
Can you please let me know how to process a blanket purchase order received from a customer?
Can we create a sales order based on the customer's blanket purchase order?
Please help me out with this issue.
Sincerely,
Puja

Dear Puja,
You can create Sales Order ....with reference to Blanket / Frame Purchase Order. This Frame PO contains, Validity and Limit.
Based on this info, you can create Blanket Sales Order.
You can split the blanket sales orders relevant to the customer PO.
Regards - Muralidhara

PROCESS CODE FOR PURCHASE ORDER

Hi Friends,
what is the process code for Purchase order... because i need to creating a partner profile in WE20 in the inbound side.. if iselect message type ORDERS menas.. that related.. process code( for purchase order is not displaying)..
can any of you give me the Message type and that related Process code for purchase order..
thanks
Babu

Hi Babu,
You will find out the all Process Code from WE41 for Outbound & WE42 for Inbound.
The Process code for ORDERS: Purchase order is ME10 for Outbound and you can find it out the message type for Inbound from WE42.
If need more info let me know..
Cheers
Veera

Interactive ALV report for vendorwise purchase order details

Hi Experts,
I am trying to create vendor wise purchase order interactive report, if i click any of vendor detail it has to display vendor details in a popup window or if i click any of purchase details it has to display purchase order details ina popup..
can any body explain by using function modules REUSE_ALV_POPUP_TO_SELECT and REUSE_ALV_FIELDCATALOG_MERGE...

Check the link below will be of some use to you.
http://www.geocities.com/mpioud/Z_REUSE_ALV_POPUP_TO_SELECT.html
Regards,
Murthy

Stoping process of saving purchase order(ME21/ME21N) in the user exit.

Hi,
I am using user exit "EXIT_SAPMM06E_016" of purchase order. While creating PO and after user enters 1st line item or more items and presses save button, then this user exit will be called.
Now my requirement is I have to check "item delivery date" , if it is more than 300 days from creation date then I have to show popup for warning the user for the same and if user want to make the changes then this user exit should stops the process of saving the PO and returns and allows to change the PO.
Please help me in this.
how I can stop the saving process.
Thanks,
Deepak

Hi Deepak,
You can do it in IM_ITEM method
DATA: ls_mepoitem TYPE mepoitem.
ls_mepoitem = im_item->get_data( ).
if you check ls_mepoitem-quantity field it will give your required value....pls Go through the documentation below for the method
Documentation for the method
Processing of Item Data
Functionality
The PROCESS_ITEM method enables you to change the item data and check it
for correctness.
Parameters
The following parameters are available:
o IM_ITEM - Document item
The interface reference is of the category
IF_PURCHASE_ORDER_ITEM_MM. You can use all methods defined there.
Note
Please note the general hints on Error Handling.
If you wish to mark the document item as invalid, use the
INVALIDATE() method of the IF_PURCHASE_ORDER_ITEM_MM interface.
Regards
Byju

Error in process when creating Purchase Order against WBS

Hi!
We are creating a purchase order (BBP_POC) against a WBS. But when trying to purchase for more than what the project budget is set to the purchase order gets the status "Error in process". We do not want the purchase order to be replicated to ECC but dont want it to be created in SRM as well. Is there a way to get an error message when trying to create the Purchase order? We do not want to end up with alot of purchase orders with "errror in process".
When doing the exact same thins in sourcing cockpit it is not possible to create the purchase order. Then we receive the error message (or warning) stopping us from creating a PO in SRM.
How to get the error and warning in BBP_POC?
Sincerely
Anders Öhrling

The budget check should work in the following cases
    1. When you create and change a shopping cart (e.g. after it has been held)
    2. When you create and change a purchase order (purchasing cockpit)
    3. When you create a purchase order from within the sourcing cockpit (as of SRM 2.0)
    4. With the approval of shopping carts and purchase orders
Unfortunately nr 2 is not working.
BBP_BUDGET_CHECK is not implemented.
Sincerely
Anders Öhrling

Process button in purchase order response SUS not present

Hi all.
We have SRM 7 and ECC 6.4. Scenario MM-SUS Purchase Order Response.
We can transfer purchase orders from MM to SUS. Purchase Order SUS are generate correctly In SUS system.
However. When a Vendor user enters in the SUS system to create the POR, we can not create it because the Process button is not present.
The user was create by process of Creating Buyer Data (BBP_SUS_BP_ADM) and rols SAP_EC_SUS_BIDDER and SAP_EC_SUS_ORDER_PROCESSOR in trx SU01
I appreciate a tip to solve this issue.
Regards
Raul.

Hi,
You can do what Sam has suggested in vendor master too so that everytime a PO for that vendor is issued, you do not have to manually maintain these settings in the PO.
Regards,
Nikhil

Want Interactive Report which displays the Purchase Orders

Hi all,
What are the select-options,parameters and tables used in purchase orders report and if possible send me the code for the same.
Thanks in Advance
Santosh R

see if this one helps
REPORT YSG_MATSTK_REPT LINE-SIZE 220
 LINE-COUNT 50(5).
*& DATA DECLARATION *
TABLES: MARA, "GENERAL MASTER DATA
 MARC, "PLANT DATA FOR MATERIAL
 MARD, "STORAGE LOCATION DATA FOR MATERIAL
 MVKE, "SALES DATA FOR MATERIAL
 MAKT, "MATERIAL DESCRIPTION
 EKKO, "PURCHASING DOCUMENT HEADER
 EKPO, "PURCHASING DOCUMENT ITEM
 VBAK, "SALES DOCUMENT HEADER DATA
 VBAP. "SALES DOCUMENT ITEM DATA
TYPE-POOLS : SLIS.
DATA: VT_FIELDCAT1 TYPE SLIS_T_FIELDCAT_ALV,
 V_FIELDCAT TYPE SLIS_FIELDCAT_ALV,
 V_LAYOUT TYPE SLIS_LAYOUT_ALV,
 BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
 BEGIN OF I_MARA OCCURS 0,
 MATNR LIKE MARA-MATNR, "MATERIAL NUMBER
 MBRSH LIKE MARA-MBRSH, "INDUSTRY SECTOR
 MEINS LIKE MARA-MEINS, "BASE UNIT OF MEASURE
 MATKL LIKE MARA-MATKL, "MATERIAL GROUP
 END OF I_MARA,
 BEGIN OF I_MARC OCCURS 0,
 MATNR LIKE MARC-MATNR, "MATERIAL NUMBER
 WERKS LIKE MARC-WERKS, "PLANT
 LVORM LIKE MARC-LVORM, "FLAG MATERIAL FOR DELETION AT PLANT
 "LEVEL
 DISPO LIKE MARC-DISPO, "MRP CONTROLLER
 END OF I_MARC,
 BEGIN OF I_MAKT OCCURS 0,
 MATNR LIKE MAKT-MATNR, "MATERIAL NUMBER
 MAKTX LIKE MAKT-MAKTX, "MATERIAL DESCRIPTION
 SPRAS LIKE MAKT-SPRAS, "LANGUAGE KEY
 END OF I_MAKT,
 BEGIN OF I_MVKE OCCURS 0,
 MATNR LIKE MVKE-MATNR, "MATERIAL NUMBER
 VKORG LIKE MVKE-VKORG, "SALES ORGANIZATION
 VTWEG LIKE MVKE-VTWEG, "DISTRIBUTION CHANNEL
 END OF I_MVKE,
 BEGIN OF I_MARD OCCURS 0,
 MATNR LIKE MARD-MATNR, "MATERIAL NUMBER
 LGORT LIKE MARD-LGORT, "STORAGE LOCATION
 LABST LIKE MARD-LABST, "VALUATED STOCK WITH UNRESTRICTED USE
 END OF I_MARD,
 BEGIN OF I_EKPO OCCURS 0,
 EBELN LIKE EKPO-EBELN, "PURCHASING DOCUMENT NUMBER
 EBELP LIKE EKPO-EBELP, "ITEM NUMBER OF PURCHASING DOCUMENT
 MATNR LIKE EKPO-MATNR, "MATERIAL NUMBER
 END OF I_EKPO,
 BEGIN OF I_VBAP OCCURS 0,
 VBELN LIKE VBAP-VBELN, "SALES DOCUMENT
 POSNR LIKE VBAP-POSNR, "SALES DOCUMENT ITEM
 MATNR LIKE VBAP-MATNR, "MATERIAL NUMBER
 END OF I_VBAP,
 BEGIN OF I_OUT OCCURS 0,
 MATNR LIKE MARC-MATNR,
 WERKS LIKE MARC-WERKS,
 LVORM LIKE MARC-LVORM,
 DISPO LIKE MARC-DISPO,
 MBRSH LIKE MARA-MBRSH,
 MEINS LIKE MARA-MEINS,
 MATKL LIKE MARA-MATKL,
 VKORG LIKE MVKE-VKORG,
 VTWEG LIKE MVKE-VTWEG,
 SPRAS LIKE MAKT-SPRAS,
 MAKTX LIKE MAKT-MAKTX,
 LGORT LIKE MARD-LGORT,
 LABST LIKE MARD-LABST,
 EBELN LIKE EKPO-EBELN,
 EBELP LIKE EKPO-EBELP,
 VBELN LIKE VBAP-VBELN,
 POSNR LIKE VBAP-POSNR,
 END OF I_OUT,
 BEGIN OF I_HEADING OCCURS 0,
 TEXT1(20),
 TEXT2(20),
 TEXT3(20),
 TEXT4(20),
 TEXT5(20),
 TEXT6(20),
 TEXT7(20),
 TEXT8(20),
 TEXT9(20),
 TEXT10(20),
 TEXT11(40),
 TEXT12(20),
 TEXT13(20),
 TEXT14(20),
 TEXT15(20),
 TEXT16(20),
 TEXT17(20),
 END OF I_HEADING.
*& 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-100.
SELECT-OPTIONS: S_MATNR FOR MARA-MATNR. "OBLIGATORY.
PARAMETERS: P_WERKS LIKE MARC-WERKS. "OBLIGATORY.
SELECT-OPTIONS: S_LGORT FOR MARD-LGORT,
 S_DISPO FOR MARC-DISPO,
 S_EBELN FOR EKPO-EBELN .
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-101.
PARAMETERS : RB1 RADIOBUTTON GROUP G1,
 RB2 RADIOBUTTON GROUP G1,
 RB3 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF BLOCK B2.
*& I N I T I A L I Z A T I O N *
*INITIALIZATION.
*& S T A R T - O F - S E L E C T I O N *
START-OF-SELECTION.
SELECT MATNR WERKS LVORM DISPO FROM MARC
INTO CORRESPONDING FIELDS OF TABLE I_MARC
 WHERE MATNR IN S_MATNR
 AND DISPO IN S_DISPO
 AND WERKS = P_WERKS.
IF I_MARC[] IS INITIAL.
 WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MARC'.
 EXIT.
ENDIF.
PERFORM PURCHASEDATA_VALIDATION.
PERFORM SALESDATA_VALIDATION.
SELECT MATNR LGORT LABST FROM MARD INTO TABLE I_MARD
 FOR ALL ENTRIES IN I_MARC
 WHERE MATNR = I_MARC-MATNR
 AND WERKS EQ P_WERKS
 AND LGORT IN S_LGORT.
IF I_MARD[] IS INITIAL.
 WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MARD'.
 EXIT.
ENDIF.
SELECT MATNR VKORG VTWEG FROM MVKE INTO TABLE I_MVKE
 FOR ALL ENTRIES IN I_MARC
 WHERE MATNR = I_MARC-MATNR.
IF I_MVKE[] IS INITIAL.
 WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MVKE'.
 EXIT.
ENDIF.
LOOP AT I_MARC.
 MOVE-CORRESPONDING I_MARC TO I_OUT.
 CLEAR MARC.
 SELECT SINGLE MATNR MBRSH MEINS MATKL FROM MARA
 INTO CORRESPONDING FIELDS OF MARA
 WHERE MATNR = I_OUT-MATNR.
 IF SY-SUBRC = 0.
 MOVE: MARA-MBRSH TO I_OUT-MBRSH,
 MARA-MEINS TO I_OUT-MEINS,
 MARA-MATKL TO I_OUT-MATKL.
 ELSE.
 CONTINUE.
 ENDIF.
 SELECT SINGLE MATNR MAKTX SPRAS FROM MAKT
 INTO CORRESPONDING FIELDS OF MAKT
 WHERE MATNR = I_OUT-MATNR.
 IF SY-SUBRC = 0.
 MOVE: MAKT-MAKTX TO I_OUT-MAKTX,
 MAKT-SPRAS TO I_OUT-SPRAS.
 ELSE.
 CONTINUE.
 ENDIF.
 LOOP AT I_EKPO WHERE MATNR = I_MARC-MATNR.
 MOVE: I_EKPO-EBELN TO I_OUT-EBELN,
 I_EKPO-EBELP TO I_OUT-EBELP.
 ENDLOOP.
 LOOP AT I_VBAP WHERE MATNR = I_MARC-MATNR.
 MOVE: I_VBAP-VBELN TO I_OUT-VBELN,
 I_VBAP-POSNR TO I_OUT-POSNR.
 ENDLOOP.
 LOOP AT I_MARD WHERE MATNR = I_MARC-MATNR.
 MOVE: I_MARD-LABST TO I_OUT-LABST,
 I_MARD-LGORT TO I_OUT-LGORT.
 ENDLOOP.
 LOOP AT I_MVKE WHERE MATNR = I_MARC-MATNR.
 MOVE: I_MVKE-VKORG TO I_OUT-VKORG,
 I_MVKE-VTWEG TO I_OUT-VTWEG.
 ENDLOOP.
 APPEND I_OUT.
 CLEAR I_OUT.
ENDLOOP.
PERFORM OPTIONS.
* FORM OPTIONS *
FORM OPTIONS.
IF RB2 = 'X'.
 PERFORM FIELDCAT.
 PERFORM OUTPUT.
ELSE.
 IF RB1 = 'X'.
 PERFORM HEADINGS.
 PERFORM DLOAD.
 ELSE.
 IF RB3 = 'X'.
 PERFORM HEADINGS.
 PERFORM DLOAD.
 PERFORM FIELDCAT.
 PERFORM OUTPUT.
 ENDIF.
 ENDIF.
ENDIF.
ENDFORM. "OPTIONS
* FORM HEADINGS *
FORM HEADINGS.
I_HEADING-TEXT1 = 'MATNR'.
I_HEADING-TEXT2 = 'WERKS'.
I_HEADING-TEXT3 = 'LVORM'.
I_HEADING-TEXT4 = 'DISPO'.
I_HEADING-TEXT5 = 'MBRSH'.
I_HEADING-TEXT6 = 'MEINS'.
I_HEADING-TEXT7 = 'MATKL'.
I_HEADING-TEXT8 = 'VKORG'.
I_HEADING-TEXT9 = 'VTWEG'.
I_HEADING-TEXT10 = 'SPRAS'.
I_HEADING-TEXT11 = 'MAKTX'.
I_HEADING-TEXT12 = 'LGORT'.
I_HEADING-TEXT13 = 'LABST'.
I_HEADING-TEXT14 = 'EBELN'.
I_HEADING-TEXT15 = 'EBELP'.
I_HEADING-TEXT16 = 'VBELN'.
I_HEADING-TEXT17 = 'POSNR'.
APPEND I_HEADING.
ENDFORM. "HEADINGS
* FORM DLOAD *
FORM DLOAD.
CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
 FILENAME = 'C:MATSTK.csv'
 FILETYPE = 'DAT'
 WRITE_FIELD_SEPARATOR = 'X'
 TABLES
 DATA_TAB = I_HEADING
 EXCEPTIONS
 FILE_WRITE_ERROR = 1.
CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
 FILENAME = 'C:MATSTK.csv'
 FILETYPE = 'DAT'
 APPEND = 'X'
 WRITE_FIELD_SEPARATOR = 'X'
 TABLES
 DATA_TAB = I_OUT.
ENDFORM. "DLOAD
* FORM FIELDCAT *
FORM FIELDCAT.
V_FIELDCAT-COL_POS = '1'.
V_FIELDCAT-FIELDNAME = 'MATNR'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'MATNR'.
V_FIELDCAT-REF_TABNAME = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '2'.
V_FIELDCAT-FIELDNAME = 'WERKS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'WERKS'.
V_FIELDCAT-REF_TABNAME = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '3'.
V_FIELDCAT-FIELDNAME = 'LVORM'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'LVORM'.
V_FIELDCAT-REF_TABNAME = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '4'.
V_FIELDCAT-FIELDNAME = 'DISPO'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'DISPO'.
V_FIELDCAT-REF_TABNAME = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '5'.
V_FIELDCAT-FIELDNAME = 'MBRSH'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MBRSH'.
V_FIELDCAT-REF_TABNAME = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '6'.
V_FIELDCAT-FIELDNAME = 'MEINS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MEINS'.
V_FIELDCAT-REF_TABNAME = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '7'.
V_FIELDCAT-FIELDNAME = 'MATKL'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MATKL'.
V_FIELDCAT-REF_TABNAME = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '8'.
V_FIELDCAT-FIELDNAME = 'VKORG'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'VKORG'.
V_FIELDCAT-REF_TABNAME = 'MVKE'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '9'.
V_FIELDCAT-FIELDNAME = 'VTWEG'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'VTWEG'.
V_FIELDCAT-REF_TABNAME = 'MVKE'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '10'.
V_FIELDCAT-FIELDNAME = 'SPRAS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'SPRAS'.
V_FIELDCAT-REF_TABNAME = 'MAKT'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '11'.
V_FIELDCAT-FIELDNAME = 'MAKTX'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MAKTX'.
V_FIELDCAT-REF_TABNAME = 'MAKT'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '12'.
V_FIELDCAT-FIELDNAME = 'LGORT'.
V_FIELDCAT-TABNAME = 'I_OUT'.
* V_FIELDCAT-REF_FIELDNAME = 'LGORT'.
* V_FIELDCAT-REF_TABNAME = 'MARD'.
V_FIELDCAT-SELTEXT_L = 'STRG LOCT'.
V_FIELDCAT-OUTPUTLEN = 10.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '13'.
V_FIELDCAT-FIELDNAME = 'LABST'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-SELTEXT_M = 'STOCK'.
V_FIELDCAT-OUTPUTLEN = 15.
* V_FIELDCAT-REF_FIELDNAME = 'LABST'.
* V_FIELDCAT-REF_TABNAME = 'MARD'.
V_FIELDCAT-DO_SUM = 'X'.
V_LAYOUT-TOTALS_TEXT = 'TOTAL STOCK:'.
V_FIELDCAT-HOTSPOT = 'X'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '14'.
V_FIELDCAT-FIELDNAME = 'EBELN'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'EBELN'.
V_FIELDCAT-REF_TABNAME = 'EKPO'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '15'.
V_FIELDCAT-FIELDNAME = 'EBELP'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'EBELP'.
V_FIELDCAT-REF_TABNAME = 'EKPO'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '16'.
V_FIELDCAT-FIELDNAME = 'VBELN'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'VBELN'.
V_FIELDCAT-REF_TABNAME = 'VBAP'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '17'.
V_FIELDCAT-FIELDNAME = 'POSNR'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'POSNR'.
V_FIELDCAT-REF_TABNAME = 'VBAP'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
ENDFORM. "FIELDCAT
* FORM OUTPUT *
FORM OUTPUT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = SY-REPID
 I_CALLBACK_TOP_OF_PAGE = 'TOP-OF-PAGE'
 I_GRID_TITLE = 'CLICK ON MATERIAL/PURDOC/SALESDOC FOR DETAILS'
 I_CALLBACK_USER_COMMAND = 'DISPLAYDETAILS'
 IS_LAYOUT = V_LAYOUT
 IT_FIELDCAT = VT_FIELDCAT1
 TABLES
 T_OUTTAB = I_OUT.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM. "OUTPUT
* FORM TOP-OF-PAGE *
FORM TOP-OF-PAGE.
DATA: T_HEADER TYPE SLIS_T_LISTHEADER,
 WA_HEADER TYPE SLIS_LISTHEADER.
WA_HEADER-TYP = 'H'.
WA_HEADER-INFO = 'REPORT FOR : '.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'MATERIAL DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'PURCHASE ORDER DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'SALES ORDER DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 I_LOGO = 'GEAR'
 IT_LIST_COMMENTARY = T_HEADER.
ENDFORM. "TOP-OF-PAGE
*& FORM DISPLAYDETAILS *
FORM DISPLAYDETAILS USING UCOMM LIKE SY-UCOMM
 SELFIELD TYPE SLIS_SELFIELD.
IF SELFIELD-FIELDNAME = 'EBELN'.
 IF UCOMM = '&IC1'.
 READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
 PERFORM PORECDNG.
 CLEAR BDCDATA[].
 ENDIF.
ELSE.
 IF SELFIELD-FIELDNAME = 'MATNR'.
 IF UCOMM = '&IC1'.
 READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
 PERFORM MMRECDNG.
 CLEAR BDCDATA[].
 ENDIF.
 ELSE.
 IF SELFIELD-FIELDNAME = 'VBELN'.
 IF UCOMM = '&IC1'.
 READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
 PERFORM SALESRECDNG.
 CLEAR BDCDATA[].
 ENDIF.
 ENDIF.
 ENDIF.
ENDIF.
ENDFORM. "DISPLAYDETAILS
* FORM PORECDNG *
FORM PORECDNG.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0105'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RM06E-BSTNR'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
PERFORM BDC_FIELD USING 'RM06E-BSTNR'
 I_OUT-EBELN.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0120'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RM06E-BSTPO(01)'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=AH'.
PERFORM BDC_FIELD USING 'RM06E-EBELP'
 I_OUT-EBELP.
PERFORM BDC_FIELD USING 'RM06E-TCSELFLAG(01)'
 'X'.
PERFORM BDC_TRANSACTION USING 'ME23'.
ENDFORM. "PORECDNG
* FORM MMRECDNG *
FORM MMRECDNG.
PERFORM BDC_DYNPRO USING 'SAPLMGMM' '0060'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RMMG1-MATNR'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
PERFORM BDC_FIELD USING 'RMMG1-MATNR'
 I_OUT-MATNR.
PERFORM BDC_DYNPRO USING 'SAPLMGMM' '0070'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(01)'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
PERFORM BDC_FIELD USING 'MSICHTAUSW-KZSEL(01)'
 'X'.
PERFORM BDC_TRANSACTION USING 'MM03'.
ENDFORM. "MMRECDNG
* FORM SALESRECDNG *
FORM SALESRECDNG.
PERFORM BDC_DYNPRO USING 'SAPMV45A' '0102'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'VBAK-VBELN'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
PERFORM BDC_FIELD USING 'VBAK-VBELN'
 I_OUT-VBELN.
PERFORM BDC_TRANSACTION USING 'VA03'.
ENDFORM. "SALESRECDNG
* FORM BDC_TRANSACTION *
FORM BDC_TRANSACTION USING TCODE.
CALL TRANSACTION TCODE USING BDCDATA MODE 'E'.
ENDFORM. "BDC_TRANSACTION
* FORM BDC_DYNPRO *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM. "BDC_DYNPRO
* INSERT FIELD *
FORM BDC_FIELD USING FNAM FVAL.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
ENDFORM. "BDC_FIELD
*& FORM PURCHASEDATA_VALIDATION *
FORM PURCHASEDATA_VALIDATION.
SELECT EBELN EBELP MATNR
 FROM EKPO
 INTO TABLE I_EKPO
 FOR ALL ENTRIES IN I_MARC
 WHERE MATNR = I_MARC-MATNR
 AND EBELN IN S_EBELN
 AND WERKS EQ P_WERKS.
IF I_EKPO[] IS INITIAL.
 WRITE:/ 'NO MATCHING DATA AVAILABLE FROM TABLE EKPO'.
 EXIT.
ENDIF.
DATA: T_EKPO LIKE I_EKPO OCCURS 0 WITH HEADER LINE.
T_EKPO[] = I_EKPO[].
REFRESH I_EKPO.
FREE I_EKPO.
LOOP AT T_EKPO.
 SELECT SINGLE EBELN FROM EKKO INTO EKPO-EBELN
 WHERE EBELN = T_EKPO-EBELN.
 IF SY-SUBRC = 0.
 MOVE-CORRESPONDING T_EKPO TO I_EKPO.
 APPEND I_EKPO.
 CLEAR I_EKPO.
 ELSE.
 CONTINUE.
 ENDIF.
ENDLOOP.
SORT I_EKPO.
ENDFORM. "PURCHASEDATA_VALIDATION
*& FORM SALESDATA_VALIDATION *
FORM SALESDATA_VALIDATION.
SELECT VBELN POSNR MATNR
 FROM VBAP
 INTO CORRESPONDING FIELDS OF TABLE
 I_VBAP FOR ALL ENTRIES IN I_MARC
 WHERE MATNR = I_MARC-MATNR.
IF I_VBAP[] IS INITIAL.
 WRITE:/ 'NO MATCHING DATA AVAILABLE FROM TABLE VBAP'.
 EXIT.
ENDIF.
DATA: T_VBAP LIKE I_VBAP OCCURS 0 WITH HEADER LINE.
T_VBAP[] = I_VBAP[].
REFRESH I_VBAP.
FREE I_VBAP.
LOOP AT T_VBAP.
 SELECT SINGLE VBELN FROM VBAK INTO VBAK-VBELN
 WHERE VBELN = T_VBAP-VBELN.
 IF SY-SUBRC = 0.
 MOVE-CORRESPONDING T_VBAP TO I_VBAP.
 APPEND I_VBAP.
 CLEAR I_VBAP.
 ELSE.
 CONTINUE.
 ENDIF.
ENDLOOP.
SORT I_VBAP.
ENDFORM. "SALESDATA_VALIDATION

Error in process while creating Purchase order.

Hi,
    We are using ECS ,Purchase order is not getting replicated to backend as we are getting the following error " With non-valuated GR, please also enter GR indicator" .
Appreciate your inputs!!
Thanks
Rakesh.

Hello,
Please check note:1029209 is applied. Could you please deactive badi:BBP_DOC_CHANGE_BADI and test system behavior again.
Please check the following customizing in backend R/3 system.
(Tr:SPRO)
Materials Management
Purchasing
   Account Assignment
    Maintain Account Assignment Categories
Here, please double click "K" and remove flag for fields
"Goods receipt" and "GR non-valuated", after that, please create a new
PO and test system behavior again.
Kind regards,
Gaurav
PLEASE GIVE FULL POINTS FOR USEFUL REPLIES

Payment Processing tab in Purchase Order

Hi
can anybody help me, How do we get the Payment Processing tab which is used for Retention purpose ? Which SAP Note or package is involved in this as i am unable to find that tab? We have just installed SAP ERP ECC 6.0 EHP4. Kindly guide me.
Regards
Samuel
Edited by: samuel mendis on Sep 23, 2010 2:20 PM

un-answered

Cut off process for Open Purchase Orders

Dear friends
We are preparing for Go Live. i want to know what are the steps required in Cut off activities with respect to Open POs. E.g if there is a PO for 1000 units against which GRN has been done for 200 units and Invoicing has been done for 100 units. How would such Open PO uploaded in the system and what would be accounting implications?
Thanks
Amit

Hi Amit,
For Open POs there would be two types of situation:
1) No GR and IR has been done
2) Partial GR and IR have been done
In the first case you can upload all the Open POs using LSMW or any other program since GR and IR both would be done in SAP.
However for 2nd case, if GR has been done but IR has not been done then you have to post invoices using FB60 only since PO would not be having a history of GR. What you should do is post these types of GR entries to some Stock Clearing Account as credit and when you do invoice posting through FB60 in SAP debit this Stock Clearing Account. This will also give you tracking that until this GL Account becomes zero there are some entries to be passed.
Hope it answers your question.
Regards,
Sanjay

Creating deliveries from purchase order -Plant to plant process

Hi All,
I am carying out delivery creation in P2P process from a purchase order . There are two bill to parties assigned in customer. When i create delivery for first bill to party , system creates only one delivery for all line items . But supposed i create delivery for second bill to partyy , the system creates diferent deliveries for each line item . It gives message as delivery split because the partners are different . Can anybody help me why this is hapening .
Note : i have already maintained "order combination tick " in customer master and also in PO line item level .
Thankls
Rohit Chavan

Just check in the Second Bill-to party the following points as per the Line Items:-
1. Shipping point
2. Route
3. Ship-to Party
4. Incoterms
If the above mentioned are different,then delivery will be splitted into many Deliveries.
Best regards,
Ankur

GATP Product allocation status report and backorder processing

Dear Experts,
We are using product allocation as the first and only step in GATP check.
The scenario is like this:
Sales order total quantity = 200
Planned allocation quantity=150
Thus
Confirmed sales order quantity=150
Questions:
1.Now how can see the confirmed/unconfirmed situation for all sales orders.
Is there any standard report.
I understand that this report need to show the planned allocation quantity,total sales order quantity and the confirmed sales order quantity may be bucket wise.Also this report can show the details of all sales orders in the bucket.
The GATP planning book only shows confirmed sales orders in the "sales order" keyfigure until you have introduced another order series key figure for sales order(not related to GATP) which has sales order/scheduling agreement category group assigned to it.
2.Can I do backorder processing of sales orders assuming that after the above report is run,I have changed the planned allocation quantity from 150 to 200 and I need that the sales order can be confirmed now by this program rather than by going into ECC and triggering the GATP check again.
Note that the stock availability situation may remain the same.
Request you to kindly suggest if this is possible in backorder processing.If yes,then what are the settings and the transactions to execute this.
Thanks,
Chandan

Thanks so much Michael for a prompt reply.
Couple of points.
1./sapapo/ac42-This report is helpful but this has 2 issues.
It has to be run at individual CVC level.Thus it is not a comprehensive report.
It does not provide sales order original quantity.It just provides the planned allocation quantity,confirmed sales order quantity and the remaining quantity.This is normally already available in interactive planning of GATP planning area.
What we need is a report which must say what is the original sales order quantity and how much has been confirmed and how much is the bucket planned allocation quantity.
2.Running ATP in product view or interactive backorder processing view may not help as they seem to be working with ATP group and not with check mode.Note that product allocation gets triggered when check mode comes into play.
Do you know if we can make it work with check mode.
3.The batch backorder processing is working when I am using the "update changes" option.I am still evaluating the results as I don't understand many settings here.It will be nice if you can elaborate on some of the settings used in this transaction please.
Thanks again.
Regards,
Chandan

Restrict Posting of Goods Receipt by Purchase Order Type

Does anyone know of a way to prevent posting goods receipt for a specific purchasing document type? We need to prevent users from posting PO's that were system generated through an outside interface. They are brought back into ECC as the system of record. Since authorizations are only based on movement type, plant, and storage location with MIGO, without creating a new movement type, is there any way to achieve this?
Thank you in advance for your help!

Hi,
Normally it would be the other way around, where the continued process for Open Purchase Orders will be done in SAP ERP, and no longer continued in the legacy system.
So in your case, to avoid performing double posting (e.g. goods receipt in legacy and in SAP which causes duplicate inventory in books compared to physical) you would need to stop the Open POs in SAP ERP from being processed further.
Just to be sure, there are a few types of Open POs
1) Open PO where Goods Receipt have not been done.
For this type, normally we would be doing the future receipts in SAP ERP
2) Open PO where Goods Receipt done, but pending Invoice
For this type, we could ignore the PO all together and create a FI Invoice when the invoice comes. (The quantity is entered in SAP ERP via 561 initial stock balance movement type)
For type 1, if you perform goods receipt in legacy system, how are the quantities being captured in SAP ERP? How about payment, will this be done in legacy as well? How do you plan to reflect it in SAP?
For type 2, will you be performing invoice receipt and payment in legacy? How will it be reflected in SAP without being a duplicate with the legacy payment?
If you could answer these questions, then you could lock the SAP PO numbers by highlighting each line item, and click on the lock button. This will prevent future receipts in SAP.

Interactive Backorder Processing on Replenishment Purchase Orders

Similar Messages

Maybe you are looking for