How To Fix GLT0004 - Document splitting causes field overflow for currency type & in row &

SAP Error Message - Details

• Message type: E = Error

• Message class: GLT0 - Split processor

• Message number: 004

• Message text: Document splitting causes field overflow for currency type & in row &

What causes this issue?

When document splitting is performed, the total of the amounts of the
base rows is very small. The split amounts are calculated by division by
the total of the amounts of the base rows. This produces very large
amounts that can in some cases extend beyond the space available in the
field.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Possible solutions:
1) Split the FI amount into multiple documents if this is possible from
the business or technical points of view.
2) Avoid running active document splitting if all of the document
splitting characteristics are present on all relevant rows.
3) Make further changes to the Customizing settings for document
splitting to change the basis of active document splitting for a row to
be split.
To 1) Multiple business processes are posted in one FI document. In this
way, all base rows of all business processes produce a very small total
that leads to the above problems when active document splitting is
performed. If each business process is posted in a separate FI document,
only the total of the base rows of the partial documents is applied.
The problem can also arise when multiple documents are posted
technically within the same logical unit of work (LUW), such as for
invoice reductions. In such cases, a possible solution would be to
distinguish these documents using the logical transaction (in the LOGVO
field) and to activate document splitting for the relevant business
transaction variant separately for each logical transaction. The
prerequisite for this is the implementation of SAP Note 1030391.
When document splitting is active, we always recommend posting just one
business transaction per FI document. This is the only way of ensuring
that the individual business processes are correctly identified and
handled in document splitting. For example, agency business can involve
supplier invoices being allocated by a central regulator to one or more
customers. For more information, see SAP Note 956161.
To 2) An active split can be avoided by using an appropriate variant
(such as standard variant 0001) for corresponding document types (or the
underlying business process) for the business transaction Unspecified
Posting (0000) or Goods Receipt for Purchase Order (0600), for example.
The variant must not contain any item categories that are to be edited
but that do not need to be split actively because the document splitting
characteristics are all present on all relevant rows.
Example: Goods Receipt for Purchase Orders:
When goods receipt for purchase orders is posted, the system generates a
price difference row and a freight row. In document splitting
(transaction: GSP_LZ2), both G/L accounts are classified as expense
accounts (item category 20000). Furthermore, document splitting is
configured so that the material rows and any other balance sheet rows
are split on the basis of the expense rows (transaction: GSP_RD). For
example, the total of the base rows (price difference row and freight
row) is between -1 and 1. When the split amounts are calculated, the
field overflows.
In the case of goods receipt for purchase orders, Materials Management
(MM) provides the posting lines complete with account assignment.
Consequently, we recommend setting business transaction 0600 Goods
Receipt for Purchase Order and business transaction variant 0001 in
transaction GSP_VZ3 of the corresponding document type (standard
document type). In this way, document splitting is not performed and the
error is avoided.
To 3) You need to ensure that the base rows do not produce a very small
total for each row to be split.
For this, you have various options, such as the following:
a) Do not define item categories as base types for the item to be edited
b) When classifying the G/L accounts, change the assignment of the item
category for the G/L account
c) Assign a different business transaction variant to the document type
or use a document type with a different business transaction variant .
This decision needs to be made on a case by case basis, and any change
made must be compatible with the overall concept.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GLT0004 - Document splitting causes field overflow for currency type & in row & ?

  The SAP error message GLT0004 indicates that there is a field overflow issue related to document splitting, specifically for currency types in a financial document. This error typically occurs when the total amount for a specific currency type exceeds the allowed limit for the field in the database.
  Cause:
  
  
  Field Overflow: The error arises when the total amount for a currency type exceeds the maximum value that can be stored in the designated field. This can happen if:
  
  The document splitting configuration is not set up correctly.
  The amounts being posted are too large for the defined field size.
  There are multiple line items that, when summed, exceed the field limit.
  
  
  
  Document Splitting Configuration: If document splitting is enabled, it may be incorrectly configured, leading to issues when trying to split documents into multiple segments.
  
  
  Currency Type Issues: The error may also be related to specific currency types that have different field sizes or limitations.
  
  
  Solution:
  
  
  Check Document Splitting Configuration:
  
  Review the document splitting settings in the Financial Accounting (FI) module. Ensure that the configuration aligns with your business requirements and that the field sizes are appropriate for the amounts being processed.
  
  
  
  Adjust Field Sizes:
  
  If possible, consider adjusting the field sizes in the database or the configuration settings to accommodate larger amounts. This may involve working with your SAP Basis team or a technical consultant.
  
  
  
  Review Line Items:
  
  Analyze the line items in the document that is causing the error. If there are unusually large amounts, consider breaking them down into smaller transactions or adjusting the amounts to fit within the limits.
  
  
  
  Check Currency Types:
  
  Ensure that the currency types being used are correctly defined and that their settings do not lead to overflow issues. This includes checking the configuration for each currency type in the system.
  
  
  
  Testing:
  
  After making adjustments, test the posting process with similar transactions to ensure that the error does not recur.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  
  Related Information:
  
  Document Splitting: This is a feature in SAP that allows for the automatic splitting of accounting documents into multiple segments based on defined criteria. It is often used for segment reporting and can be configured in the Financial Accounting module.
  Field Size Limitations: Different fields in SAP have specific size limitations based on their data types (e.g., INT, DEC). Understanding these limitations is crucial for troubleshooting overflow errors.
  SAP Community and Forums: Engaging with the SAP Community or forums can provide insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve SAP support or a technical consultant for further investigation.