flr. ctp building, e: [email protected] optimind ... · software requirements specification...

2nd Flr. CTP Building,

5 Gil Fernando Ave., Marikina City

P: (63) 2 6820173, (63) 2 3879200

E: [email protected]

OPTIMIND TECHNOLOGY SOLUTIONS

Software Requirements Specification – 1SS-C3S Mobile Application Phase 1

Once this form is signed, it authorizes Optimind’s Development team to finalize the project and prepare it to the next phase

About the Client

Company Name : United Laboratories Inc.

Address 66 United Street, Mandaluyong City, Metro Manila

Contact Person : Ms. Hershey Baluyot

Telephone No. : +632 8581000 loc. 8681

E-mail Address : [email protected]

Purpose

The purpose of this document is to serve as a guide to designers, developers and testers who are

responsible for the engineering of the EXM Mobile project. It should give the engineers all of the

information necessary to design, develop and test the software.

Scope

This document contains a complete description of the functionality of the EXM Mobile project. It

consists of use cases, functional requirements and non-functional requirements, which, taken

together form a complete description of the software.

System Overview

The EXM Mobile app aims to speed up the process in approving / rejecting selected 1SS and C3S

transactions. The application will run both on android and iOS phones and tablets and will be used

internally by approvers within Unilab’s organization.

Use Cases

Name UC-1: Main Application Login

Summary Login to access the system

Rationale To filter transactions that will be displayed within the mobile app based on

username credentials and to enforce access security.

Users All Users

Preconditions 1. App is already installed in the user’s device and no previous login data is

saved.

2. User has an active account in Unilab’s Active Directory.

tel:%2B632%208581000



P: (63) 2 6820173, (63) 2 3879200



3. App is connected online.

Basic Course of

Events

1. User opens the app by clicking on the icon

2. User enters username and password and clicks Login button

3. FOR 1ST

TIME USERS: If username and password matches, user is

redirected to the 1SS and C3S Login Activation screen; OTHERWISE, user

is redirected to the UC-4: Pending Items (Main View)

4. If username and password did not match, user is shown an access denied

error

Post Conditions Upon successful login, the user will proceed to 1SS and C3S Login Activation

screen OR to Pending Items (Main View)

Other Notes 1. If the app was successfully logged out but the UC-2: 1SS and C3S Login

Activation had been verified successfully, this will be the default view

upon re-opening the app

2. If the app was closed but was not logged out, user directly proceeds to

UC-4: Pending Items (Main View) upon re-opening the app

Name UC-2: 1SS and C3S Login Activation (Account Settings)

Summary Login to activate access to 1SS and C3S

Rationale To activate connection to both systems, i.e. 1SS and C3S, and be able to filter

and retrieve associated transactions linked to the logged in user

Users All Users

Preconditions 1. User has already logged into the mobile app using his Active Directory

account in the Main Application Login

2. App is connected online.

Basic Course of

Events

1. User enters his 1SS username and password and clicks “Activate” button

or icon.

2. User enters his C3S username and password and clicks “Activate” button

or icon.

3. If the username and password matches, notification will be shown and

user is redirected to UC-4: Pending Items (Main View)

4. If the username and password did not match, user is shown an access

denied error

Post Conditions Upon successful login, the user will be directed to the Pending Items (Main

View). User may also access other menu items of the app.

Other Notes 1. User may choose to activate only 1 system – either 1SS or C3S

2. Once the user is validated, this screen will no longer be displayed upon

logging in Main Application Login page but can still be accessed via

Account Settings

Name UC-3: Logout

Summary Logout of the app

Rationale To allow the users extra security by logging out of the application

Users All Users

Preconditions User has already logged into the mobile app using at least his Active Directory

account



P: (63) 2 6820173, (63) 2 3879200



Basic Course of

Events

1. User clicks on menu on top left

2. User clicks on Logout

3. User gets redirected to UC-1: Main Application Login

Post Conditions 1. Upon logout, user may only access the Main Application Login screen of

the app of re-opened

2. If the app was closed but was not logged out, user directly proceeds to

UC-4: Pending Items (Main View) upon re-opening the app

Name UC-4: Pending Items (Main View)

Summary The Pending Items view is the default screen that will be displayed whenever

a user opens the app. This view shows all pending transactions for approval

from C3S and 1SS. From this screen, the user will be able to do the following:

