SAP Logistics

This is the common requirement from business to create new commodity codes as a part of the day to day activity. In general, Consultants consider this as a change request but this can be done through a standard program provided by SAP. This program can be enabled only with a minor config change specific to the country commodity code is applicable which is a one-time activity. Once done. Business can leverage the standard program through T.Code VI94. New commodity code needs to be maintained in a flat file using the above T.Code. Note: This T.code will only be applicable for EU nations and for other nations SAP has provided different T.Code which we need to be utilized to perform the activity. Thank you.

This is the common issue faced by most of the business users as business try to perform reversal than in LT0G item will be locked status as the existing quant was disturbed. In this scenario, we can we use the below process steps to fix this issue. Below are the process steps to fix this issue per recommendations by SAP.   Use transaction LT01 to manually create a TO and move the stock back into the warehouse. The delivery is not updated when LT01 is used so the pick quantities need to be reset to 0. To do this, change the delivery quantity to 0 and then copy the delivery quantity as pick quantity (Menu path Edit -> Copy pack quantity as delivery quantity). Once the pick quantity has been reset to 0, the delivery quantity can be changed back to its original value or the item can be deleted if it is no longer required. Report RVDELSTA can be executed to update the delivery WM and picking status. Change Delivery Quantity to '0' without performing changes at...

In general, When the business receives an order from a customer and in return business transfer the order to the manufacturer such that OEM delivers goods directly to the customer. This process is termed as third party process where goods will be directly dispatched to the customer. Below are the trigger points : 1.Item Category - TAS with billing relevance as ' F' Order related billing with Invoice Quantity 2. Schedule line category - CS with account assignment category as '1' and Item Category '5' Check P. Req Del. Sched if we require passing Sales order schedules to Purchase Requisition 3. Assign Order related Billing type at document type level. 4. Billing Quantity at Copy Control should be ' F' Based on the above setting Purchase Requisition gets generated upon save of sales order. As Account assignment category '1' is not relevant for goods receipt so upon Purchase order invoice document will be done. On...

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

Many might not have a clear idea of how credit values get updated in info structures S066 and S067. Per standard system behavior, Infostructure S066 should be updated with open sales order value items which are relevant for delivery and S067 should be updated with open delivery and billing values. Subtotal 'A' in the pricing procedure is used in deriving the credit price of a material and this will be calculated against the confirmed open schedule line quantity to get the open order value.

Commonly, Business receives less than the ordered quantity from the vendor ie., short delivery will happen then in the case the remaining quantity will still appear in requirements list until it is delivered. If no further deliveries are expected from the vendor then this requirements need to removed from the requirements list else it will mislead the MRP controller. So In order to remove them from MD04 then we need to perform any of the below activities.  1. Reduce the PO quantity to that GR quantity so that no remaining quantity exists 2. Maintain delivery complete indicator for the PO line item so that remaining quantities will not be displayed in the MRP. Below is the process steps for reference. Delivery complete indicator is maintained against the PO line item Remaining quantity got removed from the MRP list.

Standard SAP doesn't control the change of quantity at inbound delivery due to this business user will have a provision to increase the quantity of the inbound delivery to that of Purchase order quantity. This will be commonly seen when an inbound delivery gets created through IDoc, System by default will create for the quantity received rather than validating against the PO which will be quite confusing for the buyer and receiving department. To restrict this, SAP  has provided message control functionality. Below is the process steps to achieve this. AS IS Config Changes at Message Control Level After Change Increase the Inbound delivery quantity to that of PO quantity then system will throw an error message as stated below Thank You.