Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SAP Biller Direct: Set-up LDAP fields for use with UME

When setting up UME with external LDAP for using SAP Biller Direct, new LDAP fields were added (see appendix 1), but how to link these fields with the parameters added in the j2ee admin tool (see appendix 2)?

The current situation is that even when the parameter name is the same as the LDAP field name, the value that is added from LDAP is not shown up on UME additional tab for Biller Direct (customized information)

What is the correct set-up of the LDAP fields to allow the UME to pick-up values from the LDAP fields (see appendix 4 and 5 for java classes)?

Appendix 1:

<attribute name="fscm_refuser">

<physicalAttribute name="sapBillerDirectFscmRefuser"/>

</attribute>

<attribute name="objtype_0">

<physicalAttribute name="sapBillerDirectObjType"/>

</attribute>

<attribute name="objkey_0">

<physicalAttribute name="sapBillerDirectObjKey"/>

</attribute>

Appendix 2:

Releasing and Processing Users in the UME

To enable new users to access SAP Biller Direct, you create a reference user (for the authorizations) and specify the business partners. To make these attributes that are specific to SAP Biller Direct visible in the interface of the UME, you release them.

...

1. Choose Visual Admin(J2EE Engine) ? Server ? Services ? Configuration Adapter ? cluster_data ? server ? cfg ? services ? Propertysheet com.sap.security.core.ume.service.

2. Enter the reference user com.sap.security.core.user.refuser:fscm_refuser as the value for ume.admin.addattrs.

Always release the type and key for the business partner:

com.sap.security.core.user.references:objtype_0; com.sap.security.core.user.references:objkey_0;

Separate the values with semicolons. If you use more than one business partner, increment the index of objtype_ and objkey_.

You have released the parameters in the UME, and can now process them in the interface of the UME.

Not what you were looking for? View more on this topic or Ask a question