Flow Analysis of Payment Transactions in SAP

Reduction of Data with Some Testing Method in PT

XYZ
1st Rizki Nuzuli
2nd Warih Puspitasari
3rd Umar Yunan K.S. Hediyanto
School of Industrial and System
Engineering
Telkom University
Bandung, Indonesia
rizkinuzuli@gmail.com
warihpuspita@gmail.com
umaryunan@telkomuniversity.ac.id

Abstract— PT XYZ expands service with changing business
portfolio Fixed, Mobile, and Multimedia (FMM) to
Telecommunications, Information, Media and Edutainment
(TIME) to be competitive in the telecommunications market.
POTS services are one of those services with fixed wireline and
indiehome broadband are the main products. It due to
customers needs a wireline telephone service with fast
connectivity. This development provided directly increase the
number of customers. Accordingly, the SAP database on the
currently PT XYZ server has been taking the data with large
capacity. This resulted in an SAP system in organization
impaired operation within a certain period (downtime). To
overcome the problems, PT XYZ performs data reduction of
the payment transaction from current server to a new server.
A process is needed to ensure that each transaction unit using
reduced and migrated data to run properly on the new server.
Therefore, a testing process is needed to test every unit of the
payment transaction data reduction. Tests were conducted
using a black-box test, system integration test, and user
acceptance test to determine if there are defects or bugs in the
system. The expected results in this study are an analysis of
system testing of SAP applications.
Keywords— POTS, SAP, Black Box Test, System Integration
Test, User Acceptance Test
productivity by 37% in companies. Reduction of data are
carried out to improve the performance of the system
transactions. As an evaluation of the process, a test is
required to ensure the consistency of the payment transaction
flow against the data reduction. Testing conducted on SAP
applications and based on several methods of testing,
including black-box test to ensure input and output
transaction on the system, system integration system to test
the relation of the transaction unit on the system, and user
Acceptance test to know the user's suitability requirement to
any transaction on the system. The results of the test will be
analyzed to assess the suitability of the transaction flow
against the reduction data on the system.
II. METHODOLOGY
Based on the approach given in Fig.1 [2], the testing done
because the flow of transactions against the resulted data
runs properly on the new server. Black box test, system
integration test and, user acceptance test are the testing
method which used in this research. The concepts used to
strengthen the analysis and literature study from various
sources to know more about the problems experienced.

I. INTRODUCTION
PT XYZ which is engaged in the telecommunications
business in Indonesia has implemented ERP systems using
SAP ERP application to integrate business processes in
Human Resource Management and Finance. PT XYZ has
changed the business line from Fixed, Mobile, and
Multimedia (FMM) to Telecomunication, Information,
Media and Edutainment (TIME) and made the variance of
products become increased [1]. This resulted in the
segmentation of provided product services, one of which is a
POTS segmentation. Plain Old Telephone Services (POTS)
is a regular telephone service offered by PT XYZ, including
fixed-line and indiehome telephones. This led to the
increasing number of customers, especially in the customers
of POTS itself. Fig.1. Conceptual model of research

Payment transactions which become one of this III. LITERATURE REVIEW

organization’s main business activities have risen data of
customers. Currently, the massive data stored on the database
servers cause occurrence downtime on system. As a result,
business operations disrupted by 55% and reduced business

XXX-X-XXXX-XXXX-X/XX/$XX.00 ©20XX IEEE

