Orbian Buyer SAP Configuration Guide V2.1

Orbian Supply Chain Finance Solution
SAP Configuration Guide

for Buyers
Version 2.0
This document forms part of Orbian’s policies and procedures. All defined terms used in this document shall have the meanings given to them in
the Service Agreement, except where they are re-defined in this document or where their meanings must, necessarily, be varied by the context in
which they arise in this document. In the event of conflict between this document and the Service Agreement, the Service Agreement shall control.
Except as permitted by the Service Agreement, this document must not be disclosed outside of your organization and you are not authorized to
duplicate or distribute it (whether electronically or otherwise) in whole or in part.
Orbian Buyer SAP Configuration Guide V2.1.docx

© Orbian. Confidential and Proprietary. All rights reserved.Page 1 of 33
TABLE OF CONTENTS
Page
1 INTRODUCTION .............................................................................................................................................................. 3
1.1 CONFIGURING SAP FOR ORBIAN ---------------------------------------------------------------------------------------------- 3
1.2 SAP CONFIGURATION RELEASE SUPPORT -------------------------------------------------------------------------------- 3
1.3 THE STEPS FOR CONFIGURING SAP FOR ORBIAN ---------------------------------------------------------------------- 4
2 SAP CONFIGURATION STEPS ...................................................................................................................................... 5
2.1 CREATE ORBIAN AS A FINANCIAL INSTITUTION -------------------------------------------------------------------------- 5
2.2 CREATE ORBIAN AS A HOUSE BANK ----------------------------------------------------------------------------------------- 6
2.3 CREATE THE GENERAL LEDGER ACCOUNTS FOR THE ORBIAN PROCESS ------------------------------------ 7
2.4 CREATE HOUSE BANK ACCOUNTS FOR THE ORBIAN PROCESS -------------------------------------------------- 8
2.5 ACTIVATE PAYMENTS WITH ORBIAN ----------------------------------------------------------------------------------------- 9
2.6 DEFINE THE ORBIAN PAYMENT METHOD ---------------------------------------------------------------------------------- 10
2.7 DEFINE INSTRUCTION KEY ------------------------------------------------------------------------------------------------------ 15
2.8 APPLY INSTRUCTION KEY AS DEFAULT ------------------------------------------------------------------------------------ 16
2.9 CREATE ORBIAN PAYMENT FORMAT ---------------------------------------------------------------------------------------- 17
2.10 MAINTAIN AP VENDOR MASTER DATA -------------------------------------------------------------------------------------- 18
2.11 CREATE ACCOUNTS PAYABLE INVOICE ------------------------------------------------------------------------------------ 20
2.12 SETTINGS FOR CASH SETTLEMENT OF ORBIAN PAYMENT REQUESTS---------------------------------------- 22
2.13 DOWNLOAD ORBIAN PAYMENT FILE ----------------------------------------------------------------------------------------- 23
2.14 MODIFY ORBIAN PAYMENT FILE – INCREASE NUMBER OF REMITTANCE RECORDS---------------------- 25
2.15 MODIFY ORBIAN PAYMENT FILE – ENHANCE REMITTANCE INFORMATION ----------------------------------- 26
2.16 CUSTOMIZE PROCESSING OF THE ELECTRONIC BANK STATEMENT ------------------------------------------- 28
3 APPENDIX 1 - VENDOR INVOICE CLEARING ............................................................................................................ 32
3.1 VENDOR INVOICE CLEARING DATE ------------------------------------------------------------------------------------------ 32
3.2 VENDOR INVOICE AP DOCUMENT REPORTING-------------------------------------------------------------------------- 32
4 APPENDIX 2 – CLEARING OF GENERAL LEDGER ACCOUNT ENTRIES ................................................................ 33
4.1 AUTOMATIC CLEARING (F.13) -------------------------------------------------------------------------------------------------- 33

1 INTRODUCTION
1.1 Configuring SAP for Orbian
The objective of the SAP Configuration Guide is to assist you in the configuration and development of your SAP ERP
system to facilitate the generation of Orbian Payment Files, processing of Orbian MT940 statements and performing
reconciliations.
This guide provides an example of the configuration and ABAP development steps required to implement the Orbian
functionality, per company code. More complex SAP installations, for example a centralized payment company code,
may require additional configuration and development activity by the Buyer.
Please read the following Orbian documents, before reading this SAP Configuration Guide:
 “Buyer Implementation Overview”, in order to understand the fundamentals of the Orbian Supply Chain Finance
product.
 “SAP Buyer Accounting process example”, in order to see an example of a production accounting process for
Buyers who use SAP.
1.2 SAP Configuration Release Support
The Orbian Supply Chain Finance functionality is already included in SAP, for the following releases:
 Release 4.0B: as of Support Package 79

 Release 4.6C: as of Support Package 20
 Release 4.7: as of Support Package 01
 Standard delivery for all releases after 4.7
Please see SAP note 532339 for more information regarding these Support Packages.
SAP also offers support for the Orbian functionality.
This guide is based on Release 4.6C with at least Support Package 20 installed.

