PPAY MD070 Application Extensions Technical Design V1.0

Apollo - Implementation of Oracle Applications R11i –
Financial and Purchasing Modules

MD.070 APPLICATION EXTENSION TECHNICAL
DESIGN
Positive Pay File
Author: Joydip Mahanty
Creation Date: November 1, 2005
Last Updated: November 1, 2005
Version: 1.0
Approvals:
Gino Marghella
Christina
Submitted by:
Satyam Computer Services Limited
Enterprise Applications and Business Intelligence Solutions
Tel: +91-40-6316666, Fax: +91-40-6319990 - www.satyam.com
Copy Number _____

Apollo - Implementation of Oracle Applications R11.5.10– Financial and Purchasing Modules
Document Control
Change Record
3
Date Author Version Change Reference
01-Nov-05 Joydip Mahanty 1.0 No Previous Document
Reviewers
Name Position
Distribution
Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4
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.
Positive Pay File456337714.doc

Page 2 of 20
Contents
Document Control...................................................................................................................2
Detailed Information of Interface..........................................................................................5

Business Rules...................................................................................................................5
Mapping Table (Rules).....................................................................................................7
Assumptions....................................................................................................................19
Concurrent Program Description........................................................................................20
When to Run the Program.............................................................................................20
Launch Parameters.........................................................................................................20
Business Rules Implemented........................................................................................20
Open and Closed Issues for this Deliverable....................................................................22
Open Issues......................................................................................................................22
Closed Issues...................................................................................................................22

Page 3 of 20
Detailed Information of Interface

Positive Pay File will be used for transferring data required by Royal bank to process
wire, EFT and check transactions from Oracle Payables.
Postivie Pay File program will generate a report that enables user to review the same. It
will also generate a flat file in prespecified format for the purpose of transmission to
Royal Bank. The file contains information like the Vendor Name, Vendor Address,
Vendor bank Details, Amounts to be transferred etc as required for the EFT and the
Wire transfers. This information will then be uploaded to the Royal Bank which then
shall process this information to perform the wires and EFT to the Vendors. Royal Bank
then provides to the Brick with a log file for the errors that might have occurred during
the wire or EFT transfers due to reasons like Vendor Bank Account etc.
This file also contains information on the check issued by Brick to its Vendors. These
payments are made by the Brick using Oracle Payables and Document Express. The data
for these checks issued by Brick is also uploaded to the Bank as a confirmation for the
checks issued.
Postive Pay File contains two components:
 Postive Pay Report
 Postive Pay Text File
Positive Pay File provides features to satisfy the following basic business needs:
 Upload EFT and Wire Transactions to Royal Bank
 Upload confirmation regarding the checks issued to Royal Bank
This program would be developed in SQR.
Business Rules
 Program shall generate output file for User reveiw and txt file that will be
uploaded to Bank.
 Positive Pay Report shall be generated for a Payment Batch Run or Single Check
Run.

Page 4 of 20
 Vendor Bank Details and Vendor Invoice Details are not required to be
provided for payments disbursed through checks & Wires.
 Postive Pay should include the Payments or Payment Batches with in the User’s
Operating Unit.
 For every record included in the Postive Pay Report AP_CHECKS.Attribute15

will be updated with the report run date. Records that have the Attribute 15 as
not null will not be included in the next Report Run(this is the selection criteria
for the records need to be processed)
 The Program shall generate an output file and text delimited files. The output
file can be viewed from the Oracle Application “View Output”.
 Text Delimited file will be placed on a common shared directory (would be

provided) and will be uploaded to bank.
 Text Delimited will have two duplicate file generated on the shared directory.
The file naming will be as follows
o brick.txt (This will be transferred to the Bank)
o brick.txt.<system time and date>_bkup (used for maintaining backup)
 Report shall generate based on the report parameters of the Check Payment
Date from and To, Bank Account Number.
 Negative Payments can be included (ie Refunds from Vendors) in case the
