SAP Logistics

The physical inventory process plays a vital role in the warehouse as it is part of statuary requirements that all materials should be counted at least once a year. Physical inventory process can be carried out at Inventory Management level, Warehouse Management Level and Handling Unit level. This article will talk about the physical inventory process at Handling Unit level . Below are the HU physical inventory process steps : Create Physical inventory document - HUINV01 Change or delete physical inventory - HUINV02 Perform Stock Count - HUINV03 Perform Stock Recount - HUINV04 Post HU stock differences - HUINV05 Inventorize HU - HUINV06 Different status of HU's during Inventory: Before creation of physical inventory document - HU status will be PHEX and WHSE Ideally ( Available to use) Upon creation of physical inventory document - HU status will be INIV,PHEX and WHSE If Physical inventory document is deleted then system will remove INIV status again Perform Stock Cou...

 At times, We find difficult to identify exits for a program.  This post will explain you an easy way to find list of  Customer Exits and BADI's available for a program. Below are the process steps to be followed : Step 1 : Goto T.Code : SE16N, Enter transaction code  Step 2 : Fetch program name Step 3 : Collect Program Name and pass it to TADIR table to fetch development class Step 4 : Pass Development class again into TADIR table by passing OBJECT as SMOD to fetch all customer exit's and OBJECT as SXSD to fetch BADI's related to the program. In this case, I have passed SMOD to fetch customer exits. Step 5 : All Customer exits related to the program are displayed Step 6 : Once EXIT is identified. To get description related to it, Pass Exits into table MODSAPT and SXS_ATTRT to get descriptions corresponding to them. Thank you.  

If Quality management is enabled, stock posting from quality to unrestricted will be done from inspection lot. In this situation, There will be a case where business will take sample before batch release.If sample is good, then rest the stock will be posted to unrestricted stock. As per standard SAP functionality, Conversion from transfer requirement (TR) to transfer order (TO) will be done automatically only when full stock of inspection lot is moved in one go. If business consume some stock for sample, then auto conversion from TR to TO will not work as standard SAP functionality will not support for partial stocks. In this situation, We need to schedule a background Job for program - RLAUTA11 for auto conversion from TR to TO for partial stocks.

Per SAP Note - 2420306, There are no change documents for the transfer order tables LTAK and LTAP. Transactions to create/confirm transfer orders will update tables CDHDR and CDPOS in the event that certain other documents are changed - e.g. if a delivery is changed (CDHDR object class 'LIEFERUNG') or if a batch is changed (object class 'CHARGE') or if a handling unit is involved (object class 'HANDL_UNIT').                                                  This is because deliveries, handling units and batches can have multiple changes and therefore require a change history; whereas a WM transfer order is transactional. A transfer order is simply created then confirmed - there is no editing, therefore the transfer order includes the changes within its own document data.   ...

Error L3883 will be displayed if the business tries to perform partial transfer posting from HU-managed storage location to another HU-managed storage location. During analysis, we have identified that standard SAP doesn't allow to perform transfer posting with partial quantity in case of partner storage location is HU managed as well. So in this case, always transfer posting need to be performed for the complete quantity.

There is a common requirement from functional consultants on how to do debugging. Below is the raw info on the debugging and different ways of doing it. Debugging is a common tool used by the technical team to analyze dumps during transactional processing and program behavior. Through debugging we will come to know the run values of the program as well. Debugging can be performed in two different ways : 1. Debugging by watchpoint 2. Debugging by Breakpoint Debugging based on watchpoint At times, we are unsure about how the value is getting determined for a variable then we can put the watchpoint on the variable deriving the value so that the system will stop at all points where the value is being fetched for the variable. Debugging based on Breakpoint Debugging based on break point will be done only when the consultant is aware of the exact piece of code where a breakpoint can be enabled. The breakpoint can be done in two ways. Internal breakpoint E...