Error message "Person edited was rejected" during Simulation

[former_member223220]

Hello friends,

I receive the error message "Person edited was rejected" while simulating the travel expense in transaction TRIP or PR05. I have implemented the SAP note “1888288 - ES: Person edited was rejected in RPRTEC00” to solve this issue. But this error message is still coming.

Please help me with this issue. Thank you.

Best Regards,

Jeetendar

[Monika_]

Hi,

Have you maintained the constants MINHO and MINST for French in V_T706_CONST?

Regards,

Monika

[Former Member]

Hi Jeetendar,

OK it is only for one person or do you have this for all employees?

Also please check transaction PR_CHECK.

Best regards, Sigi

[former_member223220]

Hi Sigi,

This issue is arising only for few employees.

Best regards,

Jeetendar

[Former Member]

Hi Jeetendar,

OK, are you able to just save a trip for this person?

If yes than compare via transaction PRTE what is different for this person than for a person without any problem. (first two transparent table in the list of the report)

If not possible check exactly the HR master data to see what is different.

And check your feature settings in PE03.

Best regards, Sigi

[former_member223220]

Hi Sigi,

I have checked the transaction PRTE. The only difference for bot the employees is that they have different TRIP posting variant assigned.  The employee with the POLISH posting variant is ok whereas for employee with FRENCH posting variant is not ok.

I also checked the table v_T706_CONST. For both the varaints the enteries have been maintained.

Best Regards,

Jeetendar

[Former Member]

Posting variant = Trip Provision Variant?

Than your settings are not OK for the France Trip Provision Variant.

Please check transaction PR_Check for Trip Provision Variant France.

[Monika_]

Hi,

Check the PREC log file - in case a constant is missing in T706_CONST it's often listed in the log.

Regards,

Monika

[Former Member]

Hi Jeetendar,

Which trip variant does your employee belong to? Based on that there could be some missing entry in table v_T706_CONST or incorrect master data in IT0001 or IT0017.

Ankur