A. ERP System
Enterprise Resource Planning System is a package of
information systems that can be configured to integrate
information between functional areas within an organization
[3]. The ERP system consists of business modules
supporting applications, which include sales and marketing,
production, accounting and finance, human resources, and
product development [4]. With the integration offered by
ERP, the decision making process can be done more
effectively and efficiently [5].
B. SAP
System Application and Production in Data Processing
SAP is a package of ERP system solutions in the form of
software released by German companies. This application
can manage information, thus it can be integrated between
parts of the company [6]. SAP consists of several modules
that are mutually integrated. Its main products include SAP
ERP Operation, which is the core ERP application solution
for procurement, sales, production, stock, shipping and
transportation of materials and SAP Business Suite, which is
a package of e-business application solutions and various
other applications [7].
C. Lifecycle Testing Phases
Lifecycle testing phases describe four main test phases,
such as test preparation phase, test design phase, test
execution phase, dan test evaluation phase [8].
Fig.2. Lifecycle testing phase
The following is an explanation of each of these phases:
• Test preparation phase, describes the supporting
components of the test preparation process. These
components include defining the scope and objective
of testing; identify testing strategies; identify risk of
testing; allocating test resources; and defining a test
schedule.
• Test design phase, identified and made test cases,
scenario tests, data tests and template test scripts. Test
cases and scenario tests are needed to test the
requirements that have been submitted. Test data is
needed to prepare input data for the test scenario. A
template test script is needed to create a test script
that functions as a guide when testing executed.
• Test execution phase, the black box, system
integration and user acceptance test processes occur
in this phase. The purpose of this testing process is to
check for system defects. The execution phase will
produce test documentation, report status testing and
handling defects.
• Test evaluation phase, ensures the passing of all
system tests from the results of the test reports.
Decision making from the evaluation results is done
after obtaining the analysis of the requirements that
Identify applicable funding agency here. If none, delete this text box.
have been tested. In this phase, an analysis of the
defects found is also carried out and ensures
documentation of each testing process.
D. Type of System Test
The following are some types of application testing:
• Black box test, is a test that sees system as a black
box, which means the testers do not need to know
how the system works internally. This test focuses on
the functionality of the module [9]. Functionality is
tested based on requirements that contain the
expected features or functions. This test requires a
test case prepared by testing team and client [10].
• System integration test (SIT), is a test of the relevance
and connectedness of modules in a software system.
A system consists of several modules that are
interconnected to achieve one goal. Modules can be
subroutines, functions, procedures, classes, or a
collection of basic elements that are put together to
provide services to a system. The main purpose of
this test is to create a system that is stable in its
environment, therefore it can withstand the rigidity of
testing systems in the actual environment [11].
• User acceptance testing (UAT), is a test from the
perspective of end-users so that they will interact with
the system in their environment. UAT consists of re-
executing integration tests carried out previously with
end-users, system demonstrations, or making new test
cases [12], [13].
IV. RESULT AND DISCUSSION
A. Test Design Phase
• Use case
Use case diagram in Fig.3 describes the events
that occur in the system carried out by the user
role. Use case diagram of payment transaction has
two roles in running the system, finance division
and IPC front desk. The finance division can do a
clearing down payment, release security deposit,
check customer payment, and clearing claim on
SAP applications. Whereas the IPC front desk can
do a process full payment or partial, cancel
payment, process installment, process down
payment, process security deposit, and process
claim on IPC website application.
 • Test case
The test case is prepared based on the results of
the use case analysis and the test scenario that was
made. The test case to support testing to fit the
specified case are given in Table II.
TABLE II. TEST CASE OF PAYMENT
TRANSACTION POTS
Test
Expected
Case Test Case System Transaction
Result
ID
TC01 Display SAP FPL9 Account
customer Display:
payment Basic List
account displayed
according
to Business
Partner
Fig.3. Use case diagram
TC02 Proceed IPC Pay one by Full
• Test scenario full one payments
payment saved and
The test scenario is structured as a scenario for invoices
testing. This scenario is based on the results of a use displayed
case analysis. The scenario of payment transaction
tests are given in Table I. TC03 Proceed IPC Correction / Payment
TABLE I. TEST SCENARIO OF PAYMENT cancel cancel canceled
TRANSACTION POTS payment transaction based on
receipt
Use Case Test Expected number
Scenario ID
ID Scenario Result
UC01 ST01 Display Customer TC04 Proceed IPC Pay one by Partial
customer payment partial one payments
payment account payment saved and
account displayed invoices
UC01, ST02 Proceed full Full customer displayed
UC02 payment payment is
paid TC05 Proceed IPC DP / SD Down
UC01, ST03 Proceed Customer down payment
UC03 cancel payment payment saved and
payment transaction invoices
canceled displayed
UC01, ST04 Proceed Partial
UCO4 partial customer TC06 Clearing SAP FPE1 Post
payment payment is down clearing
paid payment down
UC01, ST05 Proceed Down document payment
UC05, down payment document
UC06 payment customer
payment is TC07 Proceed IPC DP / SD Security
paid security deposit
UC01, ST06 Proceed Security deposit payments
UC07, security deposit saved and
UC08, deposit customer invoices
UC09 payment is displayed
paid
UC01, ST07 Register Customer TC08 Release SAP FPRL Security
UC10 installment installments security deposit
registered deposit document
UC01, ST08 Proceed Customer document released
UC11, claim claim
UC12 registered TC09 Clearing SAP FPE1 Post
security clearing
deposit security
document deposit
 document Thus, an analysis of the test results is carried out to