1. search for specific transaction/s

2. approve single or multiple transaction/s

3. reject single or multiple transaction/s

4. comment on a rejected transaction/s

Rationale To provide a quick view of all pending transactions that require the user’s

approval

Users All Users

Preconditions 1. User has already logged into the mobile app via Main Application Login

and 1SS and C3S Login Activation

2. Mobile App synchronized - manually through the synchronize button

from the menu if auto-sync is disabled.

Basic Course of

Events

View Pending Transactions Summary

1. User clicks on search and types a keyword

a. List will be filtered based on what matches the keyword as the user

types

b. Search will match the following fields: Requestor, Particulars, and

Reference No.

OR:

1. User scrolls through the list that shows the following details for each

transaction:

a. Reference No.

b. Request Type (Acronym) – Particulars*

c. Requestor’s Name

d. Amount

e. Date/Time Stamp/Age of the request (in hours, days or weeks)

*Refer to Appendix A for the Transaction Acronyms

For other actions within this view, refer to UC-6, UC-7, UC-8, UC-19 and UC-20

Other Conditions Depending on the preference saved, the main view will either list C3S or 1SS

only or it can list both (Refer to UC-13 and UC-16)

Post Conditions none



P: (63) 2 6820173, (63) 2 3879200



Name UC-5: Menu

Summary The menu is a list of items that can be accessed within the app. Items that can

be accessed are: Pending Transactions, C3S, 1SS, Settings, Logout

1. Account Settings

2. Pending Items (Main View)

3. Outbox

4. Auto-Sync

5. Logout

Rationale Screen for the users to access different functionalities within the app.

Users All Users

Preconditions User has already logged into the mobile app using Active Directory

Basic Course of

Events

1. User clicks on menu on top left and selects desired action:

a. Account Settings

b. Pending Items (Main View)

c. Outbox

d. Auto-Sync (on/off switch)

e. Logout

2. User gets redirected to the corresponding view

Post Conditions Redirect user to selected view

Name UC-6: Quick Approve Transaction

Summary Quickly approve a transaction without the need to view details

Rationale Two-step way to approve a transaction

Users All Users


Basic Course of

Events

1. User goes to main view

2. User selects the transaction (either by scrolling or searching) to be

approved

3. User swipes right over the selected transaction cell

4. User is presented with a check button

5. User click check button that suggests approval of transaction

6. User is presented with dialog box to confirm if OK to approve or CANCEL

to go back to Pending Items (Main View) screen

7. User clicks on OK to confirm approval or Cancel to return to main view

and undo action

Post Conditions 1. Upon clicking OK, the transaction will be tagged as Approved:

a. If online, it will be sent back to respected back-end system and be

removed from the list

b. If offline, it will be marked until the mobile app is automatically or

manually synchronized to the back-end system

2. Upon clicking CANCEL, the user will be redirected back to the Main View

Name UC-7: Quick Reject Transaction

Summary Quickly reject a transaction without the need to view details

Rationale Two-step way to reject a transaction



P: (63) 2 6820173, (63) 2 3879200



Name UC-7: Quick Reject Transaction

Users All Users


Basic Course of

Events


2. User selects the transaction (either by scrolling or searching) he wants to

reject

3. User swipes left over the transaction cell

4. User is presented with 2 buttons:

a. Return – button activated for 1SS transactions only

b. Reject

5. User selects the Reject button

6. User is required to input comments or reason for rejection

7. User is presented with dialog box to confirm if OK to send or CANCEL to

go back to Pending Items (Main View) screen

8. User clicks on OK to confirm rejection or Cancel to return to main view

and undo action.

Post Conditions 1. Upon clicking OK, the transaction will be tagged as “Rejected”:






Name UC-7: Quick Return Transaction (1SS)

Summary Quickly send back a 1SS transaction for resubmission without the need to

view details

Rationale Two-step way to return a transaction

Users All Users


Basic Course of

Events


2. User selects the transaction (either by scrolling or searching) to be

returned

3. User swipes left over the selected transaction cell

4. User is presented with 2 buttons:

c. Return – button activated for 1SS transactions only

d. Reject

5. User selects the Return button

6. User is required to input comments or reason for returning and

requesting for resubmission

7. User is presented with dialog box to confirm if OK to send or CANCEL to

go back to Pending Items (Main View) screen

