EN_RFFOJP_L(1)

Globalization Service / SAP AG

Foreign Remittance

(Since SAP R/3 Release 4.6C)

© 2012 SAP AG. All rights reserved. 2

Domestic Vendor

(Domestic Bank) (Domestic Bank) (Foreign Bank)

Company Foreign Vendor

What Format ??

SWIFT

Oversea Japan

Zenginkyo

Format

Zenginkyo

Format

Zenginkyo

Format

Data Exchange Between Banks and Companies

Data exchange within Japan is done in Zenginkyo Format.

If a bank is a foreign affiliated firm and non-member of Zenginkyo, they must follow their own data exchange format.

Data exchange between a domestic bank and a foreign bank is normally done in SWIFT.


Data transfer between Bank and Company

International standard

SWIFT MT100 (Outgoing Payment)

SWIFT MT940 (Incoming Payment)

Japan : ‘Zenginkyo’ format

Domestic Transfer (since Rel.2.0)

Wage Transfer (Profit Org) (since Rel.2.0)

Incoming Remittance (since Rel.3.0)

Incoming/Outgoing Payment (since Rel.3.0)

Foreign Remittance (since Rel.4.6)

Foreign Exchange Transaction Statement: Add-on (Since Release 3.1H, SAP

Japan’s chargeable consulting services)

* When exchanging data between Japanese banks in Japan, Zenginkyo format must be used.

* Each Zenginkyo format is different in record length, layout, record order and editing method

= about 30 record formats for applicable businesses cases.

MT100 and MT940 of International Standard

(SWIFT) is supported in R/3 standard

program and there are many SAP extensions

(exits).

Zenginkyo has established about 30 different

record format to meet applicable businesses

cases.

Each record format is different in record

length, layout and record order and editing

method and it is necessary to have a program

for each record format.

RFFOJP_T : Domestic Transfer

RFEBJP00 : Remittance

RFFOJP_L : Foreign Remittance

RFFOM100 : SWIFT MT100


Application for Foreign Remittance

Zenginkyo Format: Foreign Remittance Record

Application for Foreign Remittance(Japanese), Payment advice (Receiver’s

language): SAP script

Rate Category

Zenginkyo accepted – SPOT, CONT, NOEX, Yen, Yen equivalent currency

Not Zenginkyo accepted - Foreign currency equivalent to other currency remittance, Foreign currency

equivalent to Yen remittance (Only output possible on Application for Foreign Remittance)

Transfer Type Category, Payment Category, Instruction Key, Transfer Reason

(International Income Item Number) can be set by parameters setting.

Send Payment Order number taken by automatic payment (F110) as requester’s

reference number to the bank

Accounting line items : Using OPEN FI, it is possible to divide one remittance

data to three installments.

Foreign Remittance (Zenginkyo Process)

by SAP (Rel. 4.6)


Invoice

Foreign Transfer (Zenginkyo Process) by SAP (Rel. 4.6)

1/3

AP

Open items Data

Receiver

(Vendor)

FB01: Post AP / MIRO: Logistics Invoice Verification

FB02: Document Change by an employee in the

accounting or treasury division

Set the detail information on

foreign remittance

1

2



2/3

* settlement of open items by using

Payment Order number Origination of transfer

Zenginkyo

Format

DME-file

Receiving Bank

(Vendor’s Bank)

AP

Open items Data

Automatic

Payment Program

* Take Payment Order

number (remains open

items)

Payment Data

REGUH

Receiver

(Vendor)

Sending Bank

(House Bank)

Mail/FAX

Manual payment, or

Import Foreign Exchange

Transaction Statement

(add-on)

Foreign Remittance

Program (standard)

Zenginkyo

Format

DME-file

Application

for Foreign

Remittance

Payment

advice Foreign Remittance

Program (add-on)

3

4

5



3/3

Flow after receipt of source data (AP Open Item data) for transfer is as follows.

- First, generate payment data from open items data by using the Automatic payment process (F110)

