Professional Documents
Culture Documents
070 - MODULE FUNCTIONAL AND TECHNICAL DESIGN XX211 CE Bank Statement Interface
Document Control
Change Record
4
Date 21-Dec-2010
Author Rajesh
Version 1.0
Reviewers
Date
Approvers
Name Salli Churchill Arunova Majumdar Position XX Project Manager Genpact Project Manager Date
Contents
Document Control ................................................................................................................... 2 Preface...................................................................................................................................... 1 Intended Audience ........................................................................................................... 1 Functional Design Approval ................................................................................................... 2 Functional Topical Essay ....................................................................................................... 3 Scope and Application ..................................................................................................... 3 Impact to 3rd Party Systems ............................................................................................ 3 Process Change Impacts ................................................................................................. 3 Assumptions ..................................................................................................................... 3 Definitions .......................................................................................................................... 4 Setups and Requirements .............................................................................................. 4 Business Rules ................................................................................................................. 4 Data Elements .............................................................. Error! Bookmark not defined. Selection Criteria .............................................................................................................. 4 Data Transformation/Translation ................................................................................... 4 Solution Design ....................................................................................................................... 5 Functional Overview ........................................................................................................ 5 Selection criteria: ..................................................................................................................... 6 Data Flow Diagram ................................................................................................................. 8 Process Flow Diagram ........................................................................................................... 9 User Procedures ................................................................................................................... 11 Program Navigation ....................................................................................................... 11 Input Parameters ............................................................................................................ 11 Error Handling/Troubleshooting ................................................................................... 11 Running/Scheduling ....................................................................................................... 12 User Test Plan .............................................................. Error! Bookmark not defined. Technical Overview ............................................................................................................... 14 Approach-- ...................................................................................................................... 14 Module List-- ................................................................................................................... 14 Concurrent Program ............................................................................................................. 15 Calling Arguments .......................................................................................................... 16 Log Output .................................................................... Error! Bookmark not defined. Table and View Usage .................................................................................................. 16
Program Logic (pseudo code) ...................................................................................... 16 SQL Statements ............................................................................................................. 17 Default Data Sources .................................................................................................... 17 Validation Logic .............................................................................................................. 17 Incompatibility ................................................................................................................. 17 Performance Considerations ........................................................................................ 17 Value Sets ....................................................................................................................... 17 Synonyms........................................................................................................................ 17 Archiving .......................................................................................................................... 18 Tables, Indexes, Sequences ........................................................................................ 18 Test Plans .............................................................................................................................. 19 Unit Test Plan ................................................................................................................. 19 Open and Closed Issues ...................................................................................................... 20 Open Issues .................................................................................................................... 20 Closed Issues ................................................................................................................. 20
Preface
This document describes the process of interfacing Bank information from Bank to Oracle Cash Management. The document relates the functional mappings from the existing Banks into the individual fields in Oracle which makes sure the information being interfaced from Bank System is correctly represented and maintained in Oracle Cash Management.
Intended Audience
Audience of this MD70 document can be both the functional users and the technical group. The functional area mentioned in this document can be used by the functional users and the technical portion can be ignored as the technical section gives the technical details of how the interface is build from a technical stand point. The technical audience can also review the functional area for the functional requirements for this interface.
XX PM Genpact PM
Assumptions
The accounting period in Accounts Payables, Accounts Receivables and General Ledger are open. Bank transaction codes according to the Harris Bank (HB), Bank of Montreal (BOM). The Bank Statement File in the Format BAI2 should be handled only one time by the CE user, after download the weekly file from the bank. The bank statement file from the HB and BOM website systems has been downloaded onto a shared network drive. The Business owns the bank statement data file from the HB and BOM systems and the rights to the folder where it is stored. A custom concurrent request will be scheduled to transfer the bank statement file from the shared network drive to the Unix Server. The bank statement file will be available under $XXCE_TOP/data/in on UNIX server.
Definitions
HB and BOM Banks 3rd party payroll system
Functional Details
Business Rules
Basic process requirements Data from Bank system will be automatically loaded into Oracle with the help of standard Bank Interface on bi weekly basis.
List of exclusions/inclusions, which must be considered while designing the solution. There must be a master mapping file for both XX Manufacturing and Workrite to map each individual to a respected cost center.
Selection Criteria
While running the CM Bank Statement Interface program in Oracle, select the required parametsr to load from data field into Oracle.
Data Transformation/Translation
The concurrent program which will be used to create the Bank Details from Bank system should be scheduled in Oracle based on the exact requirements.
Selection criteria: Mapping Information The different fields in BAI file need to be mapped to Oracle Cash Management table to facilitate the import. These needs to be done using the standard Oracle mapping form (refer to below screenshot)
Headers:
Lines:
The high-level Bank statement process flow from Statement download -Banks to Reconciliation in Oracle Cash management module.
START
Bank Statement Data file is transferred to Folder KV_TOP/CE/In in Unix server From network drive.
QFD
Quality Function Deployment (QFD) is used to identify the best solution on the basis of ranked CTQs. Use this tool when there are multiple solutions available and a decision has to be made. Example Three solutions are available, one has to be selected. ******************************************************************************************************* Alternative # A B C D
Options
No Change
Automate Process
Description
Schedule the Manually key in Upload with entire Bank Statement Auto reconcile
Fewer than 10 touch points 0 to Negligible Customization Proven technology 0 to Negligible training required Con's More than 10 touch points High Customization XX team to work in more than 1 apps Un proven technology New apps training required
0 0 1 0
2 2 2 2
3 3 4 3
4 0 1 0 0 5
2 1 3 2 1 17
1 2 3 2 3 24
Legend : Ranking goes from 0-4 where 0 meaning the least and 4 the max
User Procedures
This section describes the the user interactions for the interface.
Program Navigation
Concurrent Program Name: XX Bank Statement Interface Navigation Path: 1. Switch to Cash Management Responsibility
Input Parameters
----
Error Handling/Troubleshooting
The different exceptions and exception handling is summarized below: Stage / Exception Staging Table 1. File not loaded in specific folder or do not have proper privileges / access Exception Handling For the interface, need to run the program Bank Statement Loader which will have the details like BAI2 file name, file path, etc. This program will also trigger other programs including Run SQL*Loader- BAI2 For this exception, this program will error out and log file will indicate that there are no files available. Place the file with proper privileges / access. Oracle Interface Table Statements are not imported for following reasons: a. Duplicate statement number For this bank and date, statement is already created. Please review the existing statement before importing Check the GL date specified in Import program As these are optionally, it will be warning messages only and statement will be imported
b. GL period is closed c. Validation failed for control total information in bank statement like begin balance, closing balance, line count of payment & receipt, amount
of payment & receipt d. Bank transaction codes not setup If they are not setup, the entire statement will not be loaded. The output of the program Bank Statement Import Execution Report will give the reason and also line number The new transaction code needs to be defined and run the import program again. e. Exchange rate not defined If the line is foreign currency denominated line, defined the exchange rate and run the import program. As these are standard Oracle errors, please refer to exhaustive list of exceptions and resolution
Reconciliation related
Running/Scheduling
The scheduling of this will be decided based on all the interface scheduling decided later.
Main Path
Actor Actor Action System Response
(Resp) Cash Manager Super User (M) Other> Programs> Run, Request Set (B) OK, Search for Bank Statement Load, Enter Parameters (B) OK, (B) Submit In the bank statement, Ensure that there are transaction codes enabled In the bank statement, Ensure that there are transaction codes with Multicode enabled with both credit & debit entries In the bank statement, Ensure that there are transaction codes . This receipt needs to be created manually. Create a payment batch with dates & amounts matching debit entries in the bank statement.
Program submitted
System will create bank statement interface line System will create bank statement lines with +ve and ve amounts System will create bank statement interface line with unreconciled receipt System will create bank statement interface line with unreconciled payments. When Auto Reconciliation is done, these payments will be matched. System will create bank statement interface line with unreconciled payments / receipts. These records will be matched manually. Program will create necessary AR transactions for Reconciliations For completion/ review please run relevant reports.
In the bank statement, enter an entry for bank charges, direct debits, payment to customer, unfulfilled supplier payment (credit of payments that the bank cannot process)
Create Automatic / Manual Receipt, Negative Receipts based on Transaction codes. Run necessary reports
Technical Overview
This document describes the interface for Cash Management Bank from source system to Oracle Cash Management. The Bank interface will be able to accept data from source system and validate it before processing, using Custom shell script program defined below, finally Import the data to Oracle Cash Management through the standard Import Program.
Approach-To upload the Banks data one request set has to be submitted i.e XX Bank Statement Interface which will run the following programs in a sequentially. 1. Load the data from Flat file from the UNIX directory $XXCE_TOP/data/in to Oracle standard interface table. 2. Run the Standard Loader and Import program to create the statement in Cash Management
Module List- XX Banks Statement Data Upload Loading the data from data file to Oracle staging table
Concurrent Program
Concurrent Program Executable: Executable Short Name Application Description Execution Method Execution File Name Subroutine Name XXBANKSTMTUPLOAD XXBANKSTMTUPLOAD Custom Cash Management XX BANK STMT Data Upload Host XXBANKSTMTUPLOAD
Concurrent Program: Program Short Name Application Description : XX BANK STMT Data Upload : XXBANKSTMTUPLOAD : Custom Cash Management : XX BANK STMT Data Upload Options Method Host Enabled [ X ]
Yes Format:
Save (Yes/No) Print (Yes/No) Columns Rows Style
Yes
Yes
Printer
Yes
No
Required
Display
Size
Prompt
Token
Calling Arguments
Argument
Prompt
Value Set
Default Value
Table Name
Select
Insert
Update
Delete
SQL Statements
NA
Validation Logic
Error Conditions: Bank name, Bank account number, Bank Branch Name, Amount, Currency values passed in the flat file was wrong.
Warning Conditions: NA
Incompatibility
Performance Considerations
NA
Value Sets
Value Set
Size
Type
Rqd
Validation/Values
Synonyms
Owner
Object
Grantees
Archiving
After the data file is read and the data is inserted into the staging table, the data file should be archived to the archive folder with a current timestamp.
Test Plans
Unit Test Plan
Seq Action 1. Place the data file in Unix directory $XXCE_TOP/data/in 2. Upload the Bank data file in Oracle.
Expected Results
Actual Results
Run the custom program and review the Interface table whether the data is successful or not. Run the standard import program which should pick the data from standard interface to the cash management tables
Open Issues Business ID Issue Resolution Responsibility Target Date Impact Date
Closed Issues Business ID Issue Resolution Responsibility Target Date Impact Date