eft user guide - english.pdf

LAD Add-on localizations

F033 - Brazilian Electronic File

Transfer

User Manual

RELESE 12

Version 1.5

DISCLAIMER:

CURRENTLY, ORACLE OFFERS OR CERTAIN OTHER ASSETS resalable DEFINED SERVICE DELIVERABLES (Collectively Referred TO THE "SERVICE DELIVERABLES") UNDER A LIMITED USE LICENSE. SERVICE CURRENTLY THE DELIVERABLES INCLUDE, BUT ARE NOT LIMITED TO, ORACLE INTEGRATION HUB. YOU AGREE THAT:

(18) DELIVERABLES ORACLE SERVICE ARE NOT STANDARD SOFTWARE PROGRAMS, (Ii) TECHNICAL SUPPORT FOR SERVICE IS NOT AVAILABLE FROM DELIVERABLES UNDER OR, OR PROVIDED BY OR THROUGH, ORACLE'S SUPPORT SERVICES OR YOUR ORGANIZATION ORACLE PROGRAM LICENSE AGREEMENT, (Iii) YOUR RIGHT TO USE AND RECEIVE SUPPORT SERVICES FOR SERVICE IS DELIVERABLES Solely as described in YOUR CONTRACT FOR SUCH SERVICE DELIVERABLES, AND (Iv) A SERVICE REQUEST SERVICE Regarding DELIVERABLES, regardless of HOW OR INITIATED LOGGED, WILL BE IN Accordance Addressed WITH THE TERMS OF YOUR CONTRACT FOR SUCH SERVICE DELIVERABLES.

Control Document

Registration Changes

Date

10-DEC-07

15-JUN-08 03-JUN-09

Author

Odirley Davson Bolzam

Odirley Davson Bolzam Cristina Faria

Version

1.0

1.1 1.2

Reference Amendment

No prior Document

Including Profiles, Concurrent import and Pay Limit. Update-Item Payment Method -Update item Boleto -Update item Registering Events Banking -Update Item Tracking Return Banking Overhaul - New Updates -Changing the process for billets Clarifications-general implementation -Best practices -Changing the validation process for Boletos Inclusion of two new attributes to the extent Account Paying Bank - Commitment Code (Supplier) - Code of Commitment (Self payment)

18-Mar-10 Odirley Davson Bolzam 1.3

06-Jul-2010 02-may-12

Odirley Davson Bolzam Ricardo Antonio

1.4 1.5

Reviewers

Name Function

LAD Consulting localizations F033 - Brazilian Electronic File Transfer

User Manual i

Content

Control Document i

Foreword 3

The Manual 4

How to Use this Manual 4 Related Documents ................................................ .................................................. 4 Comments / Suggestions 5

CHAPTER 1 Introduction 6

Oracle Payables 7

Assumptions 7

CHAPTER 2 Procedure 8

Procedure 9

Finding IUs for additional data ............................................. ................................ 9 Validation Boletos 14 Registering Payment Limit for TED / DOC ........................................... ......................... 16 Registering Results Banking .............................................. ........................... 18 Importing Bank Return .............................................. ......................................... 18 Monitoring the Return .............................................. Banking ............................. 19

CHAPTER 3 Good practices for Payments (IBY) and Payments (CLL) ...................................... ............... 22

Bills 23


User Manual ii

Foreword

E ste manual contains information needed to clarify the use of

locations (F033 - Brazilian Electronic File Transfer) implemented to locate the Oracle Payments as the nescessidades specific entities with activities in Brazil, which in its business processes utilize the services of banking EFT.


User Manual 3

The Manual

This chapter contains important information regarding the structure of the manual.

How to Use this Manual

The manual contains the illustration of the system screens to facilitate the understanding of the tool, and always after the figure is described functionality for each field.

Below is shown the standard adopted in the manual to describe the functionality of the field:

Name Feature Form

Name

Is the name of the field displayed on the system screen.

Feature

Various types of features, and are varied as the function of the field:

Required Necessary to enter a value for the field, before save the changes.

It may or may not enter a value for the field.

It depends on a previous action to provide field editing.

Does not allow changing the value of the field. The EFT, uses these fields to display information.

The EFT, automatically enters a value for the field may be modified if necessary.

Optional

Conditional Required

View Only

Suggested, Required

Form Editing / Access

The forms editor / access fields are:

Pick The field will be filled only by a list of values relevant to the field.

