Exploring Data Connectors

So what do we mean by integration? Well, let’s start with what it doesn’t mean: It doesn’t mean that SAP Fieldglass is literally merged into these other systems.

These systems perform different functions, so even though there is a lot of information that is common to these systems, merging them together would be costly, difficult, and entirely unnecessary.

It’s far more practical to identify the common data and determine a method for sharing that data among the systems.

And that’s what we mean by integration: the manner in which the SAP Fieldglass application connects to and communicates with other applications, such as WorkingNet’s human resources, accounts payable, and security ID systems.

An integration with SAP Fieldglass facilitates the transfer of data, eliminating the need for manual data entry.

This would mean that Patricia, WorkingNet's Director of Security, wouldn't  have to continuously add new temporary workers to WorkingNet’s ID system. She can let SAP Fieldglass identify the new workers, and then use the ID systems to assign appropriate access to them.

This in turn removes the chance of errors that can be introduced through manual data entry.

So Nelson, WorkingNet's director of HR, doesn’t have to worry about a worker’s status being entered into the human resource system incorrectly. SAP Fieldglass can simply feed the worker information into the Human Resources system directly.

And it helps enforce proper business transactions by creating appropriate connections between specific data points.

This frees Melanie from worrying whether a transaction is performed incorrectly. SAP Fieldglass will provide WorkingNet’s accounts payable system with the predetermined information, ensuring appropriate checks on transactions.

Access data is the information that the systems require in order to recognize a particular user. This information dictates what systems and/or data a user can access.

For instance, when Nelson comes into the office in the morning with his coffee and bagel and signs into his computer with his username and password, he is entering the Access data that tells WorkingNet that— yep!—this is Nelson!

Of course, there’s more to the Access data than just the username and password: there is, in fact, an entire profile of Nelson that is shared.

If an organization has SSO—or Single Sign-On—enabled, that user profile is stored in a central system and used as the basis for access to all integrates systems.

SSO basically means that both SAP Fieldglass and the human resources system will accept the same user profile that Nelson has with WorkingNet, so that when he signs on in the morning, his credentials are essentially verified across any systems that are connected to WorkingNet via the SSO.

Hence the term: Single Sign-On. Nelson doesn’t actually have to log into the other systems individually: the SSO does it for him.

Master data essentially identifies WorkingNet as an organization.

It’s sometimes also called Foundational data because it represents the foundational attributes of the organization. Really, it’s any data that is critical to the day-to-day operation of the organization.

At a minimum, SAP Fieldglass requires Business Units, Sites, and Cost Centers to be defined as Master data in order to be able to perform transactions.

For instance, when Mavis, WorkingNet's manager of network engineering, creates a job posting, the master data indicates that the job is for the Information Technology business unit in the Chicago office and is to be billed to the Networking Engineering cost center.

Transactional data is just as the name implies: data that is generated for and by specific transactions in a system.

So when Mavis wants to procure Joe from reCrewIT, she’ll use SAP Fieldglass to create things like job postings, work orders, invoices, statements of work, and other items to procure Joe.

All the data used in those items constitute transactional data because they were integral and specific to the transaction of procuring Joe.

Then, when Mavis hires and onboards Joe, the transactional data regarding Joe is shared with the human resource system so Nelson can keep track of Joe’s employment; with Patricia’s identification management system so Joe can access to the appropriate WorkingNet office; and with Melanie’s accounts payable systems so she can ensure that reCrewIT is paid.