SAP Logistics

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 new output ty

Requirement Business requires to auto clear customer down payment upon receipt of payment. Standard Ideally, T.Code F.13 is used for clearing of customer,Vendor and GL account postings but where this T.Code doesn't support clearing of special GL's. Custom Development In this situation the solution that we have given to accomplish this task is through custom development, Where a BDC program is prepared for T.Code F-39 and is included as implict enhacement in FM POST_DOCUMENT such that whenever customer downpayment is received clearing will happen automatically. Thank you.

We normally come across warehouses which is handled in Cases/Boxes or Pallets. Handling goods in this manner will make life of the warehouse clerk easy. Warehouse activities is broadly divided into three categories : 1. Inbound 2. Outbound 3. Internal Inbound activity Receiving department of the warehouse will be responsible for this, Where they deals with receiving of goods from the vendors. Whenever we receive stock into a storage location which is HU Managed then delivery will be created automatically based one the settings in the LG-HU view. In delivery will be do packing and put the stock the respective location. Outbound Activity Dispatching the goods to the customer will be done through this process. Ideally shipping department is responsible for this. During dispatch to customer stock from a HU managed storage location stock need to be packed and only then goods issue will be allowed to be performed Internal Activity Movement of goods within the warehou

Business at times raise a question like why PR header text is not copied to PO but whereas Item Text is copied. This cannot be done through standard SAP functionality and Exit - 'EXIT_SAPMM06E_012' is used to accomplish this. Thank you.

At times, there might be cases where file not getting stored in the required path after execution of the program. In this case instead of reaching out to technical team functional team can check if the given path is valid and ready to receive  using the below T.Codes. CG3Y - To Save a file From Application server to Presentation server directly. CG3Z - To Save a file From Presentation server to Application server directly.

Ideally in order to fetch any data pertaining to text technical team will use ' READ_TEXT' functional module in order to fetch data. At times business might require fetching data functionality rather than programmatically then in that case below are the steps need to be followed.

At times business requires appending new fields to the ME1P report output. In this case below is the logic needs to be implemented. Append new fields into Standard Structure - 'MEREP_OUTTAB_PRHIS' Write implicit in the function module - 'MEPOBADI_CHANGE_OUTTAB' Thank you.

2315269 - FSCM Credit Management: Error when calling credit management (Technical error, web service issues) T.Code to check credit Management Web service calls failure - SRT_TOOLS, SRT_MONI All service failures will be checked in Dump Analysis T.Code - ST22 814637 - Credit Management: Various corrections

Business Requirement: If the customer is blocked due to credit then credit release should happen only for the first time. When the second order is created for the customer and is blocked for credit then the system should through error message with below info Solution approach: Userexit_SAVE_DOCUMENT Logic If SY-TCODE EQ ‘VKM4’ Pass KUNNR into Table VBAK and fetch all entries where VBAK – CMGST = ‘D’ and VBAK-GBSTK and VBAK-LFSTK = ‘C’ If SY-SUBRC is INITIAL Pass VBELN into table VBFA-VBELV and fetch VBELN with VBTYP_N = ‘M’ If SY-SUBRC is INITIAL Pass VBELN into Table BSID – ZUONR and fetch BELNR If SY-SUBRC is INITIAL Message ‘Payment pending for Order exist. Hence cannot release this Sales Order’ type ‘E’.

Display Credit Exposure - UKM_BOL_COMMITMENTS_1 This gives the list of open document and levels at which they are in  open status i.e., order, delivery or Billing Table - V_UKM_TOTALS This table gives the commitment amount and the exposure perceived Report - UKM_RVKRED06 The report checks all blocked documents from the credit view Report - UKM_RVKRED77 This is used for the reorganization of credit data after update errors

Mass printing of sales orders will be done through Program - 'SD70AV1A'. There is no standard T.Code assigned to it and if business required to make use of the program front end then we are required to create a custom T.Code for it. Mass Printing of Outbound deliveries will be done through T.Code - VL71 Mass Printing of Handling Units will be done through T.Code - VL74 Mass Printing of Billing documents will be done through T.Code - VF31

At times business might require additional fields in addition to the standard fields provided by SAP. In this situation, SAP has given a provision to add those fields in Purchase order header data. Below are the process steps need to be followed to accomplish this task. Step 1: Append the required custom fields in EKKO table Step 2: Goto SE51 Program - SAPLXM06 Screen number 101 and go to Layout to add the required custom fields. Below is the screenshot for reference. Thank you.

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

