HTTPS://WWW Scribd com/document/346214992/Tcodes-List-S4HANA

PUBLIC
Enhancements in Bill of Exchange

Processing
Release Family 8.8
Applicable Release:
SAP Business One 8.82 PL05
Brazil
English
April 2012
© 2012 SAP AG. All rights reserved.

Enhancements in Bill of Exchange Processing 2
Table of Contents
Table of Contents .............................................................................................................................................. 2
Introduction ...................................................................................................................................................... 3
Glossary ............................................................................................................................................................. 3
Retorno File Import and Matching Wizard .................................................................................................... 4
Prerequisites ...................................................................................................................................................... 4
Settings for House Bank Accounts .................................................................................................................... 4
Defining Additional Codes in Payment Methods ............................................................................................... 5
Defining Retorno Operation Codes ................................................................................................................... 5
Duplicating Retorno Operation Codes ............................................................................................................... 6
Importing and Matching Retorno Files ............................................................................................................... 7
Loading Saved Files and Re-Matching Imported Transactions......................................................................... 9
Deleting Imported Files of Saved Wizard Runs ............................................................................................... 10
Payment Wizard Enhancements .................................................................................................................. 11
Alternative Posting Method for Bills of Exchange ..................................................................................... 15
Appendix A: BFP Tree Format Definition for CNAB240 and CNAB400 (Boleto Retorno) ...................... 16
Mapping or Constant Fields ............................................................................................................................. 17
Header Row Fields .......................................................................................................................................... 17
Body Row Fields .............................................................................................................................................. 18
Custom Validation Check Fields ...................................................................................................................... 20
Copyrights, Trademarks, and Disclaimers.................................................................................................. 21
Introduction
This document describes the enhancements towards business practice compliance implemented in SAP
Business One 8.82 PL05 to support bill of exchange processing.
Key enhancements:
 Retorno File Import and Matching Wizard – enables you to automatically import retorno electronic
files provided by the different banks in Brazil, and clear bills of exchange created in SAP Business
One against the transactions included in the imported retorno file.
 Payment Wizard – enhanced to support the processing of existing incoming bills of exchange and
the generation of bank files for bills of exchange in various statuses (Sent, Generated, Deposited,
and Paid).
 Bank File Formats – the following are supported:
o Remessa CNAB240 for Banco do Brasil of Cobranca type (outbound bank file)
o Retorno CNAB240 for Banco do Brasil of Cobranca type (inbound bank file)
 Possibility of mapping other bank file formats via the SAP Business One Electronic File Manager –
Format Definition add-on.
 Alternative posting method for bills of exchange.
Glossary
Term Abbreviation Definition
Remessa bank file Remessa Outbound bank file that contains
instructions to be executed by
banks for a specified incoming or
outgoing bill of exchange (or even
bank transfer). The file needs to
be manually communicated to the
bank (generally uploaded via the
bank’s webpage).
Retorno bank file Retorno Inbound bank file that contains a
reply from a bank for a specified
incoming or outgoing bill of
exchange. The file needs to be
manually imported into SAP
Business One via the new
Retorno File Import and Matching
wizard, and its contents need to
be processed further (bill of
exchange updated).

Retorno File Import and Matching Wizard

The Retorno File Import and Matching wizard enables you to do the following:
 Import new incoming bank files and match them against bills of exchange existing in your SAP
Business One company.
 Load saved files and try to match against transactions that were not matched in previous runs
 Delete saved wizard runs
To use the Retorno File Import and Matching wizard for the first time, you must complete the following
settings:
 Assign the retorno file format (mapped via EFM-EF) and define default G/L accounts for the different
house bank accounts you want to include in the wizard runs.
 Define additional parameters in the relevant payment methods.
 Define retorno operation codes.