8. User clicks on OK to confirm return or Cancel to go back to main view

and undo action.

Post Conditions 1. Upon clicking OK, the transaction will be tagged as “Returned for

Resubmission”:

c. If online, it will be sent back to respected back-end system and be



P: (63) 2 6820173, (63) 2 3879200




d. If offline, it will be marked until the mobile app is automatically or



Name UC-9: View Transaction Details

Summary View all information associated with a transaction

Users All Users

Preconditions User has selected a transaction from the main view

Basic Course of

Events

1. User selects the transaction by clicking on the transaction cell

2. User sees all information related to a transaction including breakdown of

transaction items

Refer to Appendix B for Field Mapping.

Post Conditions 1. User is presented with selected transaction’s details

Name UC-10: Approve Transaction from Transaction View

Summary Approve a transaction from the detailed transaction view

Rationale Approve transaction upon reviewing its details

Users All Users


Basic Course of

Events

1. User reviews transaction and clicks on approve request

2. User is presented with a dialog box to confirm if OK to proceed or

CANCEL to go back to Transaction View screen

3. User clicks OK to confirm or Cancel

4. User will be shown a success message

Post Conditions 1. Upon clicking OK, a success message will be shown and the transaction

will be tagged as Approved:


removed from the list.



User will be redirected back to main view


Name UC-11: Reject Transaction from Transaction View

Summary Reject a transaction from the detailed transaction view

Rationale Reject transaction upon reviewing its details

Users All Users


Basic Course of

Events

1. User reviews transaction and clicks on reject request

2. User is shown text box to enter comment or reason for rejection




5. User is shown a success message



P: (63) 2 6820173, (63) 2 3879200




will be tagged as Rejected:



d. If offline, it will be marked until the mobile app is automatically or




Name UC-12: Return Transaction from Transaction View (1SS)

Summary Return transaction from the detailed transaction view

Rationale Return transaction upon reviewing its details

Users All Users


Basic Course of

Events

1. User reviews transaction and clicks on return request

2. User will be shown text box to enter comment or reason for returning




5. User will be shown a success message


will be tagged as Returned for Resubmission:







Name UC-13: Preferences OK but note that the design and use case did not match

Summary Update user’s preferences of the app

Rationale Allow user to set his own preference on how the transactions are displayed and synchronized

Users All Users


Basic Course of Events

1. User clicks on menu from the top left 2. User clicks on Preferences 3. User select his default settings for Main View list – display C3S only,

display 1SS only or display both C3S and 1SS 4. User select his default settings for synchronize – Manual or Automatic

Post Conditions Automatic saving of preferences upon selection

Name UC-14: Manual Sync

Summary Manually synchronize data from phone and server

Rationale Synchronize data between mobile app and the central 1SS and C3S database

Users All Users



P: (63) 2 6820173, (63) 2 3879200




Basic Course of

Events

1. User clicks on synchronize on the top menu

2. Updated data is downloaded and uploaded from the web server

3. User is presented with the latest updates from C3S and 1SS

User select his default settings for synchronize – Manual or Automatic

Post Conditions Server and mobile data should have the same set of data

Name UC-15: Notifications

Summary Alerts the user about the no. of pending items in the application

Rationale To remind the user to approve/reject transactions

Users All Users

Preconditions 1. User is logged into the mobile app using Active Directory

2. Mobile Application is opened

Basic Course of

Events

User checks notifications by clicking on the menu screen

Name UC-16: Main View Filter

Summary Filter transactions by type – C3S, 1SS or Both

Rationale Allows the user to filter the list by the type of transactions they need

Users All Users

Preconditions User has already logged into the mobile app using Active Directory and C3S

login credentials

Basic Course of

Events

1. User clicks on filter from the top menu

2. User selects an option from one of the three: 1SS, C3S, All

3. List of transactions are updated based on the selected filter

Name UC-17: Pending Items (Main View) Search

Summary Allows a user to search for a transaction by entering a keyword that will

match either the particular or the requestor’s name

Rationale Allows the user to easily find a transaction that they are looking for

Users All Users

Preconditions User has already logged into the mobile app using Active Directory and C3S

login credentials

Basic Course of

Events

1. User clicks on search from the top menu

2. User enters the keyword

3. List is refreshed with matching keywords based on its search from the

following fields:

