SAP

During a pricing Determination, if several valid Condition Records were available for a Condition type, We can define a Rule to determine a condition record to be considered a to be ignored For example, we want a most favorable condition record among valid for a single condition type, then we define a Condition Exclusion and set Rules Configuration of Condition Exclusion: 1. Condition Exclusion for a Group of Conditions: Under this node we have several sub-nodes 1a.  Define Condition Exclusion Groups:                     1b.    Assign Condition types to the exclusion Groups                                   1c.  Assign Condition Exclusion to the Pricing Procedure:                            In this Configuration, we have procedu...

In all Sales Business Cycles, Returns from customers are Normal, Returns can be expected when 1.  Customers expected Quality is  not met by the  product delivered 2. Some times Customers Orders more products than it is required 3.  DOA or Miss shipments ( wrong Products delivered). In above all cases, Customers will return the material,  and these returns can be handeleted by ADVANCE RETURNS MANAGEMENT ADVANCE RETURN ORDER :                            Advance Return Order is the document  which initiates the Customer Returns                         It Controls , how a return should happen and its Results We have to enter   RETURN  REASON :  Reason for Customer Reason MATERIAL RECEIVED :  Identifies that the Physical material in the warehouse and initiates immediate delivery ...

In the other Blog, we have seen how to Activate  " HOW TO ACTIVATE MATERIAL LENGTH" https://santoshvemuri.blogspot.com/2020/04/s4hana-sourcing-and-procurement.html now we will see, what kind of errors we could get and how to handle them As we know there are two transactions to be set for material length Extension 1. FLETS 2. OMSL , let us assume, we have activated Material Length  ( refer below screen), which means system  can now allow us to create material beyond 18 Characters Now we will try to create a material master in MM01 with more than 18 and see!! We get error as the length of the material is Longer than it is set, how does this error trigger and what we have to do?? This error triggered from OMSL setting, where the material length is defined as 18 So let us try to change this length and see how it works i have set material No length as 30 Characters and tried to Create a material beyond 18 characters After i set...

  Migrating Business Partner in S/4HANA ,  we use a tool called LTMC.  In this blog , i would like  to highlight the Content of Upload file in S/4HANA 1610 and how Number Range is determined . above is the file Content which is Upload template. In-fact this is template from 1610 version of S/4HANA. Now if you see, we can enter the Customer number ( either for GreenField Implementation/Brown Field Implementation) and Account Group.  We dont have any field in S/41610 to enter Number Range Or BP Grouping. Only option we have is, Once is file has uploaded to the Migration Project and once you start the Project, in the next step system prompts to select either Internal Number assignment Or External Number assignment. Based on the Option, we have chose system will get the number Range from the Configuration of BP Grouping Let us see how the Number Range is Configured in Business Partner Approach IMG--->CROSS APPLICATION COMPONENT--->BUSINES...

We already know there is a change in Material Length from Simplification List of Sourcing and Procurement. Let us understand, Business scenario where this Material Length is required to extend and what are the implications. In automotive industry, In Retail and Heavy Equipment and High-Tech Industry, it is common to have a material with more than 18 Characters Also some IS- solution, MII has 40 characters length of Materials. When we use ECC to interface such system, we were converting the length of ECC material to suit 40 Chars length of Target system in Interface. But when we convert our ECC system to S4HANA,  some  "IS_ Specific Modules and any other modules where the length is 40 till now are part of S4HANA. If we extend the length in S/4HANA system it is not required to do any adjustments or enhancements further. Data base Representation of material number  is MATNR; ECC it shows 18 Chars                  ...

in General, while Creating a sales Order there are certain fields which would be considered important for further processing of Sales order. Although these fields are not marked as Mandatory , but considered to be equally important to Mandatory fields Such fields are controlled by Incompletion  Procedure Functionality in Sales and Distribution. We will see how to Find Incomplete list of Sales Orders in S4HANA Steps:-- 1. Create a sales Order in VA01 ---( Create Sales order App in S4HANA) 2. For testing, I have not maintained Purchase Order field in the Sales Order- Overview Screen. In S4HANA this field is termed as CUSTOMER REFERENCE . While Saving the sales Order, system prompts to enter this field ( based on the Configuration of Incompletion Procedure) 3. In ECC, we can either go to Sales order-->Edit-->Incompletion documents and check what fields are missing 4. In case, if you want to look collectively for multiple documents, we use V.02  ...

This Blog will emphasis on Simplification of S4HANA  Logistics. Sales:- Advanced Order Processing and Billing for Contractors to the public sect :  This Functionality is completely Obsoleted and No Improvement available in this Area Billing Document Output Management :  BRF + is new advancement in this area Business Role Internal Sales Representative : New BP role is available for Internal Sales Representative. Credit Management : This Functionality is not available and replaced with SAP FSCM Credit management. Data Model Changes in SD Pricing : Changes to the existing Functionality such as new Table PRCD_ELEMENTS has to be used for KONV ERP SD Revenue Recognition :  this Functionality is No Longer Available and is replaced with Revenue Accounting and Reporting.  Foreign Trade : This Functionality is replaced with  GTS and International Trade Ope...

