Who Modified a Job in SAP? A Guide to Tracking Recruitment Changes in 2026

[Regina]

I can tell you exactly who modified a job in SAP – it’s actually not as mysterious as it seems. In most SAP-based recruitment systems, every change to a job posting is logged in the change log or audit trail. You just need to check the transaction code SE16 or the specific PA20/PA30 infotype history. For example, when I needed to find out who changed the salary range on a role last month, I navigated to the Data Browser for table PA0001 (or relevant recruitment tables like HRP1001), filtered by the job ID, and the system showed the user ID, timestamp, and old vs. new values. The key is that user permissions are critical – only authorized users (like recruiters, hiring managers, or HR admins) have access to modify jobs. If you’re using SAP SuccessFactors, the audit log is even more straightforward: go to Admin Center > Audit Log and search by object type. In my experience, about 70% of modifications are done by the recruiter assigned to the requisition, 20% by a hiring manager, and 10% by system administrators correcting data entry errors. Below is a quick reference table for common SAP transaction codes used to track changes:

Transaction Code	Purpose
SE16	Data Browser – view table contents
PA20/PA30	Personnel Actions – display infotype history
SLG1	Application Log – system-wide logging
SUIM	User Information System – check user authorizations

So, to answer your question directly: the person who modified a job in SAP is the user whose ID appears in the change log. You just need to know where to look.

[RonanLee]

Honestly, I get why you're asking. I once spent an entire afternoon trying to figure out who changed a job title in our SAP system. It turned out to be a junior recruiter who didn’t realize they had edit permissions. The system logs are your best friend – I just go to transaction code SUIM and pull up the user’s activity report. But here’s the thing: people often forget to check the date and time. The modification might have been done days ago by a temp worker. My advice? Always look at the timestamp first, then cross-reference with the user’s role. That saves you from chasing ghosts.

[Virgil]

From a technical standpoint, the answer is in the SAP audit trail tables. I usually query CDHDR (change document header) and CDPOS (change document items) using the job object ID. The field USERNAME gives you the exact person. But here’s a catch: if the modification was done via an interface or API, the user might show as a system user like “BATCH” or “RFC”. That’s not a real person – it’s an automated process. So always check if the user ID is a named user or a background job. If it’s a batch user, you need to trace the job scheduling logs.

[ColtonAnn]

What matters to me is accountability, not just the name. When I see a job modification in SAP, I want to know why it was changed, not just who did it. The change log shows the old value and new value, so I can spot if someone altered the job description, location, or hiring manager without approval. In my experience, unauthorized modifications often happen when permissions are too broad. For example, a hiring manager might accidentally change the job status from “Open” to “Filled” because they thought they were closing a different role. So I always recommend running a monthly audit report using ALV Grid to flag any changes made by users outside the recruitment team.

[DeOmar]

I’m not an HR person, but I saw my job application status change from “Under Review” to “Rejected” overnight, and I had no idea why. I later found out that the recruiter modified the job posting to remove the position because the budget was cut. But the system logged it as a “job modification” and the user ID was the recruiter’s. So from my perspective, the answer is: the person who modified the job is the one who controls the hiring process. But it would be nice if companies sent a notification when a job status changes – it’s just fair to applicants.