
1. Defining Custom Document Types
Document Types can be defined in SAP GUI under the Master Data section. There are separate transactions depending on the nature of the Document you wish to configure, including for automatic tasks or manual postings.
E.g. A custom Doc Type for an elimination method would be defined under ‘Define Document Types for Reclassification in Consolidation Monitor’.
In this scenario, we will use the app Define Document Types for Manual Posting in Consolidation Monitor.
When creating a new Document, you can specify an ID, description plus other specific characteristics. In our context, we will create a Doc Type at Posting level 30 with a Business Application of ‘Other’ from the list of options. Under Posting, select the ‘Manual’ option and under Currencies specify ‘Group Currency’ only (Note that LC would be enabled for manual adjustments at PL10).
In the subsequent tab ‘Number Ranges/Auto Reversal’, we specify the version-specific ‘Document Number’ range 30 to be posted against with this document. Here, you could also select the document to auto-reverse in subsequent year if desired.
2. Assigning Custom Document Types to tasks
To be able to use this custom document, it first needs assigning to the relevant task. This can be done in ‘Define Tasks for Manual Posting’ under Data Collection for Consolidation.
For this scenario, we want to assign the custom document types to PL30 for Group adjustments (i.e. pre-delivered Task 2150). However, if you were creating a custom document type for manual local adjustments it would be assigned to PL10 (task 1095), and similarly to PL20 for manual eliminations (task 2050).
Under ‘Document type assignment’, we want to create a new entry for our Custom Document type which is active from a specified Fiscal Year & Period.
You will now be able to post to this custom document type via the ‘Post Group Journals’ or ‘Import Group Journal Entries’ apps.
3. Combining Document Types during BCF
Suppose, the company therefore no longer needed the extra document and wanted to merge Z1 with Doc Type 32 from FY26 and into the future. This can be done under Balance Carryforward within Define Balance Carryforward Settings.
Under ‘Define Destination Version’, you would need to specify this behaviour for each Fiscal Year where it applies. For instance, if you had a restatement version ‘R10’ that you wanted to automatically carry into Y10 in every year from 2025-35, you need to specify each year individually:
However, under ‘Define Destination Document Type’, you need to only specify a start and end year for the behaviour. In our example, where we want historical adjustments under Z1 to Carryforward to Document Type 32 form FY26 onwards, this would be configured as per the screenshots below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 | |
1 |