SAP Logistics

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

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

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

NAST table is used to store all output condition records whenever the output is triggered. At times, Business requires to delete the obsolete or Old NAST records which are no longer required.  Archiving of the output records will reduce the load and increase the performance of system during processing of output condition records. To archive obsolete condition records, SAP has provided standard program  RSCLNAST to perform this activity. Ideally, business can schedule a batch job once every month to delete the older records as per the data retention date range or this can be done manually as well.

BRF+ is the new output functionality provided in S/4 HANA. This new functionality, has it's own benefits where logo or addresses change doesn't require technical team but this has it's own limitations. BRF+ cannot be used if one of the following NAST transmission mediums is required: 8 Special function 9 Events (SAP Business Workflow) A Distribution (ALE) T Tasks (SAP Business Workflow) In this case, if business is inclined to use the above mentioned mediums then business has to be use NAST-based output management (NACE) along with BRF+ which SAP supports. In general, BRF+ can be widely used if business require to use print and email functionality.

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.

Commonly, We schedule background job for every 5 min or so on periodically depends on the functionality of the program and data updates required. In this situation,there might be a situation where previous background job still continue to run even after next schedule due to data or some other reason. This will make two jobs of same program run parallel and might create locking or performance issues. To avoid such situation, We can add a step to the existing background job prior to the step of the actual program. The below mentioned program should run prior to the actual program execution.  This program will check and cancel the subsequent job of the next run if the program still runs before next execution. Program Name - RSBTONEJOB Note that the variant of this program should be maintained with same name as that batch Job name.