![]() ![]() The most common cause of this issue is changing the Account Assignment associated with either a position or org structure where there is no job change. This flag locks the employee master data on the PA side and can only be released by performing the action specified in table T77S0. When you transfer a position with an incumbent to a new company code, a ‘flag’ is created in the integration table T77INT. You will be unable to complete any actions until you remove the pre-booking lock. If you attempt to run an action for the employee, you will get a new message that reads Pers.number already flagged for. The error occurs when there is an organization change with no change in the assignment. SAP created a lock on employee master data when you transfer an employee across company codes to prevent changes until the corresponding assignment data is updated. We will also show you how to prevent it from happening again. We will show you how to solve this problem in a few minutes, even if it involves a large number of records. When you maintain employee master data in SAP, you may encounter an error that reads Pre-booking exists for personnel number. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |