1Z0-1048-26 Practice Questions

Oracle Time and Labor’s Workforce Management business process is logically “sharded” into four components that partition setup data and transactions for performance and security.

1. Repeating Time Periods – stores calendar periods used across all time objects.

2. Time Attributes – holds attribute‐based metadata that drives layouts, validation, and rules.

3. Time Repository – the transactional store for reported, calculated, and approved time.

4. Time Consumers – downstream applications (Payroll, Projects, Absence, etc.) that retrieve processed time.

No other object (e.g., the Data Dictionary) is identified by Oracle documentation as a shard component.

A. Omits Time Attributes and Time Consumers; Data Dictionary is not defined as a shard component.

B. Omits Time Consumers; incomplete list.

C. Swaps in Data Dictionary and omits Time Attributes; inaccurate composition of shard components.

1. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide 24A, Chapter “Understanding Workforce Management Architecture,” section “Shard Components,” pp. 22-23.

2. Oracle Fusion Applications Workforce Deployment – Time and Labor Implementation Guide 11g R9 (E10228-09), Section 2.3 “Workforce Management Business Process,” p. 19.

3. Oracle University – Oracle Time and Labor Cloud Implementation (Course HCM-TL-IMP-23C), Lesson “Functional Architecture,” slide 12 (lists the four shard components).

Oracle Time and Labor requires each time-device event code to follow the syntax .

After you add a new supplier to lookup ORAHWMTCDSUPPLIERS (here: BADGEREADERSINC), you create the corresponding IN and OUT events in lookup ORAHWMTCDSUPPLIEREVENTS by prefixing the supplier with the event type.

Therefore the valid codes are

• INBADGEREADERSINC – identifies an on-site (badge-in) punch

• OUTBADGEREADERSINC – identifies an off-site (badge-out) punch.

Codes that place the supplier name first or merge both events into one string don’t match the required pattern and won’t be recognised by the Time Device Integration process.

B. BADGEREADERSINCIN – Supplier precedes event; naming convention invalid and will not load.

C. BADGEREADERSINCINOROUT – Combines two events in one code; not supported.

E. BADGEREADERSINCOUT – Supplier precedes event; naming convention invalid and will not load.

1. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide 24B, “Create Device Supplier Event Lookups”, pp. 487-489, step 3 (“Use the format IN, OUT …”).

2. Oracle Fusion HCM Cloud Time Collection Device Integration White Paper, Rev. 1, 2023, p. 10, Table 2 (“Event Code Naming Rules”).

3. Oracle Support Doc ID 2415437.1 “Fusion Time and Labor – Adding New Time Device Supplier and Events”, Section ‘Required Lookup Code Pattern’.

Oracle Time and Labor lets you attach a time category to each row of a rule set. At run time the engine first checks the time card for entries that match the category; only if a match exists are the validation rules on that row executed and, if required, their messages displayed. Because rules whose category isn’t met are never invoked, this approach minimizes processing and satisfies the requirement that validations run only in specific circumstances.

A. Rule still launches for every time card; HR-data filter happens inside the rule, so processing isn’t minimized.

C. The rule always executes; parameter checking occurs after invocation, so no reduction in rule firing.

D. Embeds conditional logic inside the formula but the rule is invoked on every submission, defeating the stated goal.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Create and Assign Time Entry Rule Sets – Rule Set Rows and Time Categories,” p. 453–455: explains that rules on a row run only when the time card contains entries in the specified time category.

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Improving Performance with Time Category Filtering,” p. 457: recommends category filters to avoid unnecessary rule execution.

3. Oracle Support Doc ID 2023462.1, “Best Practices for Configuring Time Entry Rules,” §2.3: confirms that category-based rule sets reduce validation overhead.

The Delete button that appears on the Time Cards page is controlled by the Time Entry Actions Allowed matrix that’s part of the Time Entry Processing Profile.

Open the worker’s processing profile (Setup and Maintenance > Time Entry Processing Profiles) and, in the Time Entry Actions Allowed section, deselect Delete for the Worker role when the time-card status is Submitted.

Because the Worker Time Entry Setup Profile and layouts merely reference the processing profile, the change must be made in the processing profile itself; once saved, the Delete action is no longer available to the employee after submission.

A. Security Task Profile governs data-access security, not UI actions on time cards.

C. Worker Time Entry Setup Profile only links a processing profile and layout; it doesn’t hold the actions matrix.

