Skip to main content

Individual Purchase Order - SAP SD

During sales order processing, the system automatically determines individual purchase order items. However, you can also change standard items to individual purchase order items during sales processing manually.

Material exclusive for Individual purchase order,

If you procure a material exclusively by individual purchase order, you can define in the material master record that the material is always treated as an individual purchase order item during sales processing. The system will then automatically determine the appropriate item category TAB.

To identify a material as an individual purchase order item in the material master record, enter BANC in the field Item category group on the Sales: sales org. 2 screen.

Changing Manually in Sales Order

If you want to use an individual purchase order to purchase a material that you normally produce yourself, you can overwrite the item category in the sales order, provided that the configuration of your system permits it. The standard version of the SAP System, however, does not support this transaction.

Enter the item category group NORM in the Item category group field in the Sales: sales org. 2 screen of the material master record for materials that you normally produce yourself.
If, as an exception, you purchase a material using an individual purchase order, change the entry in the ItCa field in the sales document from TAN to TAB.

Changing the Sales Order

You cannot subsequently change the quantity or the delivery date for an individual purchase order item in the purchase requisition. You can only change them in the sales order. Changes you make in the sales order are always automatically reflected in the corresponding purchase requisition, as long as this is permitted by the release status for the purchase requisition.

Shipping and Billing


When you create a delivery, the system checks if goods are available in the sales order stock. You then create a delivery-related billing document.

Process Flow

1. Create Sales Order Using VA01  ( Ensure to Maintain Item Category as 'TAB'
2. Goto change mode of sales order using VA02 and fetch PR number populated at line item schedule line level
3. Create Purchase Order with reference to Purchase Requisition using ME21N ( Manual )
4. Perform Goods Receipt using T.Code MIGO ( Special Stock 'E' sales order stock gets updated)
5. Upon MIGO, We are allowed to create delivery and perform Goods issues against the sales order stock
6. Perform MIRO ( Vendor Invoice)
7. Create Customer invoice using VF01

Reports :

Sales Order stock can be monitored through MMBE

Comments

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...