Defining Submission Phases

Defining Submission Phases Your review process requirements may vary by period. For example, the monthly close cycle might require a single-phase review process for Balance Sheet and Profit/Loss data in January and February. For a quarterly month such as March, the quarterly closing review process may require multiple phased submission cycles for Balance Sheet and Profit/Loss data and supplemental data. Your review process requirements may also vary by scenario. For example, the Actual scenario might require only Balance Sheet and Profit/Loss accounts to be submitted for review. For the Budget scenario, all accounts might be required, and for the Forecast scenario, only Profit/Loss accounts and supplemental data might be required. You can use a maximum of nine submission phases in the review process. For example, in the  Actual scenario, scenario, you might submit submit Balance Balance Sheet Sheet and Profit/Loss Profit/Loss accounts for for review in Phase 1, 1, and supplemental data in Phase 2. In the Budget scenario, you might submit Intercompany data in Phase 1, Balance Sheet and Profit/Loss accounts in Phase 2, and supplemental data in Phase 3. You perform these tasks to set up submission phases: 



Set the application and dimension metadata attributes to use submission phases. See Defining Application Settings. Settings . o Set the UseSubmissionPhase application attribute attribute to Y. By default, the setting for submission  phases is disabled, and you must must set this attribute to to enable phased submissions submissions in the application. o Set SupportSubmissionPhas SupportSubmissionPhaseForAccounts, eForAccounts, SupportSubmissionPhaseForCustom, SupportSubmissionPhaseForCustom, or SupportSubmissionPhaseForICP SupportSubmissionPhaseF orICP attributes as required. You must define which dimensions (Account, Custom, and ICP members) are enabled for process management. For example, if the application needs submission by accounts and not for Custom or Intercompany (ICP) dimensions, you can select the SupportSubmissionPhase SupportSubmissionPhaseForAccounts ForAccounts attribute. You must enable at least one dimension. Assign validation accounts. See Defining Application Settings. Settings . The validation account is used in Process Control and for data locking. The validation account amount must be zero before data can be promoted, approved, or locked. If you do not want to use validation in Process Control or for data locking, leave the validation account blank. If you are using phased submissions, you can specify a separate validation account for each submission phase. An application can have up to nine submission phases. For applications that use  phased submissions, the Validation Validation Account setting setting identifies identifies the validation validation account for phase 1. Validation accounts 2 through 9 identify the remaining phases.





Define submission groups and assign submission groups to dimension members. See Setting Up Submission Groups. Groups. Assign submission groups to submission phases. See Assigning Submission Groups to Phases. Phases .