Access Management

Data Flow

Overview

Sales order

This part of Global Sales is used to have the historical data (last 3 years) for:

• Sales orders
• Schedule lines
• Delivery
• Shipment
• Billing

Sales documents types

Sales order

All the sales documents types are in the historic. Regarding the sales document type, a sales order line can be in one of the categories below:

• Sales
• Return
• Consignment
• Credit/Debit memo

The categories are stored in the object C_DOCTYP2 with the attribute C_GRPDOC. The attribute is updated manually.

IMPORTANT:  This concept of categories isn't standard. It was created for Global Sales.

Delivery

All the delivery types are in the historic. Nothing is done to group the delivery type.

Billing

All the billing document types are in the historic. Regarding the billing document type, a billing line can be in one of the categories below:

• Sales
• Pro Format
• Inter-company

The categories are stored in the object C_BILLTYP with the attribute C_BILLCL. The attribute is updated manually.

IMPORTANT:  This concept of categories isn't standard. It was created for Global Sales. An exclusion is done between the propagation layer and the business to don't have the billing Pro-format..

Data flow

The data flow is based on the LSA method. The data visualization is done on the multiproviders:

• MVSDSO44 (MP: Global Sales) for the aggregated queries.
• MVSDSO45 (MP: Detail Jump Query) for the detailed queries.

Global Sales data layers:

• Propagation Layer
• Business Layer
• Reporting Layer
• Virtual Layer
• Master Data

See the data flow of the multiprovider MVSDSO44 (MP: Global Sales) :

See the data flow of the multiprovider MVSDSO45 (MP: Global Sales) :

Propagation layer

List of infoproviders used by the Historical data:

Technical point: We never use the propagation layer for reporting. No SIDs are generated in the propagation layer.

Business layer

List of infoproviders used by the Historical data:

Reporting layer

List of infoproviders used by the Historical data:

Virtual layer

List of infoproviders used by the Historical data:

PO's transfers

The data flow is based on the LSA method. The data visualization is done on the multiproviders MVSDSO42 (MP: Global PO (Global Sales)) and MVSDSO43 (MP: Detail PO Jump (Global Sales)).

Global Sales data layers:

• Propagation Layer
• Business Layer
• Reporting Layer
• Virtual Layer

See the data flow of the multiprovider MVSDSO42 (MP: Global PO (Global Sales)):

See the data flow of the multiprovider MVSDSO43 (MP: Detail PO Jump (Global Sales)):

Propagation layer

IMPORTANT: To build the PO's transfers order book, we use data coming from the propagation of SPRINT.

List of infoproviders used by the PO's transfers order book:

Business layer

List of infoproviders used by the PO's transfers order book:

Reporting layer

List of infoproviders used by the PO's transfers order book:

Virtual layer

List of infoproviders used by the Historical data PO's transfers:

Core rules

PO's transfers

Purchase order documents types

All the rules used in Global Sales were determined by SAP experts.

IMPORTANT:

Solvay:

• PO's types UB and NB, the vendor must be flagged as intra-group. Exception is done for purchase organization. The exception is done with the technical object C_POSD.

          It's implemented in the start routine of the transformation:DP_PUSL2 -> DBSDSO26;

        Consider only the records which exist in C_POSD with LOGSYS = DP_PUSL2.LOGSYS and C_PUR_ORG = DP_PUSL2.C_PUR_ORG   and  C_VENDID.C_FLGINT !=''

Rhodia:

• PO's types UB and NB, the purchase organization 3200 is used for the type UB. The purchase organization 3001 to 3008, 3200 and 3400 are used for the type NB.
  It's implemented in the start routine of the transformation:DP_PUSL1 -> DBSDSO66; Consider only the records which exist in C_POSD with LOGSYS = DP_PUSL1.LOGSYS and C_POSD = DP_PUSL1.C_BSART(Purchase Doc Type) and C_PUR_ORG = DP_PUSL1.C_PUR_ORG

Purchase order

Global Sales uses the data coming from SPRINT to have the PO's transfers order.

• DP_PUSL1(PO : Schedule Line (Rhodia))
• DP_PUSL2(PO : Schedule Line (Solvay))

Delivery

The deliveries are coming from the DSO DBSDSO29 "PO Global: Transfers orders delivery (Solvay)".

The deliveries are coming from the DSO DBSDSO69 "PO Global: Transfers orders delivery (Rhodia)".

Billing

The billing are coming from the DSO DBSDSO27 "PO: Transfers orders Invoices (Solvay)".

The billing are coming from the DSO DBSDSO67 "PO: Transfers orders Invoices (Rhodia)".

IMPORTANT:

• Transfers done with the PO type UB is always done between the same GBU.
• Transfers done with the PO type NB is always done between Solvay's entities.

Master data

The master data used, is the master data of SPRINT, with the object C_PO_ITM (Purchase Order Item). Please refer to SPRINT documentation for more detail.

Reporting

The reporting is based on Core workbooks based on Core queries.

The core workbooks give an aggregated view, to have information on the documents detail jumps are done.

IMPORTANTE: The core queries are not published on the role menu. Only the workbooks are published on the role menu, folder Historical data.

Sales order

The core queries are used to build the workbooks and to have the detail at the documents lines level (jumps).

PO's transfers

IMPORTANT:   The calendar Year/month corresponding to:

• the last requested GI date for the sales orders part
• the actual GI date for the sales deliveries part
• the billing document date for the billing part

Data loading

IMPORTANT: The same process chain is used to update the Sales order and the Historical sales data.

IMPORTANT: The same process chain is used to update the PO's (transfers) order book and the Historical PO's (transfers) data.

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)>