Enterprise IT: Business Solutions- Inventory Management

Document: Low-level FSD STO Text Element Extraction

Project: Cousteau
Release: Jan 2016
Clarity ID: PR207383

Document Revision 1.0

Date Oct 22, 2015
Author(s) Ram Bandaru
Department(s) ESBS SAP IM/MM team
Document Location http://projects.internal.t-
mobile.com/sites/pp/2013/PR207383/PL/Forms/AllItems.aspx?RootFolder=
%2Fsites%2Fpp%2F2013%2FPR207383%2FPL%2F04%2DDesign%2FIM
%2DOER%20FS%20docs%2FLow%2Dlevel%20FS%20docs
 FSD Template

Table of Contents
1 DOCUMENT OVERVIEW 3
2 DOCUMENT APPROVALS & REVIEWERS 3
2.1 Approvers 3
2.2 Reviewers 3
3 DOCUMENT HISTORY 4
4 CONTACTS 4
5 PROJECT OVERVIEW 4
5.1 Project Overview 4
5.2 Scope Summary 5
5.3 Related documents 5
5.4 Assumptions 6
5.5 Business Requirements 6
5.6 High Level System Design (HLSD) 6
5.7 As-Is Process 6
6 DESIGN 6
6.1 High Level Design 6
6.1.1 Requirement 8
6.1.2 As-Is Design 8
6.2 To-Be Design 9
6.2.1 Selection Screen 9
6.2.2 Processing Logic 10
6.2.3 File Output 11
6.2.3.1 Output file names 11
7 UNIT TESTING 11
8 BACKGROUND JOBS 13
8.1 Job: ZTMM_STO_Text_EXTRACT 13

Last Updated 9/14/2017 Page 2 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

1 Document Overview

2 Document Approvals & Reviewers

2.1 Approvers
Name Business/IT Group Approval

Raj Julakanti ES Business Solutions SAP OTC Sr. Raj Julakanti

Manager
Sharan ES Business Solutions SAP IM/Supply Chain Sharan Kumar
Kumar - Manger
Meridith Senior Manager Sales Operations Meridith Emmett
Emmett
Nancy Senior Manager Fulfillment Finance Nancy Watson
Watson
Raj Julakanti ES Business Solutions SAP OTC Sr. Raj Julakanti
Manager

2.2 Reviewers
Name Business/IT Group Project Role

Karanbir Sidhu ES - Technical Delivery Manager

Unmukt ES Architect
Gadkari
Debadrita Roy SAP ABAP and PI Development- Lead
Developer
Jeff Green TDM

Last Updated 9/14/2017 Page 3 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

3 Document History

Version Change Date Author(s) Notes, Comments, Change Reasons

ID
1.0 10/22/2015 Ram Bandaru Initial draft created

4 Contacts
Group Contact Email Phone Primary /
Secondary
Ram.Bandaru@t 614 602 7840
SAP IM/MM Ram Bandaru
-mobile.com

5 Project Overview

5.1 Project Overview

Problem Statement

Opportunity Statement

Deploy the processes and related application changes to transitioning fulfillment of warranty
claims to Retail.
When fulfilling a warranty claims through Retail, the customer will be required to bring the
device to be exchanged to a T-Mobile store. Having the device returned through a T-Mobile
store (instead of having the device sent by customer directly to a return center) will ensure the
device is actually returned and is in an acceptable condition.

Last Updated 9/14/2017 Page 4 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

This should significantly reduce the warranty claims ending as returns out-of-warranty (OOW),
no-trouble-found (NTF), as well as with no device being returned. Such claims cost the
company millions of dollars annually. This project will aim to close these gaps and identify better
ways to service our customers with warranty related situations.

5.2 Scope Summary

In Scope:

OEM warranty exchange claims filed by customer through retail store including advanced
exchange, loaner device, multiple exchange and alternate exchange, as well as the case
where the customer cannot come physically to a store (case similar to the current process)
Channels: Retail, Branded (TPR, TPRi), Care.

Out Of Scope

Fulfillment of Insurance claims in-store

Prepaid
Puerto Rico
MVNO
Brand: Walmart Family Mobile
Brand: BrightSpot Mobile
Channel: IVR
Channel: National Retail (Wireless Advocates, Apple)
Channel: Web
*This channel does not support warranty exchange
Channel: Telesales
*This channel does not support warranty exchange
Channel: B2B
*This channel does not support warranty exchange
Indirect dealers
Brand: MetroPCS

5.3 Related documents

