This is a basic example with simplified chart of consolidations focusing on data entry of a balanced balance sheet with minimum number of items with the goal of producing a group balance sheet after translation which will be shown in subsequent pages. All expamples are hypothetical and don't necessarily reflect real business transactions but rather are shown to illustrate concepts of consolidation.
Right-clicking on the node between the task and the unit starts the processing in the monitor. This is similar to the way the monitor is being used in other UI's. After becoming familiar with effects of the task in the test mode, now is the turn for the 'update' mode which has the potential of writing the records to the permanent storage.
This screen is the intermediate step between the task and the actual form in which data can be written, checked, and eventually saved. It shows how the data stream (Totals Records) contains the layout group and layout itself, the part of which is the customizable form which is the actual template for entering balances for each consolidation entity. This example is for the manual input, but this step is identical (except for the actual icon) to the upload one. Once the pencil and page icon is clicked the actual form will display.
This customized form shows the values for company codes (if the top node was selected). It also shows the items where credit sign is shown at the end of the item. The nesting is for subassignment by partner unit and there are separate columns for transaction currencies (USD and EUR).
The Input Form can be customized to show totals for all the items. This is a quick form of validating that all balances on both debit and credit side net to 0. This can be done in test as well as in the update mode.
Including breakdowns (subassignments or roughly equivalent of the coding block) allows for using subtotals and shows how the values are rolled up.
It should be obvious, but it is worth reminding. When moving from one entity to another without saving, before the user leaves the entry form entirely, he or she will be warned that the input is lost, so here is the last opportunity to save the work.
The input (selection) screen comes with the blank "Reporting Logic" dropdown and it will error out unless there is a value selected. Otherwise no additional inputs are required to view the trial balance as per the underlying InfoCube.
Trial Balance output is not configured by default, but with few layout adjustments lends itself to further analysis and can be exported to Excel (out of the box) and PDF (after additional webdynpro activations)
The final screen shows the successful status of the data entry task which allows further closing activities like reconciliations, approvals, and sign-offs.