parameter. Refunds are recognized in
AP_CHECKS_ALL.PAYMENT_TYPE_FLAG = ‘R’
 Void Payments will not be included in the Positive Pay File.
Refer to the functional design document for a detailed understanding of the above mentioned scenarios.

Page 5 of 20
Mapping Table (Rules)
NOTES:
1. All the columns in the target table has to be mapped and logic for the columns has to be in conversion
description/pseudo logic column
2. Specify the full target column name under column “TARGET COLUMN NAME” in the table.
3. Specify the full table name.column name under column “SOURCE NAME” in the column .
4. Specify the following in the column “CONVERSION DESCRIPTION / PSEUDO LOGIC”
a. Default values in case of null
b. SESSSTARTTIME in case of default sysdate which is there in Informatica.

Page 6 of 20
Mapping Name
AP_CHECKS, AP_BANK_BRANCHES,AP_BANK_ACCOUNTS, PO_VENDORS, PO_VENDOR_SITES, AP_INVOICES,
Target Table Name
AP_INVOICE_PAYMENTS
Source Name(s)
Strategy
Comments
SQL Override
Mapping for TXT file
Header Record:
Field Name Start Length Usage Format Comments

Column
Tag 1 1 O Text “H” for header
Payment Type 2 1 M Text If the payment issued using the check format (ie.
AP_CHECKS.PAYMENT_METHOD_LOOKUP_CODE =
‘CHECK’) then Payment Type will be ‘L’. In other case it
will be picked from the attribute1 of the Bank associated
with the Vendor Bank. The Bank Account ID is stored
AP_CHECKS under EXTERNAL_BANK_ACCOUNT_ID.
Payment Amount 3 15 M Numeric(1 AP_CHECKS.AMOUNT

2,2)
999999999 NOTE:
999.99
Max field length for retail is 10
Max field length for cheque printing is 10
Max field length for DA is 10
Payment Date 18 8 M Date(CCY AP_CHECKS.CHECK_DATE

YMMDD)
NOTE: Wire payments cannot be issued with dates falling
on a Bank holiday.

Page 7 of 20
Column
Payment Trace Number 26 30 M Text AP_CHECKS.CHECK_NUMBER
Reference Information 56 35 O Text Dependent on payment type
Currency (Originator) 91 3 M Text AP_CHECKS.CURRENCY_CODE
Currency of originator’s account (debit account) “CAD”

or “USD”
Currency (Receiver) 94 3 X Text AP_CHECKS.CURRENCY_CODE
Currency of receiver’s account (credit account)
Currency Conversion Code 97 1 X Text DEFAULT = 1
Required for wire payments only
“1” = No currency conversion required
“2” = Currency conversion required
Wire Advice notification 98 1 X Text DEFAULT = 1
Required for wire payment only
“1” = credit account under advice
“2” = credit account no advice
Special Instructions 99 35 X Text This will be picked from the attribute2 of the Bank
associated with the Vendor Bank. The Bank Account ID is
(Can be used to a max of 3 (x 3) stored AP_CHECKS under
times) EXTERNAL_BANK_ACCOUNT_ID.
Used for cheque printing and wire payments

Page 8 of 20
Column
Note : Free form message
Source Bank/Branch Number 204 9 M Text AP_BANK_BRANCHES.BANK_NUM
Derived based on AP_CHECKS.BANK_ACCOUNT_ID

AND BANK_BRANCH_ID in AP_BANK_ACCOUNTS
Source Bank Account Number 213 12 M Text AP_BANK_ACCOUNTS.BANK_ACCOUNT_NUM
Derved based on AP_CHECKS.BANK_ACCOUNT_ID.
Vendor Id 225 15 O Text PO_VENDORS.SEGMENT1
Derived from ap_checks.vendor_id
Vendor Name 240 35 M Text AP_CHECKS.VENDOR_NAME
Vendor Address Line 1 275 35 X Text AP_CHECKS.ADDRESS_LINE1
Mandatory for wires & cheque printing
Vendor Address Line 2 310 35 X Text AP_CHECKS.ADDRESS_LINE2

