How To Fix G06036 - Migration doc. type &1 is assigned to an activity/accounting technique

G06036 - Overview

• Message type: E = Error

• Message class: G06 - SAP Cons - Error Message re. Consolidation of Investments

• Message number: 036

• Message text: Migration doc. type &1 is assigned to an activity/accounting technique

What causes this issue?

You are running the migration of statistical postings with document type
&V1&. However, this document type is assigned to one or more activities
or accounting techniques.

System Response

Cannot perform the migration.

How to fix this error?

For migrating statistical postings of consolidation of investments, use
a document type that is not assigned to another task.
Note that for use with automatic postings, the migration document type
needs to use posting level 30 (consolidation entries) and business
application 6 (consolidation of investments).

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G06036 - Migration doc. type &1 is assigned to an activity/accounting technique ?

  The SAP error message G06036 indicates that a migration document type is assigned to an activity or accounting technique that is not compatible with the current operation you are trying to perform. This typically occurs during the migration of financial data or when trying to post documents in the system.
  
  Cause:
  
  Document Type Assignment: The migration document type you are using is linked to a specific activity or accounting technique that does not allow the operation you are attempting.
  
  Configuration Issues: There may be configuration settings in the SAP system that are not aligned with the document type being used.
  Incompatibility: The document type may be set up for a different purpose (e.g., for internal postings rather than external transactions).
  
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for document types in SAP (Transaction Code: OBA7).
  Verify the settings for the migration document type in question and ensure it is correctly configured for the intended use.
  
  
  
  Review