Error while Passive enrollment to register end users of SAP Biller Direct

[Former Member]

Hello All,

We are in a process of creating a user in Biller Direct using passive enrollment.

After creating the request i am getting an notification number successfully, using this notification number from TX - IQS22 after  performing check data

when i am trying to Create User E mail i am getting the below mentioned error

Message Class    WEBFI_MASTER

Message Type    E

Message Number    338

Message Variable    Error when communicating with the JCO RFC server

Text    Bean APAR_LDAP_CREATE_USER_2not found on host <hostname>, ProgId =<program id >: Object not found in loo

    3

Some time i am able to create user successfully, in some cases it is failing i don't know whats going wrong.

I have configured XCM for JCO rfc server and registered RFC "JCO_LDAP_RFC_DEST"in SM59 Abap back end connections are working fine.

Please help me in moving forward

Thanks in advance

Regards

Vardhan.

[Former Member]

Hi,

Can you please let me know the version.

Note 782587 - FSCM-Biller Direct: Passive enrolement

Can you also check that the function module APAR_LDAP_CREATE_USER_2 is in your system in SE37 and is active.

Was it working before or stopped after some changes.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi Abrol ,

Thanks for your quick response.

We are on EEC6 EH3 both BD and ECC are on same instance.

I have reactivated FM in SE37 .

But again some times it is sending and some time its is poping up the same communication error as shown above.

Please  advice me in moving forward.

Thanks,

Vardhan

[Former Member]

Hi,

Please check if you can implement this note.

Note 1444579 - No error texts reported from SAP self user creation routing

Thanks

Rishi Abrol

[Former Member]

Hello Rishi,

I have implemented this note and verified still i am getting the same error.

I have also reactivated function module but still the error persists.

Thanks,

Vardhan.

[Former Member]

Hi,

What's the error message now. Still the same.

Thanks

Rishi abrol

[Former Member]

Hi Rishi

Yes the same error

Message Class    WEBFI_MASTER

Message Type    E

Message Number    338

Message Variable    Error when communicating with the JCO RFC server

Text    Bean APAR_LDAP_CREATE_USER_2not found on host <hostname>, ProgId =NWA_PROGRAM: Object not found in loo

    3

My  TCP/IP Connection JCO_LDAP_RFC_DEST is working fine still error persist.

Thanks,

Vardhan

[Former Member]

Hi,

As a last resort please check the below note else you will have to create a message with SAP.

Note 788192 - Using the JCO-RFC server

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

From the above note i have performed all the action but confused about the below mentioned  step

Activate the ISR Service "Create Users": Maintain the ISR message type 71 in the IMG

can you please let me know how can this be done .

Thanks,

Vardhan.

[Former Member]

Hi,

This means that you need to go in transaction SPRO.

Assign a number range to notification types 70 (create, change, delete address, bank and card data) and 71 (create user). To do this, choose Cross-Application Components ® Notifications ® Notification Creation ® Notification Type ®Define Number Ranges.

  Assign the accounting clerks who are to receive the notifications to notification types 70 and 71. To do this, choose Cross-Application Components ® Internet/Intranet Services ®Internal Service Request ® Scenario Definition ® Prepare General Notification ®Notification Creation ®Partner ®Define Partner Determination Procedures ® Assign Partner Functions to Notification Type

Below is the link.

http://help.sap.com/saphelp_afs64/helpdata/en/1a/844cc3e0517e47bc40d9870c2de962/content.htm

Hope it helps....

Thanks

Rishi abrol

[Former Member]

Hi Sri,

We are also facing the same issue.

Can you please let us know how did you solve this issue.

BR,

Anurag

[Former Member]

Hi Anurag,

All my standard configurations were correct except server program creation.

Make sure you are creating server program pointing to correct abap machine,

In my case there was an issue while creating server program, i was pointing to wrong ip-address.

Hope this helps.

Thanks,

Vardhan.