1. Definition:
- Master Data:
Permanent, relatively static data that defines core entities in the system, such as employees, organizational units, or pay structures. - Transaction Data:
Dynamic data that records day-to-day business events or activities related to employees, such as payroll runs, time recordings, or leave requests.
2. Nature of Data:
- Master Data:
Long-term and rarely changes. Example: Employee personal details, job positions, cost centers. - Transaction Data:
Temporary and frequently changes with business processes. Example: Monthly salary, overtime hours, promotions.
3. Examples in SAP HCM:
- Master Data:
- Employee Infotype 0002 (Personal Data)
- Employee Infotype 0001 (Organizational Assignment)
- Pay scale structures, Positions, Departments
- Transaction Data:
- Payroll results (IT 0008)
- Time sheets, attendance records
- Leave or absence records (IT 2001, IT 2002)
4. Purpose:
- Master Data:
Provides the foundation for HR processes and reporting. - Transaction Data:
Captures real-time business transactions to process payroll, benefits, and HR reporting.
5. Dependency:
- Master Data:
Needed before transaction data can be recorded. For example, you need employee info (master data) before processing payroll (transaction data). - Transaction Data:
Depends on master data to execute business operations.
6. Frequency of Update:
- Master Data:
Updated occasionally (e.g., job change, marital status update). - Transaction Data:
Updated regularly (e.g., daily attendance, monthly payroll).
7. System Storage:
- Master Data:
Stored in infotypes with long validity periods. - Transaction Data:
Stored in infotypes with specific periods and linked to events.
Sign in to leave a comment.