Do you have any question about this error?
Message type: E = Error
Message class: EQ - Cross-IS-U functions
Message number: 124
Message text: Contract &1 for the business partner item does not have a move-in date
Contract &V1& does not contain a move-in date. This contract should not
therefore be used as a contract reference when entering an accounting
document.
Document &V2& cannot be reversed because contract &V1&, to which the
document is assigned, does not have a move-in date.
The basic setting for IS-U (utilities industry) does not allow
accounting documents to be entered for a contract (contract reference),
which does not have a move-in date.
Contact your system administrator to change the settings for this error
message.
If the setting has been changed for this error message, you must ensure
that all items that have been entered for this contract have been
reversed. All items with this contract reference must be cleared.
Documents that were transferred using transaction FP40 (Transfer Items)
from a contract <ZH>A</> to a different contract <ZH>B</> must be
reversed if the move-out is to be reversed for contract <ZH>B</>. A new
transfer from contract <ZH>B</> to contract <ZH>A</> means that
following the reversal of the move-in for contract <ZH>B</>, you can no
longer reverse the transfer.
INCLUDE FICA_NA_CUST_1 OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
EQ124
- Contract &1 for the business partner item does not have a move-in date ?The SAP error message EQ124 indicates that there is a missing move-in date for a business partner item in a contract. This error typically occurs in the context of SAP's Real Estate Management (RE) or Contract Management modules, where contracts are associated with business partners (customers, vendors, etc.) and their respective items.
Cause:
The error arises when:
- A contract is created or modified, and the associated business partner item does not have a move-in date specified.
- The system requires a move-in date for processing the contract, and its absence prevents the transaction from being completed.
Solution:
To resolve the EQ124 error, you can take the following steps:
Check the Business Partner Item:
- Navigate to the business partner master data associated with the contract.
- Ensure that the relevant business partner item has a move-in date specified.
Update the Move-In Date:
- If the move-in date is missing, you can add it by editing the business partner item.
- Go to the transaction for maintaining business partner data (e.g., transaction code BP).
- Locate the relevant business partner and item, and enter the required move-in date.
Review Contract Settings:
- Ensure that the contract settings are correctly configured to require a move-in date.
- Check if there are any specific validation rules or settings in the contract type that might be enforcing this requirement.
Test the Changes:
- After updating the move-in date, try to execute the transaction again that triggered the EQ124 error.
- Verify that the error no longer appears and that the contract can be processed successfully.
Related Information:
Transaction Codes:
Documentation:
User Roles:
Consulting SAP Notes:
By following these steps, you should be able to resolve the EQ124 error and ensure that the business partner item has the necessary move-in date for contract processing.
Get instant SAP help. Start your 7-day free trial now.
EQ123
Object was noted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EQ122
Children can only be created below the initial object
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EQ125
No installation was found for premise &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EQ126
No contract was found for premise &1
What causes this issue? You have attempted to create a move-out for premise &V1&. No contracts suitable for move-out could be found for this ...
Click on this link to search all SAP messages.