Do you have any question about this error?
Message type: E = Error
Message class: GL - FI-SL Rollup
Message number: 327
Message text: Rolling up from global to local ledgers only with fixed company code
You are trying to roll up data from a global leder to a local ledger.
You can only do so if you roll up the data to a fixed company code.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enter a rollup substitution activity in the field movement; this
substitution activity is used to define a fixed receiver company code.
Error message extract from SAP system. Copyright SAP SE.
GL327
- Rolling up from global to local ledgers only with fixed company code ?The SAP error message GL327 typically occurs in the context of financial accounting when there is an issue with the rolling up of data from global ledgers to local ledgers, particularly when dealing with fixed company codes. This error can arise due to various reasons, and understanding the cause and potential solutions is essential for resolving it.
Cause of GL327 Error
Configuration Issues: The error may stem from incorrect configuration settings in the SAP system, particularly in the Financial Accounting (FI) module. This includes settings related to the ledgers, company codes, and their relationships.
Data Inconsistencies: There may be inconsistencies or discrepancies in the data between the global and local ledgers. This can happen if transactions are not properly recorded or if there are missing entries.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to perform the rolling up of data between ledgers.
System Limitations: The SAP system may have limitations or restrictions on how data can be rolled up, especially if certain configurations are not aligned.
Solutions to GL327 Error
Check Configuration Settings:
- Review the configuration settings for the ledgers and company codes in the SAP system. Ensure that the global and local ledgers are correctly defined and linked.
- Verify that the settings for the fixed company code are correctly configured.
Data Validation:
- Perform a thorough check of the data in both the global and local ledgers. Look for any missing or inconsistent entries that could be causing the issue.
- Use transaction codes like FB03 (Display Document) to review specific entries and ensure they are correctly posted.
Authorization Check:
- Ensure that the user attempting to perform the rolling up has the necessary authorizations. This can be checked in the user roles and profiles.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address the GL327 error. There may be patches or updates that can resolve the issue.
System Logs:
- Review system logs for any additional error messages or warnings that may provide more context about the issue. Use transaction code SLG1 to access the application log.
Testing in a Sandbox:
- If possible, replicate the issue in a sandbox environment to test potential solutions without affecting the production system.
Contact SAP Support:
- If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error and the steps taken to troubleshoot.
Related Information
By following these steps, you should be able to identify the cause of the GL327 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
GL326
Error when updating a record in table &
What causes this issue? Since the name of the accessed form routine &V1&_USER_EXIT in program SAPFGLRU is determined from the user exit name ...
GL325
Receiver ledger & stores ledger currency &, but sender & stores &
What causes this issue? The ledger currency is stored in the sender and receiver ledger, but has different units in these ledgers, so that a rollup w...
GL328
Create fiscal year variant &
What causes this issue? The fiscal year variant &V1& assigned to the combination of company code or global company and ledger does not exist....
GL329
Fiscal year variant & has &, & however & periods per fiscal year
What causes this issue? The number of posting periods per fiscal year is different for the receiver and the sender. Only the posting periods should ...
Click on this link to search all SAP messages.