- Next, using Application for Foreign Transfer program (RFFOJP_L), generate Application for Foreign

Transfer Data

(Execute as print program of automatic payment)

Application for Foreign Remittance Data: DME File in Zenginkyo Format

Application for Foreign Remittance: When requesting transfer to a bank on a paper or for keeping it

your file. (This is a privately generated foreign remittance application form, therefore it is necessary

to obtain the bank’s permission beforehand.)

Payment Advice: Notification to Receiver (Vendor) (possible to output in the language of vendor

master)

SAP Japan separately sells an add-on program that is a modification of standard program

Apply for foreign remittance at the bank.

- Request a sending bank to do “Foreign Bank Transfer” (electronically send DME file or send Foreign

Transfer Request by FAX / Mail / Manual Delivery)

- Send Receiver (Vendor) the Payment Advice by FAX or Mail.

- Sending bank transfers the payment to receiving bank, then returns the actual rate and fee information

to the requester.

- Using actual rate by the sending bank, settle the open items and post the fee. (Automatic Settling

program has been developed as an add-on and being separately sold by SAP Japan)


Agenda

1: Pre-Configuration

2: Vendor Master Data Define

3: Accounting Document

4: Automatic Payment

5: Enhancement RFFOX230

Appendix A: ZENGINKYO Record Layout

Appendix B: Payment Program (Process Flow)

Appendix C: Add-on Programs Provided by SAP Japan Chargeable Consulting

Service

1. Pre-Configuration


1: Pre-Configuration

1.1 Define a function module in the ‚Event‘

1.2 Define Instruction Key (Transfer Type, Payment Type, Exchange Rate

Category, Cost Allocation on Bank Charge)

1.3 Payment Method in Country

1.4 Setting for the form of ‚Application for Remittance‘

1.5 Setting for the form of ‚payment advice‘

1.6 Bank Determination (Sending Bank)

1.7 Setting for House Bank

1.8 State Central Bank – Object of Transfer


1.1 Define a function module in ‚Event‘

IMG: Financial Accounting -> Financial Accounting Global Settings -> Tools -> Customer Enhancements ->

Business Transaction Events -> Settings -> P/S function Modules -> Of on SAP Appl.

If there are different categories of the exchange rate for one

document, it should be updated on the document separately.

Therefore, to enter the different category of exchange rate,

two function modules are used under the FI posting event.

Please refer to the below description ‘3.3 Additional

Information for Bank Transfer Abroad’.

Open FI for Foreign Remittance

Since Rel. 4.6 additional events are available for Japanese foreign remittance

Event－1012 : At change document, when ‘More Data’ icon is clicked it displays

Additional Information for Line Item screen

Event－1013 : At change document, when ‘*’ is entered in Reference key 3,

‘More Data’ icon is displayed.


1.2 Define Instruction Key

Transfer Type, Payment Type, Exchange Rate Category

IMG: Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Data Medium Exchange -> Define Instructions for Payment Transactions

** Instruction key is used in Japan for data medium exchange abroad.

A maximum of

four fields are

available for

entering

instructions.

Japan only uses

3 fields for

instruction key.

Instruction Key consists of four fields. These fields are filled during posting an

A/P document. But Japan uses only 3 fields.

1st field is for Transfer Type. It informs the bank whether payment should be

wired or mailed, or whether a check should be sent.

2nd field is for Payment Type, it informs the bank whether the payment should be

made according to notification or to an account.

3rd field is for Exchange rate category. It informs the bank whether the currency

translation should be made according to the current rate of exchange or a

hedged exchange rate, or whether payment should be made from a foreign

exchange account or in Japanese Yen.

So you have to define what kind of transfer type, what kind of payment type and

what kind of exchange rate category will be permitted per each field as next

screen.

For example) 3rd field allows 6 instruction keys. If a payment should be done with

current exchange rate, you have to select ‘1’ in the 3rd instruction key field.

Caution: Value of the field ‘Instrtn’ in the screen in the next page will be used

