Do you have any question about this error?
Message type: E = Error
Message class: FISA_LOC - FI Localization for KSA
Message number: 121
Message text: G/L account assigned to exp.order and settlement document are different
G/L account assigned to the expenditure order and settlement document
are not the same.
The system does not allow you to settle the expenditure order.
Assign a settlement document with the same G/L account.
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.
FISA_LOC121
- G/L account assigned to exp.order and settlement document are different ?The SAP error message FISA_LOC121 indicates that there is a mismatch between the General Ledger (G/L) account assigned to an expense order and the G/L account associated with the settlement document. This typically occurs during the settlement process in SAP, particularly in the context of internal orders or projects.
Cause:
- G/L Account Configuration: The G/L account assigned to the expense order may not match the G/L account that is being used in the settlement document. This can happen if the expense order is configured to use a different G/L account than what is defined in the settlement rules.
- Settlement Profile: The settlement profile assigned to the order may not be correctly set up to allow for the intended G/L account.
- Master Data Issues: There may be inconsistencies in the master data for the expense order or the G/L accounts involved.
- Transaction Type: The transaction type used for the expense order may not be compatible with the G/L account used in the settlement.
Solution:
Check G/L Account Assignment:
- Review the G/L account assigned to the expense order. Ensure that it is correctly configured and matches the intended account for settlement.
- You can check this in the internal order master data (transaction code: KO03).
Review Settlement Profile:
- Verify the settlement profile assigned to the expense order. Ensure that it is set up to use the correct G/L accounts for settlement.
- You can check the settlement profile settings in the configuration (transaction code: OKO7).
Adjust Master Data:
- If there are discrepancies in the master data, update the expense order or G/L account settings as necessary to ensure consistency.
Check Transaction Types:
- Ensure that the transaction types used for the expense order and the settlement document are compatible. You may need to adjust the configuration if there are mismatches.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific guidance related to your organization's configuration.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP Financials for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FISA_LOC120
Settlement number not found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FISA_LOC119
Settlement number already used in expenditure order &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FISA_LOC150
Approve or reject expenditure order
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FISA_LOC151
Approve or reject payment order
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.