Interface

Technical Specification

New Extractor for Transaction Data EWM

Version 0.7

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 1 of 15
DOCUMENT REVISION HISTORY

Version Revision Date Author(s) Revision Notes

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 2 of 15
CONTENTS

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

2.0 General Information..................................................5
3.0 Functional Interpretations.........................................5
3.1 Technical Description............................................................................................................................. 5
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.............................................................................................................................. 7
4.3.1 Info sources / Data sources................................................................................................................ 7
4.3.2 Transformations.................................................................................................................................. 7
4.3.3 DSO.................................................................................................................................................... 7
4.3.4 Cube................................................................................................................................................... 8
4.4.5 Process Chain..................................................................................................................................... 8
4.4 File Layout and Data Mapping............................................................................................................... 8
4.5 Selection Screen.................................................................................................................................... 8
4.6 Selection Screen and Report Output Layout.......................................................................................... 8
4.7 Selection Screen Validation................................................................................................................... 8
4.8 Processing Logic.................................................................................................................................... 8
4.9 Flow diagram (Optional)....................................................................................................................... 10
4.10 Processing Steps............................................................................................................................... 11
4.11 Error Messages.................................................................................................................................. 11

5.0 Other Details...........................................................11

5.1 Error Handling...................................................................................................................................... 11
5.2 Logging................................................................................................................................................ 11
5.3 Restart and Recovery procedures........................................................................................................ 11

6.0 Conversion specific Information...............................12

6.1 Data cleansing..................................................................................................................................... 12
6.2 Conversion Steps................................................................................................................................. 12

7.0 Open Design Questions............................................12

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 3 of 15
8.0 Processing Report Output Details.............................13
9.0 Unit Test Plan......................................................................... 13

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 4 of 15
1.0 Request Details
Program Title P&A Reporting
Program Name /GMC/IO_FM_FIXBIN Type Interface
/GMC/IO_FM_HUINVTRY
/GMC/IO_FM_STOBIN
Function Spec ID NewExtractorsForTransactiona Version 0.7
lDataEWM_v1.doc
Developer On Site Coordinator
Phone
Email
Process Team IBM P&A Functional Contact
Phone
Email
SAP System and Version SAP BI 7 Process Doc. N/A
Reference
SAP Module and SCM Work step/ Task N/A
Sub module
Priority X Essential ( Business critical) Release xxx

Complexity High

2.0 General Information

Direction From SCM to BI
Interface / Conversion EWM Extractors
Technology
Transaction Code RSA5 , RSA6 , RSA1
Package /GMC/XXX
Message Class Standard message class will be used
Authorization Group Authorization will be controlled to specific users to run this extractor
Initiation Process Manual/Batch/Ad-Hoc
Run Frequency daily

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 5 of 15
3.0 Functional Interpretations

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.

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
 Any modification to the data is done at source.
 Master data is available in the source for extraction timely before transaction data is loaded.
 The fields to be added are available in source and it is possible to have a delta load of these
fields, otherwise daily full load should be feasible.
 IBM to ensure all data is present in BI system
 Report design to be completed by Business and IBM in Realization phase

3.4 Dependencies
Transactional data is maintained in EWM which must contain all the reporting attributes.

3.5 Additional Information

List of table and fields with extractors to be created are as below

C:\Documents and
Settings\Administrator\Desktop\kickoff_docs\Report Mapping 2011-10-13.xls

4.0 Interface Details

4.1 Tables
Standard tables used As this will be a custom Extractor. Function Module will be create to extract
SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 6 of 15
 data from SCM.
Custom tables used Not applicable
Standard objects used N/A

Custom objects created Custom Function Module:

/GMC/IO_FM_FIXBIN
/GMC/IO_FM_HUINVTRY
/GMC/IO_FM_STOBIN
Custom Structure:
/GMC/IO_DS_FIXBIN
/GMC/IO_DS_HUINVTRY
/GMC/IO_DS_STOBIN
Custom Data source:
/GMC/IO_EX_FIXBIN
/GMC/IO_EX_HUINVTRY
/GMC/IO_EX_STOBIN