during FI posting, but the value of the field ‘Code word’ will be used in the DME

file’. For more information of Instruction key, Please refer to the below diagram.


The permitted entry values for

1st instruction key field

The permitted entry values

for 2nd instruction key field

The permitted entry values

for 3rd instruction key field

1.2 Instruction Key

Transfer Type, Payment Type, EX rate category

Field

1 : Transfer type

2 : Payment Type

3 : EX rate category

Codes decided by Bank

(output on DME file)

Texts of Codes

(output on form of payment order)


1.2 Instruction Key

Transfer Type, Payment Type, EX rate category

Usable Exchange rate category in ‘Zenginkyo’ format

01: SPOT (Current rate)

02: CONT (Hedged exchange rate)

03: NOEX (Payment from foreign exchange account )

04: Payment in Yen from Yen account

05: Yen equivalent

It should be converted to ’01’, because only 01-04 are admitted by Zenginkyo format.

Ex) Currency of AP is Yen and paid by foreign currency (using ‘payment currency’ )

An invoice 100 Yen is paid by 1 USD.

06: Foreign currency equivalent

It should be converted to ’01’. This is not output on DME.

Ex) Currency of AP is foreign currency and paid by the other foreign currency (using ‘

payment currency’)

An invoice 100 Russian ruble is paid by 110 USD.

07: Payment by Yen equivalent to foreign currency

It should be converted to ’01’. It is not output on DME.

Ex) Currency of AP is foreign currency and paid by Yen (using ‘payment currency’)

An invoice 1USD is paid by 100 Yen.


1.2 Instruction key

Cost Allocation on Bank Charge

Instruction key is set

on Bank Master of Vendor Master

Instruction Key

You can define an Instruction keys per payment method. The field of ‘CA’ means

Cost Allocation key which is used for both transfers by DME with the following

values:

1 Charges payable by payee

2 Charges payable by payer

You have to define this instruction key in the vendor master data.

Please refer to the 2.2 Vendor Master - Bank Information (Sending Bank).

Instruction Key has three types of information:

1) ‘Transfer Type’ ,2) ’Payment Type’,3) ’EX rate

category’.

Translation Example:

Payment Method ‘E’ and Instruction key ’01’

- Transfer Type’1’ : Telegraphic transfer

- Payment Type’2’ : Payment to an account

- EX type catgory’1’ : Current rate Exchange

- Bank charge is paid by Payee


1.2 Instruction key

Exchange Category

Instruction key is set as the

default value in Vendor Master,

House Bank Master

(Case No)

(1) (2) (3) (4) (5)

(6) (7)

Document(AP)

Currency =JPY

(dta_pswsl)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Payment Currency

=JPY

(dta_waers)

Yes

Yes

Yes

No

No

No

No

Account Currency

=JPY

(up_twaers)

Yes

Yes

No

Yes

Yes

No

No

Contract Number

=No input

Yes

No

Yes

No

Yes

No

Exchange

rate

category

(up_exchange)

04

Error

Error

05→01

SPOT

Error

Error

Error

This matrix explains how Exchange Rate Category is decided by

FORM accounting_info_fields_fuellen / include RFFORIJ5 / RFFOJP_L.


1.2 Instruction key

Exchange Category

（Case No)

Document(AP)

currency =JPY

Payment

Currency=JPY

Invoice Currency =

Payment Currency

Account

Currency=JPY

Invoice currency ＝Account currency

Payment currency ＝Account currency

Contract Number =

No input

Exchange

rate

category

(8)

No

Yes

(No)

Yes

(No)

Yes

07

→

01

(9)

No

Yes

(No)

Yes

(No)

No

Error

(10)

No

Yes

(No)

No

Error

(13)

No

No

Yes

No

Yes

Yes

03

NOEX

(14)

No

No

Yes

No

Yes

No

Error

(12)

No

No

Yes

Yes

(No)

NO

02

CONT

(11)

No

No