The field allows entry of user-defined data. Edit

Related Documents

Technical Information EFT can be found in the technical manual available on metalink.


User Manual 4

Comments / Suggestions

LAD Consulting localizations developed this manual to assist in the deployment and use product and also appreciates your comments / suggestions for improving the documentation, reported below our address and contact to send your comments / suggestions to analysis and if approved will be included in a future version:

Oracle of Brazil Rua Alfredo Egidio de Souza Aranha, 100 - São Paulo - CEP 04726-170 A / C Silvia Tonissi +55.11.5189-3060Email: silvia.tonissi @ oracle.com


User Manual 5

CHAPTER

1 Introduction

E his chapter describes the basic concepts and assumptions for deployment and use of

features available for the F033 - Brazilian Electronic File Transfer.


User Manual 6

Oracle Payables

LAD Consulting in Brazil localizations provided a solution with programs, screens and reports to meet specific requirements and common in Brazilian companies.

All configuration and procedures detailed in this manual will be used to perfect understanding of the solution to be implemented on the client.

Assumptions

This manual assists in the implementation and use of EFT, we will not address the features Oracle Payments module, in case of doubt or deepening of this product is recommended the completion of training by Oracle University or consultant support of Oracle Consulting.

It is very important to review the data configuration before starting Oracle Payments setting the location


User Manual 7

CHAPTER

2 Procedure

E his chapter describes how to deploy and use EFT.


User Manual 8

Procedure

The procedures for implementation of EFT comprise the following steps:

Step

One.

2nd.

3rd.

4th.

5th.

Step Name

Customizing UI's (Forms and Web Based Applications) for registration of data Additional

Registering Payment Limit for TED / DOC

Registering Results Banking

Monitoring the Return Banking

Good practices for Payments (IBY) and Payments (CLL)

Locating IUs for additional data

In payment instructions are needed various information of Bank Account pays lacking specific fields to be stored in EBS. Therefore, this information is recorded in extended fields (CLL).

The need for additional data that will be used for localized solutions, we implemented four new Extensions to the Payments.

Payment method

One. Payment Method Type - Used to identify the payments as selected by the Core should be treated located within the programs, to identify the form of royalty payments.

Payments Setup Administrator / Payments Setup / Setup Funds Disbursement / Payment Methods


User Manual 9

The added field in the query result table of Payment Method has the link (CLL Additional Info) for additional setup information.

Types of Payment Method are:

Type Payment Method

CHECK

Description

CLL Check Payment

Use

Creates rows in flat file with formatting for checks.

Creates rows in flat file with formatting for slips.

Creates rows in flat file with formatting Dealers pay.

Creates rows in flat file with formatting TED, DOC, Credit Account, etc..

Creates rows in flat file with formatting Payment Order.

Creates rows in flat file with formatting REAL TIME payment. Currently it is used only for Bradesco

Creates rows in flat file with formatting TED STR

COLLECT_DOC CLL Docs Collection Payment

CLL concessioner Concessioner

ELECTRONIC CLL Electronic Payment

PAYMENT_ORDER CLL Payment Order

REAL_TIME CLL Real Time

TED_STR CLL Ted STR

Paying Bank Account

One. File Sequence - Used to sequence the files sent to banks. The numbers must be observed occur when application deployment after the beginning of the activities of banks with EFT. The number should be populated with the last number used by the previous system.

Complementary Account Number - Additional information to the Core (IBY).

Establishment Registration Number - Default Establishment for recovery identification number (CNPJ).

2nd.

3rd.


User Manual 10

4th.

5th.

6th.

Registration Type - Used to indicate the type of validation applied to the type of person (Juridica) CNPJ.

Movement Code-Used to enable the payment schedule.

Warning Payee Type - (Available only for the bank Itaú). This attribute is used to enable or disable the sending additional information to the payee. If yes, additional information will be sent in segments defined in the manual specific to each bank, after which the batch processing sends payment details for the payee in accordance with the service contracted by the client. The value of this attribute must be populated Extracted from manual bench and should represent when the payee will receive information detailing the payline.

Invoice Payment Identification - Payment identifier.

Commitment Code (Supplier) - Supplier Code of Commitment, used by the Caixa Economica Federal, within the Batch Header line. Modalities used for Credit Account, DOC and TED (Another Ownership).