a. Requestor

b. Particulars

c. Reference No.

Name UC-18: Validate Transaction from Transaction View (C3S-CCLF)

Summary Approve or reject a sub-transaction from the detailed transaction view of

C3S-CCLF

Rationale Approve the whole transaction or reject/approve selected items from C3S-



P: (63) 2 6820173, (63) 2 3879200



CCLF transaction view

Users All Users

Preconditions User has selected a C3S-CCLF transaction from the main view

Basic Course of

Events

1. User approves or reject single sub-transactions

a. User clicks on Validate that corresponds to a single sub-transaction.

b. User clicks approve or reject

c. User is shown a confirmation box

d. User clicks OK or Cancel to confirm action

2. User approves all sub-transactions

a. User clicks on Submit and Approve the Rest button

b. User is shown a confirmation box

c. User clicks OK or Cancel to confirm action

Post Conditions Upon clicking Submit and Approve the Rest button, all sub-transactions that

were not validated will be automatically approved.

Name UC-19: Approve Multiple Transactions from Pending Items (Main View)

Summary Approve multiple transactions from Pending Items (Main View)

Rationale Quickly approve multiple transactions without reviewing them.

Users All Users

Preconditions User has already logged into the mobile app via Main Application Login

Basic Course of

Events

1. User clicks on the radio button corresponding to the transaction/s that

he wants to approve.

2. User clicks on Approve button at the bottom of the screen

3. User is shown a confirmation box

4. User clicks on OK or Cancel to confirm action or undo selection


will be tagged as Approved:


moved to Outbox first until completely removed from any list.

b. If offline, it will be moved to Outbox and be marked until the mobile

app is automatically or manually synchronized to the back-end

systems

2. Upon clicking CANCEL, all radio buttons will be cleared

Name UC-20: Reject Multiple Transactions from Pending Items (Main View)

Summary Reject multiple transactions from Pending Items (Main View)

Rationale Quickly reject multiple transactions without reviewing them.

Users All Users

Preconditions User has already logged into the mobile app via Main Application Login

Basic Course of

Events

1. User clicks on the radio button corresponding to the transaction/s that

he wants to reject.

2. User clicks on Reject button at the bottom of the screen

3. User is required to enter comment or reason of rejection per transaction

4. Once complete, User is shown a confirmation box

5. User clicks on OK or Cancel to confirm action or undo selection



P: (63) 2 6820173, (63) 2 3879200




will be tagged as Rejected:


moved to Outbox first until completely removed from any list.

d. If offline, it will be moved to Outbox and be marked until the mobile

app is automatically or manually synchronized to the back-end

systems

2. Upon clicking CANCEL, all radio buttons will be cleared

Name UC-21: Outbox

Summary Shows transactions that are not yet synchronized with the main system

Rationale To show the user the list of transactions that were not yet synchronized so

they can connect to the internet and trigger manual sync or wait for the auto-

sync to trigger.

Users All Users

Preconditions User approved, rejected or returned on a transaction.

Post Conditions Upon completion of synchronization, outbox will be empty.

Name UC-22: Auto-sync

Summary Set auto-sync settings. If on, the sync uploads and downloads changes to and

from the server every 30 minutes.

Rationale Allow users to turn auto sync on/off

Users All Users

Preconditions 1. User has already logged into the mobile application via Main Application

Login

2. There is an active internet connection

3. The app is opened

Basic Course of

Events

1. User clicks on the menu.

2. User turns auto-sync on or off

Note: Auto-Sync preference may also be accessed from Preferences (UC-13)

Name UC-23: Alert/ Reminder

Summary Indicator from app icon that shows the no. of pending items that needs to be

approved

Rationale Quickly show the user the no. of pending items to be approved within the app

Users All Users

Preconditions 1. User has already logged into the mobile app via Main Application Login

2. Mobile App is opened

Basic Course of

Events

1. User opens his mobile phone.

2. User looks at the app icon.

3. User is alerted in his Notification bar twice a day



P: (63) 2 6820173, (63) 2 3879200



List of Web Services

1. retrieve_pending_transactions

input parameters:

◦ username

◦ password

◦ type

▪ 1 -> all

▪ 2 -> C3S only

▪ 3 -> 1SS

output

◦ json format of transaction list with details of each

approve - upload all approved transaction

input parameters:

username

password