4.2 Input File Details

Not applicable
File Name NA
File Type NA
File Delimiter NA
Location NA
Logical File Name NA
Comments NA

4.3 Configuration values

4.3.1 Info sources / Data sources

Custom Data source fields are in the attachment below
Data source name: /GMC/IO_DS_FIXBIN
/GMC/IO_DS_HUINVTRY
/GMC/IO_DS_STOBIN
Description of the Data source: Extractor for EWM transactional data.

EWM
DataSource_560.xls

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 7 of 15
 4.3.2 Transformations
Transformation from Extractor to WO DSO can be seen below

Mapping DS to WO
DSO_560.xls

4.3.3 DSO
Transformation from WO DSO to DSO can be seen below

Mapping WSO DSO

to DSO_560.xls

4.3.4 Cube
Transformation from DSO to Cube can be seen below

Mapping DSO to
Cube 560.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.2

4.5 Selection Screen

No Selection screen required as this is creation of new extractor.

4.6 Selection Screen and Report Output Layout

No Selection screen required as this is creation of new extractor.

4.7 Selection Screen Validation

No Selection screen validation required as this is creation of new extractor.

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 8 of 15
4.8 Processing Logic

Logic for Data Extraction:

Step 1: Go to transaction SE11 and create 3 structures

/GMC/IO_DS_FIXBIN for Fix Bin Assignment

/GMC/IO_DS_HUINVTRY for HU Inventory
/GMC/IO_DS_STOBIN for Storage Bin Inventory

Step 2: Go to SE37 and create three function modules

/GMC/IO_FM_FIXBIN for Fix Bin Assignment

/GMC/IO_FM_HUINVTRY for HU Inventory
/GMC/IO_FM_STOBIN for Storage Bin Inventory

This function module will have the following parameters:

The table parameters of function module should be of type, extract structure for the data can be extracted

IMPORT Parameters:
I_REQUNR TYPE SRSC_S_IF_SIMPLE-REQUNR
I_DSOURCE TYPE SRSC_S_IF_SIMPLE-DSOURCE
I_MAXSIZE TYPE SRSC_S_IF_SIMPLE-MAXSIZE
I_INITFLAG TYPE SRSC_S_IF_SIMPLE-INITFLAG
TABLES Parameter will have the following:
I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT
I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS
E_T_DATALIKE /GMC/IO_DS_TRANSEWM

Step 3: All the three extractions will run for delta load. Get the last delta execution time stamp from table
ROOSGENDLM, Fetch all the records which are changed after the previous delta execution and update
ROOSGENDLM with the current execution time stamp.

Step4: Do the OPEN CURSOR and write logic to fetch data from the below tables in FETCH CURSOR
for all the three extractors.

Fix Bin Assignment:

Fetch data from table /SCWM/BINMAT – (Assignment Table for Fixed Bins – Product) based on field
DATOUT ("Storage Bin Improvable" Changed On ) to get the details of fixed bin assignment.

HU Inventory:

 Fetch handling unit header details from table /SCWM/HUHDR based on field
