South African Business Address Changes
(Doc ID 1297657.1)
Last updated on FEBRUARY 06, 2018
Applies to:Oracle HRMS (South African) - Version: 12.1
Information in this document applies to any platform.
SARS requires the business address of employees to be submitted on the IRP5/tax file. The address is currently stored at the person level the customer would like it stored on the HR location.
a) Remove the "South Africa - Business" (ADDRESS_TYPE='ZA_BUS') from
PER_ADDRESSES (Person addresses).
b) Adjust the address style of HR location to use the ZA_SARS style.
c) Adjust Tax year end pre-process (archiver) to pick up the busines
address off the employee (primary) assignment by 1st checking if a location
is assigned directly to the assignment, if so then use that assignment
location, if not (the assignment location is null), use the location of the
organisation on the assignment. If the assignment organisation has no
location captured against it, that constitutes a validation error to be
raised by the Tax Year end Data Validation report.
SARS requires the business address of employees to be submitted on the IRP5/tax file. This however should not be stored at the person level, but rather on the HR location.
Storing the "South Africa - Business" address on the person, will cause massive duplication of data as the same address will need to be captured repeatedly on every person. With all the duplication comes the added risk of bad data quality. Also this adds huge overhead to the resources as so much more data capture is required.
If the business relocates an office the new business address will have to again be updated on each person, one by one (or would necessitate technical skills so that an update script may be written).
If the business address is stored on the hr location, it only needs to be created/maintained once for every office/site that the business has. This greatly enhances data quality and totally removes data duplication. Also the business now has the option of using this via the organisation that is assigned to an employee (the og has its own location) or if need be, by assigning a location directly on the assignment record.
Having the location on the assignment (directly or indirectly via organisation on the assignment) also now greatly eases the maintenance burden in the case of an office relocating as now the end-user may make use of the Mass Assignment update functionality to achieve the change and this without needing to call in technical support/help.
So, in short, having the business address at person level greatly increases waste (of resources, storage) and TCO, while having it at HR Location geatly reduces overhead, totally removes waste and allows for low TCO in this regard.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|