Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
SD-BIL-RB-ENH (Application Component) Extended Rebate⤷
RBT_ENH (Package) Extended Rebate
IMG Activity
| ID | RBT_ENH_CSEQ | Set up Variable Key for Rebate Settlement |
| Transaction Code | S_ABV_91000189 | IMG |
| Created on | 20011210 | |
| Customizing Attributes | RBT_ENH | Extended Rebate Processing |
| Customizing Activity | RBT_ENH_CSEQ | Set up Variable Key for Rebate Settlement |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RBT_ENH_CSEQ |
Here you maintain the composition of the variable key for the rebate processing of each agreement type, and the assignment of the values to the corresponding fields in the credit memo. When the rebate info structure S469 is updated, the values from the communication structures are copied into the variable keys in the order specified by the counter. When the credit memo is created, the corresponding values are copied from the variable key into the indicated target fields of the structure KOMFKGN. It is also possible to replace a value from the communication structures by a direct value, which is then copied into the corresponding target field of the structure KOMFKGN.
When the rebate is settled, the system generates a line for each variable key in the S469 in the credit memo instead of a line for each condition.
Example
- You have defined a rebate condition at material group level. But you want to settle the rebate agreement for different materials within a group. You can, for example, copy the material number MATNR from the structure MCVBRP. As a result the sales for each material number will be updated in the statistic. To identify the relevant material in the credit memo as well, the material number MATNR needs to be reassigned to the target field, too.
- If you want to perform a settlement according to the customer who caused the sales, you can, for example, enter the sold-to party in the variable key (MCVBRK-KUNAG). In this case you should also choose the KUNAG for the target field. If you want to have the same customer as bill-to party in the credit memo, you can fill the field KUNRE from BRK-KUNAG in an additional line. ATTENTION Please make sure that the fields of the credit memo are filled in accordance with the key of the invoice mapping the sales; otherwise a partial settlement cannot be assigned to the proper key. If, for instance, you have the sold-to party in the variable key but enter only the bill-to party, the sold-to party in the credit memo may differ. The credit memo will then be posted for a deviating key. In this case it will no longer be possible to consider partial payments correctly for each key!
Requirements
Working with the extended rebate processing requires that the new rebate procedure is active, i.e. the info structure S136 has been activated.
Standard settings
Recommendation
The variable key of a payment should correspond to the key of the invoices mapping the sales. Therefore please make sure that the fields for the credit memo - i.e. the target fields - are filled in accordance with the variable key of the invoices mapping the sales. Otherwise it is not possible to assign partial payments to sales of specific keys. This may cause unwanted side-effects in particular for periodic settlements.
Activities
Further notes
As soon as data for an agreement type are updated in the rebate info structure S469, the structure must not change. Changes may cause incorrect settlements. That is why Customizing data are stored in a separate table during the first update. Then only the stored values are used to generate the variable key. Changes in Customizing no longer affect rebate processing.
If changes are still required, the statistical data of the rebate info structure S469 need to be set up with the initial values. In this context the separately stored Customizing data will be deleted and new Customizing settings will be considered in the update.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| BON_ENH_CSEQ | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20030409 |
| SAP Release Created in | 46C |