CHANGED_AT(UTC Time Stamp in Short Form (YYYYMMDDhhmmss) to get the details of
handling unit.

 Fetch handling unit item details from table /SCWM/GMHUITM for all the changed products from
table /SCWM/HUHDR.

Storage Bin Inventory:

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 9 of 15
Fetch the Storage Bin and warehouse number details from table /SCWM/LAGP based on Time of
Change (LAEDT) field.

Call FM /SCWM/STOCK_INC_OUT_MON by passing Import parameters LGNUM and LGPLA and get
the storage bin inventory details in exporting parameter ET_data.

This OPEN CURSOR and FETCH CURSOR acts like a loop and fetches the data from table till it reaches
its maximum packet size and the fetched data is send to the extractors.

Step 5: Create three Data source using transaction RSO2 as shown below:
/GMC/IO_EX_ FIXBIN for Fix Bin Assignment
/GMC/IO_EX_HUINVTRY for HU Inventory
/GMC/IO_EX_STOBIN for Storage Bin Inventory

Step 6: Assign structure and Function module to Data source:

1. Fix Bin Assignment:

Assign the structure /GMC/IO_DS_FIXBIN and function Module /GMC/IO_FM_FIXBIN to the Data
source /GMC/IO_EX_ FIXBIN which is created in step 5.
2. HU Inventory:
Assign the structure /GMC/IO_DS_HUINVTRY and function Module /GMC/IO_FM_HUINVTRY to
the Data source /GMC/IO_EX_HUINVTRY which is created in step 5.
3. Storage Bin Inventory :
Assign the structure /GMC/IO_DS_STOBIN and function Module /GMC/IO_FM_ STOBIN to the
Data source /GMC/IO_EX_STOBIN which is created in step 5.

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 10 of 15
4.9 Flow diagram (Optional)

Handling unit Inventory data flow

YES
First Start init delta
Start
time with data option
data
load?
NO

Start delta load

Function module populates the customized

DS with Handling unit Inventory data

Handling unit inventory

data loaded to PSA from
SCM

DTP pulls data from PSA

to WO DSO GSEWMO11

DTP pulls data from DSO DTP pulls data from WO

GSEWMO12 to cube DSO GSEWMO11 to DSO
GSEWMC06 GSEWMO12

End

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 11 of 15
Storage bin inventory data flow

YES
First Start init delta
Start
time with data option
data
load?
NO

Start delta load

Function module populates the customized

DS with storage bin inventory data

Storage bin inventory

loaded to PSA from SCM

DTP pulls data from PSA

to WO DSO GSEWMO13

DTP pulls data from DSO DTP pulls data from WO

GSEWMO14 to cube DSO GSEWMO13 to DSO
GSEWMC07 GSEWMO14

End

4.10 Processing Steps

1 Using transaction RSO2 new data sources will be created based on the tables
mentioned in the excel sheet in section 4.1
2 Once created the new data source will be replicated into BI and activated
3 Create Info package to initialize delta load data from SCM to BI. Then create an info
package for delta load from SCM to BI
SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 12 of 15
4.11 Error Messages
Error No. Error Message
1 No Authorization
2 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 sustain team will be informed about the failure. The
sustain team will update the concern team and the data correction should be completed by the concern
team before next load or reload. For delta load failure the QM status should be made red before repeat
delta is made.

5.2 Logging
Logging of SAP BW process chains is automatic.

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

No conversion needed

7.0 Open Design Questions

No open design questions
No Issue / Resolution Description Name Date Status

SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 13 of 15
SAP BI NewExtractorsForTransactionalDataEWM_v0.6
Page 14 of 15
8.0 Processing Report Output Details
# Report Field Field Report Level Sort length / SAP Table Processing
Name
Definition Reader/Item Format -field Description
/ Calculation Logic

9.0 Unit Test Plan

# Step Screen Expected Actual Executed
Result By/Date
shots Result/Remarks
1 Run info package for Init delta (with data N- number of
option) records
should be
fetched and
the load
status should
b green
2 Run info package for delta load Zero records
immediately should be
fetched and
the load
status should
b green
3 Run info package for delta daily Daily runs
should bring
new records
4 Check the values for the data fields in The data
new data source in SAP BI and same should match
values in SCM in both BI
and SCM
5 Repeat above step for different datasets The data
should match
in both BI
and SCM
6 Check the time dependent characteristics The value
should be
within validity
period
7 Load test data with incorrect values like The load
wrong date format, invalid characters should fail

SAP BI 15399_ETD_E560_NewExtractorsForTransactionalDataEWM_v0.4
Page 15 of 15