Financial Supply Chain Management Biller Direct Process Integration with Accounts Receivable Accounting 

I think you may need to activate the BADI APAR_EBPP_GET_DATA. 

All configuration in SPRO is done, thats why we can see SD billing documents in Biller Direct, do you think if we still missing something which is responsible for not getting FI open items. 

Yes, we have all the BADIs active: APAR_EBPP_GET_DATA EBPP_INVOICEDETAIL EBPP_INVDETAIL_MM EBPP_INVDETAIL_SD 

Select FI_UserManagement under Application Configuration -> SAP

Click on edit button, Give a name to the custom configuration, say BDTest. Then click on Create Button. 

Select the checkbox corresponding to default configuration. 

Leave the default UserManagement value as fi. 

In Application Settings select the option Accounts Receivable (FA-AR). 

In UserInterface select the option Private Customer View (B2C). 

In ConnectionManager select the option “Select to create component configuration” and click on the 

button ConnectionManager.

Give a name say BD_CM and click on Create button. 

Mention the parameters to connect to your backend ECC system. 

Select  back to application configuration to go back to your main screen. 

Select the option BD_CM corresponding to ConnectionManager.

Click on the Display button to display advance settings. 

Corresponding to JCoRFCServer select the option “Select to create component configuration”. Then 

select the button JCoRFCServer. 

Give the name as BD_JCoRFC and click on Create button. 

Mention the programID as BillerDirect. The gwServer should be mentioned as sapgw. 

Mention the other parameters as defined below.

Select  to go back to your main screen. 

Corresponding to JCoRFCServer select the option BD_JCoRFC. 

Save it.

Restart the BD application for the changes to take effect. 

2. Settings in the Backend ECC System  

In the SAP Easy Access menu, choose Tools -> Administration -> Administration -> 

Network -> RFC Destinations. 

Create a new RFC connection with the name JCO_LDAP_RFC_DEST. Do not change 

this name as it is used as a reference. Enter T (Start an external program via TCP/IP) as the connection 

type.

On the Technical Settings tab, set the activation type to Registered Server Program 

and enter the same ID in the Program field as in the XCM in the JCoRFCServer 

component (in the example, BillerDirect).

Enter the host of the SAP system you are using as the host under Gateway Options 

(such as pwdf0143.wdf.sap-ag.de) and under Gateway Service enter the same 

setting as in the JCoRFCServer component in the XCM (such as sapgw10).

Go to the tab MDMP & Unicode and select Unicode.

Click on the save button. You can test the connection by choosing Test Connection in the application

toolbar, providing you have started the Java server.

3. Integration with SAP Portal  

Create a portal system under System Administration -> System Configuration -> Portal 

Content of type com.sap.portal.howtos.webapp (portal archive). 

Open the system. Under Portal Category System Definition mention the properties as 

shown below. 

Name of the server:  

Port number:  

Protocol of target system: Http/Https 

URL of web application: bd/public/frameset_top_html.jsp

Under Property Category UserManagement mention the properties as shown below: 

Logon Method: UIDPW 

User Mapping Type: admin,user 

Give a system alias for the system. 

Create an iview of type com.sap.appintegrator.sap under Content Administration -> Portal Content. 

Open the iview. Mention the properties as shown below: 

System:  

URL Template: System.protocol>://:/? 

URL Template fragment for User Mapping: j_user=&j_password=

In the Authentication Scheme select uidpwdlogon

SAP Biller Direct on SAP Portal?Posted by AVIK SANYAL in avik.sanyal on Oct 29, 2012 4:44:03 PM

inShare

Hello Friends, After months I finally sit down to write a blog on SDN. Thanks to "Sandy" and thanks to Biller Direct project that I have been doing for my client here in NYC. Now, my client wants to use Biller Direct and want to publish it on WWW so that all its customers can view, pay bills etc. This makes perfect sense, as many leading utilities companies use this package to cater to similar requirement. Even we as customers use it all so often when we pay our utilities bills without even thinking that we are dealing with SAP. So, I come up with a plan. Deploy the biller direct package, make a few settings on XCM Admin and we are all set to go.Then my client required look and feel changes based on the branding policies.Also, there are some additional config tweaks that my client needed to align the process. Took me a few weeks and some coding and configuration effort and yuppy. We are done. Now the big challenge.......!!!! Our customers needed new logon screen.Also, they wanted to show Portal FAQ docs and Policy documents that are published on Portal on the Biller Direct page.So, how do we do that? The answer is we integrate with Portal.For this I created an alias. Created a Portal Desktop. Created an iView that launches the BD App.Then I created a page that has both the BD App iview and KM iViewThen I mapped all of them together. I add a new rule that opens up the Desktop for BD when accessed via the alias something like https://<host>:<port>/irj/portal/bdAnd we are done. For the new logon page, I decided to use the good old formula for Portal Logon PAR modification. And I add new JSPs and modify look and feel as per client's recommendations and write a small if-else block that opens up the modified JSPs when accessed via alias. The Result is an outstanding, solid and elegant solution which the users love to use.The users have access to BD App and at the same time they have access to policy documents and How-Tos and FAQs. They have access to all the information at their fingertips. Combining the two areas was so much fun and so much challenging, but the results were really fulfilling. Hope you have fun and stay safe in this weather.