W22_ConfigGuide_FSCM_Biller_Direct.doc

SAP ECC 5.00

July 2005

English

W22: FSCM Biller Direct

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Building Block Title: Configuration Guide

Copyright

© Copyright 2005 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 34


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.



ContentsConfiguration Guide........................................................................................................................ 6

1 Purpose................................................................................................................................... 6

2 Preparation.............................................................................................................................. 6

2.1 Prerequisites..................................................................................................................6

3 Configuration........................................................................................................................... 6

3.1 Release Card Payment.................................................................................................6

3.1.1 Release Credit Cards................................................................................................6

3.2 Define Payment Methods..............................................................................................7

3.2.1 Set Up Payment Methods per Country......................................................................7

3.2.2 Set Up Payment Methods per Company Code..........................................................8

3.2.3 Set Up Bank Determination for Payment Transactions.............................................9

3.3 Assign Payment Methods for Paying Bills through the Web........................................10

3.3.1 Edit Payment Methods............................................................................................10

3.4 Assign Text ID.............................................................................................................11

3.4.1 Define Text Ids for Documents................................................................................11

3.4.2 Assign Text ID.........................................................................................................12

3.5 Define Partial Payment................................................................................................12

3.5.1 Define Partial Payment and Currency.....................................................................12

3.6 Define Settings in Customizing for Sales.....................................................................13

3.6.1 Maintain Output Types............................................................................................13

3.6.2 Maintain Output Determination................................................................................14

3.6.3 Defining E-Mail Address..........................................................................................15

3.7 Define Settings for Payment Cards.............................................................................15

3.7.1 Determine Card Categories.....................................................................................15

3.7.2 Assign G/L Accounts...............................................................................................17

3.7.3 Set Account Determination for Credit Cards............................................................17

3.8 Assign Number Range................................................................................................18

3.8.1 Define Number Ranges...........................................................................................18

3.9 Define Settings in the Application................................................................................19

3.9.1 Create Condition Records.......................................................................................19

3.9.2 Update Customer C6120 with Bank Details............................................................21

3.9.3 Update Company Code Address Information..........................................................21

3.10 Configuration of JCO RFC Server...............................................................................22

3.10.1 Create RFC Destination..........................................................................................22

3.11 XCM Configuration......................................................................................................22



3.11.1 Prerequisites...........................................................................................................22

3.11.2 Configuring a Scenario............................................................................................23

3.12 Modify SAPJSF User...................................................................................................29

3.12.1 Assign Profile to SAPJSF SU01 User.....................................................................29

3.13 Create BADI Implementation.......................................................................................29

3.13.1 Create ZAPAR_EBPP_NOTIFY2 BADI Implementation.........................................29

3.14 Assign Number Range................................................................................................32

3.14.1 Assign Number Range to Notification Type.............................................................32

3.14.2 Configuration of JCO RFC Server (optional)...........................................................33

3.14.3 Configuration of the Logon Dialog for Biller Direct User Creation (optional)............33



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

J03 Financial Accounting

J08 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

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.



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.


Field name User action and values

Country US

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

Key in code line 05

Name of print dataset LIST3S

4. Choose Back.

5. Choose New Entries.



Country US

Pmt method 9

Description Biller Direct Credit Card


Payment method classification: Card Payment Selected




Selected


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.



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.



Paying co. code BP01

Pmt method 0

Maximum amount 999999999.99

Bank selection control: No optimization Selected

4. Choose Back.




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.



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.






Pmt method 0

Currency USD

Rank.order 1

House bank BANKB

5. Choose Back.

6. Choose Save.

7. Choose Bank Accounts.




House bank BANKB

Pmt method 0

Currency USD

Account ID CHECK

Bank subaccount 113025

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.



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.




Paying co. code Classification Pmt method

BP01 Credit Card 9

BP01 Collection 0

4. Choose Back.




Country US

Pmt method 9

Description Biller Direct Credit Card


Payment method classification: Card Payment Selected




Selected


7. Choose Save.

8. Choose Back.

9. Choose Back.

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.



IMG Menu Financial Accounting Financial Accounting Global Settings Document Document Header Define Text Ids for Documents

2. On the Maintain Text Determination Configuration: List screen, make the following entries:


ID 0005




Description Correspondence Biller Direct

Relevant text Selected

3. Choose Save.

4. Choose Back.

3.4.2 Assign Text ID

Use The purpose of this activity is to assign the text ID to be used in SAP Biller Direct.



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:


Text ID 0005

3. Choose Save.

4. Choose Back.

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.



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.



Company Code BP01

Part. Settle CR Selected

Currency USD

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.



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

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.



Transm. Medium 5 External send

Processing 1: Program EBPP_BILL_NOTIFY

