SAP Writeback Data Elements
Data Writeback Elements
The following tables itemize all of the data that can be written back to SAP from Classic Nakisa HR Suite:
Attributes:
|
OrgUnit |
|
|---|---|
|
SHORT |
abbr |
|
STEXT |
name |
|
TLINE |
orgDescription_description |
|
BURKS |
orgCompanyCode_companyCodeId |
|
ABTEL |
orgDepartmentStaff_department |
|
LAND1 |
orgLocation_countryId |
|
PERSA |
OrgunitBelongsToPersonnelArea |
|
BTRTL |
OrgunitBelongsToPersonnelSubArea |
|
REGIO |
orgLocation_regionId |
|
ORT01 |
orgLocation_city |
|
GSBER |
businessArea_objectId |
|
Position |
|
|---|---|
|
SHORT |
abbr |
|
STEXT |
name |
|
TLINE |
posDescription_description |
|
STABS |
posDepartmentStaff_staff |
|
WKAVG |
posWorkPlan_hoursPerWeek |
|
VACAN |
vacancy_vacant |
|
PERSA |
posPersonnelArea_personnelAreaId |
|
BTRTL |
posPersonnelArea_personnelSubAreaId |
|
PERSG |
EmployeeBelongsToGroup |
|
PERSK |
posEmployeeGroup_employeeSubGroupId |
Relationships:
|
OrgUnit |
|
|---|---|
|
orgCostCenter_costCenter_choice |
A011 |
|
Position |
|
|---|---|
|
PositionBelongsToOrgunit |
A003 |
|
posCostCenter_costCenter_choice |
A011 |
|
PositionBelongstToPosition |
A002 |
|
PositionDottedToPosition |
A005 |
|
job_objectId |
B007 |
|
PositionManagesOrgunit |
A012 |
| Employee | |
|---|---|
|
EmployeeOccupiesPosition |
A008 |
OM/PA Integration After Writebacks
Following Classic Nakisa HR Suite writeback operations, you need to review and update your PA data requirements to ensure consistency between the OM structure and the PA structure (similar to batch input sessions that are processed in the Organizational Management system). Mass or bulk processing of PA measures can be handled as a batch job in several ways:
- By using the output of Changes Report to identify changes that may require PA measures, and having an HR PA Administrator process these changes manually based on these reports.
- By exporting the contents of the Changes Report to Excel, then manipulate it and feed it into a customer-specific mass report for PA measures.
- By using batch input procedures and transactions (reports RHINTE10/RHINTE20/RHINTE30).
- RHINTE10: If objects are created using Classic Nakisa HR Suite, this report generates the required relevant tables for OM-PA Object integration. (T513 - Jobs, T513S - Jobs, T528B - Positions, T528T - Work Center, T527X - Org Unit)
- RHINTE20: Checks for all objects for integration between PA and OM - tables T513/T513T - Jobs, T528/T528T - Position, and T528X - Org Unit. It will then compare it against the HRP table to find missing objects. If there are any missing objects, it will create the record.
- RHINTE30: Transfer OM to PA. This will create infotype 0001 and perform many integration checks.
For more details, see http://help.sap.com/saphelp_nw70ehp3/helpdata/en/bb/bdc1e8575911d189240000e8323d3a/frameset.htm.
After processing, we recommend running a combination of PD reports to ensure consistency of the PD data (including, but not limited to, RHCHECK1, RHCHECKP, RHCHECKI, RHCHECKRELATIONS, RHCHEXOB).
In most environments, using a combination of the processes listed above provides the best results, however Nakisa recommends starting with the last option as this process highlights only the OM/PA inconsistencies that need to be addressed.
|
Classic Nakisa HR Suite 2022.R2-SP1 © 2023
|
Nakisa Inc. All rights reserved worldwide. |