Post Initialization Mappings

Multiple integration definitions enable you to manage project integrations across multiple currencies, accounting periods, and organizational boundaries. You can create multiple integration definitions by prefacing an integration definition with a different name and then associating it with a unique calendar. In this case, you also need to further define settings in each of the integration definition to identity unique values specific to the integration, such as the business unit, currency, or calendar.

For example, suppose you have set up your export business and your domestic sale business as two separate business units: "export" and "domestic sales." The "export" business unit may use accounting periods that differ from the accounting period selected for domestic sales. In this case, the administrator needs to explicitly define the entity or business unit used for the integration definition.

You can add or modify mappings by clicking next to the integration project definition file on the Integration page and then selecting Options. Then from the Edit Integration page, select the Options or Filters tab.

The following table describes the project integration definition file where you may need to define the specific settings depending on the integration definition.

Project Integration Definition Name	Mapping Requirements
Export Project	On the Filters tab, replace the "Entity" value in the Value field with the business unit associated with the specific integration definition.
Export Project Budget	On the Filters tab, replace the "Entity" value used in the predefined Org filter condition with the business unit associated with the specific integration definition. For example, if the filter condition shows: @ILvl0Descendants("OEP_Total Entity") and your business unit is "Domestic Sales" for the integration definition, replace ("OEP_Total Entity") with ("OEP_Domestic Sales").
Export Project Actuals	On the Options tab, from Period Mapping Type, select Explicit. Then from the Calendar drop-down, select the name of the source period mapping calendar used for exporting project actuals. If the Calendar field is empty, all actuals are exported provided mappings exists between EPM Planning Projects and Project Management. For more information, see Applying Source Mappings.
Import Project	On the Filters tab, specify the "Business unit" value used for the specific integration definition in the Value field. In Maximum Age of Past Projects in Days, specify the number of days to include for both active and closed projects in the integration definition. For example, if you enter a value of 10, the project includes projects finished in the last 10 days. But if you enter 365, then even a project one year old is migrated, but not older than that.
Import Project Budgets	On the Filters tab, specify the "Business unit" value used for the specific integration definition in the Value field. In Maximum Age of Past Projects in Days, if there are multiple currencies, you have the option to include past projects that are in an active status. You can do this by indicating the number of days in the past you want to include. By default, the value is considered as "0." Only projects that have the finish date today or later - and not earlier - are considered when importing. All active future ending projects are always imported.
Import Project Actuals	On the Filters tab, specify the accounting calendar name in the Value field. On the Options tab, from Period Mapping Type, select Explicit. Then from the Calendar drop-down, select the name of the source period mapping calendar used for exporting project actuals. If the Calendar field is empty, all actuals are loaded provided mappings exists between EPM Planning Projects and Project Management. For more information, see Applying Source Mappings.
Import Project Properties	On the Filters tab, specify the "Business unit" value used for the specific integration definition in the Value field. In Maximum Age of Past Projects in Days, if there are multiple currencies, you have the option to include past projects that are in an active status. You can do this by indicating the number of days in the past you want to include. By default, the value is considered as "0." Only projects that have the finish date today or later - and not earlier - are considered when importing. All active future ending projects are always imported. For example, if you enter a value of 10, the project includes projects finished in the last 10 days. But if you enter 365, then even a project one year old is migrated, but not older than that.