Commitment Code (Self Payment) - Code of Commitment to Auto Pay, used by the Caixa Federal, within the Batch Header line. Modalities used to TED (Same Ownership) Ceps (Collection Doc) and Payment of Dealers.

Eg For the bank Itaú reported values must be checked in Note 16 of the manual SISPAG CNAB.

Payables / Bank Accounts

7th.

Eight.

9th.

An added field in the query result table has the link (CLL Additional Info) for additional fields.


User Manual 11

Paying Agency

One. Complement Branch Number - Not Mandatory - Additional information for the digit of branch was created initially to be used as a contingency the behavior of the screen Core registration of agencies that do not allowing the insertion of hyphen for separating digit number and the agency. If the screen is refreshed the Core problem must be solved, thus eliminating the use of additional information.


User Manual 12

Added a button on the edit screen agency has the link (CLL Additional Info) for additional fields.

Billet

One. Bar Code - Not Mandatory - The registration of Billet is performed on a screen of Globalization (JL) and then associated with the installment payment schedule. Additional information for the UI creation Boletos was created to be used as a contingency for registration of the Bar Code or Line of Billet already digitável Core UI that lacked specific field to store the same. Some ER's were opened Ordering adequacy localizations Add-On for Oracle Payments in relation to Bar Code.

The solution was implemented in two stages:

JL suitability of the product (Collections and Maintain)

Changes in the product CLL adjustments to suit the product JL

So for the client to obtain the complete process, it should apply the patches (JL + CLL).

JL - 7258844: R12.JL.A - Applicable in Oracle Application 12.0.5 or higher

CLL - 9245381

In JL product, changes were made to include the BARCODE field, and a Flag to set the origin billet. The changes were implemented in Forms Sets and Collections Maintain Interface. In Consequently, also in all the processes involved in the importation of table rows interface.

What has changed for Lad Add-On?

The Barcode, which was once a field extension, should now be populated in itself forms JL (Sets Collections). For now, the table of CLL Extension will not be disabled, allowing the use of the two sources. As a first option, the extraction program will check if the field was populated JL and then the Barcode field on the screen Extension of the form Set Collections.

Load the numbers representing a Billet?

The numbers contained in a ticket can be collected using an optical reader or by manual entry the numbers specified in the document.

Reader Optics - In this case the barcode is read by reader and transported to the storage field automatically. Regardless of the brand or type of reader, the value transferred to the storage field should be represented by the barcode and not the number available for online digitavel.


User Manual 13

Entered - In this case the user will enter the number sequence of the barcode as it is described on the docket. The Typing dots (.) is mandatory. Blanks should be disregarded. The lack of typing points, or improper typing space characters and / or unanticipated entail formatting error in the paylines, causing thus possible criticisms and rejections of the payment file.

Payables / localizations / Documents Collection / Sets

A menu option has the tools link (CLL Additional Info) for additional fields.

Validation Boletos

For the validation process payments Boletos was implemented a rule that checks whether each parcel selected for or payment is not tied to a JL Billet tables and / or if it has a bar code registered.


User Manual 14

If the selected portion does not have a assossiação with a collection and a number of slips, the formatting program ended with an error specific to the problem and list the parcels which were selected that have no relation to collections or docket number.

Validation should be enabled in the System Profile: CLL_F033_ENABLE_BARCODE_VALIDATION -"CLL F033: Enable Barcode Validation Brazilian Payables EFT. "


User Manual 15

Registering Payment Limit for TED / DOC

In banking transactions to electronic payments, we have options that DOC and TED have a parameter that distinguished by the amount of the payment, which document type should be issued.

This parameter should be set in responsibility Payments Setup Administrator the following steps:

Clicking on the item Bank Instruction Codes

Clicking the button Create

In the field Code should be inserted and the value CLL_F033_PAYMENT_TYPE_LIMIT Format Value Mapping the value defined as the boundary between DOC / TED. Field Name is not observed by the programs locations.


User Manual 16


User Manual 17

Registering Results Banking

In return bank, each bank can return lines to return one or more codes Occurrence, indicating current status of the returned row. These codes can be searched and changed the screen Core of Lookups.

Access this screen is the responsibility Application Developer => Lookups => Application Object Library

For each bank locations addressed by the programs there is a lookup. These lookups can be searched by field Type CLL_F033_% = _RETURN.

