Exploring the Contingent Administration Menu

Objective

After completing this lesson, you will be able to identify the areas of the Admin Menu that impact Contingent transactions.

The Job Posting Template

The basis of contingent transactions is the Job Posting. Job postings are the documents that define the type of contingent worker a buyer requires, what the worker will be doing, and when and where the worker will be doing it, among other details.

The basis of all job postings is the Job Posting Template. Job posting templates are preconfigured structures that define the various data elements, settings, rules, and functionalities that will be available for a job posting request that is created using that template. They contain the default values and information fields that appear when a job posting is created, such as rates, supplier distribution lists, and specific rules that need to be applied to related job postings.

At least one job posting template must be defined before a job posting can be created; job postings cannot be created SAP Fieldglass without first choosing a job posting template. When a user creates a job posting, the template provides default information, reducing the number of fields required to create the posting.

A job posting during creation displaying the templates available for selection. Each template listed details the title, category, ST Bill Rate, and a Description. The list can be sorted by each of those details through fields above the list.

The manner in which job posting templates are configured depends on an organization's procurement workflows. For example, an organization can create separate templates to use when hiring for positions in marketing, finance, manufacturing, or really any position that it may need to hire for. Each template would be configured for the specific position required.

Contingent Administration Objects

As with everything in SAP Fieldglass, transactions are made possible by the appropriate configuration of objects in the admin menu. Job posting templates depend on a number of admin objects in order to capture the data required to make a distinct template. Most of the necessary admin objects that are to be used in a job posting template must be configured before the template can be created. The admin objects that typically make up a job posting template are depicted below.

Depiction of how the various contingent admin objects contribute to a job posting, starting with the Contingent Type, Labor Type, and Rates, all leading into the Job Posting Template, which is the basis of a Job Posting. It also shows the additional optional admin objects, including Worker Pay Type, Distribution List, Approval Group, Job Questions, Job Question Checklist, Qualification, and Qualification Categories as separate from the required four objects but still contributing to a job posting template.

Required Contingent Admin Objects

Of all the administrative objects listed in the admin menu, the following four culminate in and lay the foundation for a job posting. In fact, a job posting template cannot be created without them.

The SAP Fieldglass admin menu, highlighting the admin objects that are required to create a job posting template: Contingent Type and Job Posting Template in the Worker menu, Labor Type in the Company Structure menu, and the entire Rates menu.
1Contingent TypeContingent Types define the rules, settings, and defaults that are available in Job Posting Templates. They define the position that each template is created for. Selecting a contingent type is required when making a job posting template. It can be found in the Worker section of the admin menu.
2Labor TypeLabor Types are clusters of the most common job types that have been determined using industry-wide standards. Labor types are not presented as choices within transactions; instead, they impact the availability of associated job postings and templates and can drive the routing of postings to certain suppliers. The Labor Type object can be found in the Company Structure section of the admin menu. Note that Labor types are hard-coded into SAP Fieldglass; they cannot be added or created.
3RatesRates define the amount a buyer will pay a supplier for a worker or service. Rates are built using most of the admin objects found in the Rates section of the admin menu. (If the organization's tenant is configured to use Rates 2.0, a Custom Lookup for rates would also be a required in order to create a job posting template.)
4Job Posting TemplateThe Job Posting Template is the key item required for creating a job posting. It is the template that contains all of the basic information pertaining to a particular job. A job posting cannot be created without a job posting template to choose from. In order to create an appropriate job posting template, the contingent type and rates must first be configured. The Job Posting Template object can be found in the Worker section of the admin menu.
Rates are used across both Contingent procurement and Services procurement, so they will not be discussed at length in this course. Nor will Labor Types, which are defaulted designations and cannot be altered. If you require a review of those topics, please refer to the unit Working With Rates in the course Exploring SAP Fieldglass Administration.

Optional Contingent Admin Objects

There are a number of optional admin objects that can be included on a job posting template to capture information that an organization may require. These admin objects can contain information including which suppliers will receive the job posting, what criteria is necessary for a job seeker to qualify for a position, and how the job posting will be routed for internal approvals.

The SAP Fieldglass admin menu, highlighting the optional admin objects that can be used in a job posting template: Job Question, Job Question Checklist, Qualification, Qualification Checklist, and Worker Pay Type in the Worker menu, and Distributions List in the Supplier menu.
5Worker Pay TypeA Worker Pay Type, found in the Worker section of the admin menu, is an association category that allows for variances in pay rates based upon certain circumstances, such as whether the supplier or buyer will be responsible for paying the worker. While these Worker Pay Types are not required on job posting templates, they may be necessary for buyers who will have to consider differing payment circumstances across multiple locations.
6Distribution ListA Distribution List is a structured list of suppliers who should receive a particular job posting. If an organization uses multiple suppliers for a particular job type, a distribution list will allow all of those suppliers to receive a job posting for a specific type of worker. The Distribution List object can be found in the Supplier section of the admin menu.
7Job QuestionJob Questions are questions that appear on a job posting that a job seeker must answer before being considered for a position. They can help hiring managers judge whether the job seeker is the right fit. The Job Question object can be found in the Worker section of the admin menu.
8Job Question ChecklistsIndividual job questions cannot be added directly to job posting templates; they must first be grouped into Job Question Checklists, which are then added to templates. The Job Question Checklist object can be found in the Worker section of the admin menu.
9QualificationQualifications are characteristics or skills needed or requested for specific positions. They differ from job questions in that they offer more specific requirements and methods of gauging those requirements. The Qualification object can be found in the Worker section of the admin menu.
10Qualification CategoryQualification Categories are broad categories into which qualifications can be organized. They make it easier to find Qualifications when creating Job Postings. The Qualification Category object can be found in the Worker section of the admin menu.

We’ll walk through how to create some of these admin objects in later lessons and then fit them together to make a robust job posting template.

Summary

A Job Posting Template is the basis of a Job Posting, which is essential for procuring contingent labor. A template must be created using specific required and optional admin objects to capture necessary job information and to follow an organization's procurement workflows.

Key Points:

  • Job Posting Template: Critical for creating job postings in SAP Fieldglass, capturing default values and fields like rates and supplier distribution lists.
  • Required Admin Objects: Necessary components including Contingent Type, Labor Type, Rates, and the Job Posting Template itself, must be configured before creating a template.
  • Optional Admin Objects: Additional elements like Worker Pay Type, Distribution List, Approval Group, and Job Questions can be included to capture specific organizational needs.
  • Customization for Different Roles: Templates can be tailored for various positions (e.g., marketing, finance, manufacturing) to align with specific workflows.
  • Dependency on Admin Objects: Proper configuration of necessary admin objects is essential before a job posting template can be created and used.