Account determination is main integration between SD -FI . We will see the integration of this functionality and how it is triggering G/L account and how is it different from SD condition technique ACCOUNT DETERMINATION is a functionality which also determines based on the CONDITION TECHNIQUE, But the way it is configured and controlled differentiates it from SD condition technique in this Article we will discuss on, How to create a new Access sequence in VKOA- ACCOUNT DETERMINATION TABLE I have create a new Table 496 with Condition type and account Key - Technically it will generate a database table as C496 the Configuration lies in Sales and distribution-->Basic functions-->Account Assignment-->Revenue Account determination Unlike SD, where we set Exclusive Indicator on Access Sequence, VKOA has no such functionality Then Question arises on how system will search and stop at particular Condition table? So, in VKOA system will always search from More sp...

SPLIT VALUATION is a functionality in SAP to differentiate the stock on VALUE basis for same material. In Sourcing and Procurement ( SAP MM) - we can difference the stock based on its Country of Origin such as  US or UK In Plant Maintenance and Customer, we can differentiate between NEW PART, DEFECTIVE PART and REFURBISHED PART In Sales ( SAP SD), we can differentiate based on STATUS of material ( for example domestic sales and international Sales) We will see Hands-on from Sales Perspective with Configuration and End-user transactions CONFIGURATION: 1. VALUATION  CATEGORY :                               Valuation Category specifies the Criteria to be used for differentiating the                                between different special stock of same material Under a Plant         ...

  In recent times SAP is continuously enhancing SAP Transportation Management. Latest in this improvement is S4HANA 1709 where Transportation Management was made embedded . Currently, i am focusing on TM-SD integration from ECC perspective As many of us know that Transportation is integral part of SAP R/3  as LE-Transportation for shipment and cost calculation. Later SAP came up with some advancement in terms of Advance planner and Optimizer. During 2009 SAP TM emerged as Stand Alone system supporting Service providers such as DHL , LINFOX . By adding shipper business process TM now supports AIR, OCEAN and Land transportation Now as part of Knowledge sharing, i would like to share the integration between SAP R/3  SD (Sales orders , Deliveries) and SAP TM SAP ERP integrates with SAP TM mostly in shippers business process where all the Transportation planning and execution phases is handled by SHIPPER ( manufacturer) Business process: Let’s assume, c...

In General, we deal with  Service Orders in Customer Service Module in Integration with SD for Returns and Repairs. Frequently we will come across Revenue and Non -Revenue Bearing Service Orders. Most of us will have a doubt what is difference ? In this Article, we will try to Focus from 1. Business Perspective and 2. Technical Perspective First of all let us see how it is controlled in SAP and later we will focus on the Business terminology In the Configuration of Order types OIOA and through NAVIGATION>>>SAP--->PMCS--->MAINTENANCE AND SERVICE PROCESSING-->SERVICE ORDERS-->SERVICE ORDER TYPES This Indicator  ❏ REVENUE POSTINGS will control whether Revenues can be posted to the service Order or not. What does it mean? What happens if this indicator is set? and when do we set this indicator? Normally, we set this indicator for Service Orders which are allowed to receive Revenues which means , technically Service Orders which are Crea...

We will understand why there is no Accounting document posted after a customer Return Order and subsequent Return Delivery is Created in SAP. What will happen to the stock, Will it never be accounted in FI books? We all know that this behaviour is controlled in Movement type Configuration, Yes but what is the business Logic for this behavior. We will take a look by Creating a return Delivery in SAP. Before a Return delivery to be posted, there should be a Fulfillment Order already created for the customer n the SAP. Assume there is a Fulfillment Order already exists in the system. Now, with reference to the Sales Orders we will create a Return sales Order. Return Delivery with Reference to Return Sales order Now perform PGR and check the Accounting document, you will get an information message as this document is not relevant for account The Main Reason for this is, 1. Movement type 651 has not account Grouping in OMJJ configuration 2. Why it is no...

Business Requirement: - When we have Auto PO/PR  Order Creation enabled in S4HANA through RPA ( Robotic Process Automation), Purchase  orders will get created through RPA Mechanism.  In this scenario, we get a file with vendors Products and Info records  which will be fetched by RPA programs to Create PRs orders.  As system is processing data automatically, there could be chance that few of the master Data of Vendor is not complete which can forbid creation of PO order. To Ensure all the data is complete, we need to check the file of Vendor with Incompleteness Data transaction We know in S4HANA,  we are not manually creating  Vendor, instead it is automatically created through Business Partner.   So, at first we need to identify the Vendor Numbers for Respective Business Partners though CVI Link Tables Tables to check: Assume a BP is Created with 1121, we need to find Corresponding Vendor for it. So Call Table  BUT000  and ...