SAP Sales Pricing (DP81) via Project

 

 

Business Scenario:

Sales Pricing is the functionality of SAP SD module which will use the planned cost of the Project to determine and save the Prices for the services or materials produced. Sales Quotations will be created automatically through Projects by using Sales Pricing. Revenue planning of sales Project.

Typically, the data of sales pricing is used particularly for the creation of quotations and the revenue planning of SD projects for which sales prices cannot be determined based on standard prices. If you can use existing standard prices and fixed conditions for SD projects, sales pricing is usually not required. In this case, the quotation is not created via sales pricing, but directly in SD.

 

Following are the two ways to create Sales Pricing

Transaction	Process	Remark
DP81	Sales Quotations will be created w.r.t. Customer Inquiry
DP82	Sales Quotations will be created without customer inquiry

 

Project assigned customer inquiries:

The customer inquiries will be created about the price or availability of services or materials in the presales phase of the Customer Projects. This sales document (i.e. Inquiry) should be account assigned to a WBS element which is necessary to establish the link between sales document item and the Project. Which planned data is considered during sales pricing, and how and according to which criteria the data is aggregated, is controlled via a dynamic item processor profile (DIP profile) that must be stored in the detailed data of the sales document items (entered in the inquiry item under Sales B).

It is possible to create pricings not only for operative projects, but also for simulations. The onlylimitation is that there must be at least the billing WBS elements in an operative project and theplanned revenues from the quotations must always be updated to the operative project. To getplanned revenues for a simulation, you must use billing plans which can be created out of thepricing.

Projects without customer inquiry

            The SD data (like Sales Organization, distribution channel, Division & DIP Profile) required for a sales pricing must then be stored in the project definition. For specifying the customer, an appropriate partner determination procedure must be entered on the project definition level that enables you to enter a customer number on the Partnertab of the project definition. Sales pricings for projects that do not reference any inquiries canbe created using the Project Builder or directly via Transaction DP82.

 

During sales pricing, a two-step aggregation of the planned data of the project takes place which are as follows:

1. Sales price basis: Planned cost of the Project were aggregated according to the dynamic items (defined in the DIP Profile). In addition to the aggregation itself, the DIP profile controls how the aggregated values (dynamic items) are presented in the upper area of this view. The lower area of the sales price basis view has more details about the aggregated items. In particular, the lower area allows for a manual change to items by an amount, quantity, or percentage. If you change items, the amount transferred to the sales pricing deviates from the original amount.
    

    
   

2.  Sales price view: During the second aggregation step, the aggregated and possibly manually changed items of the sales price basis are automatically linked to material numbers. Depending on the DIP profile settings, these can be, for example, material numbers from material components of the project, or fixed material numbers stored in the DIP profile for project activities or for the material to be produced using the project. The material numbers are sorted and grouped into sales document items.Using the pricing function of SD, the system can now determine a sales price for the individual items using the material numbers and the SD data of the inquiry (customer number, sales organization, etc.). The sales document items and the corresponding sales prices are shown in the sales price view. The sales price view corresponds to a customer view of the sales pricing.

The purpose of this blog is to explain the Sales Pricing process with Easy cost planning in detail. It is a common requirement which we received from client to generate a customer quotation based on the planned costs in the project builder.

In simple words, to generate sales pricing & then from Sales pricing to quotation creation, you need just stick to ECP.

Any planned cost can be transferred to sales pricing, But you need to configure DIP profile for this. Learn DIP profile, that is very important to create sales pricing & RRB.

Configuration details

DIP Profile (ODP1)

DIP profile usage used to handle different business processes with same profile:

1. Billing and Result analysis:The first usage is "Billing and Results Analysis". Two sales document types can be specified: one for debit memo requests, the other for credit memo requests. The decision on which items are debited or credited is based on the sign of quantity and amount. If only one sales document for debit memo requests is specified, all items are debited, but negative quantities or amounts with opposite signs. It is not possible to set up a profile with only an entry for the credit memo request,nor should you specify a sales document type of a credit memo request in the column of the sales document type for the debit memo request. If you are using both credit memo requests and debit memo requests, take care to customize your sales document types and the item categories correctly. 
2. Quotation Creation and Sales Pricing:The second usage is "Quotation Creation and Sales Pricing". Here, only one sales document type can be specified for the created or simulated quotation. Normally, there should be no negative items in this document, but if there are, the negative items are treated as they would be in the single document case of billing usage.

Characteristics:

