Rules
- This report runs for the exact dimension members selected on the report page. When a consolidation member is selected, its descendants are not processed unless specifically selected. The exception to this is the Schedule dimension. If the Schedule dimension is selected, all lines are included in the report.
- This report does not show data for consolidation units.
- In general, journal data is
displayed only if it meets the requirements for all specified members. If no data
exists for the selected data slice, the report returns
No records found that match the report specification
. An example is if the selected period is outside the effective life. - This table shows data for these journals for the currency/posting status:
Journal type | Local currency | Translated currency | ||
---|---|---|---|---|
Unposted | Posted | Unposted | Posted | |
Intercompany Eliminations | x | x | x | x |
Acquisition | x | x | x | x |
Standard | x | x | x | |
Standard PL-BS | x | x | x | |
Reversal | x | x | x | |
Ownership | x | |||
Reclassification | x | |||
Reference | x |
- If a posted web journal in
the report is unbalanced in the translated currency view, an extra row entitled
Total Credits: <amount> Total Debits: <amount> Total Difference: <amount>
is displayed. This line is not displayed in the local currency view.A web journal is displayed as unbalanced when:
- A balanced adjustment includes lines to different schedules and one of the accounts is not in the report's scope. In this case, select the missing schedule and rerun the report.
- An unbalanced adjustment includes lines that are not required to balance, such as an acquisition line. In this case, check that another journal type includes a non-acquisition line that balances the Acquisition journal adjustment. If none exists, submit a new journal or edit an existing journal to balance your entries.
- A Standard PL-BS journal is posted to multiple periods. This is expected PL-BS behavior, because balance sheet values are year-to-date, even in the periodic view. For more information, see the Infor CPM Consolidation User Guide.
- If the report requests both posted and unposted journals, a Status column displays a posted or unposted status (according to the selected data slice) of each journal. If the report requests only posted or only unposted journals, no status column displays.
- Selecting the Posted Journals check box returns only journals that posted for the selected data slice. Journals are not displayed if posted to a different data slice. For example, a journal that posted only for May has an unposted status for June. Similarly,, a journal that posted only for Euro has an unposted status for USD.
- Selecting the Unposted Journals check box returns journals that could post for the selected data slice, such as journals that are unposted or journals that are posted but not for the selected data slice.
- A journal is considered
posted for a specific period if one or more adjustments posted during a
consolidation. Consequently, there may be one or more unposted adjustments in a
posted journal. These rules apply to posted adjustments:
- Reclassification journals. The posted or unposted status is displayed for both the source and destination adjustments. If a journal is unposted, amount fields are blank. This journal data displays only for translated currency, not local currency.
- Reference journals. The posted or unposted status is displayed for destination adjustments only. If a journal is unposted, amount fields are blank. This journal data displays only for translated currency, not local currency.
- Ownership journals. The posted or unposted status is displayed for ownership units only. The posted or unposted status is also displayed for destination adjustments and source adjustments (if applicable). If a journal is unposted, amount fields are blank.
- Intercompany Elimination journals. The posted or unposted status is displayed for elimination units only. Transaction details are not associated with a posted or unposted status on the report.
- Web journals.
Individual adjustments are displayed with a posted status if the adjustment has
been posted for the selected dimension members. If at least one adjustment is
posted for the data slice, the journal status is Posted.
Values do not display for unposted adjustments for (1) translated currency (whether the journal is posted or not) or (2) local currency for a posted journal.
- Year-to-date data is not available for Intercompany Eliminations journals on a detail level. No journal data is displayed if year-to-date is selected as an option. The Reconciliation report shows the effects of year-to-date Intercompany Eliminations data on a summary level.
- If more than one journal type is included in the report, the report is sorted by journal type. Within each journal type, the report is sorted by journal name.
- For Ownership, Reference,
and Reclassification journals, the destination lines display first, followed by
the source lines.
These tables describe expected report behavior when selecting period, currency, and journal types. The tables assume journals exist for the selected data slice.
Local currency | |||
---|---|---|---|
Journal status | Amount displays | Posted adjustment | Unposted adjustment |
Unposted | x | x | |
Posted | x | ||
Posted | x | x |
- Data for unposted Ownership journal is not displayed.
- Reference and Reclassification journals do not post to local currency.
Translated currency | |||
---|---|---|---|
Journal status | Amount displays | Posted adjustment | Unposted adjustment |
Unposted | x | ||
Posted | x | ||
Posted | x | x |
- Unposted Ownership journal data is not displayed.
- For Intercompany Eliminations and Acquisition journals, an amount is displayed only if data was prepared or submitted for the selected currency.
- Journal data is displayed (except for the amount) if a Reference, Reclassification, Standard, Standard PL-BS, or reversal journal is not posted for the specified data slice.
- No journal data is displayed if an Intercompany Eliminations, Acquisition, or Ownership journal is not posted for the specified data slice.