Oracle Fusion HCM Patching Explained: CWB, Weekly Bundle, Monthly Maintenance Pack & Quarterly Updates (A Beginner-Friendly Guide)

Oracle Fusion HCM Patches Explained in Simple Terms

If you work with Oracle Fusion HCM—whether you're in HR, IT, a functional consultant, or a system administrator—you've probably heard terms like CWB, Weekly Bundle, MMP, and Quarterly Update.

At first, these names can be confusing. But once you understand what each one does, the whole patching process becomes much easier to follow.

Why Does Oracle Release So Many Patches?

Oracle Fusion HCM is a cloud-based application (SaaS), which means Oracle manages and updates the software for all customers.

Unlike older on-premise systems where companies decided when to upgrade, Oracle Cloud is updated on a regular schedule. This helps keep the system secure, stable, compliant, and up to date with new improvements.

Oracle releases updates in four different ways.

1. CWB (Continuous Weekly Build)

Think of this as an emergency fix for a specific problem.

• Released only when a particular issue needs to be fixed.

• You don't get it automatically.

• You request it only if your organization is facing that exact issue.

• Usually used when a bug needs to be resolved quickly.

Simple example:
"We've found a bug that's affecting us. Oracle has a fix, so we'll request that patch."

---

2. Weekly Bundle Patch

Instead of releasing individual fixes one by one, Oracle groups several recent bug fixes into a weekly bundle.

• Released every week.

• Contains multiple bug fixes.

• Optional—you only apply it if it includes a fix you need.

• Doesn't introduce new features.

Simple example:
"Oracle has fixed several issues this week. If any of those affect us, we can install this bundle."

---

3. Monthly Maintenance Pack (MMP)

This is the monthly update that everyone is expected to stay current with.

• Released once every month.

• Combines previous weekly fixes into one package.

• Mandatory for Oracle Cloud customers.

• Focuses on stability, reliability, and bug fixes—not new features.

Simple example:
"This is the monthly health check for your system. It keeps everything stable and up to date."

---

4. Quarterly Update

This is Oracle's biggest release and happens four times a year.

You'll see names like 24A, 24B, 24C, and 24D (or similar naming based on the year and quarter).

These updates include:

• New features

• User interface improvements

• Functional enhancements

• Performance improvements

Oracle first installs the update in your Test environment, giving your team time to test everything before it reaches Production a few weeks later.

Most new features are delivered through Oracle's Opt-In model. This means the feature is available, but you decide when to turn it on.

Simple example:
"This is the major upgrade. You get new capabilities, test them first, and enable them when you're ready."

---

Quick Summary

Patch Type	How Often?	Mandatory?	Purpose
CWB	As needed	No	Fixes one specific issue
Weekly Bundle	Weekly	No	Collection of recent bug fixes
Monthly Maintenance Pack (MMP)	Monthly	Yes	Keeps the system stable and up to date
Quarterly Update	Every 3 months	Yes	Adds new features and major improvements

The Easy Way to Remember It

Think of Oracle updates like maintaining a car:

• CWB = Fix one problem immediately.

• Weekly Bundle = A group of small repairs.

• Monthly Maintenance Pack = Your regular service to keep everything running smoothly.

• Quarterly Update = A major upgrade with new features and improvements.

Why Should You Care?

Knowing the difference helps your organization plan better.

• Better testing: Quarterly updates should always be tested before they reach Production.

• Less risk: Understanding which patches are optional and which are mandatory helps you focus on what really matters.

• Better planning: Someone should review the new Opt-In features every quarter so your business can take advantage of useful improvements instead of discovering them months later.

Once you understand Oracle's update cycle, it's actually quite straightforward:

Fix individual issues when needed → Collect fixes weekly → Apply a mandatory monthly maintenance update → Receive major new features every quarter.

Have questions about a specific Oracle Fusion HCM release or patch strategy for your organization? Drop a comment below or reach out — always happy to help demystify Oracle Cloud.

#OracleFusionHCM #OracleCloud #HRTechnology #HCMPatching #OracleFusionPayroll #Oracle

Cascading Value Sets for Element Input Values in Oracle Fusion Payroll

If you are configuring Element Input Values in Oracle Fusion Payroll and need a parent-child relationship like Bank to Branch, you might reach for an Independent or Dependent value set. However, assigning either of these will throw an error: "You must enter a valid value set. The current value set is <YOUR_VS_NAME>. (XLA-870689)."

Here is why this happens:

• Oracle Fusion Global Payroll has a hard restriction that only Table-based value sets are supported for Element Input Values.

• Independent, Dependent, and Format Only value sets are strictly not supported.

• Even without this restriction, the Input Values UI does not have a mechanism to pass a "parent segment" context.

The Solution: Table Value Sets and Context Parameters

You can still build a cascading experience using Table-type value sets by adding a context parameter to the WHERE clause. Oracle exposes a specific token for this purpose: :{PARAMETER.<InputValueName>}.

• The <InputValueName> must be the exact Name of the parent Input Value on the element.

• It cannot be the value set's code.

• It cannot be the display label.

Step-by-Step Guide: Building a Bank to Branch Setup

Step 1: Create the Banks Value Set (Parent)

Create your parent value set named ATL_BANKS_TBL_VS using the following configuration.

Field	Value
Validation Type	Table
Value Data Type	Character
FROM Clause	ce_index_banks cba
Value Column Name	bank_name
WHERE Clause	cba.BANK_INSTITUTION_TYPE = 'BANK'
ORDER BY Clause	bank_name

Step 2: Create the Bank Branches Value Set (Child)

Next, create the child value set named ATL_BANK_BRANCHES_TBL_VS to reference the parent parameter.

Field	Value
Validation Type	Table
Value Data Type	Character
FROM Clause	ce_index_banks cba, ce_index_bank_branches cbb
Value Column Name	cbb.branch_name
WHERE Clause	cba.bank_party_id = cbb.bank_party_id AND cba.BANK_INSTITUTION_TYPE = 'BANK' AND cba.bank_name = :{PARAMETER.BANK_IP}
ORDER BY Clause	cbb.branch_name

Step 3: Configure the Element

1. Create an Input Value named BANK_IP.

2. Set the UOM to Character and assign the Value Set to ATL_BANKS_TBL_VS.

3. Create a second Input Value named BRANCH_IP.

4. Set the UOM to Character and assign the Value Set to ATL_BANK_BRANCHES_TBL_VS.

5. Sequence the Bank input above the Branch input on the Input Values page.

6. Save and submit your configuration.

Selecting a bank on Element Entries will now automatically scope the Branch list of values (LOV) to that specific bank's branches.

Avoid This Common Mistake

The parameter token only works if its name exactly matches an actual Input Value's Name field.

• Wrong Setup: AND cba.bank_name = :{PARAMETER.ATL_BANKS_TBL_VS}. This incorrectly references the value set name.

• Right Setup: AND cba.bank_name = :{PARAMETER.<InputValueName>}. This correctly references the parent Input Value's Name.

• If you reference the wrong name, the parameter silently resolves to NULL.

• There is no error message; the LOV simply comes back empty, which can look like a data issue rather than a naming mismatch.