SAP Logistics

  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

Shipping Point 1 As soon as the material availability date or the transportation scheduling date for a schedule line is reached, the schedule line becomes due for shipping. I.e., Order will be displayed in the delivery due list VL04. Point 2 Delivery block can be controlled in Sales document type (Header Level) and Schedule line Category (Schedule line level) Point 3 Delivery status of an order is updated upon creation of the delivery document. Delivery status is updated at header and Item level of sales document Point 4 Shipping Point Determination Shipping point is an independent organisation unit within which processing and Monitoring of the deliveries as well as goods issue is carried out. A delivery is processed by one shipping point only. Shipping point can be determined for each item based on the below criteria. Shipping conditions from customer master data + Loading group from Material master record + Delivering Plant. Delivery can be process

Message type ' CRESTA ' (FM -  IDOC_INPUT_CRESTA )  is used to distribute the credit management information between SAP systems and Non-SAP to SAP systems in case of business uses central finance. Standard SAP has provided transaction Code 'FCV1' is create A/R summary report which will subsequently generate CRESTA IDoc with customer credit information. This program creates A/R summary data within a control area per credit account. This data can then be used either within distributed credit management, or in a non-distributed system. CRESTA IDoc will not update the credit master data (FD32) in the the target system instead it will update  A/R summary data in the credit master data. In technical terms, System will not update table KNKK ( Credit Master data) instead it updates KNKKF* tables (Credit Management: FI Status Data). While creating the sales order, system will perform credit check based on the data from

 At times, You might find it difficult to find the open transport request for a smart form, program, table or any when developer take over the project in between. In this situation, We have taken an example to find transport request for a smart form to shown case the process to be followed. Step 1 : Go to transaction code - SE03 and then select find objects in request/tasks. Step 2 : By default system doesn't provide you object type for smart form. Hence Enter object type as 'SSFO' and then enter form name in the object name field . Step 3 : Select the object and select request status as both' Released' and 'Modifiable' Step 4 : Click on execute button to get the TR details Step 5 : Double click on the TR to get objects included in the transport request. Thank you.

At times, business is raise request to add custom fields in the billing documents report (VF05N). This document will provide you an easy to accomplish this request. In this document, We have considered an example where business requires Customer name to be displayed as standard SAP provides only Customer Code. Below are the process steps to be followed to accomplish this request. Step 1 :  Report layout is displayed with the number of fields containing in the structure -  ERPSLS_BILLDOC . So in this case, We have added Customer name in the mentioned structure. Step 2 : To populate values in the newly added field in the structure, We have used implicit enhancement as per the below. Goto Report of VF05N - ERPSLS_BILLDOC_VIEW and then go to include - ERPSLS_BILLDOC_VIEW_DATA_SEF01 Post processing of call function - ERPSLS_BILLDOC_VIEW   Write the below code which is used to populate customer name IF LRT_DOC[] IS NOT INITIAL. select KUNNR,name1 from kna1 into table @DATA(LRT_DOC_TEMP) FOR

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.  

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.

Report: RM07KO01 - Stock consistency check between ML and IM Description : With the Stock Consistency Check report (RM07KO01), you can check the consistency of your stock data at company code level, valuation level, or material level. Possible errors in your stocks can thus be determined at an early stage before they cause major problems Transaction Code : CKMC - Consistency check between Material Master and Material Ledger

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.

Both LTMC and LSMW are commonly used for migrating the data and both are available in S/4 HANA system. But however, Per comunication from SAP, LSMW will no longer be developed and  LTMC is the tool suggested by SAP going forward from S/4 HANA. Below are the few details of activating LTMC in S/4 HANA system : Feature – Data Migration Cockpit S4H Option – On-Premise Below are the activities need to be performed to activate LTMC : 1. Activate the service ' dmc_wda ' through SICF transaction  2. Maintain Host as below in the below path : -  To be maintain in individual system Host should contain SAP Logon pas IP address and the Host name displayed in the URL. Once the above steps are completed : Goto Transaction Code – LTMC to launch it.

Core component of SAP Retail is Retailing functionality which mainly covers SD,MM & WM. When Log on to SAP Retail, system will in general display SAP Easy Access menu meant for generic to Manufacturing domain but however if we require default screen to be displayed as Retail Easy Access  Goto User Own data ----> Goto Defaults  and enter W10T in Start Menu. Below are the Retail Terminologies commonly seen :    SAP Retail                                                                        R/3                                                                        Article                                                                                 Material Site                                                                                         Plant Logistics Calendar                                                Factory Calendar Merchandise Category                                         Material Group Requirements Planning                                    Materials

There are two types of commonly used requests : 1. Customizing request 2. Workbench request Customizing request is client specific request but where as workbench is cross client request. Applicable for customizing request only Client to Client transport request movement within the same server: In general, configuration changes will be performed in Golden client and then move the changes to Test client within development system This will be done through transaction code - SCC1 without the release of TR Applicable for customizing and workbench request Moving changes between systems : If we require to move changes from development system to any other system ( Quality or Production) , transport request ( TR) need to released through SE09. Then BASIS team is required to perform STMS_IMPORT to import the changes into the respective system.

MM Configuration for the plant : Creation of the plant - V_T001W Assignment of storage location to the plant - V_T001L Assignment of the valuation area to Company code - V_T001K Assignment of the purchase organisation to the plant - V_T024W Maintain stock and value update for the respective material types linked to the plant - T134M Maintain Plant parameters - V_159L Maintain negative stocks to the storage location ( if required ) - MM ---> IM ---> Goods issues SD Configuration for the plant : Shipping point determination - TVSTZ Assign sales organization - distribution channel - plant - V_TVKWZ_ASSIGN Assign shipping point to plant - V_OVXC Define, copy, delete, check shipping point - V_TVST Storage location determination - V_TVKOL PS configuration for the plant : Specify Parameters for Network Type - V_T399X_NN Specify Parameters for Network Scheduling -  V_TCX00_FAUF Define Checking Control -  V_TCO11 Define Confirmation Parameters - V_TCORU_P In case

Based on SAP Note -  2590037 - Output Management for Deliveries Output control for delivery documents is still based on the former SD output control framework (NACE) The new output management framework is not yet supported for delivery documents in SAP S/4HANA. Path to configure Output Control for Deliveries You configure output control in the Implementation Guide (IMG) under Logistics Execution →  Shipping → Basic Shipping Functions → Output Control.

At times, We might require to enhance the item segment of the Standard Purchase Order confirmation IDoc type 'ORDERS05' which requires two activities to be performed in this situation: Append the new field to the segment Populating values in the fields during IDoc processing Append field in the segment The custom field is required to be appended to the item segment field 'EIEDP01' which is a structure through append structure functionality in SE11 Populating values in the fields during IDoc processing Populating values in the custom field related to the item segments of the purchase order 'E1EDP01' will be accomplished through the customer exit 'EXIT_SAPLEINM_002' Thank you.

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.                                         Therefore, if you wish to check change logs relating to a WM document, you could

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th