SAP Logistics

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

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