Free 1Z0-1048-26 Practice Test Questions and Answers (2026)

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’.

Calendar-entry validations must fire the moment the user clicks Save in the calendar dialog.

According to the Time and Labor implementation flow, only a Time Entry Rule (TER) is evaluated at that exact event. Oracle instructs implementers to build the TER fast formula with the delivered Workforce Management calendar-validation subroutine (for example, HWMCALENDARENTRYVALIDATION) so the formula can interrogate the worker’s schedule and return a message.

The finished formula is attached to a TER rule, placed in a TER rule set, and that rule set is referenced by the worker’s time-entry profile. This configuration meets the stated requirement; none of the other rule types are executed from the calendar dialog’s Save action.

B – “All of the above” is false because several listed options execute at different events or on different devices.

C – A Time Submission Rule (TSR) fires on Submit, not when the calendar dialog is saved.

D – No standalone “calendar validation function” exists; Oracle specifies the calendar-validation subroutine, making this description inaccurate.

E – Time Card Rules (TCR) evaluate the whole time card during Save/Submit, not single-entry dialog saves.

F – Time Device Rules (TDR) are evaluated on physical/mobile devices, not the web calendar entry page.

1. Oracle Fusion Cloud Time and Labor 24B Implementing Time and Labor Guide, “Define Time Entry Rules – Example: Validate Calendar Entry Using a Time Entry Rule,” pp. 124–126, Doc ID F48341-01.

2. Oracle Fusion Fast Formula User Guide 24B, “Workforce Management Calendar Validation Subroutines,” Table 5-1 (HWMCALENDARENTRYVALIDATION), Doc ID F30629-01.

3. Oracle Fusion Cloud Time and Labor 24B Implementing Time and Labor Guide, “Rule Evaluation Events,” p. 30 (TER vs. TCR vs. TSR vs. TDR distinctions), Doc ID F48341-01.

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.

When employees or managers distribute worked time across multiple projects, departments, or other costing segments, Oracle Fusion Time and Labor offers three allocation methods. The user can:

• enter the exact number of Hours for each segment;

• enter the Percentage of the total time card hours that each segment should receive; or

• choose Equally, letting the application divide the total hours evenly among the selected segments.

No other allocation types are delivered in the product, so Hours, Percentage, and Equally are the only valid choices.

A. “Time Card Period” isn’t an allocation method; it’s the span the card covers.

C. “Week” and “Bi-Weekly” are schedule periods, not allocation types.

D. “Number” and “Proportionally” aren’t defined options in the Allocate dialog.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, Chapter “Manage Time Entry Configuration”, section “Create Time Allocation”, Table 12-1 Allocation Methods – lists Hours, Percentage, Equally (Doc ID F46985-04, p. 428).

2. Oracle Fusion Cloud Time and Labor Using Time and Labor 24B, topic “Allocate Time on a Time Card”, step 4: “Select Hours, Percentage, or Equally.” (https://docs.oracle.com/en/cloud/saas/human-resources/24b/fautl/).

3. Oracle University courseware “Oracle HCM Cloud: Time and Labor Implementation”, Lesson 3 “Time Entry and Allocation”, slide 17 – “Allocation methods: Hours, Percentage, Equally.”

When a group is refreshed, Oracle HCM Cloud constructs membership in three steps:

1) add every worker explicitly marked Include,

2) add everyone who satisfies the criteria,

3) finally remove anyone explicitly marked Exclude.

Seven workers were manually entered in the Include/Exclude Members region; if no Exclude flag is set for them (the normal interpretation when the verb “added” is used), those seven are included regardless of criteria outcome. Additional salaried present or past employees may also be added, but the only quantity that is guaranteed—hence the smallest number the refresh must return—is those seven explicitly-included workers.

A. Requires knowing the organisation has at least one salaried current or ex-employee; not guaranteed.

B. “9” cannot be inferred from any rule or data given.

D. Minimum can be determined from include logic; it is 7, not indeterminable.

1. Oracle Fusion Cloud HCM: Implementing Global Human Resources, 23B, Chap. “Manage HCM Groups”, section “How the Application Builds Membership”, pp. 623-624.

2. Oracle Fusion Cloud HCM: Implementing Common Features for HCM, 23B, “HCM Groups: Include or Exclude Selected Workers”, p. 141 (“Workers added as Include are always returned unless explicitly excluded.”).

(Only official Oracle documentation—no commercial prep sources—has been used.)

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).

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.”

To display the overtime bar you must (1) create a repeating time-period definition that contains an overtime period and (2) allow the time-entry layout to highlight that overtime period.

When you create the repeating time period (Setup and Maintenance > Define Time Periods > Create Repeating Time Period) you mark the Contains Overtime Period check box in the Usage region; this generates an overtime period that can differ from the time-card period.

In the time-entry layout (Manage Time Entry Layout Components > Time Card Matrix) you enable the Highlight Overtime Periods option so the overtime bar appears on the calendar page and inside the matrix.

A – Time categories classify reported time; they don’t create or display overtime periods.