1.3 The Steps for Configuring SAP for Orbian
The following is a brief overview of the configuration steps to be undertaken by the Buyer for the Orbian Supply Chain
Finance Solution:
Steps Reason
1. Create Orbian as a Financial Institution. Orbian has to exist in your SAP system as a financial
institution to enable payments to be made.
2. Create Orbian as a House Bank. Your Orbian Business Partner number, included in the Orbian
Payment File, is stored on the house bank.
3. Create General Ledger Accounts for the In order that the automated General Ledger postings can take
Orbian process place as part of the Orbian process.
4. Create House Bank Accounts for the Defines the Buyer Orbian Account as a House Bank Account
Orbian process. and links to the “Vendor Account Payables – Orbian” GL
account used for reconciliation purposes.
5. Activate payments with Orbian. Activates Orbian as a permitted Payment Method classification
and specifies the maximum maturity period for a Payment
Instruction.
6. Define the Orbian Payment Method. This enables the F110 payment program to automatically
generate Orbian Payment Requests on the required Orbian
Buyer Account.
7. Define Instruction Key. Defines the payment type required by the Orbian system.
8. Apply Instruction Key as default. Sets the default Instruction Key (defined above) for data
medium exchange.
9. Create Orbian payment format. Create the Orbian DME payment format. This is a proprietary
payment format specific to Orbian, rather than the standard
MT100 format.
10. Maintain AP vendor master data. Maintain the AP vendor master record with the required Orbian
information; and the partner bank type, for each AP vendor to
be paid using Orbian.
11. Create Accounts Payable invoice. Specifies key invoice data required for Orbian Payment
Requests to be made.
12. Settings for cash settlement of Orbian Specifies the Bank Key and Bank Account from which cash
Payment Requests. settlements are made to Orbian, at the due date of the
Payment Request.
13. Download Orbian Payment File. Enables the Orbian Payment file to be electronically output
from the SAP system, once the payment run has completed.
14. Modify Orbian Payment File – increase Extends the number of remittance records per Orbian
number of remittance records. Payment Request.
15. Modify Orbian Payment File – enhance Enables an enhanced format of remittance information to be
remittance information, included in the Orbian Payment File.
16. Customize the processing of the Customize the Electronic Bank Statement functionality to
Electronic Bank Statement. process an Orbian MT940 Statement file.

2 SAP CONFIGURATION STEPS
2.1 Create Orbian as a Financial Institution
Steps Reason
2.1. Create Orbian as a financial institution.  Orbian has to exist in SAP as a financial
institution to enable payments to be made.
Procedure
 Call up transaction FIOR. Note: This transaction is not on the customizing IMG.
 Enter the following data.
Field Name Value Comments
Bank Country US
Bank Key ORBIAN Enter ORBIAN.
The bank key is managed at Orbian under this
description. If you enter a different description, the
Payment Request data cannot be transferred to the
Orbian system.
Bank Name ORBIAN
Region CT
Street Connecticut Avenue
City Norwalk
Bank Number ORBIAN
 Save your entries.
 To Display or Change the entry follow the application path below:
o Accounting
o Financial Accounting
o Banks
o Master Data
o Bank Master Record
o Display or Change in the initial screen

2.2 Create Orbian as a House Bank
Steps Reason
2.2. Create Orbian as a House Bank (without Instruction  Your Orbian Business Partner number, included
Key). in the Orbian Payment File, is stored on the
house bank.
Procedure
 In the Implementation Guide choose (IMG) follow the paths below:
o Financial Accounting 
o Bank Accounting
o Bank Accounts
o Define House Banks
 Execute the IMG activity.
 Enter the company code in which you pay with Orbian.
 Choose the view House banks followed by New entries.
Company Code ZZ01 Example.
House Bank ORB
Bank Country US
Bank Key ORBIAN The bank key is managed at Orbian under this
description.
If you enter a different description, the Payment

Request data cannot be transferred to the Orbian
system.
Click on the Data Medium Exchange icon.
Customer Number 0001234566 Enter your Orbian Business Partner Number,
including any leading zeros.
Note: Orbian will provide a different test and

production Business Partner number for
Integration Testing and Production set up.
Bank Number ORBIAN

2.3 Create the General Ledger Accounts for the Orbian Process
Steps Reason
2.3. Create the required General Ledger Accounts for the Orbian  In order that automated General Ledger postings
process. can take place as part of the Orbian process.
Procedure
 In order to create account postings, arising from the payment program clearing AP vendor invoices and the upload of
Orbian MT940 Statements, it is necessary to create the following General Ledger (GL) accounts in the relevant chart of
accounts / company code(s) for each of your Orbian Buyer Accounts (which are currency specific):
o Vendor Account Payables - Orbian.
o Orbian PI Control Account.
o Orbian Cash Clearing Account.
 Create these GL accounts in the normal manner with the following characteristics:
Account Account Group Open Item Management? Line Item Display?

Orbian PI Control Account. Bank Account Y Y
Vendor Account Payables - Orbian. Bank Account Y Y
Orbian Cash Clearing Account. Bank Account Y Y
 Repeat the above steps for each of your Orbian Buyer Accounts.

2.4 Create House Bank Accounts for the Orbian Process
Steps Reason
2.4. Create House Bank accounts for the Orbian process.  Defines the Buyer Orbian Account as a House
Bank Account and links to the “Vendor Account
Payables – Orbian” GL account used for
reconciliation purposes.
Procedure
 Notes:
o An additional House Bank Account is required for each additional Orbian Buyer Account.
o Orbian Buyer Accounts are Currency specific.
 In the Implementation Guide choose (IMG) follow the path below:

