Do you have any question about this error?
Message type: E = Error
Message class: FARR_RAI - Revenue Accounting Item
Message number: 647
Message text: Legacy data merged in contract &1
In the initial load processing of revenue accounting items, contract
attributes provided in legacy data are moved to corresponding attributes
of a contract. This is done by overwriting values determined during
processing by BRFplus. At transition however, contract attributes
provided in legacy data are only taken over if no corresponding
attribute was already determined during processing by BRFplus. Legacy
data is no longer considered if the revenue accounting item is processed
again in ordinary processing due to changes.
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.
FARR_RAI647
- Legacy data merged in contract &1 ?The SAP error message FARR_RAI647 indicates that there is a problem with legacy data being merged into a contract in the SAP system. This typically occurs in the context of contract management, particularly when dealing with contracts that have been migrated from a legacy system into SAP.
Cause:
The error message is triggered when the system detects that there are inconsistencies or conflicts between the legacy data and the current contract data. This can happen due to various reasons, such as:
- Data Migration Issues: During the migration process, if the legacy data was not properly formatted or validated, it could lead to conflicts.
- Duplicate Entries: If there are duplicate entries in the legacy data that conflict with existing contract data.
- Inconsistent Data: Differences in data formats, types, or values that do not align with the current contract structure in SAP.
- Missing Required Fields: If the legacy data does not contain all the necessary fields required by the SAP contract structure.
Solution:
To resolve the error, you can take the following steps:
- Review the Contract Data: Check the contract associated with the error message to identify any discrepancies or issues with the legacy data.
- Validate Legacy Data: Ensure that the legacy data being merged is complete, consistent, and correctly formatted. This may involve:
- Checking for duplicate entries.
- Ensuring all required fields are populated.
- Verifying that data types and formats match SAP requirements.
- Data Cleansing: If inconsistencies are found, clean the legacy data before attempting to merge it again. This may involve removing duplicates, correcting data formats, or filling in missing information.
- Re-run the Migration Process: After making the necessary corrections, re-run the data migration process to see if the error persists.
- Consult SAP Documentation: Refer to SAP documentation or support resources for specific guidelines on handling legacy data and contracts.
- Engage SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FARR_RAI646
Legacy data merged in performance obligation &1
What causes this issue? In the initial load processing of revenue accounting items, performance obligation attributes provided in legacy data are mov...
FARR_RAI645
New performance obligation &1 created for contract &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_RAI648
No acct. principle in status 'Migration' found for selection criteria
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_RAI649
No items processed; see log for details
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.