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 (without Actual Goods Issue date).
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
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
In order to meet ship-pad requirements. several elements were incorporated into existing Order Book.
Same role from Global Sales
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M49 | SD - Sales and Distribution | role menu for the application |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
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”.
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.
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.
C_ITM_GS is the master data used in ship-pad report because it contains both Sales Order and Purchase Orders.
Data that comes from Sales Order item (VBAP) goes first to C_ITM_SD and then to C_ITM_GS.
Data that comes from Purchase Order item (EKPO) goes directly to C_ITM_GS.
(Objects in yellow were created during Solstice project)
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.
New attribute C_PASSPEC was added to C_BATCH2 master data and stores the passed specs (concatenated) from the batch.
Then the spec list from order line is compared against this batch atribute to generate “Passed specs flag (Y/N)” in ship-pad report.
Passed Specs (batch) is calculated at batch level comparing the spec list from order line with the passed specs from batch.
So you can have different values (Y or N) by batch, for the same order line, as in example below
This is calculated in Transformation DBSDSO57 -> DBSDSO9D.
Passed Specs (order) is an overall flag by order line.
If any of “passed specs (batch) is “N”, then “passed specs (order) = ‘N’.
This is calculated in Recursive Transformation into DBSDSO9D.
For one-time customers (VBPA-XCPDK = ‘X’), same customer code can have different names, stored at sales order level.
New DSO AASDAE03R was created to store one-time customer name at order level. It's used as a lookup when loading data into DBSDSO9D.
If customer is found in this DSO, get its name from here, else get it from customer master data.
It’s populated in DBSDSO9D via lookup in DP_GTS92 with material + following filters:
EU ECCN
Legal Regulation : DUALE
Numbering Scheme: EUECCN
US ECCN
Legal Regulation : EAR
Numbering Scheme: USECCN
ITAR Category
Legal Regulation : ITAR
Numbering Scheme: USITAR
In the first Ship Pad Version, the batch data was retrieved from Delivery level, but users wants to see the Batches before the delivery creation and its possible according to the data from SAP transaction , ZWIM023 which was loaded in BW as C_BATCH2 attributes.
Quantity available in the SAP transaction ZWIM023.
Formula at query level: ( Linked quantity / Document Item Quantity) * 100
Estimate GI Date
New field available in order to provide always a GI date for the Order Line, because when data comes from Open Order Not Scheduled DSO (DBSDSO97) the To Be Invoiced date has a constant value 01.01.1900.
This field is based in a formula at Calculation View level where it checks if the C_FLAG is Marked, if YES then considers the Goods Issue Date (GI_DATE), otherwise keep the To Be Invoiced Date (C_TBIDAT2).
Note: C_FLAG is marked only when the data comes from Open Order Not Scheduled DSO (DBSDSO97) .
Note: The next fields have been defined in the DBSDSO9D self loop transformation (Rec DBSDSO9D -> ODSO DBSDSO9D)
Check the batch attribute (C_LOBMUD), Y if all batches linked do the Sales Order/Transfer Order Item have 'R04 A' , if one of them is N, then N.
Check the batch attribute (C_ZUSTD), Y if all batches linked do the Sales Order/Transfer Order Item have Y, if one of them is N, then N.
Concatenates all the Process Order documents available to the Sales Order/Transfer Order Item.
Concatenates all the Schedule Production End dates available to the Sales Order/Transfer Order Item.
Concatenates all the Schedule Production Start dates available to the Sales Order/Transfer Order Item.
Concatenates all the Parent Batches available to the Sales Order/Transfer Order Item.
Y - Last Requested Goods Issue date (C_LSTRQGI) is less then Current day
Credit block (C_CRDBLK) is empty, A or D
Delivery blockings (C_DELBLK and C_DELBLK2) are empty
N - Other conditions
New extractor created to load data from SAP tables KOTH911 and KONDH.
Definition:
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
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 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 |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
Workbooks:
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’).
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
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
