SAP Logistics

At times, business wish to have custom criteria to perform availability check. In this situation, we can make use of the customer exit  'EXIT_SAPLATPC_001 ' to manipulate the values before passing on the data to perform availability check of a specific material.

 Below are the commonly used transactions in SAP EWM Monitor  /N/SCWM/MON Outbound Delivery ODO    /N/SCWM/PRDO Maintain Wave     /N/SCWM/WAVE Inbound Delivery   /N/SCWM/PRDI Internal Move product/ Create WarehouseTask    /N/SCWM/ADPROD Move HU/ Create HU WarehouseTask     /N/SCWM/ADHU Make Posting Change for Product   /N/SCWM/POST Confirm Warehouse Task    /N/SCWM/TO_CONF Log on RF Environment    /N/SCWM/RFUI Pack station    /N/SCWM/PACK Process Transportation Unit     /N/SCWM/TU Physical Inventory Create Phy Inv Doc       /N/SCWM/PI_CREATE Enter count Results          /N/SCWM/PI_COUNT Difference Analyzer         /N/SCWM/DIFF_ANALYZER Master Data Maintain Resource      /N/SCWM/RSRC WorkStation Master Data       /N/SCWM/TWORKST APO Product          /N/SAPAPO/MAT1WM Product         /N/SCWM/MAT1 Storage Bin            /N/SCWM/LS03 Load Storage Bind              /N/SCWM/SBUPLoad Storage Bin sorting            /N/SCWM/SRTUP Outputs PPF processing of Outputs             SPPFP

 At times, we might require validations to be maintained during warehouse creation like keeping an error message during the creation of a warehouse task if an open warehouse task exists for the same HU As standard SAP behaviour will not restrict warehouse task creation of the same HU that contains an open warehouse task already.  In this situation, we are required to implement BADI '/SCWM/EX_CORE_CR_INT_CR' to accomplish this requirement Thank you

 As per standard SAP behaviour, if we move the HU to another HU with the transaction /SCWM/ADHU, the destination HU will become a nested HU. if we want to move the stock without HU, we can use transaction /SCWM/ADPROD Field ' Control F. HU Pick' in the warehouse process type controls this behaviour. Thank you

At times, business requires to manipulate the delivery of foreign trade data such as country of origin or dispatch country etc..based on certain custom parameters. In this situation, we have to make use of the exit 'EXIT_SAPLV50E_003' to accomplish this requirement.

 Pass the delivery number in the table  SER01 and fetch OBKNR Pass OBKNR into table OBJK to fetch serial numbers for the specific delivery We can use the same process as mentioned above for all SER* tables to fetch the respective data. Thank you

 Below are the commonly used exits at shipment document level EXIT_SAPLV56U_003 is used for handling number ranges i.e, sometimes there will be a requirement to have the same shipment number as that of the DWM in that case, you can leverage this exit EXIT_SAPLV56U_004 is used to write custom functionality or validations based on the shipment status

Below is the BAPI to be used for converting from one currency to another currency based on the exchange rate on a specific date. Below are the parameters to be passed to fetch the required information.   CALL  FUNCTION  'BAPI_EXCHANGERATE_GETDETAIL'        EXPORTING         rate_type   = <Exchange rate type >         from_curr   = <From Currency>         to_currncy  = < 'Currency'>          date        = < Date >        IMPORTING         exch_rate   =  < >          return      = < >     

At times, businesses will ask for a report based on the table extract of single or multiple tables. As this is a direct table extract, we need not take the help of a developer to extract the data from the tables. SAP has given a provision to generate this kind of report by functional consultants rather than taking the help of the technical team. This report extracts by the functional team will be done with the help of SQVI and SQ01 queries. SQVI query created by a user cannot be accessed by another user ( User Dependent) SQ01 query created by a user can be accessed by other users based on the user group ( User Independent) SQVI queries in general will be generated by the business and consultants will mostly assist business users. But at times, consultants use the SQVI query to extract specific data in a quick way as per business needs and then subsequently extract them to excel and provide the required information to business users. If business insists on the query access for the SQVI,

Enterprise Structure Assignment  Relationship between individual org. elements are maintained here ********************************************************** Plant to company code assignment : Can we assign one plant to multiple company codes? One plant can be assigned only to one company code one company code can have multiple plants  ************************************************************ one plant can have 'N' number of storage locations ************************************************************ Purchase organization to company code assignment Can we assign one purchase org. to multiple company codes? One Purchase org. Cross company code purchases if I assign company code to purchase org. then I am restricting purchase org. to specific company code If I do not maintain any company code in the assignment then the purchase org. can be used for purchase goods for multiple company codes ************************************************************* Purchase organization to

 At times, business requires release strategy to be triggered for purchasing documents based on custom parameters or through internal validations. In this case, we cannot go through the standard release strategy due to custom validations or fields.  To accomplish this requirement, new logic need to be maintained in Customer exit: EXIT_SAPLEBND_002 .  Through this exit, we can perform changes to the communication structure.

Enterprise structure is the term used for organizational structure in SAP. All the company organizational elements are mapped at the enterprise structure level. Below are the important elements of organizational structure from a Material Management (MM)  perspective : Purchase Organisation Purchasing group Plant Storage Location Purchase Organisation Purchase organization is the legal entity and is responsible for all kinds of purchase activities within an organization. Ideally, Purchasing department is a company that is represented as a purchase organization Purchasing Group Buyer or group of buyers in a company purchasing department are represented as a purchasing group in SAP Plant  A manufacturing entity of a company or depo or any location that involves some kind of activity in a place can be treated as a Plant in SAP Storage location it's a subdivision of a plant where the stock will be kept. Setting up of enterprise structure is done in two parts : 1. Definition 2. Assignmen

 At times, there is a a situation where the business requires a release strategy to be triggered if there are any changes to the purchase order document value either increase or decrease of document value. In general, standard SAP does trigger a release strategy if there is an increase in document value but however, if there is any decrease in the document value system doesn't trigger release strategy. This post covers the technical changes that we have to make to trigger release strategy if there is any decrease in the document value to that of the released amount. Release strategy at purchase order level is triggered based on the function module - 'ME_REL_STRATEGIE_EKKO' so we are required to make changes in this FM to accomplish this requirement. Perform reset is used to reset the release strategy post-release of the document. IF  cekko -gnetw  GT f1 .            PERFORM reset              USING e_frgst e_frggr                   e_frgzu e_frgkz e_frgrl .           e_

  At times, we will have a table and requires to find a transaction for it.  In this situation, use the table - 'TSTCP' and pass the table name *XXXX* in the parameter field. Then click on execute to display the transaction for the table.

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

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

 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.

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