Optional for wires & cheque printing
Vendor City 345 30 X Text AP_CHECKS.CITY

Mandatory for cheque printing. & wires. (***Field length
is 20 for wires)
Vendor Province/State 375 2 X Text AP_CHECKS.PROVINCE

Vendor Postal Code/Zip Code 377 10 X Text AP_CHECKS.ZIP
Vendor Country Code 387 2 X Text AP_CHECKS.COUNTRY
Vendor Contact Name 389 35 X Text PO_VENDOR_CONTACTS.LAST_NAME||

Page 9 of 20
Column
PO_VENDOR_CONTACTS.FIRST_NAME
Mandatory for payment type “C, D, F or G” (Fax or email

remittances)
Vendor Fax Number 424 15 X Text AP_CHECKS_ALL.FAX_AREA_CODE||

AP_CHECKS_ALL.FAX
Mandatory for payment type “C or F”, (Fax remittances)
Format: 9051231234, no “-“ , “(“ , “)”
Vendor Email Address 439 80 X Text AP_CHECKS_ALL.EMAIL_ADDRESS
Mandatory for payment type “D or G”. (Email

remittances)
Vendor Bank/Branch Number 519 9 M Text AP_CHECKS.BANK_NUM
Vendor Bank Account Number 528 30 M Text AP_CHECKS.EXTERNAL_BANK_ACCOUNT_NUM.
Vendor Bank Name 558 35 X Text AP_BANK_BRANCHES.BANK_NAME
Derived from AP_BANK_BRANCHES based

AP_CHECKS.EXTERNAL_BANK_ACCOUNT_ID and
AP_BANK_ACCOUNTS.
Mandatory for wires
Vendor Bank Address Line 1 593 35 X Text AP_BANK_BRANCHES.ADDRESS_LINE1

AP_BANK_ACCOUNTS.
Mandatory for wires

Page 10 of 20
Column
Vendor Bank Address Line 2 628 35 X Text AP_BANK_BRANCHES.ADDRESS_LINE2

AP_BANK_ACCOUNTS.
Mandatory for wires
Vendor Bank City 663 30 X Text AP_BANK_BRANCHES.CITY

AP_BANK_ACCOUNTS.
Mandatory for wires
Vendor Bank Province/State 693 2 X Text AP_BANK_BRANCHES.PROVINCE

AP_BANK_ACCOUNTS.
Mandatory for wires
Vendor Bank Postal Code/Zip 695 10 X Text AP_BANK_BRANCHES.ZIP

Code
AP_BANK_ACCOUNTS.
Mandatory for wires
Vendor Bank Country Code 705 3 X Text AP_BANK_BRANCHES.COUNTRY

AP_BANK_ACCOUNTS.
Mandatory for wires

Page 11 of 20
Column
Correspondent Bank Name 708 35 X Text AP_BANK_BRANCHES.BANK_NAME
This will be picked from the attribute3 of the Bank

stored AP_CHECKS under
EXTERNAL_BANK_ACCOUNT_ID.
BANK_BRANCH_ID will be stored in segment3.

Correspondent Bank Name can be derived based on
BANK_BRANCH_ID from
Conditional for wires going to a correspondent bank
Correspondent Bank Address 743 35 X Text AP_BANK_BRANCHES.ADDRESS_LINE1

Line 1

BANK_BRANCH_ID from
Correspondent Bank Address 778 35 X Text AP_BANK_BRANCHES.ADDRESS_LINE2

Line 2

BANK_BRANCH_ID from
Optional for wires
Correspondent Bank City 813 30 X Text AP_BANK_BRANCHES.CITY

Page 12 of 20
Column


