Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.
Message number: 673
Message text: No contract account or G/L account in service provider agreement
Neither a contract account or a general ledger account is defined in the
service provider agreement between &V1& and &V2.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Maintain the corresponding service provider agreement.
Error message extract from SAP system. Copyright SAP SE.
EDEREG_INV673
- No contract account or G/L account in service provider agreement ?The SAP error message EDEREG_INV673 indicates that there is no contract account or general ledger (G/L) account associated with the service provider agreement in the system. This error typically arises in the context of billing or invoicing processes, particularly in the utilities or service industries where service provider agreements are common.
Cause:
- Missing Configuration: The service provider agreement may not be properly configured in the system, leading to the absence of a contract account or G/L account.
- Incorrect Data Entry: There may be a data entry error when creating or maintaining the service provider agreement, resulting in missing or incorrect account assignments.
- Inactive or Deleted Accounts: The contract account or G/L account may have been deactivated or deleted, which would prevent the system from finding a valid account.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the contract account or G/L account.
Solution:
Check Service Provider Agreement: Review the service provider agreement in the SAP system to ensure that it is correctly configured with the appropriate contract account and G/L account.
- Navigate to the relevant transaction (e.g.,
EEDM
for service provider agreements) and verify the details.Maintain Contract Accounts: If the contract account is missing, you may need to create or assign a valid contract account to the service provider agreement.
- Use transaction codes like
FD32
(for customer master) orOBY6
(for G/L account) to maintain the necessary accounts.Review G/L Account Settings: Ensure that the G/L account is active and correctly set up in the system.
- Check the account settings in the chart of accounts and ensure it is not marked for deletion or inactive.
User Authorizations: Verify that the user has the necessary authorizations to access the contract account and G/L account. If not, work with your SAP security team to grant the required permissions.
Consult Documentation: Refer to SAP documentation or help resources for specific configuration steps related to service provider agreements and account assignments.
Testing: After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
EEDM
, FD32
, OBY6
, and others that may be used for managing service provider agreements and accounts.By addressing the underlying causes and ensuring proper configuration, you should be able to resolve the EDEREG_INV673 error effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
EDEREG_INV672
Internal error: Incorrect field content within a row
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Procedure for System Adminis...
EDEREG_INV671
G/L account or contract account for bill category &1 not maintained
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Procedure for System Adminis...
EDEREG_INV674
Contract account and G/L account in service provider agreement
What causes this issue? Both a contract account and a general ledger account are defined in the service provider agreement between &V1& and &...
EDEREG_INV675
Point of delivery is not identified
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.