The codes registered in the profiles are references to other codes that will arise during the project, therefore, not contained in the codes lookups must be entered by the customer. It is worth noting that the field Meaning, We soon after repeat field Code, an underscore followed by a code in the example: "OK, CANCEL, and SCHED REJECT" which is used by the import program to make the return record count grouped by status.

Each lookup must contain an occurrence where generic Code = "XX" and Meaning = "XX_REJECT" which will be used If the program can not find import return the registration of the occurrence reported by the bank in the file.

For lookup Banco Real There is a particularity. Must be registered a case where Code = '000 'and Meaning = '000_OK 'which will be used to identify payments without errors.

Importing Bank Return

The return banking, initially in text format, must be imported into the tables for locations follow on screen Banking Monitoring Return.

This task is performed by a program locations, "Brazilian Load of Bank Return Payables Payments ".


User Manual 18

The program should be run as follows suit:

Where:

Bank Number which indicates to the database file must be loaded into the system

Location must contain the directory where the file is

Filename receives the name of the file that should be loaded

Monitoring the Return Banking

The bank return for the results of operations made by rows sent in flat file can be accompanied onscreen return banking.


User Manual 19

The screen fields and their meanings are:

Query Parameters

Payment Process request Required EDIT

This field adds to the selection criteria, a clause in the field that request payment process is populated in creating the batch of payments.

Return Number Required EDIT

This field adds to the selection criteria, a clause in the banking field return number which is a sequential number created in processing the return.

Occurrence Date From Required PICK

This field adds to the selection criteria, a clause with a deadline initial field Occurrence Date, which is the date of the occurrence of payment.

Occurrence Date To Required PICK

This field adds to the selection criteria, a clause with a deadline at the end field Occurrence Date, which is the date of the occurrence of payment.

Search Result

Payment Process request Required PICK

This field is populated when creating the batch of payments.

Return Number Required PICK

This is a sequential number created in processing the return.

Payment Type

This is the method of payment used.

Status


User Manual

Required PICK

Required PICK

20

This field demonstrates the status of the transaction.

Occurrence Date Required PICK

This field is the date of the occurrence of payment.

Occurrence Detail Required PICK

This field contains the details of the occurrence of payment.

Effective Date

This field is the date of payment.

Effective Payment Required PICK

Required PICK

This field contains the amount paid in the transaction.

Banking Details of Return

In detail screen can track every detail and return their values.

Document Number Required PICK

This field displays the number of transactions in AP.

Document Amount Required PICK

This field displays the transaction amount in AP.

Payment Due Date Required PICK

This field is the due date of payment.

Payment Date Required PICK

This field contains the effective date of the payment.

Payment Amount Required PICK

This field contains the actual value of the payment.


User Manual 21

CHAPTER

3 Good practices for Payments

(IBY) and Payments (CLL)

E his chapter contains notes and hints important for the correct functioning of Oracle

Payments and their locations.


User Manual 22

Bills

Master digit checker Agency

Make sure that the registration of agencies have the digit checker correctly

continas filled following the instructions in this manual.

Extension of Payment Method

Subscribe correctly extending the Payment Method. Is the impressindivel

registration of additional data for the perfect functioning of the locations.

Rules in Payment Methods

Add Rules on Payment Methods for avoiding payments without Electronics

normalization of the register of Bank / Agency / Bank Account provider. In creating the

Method of payment option is available on the screen for entering core rules

for creating transactions in Oracle Payables. If a rule for data validation

Bank Account is entered in the vendor payment methods containing containing

additional info = "Electronic", the core program itself had undertaken to put

a hold on the plots that possirem payment method with validation not

obey all the rules created.

Load the numbers representing a Billet?

The numbers contained in a ticket can be collected using an optical reader or

by manually entering the numbers specified in the document.

Reader Optics - In this case the barcode is read by the reader and transported

storage field automatically. Regardless of the brand or type of reader, the

value transferred to the storage field should be represented by the code

bar rather than the number available for the line digitavel.

Entered - In this case the user will enter the number sequence of the barcode such

which is described in the docket. Typing dots (.) Is mandatory. The spaces in

White should be disregarded. The lack of points typing, or typing

misuse of spaces and / or characters entail unforeseen error in the formatting

paylines, causing thus possible criticisms and rejections file

Payment.


User Manual 23

eft user guide - english.pdf

Documents

deliverables oracle

service request service

oracle payments

oracle payables

oracle integration hub

registering payment

registering results

limited use license