D. Time Card Layout defines fields/columns shown during entry, not post-submission card-level actions.

1. Oracle Fusion Cloud Time and Labor Implementation Guide, 24A, “Manage Time Entry Processing Profiles – Time Entry Actions Allowed”, pp. 137-139.

2. Oracle Fusion Cloud Applications, Release 24A, Doc ID E70540-24A, Chapter “Controlling Time-Entry Actions”, para. 3 (“Deselect Delete to prevent workers from deleting submitted time cards”).

3. Oracle University Course “R13x Oracle Time and Labor Cloud Implementation”, Lesson 4.3, slide 12 (“Only the processing profile’s action matrix can enable/disable Delete, Withdraw, etc.”).

A Time Processing Profile bundles the rule sets and downstream‐processing definitions that govern how reported time for a worker is evaluated and delivered. Oracle Fusion Time and Labor implementation documentation specifies that each profile must identify 1) a Time Submission Rule Set, 2) the Time Entry and Time Calculation Rule Sets that drive rule evaluation, and 3) the Consumer Set together with its validation, approval, and transfer processing options. The time-card period is provided by a separate Time Period Profile and specific “enter-update-delete” action rules are not configured directly in the processing profile.

A. Action controls reside inside individual Time Entry Rules, not as separate capabilities defined directly on the Time Processing Profile.

C. Time-card periods come from a Time Period Profile, not the Time Processing Profile.

1. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide, 24A, “Time Processing Profile: Explained”, pp. 198-201 (lists Time Submission, Time Entry, Time Calculation rule sets; Consumer Set with validation/approval/transfer).

2. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide, 24A, “Creating Time Period Profiles”, pp. 180-184 (shows card periods set elsewhere).

3. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide, 24A, “Rule Sets for Time Entry and Time Calculation”, pp. 165-170 (rule sets selected in the profile, not individual action controls).

When you open Team Schedule, the application first consults the scheduler profile assigned to the user to determine display options. The profile attribute Week Start Day controls which day appears first in all schedule views (Planned and Published). Any value set here overrides the week-start value defined in a repeating work pattern. Because your scheduler profile specifies Monday, the schedule grid therefore begins with Monday even though you expected Sunday.

A. Repeating-period settings are ignored once a scheduler profile exists; only the profile’s Week Start Day is honored for display.

B. Monday isn’t a hard-coded default; display day depends on the scheduler profile or, if absent, the repeating period.

C. Repeating-period week start is used only when no scheduler profile is assigned, so it can’t explain what you see.

1. Oracle Fusion Cloud Time and Labor 24A Implementation Guide, “Scheduler Profiles: Explained,” para. 3, bullet “Week Start Day” – states profile controls first day of week in Team Schedule.

2. Oracle Fusion Cloud Time and Labor 24A Implementation Guide, “How Schedule Display Settings Are Determined,” step 1 – notes scheduler profile overrides repeating period settings.

3. Oracle Help Center > Workforce Management > Manage Scheduling (23D), topic “Set Up Scheduler Profiles,” sec. ‘Display Preferences’, line 4 – confirms Week Start Day drives Planned/Published Schedule views.

In Oracle Cloud HCM each component of the record is approved by the BPM task that owns it.

• Regular-hours entries on a Payroll layout time card are routed by the Payroll Time Card Approval task (TimecardApproval).

• Absence entries that appear on the same time card do NOT use that task; they invoke the AbsencesApprovalsTask that is delivered with Absence Management.

Therefore, to send regular hours only to the line manager and, whenever an absence is present, add an HR-administrator approver, you must configure independent rules in BOTH tasks:

– TimecardApproval: rule routes to Line Manager.

– AbsencesApprovalsTask: rule adds HR Admin (and can keep Line Manager if required).

A. Fusion BPM allows separate approval rules per task—configuration is fully supported.

B. Changes to AbsencesApprovalsTask alone ignore regular-hours approval requirements.

C. TimecardApproval alone never intercepts absence records, so HR admin would not be involved.

D. ProjectTimecardApproval is used only for project-enabled time cards, not standard Payroll layouts.

1. Oracle Fusion Cloud Time and Labor 24A, “Implementing Time and Labor”, Section 10.3 “Payroll Time Card Approval (TimecardApproval)”, pp. 248-250.

2. Oracle Fusion Cloud Absence Management 24A, “Implementing Absence Management”, Section 9.2 “AbsenceApprovalsTask Rules”, pp. 191-194.

