SRM 7 standard call structure to Ariba

[Former Member]

Hi all!

We are using SRM 7 with new ui add-on sp5 in classic mode with Ariba as an online-catalog.  All is working fine with an approval workflow...

Requesters are punching out to Ariba but the parameters we are using in the standard call out structure  are not distinct per users. 

uniquename field is set to pilotuser3 as a SAP field

emailadress is set to emailadress@here.com as a fixed value

fullname is set to user1 as a sap field

This is causing requesters to use the same userid (with auto create id on the Ariba side).  We cannot save distinct favorites and history on the Ariba catalog.  ie requesters use the ''same shopping list in Ariba''

I ve searched on the recent sdn posts and saw some are using

uniquename field is set to SY-UNAME as a SAP field (this sounds promissing)

Would appreciate suggestion for the two following fields , obviously as a sap fields since these are stored in at the user level in SAP.

emailadress

fullname

regards,

Dan

[Former Member]

Hi Daniel,

There are no such parameters available by standard.

As per Veer. his suggestion you need to program it.

You can use badi BBP_CATALOG_ENRICH_BADI for this purpose. It enables you to provide additional/programmed parameters upon calling the external catalog (web-service).

Kind regards,

Tim

[former_member228602]

Hello Dan,

           We dont store the email address of the logged in user in any readily available variables. You can however get the details by invoking the function module BAPI_USER_GET_DETAIL by passing the

sy-uname.

          The importing structure ADDRESS contains the full name and the table ADDSMTP contains the email address. I hope this helps.

Thanks and Regards,

Veera