determine the test passing of the transaction functionality
TC10 Registering IPC Register Registration that runs on the application. to design a good application test,
customer installment of customer it is necessary to use a use case to help determine the test
installment installments case that is suitable for system conditions. Testing of system
saved integration is done twice by the developer team to increase
the passing rate of testing. In addition, this is also done to
TC11 Registering IPC Claim Registration prevent the re-testing of system integration before being
customer of customer submitted to testing carried out by end-users. Therefore, it’s
claim claim saved
needed black box test and system integration test testing
methods to ensure system integration, as well as user
TC12 Clearing SAP FPE1 Post
acceptance test testing to ensure system functionality based
claim clearing
on end user requirements.
claim
document
REFERENCES
[1] PT Telekomunikasi Indonesia, Tbk, “Mempercepat Ekonomi
Digital Indonesia,” PT Metra Digital Media (MD MEDIA),
B. Test Results And Defects Handling Jakarta, 2017.
The test results will be an assessment to determine the [2] A. R. Hevner, S. T. March and J. Park, "Design Science in
passing of testing based on the specified requirements. The Information System Research," MIS Quarterly, pp. 75-105,
2004.
report on the test results are given in Table III.
[3] J.C. Essila. (2018). “The Dynamics of Electronic Supply
TABLE III. TEST REPORT OF PAYMENT TRANSACTION Chains and Enterprise Resource Planning Systems: The New
POTS Business Challenge”. International Journal of Computers in
Clinical Practice, vol. 3, pp. 49-50, 2018.
Test Result
[4] H. Herispon, “Perencanaan Sumberdaya Perusahaan
Scenario Test Title Black Box
SIT UAT (Enterprise Resource Planning) (The Contributions of Drs.
ID Test R. Djokopranoto)”, 2018.
ST01 Display customer Passed Passed Passed [5] W. Dhewanto and Falahah, “ERP (Enterprise Resource
payment account Planning): Menyelaraskan Teknologi Informasi dengan
ST02 Proceed full payment Passed Passed Passed Strategi Bisnis”, Informatika, Bandung, 2007.
ST03 Proceed cancel Passed Passed Passed [6] SAP01, F, “SAP01 Fundamental”, SAP AG, German, 2006.
payment [7] J. Boeder, and B. Groene, “The Architecture of SAP ERP:
ST04 Proceed partial Passed Passed Passed Understand how successful software works”, tredition, 2014.
payment [8] S. Dalal and R. S. Chhillar, “Software Testing-Three P’S
ST05 Proceed down payment Passed Passed Passed Paradigm and Limitations,” International Journal of
ST06 Proceed security Passed Passed Passed Computer Applications, pp. 49-54, 2012.
deposit [9] V. John, and H. Done, “Principles and Practice of Software
ST07 Registry installm-ent Passed Passed Passed Testing: Insights into Testing”, Educreation Publishing,
2018.
ST08 Proceed claim Passed Passed Passed
[10] S. Desai, and A. Srivastava, “SOFTWARE TESTING : A
Compliance Rate 100%
Practical Approach”, PHI Learning Pvt. Ltd., 2016.
[11] K. Naik, and P. Tripathy, ”Software Testing and Quality
Assurannce” John Wiley & Sons, Inc., New Jersey, 2011.
[12] J. Boeder, and B. Groene, “The Architecture of SAP ERP:
Understand how successful software works”, three edition,
2014.
[13] J. Fajarado, and E. Dustin, “Testing SAP R/3 : A Manaager’s
step-by-step Guide.“ John Wiley & Sons, Inc., New Jersey,
2007.
Based on the report and calculation on the results above,
the compliance rate of the test is 100%. This concludes that
the black box test, SIT, and UAT tests have passed the test in
the absence of defects found.

V. CONCLUSION
The existence of a testing process on an application
system development especially in the process of data
reduction in POTS payment transactions can support the
level of acceptance of the application system. By testing the
transaction flow, application functionality will be defined.