Existing Extractors For Transactional Data - v1

Interface
Technical Specification
Enhance Existing Extractors for Transactional Data
Version 0.4
SAP BI ExistingExtractorsForTransactionalData_V0.4.doc
Page 1 of 18
DOCUMENT REVISION HISTORY
Version Revision Date Author(s) Revision Notes
0.1 Initial Version
Page 2 of 18
CONTENTS
1.0 Request Details.......................................................................5

2.0 General Information..................................................5
3.0 Functional Interpretations.........................................5
3.1 Technical Description............................................................................................................................. 6
3.2 Security / Authorization / Control Implemented......................................................................................6
3.3 Functional and Technical Clarifications.................................................................................................. 6
3.4 Dependencies........................................................................................................................................ 6
3.5 Additional Information............................................................................................................................ 6
4.0 Interface Details........................................................6

4.1 Tables.................................................................................................................................................... 6
4.2 Input File Details.................................................................................................................................... 7
4.3 Configuration values.............................................................................................................................. 8
4.3.1 Info sources / Data sources................................................................................................................ 8
4.3.2 Transformations.................................................................................................................................. 8
4.3.3 DSO.................................................................................................................................................... 8
4.3.4 Cube................................................................................................................................................... 8
4.4.5 Process Chain..................................................................................................................................... 8
4.4 File Layout and Data Mapping............................................................................................................... 9
4.5 Selection Screen.................................................................................................................................... 9
4.6 Selection Screen and Report Output Layout.......................................................................................... 9
4.7 Selection Screen Validation................................................................................................................... 9
4.8 Processing Logic.................................................................................................................................... 9
4.9 Flow diagram (Optional)....................................................................................................................... 11
4.10 Processing Steps............................................................................................................................... 14
4.11 Error Messages.................................................................................................................................. 15
5.0 Other Details...........................................................15

5.1 Error Handling...................................................................................................................................... 15
5.2 Logging................................................................................................................................................ 15
5.3 Restart and Recovery procedures....................................................................................................... 15
6.0 Conversion specific Information...............................15

6.1 Data cleansing..................................................................................................................................... 15
6.2 Conversion Steps................................................................................................................................. 15
7.0 Open Design Questions............................................15
Page 3 of 18
8.0 Processing Report Output Details.............................16
9.0 Unit Test Plan......................................................................... 16
Page 4 of 18
1.0 Request Details
Program Title Enhance Existing Extractors for Transactional Data
Program Name BADI implementation: Type Interface
/GMC/IO_IMP_RSU5_BADI
Function Spec ID EnhanceExistingExtractorsFor Version 0.3
TransactionalData_V1.0.doc
Developer On Site Coordinator
Phone
Email
Process Team IBM P&A team Functional Contact
Phone
Email
SAP System and Version SAP BI 7.0 and SAP SCM 7.0 Process Doc. NA
Reference
SAP Module and EWM (Extended Warehouse Workstep/ Task NA
Management)
Sub module
Priority Essential ( Business critical) Release
Complexity High
2.0 General Information
3.0 Functional Interpretations

Direction From SCM to BI
Interface / Conversion EWM Extractors
Technology
Transaction Code RSA5 , RSA6 , RSA1
Package /GMC/XXX
Message Class /GMC/IO_MC_INTERFACE
Authorization Group Standard authorization will be provided to development/ sustain team to
extract the data from SCM to BI.
Initiation Process Scheduled Job with ability for Manual (Ad Hoc)
Run Frequency Daily
Page 5 of 18
3.1 Technical Description
The P&A system reports on SAP Business Objects. The BO reports will be based on SAP BI data
warehouse. In order to do so, the complete transactional data records will have to be loaded from SAP
SCM-EWM to SAP BI for reporting.
After successful completion of the data loads EWM transactional data will be available in reports to fulfill
the reporting requirements.
The data will be loaded daily into SAP BI and it will be a delta load. Exceptions to this will be considered
later based on size of load and feasibility.
SAP BI Business
EWM Enhanced
data Objects
system BI content warehous reporting
extractors e
for
transactio
n data
data
3.2 Security / Authorization / Control Implemented

