Download Workday HCM Data Loading: Implementer Flashcards & Integration Basics and more Exams Nursing in PDF only on Docsity!
Workday HCM Data Loading โ
Implementer Flashcards & Integration
Basics
Tenant unique instance of WD system
- Database secures data through password-controlled access
- Each tenant has unique URL
- Tenants are configurable to meet unique business needs Production Tenant the environment in which we manage and store a customer's live, active data. Since a Production tenant often houses confidential employee information and other sensitive business information, security is critical.
- Live in WD, official system of record
- Can be binding legal transactions Sandbox Tenant helps administrators and consultants develop and test new features, customizations, and configurations before deploying into the main production tenant. ----Data located in the Sandbox tenant is typically a copy of the data in the Production tenant.
- Experimentation
- Usually copy of production from previous Friday Transactions in SX NOT official Sandbox Preview Tenant
tenant is also a copy of the Production tenant, but it includes added functionality that will be available in upcoming Workday releases. The purpose of a Sandbox Preview tenant is to help customers understand both their pre-existing Workday system and additional functionality that will be available in future release. This allows customers to make strategic decisions about when and how to uptake new features. Copy of production tenant that is NOT regularly refreshed Early access to new functionality in WD - closer to release cycle Implementation Tenant provide a secure space for testing, prototyping, and training. Customers may have multiple implementation tenants for testing integrations, loading legacy data, and conducting unit and end-to- end user testing. AKA agpbaseload / empty / foundation tenant Demonstration Tenant Types (3) GMS tenant demonstration tenant containing sample, prepopulated data for a fictitious customer. You can use this tenant for research, learning, and testing for Workday HCM and Workday Financial Management deployments.(united) NEVER LOAD CUSTOMER DATA IN GMS Used for sample data, continued learning, and running sample scenarios The Alma Mater University (AMU) tenant contains preconfigured demonstration data for educational/student customers. (higher ed, college) Green Oak Valley (GOV) tenant is a demonstration tenant available for government customers Customer Central tenant auto-provisioned tenant that contains access to deployment tools. It sits over all nonproduction tenants to make deployment more efficient, consistent, and expedient. Configure settings in the agpbaseload tenant to enable access to the Customer Central tenant Takes data from one place and push into another Gateway to access the new tools and to manage interactions between tenants Setup Data forms structure, generic and consistent for all customers, but vary by country, ex: marital status, govt ids Source = WD Configuration Data
Reference ID uniquely identify specific instances of a business object in Workday
- Primary identifier for instances of objects in workday
- the identifier remails constant across all WD environments Each reference ID has a what? Reference ID Type Reference ID Type The attribute name that distinguishes the business object what do you search to see all ID types Maintain Integration ID (report) Employee ID associated with BO of employee, ex: applicant ID Reference ID of these objects are their respective IDs Workday ID (WID) globally unique identifier (GUID) that Workday automatically generates on all customer data. Workday IDs consist of a 32-character, nonchanging string, automatic Unique for EACH environment Except WID for org visibility = global WID, same for all tenants Only used when when no other ID is available Instance ID internal integration ID that Workday generates (e.g., 216$1). The first numbers identify object class or type, after $ is instance # Used for troubleshooting when logging support cases - one instance Do NOT load data off of instance ID To view: RA on object > Instance External ID a two-part unique identifier that is controlled by an external/3rd party system and can change. Used in integrations. External IDs consist of: A system ID, which identifies an integration system in Workday. For example, ADP is a system ID for a tenanted integration system between Workday and ADP payroll system.
A value which identifies a business object instance. For example, W-001 is the external ID value for the western region instance of the sales organization. BP Process Exception Audit Report report to find all business process definitions with critical errors WD automatic background process every hour to find exceptions on BP defs If BP broken, will automatically send Fix Business Process task to BP admins and provides link to correct definition Organization Exception Audit Report Allows you to view organizations for which there are errors or warnings. Organization Type Exception Report Allows you to view organization types for which there are errors or warnings. It then displays the organization type, such as Supervisory or Company, that has the problem and a description of the problem or solution. Audit Locations for Membership in Organizations Allows you to view each organization hierarchy that allows business sites and shows each business site that has a membership problem. Shows business sites that are in hierarchy more than once OR not included in hierarchy at all Reorg > Assign Locations benefit of copying reports? You can then modify them All Active Employees report displays loaded active employees Pre-Hire Pools report report to check if the pre hires are loaded in correctly. Might take couple mins to load in Tenant Setup Report select tenant setup task = manage / configure tenant-wide settings Areas: system, global, security, BPs and Integrations, HCM Additional configs: applications & worker profile and profile groups Edit Tenant Setup - System task information, default values, time zone config, name & address display, system setup, activity stream settings, mobile, location services, inbox settings, Customer Central, user activity logging, user feedback, media settings
domain security policies Worker Profile composite view of job, worker, and group Worker Profile Groups can be used to to establish profile header, summary, and overview for said group What is defined by Workday in terms of worker profile/worker profile groups profile groups available for each profile & reports and tasks available in each group What is defined by customers in terms of worker profile/worker profile groups reports and custom tasks that display for each group, groups that display in each profile, and display order Configurating Worker Profile S: configure profile โ worker profile โ select what should be displayed in profile S: configure profile group โ overview for worker profile โ delete , add, or edit rows S: configure profile header โ worker profile โ delete , add, or edit rows User-Based Security Group based on admin responsibility, assigned directly to specific user, access is tenant-wide / unconstrained, perform setup and admin tasks Must be manually unassigned if no longer required Role-Based Security based on responsibility within an org, assign assignable roles to positions or job, constrained or unconstrained but usu constrained, Partner, perform transactional and support tasks Assignable Roles Attached to role based sec group Need to be enabled for a specific org types Assign support and leadership staff for different orgs Used in role- based security group to identify members Security Mostly assigned to Sup Orgs Individual orgs must have a manage role Assigned manually
HR Administrator (User Based) Create, maintain, view, and report on all HR operational data regardless of organization. Examples include compensation, compliance, hires, job changes, organizational assignments, performance reviews, personal data, positions and headcount, recruiting, staffing, and time off. Approval authority for HCM business processes HR Auditor (User Based) View all HCM setup and operational data regardless of organization. View all HCM business processes. HR System User Based Integrate to third-party human resource systems HR Analyst (Role Based) Perform HR reporting functions for assigned organizations. Examples include reporting on positions, staffing, compensation, and benefits. Approval authority for HCM business processes. HR executive (Role Based) View all HR setup and operational data for assigned organizations. Approval authority for HCM business processes HR Partner Role Based Perform HR management functions for assigned organizations. Examples include creating and approving new positions, job assignments, and managing the job profile framework. Approval authority for HCM business processes. Org Administrator User based Create and maintain all organization setup data. Examples include organization types, organization subtypes, business sites, and membership rules. Approval authority for organization business process Security Administrator (User Based)
Skill Normalization all systems speak same language
- Background jobs automatically manage skill migration, reducing maintained skill volume over time Integrations get skill data to where it is most valuable Web services enable loading of external skills onto objects in Workday. Once imported, used in all skills-based ML applications. Include Tenanted Skills in Matching makes all of your skill data useful, whether it's mapped or not. Automate Skill Management Workday Skills Cloud conducts regular automated background processes to maintain and tidy up skills within your tenant. These processes include managing duplicate, synonymous, and deprecated skills. Duplicate Skill Management reduces the number of crowdsourced and maintained skills in your tenant, runs hourly Synonymous SM identifies skills in your tenant synonymous with a Skills Cloud skill. Workday then replaces these skills with their synonymous Skills Cloud counterparts, affecting all crowdsourced, maintained, and Skills Cloud skills in your tenant, excluding those that candidates use Foundation Recipe Loading Deployment Tool Tenant - Customer Central Used to organize the content in WDSetup into configuration packages. We consolidate these packages into recipes based on product SKU and countries. Impl only Entreprise Interface Build (EIB) Loading Data Type Tenant: Agpbaseload Used to build simple inbound and outbound integrations between Workday and external endpoints. Advanced Load (successor to iLoad) Loading Deployment Tool Tenant : Customer Central
Password protected Used to export, manipulate, and load data using Excel: XLSX, CSV, CSV ZIP, and XML files. Impl only Change tracker Migration Deployment Tool Tenant: Agpbaseload Returns changes made to configuration data within the selected timeframe and for selected users. Impl only Configuration Catalog Migration Deployment Tool Tenant: non-production Used to migrate specific data sets of factory default data from WDSetup into customer non-Production tenants. This includes certain reports and other sets of configuration. Customer Central (deployment tool) Migration Tenant: Implementation Password Protected An Implementation tenant that serves as a central hub to secure access to data migration tools. iLoad Loading Deployment Tool Tenant: Customer Central Password protected Legacy implementation tool used to manage data migration and data loading. Impl only Implementation Suites Summary Loaded with Foundation Recipe Tenant: Customer Central Centralized access to view relevant Implementation suites within customer Implementation tenants. Impl only
