SD REBATE PROCESS

This document consist of steps ; Standard Rebate Config. , Activation of S136 table , Developments. Rebate

agreement is a special agreement granted to the customer on a specific volume of sales a specific period of time.

IMG>SD>Billing>Rebate Processing>Rebate Agreements>Define Agreement Types>

Step 1: Define Agreement Type

Select"Define Agreement type " from choose activity,double click on it.

Select an Agreement click on copy button and rename it.

Here I selected standard and renamed “0002-Material Rebate” to “Z002- Material Rebate-AA11”

Step 2: Condition Type Groups

2.1: Click on Define condition Type groups

Click on New Entries Enter your Copied Condition Type group which you created and Maintain “Blank” for Category of the condition type group.

Step 2.2: Assign Condition Types /tables to Condition Type groups

Assign Condition Type “Bo02” and Condition Table “1”to your Condition Type Group „Z002‟.

Step 2.3: Assign Condition Type groups to rebate agreement types

Click on it, Assign Condition Type group to Agreement Type.

Step 3: Condition Technique for Rebate Processing

Click on it

Same as like Pricing Procedure configuration

Step 3.1: Select Maintain condition table for Rebates

Select Maintain Condition Tables for Rebate and Click on Choose

Based on requirement we can create new condition table

Save and exit (if anything created)

Step 3.2: Maintain Access Sequence

Select Maintain Access Sequence

Click on Choose, Go to New Entries and Maintain Access Sequence

Maintain “1” Relevant for Rebates

Step 3.3: Define Condition Types

Choose Define condition types

Select it and click on Choose

Rebate condition types (BO01, BO02, BO03, BO04, BO05, BO06)are available in Standard SAP

Assign Access sequence to condition Type (if copied)

Step 3.4: Maintain Pricing Procedure

Select Maintain Pricing Procedure and click on Choose

Choose Standard or copied Pricing Procedure by use

Click on Position Button left side Dialog Structure

Make sure that Rebate condition types must available in (copied) pricing procedure

With Requirement-24 (only in Billing Document)

Account Key - ERB

Accruals - ERU

Step 4 : Account Determination for Rebates

(If your are good at Account determination Procedure configuration no need to fallow this). The same process like

Account Determination Procedure.

Step 4.1: Define A/C keys

(Standard keys available in SAP)

ERB -Rebate Sales deduction

ERU –Rebate accruals

Step 4.2: Assign Account Keys to our Pricing Procedure

In standard pricing procedure it’s available , Steps 901 to 905.

Step 4.3: Maintain Access Sequence

(standard already created like Accounting Determination Procedure)

Step 4.4: Define Account Determination Types

Assign access sequence to Condition type

Step 4.5: Assign G/L Account

Choose table 1-customer group/Material Group/Account Key

Click on Assign button and Maintain G/L Account Provision Account

Step 5: Activate Rebate Processing

IMG>SD>Billing>Rebate Processing>Activate Rebate Processing

Click on “Activate Rebate Processing”

Select “Billing Documents for Rebate Processing” in Choose Activity.

Step 5.1: Select Billing Document for Rebate Processing

T-Code: OVB0

(Or) T-code: VOFA

Enter billing Document Type and put check mark for Relevant for Rebates

Go back, Select “Activate Rebate Processing for Sales Organizations”

Step5.2: Activate Rebate processing for sales organization

Click on Choose

(Or) Go to Enterprise structure

T-code: OVX5

Select your sales organization

Put check mark for Rebate process Active

Step 5.3: The payer must be relevant for rebate processing.

Go to XD01 or XD02 Payer customer master record

Go to sales are data tab then choose Billing tab put check mark for “Rebates”

You will get details of S136 table usage instead of S060 in next step.

There will some advantages and new process to implement rebate more effectively.

REBATE PROCESS – SIS TABLE CONFIGURATIONS

This step explains how you can implement SAP's new rebate procedure . SIS 136 structure will be activating

instead of standard S060 structure.

How S136 is different from S060?

* S136 table contains billing document number that for me a advantage so S060 had all details of amounts of

rebate and invoices.

* Condition exclusion (use of condition exclusion indicator for the condition type and exclusion with exclusion

groups possible)

* Use of condition value formulae

* Use of condition basis formulae

* Exclusive condition access in the access sequence

* The difference between S136 and S060 is that in this procedure all affected billing documents are updated with

changes which are relevant for rebate.

* Additional fields in pricing procedure --> for example : Alternate condition type and alternate condition base

value.

The sales volume of earlier billing documents should be taken into consideration for subsequent agreements.

In the this procedure the old billing documents are actually changed. A new pricing is carried out (pricing type I:

only changes to rebate conditions and accruals, no change to the net price!).

Related Tables :

S136 , KOTE* , KONA .

Related OSS Notes :

105681 - Consulting: New rebate procedure 410579 - FAQ: Rebate processing 75778 - Consulting/troubleshooting for rebate processing

Standard Rebate Configuration :

Rebate Process Configuration

Related Wiki Pages :

http://wiki.scn.sap.com/wiki/display/ERPLO/Enhancements+andBusiness+add-ins+used+in+standard+t-codes+of+SD

http://wiki.scn.sap.com/wiki/display/ERPLO/REBATE+AGREEMENTS

Pricing - ERP Operations - SCN Wiki

16 Fields in Pricing Procedure and Their Description - ERP Operations - SCN Wiki

-----> Configuration steps of new rebate procedure <-----

Activation of the new procedure :

Spro --> Sales and Distribution --> Billing --> Rebate Processing --> Activation Of The New Rebate Procedure

From Release 4.6A

You can activate the new procedure by activating standard statistics structure S136 (Transaction OMO1).

You must set the update to 'Synchronous updating (1)

Basically you can also use the new procedure for existing data. In this process, consider the following:

When you activated statistics structure S136, you must set it up again for existing billing documents. You can do

this via the standard function for the statistical setup of billing documents (Transaction OLI9). 'Redetermination of

the update group' and 'Update documents' are not required.Then copy the set up version to version '000'

(Transaction OLIX).

Firstly , run belowed program, advises "Execute in background" .

Secondly, copy set up version to '000' .

For the already existing agreements there should be no rebate correction documents (B2) which already

performed an accruals correction. Otherwise, the accruals would be updated again during the following update

run of the billing documents and as a result would be corrected more than once (the update run does not take

existing rebate correction documents into account!). You may have to cancel existing rebate correction

documents.

Update of the billing documents

You can use program SDBONT06 to update the affected billing documents.

VBOF tcode can be used for to run this program.

In VBOF tcode , user must be carefully when fill required fields.

Focus on : Validity end date , FI Document type , Posting date , Test or NOT.

Please be careful validty end date before : This must be last day of the agreements.

Rebate Agreement Types

You can use Expended Rebate Agreement Types :

There will be different document types in sales and invoices.

Implementation of rebate procedure :

- Firstly , create sales order and following documents into invoice without rebate. Be sure , there must not be a

agreement.

- Secondly , create a new procedure agreement with VB01.

- When you execute a settlement , you will get a message related with non updated documents. If you update

billings with VBOF ,

SAP will update related rebate condition in calculation schema.

DEVELOPMENT / ABAP

SE24 ZCL_IM_ZWB2_SD_COND_SAVE_A

To control conditon types , this code blocked is written by Aytul Korkut.

Sap destek M.Ozgur Unal 27.03.2015