RSS Feed
Short Text
Document splitting causes field overflow for currency type & in row &
Diagnosis
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.
Procedure
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.
Examples:
In examples Profit center is defined as a document splitting mandatory characteristic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.