o Bank Accounting
o Bank Accounts
 Enter the company code in which you pay with Orbian.
 Select the Orbian House Bank you have already defined and choose the view:
o Bank accounts followed by
o New entries.
Company Code ZZ01 Example.
House Bank ORB Example.
Account ID ORBPI Example.
Description Account USD Example.
Click on Bank Accounts folder.
Bank Account 100000325 Example.
Number
Enter your Orbian Buyer Account number.
Note: Orbian will provide a different test and

production Orbian Buyer Account number, for
Integration Testing and Production set up.
Currency USD Example.
Enter the currency of your Orbian Buyer Account.
GL Account 114100 Example.
Enter the Vendor Account Payables - Orbian GL
account number that you have created to record
your Orbian Payment Instructions for this Orbian
Buyer Account.
 Repeat the above configuration, for each of your additional Orbian Buyer Accounts.

2.5 Activate Payments with Orbian
Steps Reason
2.5. Activate payments with Orbian.  Activates Orbian as a permitted Payment
Method classification and specifies the
maximum maturity period for a Payment
Instruction.
Procedure
o Bank Accounting
o Business Transactions
o Payment Transactions
o Activate Orbian Payments
Payment Method ORBIAN Activates the use of the Orbian Payment Method in
Class your SAP client.
Min Term 0 Only open AP invoices whose due date is on or
after the current date plus the minimum term will be
selected for payment by the F110 payment
program.
This must be set to zero days.

Max Term 180 Only open AP invoices whose due date is on or
before the current date plus the max term will be
selected for payment by the F110 payment
program.
180 days is used as an example. A maximum value

of 360 days is permitted.
Set the Max Term to the number of days required by

your organization.

2.6 Define the Orbian Payment Method
Steps Reason
2.6. Define the Orbian Payment Method.  This enables the F110 payment program to
automatically generate Orbian Payment
Requests on the required Orbian Buyer
Account(s).
General Note
It is assumed that the paying company code has previously been configured.
2.6.1 Procedure – Payment methods in the country
 In the Implementation Guide choose (IMG) follow the paths below:
o Accounts Receivable and Accounts Payable
o Business Transactions
o Outgoing Payments
o Automatic Outgoing Payments
o Payment Method/Bank Selection for Payment Program
o Set Up Payment Methods per Country for Payment Transactions
 Choose New Entries and enter the following data.
Country US Example.
Payment Method Q Example.
Description Orbian Payments Example.
Payment method for Select radio button
– Outgoing
payments
Payment method Select radio button
classification –
Orbian
Required master Select check box Enables the transfer of Orbian supplier member and
record specifications account details from the AP vendor master record to
– Bank details the payment dataset.
Posting details – ZP Payment postings.
Document type for
payment
Posting details – ZV Clearing postings.
Clearing document
type
Payment medium – Select radio button
Use classic payment
medium programs
(RFFO*)
Payment medium RFFOM100 This is a modified SWIFT MT100 format for Orbian
program Payment Requests.

 Click on the Currencies Allowed folder followed by New entries.
Currency USD Example,
Enter the currency of each of your Orbian Buyer
Accounts.
2.6.2 Procedure – Payment methods in company Code

 In the Implementation Guide choose (IMG) and follow the paths below:
o Outgoing Payments
o Setup Payment Methods per Company Code for Payment Transaction
Paying Company ZZ01 Example.
Code
Payment Method Q
Amount limits – Leave blank.
Minimum amount
Amount limits - 9,999,999,999.00 Example.
Maximum amount Enter the maximum payment amount permitted by
your organization.
Grouping of items – Select check box If this setting is not made, the F110 payment
Single payment for (optional) program will aggregate open AP invoices by due
marked item date and clear with a single document. This means
a single Payment Instruction in the Orbian system
will be made up of one or more vendor invoices,
with the same due date, in your AP sub-ledger. This
is the recommended setting.
If this setting is made, the F110 payment program

will clear open AP invoices individually, resulting in
a single Payment Instruction in the Orbian system,
per single AP invoice.
Grouping of items – Select check box This setting has to be made for the Orbian payment
Payment per due (mandatory) method otherwise the F110 payment program will
date report an error when entering the payment
parameters.

Foreign payments - Select check box This setting is required if your AP vendor account is
Foreign business (optional) domiciled in a country different to that of the SAP
partner allowed paying company code.
Foreign payments - Select check box This setting is required if your Orbian payments are
Foreign currency (optional) in foreign currency relative to the local currency of
allowed the SAP paying company code.
Foreign payments - Select check box This setting is required if the Orbian supplier
Customer / vendor (optional) account details stored on the AP vendor under
bank abroad Payment Transaction – Bank Details are not
allowed? domiciled in the same country as the SAP paying
company code.
2.6.3 Procedure – Bank Determination for Payment Transactions

o Outgoing Payments
o Set Up Bank Determination for Payment Transactions
Define Ranking Order.
 Choose the company code in which you pay Orbian with and choose Ranking Order.
Payment Method Q
Currency USD Enter the currency of your Orbian Buyer Account.
Ranking Order 1
House Bank ORB
 Repeat the above configuration, for each currency of your Orbian Buyer Accounts.
Define Bank Accounts.

 Choose the company code in which you pay Orbian with and choose Bank Accounts.
House Bank ORB
Payment Method Q

