sapnote_0001514922

26.09.2011 Page 1 of 4

SAP Note 1514922 - BR:RFEBKA00:DDA Legal Changes forFebraban,Itau and Bradesco

Note Language: English Version: 7 Validity: Valid Since 29.06.2011

Summary

Symptom

A new process is introduced, which replaces the boleto on paper intoelectronic boleto version(e-boleto), and is termed as DDA (Direct DebitAuthorised).Therefore the current paper boleto will be replaced by the e-boleto forDDA.

Boleto is a document for collection / a payment slip that can be printed orcan be electronic, and contains the data for collection. This document canbe paid at any bank until the due date.

The DDA system allows customers to access the bills to pay in electronicformat and the payments are done without any document in paper. The DDAprocess requires the (outgoing) payment process (F110) because theacceptance of the payer is needed (authorized debit).

This new procedure for e-boletos will be processed for these 3 formats:a) FEBRABANb) ITAUc) BRADESCO

In the existing Accounts receivable and Accounts payable payment processes,few modifications need to be carried out:

Accounts Payable:In accounts payable, the electronic payment slip received from the bankcontains the barcode information. This barcode information(44 digits) isdistributed over various fields in the incoming file, and needs to beconverted into a 47 digit numerical barcode, and then updated in thecorresponding accounting document(vendor invoice).No payment can be done without the barcode in the accounting document.These documents with the updated numerical barcode, are included in thenext payment run(F110).

Before the 47 digit numerical barcode is updated in the open vendorinvoice, the CNPJ/CPF number, due date and the amount present in theincoming file is compared with that of the open invoice in the sytem. Ifthese 3 values match, only then the numerical barcode is updated in theopen vendor invoice.

The documents where these 3 values do not match with that of the openvendor invoice in the system, are displayed in an error log.These error records need to be later handled manually.

a) For FEBRABAN and ITAU, the incoming bank file contains a newSEGMENT 'G'. This segment is specific to this new DDA requirement, andcontains the complete information about the barcode.

The program RFEBKA00 is modified accordingly to handle the incoming bankfile with the new Segment 'G', and updates the barcode automatically in the

26.09.2011 Page 2 of 4


open invoice if the document is successful(CNPJ, due date and Amountsmatch).

b) For BRADESCO, the bank file does not contain an explicit segment forDDA.The Bradesco file format contains just a Header, Detail Register andTrailer. The Detail register contains all informatiom about the barcode.

The program RFEBKA00 is modified accordingly to handle the incoming barcodeinformation present in the incoming file and updates the 47 digit numericalbarcode automatically in the corresponding vendor invoice, if the documentis successful(CNPJ, due date and Amounts match).

Account Receivables:In accounts receivables, there are certain changes in the existing filelayouts,and some field contents for remittance and return file formats.There is no new requirement in the accounts receivable process.

Other terms

FI, Brazil, DDA, Numerical Barcode, E-Boleto, RFEBKA00, RFEBBU00, RFFOBR_D,J_1B_BARCODE_CONTROLDIGIT_DDA, RFFOBR_U, Febraban, Itau, Bradesco, CNPJ,CPF, Due Date, Amount, Accounts Payable, Accounts Receivable, FEBKO, FEBEP,FEBRE, F110, FB02, FB03, REGUH, REGUP, Segment G, Vendor Invoice, ErrorLog, KUKEY, KTONR.

Reason and Prerequisites

The requirements put forth under the section "Symptom" are new and havenot been met till now. The current Note fulfills them.

THE SOLUTION FOR THE DDA PAYMENTS IS ONLY AVAILABLE FROM THE RELEASE 600AND ABOVE

Solution

The modifications suggested in this Note will be provided in the nextsupport package. For immediate results, please do the following steps.

Perform the following manual steps in sequence:

1. Do the manual steps as explained in the document"Documents_Note_1514922_DDIC_1.zip" to create the database objects.

2. Do the manual steps as explained in the document"Documents_Note_1514922_DDIC_2.zip" to create the database objects.

3. Do the manual steps as explained in the document"Documents_Note_1514922_FM1.rar" to create the Function modules.

4. Once these manual steps have been done, apply the correctioninstructions attached with this note.

26.09.2011 Page 3 of 4


Header DataRelease Status: Released for CustomerReleased on: 27.07.2011 10:29:57Master Language: EnglishPriority: Correction with medium priorityCategory: Legal changePrimary Component: XX-CSC-BR-FI Payment Files

Secondary Components:FI-AP-AP-B1 Payment transfer (w/o DE, US)

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 600 600 600SAP_APPL 602 602 602SAP_APPL 603 603 603

Support Packages

Support Packages Release Package NameSAP_APPL 600 SAPKH60019SAP_APPL 602 SAPKH60209SAP_APPL 603 SAPKH60308

Related Notes

Number Short Text1581476 DDA:Incorrect length of the field A322(structure J_1BELBYA)1579415 DDA Phase 2 development1529125 BR:RFEBKA00:DDA Legal Changes for Febraban,Itau and Bradesco

Attributes

Attribute ValueDownPort/UpPort-WF UpPort check done, symptom

not repaired

Attachments

FileType

File Name Language Size

RAR Documents_Note_1514922_FM.rar E 130 KBZIP Documents_Note_1514922_DDIC_1.zip E 1.641 KBZIP Documents_Note_1514922_DDIC_2.zip E 1.828 KB

26.09.2011 Page 4 of 4


Correction Instructions

Correction

Instructions

Validfrom

Validto

SoftwareComponent

Type

*)

ReferenceCorrection

LastChanged

938933 600 600 SAP_APPL C P7DK196485 24.11.201007:55:08

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work