No access required for Business Users as data will be seen only via reports. Access required for the
development and support teams
3.3 Functional and Technical Clarifications

Assumptions:
 Master data will be available in the source for extraction timely before transaction data is loaded.
 The enhanced data sources are functionally relevant in holding the new fields
 Report design to be completed by Business and IBM in Realization phase
 This data transfer from SCM to BI, only addresses the fields that are not standard for extraction
as defined by the data dictionary.
3.4 Dependencies
1. Master data is maintained in ECC which must contain all the reporting attributes.
3.5 Additional Information

This is not applicable
4.0 Interface Details
4.1 Tables
Standard tables used
List of table and fields with extractors to be enhanced are as below
Page 6 of 18
\
Custom tables used To Enhance the Existing Extractors BADI will be used.
Standard objects used 0WM_C06
0WM_C02
0WM_C01
0WM_C07
0WM_C10
0WM_C09
0WM_C04
0WM_C05
0WM_MP06
0WM_MP04
0WM_MP03
0WM_MP02
0WM_MP01
0WM_MP07
0WM_MP05
0WM_DS09
0WM_DS06
0WM_DS03
0WM_DS02
0WM_DS01
0WM_DS07
0WM_DS08
0WM_DS04
0WM_DS05
Custom objects created For the Extractors which need to be enhanced we will copy the standard
objects and create Custom Object for Customizations.
4.2 Input File Details

File Name NA
File Type NA
File Delimiter N
Location N
Logical File Name N
Comments NA
4.3 Configuration values
4.3.1 Info sources / Data sources

Data source fields are in the attachment below
Page 7 of 18
EWM
DataSource_559.xls
4.3.2 Transformations
Mapping document from extractor to write optimized DSO can be seen below:
Custom Write optimized DSO’s will be created for ASN delivery, warehouse tasks,
delivery items and storage bins data extraction.
Transformations to
WO DSO 559.xls
4.3.3 DSO
Structure of WO DSO’s and Standard DSO’s can be seen in the transformation attached
below. Custom DSO’s will be created for loading ASN delivery, warehouse tasks, delivery
items and storage bins data to DSO from WSO DSO
Mapping WO DSO to
DSO 559.xls
4.3.4 Cube
Cube structure and mapping can be seen below. Custom cube will be created for loading
ASN delivery, warehouse tasks, delivery items and storage bins data to cube from DSO
Mapping DSO to
Cube.xls
4.4.5 Process Chain

Process will be automated in subsequent Process chains for data loading.
4.4 File Layout and Data Mapping

Please find the mapping document attached in section 4.1 and 4.3.1
4.5 Selection Screen

No Selection screen required as this an enhancement to existing extractor
Page 8 of 18
4.6 Selection Screen and Report Output Layout
No Selection screen required as this enhancement to existing extractor.
4.7 Selection Screen Validation

No Selection screen validation required as this an enhancement to existing extractor.
Page 9 of 18
4.8 Processing Logic
In this SCM side development, the additional transactional data for ASN delivery, warehouse task,
delivery items and storage bin given in the above mapping sheets (section 4.1) are added to the existing
EWM extractors 80SPL_DS01, 80WM_DS05, 80WM_DS06 and 80WM_DS07 respectively.
Enhancing the standard data sources:

Go to transaction RSA6, select the data source structure and choose the enhance extractor structure
button.
Give a name for the append structure as /GMC/IO_DS_SPL_DS01 for the extract structure
/BIC/CE80SPL_DS01.
Add the additional fields to the append structure.
Similarly add all the fields for other data source structures using append structure.
After adding the fields to append structure activate the data source.
Enhancing Data Sources with BAdI RSU5_SAPI_BADI:
Create an implementation /GMC/IO_IMP_RSU5_BADI for the BADI RSU5_SAPI_BADI in the transaction