Prerequisites
Settings for House Bank Accounts
1. From the SAP Business One Main Menu, choose Administration  Setup  Banking  House
Bank Accounts. The House Bank Accounts – Setup window appears.
2. Define the following parameters for each house bank account you want to include in the Retorno File
Import and Matching wizard run:
Field Activity/Description
Fine Account Specify the G/L account for posting fines paid by a customer.
Interest Account Specify the G/L account for posting interest paid by a customer.
Discount Account Specify the G/L account for posting the amount of discount granted to
a customer in cases of early payment.
Service Fee Account Specify the G/L account used for posting the service fee paid by the
company.
Other Income Account Specify the G/L account for posting other incomes paid by a customer.
Other Expense Account Specify the G/L account for posting other expenses granted to a
customer or to be paid to the bank.
Retorno File Format Assign the default file format to the account.
IOF Tax Account Specify the G/L account for posting the IOF tax charges for financial
transactions.
Collection Code The special code expected by the bank
File Sequence – Next No. Sequence used in outbound bank files to distinguish between two sent
files

Defining Additional Codes in Payment Methods

New codes are added to the payment methods defined for bills of exchange payment means. To define
these codes, follow the steps below.
1. From the SAP Business One Main Menu, choose Administration  Setup  Banking  Payment
Methods. The Payment Methods – Setup window appears.
2. Browse to the payment methods defined for bills of exchange. In the Bill of Exchange Options
section, choose the ellipsis (...) button. The BoE Property window appears.
Specify the following data:
Field Activity/ Description

Cancellation Instruction Instruction to cancel previously sent instruction
The purpose of the instruction is similar to those of the existing
Instruction 1 and Instruction 2 fields.
Occurrence Code The code with instructions for the bank in case of a CNAB400
scheme.
Movement Code Special code with instruction expected by some banks in Brazil
3. Choose Update.
Defining Retorno Operation Codes

The retorno operation code determines for the Retorno File Import and Matching wizard how to match each
existing bill of exchange with its corresponding transaction in the imported retorno file.
The retorno operation code is a combination of occurrence code, movement code, and bill of exchange
status, and is defined separately for each bank and each file format. To define retorno operation codes,
perform the following steps.
1. From the SAP Business One Main Menu, choose Administration  Setup  Banking  Retorno
Operation Codes. The Retorno Operation Codes – Setup window appears.

2. Define the following information:
Bank Code From the dropdown menu, select the code of the bank in which you
have a house bank account.
File Format From the dropdown list, select the required file format to be used for
importing the retorno file. If you intend to use multiple file formats for
a given bank code, you have to define a separate retorno operation
code for each file format.
Occurence Code, Define a combination of occurrence code and movement code, and
Movement Code, BoE
indicate to which BoE status it applies.
Status
During the Retorno File Import and Matching wizard run, when the
defined combination of occurrence and movement codes is detected,
the wizard recommends updating the status of the given bill of
exchange to the status you specify here.
Any given bill of exchange status can be indicated by multiple
combinations of occurrence and movement codes.
Description Enter a meaningful description. It will appear in the matching
recommendations provided by the Retorno File Import and Matching
wizard.
Color Click a cell in a given row to set a color indicator for each
combination. The colors are then visible when the matching
recommendations are displayed.
3. After defining all required combinations for the selected bank code and file format, choose Update.
Duplicating Retorno Operation Codes

If you have to create, for different banks and file formats, multiple retorno operation codes with minor
differences between them, you can duplicate an existing retorno operation code, apply it to the required bank
code and file format, and adjust it as needed. To do so, follow the steps below:
1. From the SAP Business One Main Menu, choose Administration  Setup  Banking  Retorno
Operation Codes. The Retorno Operation Codes – Setup window appears.
2. Browse to the retorno operation code you want to duplicate by selecting the bank code and the file
format from the respective dropdown menus.
3. From the menu bar, choose Data  Duplicate (or right-click or CTRL+D). A system message
appears notifying you that the rows of the displayed retorno operation code were duplicated. Choose
OK. The duplicated retorno operation code is displayed.
4. From the Bank Code and File Format dropdown menus, select the bank code and file format to
which you want to apply the duplicated retorno operation code. The Retorno Operation Codes –
Setup window is cleared.
5. From the menu bar, choose Data  Restore. The duplicated rows are copied to the newly created
retorno operation code.
6. Make any additional adjustments as required. For example, you can delete specific rows, add
additional rows, change colors, and so on. To save your settings, choose Update.

