Writing the Required Feeder

As with previous rules you've written, you now need to write a feeder that lets the consolidation engine know where there are rules-calculated values in the Plan cube.

Keeping in mind the Date/Month discrepancy reviewed above, the following feeder statement in the rule for the Production cube (recall that the feeder in an inter-cube rule always goes in the rule for the source cube) is accurate:

['Quantity Produced - Kgs']=>DB('Plan',!CakeType,!Date,'Planned
Production
Qty - Kgs');

For a given CakeType and Date, this feeder statement feeds Planned Production Qty - Kgs in the Plan cube when the Production cube contains a value for Quantity Produced - Kgs. Note that the DB function in the feeder statement references the Date dimension, which is not a member of the Plan cube. (Month is actually the second dimension of the Plan cube.) As with the calculation statement above, this works because the Date and Month dimensions share common element names.

Procedure

  1. Double-click the Plan rule in the Server Explorer.
  2. Enter a SKIPCHECK; declaration at the top of the rule.
  3. Click Save in the Rules Editor.
  4. Right-click the Production cube in the Server Explorer and click Create Rule.

    The Rules Editor displays.

  5. Enter a FEEDERS; declaration in the Rules Editor.
  6. Enter the following feeder statement immediately following the FEEDERS; declaration: 
    ['Quantity Produced - Kgs']=>DB('Plan',!CakeType,!Date,'Planned
Production
Qty - Kgs');
  7. Click Save in the Rules Editor.