Name: Utilizing Signature Authority in SAP Fieldglass
Uploaded: 2023-9-26
Duration: 420 s

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>Signature Authority is a user attribute and function within SAP Fieldglass that can be leveraged to route transactional object approvals through a financial approval chain. <br><br>At the conclusion of this lesson, learners will be able to recognize the benefits of utilizing Signature Authority within a company’s operations, configure user Signature Authority limits and establish Approval Chaining approvals, and demonstrate how to utilize currency conversions with Signature Authority. <br><br><br><br></div></div>

Utilizing Signature Authority in SAP Fieldglass

Within the SAP Fieldglass application, companies can configure approval processes for their operational workflows and relevant objects as they require. By utilizing Signature Authority functionality, a company can define financial thresholds for individual users, or in other words, the transactional amounts they can approve to then reference in the configuration of the approval groups across multiple currencies. Approval groups within SAP Fieldglass can be defined by user roles, or can reference budgetary and financial elements to determine the appropriate users and levels required for an object's confirmation. If a company looks to implement financially driven approval chains, configuring Signature Authority levels on their user population is required. Signature Authority is a function that determines if an SAP Fieldglass transaction item must be sent through a specific approval workflow, which in this instance is called the Approval Chain. It defines a financial limit at which a user can approve an item. If the cost is above the user's signature authority, the item is automatically routed to the next highest approver in the approval chain. Objects requiring approval are compared to the user's defined signature authority and route to the appropriate user for execution. This process continues until an approver with a high enough Signature Authority value is found to approve the job posting, work order, line item, or invoice. The amounts of a user's Signature Authority can be entered for each currency used by the buyer company. Therefore, a specific user can have different approval thresholds associated to different currencies. However, if various currencies have not been defined for a user, SAP Fieldglass can be configured to automatically convert a user's default currency to the target currency and determine if the signature authority limit has been reached in real-time. WorkingNet's Hiring Manager, Mavis, needs to create a job posting for an accounting clerk who will be based in Singapore. Mavis currently has a signature authority of 10,000 US dollars defined on her user profile, but does not have any amount established for the Singapore dollar at this time. Here is how the PMO team can modify and update Mavis's Signature Authority within SAP Fieldglass to then ensure that the financial approval of the job posting base in Singapore properly runs through to her work items. Anya, the PMO admin, logs into SAP Fieldglass and is brought to her homepage. Before she updates the Signature Authority elements for Mavis, she will initially review the Approval Group setup on the job posting object for the Singapore dollar currency. To do this, she selects the Admin icon on the vertical navigation pane. Next, she clicks the Approval Group link under the Workflow section to display all the configured Approval Groups for transactional objects in SAP Fieldglass. Anya types 'job posting' into the Name section and applies the filter to the Approval Group List view. She can then see the Approval Group for the job posting with the Singapore Dollar currency listed. Clicking on the Job Posting Approval Group for Singapore Dollar, Anya can see that the first level is set to PMO Edit, with the second level reflecting Approval Chaining being initiated at the Job Posting Owner role. This means that upon editing, the job posting will then route for Financial Approval and check the Signature Authority of the Job Posting Owner. Now that she's confirmed the Approval Group configuration is correct, Anya needs to manage and view Mavis's user profile settings. After opening the Admin Configuration menu, Anya navigates to the User button within the User section. Immediately, the list of all users is reflected on the screen. To filter down the list results, she types 'Mavis' into the Name section and hits enter, which will display the single result for the user that requires the update. Anya selects the link for Manager Mavis from the results to open the record. Scrolling through the record, she sees that Mavis has $10,000 defined as her Signature Authority for the US Dollar currency. Anya selects Edit to open the user profile and make necessary changes. After scrolling down to the optional Signature Authority section, Anya enters in '$13,500' on the amount line for the Singapore dollar currency. This is equivalent to $10,000 in US dollar currency, making the amounts equal for approval purposes. She then selects Update to save the changes made to Mavis' user profile. Mavis logs into SAP Fieldglass and selects the Contingent Labor button in the navigation pane. This will open the drop-down menu for that section. She selects Job Posting to open the list view of job postings. From this list view, she can create the job posting for the accounting clerk in Singapore. Mavis completes the job posting for the accounting clerk position, located in Singapore, for one month's duration. The total budget amount reflects $12,000 SGD for the contingent transactional object. Mavis selects the Approvals Audit Trails tab of the job posting object. Here, she can see that the job posting is now assigned to her, as the Approval Chaining configuration of the approval group and her assigned Signature Authority have directed it to her assignment. In an effort for the Signature Authority functionality in routing to operate within SAP Fieldglass, one of two configurations is required on any Approval Group object. Within a given Approval Group, the Approval Group type can either reflect Amount-Based or Approval Chaining. If the approval group is configured with an Approval Chaining type, all configured levels of the group will operate referencing the signature authority defined on the assigned user against the amount of the transactional object. If the type is Amount-Based, the Signature Authority can only apply if a level of the Approval Group reflects approval chaining. Without this configuration, all approvals will merely route through the user or user profile assigned on a particular level of the group, regardless of their Signature Authority. SAP Fieldglass typically recommends using the Amount-Based type as best practice as it provides a greater amount of flexibility for buyer's operational and approval practices. Buyers manage many operational workflows and approval processes within SAP Fieldglass, many of which have financial and budgetary impact. To ensure that the proper users with financial permission approve those objects appropriately, SAP Fieldglass offers signature authority levels to be defined for each currency on their user population. This allows clients to utilize approval chaining at specific levels of approval on the required operational object.