Skip to main content

Posts

Showing posts with the label S4HANA-SD

SAP S4HANA/ SD : INDEPENDENT REQUIREMENTS & COLLECTIVE REQUIREMENTS

When we Create a Sales Order, we know Availability and Transfer of Requirements are carried out based on Availability check Configuration. in this Article, we will understand how a Collective requirement and Individual Requirements are handled for Sales Order and how is it Changed in S4HANA In the Configuration OVZ2, we can choose the option of Individual or Daily ( Collective Records) Let's check how system behaves for 01 and 02 for this scenarios, i will take two materials M-16 -- Which is set as Individual Requirement 1289 -- Which is set for Daily requirements I will two Sales order of 100 and 120 Quantity for 1289 respectively Sales Order- 100 Quantity Sales order -120 Quantity for Same material 1289 As this material is set as Collective requirements, at the end of the day, the total records were available in VBBS table here, VBBS is updated only when the Availability check is COLLECTIVE REQUIREMENT L et us run the same kind of t...

S4HANA : PM/CS - Enable E- signature at Operations

This blog is about a E- signature Functionality at service Order or Maintenance Order Operation Level. We use Maintenance or service Order Operations to perform certain tasks on the Equipment and once the task is executed, this operation can be confirmed. During Confirmation, we can do Digital signature, it is confirmation from Customer or particular Work Center Configurtion: SPRO-->PLANT MAINTENANCE & CUSTOMER SERVICE--.>MAINTENANCE & SERVICE ORDERS-->FUNCTIONS AND SETTINGS OF ORDER TYPES--.>DEFINE DIGITAL SIGNATURES FOR ORDER TYPES. You need to define signature strategy for Order type and Plant signature strategy:-                   This determines individual signature to be assigned for operation Digital signature Flag:-                This controls if a Digital signature is mandatory, optional or not required to be assigned at Operational Level signature ...

SD : Freight Cost Calculation at Delivery

A requirement to enable Freight Cost Calculation only during SHIPMENT ( Not to be confused with shipment Cost calculation). Normally we have Freight Cost Condition type at SALES ORDER and upon billing, this cost will be copied to from SALES ORDER to BILLING DOCUMENT Now we dont calculate FREIGHT COST at sales order, instead at DELIVERY LEVEL . so how this can be accomplished In General to enter Freight Cost only at Delivery Level, you need to defined pricing procedure with Freight Condition type KF00 - standard Condition type  in RVAA01 then assign this pricing procedure to Delivery type. Create SALES ORDER Create DELIVERY and add Freight Condition type manually or through Condition records Enable Copy Control from Delivery to Billing  in VTFL-- Pricing Source as E In Billing, the Freight will get copied from Delivery document Next Blog, i will try to show shipment cost calculation with  Transportation Planning points

SAP ECC Logistics and TM integration

ERP logistics Integration SAP ERP   integrated   with TM to facilitate Planning and execution   of Sales orders and Deliveries. Sales orders and Deliveries are represented as Transportation requirements in SAP TM. ERP integration enables us to -             Collectively plan transportation for all orders, and across order types -           Perform transportation Planning in SAP TM based on SAP ERP Orders, prior to delivery creation, thus enabling us to get an earlier forecast of future transportation and resource demands -           Performing tendering, subcontracting, and execution in Sap TM base don ERP orders -           Propose and create deliveries based on dates and quantities according to transportation planning results, taking into account transportation constraints...

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Nu...

SD -Condition Exclusion group and its implication in Pricing

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

SAP SD - Advance Return Management for customer Returns

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

S4HANA : SD/MM - Error Handling in Material Length Extension

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

S4HANA : Data Migration of Business partner in 1610 - Upload Template and determination of Number Range

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

S/4HANA ; Sourcing and Procurement ---Material Number Field Length Extension

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