This document discusses VOFM (Value Object Formulas) routines in SAP SD (Sales and Distribution). It provides information on:
1. Creating new VOFM formulas and assigning them in customizing
2. Standard SAP scale base formulas which alter the scale value used for condition lookups
3. Standard SAP condition base value formulas which influence the base value a condition rate is applied to
4. Examples of how these formulas can be used for pricing scenarios like volume discounts, surcharges, and tax calculations
The document discusses pricing routines in SAP SD VOFM, including requirement routines, alternate condition base values, condition base values, and alternative condition types. It asks questions about when alternate condition base values are used and difficult pricing procedures. The remainder of the document provides an introduction and table of contents for a guide on VOFM routines in sales and distribution, covering topics like creating new VOFM formulas, scale base, condition base value, condition value, group key structure, and rounding and calculation rules.
This article discusses how SAP can automatically determine which batch to use when creating a delivery based on the shelf life of the material. This is useful for industries like pharmaceuticals where batches closer to expiration should be delivered first. The document provides steps to configure SAP including importing standard characteristics, creating a class, setting up the material master, goods receipt, and multiple batches. It also demonstrates testing the configuration with a sales order, delivery, and billing document.
The document discusses sales deals and promotions in SAP SD. It provides an overview of sales promotions and deals, including their objectives to increase short-term sales and trial of new products. It also describes the configuration process in SAP for setting up promotions and sales deals, including defining promotions, sales deals, condition type groups, and assigning conditions. Finally, it provides an example of a sales promotion for a retailer and the process steps that would be demonstrated such as creating a promotion, sales deal, order, delivery and billing documents.
The document discusses pricing concepts in SAP such as condition tables, condition types, access sequences, condition records, and pricing procedures. It provides definitions of these key terms and describes how to set them up in transactions like creating a condition table, defining condition types, and maintaining pricing procedures. Steps are outlined to go through the document and SAP documentation to understand these pricing concepts.
This document describes pricing and conditions in SAP, including an introduction to condition techniques, condition types, condition tables, access sequences, and pricing procedures. It discusses how these elements work together for pricing in sales documents and outlines prerequisites for automatic pricing, pricing screens, and manual pricing. It also covers maintaining condition records, validity periods, pricing scales, condition supplements, and special pricing functions.
This document discusses sales promotions and deals in SAP. It provides an overview of promotions and deals, outlines the process for creating promotions, and describes the business advantages. Promotions are used to position merchandise competitively and can include discounts for customers or materials. The document also outlines the steps to configure promotions and deals in SAP, including defining promotions, setting up sales deals, assigning condition type groups, and creating the necessary documents.
The document discusses the transfer of requirements (TOR) process in SAP. TOR transfers the requirements from a sales order to materials requirements planning (MRP). This allows MRP to plan for meeting the demand created by the sales order. The key steps are:
1) TOR creates a demand in MRP from the sales order requirements.
2) MRP then checks availability by comparing warehouse stock, planned receipts and planned issues.
3) Configuration is required to define requirement classes and types to determine how requirements are transferred to MRP.
4) Schedule line categories and delivery blocks must also be configured to control the TOR process.
The document provides details on processing status for SAP-SD (Sales and Distribution) module. It outlines the key steps to set up the organizational structure, master data for customers, materials and pricing, and then generate sales documents including orders, deliveries and invoices. It also describes configuring parameters for pricing procedures, account assignments, and more when implementing the SAP-SD module.
The document discusses pricing routines in SAP SD VOFM, including requirement routines, alternate condition base values, condition base values, and alternative condition types. It asks questions about when alternate condition base values are used and difficult pricing procedures. The remainder of the document provides an introduction and table of contents for a guide on VOFM routines in sales and distribution, covering topics like creating new VOFM formulas, scale base, condition base value, condition value, group key structure, and rounding and calculation rules.
This article discusses how SAP can automatically determine which batch to use when creating a delivery based on the shelf life of the material. This is useful for industries like pharmaceuticals where batches closer to expiration should be delivered first. The document provides steps to configure SAP including importing standard characteristics, creating a class, setting up the material master, goods receipt, and multiple batches. It also demonstrates testing the configuration with a sales order, delivery, and billing document.
The document discusses sales deals and promotions in SAP SD. It provides an overview of sales promotions and deals, including their objectives to increase short-term sales and trial of new products. It also describes the configuration process in SAP for setting up promotions and sales deals, including defining promotions, sales deals, condition type groups, and assigning conditions. Finally, it provides an example of a sales promotion for a retailer and the process steps that would be demonstrated such as creating a promotion, sales deal, order, delivery and billing documents.
The document discusses pricing concepts in SAP such as condition tables, condition types, access sequences, condition records, and pricing procedures. It provides definitions of these key terms and describes how to set them up in transactions like creating a condition table, defining condition types, and maintaining pricing procedures. Steps are outlined to go through the document and SAP documentation to understand these pricing concepts.
This document describes pricing and conditions in SAP, including an introduction to condition techniques, condition types, condition tables, access sequences, and pricing procedures. It discusses how these elements work together for pricing in sales documents and outlines prerequisites for automatic pricing, pricing screens, and manual pricing. It also covers maintaining condition records, validity periods, pricing scales, condition supplements, and special pricing functions.
This document discusses sales promotions and deals in SAP. It provides an overview of promotions and deals, outlines the process for creating promotions, and describes the business advantages. Promotions are used to position merchandise competitively and can include discounts for customers or materials. The document also outlines the steps to configure promotions and deals in SAP, including defining promotions, setting up sales deals, assigning condition type groups, and creating the necessary documents.
The document discusses the transfer of requirements (TOR) process in SAP. TOR transfers the requirements from a sales order to materials requirements planning (MRP). This allows MRP to plan for meeting the demand created by the sales order. The key steps are:
1) TOR creates a demand in MRP from the sales order requirements.
2) MRP then checks availability by comparing warehouse stock, planned receipts and planned issues.
3) Configuration is required to define requirement classes and types to determine how requirements are transferred to MRP.
4) Schedule line categories and delivery blocks must also be configured to control the TOR process.
The document provides details on processing status for SAP-SD (Sales and Distribution) module. It outlines the key steps to set up the organizational structure, master data for customers, materials and pricing, and then generate sales documents including orders, deliveries and invoices. It also describes configuring parameters for pricing procedures, account assignments, and more when implementing the SAP-SD module.
This document discusses third party processing in SAP, which involves procuring materials from external vendors to fulfill customer orders. It describes the key steps and configurations needed, including:
1. Configuring material types and categories to define whether materials can be procured from third parties.
2. The processes involved when a customer places an order for a third party material - a purchase requisition is automatically generated which is converted to a purchase order sent to the vendor.
3. The two ways of handling third party processing - with or without shipping notification from the vendor.
4. The required configurations for third party processing without shipping notification, including creating materials, purchase organizations, vendors, and order types.
Copy Controls are programs in SAP SD that control how data is copied from one document to another when creating a new document based on an existing document. They consist of routines that determine which data fields are copied over. The standard system includes many routines to copy data between documents like sales documents, deliveries, and invoices. Additional routines can be created to meet other business needs. Copy Controls are configured using transaction codes that begin with "VT" and indicate the source and target documents. The controls determine what data is copied at the header, item, and schedule line levels and can be customized as needed for the business process.
This document discusses different types of free goods determination in SAP SD. There are two main types - inclusive and exclusive. Inclusive free goods quantity is included in the order quantity, while exclusive free goods quantity is excluded from the order quantity. Inclusive is further divided into with item generation and without item generation. Configuration involves creating condition tables, access sequences, condition types, and pricing procedures. The document provides examples and screenshots of configurations for inclusive with item generation and exclusive free goods.
Pricing Concept in SAP SD by Venkat MannamVenkat Mannam
The document discusses pricing concepts in SAP SD. It describes how pricing is determined by evaluating various factors like prices, surcharges, discounts, freight charges, and taxes. It explains that organizations emphasize automated price determination to prevent manual overrides. It then provides details on the different pricing elements, condition techniques used for pricing, including condition tables, access sequences, condition types, pricing procedures, and how the pricing procedure is determined.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
Yes, this is correct behavior in SAP. Inventory and non-inventory items cannot be billed together in the same billing document. At the time of billing document creation, SAP will split the delivery into two billing documents - one for inventory items and another for non-inventory items.
This is done to maintain the separation between inventory and non-inventory transactions in the accounting. Inventory items involve stock/goods movement and valuation, whereas non-inventory items are direct expenses. Keeping them separate in billing helps maintain the integrity of inventory and non-inventory accounting entries.
So in summary:
- Delivery can contain both inventory and non-inventory items
- But at billing, SAP will automatically split and create separate billing
Prepare for your interview with these top 20 SAP SD interview questions. For more IT Profiles, Sample Resumes, Practice exams, Interview Questions, Live Training and more…visit ITLearnMore – Most Trusted Website for all Learning Needs by Students, Graduates and Working Professionals.
Looking to add weight to your resume? Check out for ITLearnmore for varied online IT courses at affordable prices intended for career boost. There is so much in store for both fresh graduates and professionals here. Hurry up..! Get updated with the current IT job market requirements and related courses. For more information visit http://www.ITLearnMore.com.
Sap User Exit for Functional ConsultantAnkit Sharma
The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications.
User Exits is slot provided by SAP in SAP standard program.
User exits (Function module exits) are exits developed by SAP.
Code for the function module is written by ABAP Developer .
Developer does not write code directly in functional module , but in the INCLUDE that is implemented in the functional module.
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
The document discusses how to create SAP query reports using transaction codes SQ03, SQ02, and SQ01. It involves 3 steps: 1) Creating a user group, 2) Creating an infoset to define data fields, and 3) Creating queries to build reports. User groups control access to infosets and queries. Infosets define available fields from tables. Queries use infosets to select fields and build basic list or other output formats. The document provides examples of creating a user group, infoset using table joins, and a sample basic list query report.
Automatic batch determination based on shelf lifeMauricio Beltran
This document discusses how to configure automatic batch determination in SAP based on shelf life for materials like pharmaceuticals and foods. Key steps include importing standard characteristics, creating classes linked to expiration date, setting material master fields for shelf life, receiving goods into batches, and creating a search class and sort rule to select batches with the closest expiration dates first during delivery. This ensures batches are delivered before their expiration while meeting the required minimum remaining shelf life.
This document provides an overview of key concepts in SAP SD (Sales and Distribution) including:
- The SAP landscape including development, quality, and production environments
- SAP modules such as FI, CO, MM, SD, PP, and more
- SAP project types including greenfield, brownfield, and technical upgrades
- The sales cycle in SD including enquiries, quotations, sales orders, deliveries, and billing
- SAP organizational structures including company codes, plants, sales organizations, and more
- Master data relevant to SD such as customer, material, and pricing masters
This document outlines the configuration steps for automatically determining batches in delivery documents. Key steps include:
1. Configuring batch management strategies, access sequences, and search procedures.
2. Allocating the SD batch search procedure.
3. Activating automatic batch determination in sales orders and deliveries.
4. Creating a class for batch shelf life dates and maintaining it in material masters.
5. Creating batches for materials and maintaining shelf life expiration dates.
6. Maintaining condition records for batch search strategies to trigger automatic batch determination during delivery processing based on available stock batches.
This document provides a user manual for sales and distribution processes in SAP. It begins with an overview of master data, including how to create and maintain customer, material, pricing, and output condition records. Business processes like sales orders, quotations, deliveries and billing are then covered in detail. The document concludes with various reports available in sales and distribution like lists, analyses and price lists. Key aspects like account groups, tax codes and tips for record selection are also discussed in an appendix.
Guide to Configure Custom SD Output Types in S/4HANA Using BRF+Ashish Saxena
BRF+ is part of SAP provided decision service management tool (DSM) and it is not new in SAP. But doing output management via BRF+ is new in S/4 HANA system. Before knowing how output determination and management is done in S/4 HANA system using BRF+, we must know what is BRF+ and how it works.
BRF+ is comprehensive application programming interface (API) and user interface for defining and processing business rule. It allows us to model rules in an intuitive way and to reuse these rules in different applications.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
1. Create a customer master in plant DC01 for receiving plant INC1 and assign a sales area. Configure STO between the plants by defining shipping data and checking rules.
2. Make sure materials have the proper sales and availability views at the supplying plant. Configure shipping point determination for the loading group, shipping condition, and supplying plant combination.
3. Create a vendor master at the receiving plant for the supplying plant. Process an STO by creating a purchase requisition and purchase order at the receiving plant, sending the PO to the supplying plant, creating an outbound delivery and goods issue at the supplying plant, billing from the supplying delivery, goods receipt at the receiving plant, and invoice receipt.
1. The document discusses various sales order and distribution related concepts in SAP SD including drop shipments, sales areas, picking locations, customization vs configuration, shipping points, smart forms, sales document structure, plant determination, billing without delivery, sales deals, pricing date, account groups, item categories, project IMG, extending materials and customers to other sales areas, multiple deliveries, EDI usage, copy controls, schedule line categories, blocking sales documents, reconciliation vs normal accounts, access sequences, types of free goods, the 16 steps in a pricing procedure, differences between plants and storage locations, the sales order cycle, and the relationship between sales organizations and company codes.
2. It also provides explanations for concepts
The document describes the sales and distribution process for a company. It covers organizational structures like sales offices and credit control areas. It also details master data including materials, customers, and pricing. The main business processes covered are standard order fulfillment, B2B scenarios, returns, debit/credit memos, and made-to-order processes. Key steps include quotation creation, sales order entry, delivery, invoicing, purchase orders, and more.
This document provides an overview of ASAP's business blueprint for Crescent Pharmaceuticals' sales and distribution processes. It outlines the objective to map current business scenarios to SAP in order to configure the necessary processes. The methodology follows ASAP with documentation of current processes, gap analysis, and configuration. Key processes covered include sales orders, deliveries, billing, pricing, credit management, returns, and master data for customers and materials.
This document discusses third party processing in SAP, which involves procuring materials from external vendors to fulfill customer orders. It describes the key steps and configurations needed, including:
1. Configuring material types and categories to define whether materials can be procured from third parties.
2. The processes involved when a customer places an order for a third party material - a purchase requisition is automatically generated which is converted to a purchase order sent to the vendor.
3. The two ways of handling third party processing - with or without shipping notification from the vendor.
4. The required configurations for third party processing without shipping notification, including creating materials, purchase organizations, vendors, and order types.
Copy Controls are programs in SAP SD that control how data is copied from one document to another when creating a new document based on an existing document. They consist of routines that determine which data fields are copied over. The standard system includes many routines to copy data between documents like sales documents, deliveries, and invoices. Additional routines can be created to meet other business needs. Copy Controls are configured using transaction codes that begin with "VT" and indicate the source and target documents. The controls determine what data is copied at the header, item, and schedule line levels and can be customized as needed for the business process.
This document discusses different types of free goods determination in SAP SD. There are two main types - inclusive and exclusive. Inclusive free goods quantity is included in the order quantity, while exclusive free goods quantity is excluded from the order quantity. Inclusive is further divided into with item generation and without item generation. Configuration involves creating condition tables, access sequences, condition types, and pricing procedures. The document provides examples and screenshots of configurations for inclusive with item generation and exclusive free goods.
Pricing Concept in SAP SD by Venkat MannamVenkat Mannam
The document discusses pricing concepts in SAP SD. It describes how pricing is determined by evaluating various factors like prices, surcharges, discounts, freight charges, and taxes. It explains that organizations emphasize automated price determination to prevent manual overrides. It then provides details on the different pricing elements, condition techniques used for pricing, including condition tables, access sequences, condition types, pricing procedures, and how the pricing procedure is determined.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
Yes, this is correct behavior in SAP. Inventory and non-inventory items cannot be billed together in the same billing document. At the time of billing document creation, SAP will split the delivery into two billing documents - one for inventory items and another for non-inventory items.
This is done to maintain the separation between inventory and non-inventory transactions in the accounting. Inventory items involve stock/goods movement and valuation, whereas non-inventory items are direct expenses. Keeping them separate in billing helps maintain the integrity of inventory and non-inventory accounting entries.
So in summary:
- Delivery can contain both inventory and non-inventory items
- But at billing, SAP will automatically split and create separate billing
Prepare for your interview with these top 20 SAP SD interview questions. For more IT Profiles, Sample Resumes, Practice exams, Interview Questions, Live Training and more…visit ITLearnMore – Most Trusted Website for all Learning Needs by Students, Graduates and Working Professionals.
Looking to add weight to your resume? Check out for ITLearnmore for varied online IT courses at affordable prices intended for career boost. There is so much in store for both fresh graduates and professionals here. Hurry up..! Get updated with the current IT job market requirements and related courses. For more information visit http://www.ITLearnMore.com.
Sap User Exit for Functional ConsultantAnkit Sharma
The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications.
User Exits is slot provided by SAP in SAP standard program.
User exits (Function module exits) are exits developed by SAP.
Code for the function module is written by ABAP Developer .
Developer does not write code directly in functional module , but in the INCLUDE that is implemented in the functional module.
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
The document discusses how to create SAP query reports using transaction codes SQ03, SQ02, and SQ01. It involves 3 steps: 1) Creating a user group, 2) Creating an infoset to define data fields, and 3) Creating queries to build reports. User groups control access to infosets and queries. Infosets define available fields from tables. Queries use infosets to select fields and build basic list or other output formats. The document provides examples of creating a user group, infoset using table joins, and a sample basic list query report.
Automatic batch determination based on shelf lifeMauricio Beltran
This document discusses how to configure automatic batch determination in SAP based on shelf life for materials like pharmaceuticals and foods. Key steps include importing standard characteristics, creating classes linked to expiration date, setting material master fields for shelf life, receiving goods into batches, and creating a search class and sort rule to select batches with the closest expiration dates first during delivery. This ensures batches are delivered before their expiration while meeting the required minimum remaining shelf life.
This document provides an overview of key concepts in SAP SD (Sales and Distribution) including:
- The SAP landscape including development, quality, and production environments
- SAP modules such as FI, CO, MM, SD, PP, and more
- SAP project types including greenfield, brownfield, and technical upgrades
- The sales cycle in SD including enquiries, quotations, sales orders, deliveries, and billing
- SAP organizational structures including company codes, plants, sales organizations, and more
- Master data relevant to SD such as customer, material, and pricing masters
This document outlines the configuration steps for automatically determining batches in delivery documents. Key steps include:
1. Configuring batch management strategies, access sequences, and search procedures.
2. Allocating the SD batch search procedure.
3. Activating automatic batch determination in sales orders and deliveries.
4. Creating a class for batch shelf life dates and maintaining it in material masters.
5. Creating batches for materials and maintaining shelf life expiration dates.
6. Maintaining condition records for batch search strategies to trigger automatic batch determination during delivery processing based on available stock batches.
This document provides a user manual for sales and distribution processes in SAP. It begins with an overview of master data, including how to create and maintain customer, material, pricing, and output condition records. Business processes like sales orders, quotations, deliveries and billing are then covered in detail. The document concludes with various reports available in sales and distribution like lists, analyses and price lists. Key aspects like account groups, tax codes and tips for record selection are also discussed in an appendix.
Guide to Configure Custom SD Output Types in S/4HANA Using BRF+Ashish Saxena
BRF+ is part of SAP provided decision service management tool (DSM) and it is not new in SAP. But doing output management via BRF+ is new in S/4 HANA system. Before knowing how output determination and management is done in S/4 HANA system using BRF+, we must know what is BRF+ and how it works.
BRF+ is comprehensive application programming interface (API) and user interface for defining and processing business rule. It allows us to model rules in an intuitive way and to reuse these rules in different applications.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
1. Create a customer master in plant DC01 for receiving plant INC1 and assign a sales area. Configure STO between the plants by defining shipping data and checking rules.
2. Make sure materials have the proper sales and availability views at the supplying plant. Configure shipping point determination for the loading group, shipping condition, and supplying plant combination.
3. Create a vendor master at the receiving plant for the supplying plant. Process an STO by creating a purchase requisition and purchase order at the receiving plant, sending the PO to the supplying plant, creating an outbound delivery and goods issue at the supplying plant, billing from the supplying delivery, goods receipt at the receiving plant, and invoice receipt.
1. The document discusses various sales order and distribution related concepts in SAP SD including drop shipments, sales areas, picking locations, customization vs configuration, shipping points, smart forms, sales document structure, plant determination, billing without delivery, sales deals, pricing date, account groups, item categories, project IMG, extending materials and customers to other sales areas, multiple deliveries, EDI usage, copy controls, schedule line categories, blocking sales documents, reconciliation vs normal accounts, access sequences, types of free goods, the 16 steps in a pricing procedure, differences between plants and storage locations, the sales order cycle, and the relationship between sales organizations and company codes.
2. It also provides explanations for concepts
The document describes the sales and distribution process for a company. It covers organizational structures like sales offices and credit control areas. It also details master data including materials, customers, and pricing. The main business processes covered are standard order fulfillment, B2B scenarios, returns, debit/credit memos, and made-to-order processes. Key steps include quotation creation, sales order entry, delivery, invoicing, purchase orders, and more.
This document provides an overview of ASAP's business blueprint for Crescent Pharmaceuticals' sales and distribution processes. It outlines the objective to map current business scenarios to SAP in order to configure the necessary processes. The methodology follows ASAP with documentation of current processes, gap analysis, and configuration. Key processes covered include sales orders, deliveries, billing, pricing, credit management, returns, and master data for customers and materials.
SAP BUSINESS BLUE PRINT PRACTICE PROJECTVenet Dheer
This document provides an overview of mapping the current finance and controlling processes of Charminar Steel Castings to SAP. It discusses setting up the organizational structure in SAP including company codes, plants, and business areas. It also covers configuring master data, general ledger accounting, bank accounting, accounts receivable, accounts payable, payment terms, budgeting, taxes, and other financial processes in SAP. Gaps between the current and future SAP processes are identified.
This document discusses tables related to SAP SD (Sales and Distribution) module. It provides descriptions of key master data, transactional, and text tables used for sales orders, pricing, delivery, billing, contracts, output, accounting, and change management. The tables described include VBAK, VBAP, KNA1, KNB1, VBRK, VBRP, VEDA, BKPF, and CDHDR among many others that contain critical sales data in SAP.
1) Create a customer master in XD01 for the supplying plant, assign a customer number to the receiving plant in OLME. Set up an STO between the plants.
2) In the STO, assign document type UB, delivery type NL, and checking rule RP or ZS for the supplying plant. Assign document type UB for both plants.
3) Create the STO, then generate a purchase requisition and purchase order with document type UB and the supplying plant. Send the PO to the supplying plant. Create an outbound delivery to trigger a goods issue and material document. Receive the goods at the receiving plant. Post delivery costs separately.
This document provides instructions for configuring and activating split valuation in SAP to separately value in-house production stocks and externally procured stocks of materials. It outlines the steps to 1) activate split valuation in the system, 2) create valuation types for in-house and external stocks, 3) assign valuation categories to the types, and 4) create material master records and production/purchase orders to value the stocks separately. The purpose of split valuation is to allow different valuation prices for internally produced versus externally sourced materials.
This document outlines different types of plant to plant transfer orders including transfers without and with stock transport orders, with and without billing, and different document, delivery, billing, and pricing types as well as how stock is handled and costs are determined for each order type. It provides information on internal order processes for moving materials between plants.
Vendor return through quality notificationMohammed Azhad
This document explains an automated process for returning materials to a vendor through quality notifications when rejection occurs after inspection or on the shop floor after invoice verification. The process involves:
1) The quality department creating a quality notification for the rejected material in the T-Code QM01, entering the quantity and defect details.
2) The purchase department checking for new notifications in QM10, enriching it with purchasing details, and automatically creating a return purchase order and delivery.
3) The stores department checking for pending pick-and-goods issue notifications in QM10, editing the notification, and completing the PGI in VL02N.
4) Creating an excise invoice and credit memo to
This document provides instructions for pricing exercises involving expected customer price and value using EDI documents, posting goods issue, saving with incomplete documents, releasing, saving and going back, and flagging. It also references material pricing group K029.
This document discusses SAP's vendor rebate functionality including the process flow, required master and transactional data, and configuration settings. Vendor rebate arrangements can be set up at the purchasing organization or plant level based on vendor, material, and other attributes. Rebate conditions like scales based on value or quantity purchased over a period determine applicable discounts. The rebate settlement process involves comparing business volumes, settling rebates, and notifying vendors. Custom configurations may be needed if purchasing organizations are assigned to plants instead of company codes.
This document describes the master data requirements for a sales and distribution business blueprint project in SAP for an organization called Pragathi. It outlines 15 different master data elements that need to be configured including customer, material, plant, pricing conditions, and vendor masters. It also describes the client requirements for the master data implementation including authorization rules, legal requirements, and interface needs. The specifications for how these master elements will be modeled and implemented in SAP are provided.
The document provides an overview of advanced pricing in SAP SD. It discusses key concepts like pricing procedures, condition types, alternative calculation types, and account determination. Pricing procedures bring together condition types to determine prices based on complex business rules and scenarios. Condition types can be configured with special fields to handle currency conversion, group discounts, accruals, and other advanced pricing needs. Alternative calculation types and condition base values provide flexibility to calculate prices in non-standard ways. Account determination ensures prices map to the correct general ledger accounts. Advanced pricing allows businesses to configure highly customized pricing logic to address complex real-world business requirements.
Business requirements gathering and analysisMena M. Eissa
Business analysis and requirements management are a key to project success.
This workshop helps candidates perform better based on sharing real life experience with them.
This document describes product requirements planning for VOFM routines in Sales & Distribution. It provides an overview of VOFM and how to create new VOFM routines. It then describes several standard pricing requirements delivered by SAP, including requirements to check for different payer/sold-to parties, items relevant for pricing, foreign currency documents, and cost. The requirements are used to improve performance by eliminating unnecessary database accesses during pricing.
Here are the 16 pricing elements in pricing procedure and description for eachvishalsap84
The document describes the 16 pricing elements in SAP that control pricing procedures. Each element has a specific purpose, such as determining the sequence of pricing conditions, setting manual vs automatic values, and assigning general ledger accounts. The "Condition formula for alternative calculation type" refers to routines that provide an alternative way to calculate a condition value. The "Alternative formula for condition base value" refers to routines that provide an alternative basis for calculating a condition value rather than using the standard basis.
This document provides an overview of Oracle Advance Pricing. It discusses key concepts like price lists, qualifiers, modifiers, and pricing agreements. Price lists define item prices and pricing attributes. Qualifiers specify discount conditions. Modifiers apply discounts, surcharges, promotions, and freight charges. Pricing agreements negotiate prices with customers. The document demonstrates how to set up a price list, discount modifier, and apply the modifier in a sales order to provide a 10% discount.
This document discusses master data and structures in Profitability Analysis (CO-PA). Master data provides the fundamental data and defines characteristics and value fields that determine profitability segments. Structures are created by defining characteristics, value fields, and operating concerns. Master data consists of individual characteristic values that specify valuation levels through their combination into profitability segments. The document describes how profitability segments, characteristics, characteristic values, and structures are related and integrated in CO-PA. It also discusses valuation methods like using material cost estimates, conditions, costing sheets, and customer exits that are used to determine values in profitability segments.
The future of software pricing excellence transaction pricing managementVishal Sharma
The document discusses transaction pricing management in the software industry. It outlines PwC's pricing management framework, which includes pricing strategy, price formulation, transaction management, and performance measurement. The document focuses on transaction management, noting that leaders in this area have integrated, cross-functional processes for capturing pricing data from deals and using it to inform future deals. It also provides guidance on key elements of building a transaction pricing management framework, including designing a price waterfall, defining analytics, and establishing pricing policies and governance.
Cost Analysis ModelsUnit 3 Written AssignmentBUS .docxbobbywlane695641
The document provides an analysis of costs for a catering and events business. It finds the business has a break-even point of 3,158 events based on revenue of $4,500 per event and variable costs of $2,600 per event. It also calculates the business would need 5,789 events to increase profits from $3.5 million to $5 million. The analysis is limited as it makes estimates and assumptions about demand that may not reflect reality. Key data like taxes and certain fixed costs are also missing.
The Manufacturing X Release Notes document summarizes new features and enhancements in the 1811 release, including:
1) Customizing capabilities like lookup tables, MX scripting, and Groovy scripting for custom business logic and integrations.
2) Order splitting to automatically split orders from quotations into multiple sales orders.
3) Enhancements to quote lifecycles when orders are changed after syncing to ERP.
4) Product substitution to automatically or manually replace older products with newer versions.
5) Pre-submit checks on quotations to validate products before submission.
6) Product grouping and recommendations to help sales representatives find products.
1. The document discusses various SAP SD questions and answers related to concepts like drop shipment, sales area, picking location rule MALA, customization vs configuration, delivery without shipping point, smart forms, sales document structure, and more.
2. It also includes explanations of sales deals, pricing date in condition type, account group control of customers, item category and usage, need for project IMG, assigning sales organization to plant, extending material and customers to other sales areas, and processing outbound deliveries without shipping point.
3. The questions cover additional topics such as field selection customization in account groups, condition indexes, releasing change requests, product attributes, multiple packing for delivery, EDI usage, extending
Definitive Guide to Subscription and Usage-Based Pricing Strategies: Accelera...BluLogix
The SaaS industry has experienced a significant shift in recent years, with recurring revenue models taking center stage. Subscription and usage-based pricing strategies have emerged as powerful tools for accelerating growth and driving success in the SaaS business landscape. With almost half of companies having some form of usage-based pricing, and another 15% trialing it*, for many companies, it’s time to not only get on the bandwagon, but get to scale quickly.
This document provides instructions for configuring stock transport orders in SAP, which allow for the physical transfer of goods between two plants or company codes. It outlines the key configuration steps, which include defining a stock transport order document type, assigning shipping data and checking rules to plants, and associating delivery types and one-step procedures with document types and plant combinations. The configurations allow goods to be transferred between plants within a company code or across company codes with delivery and optional billing.
This document discusses changes to cost of goods sold (COGS) accounting and cost of production analysis (COPA) in SAP Simple Finance. It explains that SAP now recommends using account-based COPA rather than cost-based COPA because account-based COPA in Simple Finance can provide more detailed cost breakdowns and better reconciliation to the general ledger. The document also provides steps for customizing account-based COPA, including defining additional accounts to split the COGS posting and accounts to split production variance categories for financial reporting purposes.
Rethink Your Software Licensing Monetization StrategyFlexera
This whitepaper discusses how software companies can introduce subscription licensing models to generate recurring revenue streams. Some key points:
- Perpetual licenses are still dominant but subscription models are growing as cloud/SaaS grows. Subscription licenses provide recurring revenue over time rather than an upfront lump sum.
- Subscription models offer benefits like predictable recurring revenue, flexibility to meet different customer needs, and lower upfront costs that can open new markets. However, they require changes to business processes like pricing, product numbering, renewals, and revenue recognition.
- When implementing a subscription model, companies should add it without replacing perpetual licenses. They also need to align compensation, pricing structures, and operations to support the subscription business
This design document provides details for configuring SAP's CO-PA (Profitability Analysis) module to support analyzing profitability by market segment. Key configuration decisions include using costing-based CO-PA for flexibility, defining one operating concern for the global setup, and sourcing data for the contribution margin scheme from other SAP modules like sales and production. The design focuses on flexibly defining value fields, profitability segments, and performance measures to automatically collect and report revenues, costs, and sales deductions from business transactions processed in SD and other modules.
This document provides a step-by-step guide to configuring validations in SAP, which allow for defining custom checks on fields when business transactions are processed. It describes the basic steps to create a validation including defining prerequisites, checks, and messages. An example is provided to demonstrate restricting document types and checking posting dates equals system date using an exit. Related transaction codes for validation maintenance and assignment are also listed.
This document provides a step-by-step guide to configuring validations in SAP, which allow for defining custom checks on fields when business transactions are processed. It describes the basic steps to create a validation including defining prerequisites, checks, and messages. An example is provided to demonstrate restricting document types and checking posting dates equals system date using an exit. Related transaction codes for validation maintenance and assignment are also listed.
The key components of the SAP SD module include master data, basic functions, sales processes, shipping and transportation, billing, and sales support. A sales organization is the topmost organizational unit in SD and represents selling and distribution transactions. A distribution channel depicts the paths products take to reach customers after being sold. A distribution chain is a combination of a sales organization and distribution channels. A sales order is a contract between a sales organization and customer for supplying goods and services over a specified time frame and quantity. Special sales document types include rush orders, credit memos, return orders, and free of charge deliveries. The consignment stock process allows stock to be stored at a customer's site and billed only as consumed.
The document discusses the SAP system's capabilities for automatically dunning overdue business partner accounts. It allows setting up dunning procedures that define dunning levels, notices, and other attributes. The system can dun customers, vendors and one-time accounts. It handles credit memos, cross-company dunning, and special cases like alternative recipients. Configuration is needed in the SAP IMG, master records and document posting to use automatic dunning.
10 features to check out in your subscription management solutionkanimozhin
This document discusses key features of subscription management solutions for SaaS companies. It outlines 10 top features including package management, pricing plans, trials, usage-based billing, taxes/discounts, invoices, pre-paid/post-paid billing, payment processing, customer portals, and notifications. It also provides examples of how subscription models can vary in terms of modules offered, payment schedules, and usage limits.
1) This document describes a process for vendor-managed consignment inventory where the vendor takes responsibility for maintaining stock levels and replenishing inventory based on daily demand information from the customer.
2) Key aspects of the process include setting up EDI messages to send the customer's blanket PO and daily stock/demand data to the vendor, and for the vendor to send order confirmations and delivery advices.
3) The process aims to reduce inventory levels and handling costs for the customer by leveraging the vendor to monitor and replenish stock without additional POs from the customer.
The document is a third party sales order that triggers the automatic creation of a purchase requisition for the item. It specifies the item category as third party, does not allow delivery or availability checks, and notes the purchase requisition number should be recorded. The order type is NB, meaning it will not be billed but the business can raise an invoice when wanted based on the purchase order.
SAP Data Archiving allows organizations to remove old data from their SAP database and store it externally to reduce costs and improve performance. The archiving process involves creating archive files, running delete programs to remove data from the database, and storing the archive files externally. Archiving objects define which data to archive and how. The archive information system then allows users to search and retrieve archived data.
This document describes two methods for processing installment payments in SAP:
1. Use installment payment terms. This allows entering one invoice line that is automatically split into installments based on predefined payment terms. It involves creating a "main term" and associated installment terms, then defining the percentages and due dates for each installment term.
2. Activate document split. This provides flexible installment amounts by splitting an invoice amount on the amounts split tab. It does not rely on predefined installment payment terms. This method is used for invoices processed with the new style transactions.
Both methods allow invoices or credit memos to be paid in installments by customers or vendors. The installment payment terms method provides a standardized approach while document
This document provides a step-by-step guide to creating an eCATT (electronic Computer Aided Test Tool) script in SAP ECC version 5 and above. It describes how to record a test script using the SAP GUI, replace fixed values with import variables, create a test configuration to execute the script, and populate an external Excel file with test data to run the script. The guide explains each step in the process to create a basic eCATT script that can be used by beginners for testing in SAP systems.
This document is a user manual for implementing SAP R/3 for excise duty management at Bharat Aluminum Co. Ltd. It covers essential excise master data configuration including excise registration, group, rates, and materials. It describes roles for goods receiving and excise invoice posting. It provides guidance on capturing capital goods cenvat credit, special cases like rejections, and reports for monitoring cenvat balances and transfers. The goal is to guide BALCO's implementation and use of SAP's country-specific India features for accurate excise compliance.
This document provides an overview of the CIN Knowledge Bank, which is a handbook for quick CIN implementation. It includes sections on frequently asked questions, user exits, business events, customization, pricing, configurable messages, transaction data, security, and important notes. The document was created by SAP Labs India as a draft on November 20, 2001.
1. Create a billing variant to define conditions for invoice generation such as billing type, sales organization, or distribution channel.
2. Use the job wizard to create a background job, select the ABAP program for invoice generation, and define recipients for the spool output.
3. Specify start conditions such as periodic scheduling or restrictions on days of the week for the job to run automatically. Check the job status and output report to see invoices created and any errors.
This document provides an overview of available to promise (ATP) in SAP-SD. It discusses what ATP is, how to view the ATP situation using transaction CO09, and how the system arrives at a confirmed delivery date using backward and forward scheduling based on availability. It also outlines the key dates, times, and configurations needed for ATP checks, including requirements type, class, strategy group, checking group, rule, and scope. ATP projections are based on defined rules and are not the actual stock situation.
This document outlines the business process for tolling at IFFCO, which involves the production and distribution of DAP fertilizer. The distribution department is responsible for dispatching DAP according to movement plans, usually via rail transport paid for by IFFCO. The document specifies client requirements, modeling of the process in SAP, and gaps between requirements and standard SAP functionality that require customization. Key requirements include production, printing, authorization, legal, development, reporting, and interface needs, which are mapped to the SAP model with any non-standard needs listed for modification.
This document outlines the business blueprint for storage, handling, and transportation processes for a company implementing SAP. It describes the client requirements, how requirements will be modeled in SAP, potential gaps between requirements and standard SAP capabilities, and a process for approval. The document includes sections for the business process scope, client requirements, specification for SAP implementation, references, gap analysis, and process approval.
1. This document outlines the rebate processing business process for a company implementing SAP. It describes the types of rebates processed, including quantity rebates, prorata cash rebates, and secondary transport rebates.
2. The business process flow is described, involving calculating rebates in FoxPro and uploading them into SAP via BDC to generate credit notes.
3. Requirements like printing, authorization, legal and interface requirements are listed for implementation in SAP. Gap analysis will identify any requirements that cannot be met by standard SAP.
This document outlines the port operations process for importing raw materials at Kakinada Port in India. It describes the current process, including creating purchase orders with overseas suppliers and appointing clearing and forwarding agents. Requirements for the process like authorization, legal compliance, and reporting are also listed. The document specifies how the requirements could be modeled in SAP, including organizational elements, mapping requirements to SAP, and identifying any gaps between requirements and standard SAP capabilities. Approval of the business process is noted at the end.
This document outlines the credit management business process for a company. It describes the current process where credit limits are set by marketing and entered into the system. It exceeds credit limits are identified. It also describes requirements for implementing the process in SAP and mapping the requirements. Gaps between requirements and standard SAP functionality are identified.
This document outlines the specifications for implementing a collection processing business process in SAP. It describes the client requirements, including process, printing, authorization, legal, and interface requirements. It also provides details on how the client requirements will be modeled in SAP, including the organizational elements, to-be process flow, and a process flow chart. Any gaps between the client requirements and standard SAP capabilities are identified. The document was created on June 29, 2006 for a project called Pragathi and includes approval from process owners.
This document outlines requirements and specifications for implementing a billing process in SAP for a client. It describes the client's current billing process, requirements for printing, authorization, legal compliance, and interfaces. It also provides an overview of how the client's requirements could be mapped to SAP concepts and identifies any gaps between requirements and standard SAP capabilities.
Sd pragathi template abap reports and flow charts of sdMohammed Azhad
This document provides a summary of a business process for sales and distribution (S&D) for the Pragathi project. It lists the process owner, consultants, core team members, and details the scope as ABAP reports and flow charts for S&D. An attachment includes an Excel file listing ABAP programs and flow charts detailing the various S&D activities.
Sd pragathi template delivery and goods issueMohammed Azhad
This document outlines the delivery and goods issue process for a company. It describes the process flow for delivery against a sales order at a plant, including truck authorization, loading, weighing, invoicing and delivery. It also lists the client's requirements such as required prints, authorizations and reports. Finally, it discusses how the client's requirements will be modeled and mapped in SAP, and identifies any gaps between requirements and standard SAP capabilities.
Jill Pizzola's Tenure as Senior Talent Acquisition Partner at THOMSON REUTERS...dsnow9802
Jill Pizzola's tenure as Senior Talent Acquisition Partner at THOMSON REUTERS in Marlton, New Jersey, from 2018 to 2023, was marked by innovation and excellence.
How to Prepare for Fortinet FCP_FAC_AD-6.5 Certification?NWEXAM
Begin Your Preparation Here: https://bit.ly/3VfYStG — Access comprehensive details on the FCP_FAC_AD-6.5 exam guide and excel in the Fortinet Certified Professional - Network Security certification. Gather all essential information including tutorials, practice tests, books, study materials, exam questions, and the syllabus. Solidify your knowledge of Fortinet FCP_FAC_AD-6.5 certification. Discover everything about the FCP_FAC_AD-6.5 exam, including the number of questions, passing percentage, and the time allotted to complete the test.
Leadership Ambassador club Adventist modulekakomaeric00
Aims to equip people who aspire to become leaders with good qualities,and with Christian values and morals as per Biblical teachings.The you who aspire to be leaders should first read and understand what the ambassador module for leadership says about leadership and marry that to what the bible says.Christians sh
Learnings from Successful Jobs SearchersBruce Bennett
Are you interested to know what actions help in a job search? This webinar is the summary of several individuals who discussed their job search journey for others to follow. You will learn there are common actions that helped them succeed in their quest for gainful employment.
Joyce M Sullivan, Founder & CEO of SocMediaFin, Inc. shares her "Five Questions - The Story of You", "Reflections - What Matters to You?" and "The Three Circle Exercise" to guide those evaluating what their next move may be in their careers.
In the intricate tapestry of life, connections serve as the vibrant threads that weave together opportunities, experiences, and growth. Whether in personal or professional spheres, the ability to forge meaningful connections opens doors to a multitude of possibilities, propelling individuals toward success and fulfillment.
Eirini is an HR professional with strong passion for technology and semiconductors industry in particular. She started her career as a software recruiter in 2012, and developed an interest for business development, talent enablement and innovation which later got her setting up the concept of Software Community Management in ASML, and to Developer Relations today. She holds a bachelor degree in Lifelong Learning and an MBA specialised in Strategic Human Resources Management. She is a world citizen, having grown up in Greece, she studied and kickstarted her career in The Netherlands and can currently be found in Santa Clara, CA.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
IT Career Hacks Navigate the Tech Jungle with a RoadmapBase Camp
Feeling overwhelmed by IT options? This presentation unlocks your personalized roadmap! Learn key skills, explore career paths & build your IT dream job strategy. Visit now & navigate the tech world with confidence! Visit https://www.basecamp.com.sg for more details.
Gabrielle M. A. Sinaga Portfolio, Film Student (2024)
VOFM Routine
1. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 115
Pricing
SAP SD VOFM Routines
1. What is requirement routine in pricing?
2. What is alternate condition base value?
3. What is condition base value?
4. In which case we use alternate condition base value.
5. What is alternative condition type in which case we use alternate condition type? What is the purpose of
using this?
6. Can any body tell me any difficult pricing procedure?
VOFM ROUTINES IN SALES & DISTRIBUTION
Table of Contents
1. Introduction
2. Creating a New VOFM Formula
3. Scale Base
4. Condition Base Value
5. Condition Value
6. Structure of Group Key
7. Rounding Rule
8. Calculation Rule – Free Goods
1. Introduction
Transaction VOFM is a tool that was developed in R/3 to facilitate the definition of both SAP delivered as
well as customer defined routines/rules used in the system during various business processes. VOFM routines
are ABAP code written in Forms. VOFM provides the user with the benefit of choosing from one of the
standard delivered R/3 routines or writing their own. VOFM is intended for the implementation team when
configuring the system. It is not intended for the end user.
VOFM is divided up into four main areas. These include copying requirements, data transfer, requirements,
and formulas. This paper will focus on formulas that were delivered by SAP to support the Sales &
Distribution (SD) and Logistics Execution (LES) applications. At a high level, formulas are routines that
define how a value should be calculated or determined in the R/3 system.
For example, a pricing condition value formula allows the user to define how a specific pricing value should
be calculated. Similarly, a rounding rule formula defines how rounding should take place when pricing mass
maintenance is performed. Formulas are a powerful tool allowing the user to adjust the way in which the
system determines certain values. They can also be used to set certain variables in the coding, or even to call
other programs.
Section 2 defines how to create a new VOFM routine, in the event that the standard routines do not match the
user needs. In the remaining sections, the SAP standard delivered VOFM routines related to Sales &
Distribution and Logistics Execution are documented. Starting with Release 4.6A, this documentation is part
of the standard product. This paper assumes that the reader has a general understanding of the SD and LES
modules in R/3 as well as a working understanding of the condition technique.
2. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 215
2. Creating a New VOFM Formula
In each area of VOFM, with the exception of Structure of Group Key Formulas, SAP delivers routines using
the name space from 1 to 599. SAP customers can create their own VOFM routines using the name space
from 600 to 999. With Structure of Group Key Formulas, the SAP name space is 1 to 49, and the customer
name space is 50 to 99. To create a new routine, follow these steps:
1. First check to see whether you can use one of the formulas delivered in the standard system.
2. Either overwrite an existing formula or enter a new number on a new line from the customer name space
600 to 999. Also enter a short description of your formula.
3. Program your formula in the ABAP editor.
4. Activate the program.
5. Enter the application if you want to use the formula in a specific application area.
6. Enter your new formula in the appropriate area in customizing. For example, a new pricing condition value
formula would be assigned to a condition type or value line in a pricing procedure. As another example, a free
goods calculation rule would be assigned to a free goods condition record. New VOFM routines created at a
customer site are not overwritten by a software upgrade.
3. Scale Base
A scale base formula can be used to alter the value that the system uses to read the scales in a condition record
during pricing. In standard pricing, the system will read the scale in a pricing condition record using the
quantity, value, weight, etc. of the document depending on the type of scale that has been defined.
Example:
Price Product A
From 0 cases
$50 per case
From 100 cases
$45 per case
From 500 cases
$40 per case
If the customer orders 100 cases of Product A, the system will read the pricing scale using 100 cases and
determines the appropriate price, $45 per case. Using a scale base formula, it is possible to alter the value, in
our example 100, prior to the scale being read. Scale base formulas are assigned to pricing condition types in
R/3 configuration.
When looking at the code for the standard delivered scale base formulas or when writing your own,
XKWERT is the field name that the scale base value should be assigned to.
Following is a description of the scale base formulas delivered in the standard system.
SCALE BASE FORMULA 1: FREE
This is an example of a scale basis formula. It is not currently used.
SCALE BASE FORMULA 23: PARTIAL QUANTITY
The formula '23' sets the whole number part of the value to zero. For example, the value 203.559 would be
changed to 0.559. Formula '23' was delivered to support the R/3 delivered condition type KP03 to support
mixed pallet surcharges.
Example:
A company sells their products in cases. Each of their materials has a conversion factor to pallets. When an
order is placed by a customer, the user would like the system to add up the quantities across items and
compute the number of full pallets. If the customer does not order in full pallets, the user would like to charge
3. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 315
a fixed surcharge of 20 USD. The user sets up condition type KP03 in the pricing procedure. In customizing
for the condition type KP03, the scale base formula '23' is assigned as well as the group condition flag so that
the quantities across order items can be considered. Within the condition records for condition type KP03, the
user maintains a rate of "from 0.001 PAL" a fixed charge of 20 USD. If an order is placed, for example, that is
equal to 10.35 pallets; the formula '23' will alter the value to 0.35 and then read the condition record scale. A
surcharge of 20 USD would then be applied to the overall sales order.
SCALE BASE FORMULA 43: TAX LICENSE FRANCE
Formula '43' was delivered to support tax exemption licenses in France (R/3 delivered condition type LCFR)
where the tax exemption is granted up to a certain invoiced amount. For additional information on tax
exemption licenses, please refer to Note 72040.
SCALE BASE FORMULA 202: PRICE-BOOK SCALE
This requirement is used together with the feature 'Data determination in the access' (delivered with Release
4.5). In the R/3 delivered system, condition type PBUD can be used to determine a special scale basis in the
pricing procedure. If scale basis formula '202' has been assigned to subsequent condition types that appear in
the pricing procedure, the system uses the special scale basis versus the normal scale basis from the sales
document line item. Further information about 'Data determination in the access' can be found in the R/3 Sales
& Distribution documentation under the section titled 'Special pricing functions'.
Example:
A company wishes to define a pricing agreement that specifies that all customers in a certain customer group
receive the price associated with ordering 100 cases of product regardless of how many cases are ordered.
This involves fixing the scale basis for the customer group for a certain period of time. This can be
accomplished by using the ‘Data determination in the access”. A condition type, such as PBUD can be used to
define the fixed scale value of 100 cases. Subsequent condition types that should use this fixed value are then
assigned scale base formula ‘202’.
4. Condition Base Value
Condition base value formulas can be used to influence the condition basis to which the pricing condition rate
will be applied. In standard pricing, the system will apply the condition rate to the quantity in the sales
document. For example, the price determined by the system is $45 per case for Product A. 100 cases of
Product A have been ordered. The system would then multiply $45 times the number of cases of Product A
ordered. Using a condition base value formula, it is possible to alter the condition base, in our example 100,
prior to the calculation taking place. A condition base value formula is commonly used to determine the base
for distributing header discounts / surcharges to the sales document line items. A condition base value formula
is assigned to a condition type in the pricing procedure.
When looking at the code for the standard delivered condition base value formulas or when writing your own,
XKWERT is the field name that the condition base value should be assigned to.
Following is a description of the condition base value formulas delivered in the standard system.
CONDITION BASE VALUE FORMULA 1: VOLUME
Formula '1' uses the volume of the sales document line item as the condition base value.
Example:
A company regularly applies fixed amount header discounts to a sales order. For example, the user may apply
a fixed discount of 500 USD to the header of the sales order. Fixed header conditions are always distributed
across the line items in the document. In this case, the company would like to distribute the fixed amount
4. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 415
based on the volume of the line items. To accomplish this, the user would assign condition base value formula
'1' to the header discount condition type in the pricing procedure.
CONDITION BASE VALUE FORMULA 2: NET VALUE
Formula '2' uses the net value of the sales document line item as the condition base value.
Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 3: NET PRICE
Formula '3' was delivered to support net price processing. For additional information on the use of this
formula along with examples, please refer to Note 80183.
CONDITION BASE VALUE FORMULA 4: NET VALUE PLUS TAX
Formula '4' uses the net value plus tax of the sales document line item as the condition base value.
Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 5: KZWI1
Formula '5' uses the value determined for subtotal '1' in the pricing procedure as the condition base value.
Example:
A company regularly applies fixed amount header discounts to a sales order. For example, the user may apply
a fixed discount of 500 USD to the header of the sales order. Fixed header conditions are always distributed
across the line items in the document. In this case, the company would like to distribute the fixed amount
based on a subtotal derived based on certain values in the pricing procedure. The user has assigned subtotal '1'
to the relevant pricing procedure value(s). In addition, the user would assign condition base value formula '5'
to the header discount condition type in the pricing procedure.
CONDITION BASE VALUE FORMULA 6: KZWI2
Formula '5' uses the value determined for subtotal '2' in the pricing procedure as the condition base value.
Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 7: KZWI3
Formula '5' uses the value determined for subtotal '3' in the pricing procedure as the condition base value.
Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 11: CASH DISCOUNT BASE
Formula '11' can be used with the cash discount condition type. This formula reads the indicator for the
company code to determine if the cash discount is based on the net value of the item. If it is not, then the
system bases it off of the net value plus the tax.
CONDITION BASE VALUE FORMULA 12: GROSS WEIGHT
Formula '12' uses the gross weight of the sales document line item as the condition base value.
Example:
Reference example for formula 1
5. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 515
CONDITION BASE VALUE FORMULA 13: NET WEIGHT
Formula '13' uses the net weight of the sales document line item as the condition base value.
Example:
Reference example for formula 1
CONDITION BASE VALUE FORMULA 14: SET EXCLUSION INDICATOR
Formula '14' is an example of how a programmer can dynamically set the condition exclusion indicator based
on certain values. This condition exclusion indicator can then be checked in subsequent condition base value
formulas (reference formula '15') to exclude certain condition types.
CONDITION BASE VALUE FORMULA 15: CHECK EXCLUSION INDICATOR
Formula '15' is an example of how a programmer can check the value of the condition exclusion indicator and
then influence certain values. In this example, if the exclusion field is set to '$', the condition base value is set
to zero and the condition is marked inactive. This example is provided in combination with formula '14' which
shows how to dynamically set the condition exclusion indicator.
CONDITION BASE VALUE FORMULA 16: NET VALUE MINUS CASH DISCOUNT
Formula '16' uses the net value minus the cash discount value as the base value. This can, for example, be
applied to a tax condition type that should use this value as a basis.
CONDITION BASE VALUE FORMULA 17: NET PRICE
Formula '17' was delivered to support net price processing. For additional information on the use of this
formula along with examples, please refer to Note 80183.
CONDITION BASE VALUE FORMULA 18: NO QUANTITY CONVERSION
Formula '18' is used to avoid rounding errors that can occur for quantity dependent condition types where the
sales unit and the pricing unit are one unit of measure and the base unit of measure is another. Using formula
'18', no conversion is done to base unit of measure when the sales unit of measure and pricing unit of measure
are identical.
NOTE: As of Release 4.0, this formula is no longer necessary. The user can achieve the same result by setting
the "quantity conversion" indicator in condition type configuration.
Example:
A company uses KG as their base unit of measure, but chooses to quote prices and sell products in pieces
(PC). A quantity conversion has been maintained to indicate that 3 PC correspond to 1 KG. A pricing record
has been created to price 1 PC of product at 1 USD. If a customer orders, for example, 1 PC of product, it is
possible that the system returns back an item value of 0.999 USD. To avoid this, the user assigns condition
base value formula '18' to the price condition type as well as other quantity dependent condition types in the
pricing procedure.
CONDITION BASE VALUE FORMULA 19: KZWI4
Formula '19' uses the value determined for subtotal '4' in the pricing procedure as the condition base value.
Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 20: KZWI5
Formula '20' uses the value determined for subtotal '5' in the pricing procedure as the condition base value.
6. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 615
Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 21: KZWI6
Formula '21' uses the value determined for subtotal '6' in the pricing procedure as the condition base value.
Example:
Reference example for formula 5
CONDITION BASE VALUE FORMULA 22: WHOLE NUMBER
Formula '22' is used to convert the basis to a whole number. For example, a basis of 300.153 would be
converted to 300. Formula '22' is delivered in R/3 along with the condition type KP00 which can be used to
compute pallet discounts.
Example:
A company sells their products in cases. Each of their materials has a conversion factor to pallets. When an
order is placed by a customer, the user would like the system to calculate the number of full pallets for each
line and to offer a 5 USD discount per full pallet ordered. The user sets up condition type KP00 in the pricing
procedure and assigns condition base value formula '22'. Within the condition records for condition type
KP00, the user maintains the 5 USD per pallet discount rate. If an order line item is placed that contains 5.5
pallets, the system will adjust the base value to 5 and compute a discount of 25 USD for the sales line item.
CONDITION BASE VALUE FORMULA 24: 1 IF PARTIAL QUANTITY
Formula '24' is used to convert the basis to a quantity of 1 if a partial quantity is involved, otherwise the basis
is set to zero. For example, a basis of 300.153 would be converted to 1. As a second example, a basis of 300
would be converted to zero. Formula '24' is delivered in R/3 along with the condition type KP01 which can be
used to calculate an incomplete pallet surcharge.
Example:
A company sells their products in cases. Each of their materials has a conversion factor to pallets. When an
order is placed by a customer, the user would like the system to calculate the number of full pallets for each
line and to charge a 5 USD surcharge to the item if a full pallet quantity is not ordered. The user sets up
condition type KP01 in the pricing procedure and assigns condition base value formula '24'. Within the
condition records for condition type KP01, the user maintains the 5 USD surcharge. If an order line item is
placed that contains 5.5 pallets, the system will adjust the base value to 1 and compute a surcharge of 5 USD
for the sales line item.
CONDITION BASE VALUE FORMULA 26: BOLLO IN FATTURA
Formula '26' was provided to support the Italian Bollo in Fattura. Using this formula will set the condition to
inactive if the VAT value is not zero. This formula can be assigned to the R/3 delivered condition types BOLL
and MWBO in the pricing procedure.
CONDITION BASE VALUE FORMULA 27: XWORKK – DEACTIVATE CONDITION
This formula was delivered to support tax exemption licenses in Italy. The condition base value formula '27' is
assigned to the tax condition type in the pricing procedure. The formula is used to deactivate the tax when a
valid license exists. For additional information on tax exemption licenses, please refer to Note 72040.
CONDITION BASE VALUE FORMULA 28: 100% DISCOUNT
Formula '28' sets the rate of the condition to a 100% discount. This formula was delivered with condition type
R100 to support Release 4.0 Free Goods functionality.
7. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 715
Example:
A company has a free goods agreement with their customers. For every 10 cases of Product A that the
customer buys, the customer receives 2 cases of Product B for free. From a pricing perspective, the user wants
to track both revenue and sales deductions for the free items since Product B is also sold by itself sometimes
in the sales process. To do this, the user flags the free goods item category with the pricing indicator 'B'. In
addition, the user adds the R/3 delivered condition type R100 to the pricing procedure at the point at which the
100% discount should be applied. Condition base value formula '28' is assigned to condition type R100 in the
pricing procedure to apply the 100% discount rate.
CONDITION BASE VALUE FORMULA 29: FREE GOODS / INCLUSIVE
Formula '29' was delivered along with condition type NRAB to support Release 4.5 Inclusive Free Goods
agreements where the user would prefer to have a discount applied to the ordered item rather than having a
sub-item generated for the free quantity.
Example:
A company has a free goods agreement with their customers. If the customer orders 100 cases of Product A,
they receive 10 of these cases free of charge. Instead of having a free sub-item generated by the system to
represent the free 10 cases, the user would like a discount applied to the 100 case line item equal to the value
of 10 cases. To accomplish this, the user assigns the NRAB condition type to the pricing procedure and
assigns the condition base value formula '29'.
CONDITION BASE VALUE FORMULA 44: VAT FRANCE
This formula was delivered to support tax exemption licenses in France. The condition base value formula '44'
is assigned to the tax condition type in the pricing procedure. The formula is used to deactivate the tax when a
valid license exists. For additional information on tax exemption licenses, please refer to Note 72040.
CONDITION BASE VALUE FORMULA 50: QUANTITY ACTIVE INGREDIANT
Condition base value formula '50' was delivered to support pricing based on active ingredient quantities. This
formula is assigned to the condition types in the pricing procedure for which you work with proportion
quantities. Using this formula, the system can carry out billing at the main item level where the system
cumulates the quantities from the batch split items. For additional information on Active Ingredient
Management, please refer to the Batch Management Guide in the R/3 Library.
CONDITION BASE VALUE FORMULA 51: SHIPMENT COSTING -TAXES
Formula '51' was delivered along with shipment costing in the shipment cost document. This formula assigns
the tax indicator from the tax condition record to the shipment cost document item. This condition base value
formula should be assigned to tax condition types in the shipment cost document pricing procedure.
CONDITION BASE VALUE FORMULA 61: PREFERENCE
Condition base value formula '61' was delivered to solve a field overflow problem that can occur when
working with preference determination. This can occur due to the quantity dependency. Formula '61' is
assigned to the preference condition type in the pricing procedure (R/3 delivered condition type PREF). Also
reference condition value formula '61' For additional information, please reference Note 92321.
CONDITION BASE VALUE FORMULA 202: PRICE BOOK FACTOR
Formula '202' can be used to offer a price that is a percentage of a predefined price. For additional information
on this Release 4.5 feature, please refer to the R/3 Library documentation on Price Book, which can be found
in the Special Pricing Functions (Data Determination in the Access) section of the Sales & Distribution
Pricing Guide.
8. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 815
Example:
A company would like to define a pricing agreement with their customer whereby the customer should pay
90% of the material price from the previous year. This agreement can be stored using R/3 Price Book
functionality and the pre-delivered condition type PBUD. 90% is entered as the condition value in the PBUD
condition record and the pricing date is defined using the data determination in access functionality. In the
Price Book pricing procedure, condition type PBBS is then used to determine the base price from last year.
Next in the pricing procedure is condition type PBUP which is used to determine the gross price which should
be 90% of last year's price. To perform this calculation, condition basis formula '202' is assigned to condition
type PBUP in the pricing procedure.
5. Condition Value
Condition value formulas are available to influence the condition value that is displayed for a particular
condition type or value line in the pricing procedure. In standard pricing, the system will calculate the
condition value by multiplying the condition rate by the quantity. For example, 100 cases times $45 per case
equals $4,500. Using a condition value formula, it is possible to alter the condition value, in our example
$4,500. Condition value formulas can also be used to compute values that should appear as value lines in the
pricing procedure. As an example, standard delivered condition value formulas can be used to compute profit
margin and item net value. A condition value formula is assigned to a condition type in the pricing procedure.
When looking at the code for the standard delivered condition value formulas or when writing your own,
XKWERT is the field name that the condition value should be assigned to. Following is a description of the
condition value formulas delivered in the standard system related to SD.
CONDITION VALUE FORMULA 1: PROFIT MARGIN WITH REBATE
Formula '1' sets the value equal to the pricing subtotal '3' minus the cost of the line item.
Example:
A company offers rebate agreements to their customers that are paid out at the end of the year based on
cumulative sales. On a sales order, rebate agreement accruals show up as a statistical amount and do not affect
the net value of the line item. The company, however, would like to see the profit margin in the line item
reflect the expected rebate payments. In order to accomplish this, the user assigns the subtotal field '3' to the
relevant condition types in the pricing procedure so it's value equals the net value as well as the value of any
rebate accruals. The condition value formula '1' is then assigned to the ‘Profit Margin' line in the pricing
procedure. Note that subtotal '3' is just an example supplied by the system. Another subtotal could be used and
the user would then copy this formula and create a new one that uses the other subtotal value. If rebate
accruals should not be included in the profit margin calculation, the user would select condition value formula
'11'.
CONDITION VALUE FORMULA 2: NET VALUE
Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing
procedure. It contains the amount excluding taxes.
Example:
A company would like to show subtotals in their pricing screen that would represent the gross value, net
value, and net value 2. These are all value lines in the pricing procedure that do not correspond to a specific
condition type. To determine the value for these value lines, the user assigns the condition value formula '2'.
The system then shows in these subtotal lines the net value of the line item up until that point in the pricing
procedure.
9. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 915
CONDITION VALUE FORMULA 3: CASH DISCOUNT MINUS TAX
Formula '3' sets the value equal to the amount eligible for cash discount minus tax.
CONDITION VALUE FORMULA 4: NET VALUE PLUS TAX
Formula '4' sets the value equal to the net value plus tax. This can be assigned, for example, to a value line at
the end of the pricing procedure that should show the final value of the line item.
CONDITION VALUE FORMULA 5: PROFIT MARGIN DIALOGUE
Formula '5' provides an example of how a message can be displayed if the profit margin for a particular item
is below a predefined percentage. To use this feature, the user would copy formula '5' into a new formula and
assign the relevant percentage to the field MINDEST_PROZ.
CONDITION VALUE FORMULA 6: INITIAL PRICE
Formula '6' was delivered to support net price processing. For additional information on the use of this
formula along with examples, please refer to Note 80183.
CONDITION VALUE FORMULA 8: EXPECTED VALUE
Formula '8' provides an example of how the system can compare the customer expected value of a line item
with the net value computed by the system. If the system net value is not within a value range of 1 of the
customer expected value, than the item is blocked. Formula '8' was delivered along with the condition type
EDI2 for customer expected value. Users can copy this formula and specify their own value range tolerance in
the field MAXIMUM.
CONDITION VALUE FORMULA 9: EXPECTED PRICE
Formula '9' provides an example of how the system can compare the customer expected price of a line item
with the net price computed by the system. If the system net price is not within a value range of 0.05 of the
customer expected price, than the item is blocked. Formula '9' was delivered along with the condition type
EDI1 for customer expected price. Users can copy this formula and specify their own value range tolerance in
the field MAXIMUM.
CONDITION VALUE FORMULA 11: PROFIT MARGIN
Formula '11' computes the profit margin for a line item. This is done by subtracting the cost of the item from
the net value. This formula can be assigned to a value line at the end of a pricing procedure to show the profit
margin for the item.
CONDITION VALUE FORMULA 13: MINIMUM VALUE SURCHARGE
Formula '13' computes the applicable surcharge when the order value (before taxes) falls below the predefined
minimum order value. This formula was delivered with condition types AMIW (used to define the minimum
order value) and AMIZ (used to compute the surcharge if the minimum is not met). Within the pricing
procedure, formula '13' should be assigned to condition type AMIZ. In addition, the subtotal 'D' must be
assigned to condition type AMIW in the pricing procedure.
Example:
A company would like to define minimum order values for their customers. As an example, a minimum order
value of 200 USD is defined for Customer A. If Customer A places an order for anything less than 200 USD
(before taxes), the system should automatically compute a surcharge equal to the difference and apply it to the
order. To accomplish this, the user would configure pre-delivered condition types AMIW and AMIZ in their
pricing procedure as defined above and maintain a condition record for AMIW and Customer A equal to 200
USD.
10. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1015
CONDITION VALUE FORMULA 14: BEST PRICE
Formula '14' can be used to select the best price in a pricing procedure when more than one condition type to
determine the price has been configured.
Example:
A company quotes prices based on weight as well as number of cases. In the pricing procedure, they have
maintained two condition types for the price. Condition type ZWGT is listed first and computes the price
based on the weight. Condition type ZCSE is listed second and computes the price based on the number of
cases. When pricing is done, the system should automatically select the best price for the customer. To
accomplish this, the user assigns condition value formula '14' to condition type ZCSE in the pricing
procedure. Using this formula, the system compares the two. If the case price is more expensive, then the
ZCSE condition line is set to inactive. If the case price is less expensive, then the ZCSE condition line
remains active causing the ZWGT condition line to become inactive (active subsequent price in the pricing
procedure).
CONDITION VALUE FORMULA 15: MINIMUM PRICE
Formula '15' was delivered along with condition type PMIN to define minimum prices.
Example:
A company has defined minimum prices for materials. When a material is sold, it should not be sold for a
price below the predefined minimum price. When pricing is done for a sales document line item, if the net
price of the item falls below the minimum, the system should automatically compute a surcharge to bring the
price up to the minimum price. To accomplish this, the user would define the minimum prices using the
condition type PMIN. PMIN would be defined in the pricing procedure and condition value formula '15'
would be assigned. Using the formula, the system compares the minimum price with the net price calculated
to that point in the pricing procedure. If the minimum price is not met, the system computes the necessary
surcharge and assigns it to the PMIN condition line.
CONDITION VALUE FORMULA 16: ROUNDING THE TOTAL
Formula '16' was delivered along with condition type DIFF to support the rounding unit rules that can be
defined in T001R for company code / currency combinations. Condition type DIFF was delivered to perform
the rounding at the end of the pricing procedure with the total value. Using formula '16', the system computes
the rounded value and assigns the difference to the condition type DIFF.
CONDITION VALUE FORMULA 17: ROUNDING AS PER T001R
Formula '17' was delivered so that a condition value could be rounded off according to the rounding unit rules
that can be defined in T001R for company code / currency combinations. When formula '17' is assigned to a
condition type, the condition value will always be rounded using T001R.
CONDITION VALUE FORMULA 18: PERCENT CONTRIBUTION MARGIN
Formula '18' computes the percent contribution margin for the line item comparing the cost and net value of
the item. This formula can be assigned to a value line at the end of a pricing procedure to show the percent
contribution margin for the item.
CONDITION VALUE FORMULA 19: P-VARIANT RITTER
Formula ‘19’ is used to support the calculation of the net price. For additional information on the use of this
formula along with examples, please refer to Note 80183.
CONDITION VALUE FORMULA 20: P VARIANTS DISCOUNT
Formula ‘20’ is used to support the calculation of the net price. For additional information on the use of this
formula along with examples, please refer to Note 80183.
11. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1115
CONDITION VALUE FORMULA 25: KZWI1 MINUS TAX
Formula '25' computes the value of the condition line to be equal to the value in subtotal '1' minus tax.
Formula '25' was delivered along with condition type NETW to compute the value of the goods when tax is
part of the price. Reference standard delivered pricing procedure RVAB01 'Tax included in price'.
CONDITION VALUE FORMULA 36: CUMULATION CONDITION
Formula '36' enables the user to display the total of the net values of an item and all the sub-items belonging to
that item. This formula was delivered along with condition type KUMU. This condition type can be assigned
to the pricing procedure along with formula '36' to display cumulative values when main and sub-items are
used.
CONDITION VALUE FORMULA 37: TAX EXEMPTION LICENSE
Formula '37' was delivered to support tax exemption licenses in Italy. This formula should be assigned to the
condition type for tax exemption licenses in Italy (R/3 delivered condition type LCIT) in the pricing
procedure. For additional information on tax exemption licenses, please refer to Note 72040.
CONDITION VALUE FORMULA 38: EXCLUSION WITH VALUE ZERO
Formula '38' sets the value of the field AUSSCHLUSSWERTNULL to 'X'. This formula was delivered in
order to support condition exclusion where conditions with a value of zero should be considered in the
exclusion. For additional information, refer to Note 39641.
Example:
A company has two condition types in their pricing procedure that represent surcharges. A condition
exclusion group has been defined with these two condition types indicating that the lowest of the two should
be applied. In some cases, one of the surcharges may be zero. This could be due to a condition record that is
found or a manual entry. In order to have the system consider zero as the lowest surcharge for the customer,
condition value formula '38' must be assigned to one of the condition types in the pricing procedure.
CONDITION VALUE FORMULA 47: VAT FRANCE
Formula ‘47’ was delivered to support tax exemption licenses in France. This formula should be assigned to
the condition type for tax exemption licenses in France (R/3 delivered condition type LCFR) in the pricing
procedure to support this functionality. For additional information on tax exemption licenses, please refer to
Note 72040.
CONDITION VALUE FORMULA 48: CHECK DOWN PAYMENTS
Formula '48' was delivered to ensure that the down payment amount the user offsets in a billing document
does not exceed the actual down payment value. Condition value formula '48' is assigned to the condition type
in the pricing procedure representing down payments (R/3 delivered condition type AZWR). Down payment
functionality was delivered with R/3 Release 4.0.
CONDITION VALUE FORMULA 61: PREFERENCE MAX VALUE
Condition value formula '61' was delivered to solve a field overflow problem that can occur when working
with preference determination. This can occur due to the quantity dependency. Formula '61' is assigned to the
preference condition type in the pricing procedure (R/3 delivered condition type PREF). Also reference
condition base value formula '61'
For additional information, please reference Note 92321.
12. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1215
6. Structure of Group Key
A structure of group key formula can be used to influence the basis the system uses when reading the scale of
a group condition. Group conditions are used to cumulate quantities from more than one sales document line
item to read pricing scales. For example, when pricing a particular sales document line item, the user would
like the system to not just consider the quantity of the current line item, but the sum of the quantities of all line
items that share the same material pricing group as the current line item. The formula is assigned to a group
condition type in customizing. When looking at the code for the standard delivered structure of group key
formulas or when writing your own, XVAKEY is the field name that the structure of the group key should be
assigned to. Following is a description of the structure of group key formulas delivered in the standard system.
STRUCTURE OF GROUP KEY FORMULA 1: OVERALL DOCUMENT
Formula '1' adds up the quantities / values of all of the line items in the sales document that have the same
condition type as the group condition currently being processed.
Example:
A company defines a particular discount (condition type Z001) with scales based on weight. When a sales
order line item is priced that is eligible for the Z001 discount, the user would like the system to read the scale
with not just the weight of the current line item, but the combined weight of all items in the sales document
where the Z001 discount applies. To accomplish this, the user defines condition type Z001 as a group
condition and assigns structure of group key formula '1' to it in customizing.
STRUCTURE OF GROUP KEY FORMULA 2: ACROSS ALL CONDITION TYPES
Formula '2' adds up the quantities / values of all of the line items in the sales document independent of which
condition types have been applied.
Example:
A company defines their prices with scales based on weight. When a sales order line item is priced, the user
would like the system to read the scale with not just the weight of the current line item, but the combined
weight of all items in the sales document. To accomplish this, the user defines their price condition types as
group conditions and assigns structure of group key formula '2' to them in customizing.
STRUCTURE OF GROUP KEY FORMULA 3: MATERIAL PRICING GROUP
Formula '3' adds up the quantities / values of all of the line items in the sales document that have the same
material pricing group (field KONDM) as the current sales document line item.
Example:
A company defines a particular discount (condition type Z001) with scales based on weight. When a sales
order line item is priced that is eligible for the Z001 discount, the user would like the system to read the scale
with not just the weight of the current line item, but the combined weight of all items in the sales document
that have the same material pricing group as the current line item. To accomplish this, the user defines
condition type Z001 as a group condition and assigns structure of group key formula '3' to it in customizing.
STRUCTURE OF GROUP KEY FORMULA 10: SHIPPING MATERIAL
Formula '10' is only relevant for shipment costing in the shipment cost document. Formula '10' adds up the
quantities / values of all of the sub-items in a shipment cost document item that have the same shipping
material as the sub-item currently being processed.
7. Rounding Rule
Rounding rule formulas are provided to determine the way in which rounding should take place when a mass
change of pricing records takes place. For example, the user may be carrying out a mass price increase of 10%
to all materials in a particular material group. The user would like the system to round the new prices to .99
after the calculation. This can be accomplished with a rounding rule formula. A rounding rule formula is
13. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1315
assigned when a mass pricing change is carried out. When looking at the code for the standard delivered
rounding rule formulas or when writing your own, fields RV13A-KBETR and RV13A-CURCONV are used
to assign the rounded value to. Following is a description of the rounding rule formulas delivered in the
standard system.
ROUNDING RULE FORMULA 1: ROUND TO 9 DECIMAL PLACE
The amount is rounded down by one place and the decimal places of the rounded down amount are rounded
up to 9.
Example:
Price $698.45 increased by 1%
Without rounding rule:
$705.43
With rounding rule:
$704.99
ROUNDING RULE FORMULA 2: LAST DIGIT ROUNDED TO 9
The last decimal point of the changed amount is rounded up to 9.
Example:
Price $777.03 increased by 1%
Without rounding rule:
$784.80
With rounding rule:
$784.89
ROUNDING RULE FORMULA 3: 5 RAPPEN ROUNDING
5 Rappen rounding. This is only possible if the currency is CHF (Swiss Franc)
Example:
Price 12.10 CHF increased by 1%
Without rounding rule:
12.22 CHF
With rounding rule:
12.20 CHF
Price 12.13 CHF increased by 1 CHF
Without rounding rule:
13.13 CHF
With rounding rule:
13.15 CHF
ROUNDING RULE FORMULA 4: 2 DIGITS AFTER COMMA
The system rounds down to 0 as of the second decimal place
Example:
Price $555.55 increased by 1%
Without rounding rule:
$561.11
With rounding rule:
$561.10
14. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1415
8. Calculation Rule – Free Goods
Free goods calculation formulas can be used to define the way in which free goods quantities are computed
within a free goods agreement. The formula is assigned to a free goods condition record. When looking at the
code for the standard delivered free goods calculation formulas or when writing your own, work area L_FRM
is filled with the calculated values.
Following is a description of the free goods calculation rules delivered in the standard system.
CALCULATION RULE – FREE GOODS 1: PROPORTIONAL
Formula '1' interprets the free goods quantities as a proportional agreement.
Example:
A company offers free goods to their customers when they order certain materials. For example, when a
customer orders 100 cases of Material A, the customer receives an additional 20 cases of Material A for free.
The company would like to have the system treat the 'Buy 100, Get 20 Free' agreement proportionately. For
example, if the customer orders 162 cases, the system should automatically grant 32 for free [162 x (20/100)].
To accomplish this, the user would assign free goods calculation rule '1' to the free goods condition record.
CALCULATION RULE – FREE GOODS 2: UNIT REFERENCE
Formula '2' interprets the free goods quantities as being related to number of units.
Example:
A company offers free goods to their customers when they order certain materials. For example, when a
customer orders 100 cases of Material A, the customer receives an additional 20 cases of Material A for free.
The company would like to have the system interpret the 'Buy 100, Get 20 Free' agreement by granting 20
free for every full 100 purchased. For example, if the customer orders 162 cases, the system should
automatically grant 20 for free [100 x (20/100)]. To accomplish this, the user would assign free goods
calculation rule '2' to the free goods condition record.
CALCULATION RULE – FREE GOODS 3: WHOLE UNITS
Formula '3' grants to free goods only if whole units are ordered.
Example:
A company offers free goods to their customers when they order certain materials. For example, when a
customer orders 100 cases of Material A, the customer receives an additional 20 cases of Material A for free.
The company would like to have the system apply the 'Buy 100, Get 20 Free' agreement only if the customer
orders in increments of 100. For example, if the customer orders 162 cases, the system should grant 0 for free
since 162 is not a multiple of 100. To accomplish this, the user would assign free goods calculation rule '3' to
the free goods condition record.
Steps to transport a Configuration Request :
1) You carry out config. changes in "Golden Master" client , (say100) in DEV server.
2) When you save, system prompts a Transport request dialogue, which is generally, saved by input of a
description that identifies the Kind of Config carried out. User name appears by default with the Config
request description when saved.
3) This is required to be tested in (Unit) Test Client say 120, by Client Copy of the Request using Tcode -
SCC1.
15. Eddie Mogilevsky, SAP SD Certified Consultant, Eddie.mogilevsky@yahoo.ca, +11-972-547805649 1515
4) On successful test results, we need to release the request (Tcode = SE01 or SE10). Here Collapse the
request line once. Then click on Sub-task and press Transport button.. Then, Click on Main task and again
press Transport button System gives success message.
5) Subsequently the BASIS Guy can transport the request to QUALITY and PRODUCTION Clients.
I hope this proves good clarity on Functional Task side.
Posted
Eddie Mogilevsky
SAP SD Certified Consultant
Eddie.mogilevsky@yahoo.ca
+11-972-547805649