What causes up50r_adapter to be bound?

[Former Member]

We are moving to HANA. In our non-HANA instances, we have always been able to delimit infotypes 0009 and 0006 when employees terminate. Our HANA instance which was copied from our PRD instance does not allow us to do that. Configuration entries are the same in our HANA and non-HANA tables. We get the message "End date .... is not permitted; It would cause a gap".

I can trace this to program SAPFP50P, include FP50PF40, line of code:

"IF up50r_adapter IS BOUND."

So it is bound in our HANA system and not bound in our other systems, and a different path of logic is then followed. Why would it be bound one place and not the other?

Regards

Janice Ishee

[siddharthrajora · Accepted solution]

is it occuring in standard program, there should be no changes as such ie hana or non hana

this can boil down to data issue, please check again

[Former Member]

We are implementing Success Factors and Employee Central at the same time as HANA. One of the Success Factors consultants changed the T77S0 table, GRPID=CCURE, GSVAL=PC_UI, GSVAL=X in HANA but blank in our non-HANA systems.

[former_member186746]

Hi,

For these infotypes with time constraint 1. What ususally happens is when you create a record with an end date, a new record is created using the end data as the start date with end date 31.12.9999

Just check in pa20 for user, select infotype 6 and click overview, the latest entry has an end date of 31.12.9999

I have no idea what the functional added benefit would be to end address of a non active employee. You only need PERSG and PERSK combination to figure out what the employment status is of an employee.

Kind regards, Rob Dielemans

[Former Member]

Do you know what makes something bound?