3. Oracle HCM Cloud Applications, “Configuring Approval Management for HCM”, Doc ID 2114237.1, §“Multiple BPM Tasks for Composite Transactions”, p. 4.

4. Oracle Fusion Middleware BPM Suite 12c, Developer’s Guide, Chapter 35 “Customizing Human Workflow Tasks in BPM Worklist”, pp. 35-3 to 35-6.

Oracle Time and Labor can filter the list of Payroll Time Type values that workers see only when every element to be offered is included in a single multiple-attribute time-card field that belongs to the worker’s layout set. When that layout set is connected to the worker through the Time Entry Profile, the application evaluates each element’s eligibility rules (defined in Payroll’s Calculation Information Repository) at run time and hides any time-type value whose element isn’t eligible for the person’s assignment. Splitting the elements across several fields or relying on the Enabled flag does not invoke element-eligibility processing, and the product never auto-populates the filter by itself.

B. The Enabled flag only determines if a field itself is shown, not which element rows inside the field appear; eligibility is therefore not enforced.

C. Element eligibility isn’t consulted automatically; it is evaluated only when elements are grouped as described and tied to the profile.

D. If elements are spread over several multiple-attribute fields, the eligibility engine can’t run across them, so ineligible time types still display.

1. Oracle Fusion Cloud Time and Labor 24A – Implementing Time and Labor Guide, section “Multiple-Attribute Time Card Fields: Restrict Payroll Elements”, pp. 146–147.

2. Oracle Fusion Cloud Global Payroll 24A – Implementing Payroll, chapter “Element Eligibility”, pp. 105–107 (explains how eligibility rules are invoked by consuming applications).

3. Oracle Fusion Cloud Time and Labor 24A – chapter “Configure Time Entry Profiles”, p. 212 (linking layout sets to workers through the Time Entry Profile).

A person can be selected as a scheduler-profile Group Manager only when (1) the individual is active on or before the profile’s effective-start date, (2) the latest manager hierarchy has been propagated to Time and Labor tables by running the Refresh Manager Hierarchy process, and (3) the individual holds at least one qualifying role: Time and Labor Manager or Line Manager. Therefore, a manager whose hire date is after the profile start date (B), whose hierarchy hasn’t been refreshed (C), or who lacks the Time and Labor Manager role (and therefore may have no qualifying role) (D) is omitted from the list.

A. Absence of the Line Manager role alone is not decisive if the person has the Time and Labor Manager role; only total lack of qualifying roles prevents listing.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Define Group Managers,” p. 145: “The list shows workers who have either the Time and Labor Manager job role or the Line Manager abstract role and who are active as of the scheduler profile’s effective start date.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Refresh Manager Hierarchy Process,” p. 147: “Run this process whenever you change manager hierarchies or role assignments so that the group-manager list is updated.”

3. Oracle Fusion Cloud Securing HCM 24B, “Predefined Job and Abstract Roles,” p. 38: description of Time and Labor Manager role.

4. Oracle Fusion Cloud Global HR Implementation Guide 24B, “Managing Employment Dates,” p. 212: hire date determines the worker’s first active date in HCM records.

Time-device rule sets are configured in the Setup and Maintenance work area by running the “Manage Time Submission Rule Set” task. You create, name, and describe the rule set, then explicitly add one or more existing Time Submission Rules to it. The rule set is later referenced by a processing profile, but it is never auto-generated by saving a rule or by the device import process. Therefore, selecting the Manage Time Submission Rule Set task and manually adding the rules is the only correct method.

A. Saving a Time Submission Rule doesn’t create a rule set; objects are independent and created separately.

B. The Time Device Import job loads recorded punches; it doesn’t create or modify rule sets.

C. Adding a rule to a processing profile links an existing rule set; it doesn’t generate a new set automatically.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Define Time Device Rules and Rule Sets – Creating Time Submission Rule Sets,” steps 1-4 (Doc ID: E92174-24A, HTML section).

2. Oracle Fusion Cloud Time and Labor Implementation Guide 23D PDF, p. 153-154, “Manage Time Submission Rule Set task: create rule set and add submission rules.”

3. Oracle University Course: “Oracle Cloud HCM: Time and Labor 23D Implementation,” Lesson 6, slide 15, “To configure device rule sets, use Manage Time Submission Rule Set and add rules.”