SAP Logistics

 Issue  Delivery created from a sales order is distributed to the EWM system.  "Partial delivery at item level" is set to 'C' - Only complete delivery allowed Quantity is changed or Goods issue is complete in the EWM system.  Queue fails in the ERP system with error VL062 - "Full delivery is required" Solution Approach Maintain the following entries within your system using transaction OVM1 - if they already exist, adjust them accordingly: Application: 'L' - Shipping processing Call type 'D' - Confirm from external system Call type 'B' - Background processing, multiprocessing with Work phase 'B' Application Area = VL, Message no = 062, Type = I * Call type 'B' with Work phase 'A' is for background delivery creation.

  Issue   System carries out an ATP check despite the ATP check is deactivated in the schedule line category of the sales order in transaction VOV6. Root Cause The ATP check for sales orders with immediate deliveries is controlled by the following settings: ATP check setting in the requirement class (transaction OVZG) ATP check setting in the schedule line category (transaction VOV6) ATP check setting in the item category of the delivery (transaction 0VLP) It is not sufficient to deactivate the ATP check only in the schedule line category when ATP check is activated at the other two mentioned customizing settings. In immediate deliveries the ATP check is carried out with checking rule B (Checking rule for deliveries). The setting in the item category of the delivery is also important in this case. Solution Approach If you would like to switch off ATP in immediate deliveries you have to either: Switch off ATP check in the r...

 2799378 - ATP result does not match the quantity available in MMBE / MD04 1725088 - Discrepancy between transactions Co09 & Co06

 At times, there will be a situation where you want to control the accounting document type, not based on the billing type ( which in general is a standard behaviour) instead should determine it in a custom manner like based on company code etc. In this situation to accomplish the requirement, below below-mentioned exit needs to be implemented. EXIT_SAPLV60B_001

 At times, there will be situations where we are required to trigger a specific set of data during the creation/saving of shipment documents. In this situation, we are required to leverage the BADI 'BADI_LE_SHIPMENT' to accomplish the requirement 

At times, business requires to manipulate the delivery of foreign trade data such as country of origin or dispatch country etc..based on certain custom parameters. In this situation, we have to make use of the exit 'EXIT_SAPLV50E_003' to accomplish this requirement.

The system validates against the copy control table TVCPF and throws the mentioned error message. As a subsequent action, check if the billing document type is new then maintain the required copy control setup to fix the issue. Thank you

There will be situation where we require to amend the existing delivery Idoc with that of custom segments. In this situation, while generating the IDoc we are required to populate the custom segments values. Exit 'EXIT_SAPLV56K_002' can be used to handle this requirement. Thank you

 Pass the delivery number in the table  SER01 and fetch OBKNR Pass OBKNR into table OBJK to fetch serial numbers for the specific delivery We can use the same process as mentioned above for all SER* tables to fetch the respective data. Thank you

 At times, we will have a requirement to add custom fields in the customer master data. These new fields need to be sent to the other system through Standard  Idoc with DEBMAS message type. In this situation, we have to append new custom segment to the customer Idoc type and then populate the custom segment field values through the exit  EXIT_SAPLVV01_001 .  

************************************************** Material   Material basic data - MARA  Material Plant level data - MARC  Material Sales level data - MVKE  Material valuation data - MBEW  Material warehouse data - MLGN  Material/Batch data - MCH1  Plant/Material/Batch data - MCHA  Material stock data - MARD Material batch stocks - MCHB Material valuation data history - MBEWH Material stock data history - MARDH ********************************************** Transport  Transport Header Data - E070 Transport data view on objects - E071V *********************************************** Background Job table - TBTCP ************************************************ Idocs table  IDOC control record - EDIDC IDOC data record - EDID4 IDOC status record - EDIDS ************************************************     

Ideally, the route will be determined based on the below standard configuration at the sales order level. Standard SAP  The route  is determined automatically in the sales order based on:   Departure zone or country of the Delivering Plant Destination zone or country of the Ship-to Party Shipping condition from the Sold-to Party Customer master Transportation group from Material Master Custom But however, there are situations where standard SAP parameters cannot be used for route determination due to business constraints.  In this situation, SAP has provided an exit 'EXIT_SAPL0VRF_001' to accomplish custom requirements of route determination where businesses can maintain their own determinations.