Importing and Matching Retorno Files

To import a retorno file received from the bank into SAP Business One and match the imported transactions
against bills of exchange existing in your SAP Business One company, perform the following steps:
1. From the SAP Business One Main Menu, choose BankingBill of ExchangeRetorno File Import
and Matching Wizard. Choose Next.
2. In the Import and Matching Run – Options (step 1) window, select the Start Retorno File Import and
Matching Run radio button. Choose Next.
3. In the Selection Criteria (step 2) window, specify the parameters related to the retorno file to import.
Choose Next.

Due Date From, To By default, all the transactions appearing in the imported file are
included in the wizard run. To include transactions having a due
date within a defined date range only, specify this date range
here.
Bank Account Select the house bank account for which you want to import the
retorno file.
File Format The file format defined for the specified house bank is
populated automatically. Specify another file format if required
and available.
File Choose the Import button to open a browsing window where
you can locate the file you want to import. The path is then
populated in this field.
4. The Matching Recommendations (step 3) window lists the transactions found in the imported file and
the bills of exchange documents created in SAP Business One that can be cleared against them.
The colors of the rows represent the colors defined for the retorno operation codes.
The column Matched BoE displays the bill of exchange created in your SAP Business One company
that matches the imported transaction in the given row. In case such a bill of exchange is not
identified, this field is empty.
Press Tab to open the list of existing bills of exchange and manually select a matching bill of
exchange, if one exists.
The Requested BoE Status field indicates the BoE status to be assigned to the given bill of
exchange after the wizard is executed. You can change it manually if needed.
Select the checkbox in the rows of the transactions you want to match. Choose Next.
Note
The matching recommendations are rated as follows:
 Automatic – when the BoE number, bank account, BP name, and transaction amount in
a bill of exchange existing in the SAP Business One company are identical to those of a

transaction in the imported retorno file, it is indicated as an automatic match. In this

case, the row in the matching recommendations window is selected by default.
 Manual – when the BoE number and bank account are identical in both the BoE
document in the SAP Business One company and in a transaction in the imported
retorno file, but the total amount or BP name do not match, the match recommendation
is indicated as Manual. In this case, the rows are not selected by default.
 Not Identified – if there is no bill of exchange document in the SAP Business One
company that matches a transaction in the imported retorno file, this transaction is
marked as Not Identified.
5. In the Save Options (step 4) window, select the Execute or Save Matching Recommendations radio
button. Choose Next.
Loading Saved Files and Re-Matching Imported

Transactions
All Retorno File Import and Matching wizard runs are automatically saved and can be accessed at any time
from within the wizard. In case not all the transactions included in a specific imported file were matched, you
can load the saved file and try to match these transactions again. To do so, follow the steps below:
1. From the SAP Business One Main Menu, choose BankingBill of ExchangeRetorno File Import
2. In the Import Run Selection window (step 1) select the Load Saved Retorno File and Matching radio
button. A list of all saved and executed wizard runs appears, displaying the following information:
Sequence No. Indicates the number of the imported file to distinguish it from the other files
Stamp Date The date on which the imported file was generated by the bank
Import Format The format of the imported file
Status ndicates whether the transactions from the file are matched or not:
 Draft – indicates that the file is imported but its transactions are not yet
matched. The number of transactions that are not matched appears in
brackets. For example Draft (10) indicates that the imported file
contains 10 transactions that are not yet matched against the
respective bills of exchange in SAP Business One.
 Executed – indicates that some or all of the transactions in this
imported file are matched against the respective bills of exchange in
SAP Business One. The number in brackets indicates the number of
matched transactions, for example Executed (23). Wizard runs with
the status Executed appear in green.
When some of the transactions in a given imported file are matched, and
some are not, there are two rows in the list to represent the two types of
transactions, with both rows having the same sequence number. For example,
a file containing ten transactions is imported. Six of them were not matched
and four were. The following rows appear in the list:
Sequence No. Status
33 Draft (6)
33 Executed (4)