B – Formula-based periods generate variable lengths, not the fixed overtime segment required here.

E – “Overtime” isn’t a valid Period Type value; period type defines length (week, month, etc.), not overtime usage.

1. Oracle Fusion Time and Labor Cloud, Implementing Time and Labor, 23D, “Create Repeating Time Periods – Contains Overtime Period option,” pp. 43-44.

2. Same document, “Highlight Overtime Periods in Time Entry Layouts,” p. 112.

3. Oracle HCM Cloud, Setup and Maintenance Workbook – Time Management, section “Time-Entry Layout Properties,” Rev. 2023-10, p. 19.

4. Oracle Fusion Applications Help (MOS Doc ID 2079514.1) “How to Show Overtime Bar on Time Card Calendar,” Steps 1-4.

The customer wants payroll validations to fire as soon as the worker leaves the Time Entry page and clicks Next (which opens the Review page).

In a Time Consumer Set the only action that invokes validation at that point is “Next”.

Secondly, the transfer must include every payroll time-type entry, which the delivered time category “All Payroll Entries” already contains.

Option A combines exactly these two requirements—time category “All Payroll Entries” and “Validate on Time Card Actions” = Next—so it is the sole configuration that satisfies both parts of the scenario.

B – Adds absences; requirement is limited to payroll time types only, so transfer scope is too broad.

C – Validation fires only at Submit, not when the user clicks Next.

D – Validation fires on Save and Submit, but still not on Next, so Review-page requirement is unmet.

E – Fails both conditions: fires on Submit/Save, not Next, and also adds absences.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 23C, “Manage Time Consumer Sets”, Section ‘Validate on Time Card Actions’, pp. 211-212 — lists action ‘Next’ and its usage for review-page validation.

2. Same guide, Table ‘Delivered Time Categories’, p. 196 — defines “All Payroll Entries” as containing every payroll time-type entry (excludes absences).

3. Oracle Fusion Global Payroll Interface Implementation Guide 23C, “Transferring Time to Payroll”, p. 37 — confirms that “All Payroll Entries” is the recommended category when only payroll time is transferred.

Time-card approval rules reference the Repeating Time Period that you, as implementer, create with Manage Time Card Periods. Oracle Cloud Time and Labor lets you generate any repeating pattern (weekly, bi-weekly, 4-4-5, semi-monthly, monthly, etc.). When you build the BPM approval rule, you simply pick the required period from that list. Because the system accepts whatever repeating period exists, the set of valid approval time periods is not fixed but “any,” as long as the period is available in the Repeating Time Period lookup.

B – HCM groups determine who approves, not which time span a rule uses.

C – Excludes semi-monthly and monthly; rules aren’t limited to just weekly or biweekly.

D – Omits semimonthly and custom periods, so list is incomplete.

E – Omits biweekly and custom periods; not exhaustive.

F – Leaves out biweekly, monthly, and other possible patterns.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Manage Time Card Periods” section, para. 1-2: “You can generate any repeating time periods, for example weekly, bi-weekly, semimonthly, monthly, or any other that suits your business.” (Document ID F40238-01)

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Define Time Card Approval Rules,” step 3: “Select the Repeating Time Period … the rule applies to. The list comprises all repeating periods you created.”

3. Oracle Fusion Applications Help Portal, Topic “Overview of Time Card Approvals,” last paragraph: “The approval period is based on the chosen repeating time period; therefore, any configured period is valid for approvals.”

In the Web Clock device configurator, every button can have three optional associations that determine how the punch is interpreted and what additional data the worker supplies.

1. Time Card Field – lets the button collect an extra value (for example, Payroll Time Type).

2. Time Device Rule – determines the processing logic that converts the raw punch into a time-entry event (Clock-In, Lunch-Out, etc.).

3. Time Device Mapping – maps the captured device attributes to the application’s time-entry attributes.

Only these three pieces of information can be linked; icons and logic-rule sequences are defined elsewhere and aren’t attachable to an individual Web Clock button.

B. Display icon – Icons are part of the device layout definition, not linkable properties of a single button.

E. Logic rule sequence – Sequence belongs to rule-set configuration inside a time device rule, not a direct attribute of the Web Clock button.

1. Oracle Fusion Cloud HCM Time and Labor Implementation Guide 24B, “Configure Time Collection Devices – Add or Edit Web Clock Buttons”, steps 6-8 (pp. 127-128).

2. Oracle Fusion Cloud HCM Using Time and Labor 24B, “Entering Time Using Web Clock – Button Definitions” (p. 33).

3. Oracle University Courseware: Oracle Time and Labor Cloud 2023 Implementation Essentials, Lesson “Configure Web Clock Buttons”, slide 18-20.

Multi-attribute time card fields let you bundle several attribute values (for example, payroll time type + physical location) into a single list value. Workers simply pick the combined value that reflects the part of the day they’re reporting, so one column records both attributes. This keeps the card compact, avoids extra daily-detail rows, and prevents mismatches between time type and location, thus ensuring accuracy as users move between nearby sites.