SE19.
In the BADI implementation, create a custom methods with the name same as data source, without the
first 2 character (i.e for 80WM_DS05 the method name is WM_DS05.)
Page 10 of 18
In Data transform method; write the logic to call the custom method for each data source.
In this custom method, write the logic to fetch the data from the database tables based on the existing
data fields.
The existing field data will be stored in the import table C_T_DATA. For all the entries in this table get the
data from the corresponding database table and modify the newly added fields
.
For data source 80SPL_DS01, get the inbound delivery data from the table /SCDL/DB_PROCH_I where
inbound delivery number is equal to 80SPL_DS01-SPL_ASNGID.
Based on the inbound delivery document number get the reference document number from the table
/SCDL/DB_REFDOC.
For data source 80WM_DS05, get the warehouse task details like activity area (AAREA) from the table
/SCWM/ORDIM_C based on the warehouse task (80SPL_DS01-WM_TANUM).
For data source 80WM_DS06, get the transportation unit number based on the delivery number
(80WM_DS06-WM_DOCID) from the table /SCWM/TU_DLV. Based on the TU numbers get the details
from the table /SCWM/TUNIT.
For data source 80WM_DS07, get the storage bin details like storage section and bin type from table
/SCWM/LAGP. Based on the bin type selected, get length, width and height from table /SCWM/T303, get
the description from table /SCWM/T303T and based on storage section get the description from table
/SCWM/T302T.
4.9 Flow diagram (Optional- Custom Objects)

ASN/ Delivery Data
Page 11 of 18
YES
First time Start init delta
Start
data with data option
load?
NO
Start delta load
The method SPL_DS01 populates the

enhanced DS 0SPL_DELIVERY_DATA_1 with
ASN delivery data
ASN Delivery
transaction Data loaded
to PSA from SCM system
DTP pulls data from PSA to ASN /

Delivery Data WO DSO GSEWMO01
DTP to pull data from DSO DTP pulls data from WO DSO
GSEWMO02 to ASN Delivery GSEWMO01 to DSO GSEWMO02
Data Cube GSEWMC01
End
Warehouse tasks transaction data flow
Page 12 of 18
YES
Start
load?
NO
Start delta load
The method WM_DS05 populates the

enhanced DS 0WM_WT_WO with
warehouse task data
Warehouse task
transaction Data loaded
DTP pulls data from PSA to

Warehouse Tasks WO DSO
GSEWMO03
DTP to pull data from DSO DTP pulls data from

GSEWMO04 to Warehouse WO DSO GSEWMO03 to DSO
Tasks Cube GSEWMC02 GSEWMO04
End
Delivery Items transaction data flow :
Page 13 of 18
YES
Start
load?
NO
Start delta load

enhanced DS 0WM_DLVI with delivery item
data
Delivery Item
transaction data loaded
DTP pulls data PSA to Delivery Items

WO DSO GSEWMO05
DTP to pull the data from DSO DTP to pull data from WO DSO
GSEWMO06 to Delivery Items GSEWMO05 to DSO GSEWMO06
Cube GSEWMC03
End
Storage bin transaction data flow :
Page 14 of 18
YES
Start
load?
NO
Start delta load

enhanced DS 0WM_BIN with Storage Bin
data
Storage Bin transaction

data loaded to PSA from
SCM system
DTP to pull the data from PSA to

storage bins WO DSO GSEWMO07
DTP to pull the data from DSO DTP to pull the data from WO DSO
GSEWMO08 to storage bins GSEWMO07 to DSO GSEWMO08
Cube GSEWMC04
End
4.10 Processing Steps

1 In SCM, Enhance the existing DSOs as mentioned in the excel above with new
transactional data fields.
2 Export the data sources from SCM to BI.
3 Replicate data sources in BI.
4 Create Info package to load data from SCM to BI.
Page 15 of 18
4.11 Error Messages
Error No. Error Message
1 No Authorization
2 No Special Characters
4 Data not there for the given selection
5.0 Other Details
5.1 Error Handling

If there is a data load failure then the cause of failure should be identified. In case of short dumps failed
request should be deleted from the info provider and data should be reloaded. If the failure is due to
wrong data (wrong date format, master data etc) the concern user should be updated and the data
correction should be completed by the user before next load or reload. In case of delta load failure the
QM status should be made red before repeat delta is made.
5.2 Logging
Data source is SAP. No data cleansing is required as part of this enhancement.
5.3 Restart and Recovery procedures

