Define Pre-Posting for Team
Explanation
This activity establishes Pre-Posting for a Team,
which consists of Members supervised by one or more
Supervisors. The Pre-Posting details for a
Team are outlined in a separate section and are specified according
to each Company, as the Pre-Posting details
are tailored specifically to each Company. The main objective
of this is to facilitate the collective storage of common Pre-Posting
details for a group of individuals.
To include the Pre-Posting details, first input the
Company, which depends on the logged-in User’s
access privileges.
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 Team level, you can add all Code Parts
or selectively include necessary ones based on specific requirements.
The Validity Period defines when the Pre-Posting
details are relevant for the Team within a Company.
Overlapping Validity Periods for Code Strings
are not allowed for a Company within a Team.
In obtaining a Person's Pre-Posting details
from the Team, the Team associated with their
Direct Supervisor will be considered.
The Pre-Posting assignment at the Team
level emphasizes several key impacted areas as detailed below.
- Human Capital Management - Expense Sheet
- Financials Planning - Business Planning
- Project Management
- Human Capital Management - Salary Revision Request
- Human Capital Management - Headcount Statistics Snapshot
The priority sequence for retrieving valid Code Parts in
Pre-Posting details is as follows:
- 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.
- 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.
- 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.
- 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:
- Code Strings must be defined within the system.
- Code Part Values need to be established in the system.
- Teams consisting of Supervisor(s)
and Member(s) must be registered in the system.
System Effects
As a result of this activity, the specified Pre-Posting
details are now recorded at the Team level.