Below are the 16 steps of the pricing procedure : Step  - It depicts condition type sequence similar to Sl.No Counter - it's a substep  Condition type - Pricing elements are represented as a condition type  Description - this field displays description of the condition type From, To    - From, and To  covers the Steps to be considered during condition value calculation  Manual - if we select this, condition type should be manually entered in the document Required - if we select this, the system will not allow you to save the document until it is entered Statistical - if we select this, the Specific condition value doesn't have any impact during the price calculation Print - if the specific condition type should be printed or not will be controlled in this field SubTotal - It's used for temporary storage and can be subsequently used in other calculations Alternate Calculation type - if the condition value should be derived based on a specific ...

  At times, we will have a table and requires to find a transaction for it.  In this situation, use the table - 'TSTCP' and pass the table name *XXXX* in the parameter field. Then click on execute to display the transaction for the table.

Once a sales order is created and pending for delivery then the system will update in delivery due list table VEPVG, which the system uses to fetch and process pending deliveries.   There will be some situations where the delivery due list table is not updated even though the sales order is not blocked and pending for delivery this will result in missing the sales orders for delivery creation. This issue will occur due to the incorrect way of handling user exits when X* and Y* tables are manipulated before save of the sales documents.   In this situation, program 'RVV05IVB' is used to reorganize delivery due list entries and fix the inconsistency   SNOTE: 128947 - Correction of SD document indexes with RVV05IVB   Report RVV05IVB is available in your system for reorganizing or correcting incorrect SD document indexes. The report can correct the following index tables: Table    Contents          ...

Characteristics values for an object cannot be extracted from the database table directly. Hence we are required to follow the below steps to fetch the data : First, pass the material into table KSSK and fetch object number Pass the object number into the KLAH table to fetch the class Pass the class into a functional module: 'CLAF_CLASSIFICATION_OF_OBJECTS' to fetch the characteristics and characteristics values.

FM: WS_LM_QUANTITY_ADD is used for checking the weight and volume of an outbound delivery to calculate the delivery weight, we have to keep the FM in the loop. FM: BAPI_OUTB_DELIVERY_CREATE_STO is used to create outbound delivery for a purchase document in the stock transfer process ensure to use COMMIT FM post calling the BAPI to create an entry in the database Table VBSS - to get group number based on the sales document    FM: WS_PICK_WAV_UPDATE_PREPARE' is used for the wave picking  FM:  RV_SHIPMENT_VIEW is used for viewing shipment FM: 'SD_DELIVERY_ASSIGN_TO_SHIPMENT' is used for the assignment of delivery to shipment FM:  SD_SHIPMENTS_SAVE is used for creating the shipment FM: BAPI_SHIPMENT_CHANGE is used for changing the shipment FM:  CS_BOM_EXPL_KND_V1 is used to fetch sales order BOM items

Ideally Storage Location is determined through standard SAP functionality maintained at delivery type level based on the below criteria : Shipping point + Plant + Storage Condition (MALA) Plant + Situation + Storage Condition (RETA) but however, if business requires to deviate from standard SAP criteria then we have to leverage the below exit to accomplish the requirement : V02V0002  EXIT_SAPLV02V_002

Automatic POD Concept For customer proof-of-delivery (POD) confirmations for an outbound delivery, you can define a time window in which the confirmation from the customer must occur. This time window is specified in units of days and stored in the field 'POD timeframe' of the customer master data for the sales area (KNVV-PODTG). If the current date and time in the local time zone (!) of the user running the transaction lies before the end of the time window, the transaction / program does NOT process the delivery, because the confirmation of the customer could still happen.   Logic for POD date calculation The end of the time window in which the POD is expected from the customer is calculated as the delivery date (LIKP-LFDAT) plus the POD timeframe as a net duration. Net duration means that only the working hours according to the factory calendar of the delivery (LIKP-KNFAK) are used for this scheduling. The factory calendar of the delivery is usually determined from the calen...

  Proforma invoice Goods issue is not required to create delivery related proforma invoice. Order related billing document If business requires to raise invoice before goods are delivered to customer or Service items then order related billing document is used Delivery related billing document If business requires to deliver goods to customer before raising commercial invoice then delivery related billing document is used