Do you have any question about this error?
Message type: E = Error
Message class: FISA_LOC - FI Localization for KSA
Message number: 518
Message text: General ledger account not assigned to the custody type
You have not assigned a general ledger (G/L) account to the custody
type.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Assign G/L accounts to custody types in Customizing for <ZK>Financial
Accounting (New)</> under <ZK>Accounts Receivable and Accounts Payable
-> Business Transactions -> Country-Specific Settings -> Saudi Arabia ->
Advance Payment -> Assign G/L Accounts to Custody Types</>.
Error message extract from SAP system. Copyright SAP SE.
FISA_LOC518
- General ledger account not assigned to the custody type ?The SAP error message FISA_LOC518 indicates that a general ledger (G/L) account is not assigned to the specified custody type in the system. This error typically arises in the context of financial accounting and asset management, particularly when dealing with custody accounts in SAP.
Cause:
The error occurs when:
- A transaction is attempted that requires a G/L account to be linked to a specific custody type, but no such assignment exists in the system.
- The configuration for the custody type in the system is incomplete or incorrect.
- The G/L account being used is not set up to handle the specific custody type.
Solution:
To resolve the FISA_LOC518 error, follow these steps:
Check Custody Type Configuration:
- Navigate to the configuration settings for custody types in SAP.
- Ensure that the custody type you are working with is properly configured and that it has the necessary G/L accounts assigned.
Assign G/L Account to Custody Type:
- Go to the transaction code OBYC (or the relevant configuration path) to access the settings for automatic postings.
- Look for the relevant settings for the custody type and ensure that the appropriate G/L accounts are assigned.
- If the G/L account is missing, add the correct G/L account to the custody type.
Check G/L Account Settings:
- Verify that the G/L account you are trying to use is active and correctly set up in the system.
- Ensure that the account is not blocked or restricted for the type of transaction you are attempting.
Test the Configuration:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Consult Documentation:
- If you are unsure about the correct G/L accounts or custody types, refer to your organization's financial accounting documentation or consult with your SAP functional consultant.
Related Information:
Transaction Codes:
SAP Notes and Documentation:
User Roles and Authorizations:
By following these steps, you should be able to resolve the FISA_LOC518 error and ensure that your G/L accounts are correctly assigned to the appropriate custody types in SAP.
Get instant SAP help. Start your 7-day free trial now.
FISA_LOC516
Expenditure order is not approved
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FISA_LOC515
Payment already done for this 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_LOC519
No advance payment data in the header
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FISA_LOC520
Expenditure order 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...
Click on this link to search all SAP messages.