General presentation

Objective of the application

Tool Leader + IT leader of the application: 

Usage information

History

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation









Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






Dataflow overview

Reporting documentation drive folder:

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


https://drive.google.com/drive/search?q=MPR_CHG5

pre query used


Exemple of dataflow overview :

BW OTC - Order Changes DataFlow


Functional and Technical rules on Workbench + Reporting

Rules & Explanations

The DSO DSO_DLV1 + DSO_DLV2 + DSO_DLV3 are used for EHS application only

See EHS SVT documentation in the wiki or in the link below :

https://drive.google.com/file/d/1UuzZGuQKAlhClQm9meh4_ZDD92PK5WQWFYu6zYHKPg8/view


Dataobject : DSO_CHG6 

Only one query

Query : BW_QRY_DSO_CHG6_0001 BW - Follow-up currency change on customer sales(Core Query)





Focus on the DSO_SD02 Sales Document Schedule Line => used for APO system in the past and now for Dynasys

More general doc : http://help.sap.com/saphelp_di471/helpdata/en/dd/55fb20545a11d1a7020000e829fd11/content.htm

Source 1 : 2LIS_02_SCL Purchasing Data (Schedule Line Level) this one is used on Purchase dataflow (SPRINT project)

Source 2 : 2LIS_11_VASCL  Sales Document Schedule Line


All about Sales Document (header / item / schedule )


Sales Order is a contract between a customer and sales organization for supplying goods or service to customer within a agreed time period. Data on  the sales order  screen is derived  from  Customer Master  Table and Material Master Table for a particular sales area.The sales area that accepts the inquiry is responsible for completing the contract. T-code for sales order is -

  1.  VA01- Create sales order.
  2.  VA02-Change sales order.
  3.  VA03-Display sales order.

To create sales order we need data at four levels-

1.Organization data :  Organization data is first screen of sales document which contains fields like Sales organization,distribution channel,division,Sales Office ,Sales Group etc.

2.Header data :   Sales order header contain many tab(sales,shipping,billing etc.). Header essentially contains information mostly from the Customer Master in the Transaction. We can click on header   button for sales header screen display.

Sales Header screen is displayed as below -

3. Item data :  This contains line item .Line item contain all information related to customer / material / quantity .

4 . Schedule line data :  For each line item their are schedule line items.This data describes  quantity and date. Select item  lines for item data and click on schedule line   buttons.

Click on schedule line  button AGAIN -

  Their are three views for schedule line  -

  • Sales : Delivery date / time / quantity.
  • Shipping: it contains shipping / delivery / route etc details.
  • Procurement : It contains plant / item / quantity details.

Dependencies with other applications

Purchase application, Dynasys + Qlickview Dashboard with all naming convention without beginning QV but with RBS in the technical name.

Data loadings

Info providers and objects loaded

Loading frequency

Average performance


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

Reporting

Queries End User Documentation


Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels