Skip to content

Submission rules page

Admin

Application database > Processes tile > select process > > Process setup > (Data Entry & Submission Rules section) > Submit >

Application database > Navigation Panel > Processes & Workflows > Process > > Process definition > (Data Entry & Submission Rules section) > Submit >

Purpose of the page

This page allows you to set overrides on the following default elements:

  • data submission rules
  • data rejection rules
  • rules for locking data editability in the rejection step
  • default overrides for the incorrect data submission

Page sections

Section Description
Submission Defines specific behaviours for the data processing run on submission and for how to purge submission tables, run diagnostics on steps prior to the submitted step, and store diagnostic data offline.
Lock data Defines the method that the system uses to make data that contributed to the submission of an entity or journal no longer editable, even if rejected. The origin is no longer manual and users must input new data to leave a trace of the corrections made.
Reject Defines specific behaviour for performing rejections.
Override submission Defines submission overrides.

Fields in the Submission section

Element Description
Run data processing on submission Allows you to run all data processing enabled on the process automatically in the submission launch step (with the exception of cash flow planning and closing).
Exclude Other calculation logics from the data processing on submission Only with Run data processing on submission selected. Allows you to exclude all Other logics enabled on the process automatically in the submission launch step.
Also includes the stored procedure Only with Run data processing on submission selected. Allows you to choose a previously defined procedure (stored procedure) to be run automatically in the submission launch step, together with the other data processing. The system only uses procedures with names starting with the suffix CPM_SP_. Moreover, to allow the stored procedure to read the submission parameters, they must be named as follows: - PROCESS: data collection process - ENTITY_HIERARCHY: organisational hierarchy process - STEP_LIST: list of steps - ORIGINAL_SCENARIO_PERIOD_LIST: list of original scenarios/periods - ENTITY_LIST: list of entities - CONTRIBUTOR_NODE_LIST: list of contributor nodes - CONSOLIDATOR_NODE_LIST: list of consolidator nodes
Exclude Purge submission tables Makes the carry forward of submission information, in the entity deployment step, following changes to the process’s organisational hierarchy, optional.
Diagnose all the steps before the submitted step Allows you to check for errors in both submitted and non-submitted previous steps when running the submission of a step.
Store diagnostic result on submission Allows you to save a PDF report with the diagnostic results when the submission of an entity is complete.

Fields in the Lock data section

Element Description
With manual origin on the Journals submission Places the SUB_ prefix before the original origin on the journal rows with manual origin that have been submitted.
Calculation on journal submission Places the SUB_ prefix before the original origin on the journal rows that have been calculated by the calculated accounts data processing and submitted.
With manual origin on the submission of the entities/nodes Places the SUB_ prefix before the original origin on the (gross and intercompany) amount rows and manual journal when submitting the entity.
With calculation origin on the submission of the entities/nodes Places the SUB_ prefix before the original origin on the (gross and intercompany) amount rows and journals generated by the calculated accounts data processing when submitting the entity.

Fields in the Rejection section

Element Description
Mandatory notes Makes it mandatory to insert explanatory notes to be able to run the rejection of an entity’s data.
Mandatory reason Makes it mandatory to select a rejection reason to be able to run the rejection of an entity’s data.
User enabled for Journals rejection Defines the user responsible for the rejection of an entity’s journals.

Fields in the Override submission section

Element Description
By user Allows authorised users to submit the step even if there are blocking errors. See User lists.
With authorization of blocking errors Allows you to submit the step, even if there are blocking diagnostic errors, provided they have been authorised. The Enable detected errors trace option must be enabled in the validation rules (see Diagnostic Rules page). Errors with Blocking severity that have been authorised will be renamed Authorized blocking.

Buttons and/or links on the page

Element Description
Execution plan of jobs to run on submission and rejection Opens a page to create and relate jobs to steps of the process. See Execution plan of jobs to run on submission and rejection page.