o transaction_list (JSON FORMAT of transactions to be

approved)

transaction_id

date_approved

comment (optional, can be null)

o output:

update local database of server based on

the current approval behavior

json format of response with error or

success message

reject - upload all rejected transaction

input parameters:

o username

o password


rejected)

o transaction_id

o date_rejected

o comment (optional, can be null)

output:

o update local database of server based on the current

rejection behavior

o json format of response with error or success

message

comment

input parameters:

o username

o password


updated)



P: (63) 2 6820173, (63) 2 3879200



o transaction_id

o comment

output:

o update local database of server based on the current

add comment behavior

o json format of response with error or success

message

verify_login_active_directory

input parameters:

o username

o password

output:

o json format of verification (invalid or login

successful)

verify_login_system

input paramters:

o username

o password

o system

2 - C3S

3 - 1SS

output:

◦ json format of verification (invalid or login successful)



P: (63) 2 6820173, (63) 2 3879200



APPENDIX A – TRANSACTION ACRONYMS

ACRONYM DESCRIPTION

LCAF Liquidation of Cash Advance

RCAF Request for Cash Advance

RENP Reimbursement of Non-Project Based

CCRF Credit Card Reservation Form

CCLF Credit Card Liquidation Form



P: (63) 2 6820173, (63) 2 3879200



APPENDIX B – FIELD MAPPING

FIELD NAME DESCRIPTION DATABASE TABLE

ONE STOP SHOP (1SS)

REQUEST FOR CASH ADVANCE (RCAF)

1. Transaction Type /

DVF Type

Selected Transaction Type upon

creation of DVF transaction

tblDVFHeader.TrxTypeId,

tblExeApprovalHeader.TrxTypeID,

tblExeTrxList.TrxTypeID get TrxDesc in

tblMaintenanceTrxType

2. Vendor/Requestor Requestor of RCAF transaction tblDVFHeader.VendorId,

tblExeApprovalHeader.RequestorID get

VendorName in tblSapVendor OR

tblDVFOneTimeVendor

3. Company Selected Company for the

transaction

tblDVFHeader.CompanyId get CompanyDesc

in tblMaintenanceCompany

4. Division Selected Division for the

transaction

tblDVFHeader.DivisionId,

tblExeApprovalHeader.DivisionID get

DivisionDesc in tblMaintenanceDivision

5. Preparer Logged-in User’s Name upon

creation of transaction

tblDVFHeader.PreparerId get Name in

tblSecProfile

6. Transaction ID /

DVF Id

System generated ID after

submission of DVF transaction

tblDVFHeader.TrxId, tblDVFDetail.TrxId,

tblDVFAllocation.TrxId,

tblDVFDetailAlloc.TrxID,

tblBreakdownOfExpenses.TrxId,

tblExeApprovalHeader.TrxID,

tblExeTrxList.TrxID, tblExeTrxList.RCAFTrxID

7. Transaction Date /

Date Created

Current Date / System Date tblDVFHeader.DateCreate,

tblExeApprovalHeader.DateCreated

8. Charge to Year Year wherein the transaction will

be charged

tblDVFHeader.Year, tblExeTrxList.Year

9. Type Of Cash

Advance

Selected RCAF Type tblDVFHeader.RCAFTypeId get RCAFDesc in

tblRCAFType

10. Currency Selected Currency for the

transaction

tblDVFHeader.CurrencyId,

tblExeTrxList.Currency

11. Forex Forex Rate from SAP tblDVFHeader.ForexRate,

tblExeTrxList.ForexRate

12. Cost Center Selected Cost Center for the

transaction

tblDVFDetail.CostCenterId,

tblDVFAllocation.CostCenterId,

tblDVFDetailAlloc.CostCenterId,

tblExeTrxList.CostCenterID get

CostCenterDesc in tblSapCostCenter



P: (63) 2 6820173, (63) 2 3879200




13. Internal Order Internal Order of the selected Cost

Center

tblDVFDetail.InternalOrderId,

tblDVFAllocation.InternalOrderId,

tblDVFDetailAlloc.InternalOrderId,

tblExeTrxList.InternalOrderID get

InternalOrderDesc in tblSAPInternalOrder

WHERE InternalOrderTypeID = 'B'

14. Amount / Cash

Advance Amount

Total RCAF Amount tblDVFHeader.TotalRequestedAmount,