Yes

Yes

(No)

Yes

01

SPOT

(15)

No

No

Yes

No

No

Error

(16)

No

No

No

Yes

Yes

06

→

01

(17)

No

No

No

Yes

No

Error

(18)

No

No

No

No

Yes

Yes

Error


1.2 Instruction key

Exchange Category

（Case No)

Document(AP)

currency =JPY

Payment

Currency=JPY

Invoice Currency =

Payment Currency

Account

Currency=JPY

Invoice currency ＝Account currency

Payment currency ＝Account currency

Contract Number

=No input

Exchange

rate

category

(19)

No

No

No

No

Yes

No

Error

(20)

No

No

No

No

No

Error



If this flag is on in F110,

payment order is created

without creating the payment

document.

For foreign transfer, a payment

order is created during automatic

payment program instead of FI

Document.

Payment Program Parameters

Setting: Payment Method in

Country

Report Program : RFFOJP_L

Creation of Payment Order Only:

In automatic payment process, pick

payment order number without

settling open items.

When received the actual rate from

the bank, then settle with the

payment order number and post

realized exchange gain/loss.

Open items which has payment

order numbers can be settled just

by the payment order number and

they are not included in other types

of settlement and other automatic

payment processes.

IMG: Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions ->

Outgoing Payments -> Automatic Outgoing Payments -> Payment Method/Bank Selection for Payment

Program -> Set Up Payment Methods per Country for Payment Transactions



Japan uses RFFOJP_L to create DME file

for foreign transfer. If you want to use PMW,

PM Format should be developed.


1.4 Setting for the form of ‘Application for Remittance’



Program -> Set Up Payment Methods per Company Code for Payment Transactions

To define the form of ‘Application for

Remittance’ to be sent to bank.

Please refer to the 4.4 Application for

Remittance and Payment advice’. You can

choose whether to send DME file or to send

the Application for Remittance in the program

‘RFFOJP_L’.


1.5 Setting for the form of payment advice



Program -> Set Up Paying Company Codes for Payment Transactions

To define the form of payment advice.

Please refer to the 4.4 Application for

Remittance and Payment advice’.


1.6 Bank Determination (Sending Bank)



Program -> Set Up Bank Determination for Payment Transactions


1.7 Setting for House Bank

IMG: Financial Accounting -> Bank Accounting -> Bank Accounts -> Define House Banks

This customer number

is given by bank.

When creating DME

file, it should be

defined.

Determine the default

value of ‘Transfer

Type’, ‘Payment

type’,’EX rate

category’. This setting

has priority over one

of vendor master.

House Bank Master Record:

DME data

Customer Code(T012-DTKID): 10

digit number, which is assigned by

the house bank and used as

remittance requester’s code in

foreign remittance.

(Transfer requester’s code in

domestic transfer is the company

code (T012-DTFIN) of central bank

code.)

Instruction Key: Used as the initial

value of Bank Charge Liability Code

(Transfer type category, payment

category, Exchange rate category)



Incoming Invoices/Credit Memos -> Define SCB Indicator for Foreign Trade Regulations

Text for Payment Notice

Text for DME file

This is input on

Document item

1.8 State Central Bank－Object of

Transfer (Number of Payment Purpose)

Parameters Setting :

Central Bank Code

For remittance purpose, set

International Balance of Payment

Number (4 digits number)

Invoice type for report record :


Number’s first digit

Flag per service detail :


Number’s last three digits

Reason for Payment first line :

displayed in the text of application

for foreign remittance

Reason for payment second line:

Used as the remittance text in