Document Document
ID
BRD http://projects.internal.t-
mobile.com/sites/pp/2013/PR207383/PL/Forms/AllItems.aspx?RootFolder=%2fsites%
2fpp%2f2013%2fPR207383%2fPL%2f02%2dRequirements&FolderCTID=&View=%7
b3D61679F%2dBE04%2d458F%2d84FD%2dC76AEDD3A885%7d
HLSD http://projects.internal.t-
mobile.com/sites/pp/2013/PR207383/PL/Forms/AllItems.aspx?RootFolder=%
2fsites%2fpp%2f2013%2fPR207383%2fPL%2f04%2dDesign%2fHLSD&Fold
erCTID=&View=%7b3D61679F%2dBE04%2d458F%2d84FD%2dC76AEDD3

Last Updated 9/14/2017 Page 5 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

Document Document
ID
A885%7d

5.4 Assumptions

Assumption Assumption Description

ID
Connect Enterprise will access files from SAP ECC UNIX folder and place it into
1
SCOPSBI and TDFADS destination folders. No scripts are necessary
2 Extraction program will be setup in production as background job. No Tidal?
3 Connect Enterprise will archive the files?

5.5 Business Requirements

Business High Level Description Functional

Requirement No. Requirement No(s).

7.11.43 The reporting solution must not filter columns

from the source system's table, in order for all
source columns being visible and available for
reporting.

5.6 High Level System Design (HLSD)

http://projects.internal.t-mobile.com/sites/pp/2013/PR207383/PL/04-
Design/HLSD/HLSD%20Cousteau%20-
%20Warranty%20Exchange%20Fulfillment%20in%20Retail%20(PR207383)%20-
%20Initial%20Draft%20V6.pptx

5.7 As-Is Process

Warranty exchanges are fulfilled today via AWRE process where exchange devices are
directly shipped to customers home.

6 DESIGN
6.1 High Level Design

Last Updated 9/14/2017 Page 6 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

Data is extracted from ECC once a day and sent to SCOPSBI and TDFADS via Connect
Enterprise.
New custom program will be created in ECC to extract STO text element information and create
a flat file. Connect enterprise will access the files in SAP ECC UNIX folder and transfer to
SCOPSBI and TDFADS destination locaitons.

SAP ECC Connect SCOPSBI SCOPSBI

Celerra folder Enterprise

TDFADS folder TDFADS

ECC UNIX folder: /usr/sap/interfaces/celerra/SSI/STOTextData/out/

File names:
SAPECC_WarrantyExchangePOTextElements_XX_YYYYMMDD.dat
SAPECC_WarrantyExchangePOTextElements_XX_YYYYMMDD.done
SAPECC_WarrantyExchangePOTextElements_XX_YYYYMMDD.man

Frequency: Once a day after mid-night (1am PST), will extract all STOs created the previous
day.

Destination folders for SCOPSBI: Get from SCOPSBI FSD

QAT: \\gsm1900.org\dfsroot\as\SCOpsBI\SAP_ECC\QA\WarrantyExchangePOTextElements
PROD:
\\gsm1900.org\dfsroot\as\SCOpsBI\SAP_ECC\PROD\WarrantyExchangePOTextElements

Destination folder for TDFADS: Get from TDFADS FSD

Note: Text elements are created while the STOs are created. This information is not changed
once the STOs are created, therefore, no delta extract is required.

Next steps:
- Email SAP ECC UNIX team to have the UNIX folders created
(UnixSecurityComplianceTeam@T-Mobile.com)
Last Updated 9/14/2017 Page 7 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

- After project is committed, include Connect Enterprise team by creating RT (by

TDM/SCOPSBI/TDFADS team)
Amdocs ASM Data Transfer and Tidal <AmdocsASMDataTransferandTidal@t-mobile.com>
Reliance form needs to be filled.
6.1.1 Requirement
Warranty orders are created in HSO system, which will turn create an STO in ECC system to
transfer device from forward DC to Retail stores. Several data elements coming from HSO to
ECC are stored on STO header as text elements for further processing. Business wanted
visibility to these data elements in SCOPSBI (in addition to the same data available from HSO
to SCOPSBI as a separate extract from HSO).
Purpose of this FSD is to enable extraction of following STO text elements and send to
SCOPSBI.

Text ID Description
F79 HSO: BAN and MSISDN
F80 HSO: Mobile and Contact nos.
F81 HSO: Repair serial number
F82 HSO: Repair failure code&Desc.
F83 HSO: HSO Order Number
F84 HSO: Shipping Info.
F85 HSO: Billing Info.
F86 HSO: Old HSO order no.
F87 HSO: Additional Info.
F88 HSO: Notification Preferences
F89 HSO: Order Detail ID

Program should produce the following for any file downloaded to the SAP UNIX server:
.DAT data file
.MAN manifest file
.DONE no data, just a file that signifies the .DAT file has been fully transferred
Please see attached guidelines.

Flat File Delivery.doc

6.1.2 As-Is Design

N/A

Last Updated 9/14/2017 Page 8 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

6.2 To-Be Design

A new ABAP program ZTIMM_WARR_EXCH_POTEXT_EXTRACT will be created to extract