tblDVFHeader.TotalNetAmount,

tblDVFDetail.RequestedAmount,

tblDVFDetail.NetAmount,

tblDVFAllocation.RequestedAmount,

tblDVFAllocation.NetAmount,

tblDVFDetailAlloc.RequestedAmount,

tblDVFDetailAlloc.NetAmount,

tblExeApprovalHeader.Amount,

tblExeTrxList.Amount,

tblExeTrxList.NetAmount

15. Remarks /

Particulars / Cash

Advance Purpose

RCAF Description tblDVFHeader.Remarks,

tblDVFDetail.Remarks,

tblDVFAllocation.Remarks

16. Activity Type Internal Order’s Activity Type tblSapInternalOrder.ActivityTypeID WHERE

InternalOrderID = 'Internal Order ID' AND

YEAR = 'Charge to Year' get ActivityTypeDesc

in tblSAPActivityType

LIQUIDATION OF CASH ADVANCE (LCAF)

1. Transaction Type /

DVF Type







2. Vendor/Requestor Requestor of LCAF transaction tblDVFHeader.VendorId,



tblDVFOneTimeVendor

3. RCAF Reference RCAF Reference of the LCAF tblDVFHeader.Reference,

tblExeTrxList.RCAFTrxID

4. Company Company associated to the RCAF

Reference

tblDVFHeader.CompanyId, get CompanyDesc


5. Division Division associated to the RCAF

Reference




6. Remarks /

Particulars

LCAF Description tblDVFHeader.Remarks



tblDVFHeader.PreparerId, get Name in

tblSecProfile



P: (63) 2 6820173, (63) 2 3879200




8. Transaction ID /

DVF Id







tblExeTrxList.TrxID


Date Created



10. Charge to Year Year associated to the RCAF

Reference


11. Currency Currency associated to the RCAF

Reference



12. Forex Rate Forex Rate associated to the RCAF

Reference

tblDVFHeader.ForexRate,


13. Internal Order ID* Intrnal Order associated to the

RCAF Reference







14. Activity Type* Selected Activity Type for the

transaction

tblDVFDetail.ActivityType,

tblDVFAllocation.ActivityType,

tblDVFDetailAlloc.ActivityType get

ActivityTypeDesc in tblSAPActivityType

15. GL Expense* Selected Expense Account for the

transaction

tblDVFDetail.GLAccountId,

tblDVFAllocation.GLAccountId get

GLAccountDesc in tblSapGLAccount

16. Vendor* Selected Vendor for the

transaction

tblDVFDetail.VendorId,

tblDVFAllocation.VendorId get VendorName

in tblDVFOneTimeVendor OR tblSapVendor

17. Gross Amount* Requested Amount per item tblDVFDetail.RequestedAmount,




tblExeTrxList.Amount

18. Total Gross

Amount

Total Requested Amount tblDVFHeader.TotalRequestedAmount

REIMBURSEMENT NON-PROJECT BASED (RNP)

1. Transaction Type/

DVF Type







2. Vendor/Requesto

r

Requestor of RNP transaction tblDVFHeader.VendorId,



tblDVFOneTimeVendor



P: (63) 2 6820173, (63) 2 3879200




3. Company Selected Company for the

transaction

tblDVFHeader.CompanyId, get CompanyDesc


4. Division Selected Division for the

transaction




5. Remarks /

Particulars

RNP Description tblDVFHeader.Remarks



tblDVFHeader.PreparerId, get Name in

tblSecProfile

7. Transaction ID /

DVF Id







tblExeTrxList.TrxID


Date Created



9. Charge to Year Year wherein the transaction will

be charged


10. Currency Selected Currency for the

transaction



11. Forex Rate Forex Rate from SAP tblDVFHeader.ForexRate,


12. Internal Order* Internal Order of the selected Cost

Center







13. Activity Type* Selected Activity Type for the

transaction

tblDVFDetail.ActivityType,

tblDVFAllocation.ActivityType,

tblDVFDetailAlloc.ActivityType get

ActivityTypeDesc in tblSAPActivityType

14. GL Expense* Selected Expense Account for the

transaction

tblDVFDetail.GLAccountId,

tblDVFAllocation.GLAccountId get

GLAccountDesc in tblSapGLAccount

15. Vendor* Selected Vendor for the

transaction

