Fixing or Hiding of Subassignments
The financial statement items you post manually sometimes require a breakdown by subassignments, depending on the breakdown category. When you enter documents with many items and subassignments, document entry can become very confusing.
For this reason, document type Customizing provides the option of fixing or hiding each subassignment during document entry.
Features
Fixing a Subassignment (Permanently or Temporarily)
A fixed subassignment means that the subassignment must be unique for each posting, and thus can only have one fixed value.
A fixed subassignment can either be permanent or temporary. When you fix a subassignment temporarily, you can deactivate the fixing when entering the document.
Example
You may want to fix the subassignment transaction currency
temporarily or permanently if you normally only enter documents in transaction currency. By making the transaction currency subassignment fixed, you prevent two different transaction currencies from being entered inadvertently.
The fixed subassignments are displayed when a document is entered. The system shows the non-fixed characteristics for each document line item.
Hiding a Subassignment
You can hide subassignments that only apply to very few financial statement items.
The system only shows a hidden subassignment in a posting when you enter an item in the document line that is broken down by that subassignment.
Report for Consistency Check for Manual Document Types
If you make changes to the data model after you have created document types for manual postings, this can result in inconsistencies in the control of document fields for the document types. The system eliminates these inconsistencies when a data collection task is run to which you assigned the inconsistent document type for posting documents. If, when you execute the task, the system identifies this type of inconsistency in the Customizing settings for a document type, the system attempts to correct this inconsistency automatically. Where applicable, a message is also displayed requesting you to save the changes.
To prevent this message from appearing, you can execute report UCUMD_REPAIR_DOCTYPE_FIELDOPT
. This report checks manual document types for these inconsistencies. When you execute the report in the update run, it eliminates any inconsistencies found.
Recommendation
We recommend that you always execute the report whenever you have made changes to the data model.
Before you execute the report, specify the consolidation area in the global parameters. The report only ever checks the manual document types for this consolidation area that you specified in the global parameters.