SAP Logistics

 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

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

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

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.

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

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

Commonly, Business contains conditions which should be applied to entire document i.e., header conditions.In general, maintaining the header condition in the sales or purchasing document leads to duplicating the condition value or amount to all line items instead of splitting the condition value amount the line items. Below is the case without Group Condition Business Process : In order to fix this issue, SAP has provided Group Condition Functionality which splits the header value among the line items instead of duplicating the header condition value. Below screenshots depict the Group Condition Functionality : Process Flow Thank you

During sales order processing, the system automatically determines individual purchase order items. However, you can also change standard items to individual purchase order items during sales processing manually. Material exclusive for Individual purchase order, If you procure a material exclusively by individual purchase order, you can define in the material master record that the material is always treated as an individual purchase order item during sales processing. The system will then automatically determine the appropriate item category TAB. To identify a material as an individual purchase order item in the material master record, enter BANC in the field Item category group on the Sales: sales org. 2 screen. Changing Manually in Sales Order If you want to use an individual purchase order to purchase a material that you normally produce yourself, you can overwrite the item category in the sales order, provided that the configuration o...

Business at times as a part of product sales dumps stock at the customer location and will bill the customer based on the customer sales. The business scenario of employees taking samples to showcase at Expo can be mapped through consignment process as well. In this case, the employee needs to be created as a customer. The consignment process in SAP standard consist of four Steps: 1. Consignment fill up (send materials to customer consignment). 2. Consignment issue (issue materials from customer consignment to the customer) 3. Consignment return (return materials from customer ownership to customer consignment) 4. Consignment pickup (pickup consignment stock and move it to plant stock) Sales Process Sales Document Type Item Category Schedule Line Category Movement Type Relevant for Billing Consignment Fill Up KB or CF KBN E1 631 No Consignment Issue KE or CI KEN C0 or C1 ...

Customer Master Data  KNA1 - General Data KNB1 - Company Code Data KNVV - Sales Area Data KNVP - Partner Function Data KNVI - Tax Classification Data Material Master Data MARA - Basic Data MARC - Plant Level Data MARD - Storage Location Data MARDH - Storage Location history Data MVKE - Sales Data MBEW - Accounting Data MBEWH - Accounting History Data Customer Material Info Record KNMT - Customer-Material Info Record Data Table Sales Document Data VBAK - Header Data VBAP - Item Data VBEP - Schedule Line Data VBKD - Business Data VBUK - Sales Document Status VBFA - Document Flow VBPA - Sales Partner Data Delivery Document Data LIKP - Header Data LIPS - Item Data Billing Document Data VBRK - Header Data VBRP - Item Data Pricng Tables KONV - Conditions (Transaction Data) Logic to fetch pricing data from KONV Table Fetch KNUMV (Condition Number)  from VBAK table and pass onto KONV table to fetch conditions data Pricing Fi...

Cash sale  Ideally, there will be customers for whom transactions will happen through Cash Sale and in this case below are the points to be remembered. Cash sales have one-time customer account group and Cash sales (CS) are also not relevant for credit management is used during sales order processing Delivery automatically happens when you save the sales order.   Cash sales is order related billing and doesn't have credit active Cash sales items are not relevant for picking during delivery processing as you will be picking the goods on our own. Ideally business uses separate shipping point for Cash sales delivery processing Billing type 'BV' is used during Cash Sale process Cash sales uses RD03 as output which immediately prints the invoice Cancellation document type 'SV' is used for cash sales Ideally, cash settlement account determination procedure 'KOFIAC' is used and Cash se...

In many sectors of industry it is common to provide products free of charge, or not to charge the customer for some of the goods sold when a customer purchases certain goods. Two types of free goods exist in SAP. They are 1.      Inclusive free goods. 2.      Exclusive free goods. Inclusive free goods             The customer pays only for a part of the goods required. The rest of the goods are for free. This is called inclusive free goods which mean that part of the purchased quantity is designated as free and not billed. The unit of measure for the inclusive free goods is same as the purchased quantity. e.g.:- of the ten bottles of wine ordered two are designated as free goods. If we order ten bottles of wine then ten bottles of wines are delivered to us as ordered but we are billed only for the eight bottles and two bottles are given as free. We have rec...