Introducing the Contingent Workflow

Objective

After completing this lesson, you will be able to explain the process of procuring a contingent worker in SAP Fieldglass.

The Contingent Worker

Let’s look again at the relationship between Joe, re:CrewIT, and WorkingNet. Remember, Mavis agreed to take Joe onto her team for 6 months. This means that for the 6 months of his tenure with WorkingNet, even though he was paid by re:CrewIT, Joe was effectively a member of the WorkingNet staff. His day-to-day tasks were defined and directly managed by Mavis.

image depicting Joe as being managed by Mavis even though he is employed by re:CrewIT

In Joe’s case, because he was temporarily part of Mavis’ team and his tasks were directly managed by her, he was classified as a Contingent worker.

So a worker whose work is directly managed by the buyer equals contingent.

The Contingent Workflow

Let’s briefly run through one possible workflow illustrating how to procure and engage a contingent worker as a buyer. We’re going to break the process into three stages to make it easier to follow and show how the various users will enter information in SAP Fieldglass.

image depicting the process of engaging, managing, and paying a contingent worker

The three stages will show how SAP Fieldglass is used to procure, engage, and pay a contingent worker.

Procure

A job posting is created by the hiring manager and sent to the supplier for approval. If the negotiation of rates needs to happen then the program office (PMO) or the approver will assist with that prior to the job posting being sent to the supplier for review.

Create Job PostingIn SAP Fieldglass, the first thing Mavis must do, to fill the network engineer position, is to actually post the open position. Now, Mavis doesn’t actually post the position to a job board like CareerBuilder, LinkedIn, or Indeed. Instead, Mavis creates what’s called a job posting from a list of job posting templates WorkingNet’s PMO has made available in SAP Fieldglass. These templates consist of job duty descriptions, pay rates, work hours, worksite locations, and other such information.
Review Job PostingOnce the job is posted in SAP Fieldglass, it is routed for review and approval to Brian at WorkingNet’s PMO--or any other approvers within WorkingNet--to verify that the information on the job posting is correct and the budget is available.
Submit Job SeekersWhen the position is fully approved, the job posting is distributed to select Suppliers that WorkingNet has partnered with. These suppliers, like re:CrewIT, receive and review the job posting, interview potential candidates, and then submit a list of job seekers who meet Mavis’ criteria for the position.
Review Job SeekersMavis reviews the submitted job seekers and selects the best ones to interview.

Engage

Begins with the approval of the job posting and the onboarding of the worker. The buyer uses SAP Fieldglass to manage the worker by tracking milestones and deliverables, as well as tracking expenses and approving completed transactions.

Create Work OrderMavis decides she wants to hire Joe, an experienced data network engineer, so she creates a work order for Joe, which outlines the final terms for his new assignment.
Approve Work OrderThe work order is routed again to the PMO and any other approvers at WorkingNet to review and approve the final work order terms.
Complete OnboardingAny onboarding requirements for Joe are completed, as required by WorkingNet. Activity Items, such as the issuance of a security badge or the completion of certain reference checks, are Marked as Complete on Joe’s Work Order.
Register in SAP FieldglassJoe is then directed to complete any require onboarding activities then register in SAP Fieldglass.

Pay

The buyer approves a worker’s time and expenses and pays the supplier, who then pays the worker.

Submit Time and ExpensesJoe then uses SAP Fieldglass to track and submit his time sheets and any expenses, which are sent to Mavis for approval.
Approve Time and ExpensesWhen Mavis approves Joe’s time and expenses…
Submit Invoice…an invoice is auto-generated and WorkingNet pays re:CrewIT…
Pay Worker…who then pays Joe.

And that was a fairly common Contingent labor transactional process flow in SAP Fieldglass. But that doesn’t mean they’re all like that. The process of procuring a contingent worker is SAP Fieldglass can differ based on the needs of an organization, the processes defined by a program, and the manner in which is SAP Fieldglass is configured.

Log in to track your progress & complete quizzes