Example.
Currency USD
Example.
Account ID ORBPI Enter the Orbian house bank account ID for your
Orbian Buyer Account.
Bank Sub Account 114109 Example.
Enter the GL account number you have created for
the Orbian PI Control Account for payments made in
this currency.
Charge Indicator Leave blank.
Business Area Leave blank.
Define Available Amounts.
 Choose the company code in which you pay Orbian with and choose Available Amounts.
 Choose New Entries and enter the following data,
House Bank ORB
Enter the Orbian house bank account ID for your
Days 999
Currency USD Example.
Available for 999,999,999.00 Example.
outgoing payment Enter the maximum payment amount permitted by
your organization.
Scheduled incoming 0.00
Payment

Define Value Date.
 Choose the company code in which you pay Orbian with and choose Value Date.
Payment Method Q
House Bank ORB
Enter the Orbian house bank account ID for your
Amount limit 9,999,999.00 Example.
Enter the maximum payment amount permitted by
your organization.
Currency This will default to the currency of your company
code.
Days to value date 0 This must be set to zero in order for the due date of
the Orbian Payment Request to be set to the due
date of the invoice.
 Repeat the above configuration for each of your additional Orbian Buyer Accounts.

2.7 Define Instruction Key
Steps Reason
2.7 Define Instruction Key.  Defines the payment type required by the
Orbian system.
Procedure
 Financial Accounting
 Accounts Receivable and Accounts Payable
 Business Transactions
 Outgoing Payments
 Automatic Outgoing Payments
 Payment Media
 Data Medium Exchange
 Define Instruction Keys
 Enter the following Data.
Bank Country US
Payment Method Q
Instruction Key 1
Payment Medium IPTC This is the payment type required by the Orbian
Instructions system.
Additional
Information

2.8 Apply Instruction Key as Default
Steps Reason
2.8 Apply Instruction Key as default  Sets the default Instruction Key (defined above)
for data medium exchange.
Procedure
o Bank Accounting
o Bank Accounts
 For the Orbian house bank in your company code, click on the Data Medium Exchange icon and enter the
following data.
Running Mode 1 Enter Instruction Key 1 which you defined in the
Instruction Key previous step.
Do not specify an Instruction Key during the

payment program proposal processing (transaction
F110) as this will be used instead of the one entered
here.

2.9 Create Orbian payment format
Steps Reason
2.9. Crate Orbian payment format.  Create the Orbian DME payment format. This is
a proprietary payment format specific to Orbian,
rather than the standard MT100 format.
Procedure
 Please refer to the “Orbian Payment File Format Guide” for more explanation on the format of the Orbian
Payment File.
 Execute transaction OBF5. Note: This transaction is not on the customizing IMG.
Alternative format ORBIAN
Description Orbian Payments
Under Other Attributes
Module is necessary Select check box
for Header
for Record
for Trailer

2.10 Maintain AP Vendor Master Data
Steps Reason
2.10. Maintain AP vendor master data.  Maintain the AP vendor master record with the
required Orbian information; and the partner
bank type, for each AP vendor to be paid using
Orbian.
Procedure
 In the SAP Menu for Standard R/3 Application Transactions follow the paths below:
o Accounting
o Accounts Payable
o Master Records
o Create or Change
 On the Payment Transactions screen, in the General Data, enter the Orbian account details for each AP
vendor to be paid using Orbian.
Country US
Bank key ORBIAN
Bank account 1000000123 Example.
Enter the vendor’s 10 digit Orbian account number
to which the payment is to be made.
BnkT USD1 Example.
Partner bank type. For example:
 USD stands for the currency of the vendor’s
Orbian account number.
 1 stands for the vendor’s first Orbian account
number. A vendor may have several Orbian
accounts to accommodate several different
divisions for example.
Reference details 0000000123 Example.
Enter the vendor’s Orbian Business Partner
number including any leading zeros.
 Notes
o For each of an AP vendor’s additional Orbian account numbers, repeat the above master data
maintenance, each time using a unique partner bank type and the relevant Orbian details.
o Each Orbian account number is currency specific.
o The Partner Bank type field (BnkT) must be populated. If this field is left blank then the vendor invoice
to be paid using the F110 payment program will be logged in the payment proposal as an exception.
The payment proposal will note on the invoice ‘No valid Payment Method found’ even though the
Orbian Payment Method has been specified.
o In order for a vendor invoice to be selected for payment via Orbian the partner bank type must be
specified in both the vendor master data and the vendor invoice. If it is not specified in either one of
these then the invoice will not be selected for inclusion within the payment run.

On the Payment Transactions Accounting screen in the Company Code data, in the section headed
Automatic payment transactions, enter the following.
Payment Method Q Note: in order for the SAP payment program
(transaction F110) to select vendor invoices for
payment, the Payment Method must be specified in
the FI document. The Payment Method must either
be entered manually at the time of invoice creation
or set as a default via the payment terms assigned
to the vendor.
 Repeat the above master data maintenance for each AP vendor to be paid using Orbian.

2.11 Create Accounts Payable Invoice
Steps Reason
2.11. Create Accounts Payable invoice.  Specifies key invoice data required for Orbian
Payment Requests to be made.
2.11.1 Procedure – Enter Vendor Invoice – Mandatory Data
 The following information must be included in the Accounts Payable invoice raised, to pay your vendor via Orbian:
