How To Fix EDEREG_REV104 - Aggregated document number &1 not transferred to individual records


SAP Error Message - Details

  • Message type: E = Error

  • Message class: EDEREG_REV - Error Messages for Reversals in the Deregulated Environment

  • Message number: 104

  • Message text: Aggregated document number &1 not transferred to individual records

  • Show details Hide details
  • What causes this issue?

    With the Reverse Aggregated Posting for Service Provider with Tax
    (ETHI_TAXREV) transaction, it is not yet possible to transfer the
    document number of the aggregated bill to the individual records of
    table DFKKTHI.

    System Response

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

    How to fix this error?

    If you generally transfer the document number to table DFKKTHI, you must
    execute the <LS>Aggregated Posting for Service Provider with Tax</>
    transaction (ETHIM_TAX) after reversal using the <LS>Transfer Document
    Number of Aggregated Bill Document</> variant.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message EDEREG_REV104 - Aggregated document number &1 not transferred to individual records ?

    The SAP error message EDEREG_REV104 indicates that an aggregated document number (usually related to financial documents or entries) was not successfully transferred to individual records. This error typically arises in the context of document processing, especially when dealing with aggregated data that needs to be broken down into individual entries for further processing or reporting.

    Cause:

    1. Data Aggregation Issues: The aggregated document may not have been properly created or may not contain the necessary details to be split into individual records.
    2. Configuration Errors: There may be configuration issues in the system settings related to document processing or aggregation.
    3. Missing Data: Individual records may be missing required fields or data that are necessary for the transfer process.
    4. Authorization Issues: The user may not have the necessary permissions to access or process the aggregated document.
    5. System Bugs: There could be bugs or issues in the SAP system that prevent the proper handling of aggregated documents.

    Solution:

    1. Check Document Creation: Verify that the aggregated document was created correctly and contains all necessary information. Ensure that the document is complete and valid.
    2. Review Configuration: Check the configuration settings related to document aggregation and processing in the SAP system. Ensure that they are set up correctly.
    3. Validate Data: Ensure that all individual records have the required fields filled out. You may need to check for missing or incorrect data entries.
    4. User Permissions: Confirm that the user has the appropriate authorizations to access and process the aggregated document.
    5. System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
    6. SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or patches that address this specific error message. There may be known issues or fixes available.
    7. Testing: If possible, try to replicate the issue in a test environment to better understand the conditions that lead to the error.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as FB03 (Display Document), FBV0 (Park Document), or FBL1N (Vendor Line Item Display).
    • Documentation: Refer to SAP documentation or help files related to document processing and aggregation for more detailed guidance.
    • Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.

    If the issue persists after following these steps, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant