Importing Pillar Two Automation

• Pillar Two Automation Import is in the Config cube. See, Application Cubes
• To enable a rule that is currently disabled, the import must be run in Replace mode. See Load Methods. See, Load Methods.
• Import Pillar Two Automation rules return an error if the import files contain data imported to the wrong level. Only Enabled/Disabled column is allowed to be overridden at a lower level. If any wrong intersection exists in the load, the entire load will fail and an error is returned in Job console.
• Import Pillar Two Automation rules cascades all the columns excluding Enabled/Disabled to the lower levels (Global cascades to Jurisdiction and Entity; Jurisdiction cascades to Entity). All rules for any Scenario, Year, and Period within the load file are affected by this cascading.

Note:

If a new Global rule is imported as disabled, the Jurisdiction and Entity levels of the Global Rule will remain Enabled after the import is complete. This is because, the Enabled/Disabled column is not cascaded to lower levels. If the intention is also to disable the Global rule at a specific Jurisdiction and Entity level, then, a row in the import that disables the Global rule at the specified Jurisdiction or Entity must be included.

If a new Jurisdiction rule is imported as disabled, the Entity levels of the Jurisdiction Rule will remain Enabled after the import is complete. This is because, the Enabled/Disabled column is not cascaded to lower levels. If the intention is also to disable the Jurisdiction rule, the specified Entity must be included.