SAP Logistics

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 External b

If a business requires to close a delivery if it is no longer required as this will have an impact at MRP level. Support team will have two ways to handle this situation. 1. delete the delivery 2. Change the status of the delivery to complete Deletion of delivery will happen only if the HU's doesn't have any movements. if the delivery provided by user is old, then the HU's might have used in some other place. So, in this VL_COMPLETE is generally used when business requires to change the status of the delivery to complete if business no longer requires that delivery.

At times, Business will face delay during transfer order confirmation and this might be occurred due to the handling units or data reasons and this might lead to inconvenience for business users. SAP Support team suggested to enabled delayed delivery update functionality to fix this issue and below is the path to be followed : Warehouse Management under Interfaces -> Shipping -> Shipping Control -> Shipping Control per Warehouse Number in the field Delayed Delivery Update. In some rare cases, this update might impact on the transfer order confirmation, where status of the delivery will not updated even though picking is completed. This need to be fixed by executing LX47. Thank you.

SAP Retail is an industry-specific solution solely cater for retail needs. Similar to the manufacturing system, retail consists of SD, MM FICO modules primarily. To handle retail functionalities, we have retail consultant as well. There is a general terminology difference between retail and manufacturing system but however, the core functionality is the same. Terminology ECC                                                 Retail Material                                        Article Plant                                             Site Manufacturing plants or depo are treated as plants in the ECC system. In Retail, Stores and distribution centers are treated as Sites. The site creation is part of master data in Retail but whereas Plant is configuration activity in ECC. Material Group                             Merchandise Category In ECC Material group is primarily used for reporting and pricing. This is optional functionality in ECC system but in Retail, all a

IDocs is an abbreviated form of Intermediate Documents. Data from SAP will send in the form of IDoc between SAP ----> SAP or SAP ----> Non SAP. Type of data exchanged between systems Master Data  Transactional data Master Data Master Data can be manually / Automatically pushed. The manual push of master data can be done by respective transaction codes and we can schedule the batch job for an auto push of master data. Sample T.Codes Send Material Master Data ---> BD10 Send Customers Master Data ---> BD12 Send Vendor Master Data ----> BD14 Send Cost Center Data  ---> BD16 Transactional Data Transaction data such as Sales Order, Delivery, Purchase Orders etc will be sent through Output Setup where IDocs will be triggered based on the Output with Medium '6'. The output type is linked with Message type in the partner profile. To enable an exchange of change data between system then we are required to create a new output ty

Requirement Business requires to auto clear customer down payment upon receipt of payment. Standard Ideally, T.Code F.13 is used for clearing of customer,Vendor and GL account postings but where this T.Code doesn't support clearing of special GL's. Custom Development In this situation the solution that we have given to accomplish this task is through custom development, Where a BDC program is prepared for T.Code F-39 and is included as implict enhacement in FM POST_DOCUMENT such that whenever customer downpayment is received clearing will happen automatically. Thank you.