Access Management
|
List of authorization objects mandatory for the application.
WARNING: For the PO part the notion of sales offices doesn't exist. The restriction in sales offices will not be considered for the reports PO and PO+SO. |
Data flow
Overview
Data Admin - Customer
This workbook works directly with Customer's Master-Data, whether or not the customer has sales.
It is possible to control the GBR(*) customer Corporate group, even if the customer still has no sales in SAP. This report works directly with master data and for that reason the GBU can't be used in prompts (GBU defined only when the customer has sales).
Data Admin - Customer Group
This report retrieves all customers' groups (Corporate and GBU), for customers with sales in SAP. It is possible to be refreshed by GBU.
Data Admin - End Use
This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not).
The axis are:
- CORPORATE END USE
- GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)
Both are available in the BW WBP reports and in the CRM Analytics.
Tabs in the report:
- END USE and SALES
- END USE link
- END USE axis
- Application
- Market
- Segment
For the Billing date we suggest to use always 1 year period.
For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).
Data Admin - Material not converted
It’s not possible to convert sales unit into prompted quantity unit (PUQ) when that conversion don't exist in SAP.
After choosing the PUQ the report retrieves all materials that are not converted in that unit.
Data flow
Please see the data flow of the multiprovider MVSDAD01(MP: Data Admin (Global Sales) - with GBU) generated from Performer Suite.
Please see the data flow of the multiprovider MVSDAD02(MP: Data Admin (Global Sales) - without GBU) generated from Performer Suite.
Please see the data flow of the multiprovider MVSDSO44(MP: Global Sales (Global Sales)) generated from Performer Suite.
Please see the data flow of the multiprovider CPSDSO54(MP: Order book, Forecast & historical (PO & SO)) generated from Performer Suite.
Reporting
Workbook | Query | ||
|---|---|---|---|
| Data Admin - Customer Corporate Group | BW_WBK_SD_CPSDSO54_0001 | Customer Corporate Groups | BW_QRY_CPSDSO54_0009 |
| Data Admin - Customer Group | BW_WBK_SD_ADM_0002 | GBR - Corporate Group (core query) | BW_QRY_MVSDAD02_0009 |
| GBR - GBU Customer Group (core query) | BW_QRY_MVSDAD01_0008 | ||
| Historical Data: Sales Orders (Core query) | BW_QRY_MVSDSO44_SD0002 | ||
| Data Admin - Customer Master Data | BW_WBK_MVSDAD02_0005 | GBR - Customer Master data (core query) | BW_QRY_MVSDAD02_0005 |
| Data Admin - Material Master Data | BW_WBK_MVSDAD02_0006 | GBR - Material Master Data (core query) | BW_QRY_MVSDAD02_0006 |
| Data Admin - End Use | BW_WBK_SD_ADM_0001 | GBR - End Use Link (core query) | BW_QRY_MVSDAD01_0001 |
| GBR - End Use Axis (core query) | BW_QRY_MVSDAD01_0002 | ||
| BW - GBR - End Use Ship to Link (core query) | BW_QRY_MVSDAD01_0010 | ||
| Historical Data: Sales Orders (Core query) | BW_QRY_MVSDSO44_SD0002 | ||
| Data Admin - Material not Converted | BW_WBK_MVSDSO44_SD0009 | Data Admin: Material not converted (Core query) | BW_QRY_MVSDSO44_SD0009 |
| Data Admin - Ship-to KA | BW_WBK_MVSDSO44_SD0002_ADMIN | Historical Data: Sales Orders (Core query) | BW_QRY_MVSDSO44_SD0002 |
Data loading
| Main Process Chain | Final Info Provider | Frequency | Start Time | Duration |
|---|---|---|---|---|
| PC_GLOBAL_SALES_MAIN | CRSDSO41, 42... | Daily | ~1:30am CET | ~3.5h |
| PC_SD_MAIN | CRSDSO01, 02... | Daily | ~2:00am CET | ~1h |
| PC_GL_SALES_MAIN_PO | CRSDSO51, 52... | Daily | ~6:00am CET | ~1h |
| PC_OBAS_TRANSFERS_MAIN | CRSDSO11, 12... | Daily | ~6:00am CET | ~0.5h |
Data Quality Controls
Data comes from SAP system. To compare data between BW and sources systems, check propagation layers.
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticality, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>