S4H_6_Bank_Master

S4H_6_Bank_Master

Document Control Information

Document Information
Document Identification S4H_6

Document Name S4H_6_Bank_Master

Project Name D-DASH

Client NA
Document Author Deloitte
Document Version 1.0
Document Status Initial
Date Released 30-Sep-16
FS Reference

Document Edit History

Version Date Additions/Modifications Prepared/Revised by
1.0 30-Sep-16 Initial Lakshmikanth Palaparthi

Document Review/Approval History

Date Name Organization/Title Comments
30-Sep-16 Lakshmikanth/Hari Deloitte / Development
Coordinator {Team}

Distribution of Final Document

The following people are designated recipients of the final version of this document:

Name Organization/Title
<Name> <Organization/Title>

20-Oct-16 Page 2 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

Table of Contents
1 General Attributes............................................................................................................................... 4
1.1 Object Information......................................................................................................................... 4
1.2 Custom Object Attributes............................................................................................................... 4
2 Technical Details................................................................................................................................. 5
2.1 Technical Logic Flow..................................................................................................................... 5
2.2 Program Structure and Processing................................................................................................ 5
2.3 Selection Screen........................................................................................................................... 5
2.4 Data Mapping................................................................................................................................ 5
2.5 Restart Capability.......................................................................................................................... 5
2.6 Verification and Reconciliation....................................................................................................... 6
2.7 Technical Assumptions.................................................................................................................. 6
2.8 Dependencies................................................................................................................................ 6
2.9 Open Items.................................................................................................................................... 6
3 Error Handling, Exception Handling and Security Constraints.......................................................7
4 Unit Test Cases................................................................................................................................... 8
5 Appendix / Object Templates............................................................................................................. 9

20-Oct-16 Page 3 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

1 General Attributes

1.1 Object Information

Program Name(s) ZFIR_BANKMASTER_UPLOAD

Include Files ZFIR_BANKMASTER_UPLOAD_TOP
ZFIR_BANKMASTER_UPLOADSEL
ZFIR_BANKMASTER_UPLOADF01
Area Menu NA
Print Transaction NA
Authorization Object Used NA
Output Type
Run Mode Foreground Background Both
Data Volume (Records) 10,000

1.2 Custom Object Attributes

Program Attributes
Name ZFIR_BANKMASTER_UPLOAD_TOP
ZFIR_BANKMASTER_UPLOADSEL
ZFIR_BANKMASTER_UPLOADF01
Description Bank Master Upload conversion
Logical Database
Development Package ZCONV_PROG
Editor Lock Yes No
Start using variant; Yes No
Fixed Point Arithmetic: Yes No
Unicode Yes No

OO ABAP Class/Interface Attributes:

Name ZCL_REUSE_BANKMASTER
Description Bank Master Upload
Development Package ZCONV_PROG
Interface Yes No
Instantiation Public
Class Type General Object
Final Yes No
Only Modeled? Yes No
Super Class ZCL_CONV_DASHBOARD

20-Oct-16 Page 4 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

Interface:
Interface Abstract Final Modeled Description
(Y/N) (Y/N) only
(Y/N)

N/A N/A N/A N/A N/A

Friends:
Friend Modeled Description
Only (Y/N)
N/A N/A N/A
Attributes:
Attribute Level Visibility Read Associated Initial Description
only Type Value
(Y/N)

GV_PARZA Instanc Public N PARZA Partner counter

e
Attribut
e
Methods:
SPLIT_FILENAME_EXTENSION Static Public Split the Filename and Extension
Method
CALL_CONV_PROGRAM Instanc Public Call Conversion Program
e
Method
CONSTRUCTOR Instanc Public Constructor
e
Method
GET_STEP_STATISTICS Static Public Get the Step Statistics
Method
PROPOSE_FILE_NAME Instanc Public Propose the Filenames
e
Method
SET_STEP_STATISTICS Static Public Set the Step Statistics
Method
SPLIT_INPUT_FILE Instanc Public Split Input File
e
Method
IMPORT_FILE Static Public Import the file
Method
GET_NODE_STATISTICS Instanc Protecte Get the Node Statistics
e d
Method
CHECK_CURRENT_STATUS Static Public Check the Current Status
Method
INPUT_FILE_REC_COUNT Instanc Public Input File Record Count
e
Method
UPD_STATISTICS_DATA Static Public Integration FM
Method
Events:
Event Type Visibility Description
NA NA NA NA

20-Oct-16 Page 5 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

Types:
Type Visibility Associated Description
type

N/A N/A N/A N/A

Table Parameters:
Parameter Name. Typing Type Optional Description
(Y/N)

N/A N/A N/A N/A N/A

Exceptions:
N/A N/A

20-Oct-16 Page 6 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

2 Technical Details

Transaction – ZCD, to run and select the node Class.

2.1 Technical Logic Flow

Start

Get Input from the User Selection

Screen

Upload File from the Selected Path

Show No Records Found

Check for Records No
error on the output screen

Yes

Create bank master data using BAPI_BANK_CREATE

Count the number of records in the file and build Audit

file

Create a BDC Session and display the

Session Name in the Output Screen

End

20-Oct-16 Page 7 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

2.2 Program Structure and Processing

