MD070 Wells Fargo ACH 1.0

MD.070 Application Extension Technical Design

Doc Ref: MD050 - Wells Fargo ACH

MD.070 Application Extension Technical Design

AIM

MD.070 Application Extension Technical Design and Unit Test Plan

ABC Corporation

CU279 Wells Fargo ACH

Author:Creation Date:9th June 2009

Last Updated:

Document Ref:

Version:1.0

Note: Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->OptionsView and checking the Bookmarks option in the Show region.

Approvals:

Note: To add additional approval lines, press [Tab] from the last cell in the table above.

Copy Number_____

Note: You can delete any elements of this cover page that you do not need for your document. For example, Copy Number is only required if this is a controlled document and you need to track each copy that you distribute.

Document Control

Change Record

1

Date

Author

Version

Change Reference

Reviewers

Name

Role

Tina Pegg

ABC Functional

Distribution

Copy No.

Name

Location

1

Library Master

Project Library

2

Project Manager

3

4

Note: The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Contents

iiDocument Control

Technical Overview1

Approach1

Assumptions2

Module List3

XXAR: WF ACH Remittance File - Concurrent Program Logic4

Calling Arguments4

Log Output4

Table and View Usage4

Program Logic (pseudo code)4

SQL Statements6

Validation Logic10

Incompatibility10

Performance Considerations10

Other Considerations10

Integration Issues12

Changes Required12

Shared Components12

Alert conditions12

Incompatibilities12

Performance Issues12

Database Design13

Desired Table Changes13

New/Updated Seed Data13

Descriptive Flexfields13

Value Sets13

Grants/Synonyms13

Archiving13

Database Diagram13

Tables, Indexes, Sequences13

Unit Test Plan14

Installation Requirements15

Implementation Notes16

Design Summary16

Coding Summary16

Testing Summary17

Installation17

Open and Closed Issues for this Deliverable18

Open Issues18

Closed Issues18

Note: To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Technical Overview

This document defines the technical components required to implement customization CU279 Wells Fargo ACH program. This Application Extension Technical Design document complements the Application Extension Functional Design document for CU279 Wells Fargo ACH program and you should consider the set to be the complete detailed design.

Wells Frago ACH program is the Remittance file that is a result of the Automatc Receipt function that we are sending to Wells Fargo bank to collect funds from ACH customers

User runs the Automatic Receipt program in Oracle from a Receipt batch

This concurrent program is developed only for INC Operating Unit (INC).

Approach

A host program (XXARWFACH) registered as concurrent program is mapped to the Custom remittance program XXAR: WF ACH Remittance File .

A PL/SQL package (XXAR_WFACH_PKG) is created which performs the following:

1. Extracts receipt information information for the batch number .

2. Constructs File header record, Batch header record, Entry detail record, Special Addenda record, Batch control record and File control record according to the required format.

3. Above records are written into a text file using UTL_FILE utility.

4. The output is emailed to [email protected] and a backup is placed in the directory XXACH_WFACH_RECEIPTS.

5. The out file is written to the directory XXACH_WFACH_RECEIPTS in the path /var/opt/utl/EBIZ/outbound/XXACH_WFACH_RECEIPTS

Assumptions

This design assumes that the following statements are true:

1. The file format is as provided by Wells Fargo

2. The program will be attached only on INC operating unit.

Note: Update Platinum inventory with returns processed in OracleIf the Functional Design included a Technical Overview section, duplicate that information here and add additional details.

Module ListForms

Wells Fargo ACH program includes the following forms:

None

Reports

Wells Fargo ACH program includes the following reports:

None

Concurrent Programs

Wells Fargo ACH program includes the following concurrent programs:

XXAR: WF ACH Remittance File - This will call the host program which will execute the PL/SQL package, which is responsible for extracting the remittance information, and generating the text output in the required format and will email the test file to the email id defined in the profile XXAR_WFACH_EMAIL_ID

Database Triggers

Wells Fargo ACH program includes the following database triggers:

None

Note: Add other components above as required

Note: Update the sample navigation logic below as needed to reflect the requirements of your customization.

Note: The diagram above is just an exampleDouble click on it to edit it as an embedded object. Select it and choose Edit->VISIO Object->Open to open it in the full Visio application.You can also use Oracle Developer to draw your diagram and define most of the information in this section.

XXAR: WF ACH Remittance File - Concurrent Program Logic

The concurrent program XXAR: WF ACH Remittance File is based on the host program XXARWFACH. This host program executes the PL/SQL package XXAR_WFACH_PKG that extracts the remittance information and builds the File header record, Batch header record, Entry detail record, Special Addenda record, Batch control record and File control record. These records are written to a text file from within the PL/SQL package. The host program also sends an email to [email protected] with the output file as attachment.