Processing 1: FORM routine ENTRY

6. Choose Output Types.



















15. Choose Save.

16. Choose Back.

3.6.2 Maintain Output Determination

Use The purpose of this activity is to define the output determination for documents.



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 Determination Procedure

2. On the Change View “Procedures”: Overview screen, select V10000 (Procedure) line, and choose Control Data.



Step Cntr CTyp Requirement

170 1 FIN0 406

180 1 FIN1 406



Step Cntr CTyp Requirement

190 1 FIN2 406

5. Choose Save.

6. Choose Back.

7. Choose Back.

8. Choose Back.

3.6.3 Defining E-Mail Address

Use The purpose of this activity is to define the e-mail address of the sender for notification messages.



IMG Menu Financial Accounting Financial Accounting Global Settings Company Code Enter Global Parameters

2. On the Change View “Company Code Global Data”: Overview screen, select BP01 (Company Code) line, and choose Details.

3. Choose Address.

4. Choose Other communication.

5. Select INT (Communication Method), and choose Enter


E-Mail Address Standard Number

<e-mail address> Selected

7. Choose Enter.

8. Choose Enter.

9. Choose Save.

10. Choose Back.

11. Choose Back.

3.7 Define Settings for Payment Cards

3.7.1 Determine Card Categories

Use



The purpose of this activity is to specify a range of numbers that are acceptable for each credit card.



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.



Type AMEX

Seq. 1

Cat 01

4. Choose Limit Checkmark.

5. On the Limit screen, make the following entries:


Payment cards from 30000000000000000

To 39999999999999999

6. Choose Execute.



Type VISA

Seq. 1

Cat 01





To 49999999999999999

10. Choose Execute.



Type MC

Seq. 1

Cat 01







To 59999999999999999

14. Choose Execute.

15. Choose Save.

16. Choose Back.

3.7.2 Assign G/L Accounts

Use The purpose of this activity is to define and link for each payment card type a receivables account.



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.


Application Condition Type

Chart of Accounts

Sales Organization

Card Type

G/L Account no.

VD A001 0010 BP01 AMEX 125300

VD A001 0010 BP01 MC 125300

VD A001 0010 BP01 VISA 125300

5. Choose Save.

6. Choose Back.

7. Choose Back.

3.7.3 Set Account Determination for Credit Cards

Use The purpose of this activity is to define and link for each payment card type a receivables account.





IMG Menu Financial Accounting Accounts Receivable and Accounts 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.



Payment card type

Card Category

Payment Method

Currency Receivables account

AMEX 01 9 USD 125300

MC 01 9 USD 125300

VISA 01 9 USD 125300

5. Choose Save.

6. Choose Back.

7. Choose Back.

3.8 Assign Number Range

3.8.1 Define Number Ranges

Use The purpose of this activity is to assign the number range for notification type.



IMG Menu Cross-Application Components Notification Notification Creation Notification Type Define Number Ranges

2. On the Number range - message screen, choose Maintain Groups.

3. Select Notification Type 70 (under the group Not assigned).

4. Choose Select element.

5. Select Internal Service Request checkbox.

6. Choose Assign element group

7. Choose Save

8. Choose Save.



9. Choose Back.

10. Choose Back.

3.9 Define Settings in the Application

3.9.1 Create Condition Records

Use The purpose of this activity is to create condition records used in the billing document for sending notification messages.


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.




Output Type

FIN1



14. On the Create Condition Records (Send Link per Job): Fast Entry screen, make the following entries:



F2 (Invoice) BP 5 1




15. Choose Enter.







19. Choose Save.


Output Type

FIN2



23. On the Create Condition Records (Send Link per Job): Fast Entry screen, make the following entries:



F2 (Invoice) BP 5 1






24. Choose Enter.







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

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 Update Company Code Address Information1. 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.

6. Enter a valid email address in the E-Mail field.

7. Save your entries.



3.10 Configuration of JCO RFC Server

3.10.1 Create RFC Destination

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.


Transaction Code SM59

2. On the Display and Maintain RFC Destinations screen, choose Create.



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.



Unicode Selected

Default Setting Selected

6. Choose Save.

7. Choose Back.

3.11 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.

3.11.1 PrerequisitesYou have done the following:

Deployed SAP Biller Direct (instructions provided in the Wholesale Quick 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 users BD_REF and 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_REF) and choose the Create button.

o In the Address tab, enter the last name.

o In the Logon data tab, enter password (for example, init). Remember your password for your BP_POOL user as your need to enter the password later in the procedure.

o In the Profiles tab, under Profiles, enter SAP_ALL and SAP_NEW.

o Repeat the earlier four steps to create the next user (for example, BD_POOL).

