biller direct
TRANSCRIPT
SAP ECC 5.00
March 2006
English
W22: FSCM Biller Direct
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany
Building Block Configuration Guide
SAP Best Practices FSCM Biller Direct: Configuration Guide
Copyright
© Copyright 2006 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
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.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 in several other countries all over the world. 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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
© SAP AG Page 2 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Icons
Icon Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG Page 3 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
ContentsConfiguration Guide........................................................................................................................ 5
1 Purpose................................................................................................................................... 5
2 Preparation.............................................................................................................................. 5
2.1 Prerequisites..................................................................................................................5
3 Configuration........................................................................................................................... 5
3.1 Release Card Payment.................................................................................................5
3.1.1 Release Credit Cards................................................................................................5
3.2 Define Payment Methods..............................................................................................6
3.2.1 Set Up Payment Methods per Country......................................................................6
3.2.2 Set Up Payment Methods per Company Code..........................................................7
3.2.3 Set Up Bank Determination for Payment Transactions.............................................8
3.3 Assign Payment Methods for Paying Bills through the Web..........................................9
3.3.1 Edit Payment Methods..............................................................................................9
3.4 Assign Text ID.............................................................................................................10
3.4.1 Define Text IDs for Documents...............................................................................10
3.4.2 Assign Text IDs for Documents...............................................................................10
3.5 Define Partial Payment................................................................................................11
3.5.1 Define Partial Payment and Currency.....................................................................11
3.6 Define Settings in Customizing for Sales.....................................................................11
3.6.1 Maintain Output Types............................................................................................11
3.6.2 Maintain Output Determination Procedure..............................................................12
3.7 Define Settings for Payment Cards.............................................................................13
3.7.1 Maintain Card Categories........................................................................................13
3.7.2 Set Account Determination for Credit Cards............................................................14
3.7.3 Assign G/L Accounts to Payment Card Types.........................................................15
3.8 QISRSCENARIO Configuration...................................................................................16
3.8.1 QISRSCENARIO transaction - Remove SAP from Contact Person........................16
3.9 Master Data................................................................................................................. 18
3.9.1 Create Condition Records for Notifications..............................................................18
3.9.2 Update Customer C6120 with Bank Details............................................................20
3.9.3 Maintain E-Mail Address for Company Codes.........................................................20
3.10 Manual Steps...............................................................................................................21
3.10.1 XCM Configuration..................................................................................................21
3.10.2 Postprocessing Steps..............................................................................................25
3.10.3 Configuration of JCO RFC Server (optional)...........................................................29
© SAP AG Page 4 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
© SAP AG Page 5 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Configuration Guide
1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.
2 Preparation
2.1 PrerequisitesIf you want to use this building block, you must first install the following building blocks:
Building Block # Description
B32 Best Practices R/3 Installation
J02 Organizational Structure
N70 Financial Accounting
N71 Cost/Profit Center Accounting
J05 Materials Management
J04 Sales and Distribution
N74 Cost of Sales Accounting
3 Configuration
3.1 Release Card Payment
3.1.1 Release Credit Cards
UseThe purpose of this activity is to determine whether the Web users can release their bills for payment by payment card.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable SAP Financial Supply Chain Management SAP Biller Direct Release Credit Cards
© SAP AG Page 6 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
2. On the Change View “Additional Payment Method Classes”: Overview screen, choose New Entries.
3. Make the following entries:
Field name Description User action and values Note
PymtMethCI Additional Permitted Payment Meth.Classifications
2 Card Payment
4. Choose Save.
5. Choose Back.
3.2 Define Payment Methods
3.2.1 Set Up Payment Methods per Country
Use The purpose of this activity is to create separate payment methods for SAP Biller Direct, so that the Web user can make payment using either bank collect (automatic or direct debit) or credit card.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Payments Automatic Incoming Payments Payment Method/Bank Selection for Payment Program Set Up Payment Methods per Country for Payment Transactions
2. On the Change View “Payment Method/Country”: Overview screen, choose New Entries.
3. Make the following entries:
Field name User action and values
Country DE
Pmt method 0
Description Biller Direct Bank Collection
Payment method for Incoming payments
Payment method classification: Debit memo Selected
Bank details Selected
Document type for payment DZ
Clearing document type DZ
Use classic payment medium programs (RFFO*)
Selected
Payment medium program RFFOD__U
© SAP AG Page 7 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Field name User action and values
Key in code line 05
Name of print dataset LIST3S
4. Choose Back.
5. Choose New Entries.
6. Make the following entries:
Field name User action and values
Country DE
Pmt method 9
Description Biller Direct Kredit Karte
Payment method for Incoming payments
Payment method classification: Card Payment Selected
Document type for payment DZ
Clearing document type DZ
Use classic payment medium programs (RFFO*)
Selected
Payment medium program RFFOD__U
7. Choose Back.
8. Choose Save.
9. Choose Back.
3.2.2 Set Up Payment Methods per Company Code
Use The purpose of this activity is to assign the SAP Biller Direct payment methods to the Company Code.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Payments Automatic Incoming Payments Payment Method/Bank Selection for Payment Program Set Up Payment Methods per Company Code for Payment Transactions
2. On the Change View “Maintenance of Company Code Data for a Payment Method”: screen, choose New Entries.
3. Make the following entries:
Field name User action and values
Paying co. code BP01
© SAP AG Page 8 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Field name User action and values
Pmt method 0
Maximum amount 999999999.99
Bank selection control: No optimization Selected
4. Choose Back.
5. Choose New Entries.
6. Make the following entries:
Field name User action and values
Paying co. code BP01
Pmt method 9
Maximum amount 999999999.99
Bank selection control: No optimization Selected
7. Choose Back.
8. Choose Save.
9. Choose Back.
3.2.3 Set Up Bank Determination for Payment Transactions
Use The purpose of this activity is to define the bank determination and bank clearing accounts for the bank collection (automatic debit) payment method of SAP Biller Direct.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Payments Automatic Incoming Payments Payment Method/Bank Selection for Payment Program Set Up Bank Determination for Payment Transactions
2. On the Display View “Bank Selection”: Overview screen, select the BP01 (Paying company code) line, and choose Ranking Order.
3. Choose New Entries.
4. Make the following entries:
Field name User action and values
Pmt method 0
Currency EUR
Rank.order 1
House bank DB
© SAP AG Page 9 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
5. Choose Back.
6. Choose Save.
7. Choose Bank Accounts.
8. Choose New Entries.
9. Make the following entries:
Field name User action and values
House bank DB
Pmt method 0
Currency EUR
Account ID GIRO
Bank subaccount 282004
10. Choose Back.
11. Choose Save.
12. Choose Back.
13. Choose Back.
3.3 Assign Payment Methods for Paying Bills through the Web
3.3.1 Edit Payment Methods
Use The purpose of this activity is to specify which payment methods can be used in SAP Biller Direct.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable SAP Financial Supply Chain Management SAP Biller Direct Edit Payment Methods
2. On the Change View “Maintenance of EBPP Payment Methods”: Overview screen, choose New Entries.
3. Make the following entries:
Paying co. code Classification Pmt method
BP01 Credit Card 9
BP01 Collection 0
4. Choose Back.
5. Choose Save.
6. Choose Back.
© SAP AG Page 10 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
3.4 Assign Text ID
3.4.1 Define Text IDs for Documents
Use The purpose of this activity is to define the text ID used in SAP Biller Direct when a Web user creates inquiries, complaints and give reasons for any partial payments.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting - Accounts Receivable and Accounts Payable - Business Transactions - Incoming Invoices/Credit Memos - Carry Out and Check Document Settings - Define Text Ids for Documents
2. On the Maintain Text Determination Configuration: List screen, make the following entries:
Field name User action and values
ID 0005
Description Correspondence Biller Direct
Relevant text Selected
3. Choose Save.
4. Choose Back.
3.4.2 Assign Text IDs for Documents
Use The purpose of this activity is to assign the text ID to be used in SAP Biller Direct.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable SAP Financial Supply Chain Management SAP Biller Direct Assign Text ID
2. On the Change View “Text Ids for Biller Direct complaint texts”: Details screen, make the following entries:
Field name User action and values
Text ID 0005
3. Choose Save.
4. Choose Back.
© SAP AG Page 11 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
3.5 Define Partial Payment
3.5.1 Define Partial Payment and Currency
Use The purpose of this activity is to specify whether Web users can make partial payments, partial settlement of credits in SAP Biller Direct.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts Payable SAP Financial Supply Chain Management SAP Biller Direct Define Partial Payment and Currency
2. On the Change View “Biller Direct: Settings for Business Partner”: Overview screen, choose New Entries.
3. Make the following entries:
Field name User action and values
Company Code BP01
Part. Settle CR Selected
Currency EUR
Partial Payment Selected
Discount Selected
4. Choose Save.
5. Choose Back.
6. Choose Back.
3.6 Define Settings in Customizing for Sales
3.6.1 Maintain Output Types
Use The purpose of this activity is to output types used by the notification process.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Billing Documents Maintain Output Types
© SAP AG Page 12 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
2. On the Display View “Output Types”: Overview screen, choose Change.
3. Select the FIN0 (OutputType) line, and choose Processing routines.
4. On the Change View “Processing routines”: Overview screen, choose New Entries.
5. Make the following entries:
Field name User action and values
Transm. Medium 5 External send
Processing 1: Program EBPP_BILL_NOTIFY
Processing 1: FORM routine ENTRY
6. Choose Output Types.
7. Select the FIN1 (OutputType) line, and choose Processing routines.
8. On the Change View “Processing routines”: Overview screen, choose New Entries.
9. Make the following entries:
Field name User action and values
Transm. Medium 5 External send
Processing 1: Program EBPP_BILL_NOTIFY
Processing 1: FORM routine ENTRY
10. Choose Output Types.
11. Select the FIN2 (OutputType) line, and choose Processing routines.
12. On the Change View “Processing routines”: Overview screen, choose New Entries.
13. Make the following entries:
Field name User action and values
Transm. Medium 5 External send
Processing 1: Program EBPP_BILL_NOTIFY
Processing 1: FORM routine ENTRY
14. Choose Output Types.
15. Choose Save.
16. Choose Back.
3.6.2 Maintain Output Determination Procedure
UseThe purpose of this activity is to define the output determination for documents.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the
© SAP AG Page 13 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Condition Technique Maintain Output Determination for Billing Documents Maintain Output Determination Procedure
2. On the Change View “Procedures”: Overview screen, select V10000 (Procedure) line, and choose Control Data.
3. Choose New Entries.
4. Make the following entries:
Step Cntr CTyp Requirement
170 1 FIN0 406
180 1 FIN1 406
190 1 FIN2 406
5. Choose Save.
6. Choose Back.
7. Choose Back.
8. Choose Back.
3.7 Define Settings for Payment Cards
3.7.1 Maintain Card Categories
Use The purpose of this activity is to specify a range of numbers that are acceptable for each credit card.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Billing Payment Cards Maintain Card Categories Determine card categories
2. On the Change View “Payment Cards: Determine Categories”: Overview screen, choose New Entries.
3. Make the following entries:
Field name User action and values
Type AMEX
Seq. 1
Cat 01
4. Choose Limit Checkmark.
5. On the Limit screen, make the following entries:
Field name User action and values
Payment cards from 30000000000000000
© SAP AG Page 14 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Field name User action and values
To 39999999999999999
6. Choose Execute.
7. Make the following entries:
Field name User action and values
Type VISA
Seq. 1
Cat 01
8. Choose Limit Checkmark.
9. On the Limit screen, make the following entries:
Field name User action and values
Payment cards from 40000000000000000
To 49999999999999999
10. Choose Execute.
11. Make the following entries:
Field name User action and values
Type MC
Seq. 1
Cat 01
12. Choose Limit Checkmark.
13. On the Limit screen, make the following entries:
Field name User action and values
Payment cards from 50000000000000000
To 59999999999999999
14. Choose Execute.
15. Choose Save.
16. Choose Back.
3.7.2 Set Account Determination for Credit Cards
UseThe purpose of this activity is to define and link for each payment card type a receivables account.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting Accounts Receivable and Accounts
© SAP AG Page 15 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Payable SAP Financial Supply Chain Management SAP Biller Direct Set Account Determination for Credit Cards
2. On the Determine Work Area: Entry screen, enter BP01 as Paying Company Code, and choose Enter.
3. Choose New Entries.
4. Make the following entries:
Payment card type
Card Category
Payment Method
Currency Receivables account
AMEX 01 9 EUR 246100
MC 01 9 EUR 246100
VISA 01 9 EUR 246100
5. Choose Save.
6. Choose Back.
7. Choose Back.
3.7.3 Assign G/L Accounts to Payment Card Types
UseThe purpose of this activity is to define and link for each payment card type a receivables account.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Billing Payment Cards Authorization and Settlement Maintain Clearing House Account Determination Assign G/L Accounts
2. On the Assign G/L Accounts screen, select 6 SlsOrg/Card cat. line.
3. On the Change View “SlsOrg/Card cat.”: Overview screen, choose New Entries.
4. Make the following entries:
Application Condition Type
Chart of Accounts
Sales Organization
Card Type
G/L Account no.
VD A001 IKR BP01 AMEX 246100
VD A001 IKR BP01 MC 246100
VD A001 IKR BP01 VISA 246100
5. Choose Save.
6. Choose Back.
7. Choose Back.
© SAP AG Page 16 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
3.8 QISRSCENARIO Configuration
3.8.1 QISRSCENARIO transaction - Remove SAP from Contact Person
1. Access the activity as follows:
Transaction Code SM30 using Customizing Object VSCENARIO orQISRSCENARIO
IMG menu path Cross-Application Components Internet/Intranet Services Internal Service Request Definition of Scenarios with Specific Customizing Request for Adjustment Posting Define Scenarios for Request for Adjustment Posting
2. Enter the following data:
Scenario S2AD SCUS
DescriptionChange Address Data Create User
Active X X
Notification type70 71
Internet service
Entry type in web
F F
Automatic Costing
Costing variant
Qty struct. Template
Long text exists
Cost Incurring Scen.
Estimated costs0 0
Currency
Controlling Area
© SAP AG Page 17 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Contact Person
Partner role contact
§A §A
Costing ModelISR_S2AD ISR_SCUS
Strat.for acct assig.obj.
Obj.no.real acct asg
Aux.acct assgnmnt_1
Reference scenario
ISR Price List
Internet link
Form
Valid From00.00.0000 00.00.0000
Valid From00.00.0000 00.00.0000
Interface
BSP Application
3. Select Save (Ctrl+S)
4. Select Back (F3)
3.9 Master Data
3.9.1 Create Condition Records for Notifications
UseThe purpose of this activity is to create condition records used in the billing document for sending notification messages.
Procedure
© SAP AG Page 18 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction Code VV31
SAP Menu Logistics Sales and Distribution Master Data Output Billing Document Create
2. On the Create Output – Condition Records: Billing screen, make the following entries:
Output Type
FIN0
3. Choose Key combination.
4. On the Key Combination screen, select Billing Type and choose Enter.
5. On the Create Condition Records (Send Link Immediat.): Fast Entry screen, make the following entries:
Bill. Type Partner Function Medium Date/Time
BV (Cash Sales) BP 5 4
F2 (Invoice) BP 5 4
G2 (Credit Memo) BP 5 4
L2 (Debit Memo) BP 5 4
RE (Credit for Returns) BP 5 4
6. Choose Enter.
7. Select all the entries.
8. Choose Communication.
9. For each entry, make the following entries:
Comm. Strategy Output Device Print immediately
Release after output
<…> LOCL Selected Selected
10. Choose Save.
11. On the Create Output – Condition Records: Billing screen, make the following entries:
Output Type
FIN1
12. Choose Key combination.
13. On the Key Combination screen, select Billing Type and choose Enter.
14. On the Create Condition Records (Send Link per Job): Fast Entry screen, make the following entries:
Bill. Type Partner Function Medium Date/Time
BV (Cash Sales) BP 5 1
F2 (Invoice) BP 5 1
G2 (Credit Memo) BP 5 1
L2 (Debit Memo) BP 5 1
© SAP AG Page 19 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Bill. Type Partner Function Medium Date/Time
RE (Credit for Returns) BP 5 1
15. Choose Enter.
16. Select all the entries.
17. Choose Communication.
18. For each entry, make the following entries:
Comm. Strategy Output Device Print immediately
Release after output
<…> LOCL Selected Selected
19. Choose Save.
20. On the Create Output – Condition Records: Billing screen, make the following entries:
Output Type
FIN2
21. Choose Key combination.
22. On the Key Combination screen, select Billing Type and choose Enter.
23. On the Create Condition Records (Send Link per Job): Fast Entry screen, make the following entries:
Bill. Type Partner Function Medium Date/Time
BV (Cash Sales) BP 5 1
F2 (Invoice) BP 5 1
G2 (Credit Memo) BP 5 1
L2 (Debit Memo) BP 5 1
RE (Credit for Returns) BP 5 1
24. Choose Enter.
25. Select all the entries.
26. Choose Communication.
27. For each entry, make the following entries:
Comm. Strategy Output Device Print immediately
Release after output
<…> LOCL Selected Selected
28. Choose Save.
29. Choose Back.
3.9.2 Update Customer C6120 with Bank Details1. Access the transaction by using transaction code FD02
2. In the Customer Change: Initial Screen enter the following:
Customer: C6120
Company code: BP01
© SAP AG Page 20 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Choose Enter
3. Choose the Payment transactions tab and enter the following bank details:
Ctry: US
Bank key: 011000390
Bank Account: 2154369830
BnkT: E000
4. Choose the Payment cards button and enter the following:
Type: MC
Card number: 5424000000000007
Valid to: 12/2008
Cardholder: RIWA Chicago
Cat: 01
Valid from: 03/2005
5. Save your entries.
3.9.3 Maintain E-Mail Address for Company Codes1. In this step you enter a valid email address for the company code.
2. Access the transaction using transaction code SM30.
3. In the Maintain Table Views: Initial Screen enter V_T001 in the Table/View field. Choose Maintain.
4. Double-click on company code BP01.
5. Choose the Address icon (or select Goto – Adress or contextmenu – Adress).
6. Enter a valid email address in the E-Mail field.
7. Choose Other communication.
8. Select INT (Communication Method), and choose Enter
9. Make sure that the Checkbox for field Standard Number is selected.
10. Save your entries.
3.10 Manual Steps
3.10.1 XCM ConfigurationYou configure SAP Biller Direct with Extended Configuration Management (XCM). This is a tool with a user interface that you use centrally to manage different scenarios and make the settings needed to configure SAP Biller Direct.
PrerequisitesYou have done the following:
Deployed SAP Biller Direct (instructions provided in the Wholesale Quick Guide)
© SAP AG Page 21 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
Created a user to the bdadmin role in the SAP J2EE Engine (instructions provided in the Wholesale Quick Guide)
Specified which accounting system you want to run with SAP Biller Direct – Accounts Receivable Accounting (FI-AR) and have made the system settings described in this document.
Created user BD_REF in the SAP R/3 system. To create the users:
o Use transaction SU01.
o On the User Maintenance: Initial Screen, in User, enter your user name (for example, BD_REF) and choose the Create button.
o In the Address tab, enter the Last name BD_REF.
o In the Logon data tab, enter password (for example, init). Remember your password for your BP_REF user as you need to enter the password later in the procedure.
o In the Logon data tab, select User Type Reference.
o In the Profiles tab, under Profiles, enter SAP_ALL and SAP_NEW.
Created user BD_POOL in the SAP R/3 system. To create the users:
o Use transaction SU01.
o On the User Maintenance: Initial Screen, in User, enter your user name (for example, BD_POOL) and choose the Create button.
o In the Address tab, enter the Last name BD_POOL.
o In the Logon data tab, enter password (for example, init). Remember your password for your BP_POOL user as you need to enter the password later in the procedure.
o In the Logon data tab, select User Type Communications.
o In the Profiles tab, under Profiles, enter SAP_ALL and SAP_NEW.
ProcedureTo define a scenario, perform the following steps:
1. Call up XCM in your web browser with the path:
[protocol]://[server]:[port]/[billerdirect-context-root]/admin/xcm/init.do
protocol will usually be httpserver Hostname of the application server.
This is the first part of the underscore-separated server name.This argument is not case-sensitive.
port Port on which the J2EE server is installedcontext-root the root node, under which the Biller Direct service has been installed
for example, http://server:1080/bd/admin/xcm/init.do Contact your system administrator or the person who installed Biller Direct for the URL.
2. Under Application Configuration in the navigation structure on the left side of the screen of XCM, expand SAP. Here you can find the preconfigured scenarios prepared by SAP that you can use as a template.
© SAP AG Page 22 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
3. Choose FI_UserManagement to select it as a template.
4. Enter WSD_FI_UserManagement as the Name of the scenario.
5. Choose Create.
6. Check the mark in checkbox Default configuration.
7. Choose Save Configuration. Confirm the dialog box requesting the restart of the Web application.
8. Choose ApplicationSettings.
9. Enter WSD_FI_ApplicationSettings for Configuration ID.
10. Make sure Accounts Receivable (FI-AR) is selected for Base Configuration.
11. Enter/select value as follows:
Field name Value Note
arrangedStatus Yes
BankCountries DE,GB,FR,US
creditsInitialMarked Yes
custExtendedParameters
customizingCountries DE,EN,FR,IT
daysToSelectFutureBills 60
defaultBORObject BUS3007 Move to next page
defaultReferenceUser RFC_ROADRUNN
defaultXmlFormat IDOCXML
defaultXmlSigned No
disputeReasons No
ebppMode ON
forceComment Yes
isAuditorMail No Move to next page
isrForAddressActive Yes
isrForBankChangeActive No
isrForBankCreateActive No
isrForBankDeleteActive No
isrForCreditCardChangeActive No
isrForCreditCardCreateActive No
isrForCreditCardDeleteActive No Move to next page
partialPayment Yes
readAdditionalData Yes
selectCredits C
selfPayActive Yes
© SAP AG Page 23 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
useCreditCardVerificationNo. yes
12. Choose Save configuration. Confirm the dialog box.
13. Choose <<back to configuration.
14. Choose ConnectionManager.
15. Enter WSD_FI_ConnectionManager for Configuration Name.
16. Choose Create.
17. Select appropriate value from Base Configuration, default is group_connect.
18. Enter appropriate values for the parameters. For example:
Field name Value
ClientEnter the number of your client
Getsso2 0
Group PUBLIC
Lang EN
Max_connections 10
Max_wait_time 10000
Msmost
Enter the name of your message serverThis is the string in field message server of your server’s properties in SAP logon.This argument is not case-sensitive
PasswdEnter the password for the user defined below.
Pool-name Bd_pool_name
R3name
Enter the name of the application server. This is a 3 letter word. This is the second part of the underscore-separated server name. This argument is not case-sensitive.
Use_named_connections No
User BD_POOL
19. Choose Save Configuration. Confirm the dialog box.
20. Choose Run test. You will see a green screen if all the parameters you entered are corrected. If not, make sure you select the appropriate value for Base Configuration and correct all the connection values.
21. Choose << back to configuration.
22. Choose UserInterface.
23. Enter WSD_FI_UserInterface for Configuration ID.
24. Choose Create.
25. Select Private Customer View (B2C) for Base Configuration.
© SAP AG Page 24 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
26. Select values as follows:
Field name Value
AGENT_PAYMENTS yes
APPROVE_BILLS yes
BALANCES no
BALANCE_CONF no
CREATE_ADVICE no
CREDITS yes
CUST_SEARCH yes Move to next page
DISPUTE_OVERVIEW yes
OPEN_BILLS start
OPEN_ITEMS no
PAID_BILLS Yes
PAYER_DIRECT No
PAYMENTS Yes
SHOW_ADVICE No Move to next page
TRANSACTIONS Yes
USER_DATA Yes
27. Choose Save Configuration. Confirm the dialog box.
28. Choose <<back to configuration.
29. Select WSD_FI_ApplicationSettings for ApplicationSettings.
30. Select WSD_FI_ConnectionManager for ConnectionManager.
31. Select WSD_FI_UserInterface for UserInterface.
32. Choose Save configuration. Confirm the dialog box requesting the restart of the Web application.
33. Close your browser.
34. Restart SAP J2EE Engine for your XCM settings to be effective.
3.10.2 Postprocessing Steps
3.10.2.1 Assign Profile to SAPJSF SU01 User
UseThe purpose of this activity is to grant additional profiles to SAPJSF SU01 User, so that requests for Biller Direct registration can be processed.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SU01
© SAP AG Page 25 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
SAP Menu Tools Administration User Maintenance Users
2. On the User Maintenance: Initial Screen, enter the following information and choose Change.
Field name Description User action and values Note
User User Name SAPJSF
3. Choose Profiles.
4. On the Maintain User screen, enter the following information:
Field name Description User action and values Note
Profile Profile Name SAP_ALL
5. Choose Roles.
6. On the Maintain User screen, enter the following information:
Field name
Description User action and values Note
Role Role Name SAP_BC_JSF_COMMUNICATION SAP_BC_JSF_COMMUNICATION_RO might be the default here, but this role doesn’t allow to register new users. Remove user SAP_BC_JSF_COMMUNICATION_RO in this case, so that just user SAP_BC_JSF_COMMUNICATION is listed here.
7. Choose Save.
3.10.2.2 Create ZAPAR_EBPP_NOTIFY2 BADI Implementation
Use The purpose of this activity is to create an implementation for APAR_EBPP_NOTIFY2 BADI that will create the content of the notification email message.
Procedure1. Access the activity using one of the following navigation options:
Transaction Code SE18
2. On the Business Add-Ins: Initial Definition Maintenance screen, make the following entries:
Field name User action and values
Definition Name APAR_EBPP_NOTIFY2
3. Choose Display.
4. On the Business Add-Ins: Display Definition APAR_EBPP_NOTIFY2 screen, choose Implementation -> Create.
5. On the Business Add-In Builder: Create Implementation screen, make the following entries and choose Continue:
Field name User action and values
Implementation Name ZAPAR_EBPP_NOTIFY2
© SAP AG Page 26 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
6. On the Business Add-In Builder: Change Implementation ZAPAR_EBPP_NOTIFY2 screen, make the following entries and choose Interface:
Field name User action and values
Implementation Short Text Send Notification eMail Message
7. Double-click on CREATE_TEXT method and enter the code listed below.
8. Choose Yes on the Save screen.
9. Enter the Package (using a local object in $TMP is also possible here) and choose Save.
10. If necessary, create a transport.
11. Copy the following text between the lines starting with ‘method’ and ‘endmethod‘.
Before or after copying the code into the editor of transaction SE18 edit the line starting with ‘l_link’ so that it contains the correct URL for the Biller Direct server by replacing the following values:
http://<server>:<port>/bd/public/frameset_top_html.jsp
<server>Hostname of the application server. This is the first part of the underscore-separated server name. This argument is not case-sensitive.
<port> Port on which the J2EE server is installed
data: lt_outtab type table of solisti1, lf_outtab type solisti1,
l_belnr type bkpf-belnr, "Document number l_bschl type bseg-bschl, "Posting key l_shkzg type bseg-shkzg, "Debit/credit indicator l_umskz type bseg-umskz, "Special G/L Indicator l_ltext type tbslt-ltext, "Name of the posting key l_crdb(32) type c, "Credit / debit text l_line(127) type c, "Generic text line l_link type urlpart, "Biller Direct URL l_kunnr like i_kna1-kunnr, "Customer number l_name1 like i_kna1-name1, "Customer name l_stras like i_kna1-stras, "Address l_ort01 like i_kna1-ort01, "City l_regio like i_kna1-regio, "State l_pstlz like i_kna1-pstlz, "Zip l_fkdat(10) type c, l_netwr(32) type c.
define add_line. lf_outtab = &1. append lf_outtab to lt_outtab. end-of-definition.
* Get the URL for the Biller Direct page l_link = 'http://<server>:<port>/bd/public/frameset_top_html.jsp'.
* Remove leading zeros from the customer number field
call function 'CONVERSION_EXIT_ALPHA_OUTPUT' exporting input = i_kna1-kunnr
© SAP AG Page 27 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
importing output = l_kunnr.
* Convert address to upper case letters
move i_kna1-name1 to l_name1. move i_kna1-stras to l_stras. move i_kna1-ort01 to l_ort01. move i_kna1-regio to l_regio. move i_kna1-pstlz to l_pstlz.
translate l_name1 to upper case. translate l_stras to upper case. translate l_ort01 to upper case. translate l_regio to upper case. translate l_pstlz to upper case.
* Format the date field
write i_vbdkr-fkdat to l_fkdat.
* Format the amount field
write: i_vbdkr-netwr to l_netwr left-justified. shift l_netwr right by 1 places. l_netwr+0(1) = '$'.
if i_sms is initial.
************************** create HTML-mail ****************************
add_line: '<html>'. add_line: '<body link=blue vlink=purple', 'style=''font-size:16; font-family:"Arial"''>'.
add_line: '<p>', 'Customer Number:', '<b>', l_kunnr, '</b></p>'. add_line: '<p>', l_name1, '<br>'. add_line: l_stras, '<br>'. add_line: l_ort01, ',', l_regio, l_pstlz, '</p>'. add_line: '<p>', l_line, '</p>'.
add_line: '<table border>'.
add_line: '<tr>'. add_line: '<td><b>', 'Document Number:', '</b></td>'. add_line: '<td>', i_vbdkr-vbeln, '</td>'. add_line: '</tr>'.
add_line: '<tr>'. add_line: '<td><b>', 'Document Date:', '</b></td>'. add_line: '<td>', l_fkdat, '</td>'. add_line: '</tr>'.
add_line: '<tr>'. add_line: '<td><b>', 'Purchase Order No.', '</b></td>'. add_line: '<td>', i_vbdkr-bstnk, '</td>'. add_line: '</tr>'.
add_line: '<tr>'. add_line: '<td><b>', 'Amount:', '</b></td>'. add_line: '<td>', l_netwr, '</td>'.
© SAP AG Page 28 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
add_line: '</tr>'.
add_line: '</table>'.
add_line: '<p>', 'To view details/payment, click:', '<a href="', l_link, '">', l_link, '</a></p>'. add_line: '<p>', 'King regards,', '</p>'. add_line: '<p>', 'SAP Best Practices', '<br>', 'FSCM', '</p>'.
add_line: '</body>'. add_line: '</html>'.
e_doc_type = 'HTM'. else.
***************************** create SMS-text **************************
add_line: 'New Bill Received. Best regards, for Company xyz'. e_doc_type = 'RAW'. endif.
e_text = lt_outtab.
e_doc-obj_name = 'Bill'. e_doc-obj_descr = 'New Bill'. return = 0.
12. Choose Save.
13. Choose Activate.
14. On the Inactivate Objects for … screen, select all the Objects and choose Enter.
15. Choose Back.
16. Choose Activate.
17. Choose Back.
3.10.2.3 Assign Number Range to Notification Type
Use The purpose of this activity is to assign a number range object to the notification type.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Cross-Application Components Notification Notification Creation Notification Type Define Number Ranges
© SAP AG Page 29 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
2. On the Number range - message screen, choose Maintain Groups.
3. On the Maintain Number Range Groups screen, click on the value 70 at the bottom of the screen.
4. Choose Select Element (F2) and afterwards from the menu Interval – Display Intervals or from the context menu – Display Intervals.
5. Select/check the box for Internal Service Request.
6. Choose Element/Group (F5).
7. Choose Save and confirm the following dialog box.
3.10.3 Configuration of JCO RFC Server (optional)
Use
You only need to configure the JCO RFC server if you are using passive enrollment to register end users of SAP Biller Direct – that is, if customers fill out an application online to request a user for SAP Biller Direct.
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SM59
2. On the Display and Maintain RFC Destinations screen, choose Create.
3. Make the following entries:
Field name User action and values
RFC Destination JCO_LDAP_RFC_DEST
Connection Type T (TCP/IP Connection)
Description 1 Biller Direct
Registered Server Program Selected
Program ID BillerDirect050405
Gateway host <…>
Gateway service sapgw<..>
4. Choose Selection Options.
5. Make the following entries:
Field name User action and values
Unicode Selected
Default Setting Selected
© SAP AG Page 30 of 31
SAP Best Practices FSCM Biller Direct: Configuration Guide
6. Choose Save.
7. Choose Back.
3.10.4 Configuration of the Logon Dialog for Biller Direct User Creation (optional)
Use
You only need to perform this activity if the logon dialog to create an user for the Biller Direct Scenario does not contain the field ‘Business Partner’, but displays two fields for password entry. Please check the Business Process Procedure for Scenario W22 to find the procedure for user creation with the Biller Direct Web Frontend.
Procedure1. Open the following file with a text editor, e.g. Notepad:
/usr/sap/<system name>/DVEBMGS<system number>/j2ee/cluster/server0/apps/sap.com/com.sap.security.core.admin/servlet_jsp/logon/root/umLogonPage.jsp
The path listed above uses the Unix convention for the file and directory path names on the application server. On a WINDOWS® application server you have to use an appropriate file path.
In order to run this procedure you have to have write access to the given directory on the SAP application server.
2. Search for the string /useradmin/selfReg (1 occurrence) and replace this string with /bd/createuser_form.sap.
3. Save the file.
It is not necessary to restart the SAP application server in order to make this change effective.
© SAP AG Page 31 of 31