General presentation
Objective of the application
The ship-pad report is based on "Order Book - To be Issued (SO + PO)", that includes Sales and Transfer orders.
The scope of the report are all open orders that haven’t been issued (Actual Goods Issue date empty).
Rejected Order lines and Order Lines with “rest to be delivered” below the Tolerance are EXCLUDED from the report.
Tool Leader + IT leader of the application:
Craig Wanamaker + Diogo Paiva
Usage information
History
In order to meet ship-pad requirements. several elements were incorporated into existing Order Book.
Roles & Access
Roles and access
Same role from Global Sales
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M49 | SD - Sales and Distribution | role menu for the application |
Authorization objects
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Dataflow overview
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
New Composite Provider CPSDAE03 based on HANA Calculation View CV_SD_AE_CPSDAE03
Initially joins DSOs below:
For Sales Order, the "rest to be delivered" (K_NONDEL) is stored, at delivery line level, in DBSDSO9D.
For Purchase Orders, it is calculated dynamically in the view accessing tables below:
DBSDSO66 - to get PO quantity / Confirmed quantity (by schedule line)
DBSDSO69 - to get Delivery quantity
New fields were added to DBSDSO9D and populated in Transformations below
Orders already shipped (DBSDSO56) are not relevant for Ship-pad. They are excluded in the query using filter “Actual GI date = blank”.
New recursive Transformation was created to populate “Passed Specs flag”.
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
New fields Aero - Sales Order
In WP1, new fields specific for Aero were added in VBAP (tab “Additional data B”)
They are then loaded as attributes in C_ITM_SD master data.
In the case of specs, which can be multiple for one order line (table ZWOCT435), they are first loaded into DSO ADPSDAE01 and then concatenated as attribute C_SPECLIS in C_ITM_SD.
New fields Aero - Purchase Order
In WP1, new fields specific for Aero were added in EKPO (tab "Aero Specific information")
They are then loaded as attributes in C_ITM_GS master data.
In the case of specs, which can be multiple for PO item, they are first loaded into DSO ADPSDAE03 and then concatenated as attribute C_SPECLIS in C_ITM_GS.
New loads into C_ITM_SD / C_ITM_GS
Sales Orders x Process Orders
Some columns from ship-pad report bring production planning information (like workcenter, parent batch).
The link between Sales Orders and Process Orders comes from table Z1C_PP_SD_LINK in WP1 and is stored in DSO ADPSDAE02.
One sales order can be linked with multiple process orders.
In ship-pad report, this will generate additional lines, but the key figures from the order line are then repeated in each line of the report.
Dependencies with other applications
Data loadings
Info providers and objects loaded
Loading frequency
Average performance
| Key Figure | Estimation |
|---|---|
| ~ 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
Workbooks:
Main queries
BW_QRY_CPSDAE03_0001 – Ship pad report
BW_QRY_CPSDAE03_0002 – Open Order – External
BW_QRY_CPSDAE03_0003 – Open Order – Internal
Last 2 queries include only Sales Order (filter on C_ITM_GS-C_SDCATEG = ‘SO’).
Main functionalities
Broadcast
Maintenance
Known bugs
Recurring procedure
Planned Evolution