o Orbian Payment Method
Note that it is possible to set the Payment Method as a default during invoice creation via the payment terms
assigned to the vendor.
o Partner Bank Type
This should be the same value as specified in the vendor payment transactions master data screen.
 Note
o If either of these items of data is omitted from the vendor invoice then it will not be selected for payment by
the F110 payment program.
2.11.2 Procedure – Default Partner Bank Type In Vendor Invoice
 It is possible to automate the default of the Partner Bank Type in to the vendor invoice using the SAP Substitution in
Accounting Documents functionality. This section details how this can be implemented.
 Notes
o Please read SAP note 42615 prior to implementing this solution.
o The partner bank type is stored in table-field BSEG-BVTYP. This field is not released for substitution as part
of the standard SAP delivery. However, a customer modification can be made to your SAP system to make
this field available for substitution (specifically see Cause and Prerequisites point 5 and Solution point 1 of
this SAP note).
o As this is a customer modification you will need to consider whether this is an acceptable solution for your
organization. Please contact SAP directly should you have questions or concerns about implementing this
note.
o Once system changes under note 42615 have been implemented, you may find that non-Orbian invoices are
modified by this substitution. It is therefore advised that careful consideration be given to the prerequisites
defined in the substitution to ensure the partner bank type default only occurs for invoices to be settled via
Orbian.
 First make field BSEG-BVTYP available for substitution by maintaining table GB01. Refer to the Solution in SAP
note 42615. In this instance field BCLFIELD should refer to BVTYP.
 In the Implementation Guide (IMG) follow the paths below:

o Outgoing Invoices/Credit Memos
o Carry Out and Check Document Settings
 Substitution in Accounting Documents

 It should now be possible to create a substitution on table BSEG-BVTYP in the usual way. If this field has
successfully been made available for substitution as per note 42615 then it should be visible in the Substitutable
fields (Class 009) fields list. This list may be displayed from the menu:
o Extras > Substitution Fields

2.12 Settings for Cash Settlement of Orbian Payment Requests
Steps Reason
2.12. Settings for cash settlement of Orbian Payment  Specifies the Bank Key and Bank Account from which
Requests. cash settlements are made to Orbian, at the due date
of the Payment Request.
Procedure
 This section assumes you have carried out the required Customizing for the payment program (SAP transaction
F110).
 Under Accounting follow the paths below:
o Bank Accounting
o Bank Accounts
o Define Orbian Details
 Choose New Entries and make the following entries:
Company Code ZZ01
House Bank ORB
Orbian Reserve ORBPI Example.
Account Enter the Orbian house bank account ID for your Orbian
Buyer Account.
Orbian Active ORBPI Example.
Account Enter the Orbian house bank account ID for your Orbian
Buyer Account.
Note: The same house bank account ID should be

entered in both the Reserve and Active Orbian Account
fields.
Bank Details For Orbian
Bank Country US Enter the appropriate country.
Bank Key 645321 Example.
Populate with the Bank Key number relating to your bank
account that you will use to cash settle your Orbian
transactions at due date. For information only
Bank Account 12312312 Example.
Populate with the Bank Account number relating to your
bank account that you will use to cash settle your Orbian
transactions at due date. For information only
Account Holder USA Corp Example.
Populate with the name of the Account Holder to whom
the Bank Key/Bank Account belongs. For information only
Payment Method Q
 Repeat the above configuration for each of your additional Orbian accounts.

2.13 Download Orbian Payment File
Steps Reason
2.13. Download Orbian Payment File.  Enables the Orbian Payment file to be
electronically output from the SAP system,
once the payment run has completed.
General Note
 The Orbian Payment File is generated by program RFFOM100 (see Step 2.6.1).
 When the file is generated, it is stored internally within SAP.
 To download the file to your local PC/network, follow the steps below.
2.13.1 Procedure – Create Variant for Program RFFOM100

 Create and save a variant for program RFFOM100, using the following values.
Paying company
ZZ01
code
Payment methods Q
Payments in MT100
Select check box
format
Alternative format ORBIAN
File name Orbian_OPF Example.
Output medium 0 or 2 If set to 0, the data is output to TemSe; then
follow the steps in section 2.13.3 to download the
file.
Specify an output medium of 2 to immediately
save the file to the application server for further
processing.
Number of sample
2
printouts
No. of items in
9999
payment summary
Number of note to
4
payee lines
Collective payment
Select check box
order
2.13.2 Procedure – Assign Variant for Program RFFOM100 in Payment Proposal Parameters
 Once the variant for program RFFOM100 has been defined in Step 2.13.1 above, this should be specified in
the parameters for the payment run (transaction F110) on the Printout/data medium tab.

2.13.3 Procedure – Download Orbian Payment File
 Assuming the payment run has successfully executed, download the Orbian Payment File using the following
steps.
 From the main F110 transaction screen, follow the menu path:
o Environment
o Payment medium
o DME administration
 In the Data Medium Overview screen:
o Highlight the payment run that has been created.
o Click on the Download icon.
 A File Name dialogue box will now appear detailing the file name specified in the variant created for program
RFFOM100.
o Simply click on the Download (Enter) tick to store the file on your local PC/network.
o Note: SAP will automatically add a sequence number to the end of the filename.

2.14 Modify Orbian Payment File – Increase Number of Remittance Records
Steps Reason
2.14. Modify Orbian Payment File – increase number of  Extends the number of remittance records
remittance records. per Orbian Payment Request.
General Note
 Orbian does not limit the number of remittance records that can be attached to a single Orbian Payment