3. To filter the list by bank account, from the Bank Account dropdown menu, select the required bank
account.
4. From the list, select the saved wizard run you would like to further process. The Rematch
Transactions checkbox appears. To try to match in the wizard run outstanding transactions that were
imported but were not matched in a previous run, select this checkbox.
Note
If you select an executed wizard run, this checkbox does not appear.
5. Follow step no. 3 onwards in the Importing and Matching Retorno Files section.
Deleting Imported Files of Saved Wizard Runs

In case a wrong file was imported by mistake, or for some other reason an imported file is not relevant, you
can delete it. To do so, follow the below steps:
1. From the SAP Business One Main Menu, choose Banking  Bill of Exchange  Retorno File Import
2. In the Import Run Selection (step 1) window, select the Load Saved Retorno File Import and
Matching radio button. The list of all saved wizard runs is displayed. Filter the list by bank account, if
needed.
3. Locate the wizard run you want to delete. From the menu bar, choose Data  Remove (or right-click
and Remove). A system message appears requesting verification that you want to delete the wizard
run. To continue, choose Yes.

Payment Wizard Enhancements

Enhancements were implemented in the payment wizard to improve the processing of bills of exchange. You
can now do the following:
 Generate bank files for transactions of bill of exchange payment means in several runs in order to
update the previous payment request, that is, the specific BoE record in the Remessa file.
 Generate outbound bank files from the payment wizard using a new default payment file format
Remessa CNAB240 (of Cobrança type) based on Banco do Brasil.
 Change the payment method proposed by the system in the payment rows of the payment wizard
recommendation report.
For information about the functionality of the payment wizard and the functionality and installation of the
Payment Engine add-on, see the online help as well as the document Payment Engine (including Cash &
Bank), which you can download from the documentation area of SAP Business One Customer Portal at
http://service.sap.com/smb/sbocustomer/documentation.
To open the payment wizard, from the SAP Business One Main Menu, choose Banking  Payment Wizard.
Following are the modifications implemented in the payment wizard to support the above mentioned
functionality:
 Handle Existing BoE checkbox – added to the General Parameters window (step 2) in the payment
wizard. Select this checkbox to include in the payment wizard run incoming bills of exchange that
already exist in your SAP Business One company. This checkbox is available only if the Bill of
Exchange checkbox is selected in the Payment Means section.
Note
When the Handle Existing BoE checkbox is selected, the Execute Payment Order Run radio
button in the Save Options (Step 7) window is disabled.

 BoE Selection Criteria section – added to the Document Parameters (step 4) window. You can use it
to fine tune the range of bills of exchange to be included in the payment run. This section is available
only if the Handle Existing BoE checkbox is selected in the General Parameters (step 2) window,
and applies only for incoming bills of exchange.
 House bank account details – in the Payment Methods – Selection Criteria (step 5) window, the
following newly added columns display the respective details relating to the bank accounts defined
for the displayed payment methods: Bank Code, Bank Name, Account Number, and Bank Account
Name.
 Recommendation Report – detailed information is displayed for the bills of exchange included in the
payment run; some of the parameters can be updated manually if needed:
BoE No. Drill down to the BoE record. You can edit this field only for non-
generated BoE objects, similarly to manual bill of exchange number
handling.
Bar Code Assign bar codes to outgoing payments (BoE from vendor), similarly
to manual outgoing payment handling.
Bank Code Displays the bank code of the house bank account linked to the
payment method in the payment row.
Bank Name Displays the bank name of the house bank account linked to the
Account No. Displays the number of the house bank account linked to the
Bank Account Name Displays the name of the house bank account linked to the payment
method in the payment row.