tblDVFDetail.VendorId,

tblDVFAllocation.VendorId get VendorName

in tblDVFOneTimeVendor OR tblSapVendor

16. Gross Amount* Requested Amount per item tblDVFDetail.RequestedAmount,




tblExeTrxList.Amount

17. Total Gross

Amount

Total Requested Amount tblDVFHeader.TotalRequestedAmount



P: (63) 2 6820173, (63) 2 3879200




CORPORATE CREDIT CARD SYSTEM (C3S)

CREDIT CARD REQUISITION FORM (CCRF)

1. CCRF Title Name of the Activity/CCRF tbl_ACTIVITIES.ACTIVITYNAME

2. IO Name Name of the IO tbl_NONPROJ_INTERNAL_ORDERS.INTERNAL

ORDERNAME

3. Requested By Name of the User who requested

the CCRF

tbl_ACTIVITIES.REQUESTORID mapped to

tbl_USERS.FULLNAME

4. Department User's Department tbl_DEPARTMENTNAME.DEPARTMENTS

5. For the Period CCRF Date From tbl_ACTIVITIES.DATEFROM

CCRF Date To tbl_ACTIVITIES.DATETO

6. Country Country Code where the

Transaction is done

tbl_ACTIVITIES.COUNTRYCODE

7. User Remarks Remarks of User tbl_CARD_TRANSACTIONS.USERREMARKS

8. CCRF No Credit Card Requisition Form

Number

tbl_ACTIVITIES.ACTIVITYID

9. IO No IO Number tbl_NONPROJ_INTERNAL_ORDERS.INTERNAL

ORDERNO

10. Rqsted on Date the CCRF is created tbl_ACTIVITIES.REQUESTORDATE

11. Emp Id Cardholder's Employee ID tbl_USERS.EMPLOYEEID

12. Requested

Amount

Amount of the Requested Budget tbl_ACTIVITIES.ACTIVITYBUDGET

CREDIT CARD LIQUIDATION FORM (CCLF)

1. Employee Name of the User who liquidated

the transaction

tbl_USERS.FULLNAME

2. Activity Name of the Activity/CCRF tbl_ACTIVITIES.ACTIVITYNAME

3. Trn Count Number of Transactions in a CCLF tbl_CCLF.TRANSCOUNT

4. Total Amt Total Amount of charged

transactions

tbl_CCLF.TOTALAMOUNT

5. Trans ID Transaction ID tbl_CARD_TRANSACTIONS.CARDTRANSID

6. Trans Dte Date of credit card transaction tbl_CARD_TRANSACTIONS.TRANSDATE

7. Post Dte CitiBank Card transaction posting

date

tbl_CARD_TRANSACTIONS.POSTDATE

8. Merchant Name Name of the vendor tbl_MERCHANTS.MERCHANTNAME

9. Post Amt Amount of charged transaction

per downloaded data from

Citibank (per transaction)

tbl_CARD_TRANSACTIONS.POSTAMOUNT

10. OR No OR number of supporting

document

tbl_CARD_TRANSACTIONS.ORNO

11. Activity* Name of the Activity/CCRF tbl_ACTIVITIES.ACTIVITYNAME

12. Project* Name of the Project tbl_PROJECTS.PROJECTNAME

13. GL Account* General Ledger Account tbl_GL_ACCOUNTS.GLNAME

14. Tax Amt* Tax Amount tbl_CARD_TRANS_ENTRIES.TAXAMOUNT

15. Gross Amt* Gross Amount tbl_CARD_TRANS_ENTRIES.GROSSAMOUNT

*in data grid/ table format



P: (63) 2 6820173, (63) 2 3879200



I HEREBY CERTIFY that the above functions has been checked and verified as per client specifications.

Wendy S. Ang

President

Signature Over Printed Name Position Date Signed

CLIENT REPRESENTATIVE SIGN OFF

I HEREBY CERTIFY that I have fully reviewed the SRS specifications. I confirm that I have had significant input into the SRS and that it is now a satisfactory level to move on the next stage.

I understand that once this has been finalized and SRS Sign off form has been signed any changes to the functions may be subject to the Developer’s current standard rates, or as outlines in the contract between the Client and the Company.

Signature Over Printed Name Position Date Signed

flr. ctp building, e: [email protected] optimind ... · software requirements specification...

Documents