0% found this document useful (0 votes)
11 views3 pages

Formatos Multicash - SAP

Formatos Multicash - SAP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views3 pages

Formatos Multicash - SAP

Formatos Multicash - SAP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SAP Note No. 36833 14.02.

2019 Page 1
________________________________________________________________________

Number 36833
Version 9

Processor
Processing Status new
Implement. Status Cannot be implemented

Language EN
Short Text Multicash Format (auszug.txt and umsatz.txt)

Component TR-CM-CM
________________________________________________________________________

Long Text

Symptom

Multicash Format (auszug.txt and umsatz.txt)

Other terms

RFEBKA00, FF.5, mulitcash, RFEKA200, bank statement, electronic


format description

Reason and Prerequisites

Solution

The files have to be ASCII-coded, no quotes.


The delimiter between the fields is the semicolon ';'.

Type description:
A - Alphanumeric
N - Numbers
X - Date in Fomat DD.MM.YY
(Example 25.01.94 for January 25th of 1994)

AUSZUG.TXT
----------
Field# Type min. max. opt. Description

1 A 0 12 bank key
2 A 0 24 bank account number
3 N 1 4 statement number
4 X 8 8 statement date
5 A 3 3 currency key
6 N 1 18.2 opening balance amount
7 N 1 18.2 debit total
8 N 1 18.2 credit total
9 N 1 18.2 closing balance amount
10 A 0 35 bank account holder
11 A 0 35 X special account name
12 X 8 8 X life start
13 X 8 8 X life end
14 0 0 not used
15 0 0 not used
SAP Note No. 36833 14.02.2019 Page 2
________________________________________________________________________
16 0 0 not used
17 0 0 not used
18 N 1 5 number of records in statement
UMSATZ.TXT
==========

Field# Type min. max. opt. Description

1 A 0 12 bank key
2 A 0 24 bank account number
3 N 1 4 statement number
4 X 8 8 value date
5 N 1 10 X primary note number
6 A 0 27 X note to payee 1
7 A 0 27 X bank posting text
8 0 0 not used
9 A 0 4 X text key
10 A 0 16 X check number
11 N 1 18.2 amount
12 0 0 not used
13 0 0 not used
14 X 8 8 Posting Date
15 0 00 not used
16 0 00 not used
17 A 0 27 X note to payee 2
18 A 0 27 X note to payee 3
19 A 0 27 X note to payee 4
20 A 0 27 X note to payee 5
21 A 0 27 X note to payee 6
22 A 0 27 X note to payee 7
23 A 0 27 X note to payee 8
24 A 0 27 X note to payee 9
25 A 0 27 X note to payee 10
26 A 0 27 X note to payee 11
27 A 0 27 X note to payee 12
28 A 0 27 X note to payee 13
29 A 0 27 X note to payee 14
30 A 0 27 X business partner
31 A 0 27 X business partner
32 A 0 12 X bank key of the partner's bank
33 A 0 24 X bank account number of the partner
34 A 0 3 X business transaction code
35 0 0 not used

Changes if multicash-EURO is used: (See also note 109893)


36 A 3 3 currency key (OCMT)
37 N 1 18.2 amount (OCMT)

Important:

Field 34 ( business transaction code ) or field 9 ( text key ) are used


as 'External business transaction code (EBTC)' in Table T028G
.
If field 34 and field 9 are both empty then field 7 (bank posting text)
is used as EBTC.

________________________________________________________________________
SAP Note No. 36833 14.02.2019 Page 3
________________________________________________________________________

Valid Releases

________________________________________________________________________

Links to Support Packages

Software Component Release Package Name


________________________________________________________________________
________________________________________________________________________

You might also like