Develop a new reporting solution for Sales & Distribution data coming from SAP/ERP/PF1 with a first deliverable the ORDER BOOK REPORT (Sold & Pending).
Detail on: Sales Orders, Purchase Orders (transfers), Sales Order Lines, Schedule Lines,Deliveries, Invoices.
Innovation: Process Core Rules integrated to the Order Book Report, generating 2 views:
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
Two roles were created for OBAS. The first one is the application role and the other one is the role menu.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZBI_RCS_SD_A01 | Application role for OBAS project / SD data / Orderbook | Role for the application |
| ZR_RCS_CA_M49 | SD - Sales and Distribution | Role menu for the application |
The authorization is done regarding the BFC GBU, the legal company and the sales office.
| Authorization object | Explanation |
|---|---|
| CPFCTR1_2 | GBU |
| C_COMPCDE | Legal company |
| C_SAL_OF | Sales office |
Sales Order Book is a presentation in a detailed level of all sales orders placed in SAP/PF1 system, being possible to determine:
The sales order book is defined at most detailed level. That means at the schedule line level. The concept of line is very important to understand how the order book. Each sales document can generate an item, the combination of the document number / item number is a line.
To generate the sales order book the documents line below is used:
Document line generation:
Comment: OBAS doesn't use the shipment line. The mandatories informations are at the shipment header level.
All the rules used in OBAS were determined by SAP experts.
IMPORTANT:
It's because in PF1, an order line is with the status "C" (completed). When the deliveries regarding the total confirmed quantity of the order line is planned or issued .
The to be invoiced date is used to know when an order line will be billed. This concept is used in the order book for the Open order and the Shipped but not billed part.
Important: the to be invoiced date can be calculated only if the type of sales order will generate a delivery document. That means the credit/debit memo are not included in the Open order and the shipped but not billed part. The returns are not considered in the Open order and shipped but not billed part.
The to be invoiced date is calculated by use the more update document in the document flow.
Regarding the order line classification, the to be invoiced is calculated following the rules below:
WARNING: A shipment document can be created without the shipment dates. If this case appears, the shipment document will be ignored in the determination of the to invoiced date.
The to be issued date is used to know when an order line will be billed. This concept is used in the order book to be issued for the Open order and the Shipped but not billed part.
Important: like the to be invoiced date, the to be issued date can be calculated only if the type of sales ordert will generate a delivery document. That means the credit/debit memo are not included in the Open order and the shipped but not billed part. The returns are not considered in the Open order and shipped but not billed part.
The to be issued date is calculated by use the more update document in the document flow.
To calcul the to be issued date we use the rules with the hierarchy below:
WARNING: A shipment document can be created without the shipment dates. If this case appears, the shipment document will be ignored in the determination of the to issued date.
The rest to be delivered is the quantity which need to be delivered to the customer to complete the requested quantity. The rest to be delivered is defined at the schedule line level. It is used in the Open order part, to determine the to be invoiced/issued quantities and the values. The calculation is done following the rules below:
IMPORTANT: If the rest to be delivered is negatif, the quantity: rest to be delivered is forced to 0.
The notion of Not Invoiced (or not billed) is very importante to generate the order book. That will define the sales documents lines which are Open or Shipped not billed.
To know if a document line is invoiced or not (billed or not billed) 2 checks are done:
IMPORTANTE: An order line can be partially billed.
If a rest to be delivered exist for an order line. The order line is open.
Two cases:
This case appear when an order line was created, but no delivery is yet planned.
Example:
The order line 4268469/20 has no delivery created. This order line is at the beginning of the sales process.
This case appear when an order line was created, and delivery is planned.
Example:
The order line 4311472/20 has the delivery lines 87743333/10 and 87743333/900001 created.
The delivery is planned but the material is not yet issued. The order line 4311472/20 is open.
Order line which has a delivery line with an issued quantity but the issued quantity is not yet billed.
Example:
The order line 4357166/10 has the deliveries lines 70367763/10 and 70367763/900001 created.
The material was issued, no billing exist for the delivery. The order line 4357166/10 is shipped not billed.
An order line is billed, when a billing line is created with reference document:
Example:
The order line 4204405/10 has a billing document created in reference of the delivery line. The order line is billed.
List of mater data:
| Technical name | Description |
|---|---|
| C_ITM_SD | Sales order item |
C_ROUTE | Route |
C_TRMODE | Transportation mode |
| C_SHIPCD2 | Shippment condition |
IMPORTANT: The object C_ITM_SD is critical due to it use to generate the order book.
The data flow is based on the LSA method. The data visualization is done on the multiprovider MVSDSO01 (MP: Sales order book).
OBAS data layers:
The draw below represente the data flow of the multiprovider MVSDS01:
Click on the draw to enlarge.
IMPORTANT: The multiprovider MVSDSO01 (Sales Order Book) is also used by DYNASIS. The order book doesn't use data coming from DYNASIS.
List of infoproviders used by the Sales order book:
| DSO tech. name | DSO description | DTS tech. name | DTS description | Comments |
|---|---|---|---|---|
| DPSDSO02 | Sales Document Item Data (Solvay) | 2LIS_11_VAITM | Sales Document Item Data | OBAS |
DPSDSO04 | Sales Document Order Delivery (Solvay) | 2LIS_11_V_SSL | Sales Document Order Delivery | OBAS |
| DPSD001 | Deliveries (Solvay) | 2LIS_12_VCITM | Delivery Item Data | OBAS |
| DPSDSO07 | Billing Document Item Data (Solvay) | 2LIS_13_VDITM | Billing Document Item Data | OBAS |
| DPSDTR22 | TR Prop: Shipments & Deliveries (Solvay) | 2LIS_08TRTLP | Shipment: Delivery Item Data per Section | From TIERS |
| DPSDTR28 | TR Prop: Shipments & Deliveries Status 1-4 (Solvay) | DTS_BW_SHIP_SBS | Extract Shipment doc overall status 1 to 4 | From TIERS |
Technical point: We never use the propagation layer for reporting. No SIDs are generated in the propagation layer.
For more detail on the propagation layer, click on this LINK.
List of infoproviders used by the Sales order book:
| DSO tech. name | DSO description | source DSO tech. name | source DSO description |
|---|---|---|---|
| DBSDSO01 | SO: Not Invoiced (Solvay) | DPSDSO04 | Sales Document Order Delivery (Solvay) |
| BDSDSO11 | SO Global: Sales Document Item Data (Solvay) | DPSDSO02 | Sales Document Item Data (Solvay) |
| DBSDSO14 | SO Global: Deliveries (Solvay) | DPSD001 | Deliveries (Solvay) |
| DBSDSO06 | SO Global: Invoices (Solvay) | DPSDSO07 | Billing Document Item Data (Solvay) |
| DBSDSO18 | SO: OPEN ORDER W/O DLV DOC (Solvay) | DBSDSO01 | SO: Not Invoiced (Solvay) |
| DBSDSO17 | SO: OPEN ORDER WITH DLV DOC (Solvay) | DBSDSO01 | SO: Not Invoiced (Solvay) |
| DBSDSO16 | SO: SHIPPED NOT INVOICED (Solvay) | DBSDSO01 | SO: Not Invoiced (Solvay) |
DBSDSO09 |
SO global: Shipments status 1 to 7 (Solvay) | DPSDTR22 + DPSDTR28 | TR Prop: Shipments & Deliveries (Solvay) + TR Prop: Shipments & Deliveries Status 1-4 (Solvay) |
| DBSDSO10 | SO global: Deliveries and Shipment to the customer (Solvay) | DBSDSO09 | SO global: Shipments status 1 to 7 (Solvay) |
For more detail on the business layer, click on this LINK.
List of infoproviders used by the Sales order book:
| CUBE tech. name | CUBE description | source DSO tech. name | source DSO description | Comments |
|---|---|---|---|---|
CRSDSO02 |
SO Order Book: OPEN ORDER+SHIPPED NOT INVOICED (Solvay) | DBSDSO16 + DBSDSO17 + DBSDSO18 | SO: SHIPPED NOT INVOICED (Solvay) + SO: OPEN ORDER WITH DLV DOC (Solvay) + SO: OPEN ORDER W/O DLV DOC (Solvay) | |
| CRSDSO01 | SO Order Book: Current month Invoices (Solvay) | DBSDSO06 | SO Global: Invoices (Solvay) |
For more detail on the propagation layer, click on this LINK.
List of infoproviders used by the Sales order book:
| CUBE tech. name | CUBE description | source DSO tech. name | source DSO description | Comments |
|---|---|---|---|---|
MVSDSO01 |
MP: Sales order book | CRSDSO01 + CRSDSO02 + CRDYN12 + CRDYN11 | SO Order Book: Current month Invoices (Solvay) + SO Order Book: OPEN ORDER+SHIPPED NOT INVOICED (Solvay) + From SO - Devileries and Invoices + DYN - Reporting | OBAS
OBAS
DYNASIS
DYNASIS |
IMPORTANT: In the multiprovider MVSDSO01, they are data coming from DYNASIS (CRDYN11 and CRDYN12). These data are not used in the Order book.
For more detail on the propagation layer, click on this LINK.
List of master data used to generate the Sales order book:
| Object tech. name | Object description | source tech. name | source description | Comments |
|---|---|---|---|---|
| C_DOCNUMB | Sales document (with System ID) | DPFIAR06 | FIAR: Credit blocked by Credit Reasons - Solvay | To have the flag credit block (Historical and dynamique) |
C_ITM_SD
|
Sales document item | DBSDSO08 + DBSDSO11 + DBSDSO12 | SO Global: Sales Document Schedule Line (Solvay) + SO Global: Sales Document Item Data (Solvay) + SO global: Sales Document Item Status (Solvay) |
Is the more critical object. Used to generate the data flow. |
C_SHIPNU2 |
Shipment Number (Core) | DPSDTR21 + DPSDTR28 | TR Prop: Shipments header (Solvay) + TR Prop: Shipments & Deliveries Status 1-4 (Solvay) |
For more detail please see the TIERS documentation |
For more detail on the master data layer, click on this LINK.
IMPORTANT: The same process chain is used to update the Sales order and the Historical sales data.
The processes chains below are used to update the multiprovider MVSDSO01 (Sales order book):
SD - Main Process Chain - UPTDATE DATA - (PC_SD_MAIN)
SD - Propagation Update (PC_SD_PROPAG)
SD - Business Layer (Solvay) (PC_SD_BUSINESS_LAYER)
OBAS: Reporting layer (PC_OBAS_REPORTING)
For more detail click on this LINK.
For detail on the processes chains of the master data, please refer to Concepts and Definitions
IMPORTANT: The sales order book is generated every day from scratch. No historic is done for the sales order book.
The data is updated every day. The process chain start after the end of TIERS update.
General performance:
Detailed performance:
The reporting is based on Core workbooks based on Core queries.
The core workbooks give an aggregated view (SNAPSHOT), 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 Order Book.
Data selections are done at the query level:
For more detail on the selections, click on this LINK.
The core queries are used to build the workbooks and to have the detail at the documents lines level (jumps).
The core query Order Book: SNAPSHOTS To be Invoiced (BW_QRY_MVSDSO01_SD004) is used to build the workbooks:
IMPORTANT: The diferences between the order book business view To Be Invoiced (consolidated view) and the order book business view To Be Invoiced , are only on the keys figures definitions. The same keys figures are used as the Order book business view, but the percentage of Solvay in a legal company is used to calculate the consolidated keys figures. For more details, click on this LINK.
Filters:
Comment: In yellow the characteristics where a filter is applied. The others characteristics are prompts.
Free Characteristics:
Rows:
Columns (Key figures):
For more detail please open the query on the query designer.
The core query Order Book: SNAPSHOTS To be Issued(BW_QRY_MVSDSO01_SD003) is used to build the workbook:
Filters:
Comment: In yellow the characteristics where a filter is applied. The others characteristics are prompts.
Free characteristics:
Rows:
Columns (Keys figures):
For more detail please open the query on the query designer.
The core query BW - Order book: Open Order (Core) (BW_QRY_MVSDSO01_SD006) is used to have the detail of the Open Orders (Jump query) in the workbooks:
Filters:
Free Characteristics:
Rows:
Columns (Keys figures):
For more details, please open the query BW - Order book: Open Order (Core) (BW_QRY_MVSDSO01_SD006) in the query designer.
The core query BW - Order book: Open Order To be issued (Core) (BW_QRY_MVSDSO01_SD001) is used to have the detail of the Open Orders (Jump query) in the workbooks:
Filters:
Free characteristics:
Rows:
Columns (Keys figures):
For more details, please open the query BW - Order book: Open Order To be issued (Core) (BW_QRY_MVSDSO01_SD001) in the query designer.
The core query BW - Order book: Shipped not billed (Core) (BW_QRY_MVSDSO01_SD007) is used to have the detail of the Shipped not billed (Jump query) in the workbooks:
Filters:
Free characteristics:
Rows:
For more details, please open the query BW - Order book: Shipped not billed (Core) (BW_QRY_MVSDSO01_SD007) in the query designer.
The core query BW - Order book: Shipped not billed To be issued (Core) (BW_QRY_MVSDSO01_SD002) is used to have the detail of the Shipped not billed (Jump query) in the workbook:
Filters:
Free characteristics:
Rows:
Columns (Keys figures):
For more details, please open the query BW - Order book: Shipped not billed To be issued (Core) (BW_QRY_MVSDSO01_SD002) in the query designer.
The core query BW - Order book: Invoiced Current Month (Core) (BW_QRY_MVSDSO01_SD008) is used to have the detail of the billed documents lines (Jump query) in the workbooks:
IMPORTANT: A selection is done on the cube SO Order Book: Current month Invoices (Solvay) (CRSDSO01) to keep only the billing documents with a billing date (Month/Year) igual to the current month.
Filters:
Free characteristics:
Rows:
Columns (Keys figures):
For more details, please open the query BW - Order book: Invoiced Current Month (Core) (BW_QRY_MVSDSO01_SD008) in the query designer.
Three core workbooks are available on the folder Order book for the sales orders. Each workbooks are based on one query.
The workbook Order book business view To Be Invoiced (BW_WBK_SD_0001) is base on the core query: Order Book: SNAPSHOTS To be Invoiced (BW_QRY_MVSDSO01_SD004) and it contains the tabs below:
IMPORTANT:
For more detail please open the workbook in Analysis (tab read-me and glossary).
The workbook Order book business view To Be Invoiced (conso) (BW_WBK_SD_0002) is base on the core query: Order Book: SNAPSHOTS To be Invoiced (BW_QRY_MVSDSO01_SD004) and it contains the tabs below:
IMPORTANT:
WARNING: the jump query will provide the detail not consolidated. To have the detail consolidated, the user need to had manually the keys figures consolidated. It's to reduce the number of core queries. The order book business view to be invoiced and the order book business view to be invoiced consolidated are using the same queries. By default the keys figures consolidated are hidden on the queries.
This workbook is base on the core query BW - Order book: Snapshots To be issued (Core) (BW_QRY_MVSDSO01_SD003) and it contains the tabs below:
For more detail please open the workbook in Analysis (tab read-me and glossary).
COMMENTS: Please note that for the sales order book. The shipped not billed and the billed parts are displayed for the current month.
All the rules used in OBAS were determined by SAP experts.
IMPORTANT:
The to be invoiced date is calculated following the rules below:
The rest to be delivered is the quantity which need to be delivered to the customer to complete the requested quantity. The rest to be delivered is defined at the purchase order line level. It is used in the Open order part, to determine the to be invoiced quantities and the values. The calculation is done following the rules below:
IMPORTANT: If the rest to be delivered is negative, the quantity: rest to be delivered is forced to 0.
A PO transfers order is open if:
Example:
The PO's line 4512394035/10 is closed because the indicator Final Delivery is flagged.
Is the quantity issued (the delivery line has an actual GI date).
Example:
The delivery line 87422928/10 which contain the bacth 900001 is issued. The quantity was delivered.
A PO transfers order line is billed, when a billing line is created with reference document:
IMPORTANT: On the transfers process, just purchase documents type NB will generate billing documents.
Example:
The PO 4511943102 has a billing document created in reference of the delivery document 86095478. The PO's transfers is billed.
The data flow is based on the LSA method. The data visualization is done on the multiprovider MVSDSO07 (MP: Transfers order book).
OBAS data layers:
The draw below represente the data flow of the multiprovider MVSDS07:
Click on the draw to enlarge.
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:
| DSO tech. name | DSO description | DTS tech. name | DTS description | Comments |
|---|---|---|---|---|
| DPSDSO02 | Sales Document Item Data (Solvay) | 2LIS_11_VAITM | Sales Document Item Data | OBAS |
| DPSD001 | Deliveries (Solvay) | 2LIS_12_VCITM | Delivery Item Data | OBAS |
| DPSDSO07 | Billing Document Item Data (Solvay) | 2LIS_13_VDITM | Billing Document Item Data | OBAS |
| DP_PUSL2 | PO: Schedule line (Solvay) | 2LIS_02_SCL | Purchasing data (schedule line level) | SPRINT |
| DP_PUHD2 | PO : Historical Data (Solvay) | DTS_BW_EKBE | PO Historical Data | SPRINT |
For more detail on the propagation layer click on this LINK.
List of infoproviders used by the PO's transfers order book:
| DSO tech. name | DSO description | source DSO tech. name | source DSO description |
|---|---|---|---|
| DBSDSO25 | PO : Transfers Historical Data (Solvay) | DP_PUHD2 | PO : Historical Data (Solvay) |
| DBSDSO26 | PO: Transfers orders sched. line (Solvay) | DP_PUSL2 | PO: Schedule line (Solvay) |
| DBSDSO28 | PO: OPEN Transfers orders (Solvay) | DBSDSO26 | PO: Transfers orders sched. line (Solvay) |
| DBSDSO27 | PO: Transfers orders Invoices (Solvay) | DPSDSO07 | Billing Document Item Data (Solvay) |
| DBSDSO29 | PO Global: Transfers orders delivery (Solvay) | DPSD001 | Deliveries (Solvay) |
For more detail on the business layer click on this LINK.
List of infoproviders used by the PO's transfers order book:
| CUBE tech. name | CUBE description | source CUBE tech. name | source CUBE description |
|---|---|---|---|
| CRSDSO12 | PO Order Book: OPEN ORDER (Solvay) | DBSDSO28 | PO: OPEN Transfers orders (Solvay) |
| CRSDSO11 | PO Order Book: Current month Invoices (Solvay) | DBSDSO27 | PO: Transfers orders Invoices (Solvay) |
| CRSDSO04 | PO Global: Deliveries aggregated (Solvay) | DBSDSO29 | PO Global: Transfers orders delivery (Solvay) |
For more detail on the reporting layer click on this LINK.
List of infoproviders used by the PO's transfers order book:
| CUBE tech. name | CUBE description | source CUBE tech. name | source CUBE description |
|---|---|---|---|
MVSDSO07 |
MP: Transfers order book | CRSDSO04 + CRSDSO11 + CRSDSO12 | PO Global: Deliveries aggregated (Solvay) + PO Order Book: Current month Invoices (Solvay) + PO Order Book: OPEN ORDER (Solvay) |
For more detail on the vitual layer click on this LINK.
Just the master data of C_PO_ITM is used. Please refer to SPRINT documentation for more informations.
IMPORTANT: The same process chain is used to update the PO's (transfers) order book and the Historical PO's (transfers) data.
The processes chains below are used to update the multiprovider MVSDSO07 (MP: Transfers order book):
OBAS: Transfers Orders Main chain (PC_OBAS_TRANSFERS_MAIN)
OBAS: Business Layer Transfers Orders (Solvay) (PC_OBAS_TRANSFERS)
OBAS: Reporting Layer Transfers Orders (PC_OBAS_TRANSFERS_ODB)
The data is updated every day. The process chain start after the end of SPRINT update.
General performance
Detailed performance
This workbook is base on the core query Order Book: SNAPSHOTS To be Invoiced (BW_QRY_MVSDSO01_SD004) and it contains the tabs below:
The data is updated every day. The process chain start runed after the end of TIERS update.
The data is updated every day. The process chain start runed after the end of TIERS update.
Available-to-promise (ATP) is a business function that provides a response to customer order enquiries, based on resource availability. It generates available quantities of the requested product, and delivery due dates.
An agent commission is a partner of Solvay. This partner receive a commission for sales. This commission is calculated via a specifics documents types which are generate by a billing document of a sales order. The agent commission is based on two keys figures. The commission base and the commission rate. The value of the commission received by the agent is igual to: the commission rate X the commission base. For more detail click on this LINK.
BILLED:
BILLING GROUP
BILLING LINE
The sales process can be stop by block(s) on the sales document(s) or document(s) line(s).
If a block exists the sales process is stopped where the block is created (at the document or document level).
Types of blocks:
For more informations click on this LINK.
An order is close if the rest to be delivered = 0.
it's the currency of the legal company responsible for the order line.
Is a part of the gross sales, it is determined during the pricing. This information provide from the billing document and it is retreived with the subtotal 4.
Is the quantity confirmed by the system. In other terms, what quantity the supply chain is able to deliver regarding the customer's requested delivery date. This quantity is defined at the schedule line level on the system. In BW the confirmed quantity is available on the data base, at the schedule line and at the sales
Is the percentage of Solvay in a legal company.
IMPORTANTE: The consolidated rate is maintained in the master data of the object C_COMPCDE (Company code). For more detail click on this LINK.
It is an financial information to know how the result of a legal company is counted in the overall group result. This characteristic is used to do the exclusion of sold entities.
CP (CURRENCY PROMPT)
CREDIT/DEBIT MEMO
CURRENCY CONVERSION
CUSTOMER
CUSTOMER GBR
CUSTOMER PICK-UP
CUSTOMER SALES VIEW
DELAYED BY ATP
A delivery line is the combination of a delivery document and an item.
Example:
70367763/10 and 70367763/900001 are deliveries lines. The important delivery line is 70367763/900001 because is the quantity isn't null.
IMPORTANT: The delivery line with the "zero" quantity must to be in the data base (DSO DBSDSO14 (Global sales deliveries)). It because billing lines can be created regarding this delivery line.
DELIVERY TOLERANCE
The concept of departure plant is used for PO's transfers . The departure plant is the plant where the product is sent.
The concept of destination plant is used for PO's transfers part. The destination is the plant where the product is delivered.
DISCOUNT & SURCHARGES
An extrapolation by working days can be applied on the different keys figures. The objective is to be able in a commercial to know the number of working days for the curent month and the number of working days passes until the last update date> The determination of the working days is done at the country's SAP standard calendar calendar.
Applications: In the sales follow-up's workbook, an extrapolation is done on the monthly delivery quantity. The references dates (number of working days for the current month and number of working days passed until the last update) are based on the SAP standard calendar of the plant's country.
IMPORTANT: The object C_TECHWD is calculated every day. If for a country code a SAP standard calendar exist. For more detail click on this LINK.
The first confirmed quantity is: the first quantity, confirmed for an order line, received in BW during an update.
IMPORTANTE: This quantity is avaible on the master data C_ITM_SD (Sales document item). For more detail click on this LINK.
FIRST CUSTOMER GI DATE
FIRST REQUESTED DATE
FIRST REQUESTED QUANTITY
GBU SHIP-TO ZONES
GROSS SALES
INTRA GBU
INTRA GROUP
IV DOCUMENTS
JUMP QUERY
LAST CONFIRMED QUANTITY
LAST CUSTOMER GI DATE
LAST REQUESTED DATE
NET SALES
OBAS AUTHORIZATIONS
OBAS CURRENT MONTH
OPEN ORDER
ORDER BOOK RULES
ORDER LINE
PRICING CONDITION
This kind of billing document is not counted in the sales result by the business. The proformat document is mandatory to be aligned with specifics countries's laws.
SCREAN SHOT
PUQ (PROMPT UNIT QUANTITY)
PURCHASE ORDER LINE (TRANSFERS)
REBATES
REJECTED ORDER
REST TO BE DELIVERED
RESTATED BUSINESS AREA
RESTATED PARTNER BUSINESS AREA
ROUTE
A scheduled line is the more detailed level in a sales order. By default each sales order line has only one scheduled line. If the business function ATP is activated for the order line. More than one scheduled line line can be generated.
SALES REPRESENTATIVE
SHIPMENT TO THE END CUSTOMER
SHIPPED BUT NOT BILLED
SNAPSHOT
TAXES
TO BE INVOICED
TO BE ISSUED
TRANSFERS ORDER
TRANSITE TIME
TRANSPORTATION MODE
UNIT CONVERSION
RETURN
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016
Detail: Schedule line
| Snapshot by BA and Ship to zone |
For more detail on the business layer click on this LINK.