Symptom
This document contains answers to frequently asked questions concerning the migration object ‘Real estate contract’.
Environment
SAP S/4HANA Cloud Public Edition
Resolution
1. How to resolve error messages DMC_RT_MSG 231, DMC_RT_MSG 39, DMC_RT_MSG 41:
1.1
- System error occurs when calling function module in target system DMC_RT_MSG 231
- System error (portion 0000000001, conversion object Z_RE_CONTR_2_XXX, at &) DMC_RT_MSG 39
- Statement MESSAGE_E is not allowed with this status. (conversion object Z_RE_CONTR_2_XXX) DMC_RT_MSG 41
The issue is with the character length of the term number. The template supports 4 characters. Since it is a key field in some sections, the API relies on it's correctness for further processing. Please note, this is applicable to all the sections where term number is expected (Posting, Frequency, Org Assignment, Condition - in case you assign a term, Adjustment, Reporting Rule, Sales Rule, Sales Rule - Frequency).
Also note that the Org assignment term number must remain empty in any case.
OR
If the above error is shown, validate if the CoCode utilized is for an entity with 'IN' country assignment. The Real Estate Contract Migration Object is not localized for India - consequently cannot be utilized in this scenario. Consider utilizing the 'Manage Contract' app to load the contract metadata.
1.2
- System error occurs when calling function module in target system DMC_RT_MSG 231
- System error (portion 0000000001, conversion object Z_RE_CONTR_2_XXX, at &) DMC_RT_MSG 39
- An RAP contract has been violated. (conversion object Z_RE_CONTR_2_XXX) DMC_RT_MSG 41
If 'Renewal term' tab is used ensure that the sequence number utilized is being maintained in SSCUI 103843 - Renewal Rules.
OR
If <Standard> terms are used, the validity date fields should be left empty - maintaining the fields will lead to the above error, while the contract will still be created and the dates corrected to their default unlimited configuration.
OR
If the 'Notice Term' tab is used and a notice rule shall contain multiple sequence entries, ensure that the sequence numbering starts with 1 and is continuous.
2. How is the 'Old Contract' field be used during the migration?
The value from the key field 'Contract ID' in the migration template is automatically transferred to the field 'Old Contract' during the migration. The 'Old Contract' field is used to check whether the contract to be migrated already exists in the system.
3. How to resolve error message RETMFI 014?
- Postings: business partner <BP number> is not found in the partner assignment RETMFI 014
For solution see KBA 3463495
4. How to migrate tax-exempt contract?
In the migration template, fields Tax Type and Tax Group on tab 'Posting Term' are mandatory and must be filled, but tax exempt contracts do not have these fields assigned in the relevant configuration.
To circumvent the current setup:
Do not maintain the Posting Term tab via the migration file in case contract type is marked with tax exempt checkmark in the relevant configuration.
This will set the business partner in the default posting term to the main business partner.
If the other fields of the posting rule such as house bank are necessary to be filled, the following options can be used:
- API call after the migration to fill the missing fields, see Overview | Real Estate Contracts | SAP Business Accelerator Hub for more details.
- BAdI BADI_RECN_CONTRACT_SUBSTITUTE to add the missing fields - see also Business Add-Ins for Contract and Lease Management - SAP Help Portal
- RPA framework to fill the missing fields.
- Fill the fields manually on the contract.
OR
Create a tax group with tax exempt status and assign a dummy tax code (0%) to it. Then maintain the 'Posting Term' tab with the newly created tax type and tax group fields. This enables entering other field values via the migration template.
5. Encounter error RECAAP010 - 'No number was entered (despite external number assignment)'
This error is presented when External numbering is maintained for the migrated contract type. In the scope of the Real Estate Contract migration object, external numbering for contract numbers cannot be utilized. Contracts with external numbering requirements need to be created manually, or external numbering indicator turned off in SSCUI 103860 - Number Range for Contracts.
See Also
Keywords
real estate contract, migration, real estate migration, SIF_RE_CONTR_2, tax exempt, tax-exempt, Y-NONE, Tax group, DMC_RT_MSG 231, DMC_RT_MSG 39, DMC_RT_MSG 41, lease contract migration, RECAAP010, external numbering, notice term sequence , KBA , RE-FX-CN-2CL , Contract (Public Cloud) , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , RE-FX-2CL , Flexible Real Estate Management (Public Cloud) , RE-FX-LC-IN , India , Problem
SAP Knowledge Base Article - Public