Calling Arguments

None

Log Output

.........1.........2.........3.........4.........5.........6.........7.........8

________________________________________________________________________________

Same as in 10.7

________________________________________________________________________________

Table and View Usage

Table Name

Select

Insert

Update

Delete

AR_BATCHES_ALL

X

AR_CASH_RECEIPT_HISTORY_ALL

X

AR_CASH_RECEIPTS_ALL

X

HZ_CUST_ACCOUNTS

X

HZ_PARTIES

X

AP_BANK_ACCOUNTS_ALL

X

AP_BANK_BRANCHES

X

Program Logic (pseudo code)

Host Program pseudo logic:

--Specify the location for writing the .Eft files, OUT_FILE and email id

1. Connect to sqlplus and get the directory paths (data and archive folder) for placing the output datfile by selecting from DBA_DIRECTORIES. Refer to SQL Statements: Data Selection 3

2. Get the EMAIL_LIST using profile option XXAR_WFACH_EMAIL_ID -- Refer SQL statements: Data selection 4

3 a. OUT_PATH=$XXVFI_TOP/bin

b. OUT_FILE=ACH$DATE.txt -- sent as email attachment

4. Take the value of Receipt Batch Name as $5 into PAY_BATCH

5. Use FCP$LOGIN to connect to sqlplus and execute the procedure xxap_wfeft_pkg.process_wfeft_paymts_prc passing PAY_BATCH as the parameter.

EXEC xxap_wfeft_pkg.process_wfeft_paymts_prc ('$PAY_BATCH');

The .Eft files will be created by this package.

6. For all .Eft files present in location $UTL_FILE, write into the OUT_FILE rename it to .bak.

7. Email the OUT_FILE to the EMAIL_LIST.

8. Copy the OUT_FILE to archive folder (/var/opt/utl/ /outbound/CU019_WF_EFT_PAYMENTS/arch) and delete OUT_FILE from $XXVFI_TOP/bin.

SQL Statements1 - Data Selection: Cursor for creating detail records

SELECT '6' || -- Record Type --

'27'|| -- Transaction Code --

rpad(nvl(substr(ABB.bank_number,1,8),' '),8,' ')|| -- Receiving DFI R/T NUMBER --

rpad(Get_Check_Digit_Fnc(ABB.bank_number),1,' ')|| -- R/T Number check digit --