BANK_BRANCH_ID from
(***Field length is 20 for wires)
Correspondent Bank 843 2 X Text AP_BANK_BRANCHES.PROVINCE

Province/State

BANK_BRANCH_ID from
Correspondent Bank Postal 845 10 X Text AP_BANK_BRANCHES.ZIP

Code/Zip Code

BANK_BRANCH_ID from

Page 13 of 20
Column
Correspondent Bank Country 855 3 X Text AP_BANK_BRANCHES.COUNTRY

Code

BANK_BRANCH_ID from
Conditional for wires going to a correspondent bank if

US$/Int’l payments are being made
Detail Record: (Detail records are not required for wire payments or payment only)
Field Name Start Length Usage Format Column mapping/Default Values/Comments

Column
Tag 1 1 M Text “D” for detail
Invoice Number 2 24 O Text AP_INVOICES.INVOICE_NUM
DERIVED BASED ON INVOICE_ID IN

AP_INVOICE_PAYMENTS_ALL based on check_id
Invoice Description 20 30 O Text AP_INVOICES.INVOICE.DESCRIPTION

Invoice Date 50 8 O Date AP_INVOICES.INVOICE_DATE


Page 14 of 20
Field Name Start Length Usage Format Column mapping/Default Values/Comments
Column
CCYYMMDD
Net Amount 58 15 M Numeric AP_INVOICE_PAYMENTS_ALL.AMOUNT –

AP_INVOICE_PAYMENTS_ALL.DISCOUNT
999999999999.99
NOTE: Max field length for cheque printing is 11
Gross Amount 73 15 O Numeric AP_INVOICE_PAYMENTS_ALL.AMOUNT
999999999999.99
Discount Amount 88 15 O Numeric AP_INVOICE_PAYMENTS_ALL.DISCOUNT_TAKEN
999999999999.99
Reference Information 103 30 O Text Dependant on payment type
Usage
*M = Mandatory O = Optional X = Conditionally Required
Mapping for Report
Field Name Column Mapping Default/Other Values
Report Date SYSDATE

Page 15 of 20
Field Name Column Mapping Default/Other Values
Bank Account Name Parameter
Include Void Parameter
From Date Parameter
To Date Parameter
Payment Type AP_CHECKS.PAYMENT_METHOD_ If the payment issued using the check format (ie.
LOOKUP_CODE AP_CHECKS.PAYMENT_METHOD_LOOKUP_CODE =
‘CHECK’) then Payment Type will be ‘L’. In other case it will
be picked from the attribute1 of the Bank associated with the
Vendor Bank. The Bank Account ID is stored AP_CHECKS
under EXTERNAL_BANK_ACCOUNT_ID.
Vendor Name AP_CHECKS.VENDOR_NAME
Vendor Site Code AP_CHECKS.VENDOR_SITE_CODE
Check / Payment Number AP_CHECKS.CHECK_NUMBER
Payment Amount AP_CHECKS.AMOUNT
Payment Date AP_CHECKS.CHECK_DATE
CCD AP_CHECKS.CURRENCY_CODE
Bank Number AP_CHECKS.BANK_NUM
Bank Account Number AP_CHECKS.EXTERNAL_BANK_A

CCOUNT_NUM.
Please refer to the functional document for a description of the report layout

Page 16 of 20
Assumptions
This design assumes that the following statements are true:
 Cross Currency Transactions will not be supported by this program.

Page 17 of 20
Concurrent Program Description

The Postive Pay Report concurrent program is needed to generate text file for all the EFT, WIRE and Check intimation transactions
needed to be uploaded to the Bank.
When to Run the Program
Positive Pay Report concurrent program should be run oafter every check run.
Launch Parameters
Launch parameters for the Postive Pay Report concurrent program include:
 Bank Account Number
 Start Date
 End Date
 Include Void
Business Rules Implemented
The business rule implemented by Postive Pay Report concurrent program is
 This concurrent program can be run at any time during the day based on the bricks requirement. The Positive Pay file
