cancel
Showing results for 
Search instead for 
Did you mean: 

SFI - Recruiting - Redefining the Originator

Former Member
0 Kudos

Hi there,

We are implementing the SuccessFactors integration with SAP and we installed AddOn 3.0

Integration is normally quite straight forward but we have found what seems to be a bug, although we have not found any problem/solution in the OSS notes, nor this forum

We are trying to enhance how to calculate the Originator, as the standard delivered method does not find anybody when the manager position is empty

We are able to extend any other field available in the HRSFI_B_FIELD_MAPPING_OUTBOUND with the exception of the ORIGINATOR. We think that it is due to the fact that the implementation for HRSFI_FLD_MAP_2_ORIGINATOR does not come with the filter SET_FIELD_SET_ID defined. All other implementations come with that filter but the ORIGINATOR. All SAP documentation that I could find requires the filter SET_FIELD_SET_ID to be defined with the correspondent FIELDSET

I am enclosing two images

- The Originator filters vs the Org unit filters (Org unit is a random field as any other field seems to behave exactly the same way)

Whenever we try to implement the BADI, we get an error stating "Conflict between adjustment SFSF_SET_FIELD = originator and SFSF_SET_FIELD = originator, as there are two implementations with the same filter and no option to add the missing SFSF_SET_FIELD_ID to the standard implementation

Is there any patch available for this scenario? Are you aware of any workaround or do you have any suggestion on how the ORIGINATOR field should be overwritten?


Thanks in advance,

Miguel

Accepted Solutions (0)

Answers (1)

Answers (1)

lukemarson
Active Contributor
0 Kudos

Hi Miguel,

What is it you're trying to achieve here?

Best regards,

Luke

Former Member
0 Kudos

Hi Luke,

We are trying to extend the Originator method using a custom field_set, without having to deactivate the standard Originator method delivered by SAP within the HRSFI_PROCESSING implementation.

We are delivering applications on a multi tenant environment, so we need to allow for tenants to use the standard fieldsets while others may use the one we modify or even can create a new one

We understand the key is the fieldset, so as soon as you define a new fieldset, you basically have to complete the implementation for all the fields that you want to use, as the standard ones define the standard field_set (either SAP_REQ_DEMO, SAP_DEMO_01 or SAP_DEMO_02) within the filter

It is possible to redefine ANY of those methods just by specifying your custom fieldset within the SFSF_FIELD_SET_ID. There is no need to deactivate the standard implementation

However, the Originator method does not define any filter, so when we try to create our custom field for it, it does show an error as it claims the method to be already declared

This seems to be a bug as there does not seem to make any sense not to filter the method by the fieldset, as it is done for all the other fields

However, there is a simple workaround: You just need to disable the standard implementation of the originator field. It is a simple solution but it will not work for those tenants trying to use the standard fieldsets

Not sure if I am clarifying our problem here though

Thanks for replying in any case!

Miguel