Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Report Result List

1 Error Messages During Reporter Creation

1.1 Data f. g. xyz (Not Found) Group Companies) CODT Valid? (CN 0763E)

When this message appears, data (usually consolidation postings) has been found for a company that is not in the group companies. This can happen if a company was not entered in the group companies in the current period (or fact) for which consolidation postings were still present in the comparative period (or fact). The company should then at least be entered with consolidation method 'K' (No consolidation) in the group companies of the current period (or fact).

In the case of a report with the report option 'T' (for subgroup breakdown), this error message can arise because consolidation postings exist for the relevant company (attribute in CNSPST, not according to the document number) in a sub-group in which the relevant company is not contained according to the group structure (tree structure according to GRPMNR). 'Contained' is the company in the sub-group where it is displayed in the group structure and in all sub-groups just above it, including the global corporation.

2 Missing or Incorrect Values

2.1 Missing Balances and Postings

Problem: The report does not contain balances and/or postings that are present in the corresponding balance and posting applications.

Solution: There may be several causes for this problem.

  • After changing the balances or postings, the report was not recreated or an error message was not acknowledged with Ignore.
  • The account was not assigned to a position in the POSKTO application.
  • The position to which the account has been assigned is not in the report.
  • A debit/credit control has been set up for the account in the report statement/income statement and there are values that ensure that the account is not included in this position.
  • For a P+L report from cost center balances, a controlling indicator is specified for the account in the POSKTO application and a controlling object with a different indicator is specified for these values.
  • For an HBI/HBII or consolidation voucher, the processing indicator was set to 'I' for ignoring/info.
  • For a group balance sheet/income statement report, consolidation vouchers for a sub-group are marked as 'ET' (one-off sub-group) and are therefore not processed.
  • • HBI/HBII postings (application PST) are not taken into account in the group report. They do not affect a higher fact until carry forward ( PRECTOSAL).
  • The absence of consolidation postings in the capital flow report may be due to the fact that, although Group movements do exist, there are no consolidation postings with correct posting key attributes. Regardless of the exKONBUCH indicator in the fact, the capital flow report always reads the consolidation postings and never the group movements.

2.2 Incorrect Values for Consolidation Postings

Problem: The values from the consolidation postings are incorrect. In particular, consolidation postings coming from a sub-group are taken into account twice or more.

Solution: In the GRPMNR application, the affected sub-group was listed more than once as book-tk.

2.3 Incorrect Values on Position Structure Positions (P6 Rows)

Problem: In the report, positions of the position structure (P6 lines) contain incorrect values, which are usually too high.

Solution: There may be several causes for this problem.

  • If the value on the position is exactly twice as large as expected, then the total row will probably be added. The reason for this is that the total store from which the total position is filled is (also) filled in an E line of the report line description. Total storage that is filled in an E-line (i.a. Differences (assets/liabilities) may not be used elsewhere in the reporting line description - only for preparing the balance sheet profit.
  • If the item structure of any positions is located below the affected position, these are presumably not marked as "of which" positions in the item master. In this case, the Davon positions are added together like all other P1 positions.

Published:

Report Result List

1 Error Messages During Reporter Creation

1.1 Data f. g. xyz (Not Found) Group Companies) CODT Valid? (CN 0763E)

When this message appears, data (usually consolidation postings) has been found for a company that is not in the group companies. This can happen if a company was not entered in the group companies in the current period (or fact) for which consolidation postings were still present in the comparative period (or fact). The company should then at least be entered with consolidation method 'K' (No consolidation) in the group companies of the current period (or fact).

In the case of a report with the report option 'T' (for subgroup breakdown), this error message can arise because consolidation postings exist for the relevant company (attribute in CNSPST, not according to the document number) in a sub-group in which the relevant company is not contained according to the group structure (tree structure according to GRPMNR). 'Contained' is the company in the sub-group where it is displayed in the group structure and in all sub-groups just above it, including the global corporation.

2 Missing or Incorrect Values

2.1 Missing Balances and Postings

Problem: The report does not contain balances and/or postings that are present in the corresponding balance and posting applications.

Solution: There may be several causes for this problem.

  • After changing the balances or postings, the report was not recreated or an error message was not acknowledged with Ignore.
  • The account was not assigned to a position in the POSKTO application.
  • The position to which the account has been assigned is not in the report.
  • A debit/credit control has been set up for the account in the report statement/income statement and there are values that ensure that the account is not included in this position.
  • For a P+L report from cost center balances, a controlling indicator is specified for the account in the POSKTO application and a controlling object with a different indicator is specified for these values.
  • For an HBI/HBII or consolidation voucher, the processing indicator was set to 'I' for ignoring/info.
  • For a group balance sheet/income statement report, consolidation vouchers for a sub-group are marked as 'ET' (one-off sub-group) and are therefore not processed.
  • • HBI/HBII postings (application PST) are not taken into account in the group report. They do not affect a higher fact until carry forward ( PRECTOSAL).
  • The absence of consolidation postings in the capital flow report may be due to the fact that, although Group movements do exist, there are no consolidation postings with correct posting key attributes. Regardless of the exKONBUCH indicator in the fact, the capital flow report always reads the consolidation postings and never the group movements.

2.2 Incorrect Values for Consolidation Postings

Problem: The values from the consolidation postings are incorrect. In particular, consolidation postings coming from a sub-group are taken into account twice or more.

Solution: In the GRPMNR application, the affected sub-group was listed more than once as book-tk.

2.3 Incorrect Values on Position Structure Positions (P6 Rows)

Problem: In the report, positions of the position structure (P6 lines) contain incorrect values, which are usually too high.

Solution: There may be several causes for this problem.

  • If the value on the position is exactly twice as large as expected, then the total row will probably be added. The reason for this is that the total store from which the total position is filled is (also) filled in an E line of the report line description. Total storage that is filled in an E-line (i.a. Differences (assets/liabilities) may not be used elsewhere in the reporting line description - only for preparing the balance sheet profit.
  • If the item structure of any positions is located below the affected position, these are presumably not marked as "of which" positions in the item master. In this case, the Davon positions are added together like all other P1 positions.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk