Pricing

General Pricing Procedure Notes

Other topics in SD have an impact on the pricing procedure, to ensure these are not

overlooked I have listed a few of them here:

• Credit management The system uses the value as stored in the subtotal A. This

will store the value in a special field called KOMP-CMPRE (item credit price).

Ensure subtotal A is assigned in the correct place in the pricing procedure, usually

the “net value.”

• Payment terms Generate a discount if the amount due is paid before a specific

date. This is automatically used by the system, and requires the condition type

SKTV to be in the pricing procedure.

• Cost of sales The system automatically uses condition type VPRS as the condition

to represent cost.

• Rebate The rebate condition types are determined if a valid rebate agreement for

the material has been created for the customer. The rebates configuration would

need to be done and a rebate agreement created for the customer. SAP will use the

rebate agreement to calculate an expected amount that this sale will contribute to

the customer’s rebate. Accruals can be posted to the GL using these amounts. In this

case the accrual account key ERU must be set up and assigned to the accrual

condition type. (Rebate condition types must be defined as expense reimbursements

in the condition type record so that they are not included in the net value.)

Use an authorization profile (not covered in this book) to ensure the users of the system

cannot view the margins or the pricing procedure.

The SAP pricing procedure does not automatically recognize during an update to price

relevant fields (excluding the few below in List A) in a sales document, whether a condition

record which uses the changed field, exists and therefore if pricing should be re-calculated

or not.

For the following List A, the system will re-price according to the re-pricing type, the

type of condition type affected is determined by the condition category.

 

 

Customizing Steps in Pricing

The sequence in the creation of the discount condition type that we followed in the example

of Z007 was used to assist continuity in thought. Whenever using the condition technique

you may find it easier to use the following sequence when customizing:

1. Put the fields you will need into the field catalog.

2. Create the condition tables you will need.

3. Create the access sequence you will need.

4. Assign the condition tables to the access sequence.

5. Create the condition types.

6. Assign the access sequence to the condition types.

7. Create the determination procedure (pricing procedure), if necessary, and assign the

condition types to it.

8. Assign the determination procedure.

9. Lastly, create your condition records.

 

Price procedure

The CTyp column shows the condition type. This is the backbone of the pricing procedure.

The condition type is the link, as you know, to the access sequence all the way to the actual

condition record.

When you enter a condition type, the description field is filled automatically with the

description from the condition type.

If you wish to enter a sub-total or total, no condition type applies. In this case, you can

enter a description without a condition type—for example, “net price.”

The From and To columns are used in two circumstances:

• To define the range for a subtotal For example, if you want to add up all the

conditions types from step 10 to 50, you would enter 10 and 50 in the From and To

columns, respectively.

• To define the basis for a calculation For example, if a discount is defined as a

percentage, you need to indicate which step must be used as the basis for the

calculation. If the calculation must be performed on step 100, you would enter 100

in the From field.

The Man column (for “Manual”) is used to indicate if the condition type for which it is

assigned to is allowed to be processed automatically or only manually.

FIGURE 8-11 Maintaining a pricing procedure

The Mdt column (Mandatory) is used to identify those condition types that are

mandatory in the pricing procedure. Mandatory condition types are, for example, the sales

price or the cost price. Should a mandatory condition not be found in the pricing procedure,

the system has an error in pricing and the respective sales order cannot be processed

further—for example, no delivery will be able to be made.

The condition types marked as statistical entries affect the pricing procedure in that they

will not be included in the Net Value calculation for that item. (The net value is displayed in

the item details of the order and invoice, and the total of all items’ net value is displayed on

the order and invoice document.)

The Stat column is used by the pricing procedure to add a value statistically. That is, the

value represented for this step will not alter the overall value in the procedure. This may be

used, for example, to represent the cost price of the material sold.

The thin column following Stat, which is normally obscured, is labeled P for Print. This

column may be made wider (as may all the other columns) by clicking the line separating

the columns and dragging it. This print indicator is used to determine what descriptions

and associated values assigned to a step are to be printed on a document—for example,

order confirmation.

The SubTo column is used to assign a subtotal key to a step in the pricing procedure.

These subtotal fields are then used in other areas of the system such as in the logistics

information system. For example, it is recommended you assign the subtotal field 4 to the

total value in the pricing procedure for freight.

The Reqt column is used to assign a requirement to the condition type. This requirement

may then be used to exclude the system from accessing the condition type and trying to

determine a value. This may be used, for example, to specify that the condition type, a

discount, should only be accessed if the customer has a low-risk credit group.

The AltCTy column is used to specify that the system is to use the formula represented

in this column as an alternative in finding the value of the condition type, rather than by

using the standard condition technique. This may be used, for example, to calculate

complex tax scenarios.

The AltCBV (alternative condition base value) column indicates a formula assigned to a

condition type in order to promote an alternative base value for the calculation of a value.

For example, you may specify a formula that uses a subtotal of 4 from the subtotal field and

then modifies it slightly by dividing it by 2 and using the resultant value as a base value for

a condition type.

The ActKy (account key) and Accrls (accruals account key) columns are used to assign

account keys that in turn are assigned to general ledger accounts, which are used by the

Finance department to register postings. The Accrls account key is used to determine a GL

account—for example, when a value is posted for rebate agreements.

Now that we know what the columns represent we need to allocate the condition types

to the pricing procedure in the best way possible in order to meet both the needs of the

business and the legal requirements.

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/14397246/viewspace-612537/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/14397246/viewspace-612537/