STO text element information. This new program will be run as scheduled background job.
A new transaction ZTMM_STO_EXTRACT will be created that can be used to run this extract
on-demand.

6.2.1 Selection Screen

Program shall contain following selection parameters.

Selection Field SAP Fieldname / Logic Type Req/Opt

Purchase Order no. Range required. EBELN Select- Opt
option
PO Document Type No range. Default to ZW01. BSART Select- Opt
option
PO Date Date range needed. AEDAT Select- Opt
option
Purchasing No range. EKORG Select- Opt
Organization option
Purchasing Group No range. EKGRP Select- Opt
option

Download to front-end Checkbox Opt

(PC)
File Pathname (PC) TYPE STRING Parameter Opt
Default to C:\Temp\
Download to server Checkbox Opt
File Pathname (Server) TYPE STRING Parameter Opt
Default to
/usr/sap/interfaces/celerra/SSI/STOTextData/out/
File Name TYPE 60 Parameter Opt
File Extension TYPE STRING Parameter Opt
Default to DAT

File Delimiter TYPE 1 Parameter Opt

Default to | (pipe)
File Counter TYPE 2
Default to 01

Last Updated 9/14/2017 Page 9 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

6.2.2 Processing Logic

1. If PO numbers are populated in selection screen, get the PO numbers and go to step 3
below.
2. If PO number field is blank in selection screen, using following as selection parameters,
get PO numbers from EKKO.
a. Document type
b. PO date
c. Purchasing Org
d. Purchasing group
3. For each of the PO, get following text elements using Function Module READ_TEXT
Field Logic Example
ID Text ID. F79 to F89 F79
LANGUAGE Always EN EN
NAME PO number 7000000120
OBJECT Use EKKO EKKO
ARCHIVE_HANDLE Blank
LOCAL_CAT Blank

4. Following output fields shall be populated based on the logic described

Last Updated 9/14/2017 Page 10 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

STO Text
elements.xlsx

5. Separate each field with separator from selection screen File Delimiter
6. Create the output file with field descriptions in 1st line followed by text element data from
STOs, one line for each STO. Each field shall be separated by File Delimiter and each
row separated by carriage return.
7. File name shall include the version number from field File Counter from selection screen
along with current date
Ex: SAPECC_WarrantyExchangePOTextElements_01_20151027.dat
8. If option Download to front-end (PC) is selected, write the output file to local path File
Pathname (PC) from selection screen.
9. If option Download to server is selected, write the output file to UNIX file path File
Pathname (Server) from selection screen.

6.2.3 File Output

File output to server and local PC should be possible based upon the user selection. See the
logic above.

Sample files below

ECC_Output_Sample
.xlsx

6.2.3.1 Output file names

The file will be created once in a day in accordance with file naming standards (refer to section
6.1.1) and delivered for ScopsBI via Connect Enterprise pick-up:
/usr/sap/interfaces/celerra/SSI/ConsignmentInventory/out/SAPECC_WarrantyExcha
ngePOTextElements_XX_YYYYMMDD.dat.gz
/usr/sap/interfaces/celerra/SSI/ConsignmentInventory/out/SAPECC_WarrantyExcha
ngePOTextElements _XX_YYYYMMDD.done
/usr/sap/interfaces/celerra/SSI/ConsignmentInventory/out/SAPECC_WarrantyExcha
ngePOTextElements _XX_YYYYMMDD.man

7 Unit Testing
Unit Test Description Results P/F
Scenario

Last Updated 9/14/2017 Page 11 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

Run the custom transaction Local PC file shall be created. Validate

1
Run the custom program in background
2
mode with wide date range (so that it
extracts about 10K STOs)
all fields in output file.
UNIX file shall be created. Validate all
fields in output file. Validate if the file
is created in correct UNIX folder.
Background job shall be complete
without error.
Output file shall be written in UNIX
folder.

Last Updated 9/14/2017 Page 12 of 13

CONFIDENTIAL AND PROPRIETARY

 FSD Template

8 Background Jobs
Note: the jobs below are new jobs that will be scheduled in SAP directly TIDAL is
needed?

The new ABAP program to send data to ScopsBI will be scheduled to run daily early in the
morning that extracts to celerra location, where files will be picked-up by Connect Enterprise
and delivered to ScopsBI:

8.1 Job: ZTMM_STO_Text_EXTRACT

Step 1:
ABAP Prog: ZTIMM_WARR_EXCH_POTEXT_EXTRACT
Date/Time: Monday to Sunday at 1am PST
Variant: STO_TEXT_EXT

Connect Enterprise:
The files will be picked up from the SSI celerra directory and
transmitted to ScopsBI using Connect Enterprise

Background_Job.xlsx

Last Updated 9/14/2017 Page 13 of 13

CONFIDENTIAL AND PROPRIETARY