Step 1 For delta load failure the QM status should be made red before repeat delta is made.
Step 2 The failed request should be deleted from the info provider
Step 3 The repeat delta should be done
6.0 Conversion specific Information
6.1 Data cleansing

Since all data is from a trusted source, SCM, there is no cleansing required, nor any data conversions
6.2 Conversion Steps

This is not applicable
7.0 Open Design Questions

No open issues to be addressed.
No Issue / Resolution Description Name Date Status
Page 16 of 18
8.0 Processing Report Output Details
# Report Field Field Report Level Sort Length / SAP Table-field Processing
Name Definition Format Description /
Reader/Item
Calculation Logic
9.0 Unit Test Plan

# Step Screenshots Expected Result Actual Executed
Result/Remarks By/Date
1 Run info package for Init N- number of records
delta (with data option) should be fetched and
the load status should b
green
2 Run info package for delta Zero records should be
load immediately fetched and the load
status should b green
3 Run info package for delta Daily runs should bring
daily new records
4 View data in Sap BI and The data should match
check the same values in in both BI and SCM
SCM
5 Check the values for The data should match
enhanced data fields in data in both BI and SCM
source for ASN delivery in systems.
SAP BI and same values in
SCM.
enhanced data fields in data in both systems BI and
source for Warehouse task SCM.
in SAP BI and same values
in SCM.
source for Delivery items in SCM.
SCM.
source for Storage bin in SCM.
SCM.
9 Repeat above step for The data should match
different datasets in both BI and SCM
SAP BI 15399_ETD_EX559_ExistingExtractorsForTransactionalData_V0.4
Page 17 of 18
# Step Screenshots Expected Result Actual Executed
Result/Remarks By/Date
10 Check the time dependent The value should be
characteristics within the validity period
11 Load test data with incorrect The load should fail
values like wrong date
format, invalid characters
SAP BI 15399_ETD_EX559_ExistingExtractorsForTransactionalData_V0.4
Page 18 of 18

Existing Extractors For Transactional Data - v1

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Existing Extractors For Transactional Data - v1

Transféré par

Droits d'auteur :

Formats disponibles

Interface

Enhance Existing Extractors for Transactional Data

Version Revision Date Author(s) Revision Notes

0.1 Initial Version

1.0 Request Details.......................................................................5

4.0 Interface Details........................................................6

5.0 Other Details...........................................................15

6.0 Conversion specific Information...............................15

7.0 Open Design Questions............................................15

2.0 General Information

3.0 Functional Interpretations

3.2 Security / Authorization / Control Implemented

3.3 Functional and Technical Clarifications

3.5 Additional Information

4.0 Interface Details

4.2 Input File Details

4.3 Configuration values

4.3.1 Info sources / Data sources

4.4.5 Process Chain

4.4 File Layout and Data Mapping

4.5 Selection Screen

4.7 Selection Screen Validation

Enhancing the standard data sources:

Add the additional fields to the append structure.

Enhancing Data Sources with BAdI RSU5_SAPI_BADI:

Create an implementation /GMC/IO_IMP_RSU5_BADI for the BADI RSU5_SAPI_BADI in the transaction

4.9 Flow diagram (Optional- Custom Objects)

Start delta load

The method SPL_DS01 populates the

DTP pulls data from PSA to ASN /

Warehouse tasks transaction data flow

Start delta load

The method WM_DS05 populates the

DTP pulls data from PSA to

DTP to pull data from DSO DTP pulls data from

Delivery Items transaction data flow :

Start delta load

The method WM_DS06 populates the

DTP pulls data PSA to Delivery Items

Storage bin transaction data flow :

Start delta load

The method WM_DS07 populates the

Storage Bin transaction

DTP to pull the data from PSA to

4.10 Processing Steps

5.0 Other Details

5.1 Error Handling

5.3 Restart and Recovery procedures

6.0 Conversion specific Information

6.1 Data cleansing

6.2 Conversion Steps

7.0 Open Design Questions

9.0 Unit Test Plan

Vous aimerez peut-être aussi