At first, you must define the relevant characteristics of your profile. Only these characteristics are filled from the sources. The relevant characteristics also define the first summarization of the source data to dynamic items. All source data with equal relevant characteristics is summarized to one dynamic item. Therefore, the more characteristics are activated in the profile, the more dynamic items are created. This can result in a 'line-item processing': for example, if you mark the characteristics 'Document number' and 'Posting Row' as relevant for source 'Actual Costs – Line Items', you get one dynamic item for each CO line item. By selecting all other characteristics provided by this source as relevant, you get the most detailed dynamic items, but system performance is not as good.Most of the characteristics are optional, but some are required, dependent on the profile usage. In both cases, the 'Object number', 'Transaction currency', and 'Unit of measure' characteristics are required. For usage 'Billing and Results Analysis', the 'Period' is an additional required characteristic. This is because the document flow for resource-related billing is stored periodically.

The "Mat. Determination" indicator defines the characteristics to be used in the criteria for the material determination (see chapter 3.1.4). You can select all characteristics here, but this may make the material determination unclear. It is better to select only those characteristics you really need.

A very important indicator is the "No Summarization" indicator. Normally, the system summarizes dynamic items to one sales document item if they both have the same material found in material determination. If this indicator is set, the system does not summarize two dynamic items if they differ in this characteristic, even if they have the same material number. Therefore, the indicator has to be set for a characteristic if you want to use it in SD - for example, to show the personnel number in your invoices. If the indicator is cleared, the system has to clear the characteristic in the sales document item because its value is clear. A better example is the characteristic "Unit of measure"'. You can only show the quantity in the invoice if you do not summarize using different units (such as PC and H). Therefore, this indicator is setby default for the characteristics"Transaction currency" and "Unit of measure" but it can be switched off for both.

Structuring:

With the structuring tool of the dynamic item processor, you can define a hierarchical display of

your dynamic items on one or more of the profile's relevant characteristics. It is even possible to

change this structure online. Therefore, you have a tool for the flexible display of the costs to be

processed. In the DIP profile, only the default structuring is defined. It is used when you start working with an object with this profile.

Select the "Structuring" indicator if you want to use a characteristic for your hierarchical overview.If you choose more than one characteristic you have also to define a 'Sequence' number telling the system in which order the structuring should be done.

 

Next, you must enter a set in the field 'Set ID'. A set is a flexible structure for organizing hierarchies also used in report writer. To maintain sets, you can use transactions GS01 (create),

GS02 (change), and GS03 (view). You can also use the green arrow in the column next to the set name to create, change or display a set. Just enter a set name and press the button. If the set exists, it is opened for edit; otherwise, you can create it. If you are in display mode of customizing,the set is opened in display mode. Sets are always created with reference to a field of a structure or table in the ABAP data dictionary. Here, the program uses the structure AD01ATTR containing all possible characteristics of dynamic items. You should also use this structure if you are using the mentioned set maintenance transactions.

For some special characteristics, you can also use sets from accounting: cost element groups,

activity type groups, cost center groups or statistical key figure groups. They use the same internal technology but are marked as special accounting sets. Therefore, they can be used in the DIP, but sets generated for the same table field using the general set maintenance transactions cannot be used in accounting.

 

 

Source Selection:

In the sources view, the source data to be processed is specified. SAP delivers nine sources for

the different business processes.

1. Actual costs - Line items: This is the most commonly used source for resource-related.
2. billing. It offers the most detailed data to create the dynamic items.
3. Actual costs - Totals records: This source can also be used for resource-related billing. It has the advantage of being faster than the line items, but you cannot use all of the characteristics offered by the line-item source.
4. Statistical indicators - Line items: This is a source for actual statistical key figures. It can be used to bill, for example, kilometers.
5. Statistical indicators - Totals records: The same as for the actual costs - faster but with fewer characteristics
6. Funds - Line items: The funds source can be used for billing payments and down payments. These payments refer to CO value types 57 and 61.
7. Funds - Totals records: Faster but with fewer characteristics than the line items.
8. Planned costs - Totals records: This source can be used for pricing or quotation creation.The system reads all planned costs.
9. Planned Statistical indicators - Totals records: A source pricing or quotation creation based on planned statistical key figures.
10. Easy Cost Planning: This source can be used for pricing for projects. In fact, it is the onlysource that can be used for pricing in Project Builder. It is also possible to select the datafrom Easy Cost Planning for a pricing based on an inquiry
11. Inter company Line Items (since Extension 2.00): This source is used for transaction DP93only.