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 |
|---|---|
| Submit | 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 the 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). |
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 reason | Makes it mandatory to select a rejection reason to be able to reject an entity’s data. |
Fields in the Override submission section
| Element | Description |
|---|---|
| By user | Allows authorised users to submit the step even if there are blocking errors. See . |
| With authorization of blocking errors | Allows you to submit the step, even if there are blocking diagnostic errors, provided they have been authorised. In the validation rules, the Enable detected errors trace must be enabled (see Diagnostic Rules page). Authorised errors with Blockingseverity will be renamed Authorised blocking. |