SAP Knowledge Base Article - Public

3585370 - Document splitting: Business transaction SKIP

Symptom

The document splitting function of General Ledger Accounting uses the the business transaction "SKIP" with variant 0001 instead of the business transaction variant assigned to the document type.

It is thus sometimes possible to post documents that contain no document line items with a mandatory item category for the originally assigned business transaction, such as a customer invoice without a customer. No document splitting rules are processed.

Environment

SAP S/4HANA Cloud Public Edition

Cause

The originally assigned business transaction variant is not 0000/0001 (unspecified posting).

The entered document does not post to any mandatory item categories or even to any item category to be processed in accordance with Customizing for the splitting rules defined for the originally assigned business transaction variant.

The entered document can also contain item categories to be processed, but only if they are split on a process-based basis (using a clearing or an invoice reference). 

No rule-based splitting is processed for such documents. The check for mandatory item categories is part of rule-based splitting.


If Customizing is not appropriate - that is, if the assigned document splitting rule does not make any provision for processing an item category to which postings were made in the document, SKIP is used as the fallback.

In this case, no rules are processed; instead, the system checks whether the document is already completely assigned without the rule-based split and can thus be posted.


A document can be posted without rule-based splitting if the required-entry document splitting fields have already been completely assigned in the data entry view or if they can be filled through process-oriented splitting (for example, in the case of clearing documents from the items for clearing) or inheritance (if the use of inheritance or constants is allowed in the Customizing of the original business transaction variant).

If Customizing is correct (if there is an appropriate assignment of business transaction variants and if these variants are used properly with regard to posting), SKIP is not used. 

Resolution

The program behavior works as intended. However, it conceals inappropriate usage of document type with regard to document splitting-based business transaction analysis since it enables the posting of documents that would not be able to be posted if the specified Customizing entries were considered exclusively.

Check the Document type used and Business transaction assigned to same with purpose in the help documentation.

See:

See Also

2814950 - GLT2001 - Item category &1 not allowed in accounting transaction &2/&3 

Keywords

KBA , FI-GL-FL-2CL , Flexible Structures (Public Cloud) , How To

Product

SAP S/4HANA Cloud Public Edition all versions