Request.
 In earlier releases of SAP, program RFFOM100 that is used to generate the Orbian Payment File restricts the
number of remittance records per Orbian Payment Request to a maximum of 154 records.
 If more than 154 remittance records are required to be attached to an Orbian Payment Request, apply SAP
note 946147 to increase this limit to 10,000 remittance records. If more than 10,000 remittance records are
required per Orbian Payment Request, then you may want to consider a customer modification based on this
SAP note.

2.15 Modify Orbian Payment File – Enhance Remittance Information
Steps Reason
2.15. Modify Orbian Payment File – enhance remittance  Enables an enhanced format of remittance
information, information to be included in the Orbian
Payment File.
General Note
 The Orbian Payment File generated by program RFFOM100 contains records in respect of both Orbian
Payment Requests and associated remittance information. The standard set up of program RFFOM100
generates standard remittance records immediately following each Orbian Payment Request; one remittance
record for each document (i.e. invoice/ credit memo) cleared by the payment program.
 The remittance information (for example Vendor invoice numbers and credit note numbers) is used by
Vendors to clear outstanding items on their Account Receivable ledger.
 The format of this standard remittance record, as seen in the file output, is shown below:
#R# Document number 123456 from 06/01/2004
o The document number 123456 is taken from the Reference Document Number field of the
Document header (table-field BKPF-XBLNR). The Reference Document Number field should be
populated with the Vendors’ transaction reference information; for example, Invoice number or Credit
memo number.
o The date, 06/01/2004, is taken from the invoice header Document (Invoice) Date field (table-field
BKPF-BLDAT). The Document (Invoice) Date field should be populated with the date from the
Vendors’ transaction reference information; for example, Invoice date or Credit memo date.
 It is possible to modify the remittance records from the standard format above, to give the Vendors more
remittance information, for example Document amount. Please see section 5.3 and 6 of the Orbian Payment
File Format Guide.for more background on enhanced remittance information
 Modification of the remittance information requires ABAP programming skills. To modify the remittance,
follow the procedures set out below.
2.15.1 Procedure – Enhance Remittance Information

 Program RFFOM100 contains a user exit EXIT_RFFOEXIT_900 that may be used to modify the remittance
information associated with each Payment Request.
 Create a new project using transaction CMOD.

o Assign Enhancement RFFOX900 to the project. Component EXIT_RFFOEXIT_900 will now be
included in the project.
o Ensure the Enhancement is activated.
 The function module for user exit EXIT_RFFOEXIT_900 contains the statement Include ZXFORU03. Create
this Include and add your own code in accordance with Step 2.15.2.
 Once you have created Include ZXFORU03, check that the Enhancement is marked as implemented within
your project.

2.15.2 Procedure – Include ZXFORU03 for EXIT_RFFOEXIT_900
 The following points may be of use when building your user exit to enhance remittance information.
1. For each record in table REGUH (i.e. Orbian Payment Request) created by the payment program
(transaction F110), user exit EXIT_RFFOEXIT_900 will be processed.
2. Remittance information is held in internal table T_DTAM100V. This internal table has the following structure:
 Tag – contains an identifier to determine the type of information held in the Value field.
 Value – contains either Payment Request or remittance information.
 Length – contains the string length of the Value field.
2.1 A Payment Request Record (which must NOT be modified) will have a:
 Tag of 00000001 for the first REGUH record processed, 00000002 for the second and so on; and
 Value commencing #T##
2.2 A Remittance Record will have a:

 Tag starting with 000000011 and incrementing by one for each additional line of remittance (i.e.
000000012, 000000013, etc.) for the first REGUH record processed, 000000021 for the second and
so on; and
 Value commencing #R##
 Note that there will be one remittance line generated for each invoice that was cleared by the payment
program and stored in table REGUP.
 The information following the #R## may be modified but must be no greater than 65 characters in
length. You may pull information from the structure I_REGUH or table T_REGUP passed to the user exit,
or use information contained within these to obtain information from the original invoices.
 Ensure that after modifying the remittance record, the Length field is updated as required. This should
be equal to the sum of the string lengths for #R## (i.e. 4) plus the remittance (i.e. up to 65), with a
maximum value of 69.
3. Ensure that in structure E_DTAM100 exported from EXIT_RFFOEXIT_900, field XCHAR_NREP is set to ‘X’.
If this is not set, then the formatting of the Payment Request and remittance records will be incorrect and
Orbian will not be able to process the file.

2.16 Customize Processing of the Electronic Bank Statement
Steps Reason
2.16. Customize processing of the Electronic Bank Statement.  Customize the Electronic Bank Statement
functionality to process an Orbian MT940
Statement file.
General Note
 It is assumed that readers are familiar with the standard electronic bank statement upload functionality
(transaction FF_5) and that this will be used to generate account postings.
 Please refer to the “Orbian MT940 file format guide” for explanation of the format of the Orbian MT940
statement.
 All steps in this section may be accessed from a common point in the Implementation Guide (IMG) defined by
the paths below:
o Bank Accounting
o Payment Transactions
o Electronic Bank Statement
o Make Global Settings for Electronic Bank Statement
 Enter a chart of accounts, for example INT.
 Choose Continue (Enter).
 Follow the steps below and enter the required customizing data.