Ideally, There will be cases where we are required to fetch business partner from customer number. In this case, we have to use the below tables and logic to do so. Pass KUNNR into TABLE CV1_CUST_LINK and fetch PARTNER_GUID Pass  PARTNER_GUID into table BUT000 and fetch  PARTNER

At times, business requires using old condition technique functionality instead of BRF+ functionality for output determination. Below are the steps need to be done for activating NAST based output determination. MMPUR_OUTP_CTRLV Purchase Order - F  Maintain as New output Management is not active VV_MMPUR_OUTP_F Maintain as New output management for purchasing documents is not active Maintain the above entries in the respective views to activate NAST output technology Below is the SAP Note for Reference. 2442696 - SAP S/4HANA Output Management for Purchase Orders

By default downpayment functionality for MM is not activated for S/4 HANA on premise. If the business requires, then business function - LOG_MMFI_P2P need to be activated in T.Code SFW5. Note: Business function activation is nonreversible once activated. Thank you.

Material Determination uses condition technique to swap one material for another in a sales order when certain conditions apply. Substituting one product with another product is called material determination. The product is only substituted during the specific period. You can use material determination if you want the system to automatically substitute, for e.g.: Customer specific product numbers with your own material numbers. International article numbers (EAN's) with your own material numbers. Substituting discontinued materials with newer materials Seasonal products. SPRO- IMG- SD- Basic Functions- Material Determination- Maintain prerequisites for material determination Assign procedure to sales doc types: determination rule Condition Technique Create Condition Table Maintain Access Sequence Maintain Condition Type Maintain Procedure Assign Procedure to Doc Type Define substitute reasons: OVRQ   Define Substitution Reasons: go to

This functionality is used by SD, MM, PP, WM Module and can be handled at client , Plant and Material Level. Configuration Condition technique Condition table ------> All possible combinations of deriving batch will be created in the form of condition table Access sequence  -----> Assignment of Condition table will be done Strategy type ----> Assignment of Access sequence will be done and besides it In this selection class and the sort sequence will be assigned Controls Classification of batches, sort sequence and Batch split Batch search Procedure  -----> Assignment of strategy type for Procedure will be done Sales area and document type ----> Assign Batch search Procedure Automatic batch determination need to be activated at Sales order and Delivery Item category level. If batch is determined at sales order level then this will be copied over to Delivery. Ideally it's better to determine batch at delivery level. Create a material which is

Logic to display final approver name  Fetch FRGGR FRGSX FRGKE by passing EBELN and FRGRL Eq ‘X’ Into table EKKO Pass FRGGR FRGSX into table T16FS and Fetch FRGC1 , FRGC2 , FRGC3 , FRGC4 , FRGC5 , FRGC6 , FRGC7 , FRGC8. If NOT FGRC1 IS INTIAL AND FRGC2 IS INITIAL PASS FGRC1 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC2 IS INTIAL AND FRGC3 IS INITIAL PASS FGRC2  INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC3 IS INTIAL AND FRGC4 IS INITIAL PASS FGRC3 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the repor

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

Order Required field : The Order Required field is used to specify the document type to be referenced in the creation of this delivery. Default Ord. Type : Specify the default order type here. If a delivery is to be created without reference, you need to specify a “pseudo” order type, which is a reference order type that is required from an internal control point of view. For example, in the case of delivery type LO, the default order type is DL. This order type is configured like any other sales document. Item Requirement: This is a provision to attach a requirement routine for delivery items without reference to a sales document. 201 No ord.w.indep.item Maintaining this routine will restrict user from adding new items at delivery level 202 Order w IndpdntItem Maintaining this routine will allow user to add new items at delivery level independent of sales order or preceding document Delivery Rescheduling You can control whether a redetermination

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 of yo

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

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport

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 Field Catalog Structu

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 settlement account will be debite

Revenue account determination is one critical integration point between Sales & Distribution and Financial Module. Here on posting a billing document to account, based on this revenue account determination, system determines relevant G/L accounts for revenue posting. As like any other basic function configuration like pricing, its configuration also based on condition technique. The condition technique is used in account determination in order to allocate the correct GL account and account key assigned in the pricing procedure against condition types carries the condition values from SD to FI. IMG -> SD -> Basic Function -> Account Assignment -> Revenue account determination -> Check master data relevant for account assignment. Through check master data relevant for account assignment, one has the opportunity to create account assignment grouping criteria. This grouping criteria provides the system with an extra variable in determ