Entering content frameProcess documentation Sales Pricing Process (PS)

Purpose

A sales project is usually a one-off service, carried out for a specific customer. The unique nature of such projects means that you will often not have recourse to standard prices when you are calculating the sales price. The price calculation in such cases is then based on the plan data from the project.

You can run sales pricing in the following ways:

  1. If you create a project due to a customer inquiry, and you wish to calculate the sales price, call up sales pricing using the menu path. The system determines the sales price based on either the planned costs (totals records) or data from Easy Cost Planning.
  2. If you carry out sales pricing for a project you created without a customer inquiry, call up sales pricing in the Project Builder. In this case the system determines the sales price based on the data from Easy Cost Planning only.

For more information, see Structure linkSales Pricing in the Project Builder.

In this process you can:

You can create any number of sales price calculations and save them in documents, without creating a quotation.

For more information, see Structure linkSales Pricing Options.

Note

This is a change from earlier releases (up to and including Release 4.5B), where the values from the SD document assigned to the document and the billing plan were added together.

As of Release 4.6A, the system records only the values from the billing plan, if there is one.

For more information, read Structure linkRecording Planned Revenues.

For more information, see Structure linkCreating Quotations for Customer Projects.

If you wish to carry out sales pricing for a project assigned customer inquiry, see the section on integration. If you wish to carry out sales pricing without a customer inquiry, using the Project Builder, then the section on integration is irrelevant.

Integration

If you wish to carry out sales pricing for a project with a customer inquiry, then you are also currently using Sales and Distribution (SD).

To link the sales order in SD with the Project System, assign one or more sales order items to a WBS element (billing element or account assignment element). The inquiry item then supplies the SD data needed by the sales pricing.

If you assign an account assignment element to an inquiry item, the system determines the relevant billing element in the project. The billing element, along with the WBS elements subordinate to it (which are not billing elements), activities, and orders, makes up the billing structure.

Regardless of whether you assign the inquiry item to a billing element or account assignment element, the system considers the whole billing structure when carrying out sales pricing.

This graphic is explained in the accompanying text

 

Prerequisites

Maintain the prerequisites listed here for the sales pricing you wish to carry out for the project assigned to a customer inquiry.

For information about the prerequisites for sales pricing in the Project Builder, see Structure linkSales Pricing in the Project Builder.

Settings in Project System (PS):

If you have not assigned a billing element to the sales document item, the system records the planned revenue in the superior billing element in the hierarchy.

For revenues from SD documents to be assigned to a project, choose an account assignment category that allows assignment to a project.

Settings in Sales and Distribution (SD)

To do this, define the WBS element to be account assigned to the sales document item on the Account Assignment tab page.

The system uses the inquiry item to determine the SD data for the sales pricing.

To do this, define a Dynamic Item Processor profile (DIP profile) in the tab strip Sales B for the sales document item.

For more information, see Customizing for the Project System under Revenues and Earnings ® Integration with SD Documents ® Assign Sales Orders to Project Account.

Other Prerequisites:

Process Flow

  1. To carry out a detailed sales pricing on the basis of the plan data in the project, access the sales pricing and enter a project definition, WBS element, and inquiry/inquiry item as your selection criteria.
  2. For more information, see Structure linkSelection Criteria.

  3. You can create a new sales pricing or edit an existing one.

When you opt to create a new sales pricing, the system works as follows:

    1. Starting with the costs planned by cost element, the system determines the sales price basis items using the DIP processor profile (see Prerequisites above). These items of the sales price basis are identified as dynamic items.
    2. The system sorts the various dynamic items per the SD document items and uses Structure linkSD price determination to calculate the sales price.

To this end, it uses the document category (from the DIP profile) to determine the pricing procedure. Further data required for the price determination, such as the ordering party, is defined in the inquiry.

  1. There are two views you can use for processing:
  2. Structure linkSales price basis, which displays the internal view of the calculation.

    Structure linkSales price view, which displays the customer view of the calculation.

    You can edit the pricing data in both views and can change views at any time.

  3. You then do one of the following:

Note

The sales price is entered in the billing plan as the target value. You can distribute the target value manually to various dates.

If the sales price is changed later, the system does not automatically copy the change to the billing plan.

 

Result

If you have adopted the sales price as the target value in the billing plan, the system uses the billing plan to record the sales price as planned revenue in the project.

If you have saved a sales price as a document, you can use it to create a quotation in SD.

 

 

Leaving content frame