2.16.1 Procedure – Create Account Symbols – Example
 The following GL accounts are relevant for Business Transactions which appear on an Orbian MT940
Statement:
o Vendor Account Payables - Orbian.
o Orbian PI control Account.
o Orbian Cash Clearing Account.
 Create one account symbol for each of these accounts.
 Click on the Create Account Symbols folder followed by New Entries. Enter the account symbol name and
text description. For example:
Account Text
VENDOR A/P ORB Vendor A/P – Orbian
ORB PI CONTROL Orbian PI Control
ORB CASH CLEAR Orbian Cash Clearing
2.16.2 Procedure – Assign Accounts to Account Symbols - Example
 Click on the Assign Accounts to Account Symbol folder followed by New Entries.
 Assign Accounts to the Account Symbols created in Step 2.15.1 as shown in the example below. The plus
sign (+) is used as a mask to signify no Account / Currency changes are to be performed.
Account Symbol Acct Modification Currency GL Account
VENDOR A/P ORB + USD Enter the GL account created for the
(Example) Vendor A/P – Orbian account for the
specified currency.
ORB PI CONTROL + USD Enter the GL account created for the
(Example) Orbian PI Control account for the specified
currency.
ORB CASH CLEAR + USD Enter the GL account created for the
(Example) Orbian Cash Clearing account for the
specified currency.
 Repeat the above configuration for each of your additional payment currencies.
2.16.3 Procedure – Create Keys for Posting Rules – Example
 Click on the Create Keys for Posting Rules folder followed by New Entries.
 Make the following entries (note the leading N is simply a pre-fix):
Posting rule Text
NXPC Issue of an Orbian Payment Instruction
NXCB Settlement of Payment Instruction
NXAD Adjustment
NRPC Reversal of Payment Instruction
NRCB Reversal of Settlement of Payment Instruction

2.16.4 Procedure – Define Posting Rules – Example
 Click on the Define Posting Rules folder followed by New Entries.
 For each Posting Rule Key created in Step 2.16.3, create the relevant posting rule.
 The Doc Type ZV (Posting Details Clearing Document Type) was created in Step 2.6.1 above.
Post Post Doc Post
Debit Credit
Rule Area Type Type
Posting Key 40 Posting Key 50
NXPC 1 ZV 1
Acct Symbol ORB PI CONTROL Acct Symbol VENDOR A/P ORB
NXCB 1 ZV 1
Acct Symbol VENDOR A/P ORB Acct Symbol ORB CASH CLEAR
NXAD 1 ZV 1
Acct Symbol VENDOR A/P ORB Acct Symbol ORB PI CONTROL
NRPC 1 ZV 1
Acct Symbol VENDOR A/P ORB Acct Symbol ORB PI CONTROL
NRCB 1 ZV 1
Acct Symbol ORB CASH CLEAR Acct Symbol VENDOR A/P ORB
2.16.5 Procedure – Create Transaction Type
 Click on the Create Transaction Type folder followed by New Entries.
 Create transaction type MT940 – Orbian MT940 Statements, as Orbian payment data is
transferred using this standard function.

2.16.6 Procedure – Assign External Transaction Types to Posting Rules
 Highlight the MT940 transaction type created in Step 2.16.5, open the Assign External Transaction Types
to Posting Rules and click on New Entries.
 Each Posting Rule defined in Step 2.16.3 / 2.16.4 must be assigned to an External Transaction Type.
 For each External Transaction Type specify an Interpretation Algorithm of 015 (Clearing transaction), as
this enables the subsequent clearing on the interim accounts (per assignment number and SAPF124).
External Transaction +/- Sign Post rule Interpretation Algorithm
NXPC - NXPC 015: Clearing transaction
NXCB + NXCB 015: Clearing transaction
NXAD + NXAD 015: Clearing transaction
NRPC + NRPC 015: Clearing transaction
NRCB - NRCB 015: Clearing transaction

2.16.7 Procedure – Assign Bank Accounts to Transaction Types
 Click on the Assign Bank Accounts to Transaction Types folder followed by New Entries.
 The MT940 transaction type defined in Step 2.16.5 is assigned to the Orbian Bank Key (defined in Step 2.1)
and the Orbian Account from which payments are made (defined in Step 2.4).
Bank key ORBIAN
Bank acct 1000000325 Example.
Populate with your Orbian Buyer Account.
Trans. type MT940
Repeat the above configuration for each of your additional Orbian Buyer Accounts.

3 APPENDIX 1 - VENDOR INVOICE CLEARING
3.1 Vendor Invoice Clearing Date
When a vendor AP invoice is to be paid via Orbian, the F110 payment program sets the invoice clearing date differently to
the standard SAP process.
 Vendor invoices paid using the Orbian Payment Method are cleared with a clearing date equal to the invoice
due date. For example, an invoice dated and paid 28 April and due 27 May will have a clearing date of 27 May.
Therefore the invoice is shown as cleared on the same date that the Payment Instruction in the Orbian system is
due to mature.
 Comparing this to a vendor invoice paid using a non-Orbian Payment Method the clearing date is equal to the
date on which the F110 payment program cleared the invoice. So an invoice dated and paid 28 April and due
27 May has a clearing date of 28 April.
3.2 Vendor Invoice AP Document Reporting
The vendor AP invoice may be displayed using the standard SAP vendor line item display report (transaction code
FBL1N). Once the invoice has been paid and cleared by the F110 payment program, then the invoice may be shown as
‘Open’ rather than ‘Cleared’ depending on how this report is run.
 Open items radio button selected.
