HCM Extract – Effective Date Parameter behaves incorrectly between Scheduled Run and Manual Run

Summary:

Hi,

I am working on an HCM Extract that needs to support both scheduled daily runs (using SYSDATE automatically) and manual runs (where a user can input a different effective date).

However, I am experiencing inconsistent behavior depending on how the Effective Date is configured (SQL bind / context binding / parameter default).

I tried using context binding/Post-SQL binding; unfortunately, for manual runs it sets the date to SYSDATE instead of the manually entered value. In SQL bind, the date does not increment for the effective date.

Is there a recommended approach (parameter design, binding type, or expression logic) that supports both scenarios cleanly?