INITIALIZATION -
1. Call utility method GET_STEP_STATISTICS of class ZCL_CONV_DASHBOARD getting the
statistics data in parameter EV_STEP_STAT and store in GS_STEP_STAT. This is the values
that are imported from the ZCD transaction to make sure that the current node is accessed
along with correct parameter for delimiter and header flag.
2. Populate the hidden selection screen parameters – Object (P_OBJECT), Sub object
(P_SUBOBJ), Guid (P_GUID), cycle GUID (P_CGUID), Header flag (P_HEADER) and
delimiter (P_DEL) from the statistics fetched in step 1 above.
3. Create object for ZCL_REUSE_PUR_REQ this calls the constructor and sets the statistics
data to memory ID “ZCLASS”
START-OF-SELECTION
4. Update the step statistics with the fields already fetched in step 1 along with timestamp
(START_TS), simulation/actual (ACTIVITY) and pass X to PROCESSINGSTAT. This is
followed by calling method SET_STEP_STATISTICS of class ZCL_CONV_DASHBOARD.
5. Upload data from the file path mentioned – this uses GUI_DOWNLAOD (in case of
presentation server) and OPEN/READ DATASET (in case of application server). The check is
made based on the radio buttons. The resultant file is stored in GT_FILE. The method for
download from presentation server is UPLOAD_PRESENTATION and from application server
is UPLOAD_APPLICATION of utility class ZCLG_COMM_UTILITIES.
6. Use BAPI_BANK_CREATE to process bank details uploaded from file
7. Get the count of the upload file records into LV_COUNT by using DESCRIBE TABLE.
8. Update the job log counter by calling method PROGRESS_CNT_FOR_JOBLOG of class
ZCL_CONV_UTILITIES
9. If the Test run flag (P_CH_SIM) is X then validate the data in the input file against check
tables. Else update the data into the system and create Purchase requisition by calling method
PROCESS using object created in step 3, importing the logs and counts.The return table is
read to check for success or failures. This information is used to populate logs and counts.
The values exported from this method are –
a. ET_SUCCESS_LOG
b. ET_ERROR_LOG
c. ET_SUCCESS_HEADER
d. ET_ERROR_HEADER
e. EV_SUCCESS_COUNT
f. EV_ERROR_COUNT
END-OF-SELECTION
10. Call method PREPARE_AUDIT_LOG of object created in step 3. This method prepares the
audit file displaying various counts and path where the files will be stored. The data populated
in file include –
a. Header data with Date, time and other details
b. Total number of records
c. No. of success records
d. No of error records
e. Success log file path

20-Oct-16 Page 8 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

f. Error log file path

g. Audit log file path
h. Data for error and success
This is stored in GT_AUDIT_LOG
11. Download the various log files using tables ET_ERROR_LOG, ET_SUCCESS_LOG fetched in
step 9, GT_AUDIT_LOG fetched in step 10
12. Write the audit data from the GT_AUDIT_LOG file using method WRITE_SUMMARY using
object created in step 3.
13. Call method INPUT_FILE_REC_COUNT using object created in step 3 and get the
REC_COUNT of step statistics structure. Fill in other values for ZCD display as follows –
a. REC_SUCCESS – EV_SUCCESS_COUNT
b. REC_ERROR – EV_ERROR_COUNT
c. AUDIT_FILENAME – P_AFILE (selection screen parameter)
d. ERROR_FILENAME = P_EFILE (selection screen parameter)
e. FILENAME = P_SFILE (selection screen parameter)
f. SPOOL – SY-SPONO
g. ACTIVITY – P_CH_SIM
h. END_TS – Timestamp.
14. Update step statistics using method SET_STEP_STATISTICS of class
ZCL_CONV_DASHBOARD
15. Update the interface data as below if the test run flag (P_CH_SIM) is not checked –
a. LOAD_COUNT – REC_COUNT]
b. OBJECTID = S4H_6
c. SUBOBJID - 6
16. Update statistics by calling method UPD_STATISTICS_DATA of class
ZCL_CONV_DASHBOARD passing IS_INTF_DATA with value populated in step 15

2.3 Selection Screen

Element Type Field name Default Values Validation

From – To (Required / Optional)
PARAMETER- Check Box CB_SIM
PARAMETER P_ALFILE
PARAMETER P_ELFILE
PARAMETER P_HEAD
PARAMETER P_PASER
PARAMETER P_PSER
PARAMETER P_SFILE
PARAMETER- Radio Button RB_APPLI
PARAMETER - Radio Button RB_PRES

20-Oct-16 Page 9 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

PARAMETER P_OBJECT No display

PARAMETER P_SUBOBJ No display
PARAMETER P_GUID No display
PARAMETER P_CGUID No display
PARAMETER P_DEL No display

2.4 Data Mapping

Provided in BODS technical specification.

2.5 Restart Capability

2.6 Verification and Reconciliation

Verification will be done via backend table BNKA to check if requisition has been created and data
is correct.

2.7 Technical Assumptions

2.8 Dependencies
N/A

2.9 Open Items

Open items would be logged in Commlog database in eRoom.

Issue No Date Opened Description Assigned To Status

N/A

20-Oct-16 Page 10 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

3 Error Handling, Exception Handling and Security Constraints

Error Handling
 N/A

Exception Handling

 N/A

Security Constraints
 N/A

20-Oct-16 Page 11 of 12 S4H_6_Bank_Master.docx

 S4H_6_Bank_Master

4 Unit Test Cases

Below test cases, depict end to end test scenario. The following unit test cases are indicative of test
scenarios covered and for related steps performed refer to technical unit test document.
Test Test Scenario Expected Results
Case Type Title
Number

Positiv Create Bank

1. Bank Details created in system
e Details

Negati
2 Incorrect data Error log populated and no Bank details created for wrong data
ve

20-Oct-16 Page 12 of 12 S4H_6_Bank_Master.docx