The date selection is for items that are ‘Open at key date’. Using the example of an invoice paid via Orbian as
detailed above, if the report is run with a key date of, say, 29 April, the vendor invoice will be included in the report
and it will be shown as ‘Open’. This is due to the specified key date of 29 April being before the clearing date of
27 May.
If the report is re-run with a key date of 27 May, the vendor invoice paid using the Orbian Payment Method will no
longer be included in the report as it is cleared on this date.
 Cleared items radio button selected.
The date selection for this setting is either:
o ‘Clearing date’ – if the report is run with a clearing date of 29 April, the vendor invoice paid using the
Orbian Payment Method will not be selected for inclusion in the report. If the report is re-run with a
clearing date of 27 May then the vendor invoice is shown with a status of ‘Cleared’.
o ‘Open at key date’ – The report output is the same as for ‘Open items’ radio button as above.
 All items radio button selected.
The date selection for this setting is by posting date. The vendor invoice paid using the Orbian Payment Method
is shown as ‘Cleared’ regardless of the posting date specified.

4 APPENDIX 2 – CLEARING OF GENERAL LEDGER ACCOUNT
ENTRIES
The accounting entries made to the Orbian PI Control GL account and the Vendor Account Payables - Orbian GL account
can be cleared manually or automatically using the following standard SAP functionality:
 Manual clearing transaction code F-03

 Automatic clearing transaction code F.13
Please see the Orbian “Buyer SAP Accounting and Reconciliation process guide” for more details of the accounting
entries that are made to the Orbian PI Control GL account and the Vendor Account Payables - Orbian GL account.
4.1 Automatic clearing (F.13)
To identify related items for automatic clearing, it is recommended to use the Request ID contained in the Assignment
field of line items (table-field BSEG-ZUONR) posted to the GL account on which clearing is to be performed.
The Request ID is the SAP clearing document number generated when the F110 payment program is used to clear a
supplier AP vendor account. This Request ID will be included in:
 The Payment Instruction Request contained in the Orbian Payment File.

 The MT940 statements generated by the Orbian system for both an Orbian Payment Instruction transaction and also
settlement of a Payment Instruction transaction.
To ensure that the Request ID is contained in the assignment field of the line item posted by the F110 payment program
to the Orbian PI Control GL account, maintain the Sort Key field in the GL account master with a value that has been
configured to document number (field BELNR). This can be defined using the IMG step:
 Financial Accounting > General Ledger Accounting > GL Accounts > Line Items > Line Item Display > Determine
Standard Sorting for Line Items
The Request ID contained in the Orbian MT940 will automatically default into the assignment field of bank statement
posting line items if the Interpretation algorithm: 015: clearing transaction specified in section 2.16.6 above is configured.
If automatic clearing is to be used, the following IMG step enables the specification of up to five document fields on which
matching is to be performed:
 Financial Accounting > General Ledger Accounting > Business Transactions > Open Item Clearing > Prepare
Automatic Clearing


Orbian Buyer SAP Configuration Guide V2.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Orbian Buyer SAP Configuration Guide V2.1

Uploaded by

Copyright:

Available Formats

Orbian Supply Chain Finance Solution

SAP Configuration Guide

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

1.2 SAP Configuration Release Support

 Release 4.0B: as of Support Package 79

SAP also offers support for the Orbian functionality.

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

If you enter a different description, the Payment

Note: Orbian will provide a different test and

Orbian Buyer SAP Configuration Guide V2.1.docx

Account Account Group Open Item Management? Line Item Display?

Orbian Buyer SAP Configuration Guide V2.1.docx

 In the Implementation Guide choose (IMG) follow the path below:

Note: Orbian will provide a different test and

Orbian Buyer SAP Configuration Guide V2.1.docx

This must be set to zero days.

180 days is used as an example. A maximum value

Set the Max Term to the number of days required by

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

2.6.2 Procedure – Payment methods in company Code

If this setting is made, the F110 payment program

Orbian Buyer SAP Configuration Guide V2.1.docx

2.6.3 Procedure – Bank Determination for Payment Transactions

Define Bank Accounts.

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Do not specify an Instruction Key during the

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

 In the Implementation Guide (IMG) follow the paths below:

 Execute the IMG activity.

Orbian Buyer SAP Configuration Guide V2.1.docx

o Extras > Substitution Fields

Orbian Buyer SAP Configuration Guide V2.1.docx

Note: The same house bank account ID should be

Orbian Buyer SAP Configuration Guide V2.1.docx

2.13.1 Procedure – Create Variant for Program RFFOM100

Orbian Buyer SAP Configuration Guide V2.1.docx

 In the Data Medium Overview screen:

o Highlight the payment run that has been created.

o Click on the Download icon.

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

2.15.1 Procedure – Enhance Remittance Information

 Create a new project using transaction CMOD.

Orbian Buyer SAP Configuration Guide V2.1.docx

2.2 A Remittance Record will have a:

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

Orbian Buyer SAP Configuration Guide V2.1.docx

 Save your entries.

Orbian Buyer SAP Configuration Guide V2.1.docx

3.2 Vendor Invoice AP Document Reporting

 Open items radio button selected.