A. Requires a separate daily-detail row for every location segment, expanding the card and offering no control over valid time-type/location pairings.

C. Entry-level daily details create additional sub-grids inside each day, making the layout longer and still needing multiple rows for multiple locations.

D. Adding Location as its own matrix column forces duplicate rows whenever location changes, inflating card size and risking invalid combinations.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24C, “Define Multi-Attribute Time Card Fields”, p. 164–167: “Combine attributes such as Location with Payroll Time Type in a single selectable value to optimize space and ensure correct entry.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24C, “Design Time Card Layout Components”, p. 148: explains impact of Daily Details and additional matrix columns on card length.

Oracle advises that you never change a rule that is already deployed and used in production because any edit forces the system to recalculate all historic time cards that referenced that rule, possibly creating new errors.

Instead, duplicate the rule, fix the input and output parameter values in the copy, and replace the old rule with the new, corrected one in the rule set. Finally, resubmit the affected time cards so that they’re processed by the updated rule.

A. Requires enabling HWMALLOWRULEEDITS and edits the live rule; Oracle guidance says to avoid editing deployed rules to prevent retroactive recalculation risks.

B. Same direct-edit approach as A (even keeps the rule in the set), violating recommended practice and still needing the profile option.

C. Deletes rule from set but still edits the deployed rule, contradicting Oracle’s “duplicate, don’t edit” recommendation and ignores profile requirement.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Maintain Time Processing Rules – Best Practices,” Note: “Duplicate the rule and make changes; don’t use Edit Deployed Rule in production” (Part No. F30546-01, chap. 16, p. 247).

2. Same guide, “Profile Options for Time and Labor,” table entry HWMALLOWRULEEDITS – default No; only needed when you insist on editing a deployed rule (p. 433).

3. Oracle Support Doc ID 2175672.1, “Guidelines for Editing Time Repository Rules,” section 2: “Recommended method is to duplicate and replace, not edit.”

(Only official Oracle documentation is cited; no commercial prep material used.)

Adding the four optional attributes as Row-Level Detail columns keeps them off the main grid. Workers expand the detail pane for each row, enter the values once, and the attributes automatically apply to every daily cell in that row. Because only the two mandatory fields remain as grid columns, the overall width of the start/stop time card is unchanged and virtually no extra horizontal scrolling is required for the weekly view.

B – Daily Details open a separate page for each day, forcing seven page visits per row and more navigation, not less scrolling.

C – A multi-attribute field still occupies at least one extra column and loses individual field validation and LOVs; scrolling is only slightly reduced.

D – Shrinking column widths does not remove columns; users still scroll to see all six fields, especially on smaller screens.

E – Freezing columns keeps mandatory fields visible but doesn’t eliminate the width added by four optional columns, so horizontal scrolling remains.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Configure Row-Level Detail Attributes” (Chapter: Design Time Card Layouts, p. 257–258): “Use row-level detail attributes to capture additional information while reducing the number of columns and horizontal scrolling in the time-entry grid.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Comparing Row-Level Detail and Daily Detail” (p. 259): explains that Daily Detail “requires users to open a day-level window for each date and is therefore not optimal for minimizing navigation.”

3. Oracle HCM Cloud Release 22B – What’s New, Feature: “Enhanced Row-Level Detail for Time Entry” (Doc ID 2869450.1): notes that placing optional fields in row-level detail “reduces the horizontal footprint of time cards.”

In Fusion Time & Labor, only Time Entry Rule (TER) formulas can raise validation or warning messages that appear on the time-card UI, whereas Time Calculation Rule (TCR) formulas return calculated time attributes.

To surface both kinds of information from one rule, embed (call) a TER formula inside a TCR formula with the Fast Formula SUBFORMULA/RETURN mechanism, pass the TER’s MESSAGECODE and MESSAGETEXT back to the TCR, and expose both the calculation results and the returned message in a custom TCR template. Because the message originates in the TER but is returned through the enclosing TCR, users see a single rule that delivers the process result line and the associated validation message on the Outputs train stop.

B – Reverses the allowed call hierarchy; a TER can’t invoke a TCR and still expose calculation results.

C – Uses two independent rules; messages are shown by TER, not “from the same rule” as required.

D – TCR templates don’t accept a TER template as a selectable parameter; no framework support exists.

E – There’s no “WFM validation utility” callable by a TCR; only TER formulas contain the validation API.

1. Oracle Fusion Time and Labor Implementation Guide 24A, “Define Time Calculation Rules: Calling a Validation Formula from a Calculation Rule,” pp. 188-190.

2. Oracle Fusion Applications Fast Formula Guide 24A, chap. “Calling Other Fast Formulas,” Example 3: SUBFORMULA with TER inside TCR, pp. 54-56.

3. Oracle Fusion Time and Labor Implementation Guide 24A, “Time Entry Rule Messages,” Table 17-3 (only TER formulas generate UI messages), p. 174.

4. Oracle Fusion Applications Fast Formula Reference – Time and Labor, “Message APIs (WFMMESSAGE),” note: “Supported only in Time Entry Rules,” p. 12.