rpad(nvl(substr(ABC.bank_account_num,1,17),' '),17,' ')|| -- Recvg DFI Account Number (Vendor A/c#) --

lpad(nvl(substr((ACH.AMOUNT * 100),1,10),'0'),10,'0')|| -- Amount --

rpad(nvl(substr(HCA.ACCOUNT_NUMBER,1,15),' '),15,' ')|| -- Individual ID --

rpad(nvl(substr(HZ.PARTY_NAME,1,22),' '),22,' ')|| -- Individual Name --

' '||

'1'|| -- Addenda Records indicator 0 for NO and 1 for YES--

'091000010000001' entry_detail_rec -- Trace Number *** Well Fargo# AND BATCH NUMBER as in Batch Header Rec--

,ABB.bank_number bank_number

,ACH.AMOUNT RECEIPT_AMOUNT

,ACH.TRX_DATE RECEIPT_DATE

,ACR.RECEIPT_NUMBER RECEIPT_NUMBER

,ABA.BATCH_ID BATCH_ID

,ach.status receipt_status

FROM AR_BATCHES_ALL ABA

,AR_CASH_RECEIPT_HISTORY_ALL ACH

,AR_CASH_RECEIPTS_ALL ACR

,HZ_CUST_ACCOUNTS HCA

,HZ_PARTIES HZ

,AP_BANK_ACCOUNTS_ALL ABC

,AP_BANK_BRANCHES ABB

WHERE ABA.BATCH_ID = ACH.BATCH_ID

AND ACH.CASH_RECEIPT_ID = ACR.CASH_RECEIPT_ID

AND ACH.ORG_ID = ABA.ORG_ID

and ACR.ORG_ID = ACH.ORG_ID

AND ACR.PAY_FROM_CUSTOMER = HCA.CUST_ACCOUNT_ID (+)

AND HCA.PARTY_ID = HZ.PARTY_ID

and ABC.BANK_ACCOUNT_ID ( + ) =ACR.CUSTOMER_BANK_ACCOUNT_ID

and ABC.BANK_BRANCH_ID = ABB.BANK_BRANCH_ID ( + )

AND ACH.CURRENT_RECORD_FLAG ='Y'

AND ABA.TYPE = 'REMITTANCE'

AND ABA.NAME = p_batch_name

AND ABA.ORG_ID = g_org_id

UNION








rpad(nvl(substr(HZ.PARTY_NAME,1,22),' '),22,' ')|| -- Individual Name --

' '||













,HZ_PARTIES HZ

,ap_bank_accounts_all ABC

,ap_bank_branches ABB

,AR_BATCH_SOURCES_ALL ABSA










AND ABA.BATCH_SOURCE_ID = ABSA.BATCH_SOURCE_ID

AND ABSA.TYPE = 'AUTOMATIC'

AND ABSA.ORG_ID = ABA.ORG_ID


AND ABA.ORG_ID = g_org_id;

2 - Data Selection: Function get_check_digit_fnc

This function returns the check digit from transit routing number, which is then

used in the batch control and file control records.

SELECT

TO_NUMBER(SUBSTR(p_routing_number,1,1))*3 + -- Ist Char * 3 --

TO_NUMBER(SUBSTR(p_routing_number,2,1))*7 + -- IInd Char * 7 --

TO_NUMBER(SUBSTR(p_routing_number,3,1))*1 + -- IIIrd Char * 1 --

TO_NUMBER(SUBSTR(p_routing_number,4,1))*3 + -- IVth Char * 3 --

TO_NUMBER(SUBSTR(p_routing_number,5,1))*7 + -- Vth Char * 7 --

TO_NUMBER(SUBSTR(p_routing_number,6,1))*1 + -- VIth Char * 1--

TO_NUMBER(SUBSTR(p_routing_number,7,1))*3 + -- VIIth Char * 3 --

TO_NUMBER(SUBSTR(p_routing_number,8,1))*7 -- VIIIth Char * 7 --

INTO

x_sum

FROM

dual;

3 - Data Selection:

SELECT directory_path

FROM dba_directories

WHERE directory_name LIKE XXACH_WFACH_RECEIPTS ';

4 - Data Selection:

Email List:

SELECT ltrim(profile_option_value)

FROM fnd_profile_option_values

WHERE level_id=10001 -- Site level

AND profile_option_id=

(SELECT profile_option_id

FROM fnd_profile_options

WHERE profile_option_name LIKE XXAR_WFACH_EMAIL_ID);

Addendum

Replaced the customer name with invoice number in the record type 6 for the field Individual Name (Position 55 76)

CURSOR cur_detail_rec IS








--rpad(nvl(substr(HZ.PARTY_NAME,1,22),' '),22,' ')|| -- Individual Name -- -- (Modified by Uday on 22-Jan-12)

(SELECT rpad(nvl(substr(RA.TRX_NUMBER,1,22),' '),22,' ')

FROM ra_customer_trx_all ra,

ar_cash_receipts_all ac,

ar_receivable_applications_all aaa

WHERE aaa.application_type = 'CASH'

AND aaa.cash_receipt_id = ac.cash_receipt_id

AND aaa.applied_customer_trx_id = ra.customer_trx_id

AND ac.cash_Receipt_id = acr.cash_receipt_id group by ra.trx_number) ||

' '||













,HZ_PARTIES HZ












AND ABA.TYPE = 'REMITTANCE'


AND ABA.ORG_ID = g_org_id

UNION








--rpad(nvl(substr(HZ.PARTY_NAME,1,22),' '),22,' ')|| -- Individual Name -- (Modified by Uday on 22-Jan-12)

(SELECT rpad(nvl(substr(RA.TRX_NUMBER,1,22),' '),22,' ')

FROM ra_customer_trx_all ra,

ar_cash_receipts_all ac,

ar_receivable_applications_all aaa

WHERE aaa.application_type = 'CASH'

AND aaa.cash_receipt_id = ac.cash_receipt_id

AND aaa.applied_customer_trx_id = ra.customer_trx_id

AND ac.cash_Receipt_id = acr.cash_receipt_id group by ra.trx_number) ||

' '||













,HZ_PARTIES HZ



,AR_BATCH_SOURCES_ALL ABSA










AND ABA.BATCH_SOURCE_ID = ABSA.BATCH_SOURCE_ID

AND ABSA.TYPE = 'AUTOMATIC'

AND ABSA.ORG_ID = ABA.ORG_ID


AND ABA.ORG_ID = g_org_id;

Validation LogicError Conditions:

None

Warning Conditions:

None

Incompatibility

None

Performance Considerations

None

Other ConsiderationsRestart Strategy

Resubmit the program

Crash Recovery

Resubmit the program

Integration IssuesChanges RequiredWithin Product

None

Other Products

None

Shared Components

Note: The Oracle Application product short names listed below are examples only. Update the shared component information to reflect the requirements of your customization.

INV

None

BOM

None

ENG

None

MPS/MRP

None

WIP

None

Alert conditions

None.

Incompatibilities

To itself

Performance Issues

None.

Database Design

This section summarizes new and changed database objects and data required to support CU279 Wells Fargo ACH Program. However, the complete database design is documented in the Database Extensions Design document.

Desired Table Changes

None

New/Updated Seed Data

None

Descriptive FlexfieldsValue Sets

None

Grants/Synonyms

None

Archiving

Archiving will be done after the creation of output file at location /var/opt/utl//outbound/ XXACH_WFACH_RECEIPTS

-- Refer to SQL Statements: Data Selection 3

Database Diagram

None

Tables, Indexes, Sequences

None

Unit Test Plan

This Unit Test Script verifies that each application extension conforms to development standards by using this standards checklist. This test script has been updated to incorporate the standards at this implementation site. The tests outlined here were performed as the first step during unit testing of each application extension.

This checklist covers only common and easily tested problems, and makes no pretense of being a comprehensive check for compliance to standards. If it were, this checklist would be as big as the UI standards document and would take far too long to go through. All developers and testers have already read the entire user interface standards document (and any relevant areas of the coding standards document). They have checked things they see against those standards even when they do not appear on the checklist.

Further, after doing your own checking, the Tester will review every window for standards problems missed by the initial tester. The Tester also identified general user interface improvements possible beyond simple standards issues. The Tester reviewed for possible overall improvements (better ways to present the information or lay out the window, better methods of how to do the necessary actions, and so on). This was done allowing enough time to make any necessary changes, not just before release. Testers were available for preliminary checks and user interface ideas at any point during the design. Preliminary reviews were starting with the un-coded window layout, or even a sketch, before beginning programming code.

Regression testing was performed to check that bug fixes did not break previously tested code. The testing execution plan is an iteration of the following

Test -> Find Error -> Fix Bug ( Retest

Following test scenarios are being tested for this conversion object

Installation Requirements

Installation scripts must be prepared to perform the following actions in an automated way:

1. Create the host program XXARWFACH.prog and create a soft link for it.Create the package XXAR_WFACH_PKG

2. Register the concurrent XXAR: WF ACH Remittance File for the host program XXARWFACH with Receipt Batch Name as parameter.

3. Please refer the MD120 document for the installation steps.

Note: Add to or modify this list as appropriate. Provide additional details where necessary to facilitate the creation of the installation routines.

Implementation Notes

Note: Complete this section after completing the customization. Update the design to reflect any changes made in the course of development and describe how the customization was implemented below.

This document describes exactly how CU279 Wells Fargo ACH was developed and implemented at ABC Corporation.

Design SummaryFunctional DesignFunctional Design ApprovalTechnical DesignDesign ReviewFinal AcceptanceCoding Summary

Development was done on ABCs Development Instance, to work with Release 11.5.10 of Oracle Applications. All coding follows the standards defined in the Build Standards document for ABC.

Program Files

The files required for this customization are as follows:

File

Description

Coded By

XXARWFACH.prog

This is the host program which will execute the package for creation of output file in required format

XXAR_WFACH_PKG.sql

This file will contain the package that will create the output file and write records in the specified format into it.

Testing Summary

The customizations were tested in ABCs test environment before being moved to production. See the Link Test scripts for more information.

Installation

All modules are installed as if part of a separate product. A UNIX directory structure is created under $APPL_TOP as shown in the following example:

$APPL_TOP

|

XXVFI

|

1.0.0

___________________________|___________________________________

| ||| | | |||

forms bin src sql log out srw install sql

The directories contain the components of the enhancement as shown below (directories not listed are empty). All future customizations will also be stored in these directories.

forms/

bin/ XXAPWFEFT.prog

src/

sql/

srw/

install/sql/

Note: Update the example directory structure above as appropriate for your project. Fill in the filenames under the appropriate directories.

The forms and concurrent programs are registered in Application Object Library under the XXVFI application.

Note: Indicate the specific menu options added to access new forms.

Open and Closed Issues for this Deliverable

Note: Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution.When this deliverable is complete, any open issues should be transferred to the project- or process-level Risk and Issue Log (PJM.CR.040) and managed using a project level Risk and Issue Form (PJM.CR.040). In addition, the open items should remain in the open issues section of this deliverable, but flagged in the resolution column as being transferred.

Open Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Closed Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

2 If > 1 12 of 20 = - Sec1 -1998 iv 12 of -1998

File Ref: MD070_CU279_Wells Fargo_ACH_1.0

Last Updated: 9th June 2009 Oracle and ABC Confidential - For internal use only

Documents

MD070 Wells Fargo ACH 1.0