Creating a Contingent Type

Objective

After completing this lesson, you will be able to create a Contingent Type for use on a Job Posting Template.

Contingent Types

Contingent Types define the structures and behaviors of job posting templates and, by extension, the job postings themselves. They define the rules, settings, and characteristics of the job posting templates created from them by specifying what fields are visible, required, locked, or hidden. The configuration of a contingent type directly impacts not only the job posting templates made from them, but also the end user experience when creating a job posting from those templates.

A Job Posting Template Details page displaying the drop down menu, which contains the contingent types available in the tenant: AI Services, Business Analyst, Software Developer, and Standard.

Contingent types provide governance whilst also simplifying template management across an organization. Instead of customizing every template individually, templates inherit the logic from the contingent type they're associated with, making them easier to maintain, in alignment with the critical parameters for the type of procurement, and synchronized to business needs.

A contingent type is so important that, in fact, you must first select which contingent type is required to build a new job posting template from.

Watch the video to better understand the role a contingent type plays in a contingent procurement transaction.

SAP Fieldglass has established new generative AI functionality that aids the job posting creation process with the enhancement of the job posting descriptions along with the translation of those descriptions into other required languages. The utilization of these AI features can be managed, defined, and defaulted on the Contingent Type object to then be reflected on the associated job posting templates and job postings themselves.

Navigating the Contingent Type Admin Object

Worker section of the Admin Menu, the Contingent Type link is highlighted.
1To view a list of contingent types associated to the tenant, select Contingent Type from the Worker section of the admin menu.

Contingent Type List page

The Contingent Type List page provides minimal information; just the name and description of the type.

Contingent Type List page displaying the list of available Contingent Types. For each is listed the name and a description. The Software Developer link in the Name column is highlighted.
2To view the details of a contingent type, select an appropriate link in the Name column.

Contingent Type Details page

The contingent type details page displays all of the characteristics of the type, and indicates which fields are enabled, visible, or locked.

The Contingent Type Details page is divided into two sections: Job Posting Template Configuration and Job Posting Form Page Configuration. Each lists details in rows, while columns indicate if the data object is hidden, locked, the name of the item, and the item's default value. The Job Posting Template Configuration section, the Job Posting Form Page Confirmation section, and the eye and lock icons in the Hidden and Locked columns are highlighted.
3The creator configures the template fields and rules. The choices made in the Job Posting Template Configuration section determine the settings that display and the values that default when a job posting template is created using this contingent type. A default option must be selected for all mandatory fields and can also be selected for optional fields.
4The Locked? (padlock icon) and Hidden? (eyeball icon) columns are available for you to indicate whether the field is visible on the template and/or if the value should be locked. If a field is hidden, that field will not appear on the Job Posting Template. If a field is locked, that field will appear on the template but will not be editable. If all the fields in a section are hidden, the section is hidden on the job posting template and job posting.
5Job Posting Form Page Configuration controls what a user sees when creating a job posting from a template that uses this contingent type. The fields that display here depend on the previous configurations selected for the template unless the field is only on the form page. If a field or section is hidden on the template, it is also hidden on the form page. If a default value was defined in the Job Posting Template Configuration section, that value defaults on the job posting form page.

New Contingent Type Pages

The process of creating a contingent type is spread across two distinct pages: the Template page and the Form & Details page, each of which control different types of fields. (A third page is also included to allow you to review the information entered in the previous two pages.)

The configurable fields on each page are divided into columns: Hidden, which contains selectable "eyeball" icons that would hide or display the field; Locked, which contains selectable "lock" icons that would lock or unlock the field; and Item, which are the actual fields that can be configured.

The Template page contains the options that control what the end user will see when creating job postings derived from the job posting template that was created from is associated to this contingent type.

The template page is the first page that must be completed when creating a contingent type. It shows the Name field, as well as some of the fields available in the Job Posting Template Configuration section such as the title of the Job Posting, Description, and whether the Simplified Workflow should be enabled. Each of these fields includes the Hidden and Locked columns.

The Form & Details page contains the options that control what the end user will see when creating job derived made from the template that is associated to this contingent type.

The Form & Details page is the second page that must be completed when creating a contingent type. It shows the items contained in the Job Posting Form Page Configuration section, such as the number of positions, Site, Business Unit, and Job Type, among others. Each of these fields includes the Hidden and Locked columns.

For instance, locking a field on the Template page would prevent that field from being changed on the job posting template (and, if relevant, on the job posting itself). But changes made on the Form & Details page only affect the job posting, so locking a field would prevent that field from being editable on the job posting but not affect the template.

Create a Contingent Type

WorkingNet Networking, Inc., a global manufacturer of data networking equipment, is building new distribution centers in several countries, while simultaneously implementing new logistics software and processes. The new logistics processes will require WorkingNet's accounting methods to be revised.

To help transition to the new software and the revised accounting methods, Melanie, the manager of the finance department at WorkingNet, needs to procure several accounting clerks for the six-month period in which the software is being configured and implemented. Each new hub location will require at least one accounting clerk.

To accommodate these new positions, a new Job Posting Template must be created. But before that can happen, a contingent type must be in place. However, as WorkingNet has many office positions besides accounting that need to be filled during the transition, they want to create a contingent type that will accommodate all office positions, not just one for accounting clerks.

As the SAP Fieldglass administrator for WorkingNet, you are now tasked with creating the new contingent type to accommodate all office positions.

Summary

Contingent Types allow buyer companies to set standards and controls for specific contingent labor positions. They influence Job Posting Templates, user experience, and data flow all the way to invoicing.

Key Points:

  • Define Standards: Contingent Types set rules and defaults for specific contingent labor positions.
  • Impact Data Flow: They influence data from Job Posting to invoicing, affecting administration and user experience.
  • Regional/Role-Based: Often configured based on regional or role-specific requirements to simplify maintenance.
  • Streamline Job Posting: Simplify the job posting process by minimizing selectable attributes for end users.
  • Control Fields: Lock or hide non-applicable fields to keep job postings relevant and straightforward.