DME file (Half-size Katakana）

http://www.boj.or.jp/z/tame/regtlist.pdf

(Japanese only)

Number of payment purpose is

4byte.

This number is defined by using

two fields.

First 1 byte is defined in

‘Document Type…’

and the other 3 bytes are defined

in

‘’Indicator acc….’

This Example is ‘010’

http://www.boj.or.jp/z/tame/regtlist.pdf

2. Vendor Master Data Define


2 Vendor Master Data Define

2.1 Address Information

2.2 Bank Information (Sending Bank)

2.3 Information for Payment


2.1 Vendor Master - Address Information

The notice for

remittance can

be printed by the

receiver’s language

Edit address (postal code,

city, Region) by address

layout key

of the country code

Information of payee’s

Address

will be described in the

DME file.

Vendor Master: Address

Name: Receiver’s name

Address: Edit address (postal code, city,

Region) by address layout key of the

country code

Mark “Print Country Name” in the

country definition.

Country Name : Use English Country

Code Names

Language: Can be used as the text

language on the payment notification


2.2 Vendor Master - Bank Information

Receiver’s Bank

Instruction Key :

Determines the default value of

‘Transfer Type’ ,’Payment type’, ’EX rate category’

And ‘Bank charge’. This instruction key is defined

In ‘OB47’. Please refer to the 1.2: Define Instruction

Key.

Bank information of payee :

1:Bank Key -> Bank No

2:Bank account

3:Acct holder-> name of payee

4:CK.=> Type of account

This information is transferred to the payment

medium by the payment medium print program.

For example, the following account types are

used in Japan.

01 FUTSU (broadly equivalent to a savings

account)

02 TOUZA (broadly equivalent to a checking

account)

04 CHOCHIKU (broadly equivalent to an assets

account)

09 Other bank accounts

Vendor Master: Bank Data

Receiver’s Bank Country code, Bank Code (Receiving Bank, used in Bank master as well), Account

Number, for some countries even Bank Control Key and Reference Detail are also needed.

Instruction Key : Used as the default value of Instruction Key (Remittance Type Category, Payment

Category, Exchange rate category). (If it not there, the code in House Bank master is used)


2.3 Vendor Master - Information for Payment

In case of Foreign Transfer, the standard

configuration for payment method is ‘E’ used

for Japan.

Vendor Master : Payment

Payment Method

Group Key : Payment Documents are divided by values in Group key.

Unit of generating REGUH entries

In case that “central bank code” is a grouping key, per “central

bank code”, the REGUH entries are generated.

In case that “single payment for marked item” is specified in the

definition of “payment method per company code”, the REGUH

entry is generated per single item. This is mandatory when the

entries in Reference key 3 exist.

3. Accounting Document


3 Accounting Document

3.1 Accounting Document

3.2 Additional Information for Foreign Transfer

3.3 Additional Detail Information for Bank Transfer Abroad


3 Account Document

Message to Payee： PAYER I/2000-123456789 OF 21/01/03 ADVERTISING EXPENSES

(reference number) (Invoice date) (item text)

Example of the Vendor Document Entry

screen in Financial Accounting

As a message addressed to the receiver,

edit Reference number, Invoice Date,

and Item text

‘payer’: Constant letters

Reference Number: Invoice Number

‘Of’: Constant letters

Invoice Date: Date in Receiver’s

country layout

Item Text: Remove First character ’*’

(Can’t be used if ’*’ not the first

character)


3.2 Adding Information for Foreign Transfer

Object of transfer -> Number of payment purpose.

Please refer to the ‘1.8 State Central Bank’

If you want to split accounting data depending on the exchange rate category

or contract no, you have to enter * in the field of ‘Reference key 3’ to jump up

to the next screen of ‘Japanese Bank Transfer Abroad. This is not a standard

procedure. To use this screen, you have to define two function module in the

event. Please refer to the 1.1 Define a function module in the ‘EVENT’.

Additional Information Entry by Financial

Department according to needs

Payment Currency:

In case of payment with different

currency other than Invoice currency

(Not accepted by Zenginkyo format)

Instructions:

In case of changing the default value

from Vendor Master / House Bank

Master Instruction Key1 : Transfer Type Category

Instruction Key2 : Payment Category

Instruction Key3 : Exchange Rate Category

Reference Key 3:

the reference number from reserving

foreign exchange OR if splitting

accounting process of a line item into

installments (up to 3), then enter ‘*’

Instruction Key: Transfer Type,

Payment type, EX rate

category

You can change default value

from setting in Master data.


3.3 Additional Detail Information for Bank Transfer Abroad

You can split the amount depending on

the Exchange Rate Category and

Contract no

Exchange Rate Category

Contract Number with

house bank

Additional Detail for line Item:

Only when entering ‘*’ in reference key 3,

it is possible to enter additional

information on Japanese Bank Transfer

Abroad – Accounting Information ER Category : Exchange Rate Category

Amount : Up to 3 total amount should match

the invoice amount

Contract Number : Reservation Number

Account ID : Enter House Bank Code

Caution

This information is NOT linked with

FSCM-TRM.

Prerequisite:

1. Document change

2. House bank is specified.

3. Individual payment

4. Impossible to transfer Yen

equivalent amount by foreign

currency (ZENGINKYO Rule)

4. Automatic Payment


4 Automatic Payment

4.1 Payment Run (F110) - Parameter Setting

4.2 RFFOJP_L Program

4.3 DME File

4.4 Application for Remittance and Payment Advice

4.5 Application for Foreign Remittance

4.6 Payment Advice Notice

4.7 Clearing Account


4.1 Payment Run (F110) - Parameter Setting

Please select the payment method

‘E’ for Foreign Transfer.


4.2 RFFOJP_L Program

You can select whether to send the form of

Application for remittance or DME file to

bank.

Set Variant as the print program of automatic payment

Parameter entry screen for Application for Foreign

Remittance Program (RFFOJP_L) which became

standard after Rel. 4.6.

Record as a Variant and set as the report program of

automatic payment process.

Proposal Run Only possible:

Not recommended to use for checking purpose

Print control Print payment medium:

Foreign Transfer Request (SAP script, Japanese)

Data Medium Exchange:

DME file in Zenginkyo’s Foreign Transfer Request format

Print Payment advice notice:

payment advice notice (SAP script, output in the language of

vendor master record)

Output control End of File:

Setting for CR/LF possible

Text in Receiver’s language:

Print payment advice notice in the language of vendor’s

master record


4.3 DME File

DME file in Zenginkyo’s Application for Foreign Remittance Layout

To the bank requested for transfer, it is downloaded by DME controller and send it by a non-SAP data

sending system.

Code change of Data is done in non SAP system according to needs (EBCDIC, JIS).


You can print out the form of ‘Application for Remittance’ and ‘Payment

Advice’ here. The related form should be configured in the IMG of automatic

payment. Please refer to the 1.4 Setting for the form of ‘Application for

Remittance’ and 1.5 Setting for the form of payment advice.

4.4 Application for Remittance and Payment Advice


4.5 Parameters Setting Payment Methods of Company

Code－Format of Application for Foreign Remittance

Payment Program Parameters Setting : Payment Methods of Company Code

Form for the payment transfer medium : SAP script name for application for foreign remittance format.

In standard, F110_JP_TRANS_L is provided

Drawer on the form : Used the transfer requester’s name for DME file


4.5 Form of “Application for Foreign Remittance” (SAP

Script)

Application for Remittance

number is the one which is

numbered through automatic

payment process.


It is SAP script and use Japanese text

It is privately made, therefore must obtain bank’s permission beforehand.


4.6 Paying Company – Payment Advice Notice Format

Payment Program Parameters Setting : Paying Company Code Data

Form for the payment advice : payment advice notice format name of SAP script

(It is the same document format as that of domestic transfer. The language of text can be set different for

each payment method)

In standard, English text is prepared for F110_JP_AVIS.


4.6 Payment Advice Notice (SAP Script)

Payment Advice Notice

It is SAP script and uses logon language or receiver’s language for text.

(Only printable language through a printer)


4.7 Clearing AP

Settlement of open items with actual rate

Payment Order Number : It is used as requester’s application number at the time of application for

foreign remittance.

Only by using

“Payment Order”,

AP items with

Payment Order can

be found.

5. Enhancement RFFOX230


Function module EXIT_RFFOEXIT_230

User Exit Foreign DME Japan Data Records 2 and 6

You use the user exit to make modifications to Japanese DME format to foreign countries.

The fields from the DTAMJP structure are available for changes.

Create an include file called ZXFORU34 in order to program the required modifications.

The file will be included in the EXIT_RFFOEXIT_230 function module.

Use the Enhancements transaction (Transaction code CMOD) to create the user exit.

1. Create your project for this purpose.

2. Assign the RFFOX230 enhancement.

3. Push the “Component” button, and you can find that the function module EXIT_RFFOEXIT_230 is

assigned. Double click on “ZXFORU34” to generate and activate an include file. Even if the warning

message is shown, please don’t go back.

4. Implement your own logic to modify the transferred data.

5. Activate Include ZXFORU34, Function module EXIT_RFFOEXIT_230, and this project.



User Exit Foreign DME Japan Data Records 2 and 6

After the data records are filled, the customer exit is called.

Modified fields are defined in the structure DTAMJP.

The logic to modify the transferred values is

implemented in include ZXFORU34.

Modified Fields are increased. Please refer to SAP

Note.1248423, 1602174, and 1884202 as well.



(Ex)Edit Payment Order Data by using Structure DTAJPZ

Payment data created by F110 Payment Run

Implement your own

logic in the user Exit.

Payment Media Data (DME)

REGUH

REGUP

Execute RFFOJP_L

and go through this

logic.

Appendix.A

ZENGINKYO Record Layout


ZENGINKYO Record Layout – File structure and sequence

flow 1/2

File structure and sequence flow


ZENGINKYO Record Layout – File structure and sequence

flow 2/2

File structure and sequence flow


ZENGINKYO Record Layout – Contents of Record 1/6









CAUTION:

There is NO specific structure defined as a standard for “Special Message to Bank”, “Payment bank” or “Through bank”.

Although it depends on the scenario, you could use the structure DTAJPZ and implement the filling logic in exit_230(rffoexit).



Appendix.B

Payment Program (Process Flow)


Payment Program – Process Flow

F110 Payment Run

(SAPF110S)

RFFO* Print Program

(ＤＭＥ File Creation)

Edit Proposal

(SAPF110O)

Configurations

(T012*/T042* ...)

FI Documents

(BKPF/BSEG ...)

Master Data

(KNA1/LFA2 ... BNKA)

Available amounts

(T042D)

Parameters

(REGUV/RFDT)

Payment Data

(REGUH/REGUP)

Proposal Data

(REGUH/REGUP)

Payment List

(RFZALI00/RFZALI10)

Payment/Exception

List

(Spool)

Payment Medium

Form (Spool)

Payment Medium ＤＭＥ

(TemSe/Filesyst.

REGUT ...)

Payment Summary

(Spool, Job protocol)

Payment Order

(PYORDH, PYORDP)

Change History(REGUA

REGUHH/REGUPO)

Payment Advice Notes

(Spool)

F110 Set Parameters

(SAPF110V)

Appendix.C

Add-on Programs Provided by

SAP Japan Chargeable Consulting

Service


SAP Japan developed two add-on programs.

(1) Foreign Remittance (add-on)

(2) Import Foreign Exchange Transaction Statement (add-on)

(1) Difference between standard and add-on

Fill “Exchange Rate Category” automatically by the this add-on program. “Exchange Rate Category” is decided based on Local currency / Invoice currency / Payment currency / Account currency / Contract Number.

Up to 3 records of Accounting data can be printed on “Application for Foreign Remittance” . The standard program only generates a DME file with 3 records of Accounting data.

Generate the form “Application for Foreign Remittance” for a payment order which ZENGINYO does NOT define (Transfer FC equivalent amount by another FC, Transfer FC equivalent amount by YEN)

(2) Foreign Exchange Transaction Statement

Import Foreign Exchange Transaction Statement provided by a sending bank

Search AP items with Payment Order Number and do the clearing posting. Gain or Loss on Exchange rate differences is also automatically posted.

FI document to post Bank Charge (In case that it is paid immediately, only) is automatically generated.

Add-on Programs provided by SAP Japan


Print “Application for Foreign

Remittance for a payment

transfer order which ZENGINYO

does NOT define


© 2012 SAP AG. All rights reserved. 65 © SAP 2007 /

Page 65

Up to 3 accounting

data can be printed

In case that a payment is to

EU, IBAN can be editable.

SWIFT BIC Code is

editable.




(2) Import Foreign Exchange Transaction Statement

(add-on)



(add-on)



(add-on)

(1) Import an inbound file from a sending bank

(2) Check imported data records

Header Record: Transaction Information Type, Bank Code, Branch

Code

Data Record: Bank Account Number, etc

(3)Extract data on “Execution of Foreign Bank Transfer” only

(4)Convert the amount and the currency translation rate to SAP

Format’s one

(5) Data Mapping

(6) Message Handling (Reference Number by Business Partner

= Application for Remittance number, etc)

(7) Proceed data extracted and converted

FB05 - Clearing vendor open items and post gain or loss on

currency translation

FB01 - Bank Charge posting

(8) Import Result List - ALV

Bank Charge is posted,

when the bank charge record

is recognized, and

when it is paid immediately,

and

when it is JPY, and

When the clearing on payment

order is possible.

Account Determination of Bank

Charge

T030/T030R/T030B , BSP

Charges Account is defined in

House Bank Master.


© 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,

Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered

trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin

are trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®,

World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry

Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App

World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,

Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, SAP HANA, and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal

Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase

products and services mentioned herein as well as their respective logos are trademarks or

registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks

of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational purposes only. National

product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be

reproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.


© 2012 SAP AG. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu

welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche

Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen

können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können

Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken der

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,

Informix und Smarter Planet sind Marken oder eingetragene Marken der IBM Corporation.

Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Ländern.

Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene

Marken von Adobe Systems Incorporated in den USA und/oder anderen Ländern.

Oracle und Java sind eingetragene Marken von Oracle und/oder ihrer

Tochtergesellschaften.

UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin

sind Marken oder eingetragene Marken von Citrix Systems, Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®,

World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri und Xcode sind Marken oder eingetragene Marken der Apple Inc.

IOS ist eine eingetragene Marke von Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry

Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook und BlackBerry App

World sind Marken oder eingetragene Marken von Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,

Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik und Android sind

Marken oder eingetragene Marken von Google Inc.

INTERMEC ist eine eingetragene Marke der Intermec Technologies Corporation.

Wi-Fi ist eine eingetragene Marke der Wi-Fi Alliance.

Bluetooth ist eine eingetragene Marke von Bluetooth SIG Inc.

Motorola ist eine eingetragene Marke von Motorola Trademark Holdings, LLC.

Computop ist eine eingetragene Marke der Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, SAP HANA und weitere im Text erwähnte SAP-Produkte und -

Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken

der SAP AG in Deutschland und anderen Ländern.

Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports,

Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwähnte Business-

Objects-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken

oder eingetragene Marken der Business Objects Software Ltd. Business Objects ist ein

Unternehmen der SAP AG.

Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und weitere im Text

erwähnte Sybase-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind

Marken oder eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der

SAP AG.

Crossgate, m@gic EDDY, B2B 360°, B2B 360°Services sind eingetragene Marken der

Crossgate AG in Deutschland und anderen Ländern. Crossgate ist ein Unternehmen der

SAP AG.

Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen

Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informations-

zwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und

Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und

in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch

SAP AG gestattet.

EN_RFFOJP_L(1)

Documents

remittance data

foreign remittance rffom100

foreign remittancejapanese

data exchange format

data transfer

different record format

currency remittance

nonmember of zenginkyo