Ansicht
Dokumentation

CRM_REB_PRICING - Define Settings for Pricing

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Here, you will find the information you need on the pricing service in CRM Rebate Processing. This service is for the following in rebate processing:

• To determine and calculate rebates (basis, scale base value, accrual value) in the rebate processing extracts

• To determine taxes or other conditions when carrying out settlement for rebate programs

You set up pricing in Customizing for rebate processing in the Rebate Determination section. Here, you have to process the following activities so that the pricing service can be used fully in rebate processing:

• In the field catalog, specify which fields can be used for creating condition tables.

• You use condition tables to define combinations of allowed fields for which you want condition records (condition master data) to be stored in the system.

• Access sequences allow you to define search strategies according to which the system searches for condition records in the condition tables.

• You use condition types to define the characteristics a condition has in a business transaction, for example rebate, surcharge, discount, or tax.

• In the pricing procedure, you define which condition types are valid within a specific business transaction, the sequence in which they are calculated, the occurrence of subtotals, and other control information. For rebate condition types enter usage BO here.

• You use condition maintenance groups to group together different conditions and their accesses. When you make an assignment to an agreement item category, the conditions permitted in it are defined.

In order to be able to make full use of the pricing service in rebate processing, you have to process the following activities in Customizing for rebate processing:

• Under Extract Types -> Define Extract Type either select the pricing procedure that you want to be used for rebate determination in the extract, or set the Transfer indicator. If you opt for the former, the pricing procedure defined is used for rebate determination. If you choose the latter, the pricing procedure of the original document (of the billing document) is used.

• Choose the pricing procedure that you want to be used in the settlement document under Rebate Profiles > Settlement Profiles -> Define Settlement Document Type.

Ensure that the pricing procedures that are used for the generation of the pricing documents of the settlement documents and for rebate determination in the extract contain at least the conditions that are contained in the relevant rebate agreements.

The fields that can be used for determination in CRM Rebate Processing are restricted in comparison to sales documents, since not all fields are transferred to the billing document and thereby also the extract by default.

If you want to use additional fields from the CRM environment or user-defined fields in pricing in CRM Rebate Processing, you have to make the following settings:

1. Enter the required fields in the field catalog (under Rebate Processing -> Rebate Determination).
2. Enhance the new fields for the extract or the settlement document under Rebate Processing -> System Enhancements -> Process Metadata.
3. Define a corresponding assignment for the pricing service under Rebate Processing -> System Enhancements -> Process Metadata.

If this assignment is not sufficient or you require additional functions, the following Business Add-Ins (BAdIs) make it possible to set up the following user-defined enhancements:

• Rebate determination mapping extract document

• Pricing mapping settlement document

You can find these Business Add-Ins in Customizing under Rebate Processing -> System Enhancements -> Generated BAdI Definitions.

• Three different rates exist in a rebate condition (normal pricing conditions only have one rate):

• The condition rate is only used for the payment, where it is used together with the condition basis cumulated via the validity period to calculate the payment value.

• The system uses the accrual rate to calculate the accruals to be created in each extract.

Note that the accruals can only be posted if the rebate condition is marked as accrual-relevant, and the system also finds it in the extract. Although accrual-relevant rebate conditions can also be transferred into sales documents and billing documents, they are only used for information purposes there. Accruals are not posted, and no condition basis or scale base value is cumulated.

• The rate for direct payment allows you to award parts of the rebate directly in the order in the form of a normal discount. In order to use this functionality, note the following:

When extracts are processed only conditions that have the condition type Relevant for Accrual in Customizing are found. The accruals are calculated and posted for these conditions only. The basis and scale base value are also determined and cumulated in the rebate due list.

Rebate processing does, however, also allow you to pay out a part of the rebate directly in the sales transaction. You have to make the following settings for this:

- Define a second rebate condition type that matches the original but does not have the indicator Relevant for Accrual set and specifies the original condition type as a reference condition. By marking the condition type as not relevant for accrual, you indicate that you want the direct payment rate to be transferred as opposed to the accrual rate.

- Enter the condition record under the original condition type, and fill the field for the direct payment rate.

- Enter the second condition type into the pricing procedure in the sales transaction.

The system transfers directly paid rebate rates from the billing document into the extract regardless of whether the condition is contained in the pricing procedure that is assigned to the extract. The value of the condition is cumulated as Paid Externally and taken into account accordingly in the settlement.

Creation of accruals, cumulation of the basis and scale base value, and payment take place on the original condition. Therefore, it must be contained in the pricing procedures for the extract and payment document.

• The scales stored in the rebate condition record are only used to determine the relevant payment amount. They play no part in the calculation of accruals or direct payment rates.

• Since no prices, subcharges or discounts are stored in the extract, the system can use the net value or user-defined subtotals to calculate value-independent rebates. The following values are transferred to rebate processing by default:

• Net value

• Gross value

• If the Subtotals of Pricing in Billing feature is activated, subtotals one to three are also transferred to the extract and saved there as additional value fields.

• In the standard configuration, net value, gross value, and subtotal 1 are transferred to pricing as rebate bases. These bases can then be accessed using formulae. The following formulae are supplied with the standard system:

• Basis formula 1201 - accesses rebate basis 1; this is filled by default from the net value

• Basis formula 1202 - accesses rebate basis 2; this is filled by default from the gross value

• Basis formula 1203 - accesses rebate basis 3; this is filled by default from the first additional value of the extract, that is to say from subtotal 1 of the billing document if the corresponding feature is active there.

• Scale base formulae exist for the scale base value.

• If subtotals 2 or 3 are used, you can fill the rebate bases differently according to your requirements using the BAdIs described above.

• If the system does not find a pricing procedure for an extract type or settlement document, it does not process pricing conditions.

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 10624 Date: 20240523 Time: 183658     sap01-206 ( 169 ms )