SAP Logistics

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