generated during the run will not include records already processed ie. Included in any of the previous Positive Pay Run.

Page 18 of 20

Page 19 of 20
Open and Closed Issues for this Deliverable
Open Issues
ID Issue Resolution Responsibility Target Date Impact

Date
Closed Issues
ID Issue Resolution Responsibility Target Date Impact

Date

Page 20 of 20

PPAY MD070 Application Extensions Technical Design V1.0

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PPAY MD070 Application Extensions Technical Design V1.0

Caricato da

Copyright:

Formati disponibili

Apollo - Implementation of Oracle Applications R11i –

Financial and Purchasing Modules

Copy Number _____

Date Author Version Change Reference

01-Nov-05 Joydip Mahanty 1.0 No Previous Document

Copy No. Name Location

Positive Pay File456337714.doc

Detailed Information of Interface..........................................................................................5

Positive Pay File456337714.doc

Detailed Information of Interface

Postive Pay File contains two components:

 Postive Pay Report

 Postive Pay Text File

 Upload EFT and Wire Transactions to Royal Bank

 Upload confirmation regarding the checks issued to Royal Bank

This program would be developed in SQR.

Positive Pay File456337714.doc

 For every record included in the Postive Pay Report AP_CHECKS.Attribute15

 Text Delimited file will be placed on a common shared directory (would be

o brick.txt (This will be transferred to the Bank)

o brick.txt.<system time and date>_bkup (used for maintaining backup)

 Void Payments will not be included in the Positive Pay File.

Positive Pay File456337714.doc

Mapping Table (Rules)

4. Specify the following in the column “CONVERSION DESCRIPTION / PSEUDO LOGIC”

a. Default values in case of null

b. SESSSTARTTIME in case of default sysdate which is there in Informatica.

Positive Pay File456337714.doc

Mapping for TXT file

Field Name Start Length Usage Format Comments

Tag 1 1 O Text “H” for header

Payment Amount 3 15 M Numeric(1 AP_CHECKS.AMOUNT

Max field length for cheque printing is 10

Max field length for DA is 10

Payment Date 18 8 M Date(CCY AP_CHECKS.CHECK_DATE

Positive Pay File456337714.doc

Payment Trace Number 26 30 M Text AP_CHECKS.CHECK_NUMBER

Reference Information 56 35 O Text Dependent on payment type

Currency (Originator) 91 3 M Text AP_CHECKS.CURRENCY_CODE

Currency of originator’s account (debit account) “CAD”

Currency (Receiver) 94 3 X Text AP_CHECKS.CURRENCY_CODE

Currency of receiver’s account (credit account)

Currency Conversion Code 97 1 X Text DEFAULT = 1

Required for wire payments only

“1” = No currency conversion required

“2” = Currency conversion required

Wire Advice notification 98 1 X Text DEFAULT = 1

Required for wire payment only

“1” = credit account under advice

“2” = credit account no advice

Used for cheque printing and wire payments

Positive Pay File456337714.doc

Note : Free form message

Source Bank/Branch Number 204 9 M Text AP_BANK_BRANCHES.BANK_NUM

Derived based on AP_CHECKS.BANK_ACCOUNT_ID

Source Bank Account Number 213 12 M Text AP_BANK_ACCOUNTS.BANK_ACCOUNT_NUM

Derved based on AP_CHECKS.BANK_ACCOUNT_ID.

Vendor Id 225 15 O Text PO_VENDORS.SEGMENT1

Derived from ap_checks.vendor_id

Vendor Name 240 35 M Text AP_CHECKS.VENDOR_NAME

Vendor Address Line 1 275 35 X Text AP_CHECKS.ADDRESS_LINE1

Mandatory for wires & cheque printing

Vendor Address Line 2 310 35 X Text AP_CHECKS.ADDRESS_LINE2

Vendor City 345 30 X Text AP_CHECKS.CITY