Define Pre-Posting for Person

Explanation

This activity is designed to establish Pre-Posting for a Person. The Code Parts are organized within the Personal File, customized for each of the Person's Employments. This means Employment records are categorized by Company, and the Pre-Posting details are dependent on the Company affiliations of the Person.

The Companies linked to the Person's Employment are displayed based on the logged-in User’s access privileges. In the context of a Company, the Employee field is an optional input that shows the relevant active Employment for the Person in the selected Company. This allows for specifying Pre-Posting details tied to a specific Employee, if needed. If no Employee is selected, it indicates that the details apply to the Person's Pre-Posting information for the Company.

Each Code Part includes the Company-specific Internal Name from the Define Code String page, with values sourced from the Code Part Values page. At the Person level, you can to add all Code Parts or selectively include only those necessary based on specific requirements.

The Validity Period specifies the duration in which the Pre-Posting details remain applicable for the Person employed at a Company. It is important to note that overlapping Validity Periods for Code Strings are not allowed for Employments. This means overlapping Validity Periods for Pre-Posting are prohibited for a Person or Employee within a Company.

The Pre-Posting assignment at the Person level emphasizes several key impacted areas as detailed below.

The priority sequence for retrieving valid Code Parts in Pre-Posting details is as follows:

  1. Transaction Level: First, verify at the transaction level, but only if the system has provided a designated space to specify the Pre-Posting details within a transaction.
  2. Personal File: If the information is not found at the transaction level, check the Personal File next.
    • If the search starts with the Employee perspective and finds a valid record, it retrieves the associated Code Parts and stops looking for a Person record. If no valid Employee record is found, it then checks for a valid Person record.
  3. Access Setup Configuration: If the details are still elusive, refer to the Access Setup Configuration page, focusing on the Supervisor Configuration Type:
    • Supervisor from Team and Supervisor Setup or Priority to Team and Supervisor Setup: If the configuration is set to any of these types, prioritize the Team.
    • Supervisor from Organization and Position Setup: If the configuration is set to this type, prioritize the Organization.
  4. Fallback: If the details are not found at the Team level, even after moving through the conditions, check the Organization as a further step.

Prerequisites

In order to perform this activity:

System Effects

As a result of this activity, the specified Pre-Posting details are now recorded at the Person level.