Provide an overview of the app (e.g Domain, key processes, purpose of the app, etc)
Describe the key User profiles that exist for the application.
General role/Viewer role:
Approver role:
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | dd.mm.yyyy | Azadeh Nasiri | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
3.0 Application Feature Overview
Similar to order book, Historical data reports included in the global sales folder in BW are categorized in three main folders as below.
1) PO folder
Related to Purchase Orders (transfers): it is about moving of orders from one plant to another, mainly called stock transfers. There are two types:
a) internal that involves moving orders from one plant to another within the same company (UB document in SAP).
b) intercompany that involves moving orders from one plant to another, but in this case, the plants belong to different companies under the Solvay umbrella (NB document in SAP).
| Detailed | Technical name | ||
|---|---|---|---|
PO → Sales orders | ✓ | Historical Data: PO's transfer deliveries (Detailed) | BE_WBK_MVSDSO43_SD001 |
| ✓ | Historical Data: PO's transfer invoices (Detailed) | BE_WBK_MVSDSO43_SD003 | |
| ✓ | Historical Data: PO's transfer orders (Detailed) | BE_WBK_MVSDSO43_SD002 | |
| × | Historical Data: PO's transfer deliveries | BE_WBK_MVSDSO42_SD001 | |
| × | Historical Data: PO's transfer invoices | BE_WBK_MVSDSO42_SD003 | |
| × | Historical Data: PO's transfer orders | BE_WBK_MVSDSO42_SD002 |
2) SO folder
Related to Sales Orders: it is about sales order documents placed in SAP/PF1 system. These reports include sales orders which are Invoiced within the reporting period, Open (planned to be invoiced by the end of reporting period), Shipped but not yet billed (this includes items that have left as planned and are on the way to the customer; the invoicing timing may vary depending on the agreed incoterms).
| Detailed | Technical name | Type | ||
|---|---|---|---|---|
SO→ Sales orders | ✓ | Order Book: PO - Invoiced (Current Month) | BE_WBK_MVSDSO47_003 | Invoiced |
| ✓ | Order Book: PO - To be Issued (Open Order) | BE_WBK_MVSDSO47_002 | To be Issued | |
| × | Order Book (PO): To be Issued (Snapshot) | BE_WBK_MVSDSO47_001 | To be Issued |
3) PO + SO (includes both)
For more details about sales order and purchase orders (transfers), refers to Functional Documentation- Orderbook
| Detailed | Technical name | Type | ||
|---|---|---|---|---|
| SO+PO | ✓ | Order Book (SO+PO): To be Issued (Open Order) | BE_WBK_MVSDSO49_SD002 | To be Issued |
| ✓ | Order Book (SO+PO): To be Issued (Shipped not Billed) | BE_WBK_MVSDSO49_SD003 | To be Issued | |
| × | Order Book (SO+PO): To be Issued (Snapshot) | BE_WBK_MVSDSO49_SD001 | To be Issued |
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Aggregated reports | ||||
| Detailed reports | ||||
4.0 Functional Specification
4.1 General Data/Calculations
4.2 Process Detail
Historical data in the global sales folder of BW include more than 40 workbooks that provide overview on sales orders and purchased orders at detailed as well as aggregated level. The reports cover historical data over the last 3 years generated in SAP (Current Year + 2 Previous Years)
There are both aggregated and detailed categories of reports that draw from a single source of data from BW, providing similar insights but at different levels of granularity.
The detailed reports provide the finest level of granularity, offering in-depth information on sales orders, order lines, and even schedule lines. Conversely, the aggregated reports take a different approach by summarizing data based on regions or other factors, without going into transactional-level details.
Both type of reports are based on the same prompt BW. It's important to clarify that the month in the report corresponds to the month of the document's creation date, which is indicated in the title of the reports. For example, when a user opens a report on 'Sales Order Invoiced' and specifies 'OCT' in the prompt, the report includes sales orders for which the invoice documents have been created in October.
Manually priced sales orders:
It was created initially for technology solutions. Currently, Novecare is also using it.
In a perfect process, there is a flow where there is a need to load the price in advance from SAP but each GBU might mange it differently. Basicaly, it says that to sell a product to this customer, there is a negotiotion with the customer customer with validity period.
The objective of manual pricing report is to determine the ratio of manually priced sales orders (invoiced orders) and sales orders that have been priced with automatic (system price). These results give the overview of pricing approach each business takes.
This report can also be used as a tool to do various analysis regarding how frequently each customer/product record is used in sales orders with manual price and then escalate this information to appointed customer service representative and sales account manager to agree/clarify whether price should or should not be added in the system as customer special price.
This report gives access to extract data in mass and see those cases where pricing data can be updated to avoid manual pricing in sales orders in the future.
4.2.1. Report/Process Definition
General rules on all reports:
- For billings without goods movement the quantity is forced to zero (WP1).
IMPORTANT: Rule not applied in PF1
- Filter objects
Example: Some Material Types (services and packaging) are excluded from Order book, but not from Historical Data. These materials will never be converted to weight units of measure (TO, KG, LB,...). If you wish to remove those Material types (PF1/Z703, WP1/ZDIE, WP1/ZVER) you have 2 options:
Example: Some Material Types (services and packaging) are excluded from Order book, but not from Historical Data. These materials will never be converted to weight units of measure (TO, KG, LB,...). If you wish to remove those Material types (PF1/Z703, WP1/ZDIE, WP1/ZVER) you have 2 options:
From Aggregated to Detailed Queries
Invoices vs. Transport cost (SO/PO)
Exchange rate method
Document type | Exchange rate |
Sales Order | Exchange rate from the day the sales document was created |
Open Order | Current Month: average monthly exchange rate M+1, M+2, M>2: forecasted exchange rate defined in BFC |
Invoiced values | Exchange rate from the day the billing document was created |
Order/Invoiced values in Reference Currency (CR) | The rate coming from the ERP: Based on the billing date for the invoiced value Based on the sales item creation date for order line value |
INDEXES | |
| PUQ | Unit prompt quantity. It is the unit quantity chosen when the report is refreshed. Can be: KG, VKG, TO... |
| CP | Prompt Currency. It is the currency chosen when the report is refreshed. Can be USD, EUR, BRL... |
| CO | Order Currency. It is the currency which the sales order was placed. |
| CR | Reference Currency. It is the currency of the legal company responsible for the sales. |
4.2.2. KPI's/Calculations/Indicators
Key figures for manual pricing
| Manual Pricing: Percentage of items with manual pricing | ||
| TOTAL of billing item: Total of billing items in the perimeter | ||
| ASP Gross Sales: Average Sales Price Gross Sales = Invoiced Gross Sales / Invoiced QTY | ||
| Credit memo: Credit memo(s) issued to the customer referring to previously invoiced order | ||
| Debit memo: Debit memo(s) issued to the customer referring to previously invoiced order | ||
| ASP Net Sales: Average Sales Price Net Sales = Invoiced Net Sales / Invoiced QTY |