Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-ISR-RSL (Application Component) Retail Stock Ledger⤷
RS_AA_WRMA (Package) Analytical Application RMA - Retail
IMG Activity
| ID | WRMA_SHRKP_ALIGN_PER | BAdI: Align planned shrinkage in periods of different calendars |
| Transaction Code | S_BH6_02000013 | (empty) |
| Created on | 20110315 | |
| Customizing Attributes | WRMA_SRHKP_ALIGN_PER | BAdI: Align planned shrinkage in periods of different calendars |
| Customizing Activity | WRMA_SRHKP_ALIGN_PER | BAdI: Align planned shrinkage in periods of different calendars |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WRMA_SHRKP_ALIGN_PERIODS |
Use
You can use this Business Add-In (BAdI) to align the total amount of the planned shrinkage for the weeks of a particular month to the planned shrinkage calculated for this month under certain conditions (detailed below). This means that rounding differences between calculation on week level and month level are avoided.
Requirements
It is assumed that the Retail Method of Accounting (RMA) is calculated for the fiscal year variant of the company code (generally the month) also at least for an alternative fiscal year variant (generally the week). This BAdI is implemented to avoid rounding differences when calculating the week.
We recommend that you implement this BAdI only, if the ending inventory at the end of the last week of the month is, apart from rounding differences, the same as the ending inventory of the month. This has to be ensured by the RMA calculation schema. Note that this is not the case with the calculation schema that is part of the standard Customizing. A minimum requirement to fulfill this condition is the calculation on a year-to-date basis.
Additionally, every month must be exactly covered by a specific number of weeks. This means that the month must end exactly on the last day of one of the weeks. The retail calendar, in which every month comprises of four or five weeks, fulfills this requirement, whereas the Gregorian calendar does not. The sample implementation of the BAdI checks if this condition is fulfilled.
We also highly recommend that the recasting periods for the monthly and weekly calculation are of the same length. This means that the beginning of the first posting period and the end of the last posting period within the recasting period match. The sample implementation does not check this condition, but unless the condition is fulfilled, reclassifications by monthly or weekly calculations are generally evaluated differently, causing different ending inventories. At this point, clearing the rounding differences no longer makes sense.
Note that this BAdI is only called for the Retail part of the planned shrinkage. Usually, no separate cost value is required for planned shrinkage.
Standard settings
There is no default clearing of rounding differences between the calculation of months and weeks since the standard calculation schemas do not provide for the synchronization of the ending inventories across different calendars.
Activities
If you wish to clear rounding differences across different calendars, use the Implementation Guide to create an implementation of this BAdI. This will allow you to copy the delivered sample implementation.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20110315 |
| SAP Release Created in | 706 |