3.11.2 Configuring a Scenario

3.11.2.1 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 (for example, http://server:1080/root/admin/xcm/init.do)

2. Under Application Configuration in the navigation structure on the right 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.

3. Choose FI_UserManagement to select it as a template.

4. Enter WSD_FI_UserManagement as the name of the scenario.

5. Choose .

6. Select Display Advanced Settings.

7. Select default configuration.

8. Choose Save Configuration.

9. Choose .

10. Enter WSD_FI_ApplicationSettings for Configuration Name.

11. Choose .

12. Select Accounts Receivable (FI-AR) for Base Configuration.

13. Enter/select value as follows:







14. Choose .

15. Choose .

16. Choose .

17. Enter WSD_FI_ConnectionManager for Configuration Name.

18. Choose .

19. Select appropriate value from Base Configuration.



20. Enter appropriate values for the parameters, for example,

21. Choose .

22. Choose - 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.

23. Choose .

24. Choose .

25. Enter WSD_FI_JCoRFCServer for Configuration Name

26. Choose .

27. Select values as follows:



28. Choose .

29. Choose .

30. Choose .

31. Enter WSD_FI_UserInterface for Configuration Name

32. Choose .

33. Select Private Customer View (B2C) for Base Configuration.

34. Select values as follows:

35. Choose .

36. Choose .

37. Select Display Advanced Settings.

38. Select WSD_FI_ApplicationSettings for ApplicationSettings.

39. Select WSD_FI_ConnectionManager for ConnectionManager.

40. Select WSD_FI_JCoRFCServer for JCoRFCServer.



41. Select WSD_FI_UserInterface for UserInterface.

42. Choose Save configuration.

43. Close your browser.

44. Restart SAP J2EE Engine for your XCM settings to be effective.

3.12 Modify SAPJSF User

3.12.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.


Transaction Code SU01

2. On the User Maintenance: Initial Screen, enter the following information and choose Change.


User User Name SAPJSF

3. Choose Profiles.

4. On the Maintain User screen, enter the following information:


Profile Profile Name SAP_ALL

5. Choose Save.

3.13 Create BADI Implementation

3.13.1 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.


Transaction Code SE18



2. On the Business Add-Ins: Initial Definition Maintenance Screen, make the following entries and choose New Entries.


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.


Implementation Name ZAPAR_EBPP_NOTIFY2

6. On the Business Add-In Builder: Change Implementation ZAPAR_EBPP_NOTIFY2 screen, make the following entries and choose Interface.


Implementation Short Text Send Notification eMail Message

7. Double-click on CREATE_TEXT method.

8. Choose Yes on the Save screen.

9. Enter the Package and choose Save.

10. Create a transport.

11. Copy the following text between the lines method… and endmethod.

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 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: '', 'Customer Number:', '', l_kunnr, ''. add_line: '', l_name1, ' '. add_line: l_stras, ' '. add_line: l_ort01, ',', l_regio, l_pstlz, ''. add_line: '', l_line, ''.

add_line: '<table border>'.

add_line: '<tr>'. add_line: '<td>', 'Document Number:', '</td>'. add_line: '<td>', i_vbdkr-vbeln, '</td>'. add_line: '</tr>'.

add_line: '<tr>'. add_line: '<td>', 'Document Date:', '</td>'. add_line: '<td>', l_fkdat, '</td>'. add_line: '</tr>'.

add_line: '<tr>'. add_line: '<td>', 'Purchase Order No.', '</td>'. add_line: '<td>', i_vbdkr-bstnk, '</td>'. add_line: '</tr>'.



add_line: '<tr>'. add_line: '<td>', 'Amount:', '</td>'. add_line: '<td>', l_netwr, '</td>'. add_line: '</tr>'.

add_line: '</table>'.

add_line: '', 'To view details/payment, click:', '<a href="', l_link, '">', l_link, '</a>'. add_line: '', 'King regards,', ''. add_line: '', 'SAP Best Practices', ' ', 'FSCM', ''.

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.14 Assign Number Range

3.14.1 Assign Number Range to Notification Type

Use The purpose of this activity is to assign a number range object to the notification type.



IMG Menu Cross-Application Components Notification Notification



Creation Notification Type Define Number Ranges

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.

5. Select/check the box for Internal Service Request.

6. Choose Element/Group.

7. Choose Save.

3.14.2 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.


Transaction Code SM59

2. On the Display and Maintain RFC Destinations screen, choose Create.



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.



Unicode Selected

Default Setting Selected



6. Choose Save.

7. Choose Back.

3.14.3 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 W22 scenario to find the procedure for user creation with the Biller Direct Web Frontend.

Procedure1. Open the following file with a text editor, for example, 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.