Bypassing cube refresh when change requests are released

When the cube refresh is bypassed, the cube refresh is not triggered each time a change request is released. The cube refresh is delayed until it is manually triggered, initiated by another process, or when a scheduled cube refresh occurrs. Bypassing the cube refresh reduces the number of cube refresh async triggers, prevents overlap with the scheduled cube refresh, and reduces the processing time of the cube refresh, improving the efficiency and availability of the cube.

Use this procedure to bypass the refresh of the GeneralLedgerTotal cube when change requests are released.

  1. Select Budgeting > Budget Edit Configuration.
  2. Open or create a record.
  3. To bypass the refresh of the GLTOT cube, select the Bypass Cube Refresh On Budget Change Order Release check box.
  4. Click Save.