BoE Our Number Displays the number assigned by the bank for the specific BoE
document.
BoE Current Status Displays the current status of the BoE (Generated, Deposited, Paid).
Remessa Movement Code, The default values of these fields are taken from the selected
BoE Instruction 1, BoE payment method (linked to a house bank account).
Instruction 2, BoE
Cancellation Instruction,
BoE Internal Portfolio ID
choose-from lists
BoE Discount Amount Enter the amount of discount to be granted to a customer who pays
by the BoE discount date, and the date for granting the discount to
the customer.
BoE Interest Amount Enter the amount of interest to be charged to a customer who does
not pay by the BoE interest date.
BoE Interest Date Enter the critical date for charging interest to a customer.
BoE Fine Amount Enter the amount of fine to be charged to a customer who does not
pay by the BoE fine date.
BoE Fine Date Enter the critical date for charging a fine to a customer. The default
value is the BoE due date.
IOF Tax Amount Enter the amount of financial transactions tax.
NF No., Series, Subseries, Displays the values of these fields as saved with documents linked
Model to the payment (e.g. Invoice)

 Payment Run Summary – this step displays how many bills of exchange documents were created,
and for how many bills of exchange a request for status update was submitted through the given
payment run.

Alternative Posting Method for Bills of

Exchange
SAP Business One 8.82 PL05 introduces an alternative posting method for bills of exchange. You can
choose whether to continue working with the existing method or to use the alternative method by selecting
the Use Alternative Posting Method for Bill of Exchange checkbox on the Basic Initialization tab in
Administration  System Initialization  Company Details.
Note
Activating the alternative posting method is irreversible.
Once the Use Alternative Posting Method for Bill of Exchange checkbox is selected, the following behavior
applies:
 When creating (either manually or through the payment wizard) a payment using bill of exchange as the
payment means, a new bill of exchange document is created. However, no posting or BoE transaction is
created. As a result, the original balance due of the invoice (for which the payment was created) is not
affected.
 When updating the bill of exchange status from Generated to Deposited, no Journal Entry posting
transaction is created.
 When updating the bill of exchange status from Deposited to Paid, the posting behind the transaction
involves the original marketing document for which the bill of exchange was created (Accounts
Receivable or Accounts Payable) and the Bank on Collection or Bank on Discounted G/L account. The
same applies when the bill of exchange status is changed from Paid to Deposited or from Paid to Failed
 When the bill of exchange status is set to Paid, the invoice for which the bill of exchange was created is
reconciled with payment of Bill of Exchange payment mean.

Appendix A: BFP Tree Format Definition

for CNAB240 and CNAB400 (Boleto
Retorno)
This document describes the tree structure of the BFP file format needed for the successful implementation
of CNAB240/CNAB400 for the Retorno File Import and Matching wizard in SAP Business One.
The Retorno File Import and Matching wizard in SAP Business One expects a certain tree structure to be
present in the import transformation XML file. It is, therefore, mandatory to follow the BFP structure to meet
the wizard’s XML structure expectations of files imported through EFM runtime.
The BFP structure must consist of a Message segment group comprising Header and Transactions sub-
segment groups. The complete base tree structure is depicted below:
 Root
 Message
 Header
 Header Row
 Transactions
 Body Row
Core CNAB240/400 BFP Tree Structure
BFP Tree Item Type General Tab Attributes Tab Mapping Tab
Root Root Encoding:  Line Breaks -
ISO 8859-1 End of Line Symbol: \r\n
Latin 1
Message Segment - Regular Expression: BankStatement
Group
(?s).*
Header Segment  Mandatory Separator: \r\n No Mapping
Group Index: 1
 Regular Expression in
Separator
Header Row Standard  Mandatory Position: 1 No Mapping
Segment Length: 240 or 400
Transactions Segment  Mandatory Regular Expression: No Mapping
Group  Repetitive (?<=.*\r\n)(.+\r\n)*(?=.+\r\n$)
Body Row Standard  Mandatory Regular Expression: RetornoRow
Segment  Repetitive .*

Mapping or Constant Fields

