Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning⤷
RS_BCT_RETAIL_MAP (Package) BW: Content MAP
IMG Activity
| ID | BW_BCT_RT_FCAL | Determine Factory Calendar for Location Dimensions |
| Transaction Code | S_B72_29000009 | (empty) |
| Created on | 20050315 | |
| Customizing Attributes | BW_BCT_RT_FCAL | Determine Factory Calendar for Location Dimensions |
| Customizing Activity | BW_BCT_RT_FCAL | Determine Factory Calendar for Location Dimensions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MAP/M_FACTCAL |
Use
This Business Add-In (BAdI) is used in the component BW-BCT-PLA-RMP ("Retail Merchandise Planning").
Using this BAdI, you can assign a factory calendar to the relevant value of a location dimension. You can do this for any number of location dimensions.
In the aggregated long-term forecast for the Retail Merchandise Planning, you can use influencing factors of the type "Number of sales days". To determine the values of this influencing factor, the system needs to know on which days the points of sale are open or closed. It uses the factory calendar to obtain this information. Depending on the application, this information can be required at different levels.
If the forecast level contains sites in the form of stores, shops, or department stores (InfoObject 0PLANT), the system can determine the associated factory calendar automatically by evaluating the "Factory Calendar" attribute of the InfoObject 0PLANT.
In other cases, this is not possible.
For example, it is possible that the forecast is carried out only at region (0REGION) level. In this case, the region needs to be assigned to the factory calendar. This information is not available in the system.
The implementation of this BAdI is obligatory if the following conditions are fulfilled:
- You use an influencing factor of the type "Number of sales days" in the forecast.
- A location dimension is assigned to this influencing factor.
- The location dimension is not the same as the dimension:
- "Shop" (0PLANT_SHOP)
- "Store" (0PLANT_STORE)
- "Department store" (0PLANT_DSTORE)
The point in time when the individual methods of this BAdI are called is described in the documentation for the methods.
Requirements
An implementation is always carried out for a list of event dimensions, which serve as a filter value for the implementations. Before you can implement the BAdI, you must have created the event dimension that is relevant for the BAdI in Customizing.
Standard settings
The BAdI is filter-dependent and cannot be implemented more than once. That is, there can be only one active implementation for a filter value. If there is no active customer implementation, no SAP default implementation is carried out.
SAP delivers active implementations for the following location dimensions:
- Dimension shop (0PLANT_SHOP)
- Dimension store (0PLANT_STORE)
- Dimension department store (0PLANT_DSTORE)
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
You can use the implementation supplied by SAP (/MAP/M_FACTCAL_PLANT) as an example for your own location dimension.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| 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 | 20050315 |
| SAP Release Created in | 702 |
