General presentation

Objective of the application

Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO

Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator

Usage information

How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site

History

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

Roles & Access

Roles and access

Two roles were created for OBAS. The first one is the application's role and the other one is the role menu.

Role CodeRole DescriptionExplanation
ZBI_RCS_SD_A01Application role for OBAS project / SD data / OrderbookRole for the application
ZR_RCS_CA_M49SD - Sales and DistributionRole menu for the application
   

Authorization objects

The authorization is done regarding the BFC GBU, the legal company and the sales office.

Authorization objectExplanation
CPFCTR1_2GBU
C_COMPCDELegal company
C_SAL_OFSales office

Order book

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Sales order book

Core rules

Order line status

To be invoiced date

To be issued date

Open order

Definitions

Open order without planned delivery
Open order with planned delivery

Shipped but not billed

Definition

Billed

Definition

Master data

Data flow

Data update

Reporting

Data selection

Core queries

Core workbooks

Purchase order (Transfers) order book

Core rules

Order line status

To be invoiced date

Open order

Definitions

Delivered quantity

Definition

Billed

Definition

Master data

Data flow

Data update

Reporting

Data selection

Core queries

Core workbooks

Historical data

Sales order

Sales documents types

Sales order

Delivery

Billing

Sales documents flows

Sales order

Schedule line

Delivery

Shipment

Billing

Master data

Data flow

Data update

Reporting

Data selection

Core queries

Core workbooks

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

 

Key FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Concepts and definitions

ATP DATES
AGENT COMMISSIONS
BILLED
BILLING GROUP
BILLING LINE
BLOCK
CLOSE ORDER
CO (CURRENCY ORIGIN)
COMMISSIONS
CONFIRMED QUANTITY
CONSOLIDATED RATE
CONSOLIDATION METHODE
CP (CURRENCY PROMPT)
CREDIT/DEBIT MEMO
CURRENCY CONVERSION
CUSTOMER
CUSTOMER GBR
CUSTOMER PICK-UP
CUSTOMER SALES VIEW
DEFERED BY ATP
DELIVERY LINE
DELIVERY TOLERANCE
DEPARTURE PLANT
DESTINATION PLANT
DISCOUNT & SURCHARGES
EXTRAPOLATION BY WORKING DAYS
FIRST CONFIRMED QUANTITY
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
PRO-FORMAT DOCUMENTS
PUQ (PROMPT UNIT QUANTITY)
PURCHASE ORDER LINE (TRANSFERS)
REBATES
REJECTED ORDER
REST TO BE DELIVERED
RESTATED BUSINESS AREA
RESTATED PARTNER BUSINESS AREA
ROUTE
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

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

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