The Header Row and Body Row nodes contain certain expected standard fields (described below). Each
standard field is mapped (Mapping tab) to a unique mapping field from the RetornoHeader or the
RetornoRow target table group. The mapping field can either transfer a value from the source Retorno file
(identified by position and length), or provide a constant value defined in the BFP file format itself.
The following table defines the types of mapping fields:
Validation Type Allowed Characters
IDNUM ”0”..”9”, ”/”
DATE ”0”..”9”
Values for Day, Month & Year must be within the
logical expected range (1..31 for day, 1..12 for
month, 1900..2099 for year).
DIGITS ”0”..”9”
CHARS ”a”..”z”, ”A”..”Z”
ALPHANUM ”0”..”9”, ”a”..”z”, ”A”..”Z”
MONEY ”0”..”9”, ”-”, ”.”
The money value must conform to the common real
value format.
(e.g. 123, -345, 234.55, -987.23)
STRING All characters allowed
If a certain field does not contain the expected characters, the Retorno File Import and Matching wizard
stops the import matching procedure with an error message and does not finish the import.
Header Row Fields

Note
All fields are defined as standard and mandatory.
Abbreviations used:
CF = constant field
MF = mapping field
TU = mapping field variant for Segment T or Segment U
CNAB240/400 Header Row Fields (RetornoHeader Target Table)
Standard Field Type CNAB2 Mapping Validation Description
40
Only
RETORNO_FORMAT FileFormat - CNAB240, CNAB400
(
CF
DATE_FORMAT CF DateFormat - DDMMYYYY

YYMMDD

CNAB240/400 Header Row Fields (RetornoHeader Target Table)

40
Only
IMPORT_CARD_NAM CF ImportCardNa - YES, NO
E me Determines whether to import
CardName or not.
CODE_HA CF  CodeHA DIGITS Header Archivo Code constant.
Value defined by bank.
CODE_HL CF  CodeHL DIGITS Header Lote Code constant. Value
defined by bank.
CODE_ROW CF  CodeRow DIGITS Row Code constant. Value defined
by bank.
CODE_TL CF  CodeTL DIGITS Trailer Lote Code constant. Value
defined by bank. For future use.
CODE_TA CF  CodeTA DIGITS Trailer Archivo Code constant.
Value defined by bank. For future
use.
ROW_CODE MF  RowCode DIGITS The value of Row Code on
particular line in RET file.
BANK_CODE MF BankCode DIGITS
BANK_ACCOUNT MF BankAccount DIGITS
BANK_BRANCH MF BankBranch DIGITS
AGREEMENT_NO MF AgreementNo DIGITS
AGREEMENT_NO_C CF AgreementNo CHARS YES,NO
HECK Check
CNPJ_CPF_CODE MF CNPJCPFCod DIGITS
e
CNPJ_CPF MF CNPJCPF DIGITS
CNPJ_CPF_CHECK CF CNPJCPFChe CHARS YES,NO
ck
COMPANY_NAME MF CompanyNam STRING
e
FILESEQ_NO MF FileSeqNo DIGITS
FILESEQ_DATE MF FileSeqDate DATE
Body Row Fields

Mapping fields for RetornoRow Target Table must be mapped in the case of CNAB240 for the T or U
segment. That is the reason why most of the mapping fields in RetornoRow Target Table come in three
variants: the basic one (for the CNAB400) and T_ or U_ prefixed (for the CNAB240).
Note
All fields are defined as standard and mandatory.
MF fields with T_ or U_ prefix variations are marked as TU in the table below.

CNAB240/400 Header Row Fields (RetornoRow Target Table)

Only
SEQ_NO MF  SeqNo -
Row will be
processed if
ROW_CODE MF  RowCode DIGITS equal to
CODE_ROW
constant
ROW_SEQ_NO MF  RowSeqNo -
Type of
ROW_TYPE MF  RowType CHARS Segment. U or T
expected.
OUR_NUMBER TU OurNumber ALPHANUM
PORTFOLIO TU Portfolio ALPHANUM
MOVEMENT_CODE TU MovementCode DIGITS
OCCURRENCE_CODE TU OccurrenceCode DIGITS
OCCURRENCE_DATE TU OccurrenceDate DATE
BOE_NUMBER TU BoeNumber IDNUM
BOE_DUE_DATE TU BoeDueDate DATE
CREDIT_DATE TU CreditDate DATE
TITLE TU Title MONEY
INTEREST_AMOUNT TU InterestAmount MONEY
DISCOUNT_AMOUNT TU DiscountAmount MONEY
SERVICE_FEE TU ServiceFee MONEY
IOF_TAX TU IOFTax MONEY
NET_AMOUNT TU NetAmount MONEY
PAID_AMOUNT TU PaidAmount MONEY
FINE_AMOUNT TU FineAmount MONEY
OTHER_CREDITS TU OtherCredits MONEY
OTHER_EXPENSES TU OtherExpenses MONEY
OTHER_INCOMES TU OtherIncomes MONEY
CANCELLATION_CODE TU CancellationCode ALPHANUM
CARD_NAME TU CardName STRING
ERRORS TU Errors STRING

Custom Validation Check Fields

In order to create flexible and robust bank-oriented BFP files, it is possible to define (as part of the BFP
format) custom checks on fixed values that should always be present in RET files, because the bank
requested them. Additional checks on such fixed values can increase assurance of importing only the right
files from the right bank; it is assumed that the absence of some fixed value in a RET file indicates either
data corruption or an incorrect file.
As part of BFP definition, users can define up to 9 custom value checks by using the following mapping fields
of RetornoHeader and RetornoRow Target Tables:
 ValueXToCheck
 ValueXExpected
(where X is a number from 1 to 9)
The ValueXToCheck mapping field (it is an MF field) defines position and length in the RET file for retrieving
data.
The ValueXExpected mapping field defines a constant value that has to be present in the respective
ValueXToCheck field for the RET file to be considered valid.
The Retorno File Import and Matching wizard processes ValueXToCheck and ValueXExpected fields by
comparing, and it stops the import process execution if any difference is found.

Copyrights, Trademarks, and Disclaimers

© Copyright 2012 SAP AG. All rights reserved.
The current version of the copyrights, trademarks, and disclaimers at http://service.sap.com/smb/

sbocustomer/documentation is valid for this document.

HTTPS://WWW Scribd com/document/346214992/Tcodes-List-S4HANA

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

HTTPS://WWW Scribd com/document/346214992/Tcodes-List-S4HANA

Diunggah oleh

Hak Cipta:

Format Tersedia

PUBLIC

Enhancements in Bill of Exchange

Release Family 8.8

© 2012 SAP AG. All rights reserved.

© 2012 SAP AG. All rights reserved.

Retorno File Import and Matching Wizard

© 2012 SAP AG. All rights reserved.

Defining Additional Codes in Payment Methods

Field Activity/ Description

Defining Retorno Operation Codes

© 2012 SAP AG. All rights reserved.

2. Define the following information:

Duplicating Retorno Operation Codes

© 2012 SAP AG. All rights reserved.

Importing and Matching Retorno Files

© 2012 SAP AG. All rights reserved.

© 2012 SAP AG. All rights reserved.

transaction in the imported retorno file, it is indicated as an automatic match. In this

Loading Saved Files and Re-Matching Imported

© 2012 SAP AG. All rights reserved.

Deleting Imported Files of Saved Wizard Runs

© 2012 SAP AG. All rights reserved.

Payment Wizard Enhancements

© 2012 SAP AG. All rights reserved.

© 2012 SAP AG. All rights reserved.

© 2012 SAP AG. All rights reserved.

© 2012 SAP AG. All rights reserved.

Alternative Posting Method for Bills of

© 2012 SAP AG. All rights reserved.

Appendix A: BFP Tree Format Definition

© 2012 SAP AG. All rights reserved.

Mapping or Constant Fields

Header Row Fields

DATE_FORMAT CF DateFormat - DDMMYYYY

© 2012 SAP AG. All rights reserved.

CNAB240/400 Header Row Fields (RetornoHeader Target Table)

Body Row Fields

© 2012 SAP AG. All rights reserved.

CNAB240/400 Header Row Fields (RetornoRow Target Table)

© 2012 SAP AG. All rights reserved.

Custom Validation Check Fields

© 2012 SAP AG. All rights reserved.

Copyrights, Trademarks, and Disclaimers

The current version of the copyrights, trademarks, and disclaimers at http://service.sap.com/smb/

© 2012 SAP AG. All rights reserved.

Anda mungkin juga menyukai