Scribd Logo
Upload

Welcome to Scribd!

  • 752 views

    Invoice Split Criteria in Billing Document

    Uploaded by

    Mirko
    This document discusses invoice splitting in billing documents. It identifies potential causes of invoice splitting as explicit settings in customizing, different header partners, different header fields, or equating billing dates in a data transfer routine. It provides solutions such as checking customizing settings, comparing header partner and field values, and entering billing dates to avoid unwanted splits due to date.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Invoice Split Criteria in Billing Document

    Uploaded by

    Mirko
    752 views2 pages
    This document discusses invoice splitting in billing documents. It identifies potential causes of invoice splitting as explicit settings in customizing, different header partners, different header fields, or equating billing dates in a data transfer routine. It provides solutions such as checking customizing settings, comparing header partner and field values, and entering billing dates to avoid unwanted splits due to date.

    Original Description:

    sap

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses invoice splitting in billing documents. It identifies potential causes of invoice splitting as explicit settings in customizing, different header partners, different header fields, or equating billing dates in a data transfer routine. It provides solutions such as checking customizing settings, comparing header partner and field values, and entering billing dates to avoid unwanted splits due to date.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    752 views2 pages

    Invoice Split Criteria in Billing Document

    Uploaded by

    Mirko
    This document discusses invoice splitting in billing documents. It identifies potential causes of invoice splitting as explicit settings in customizing, different header partners, different header fields, or equating billing dates in a data transfer routine. It provides solutions such as checking customizing settings, comparing header partner and field values, and entering billing dates to avoid unwanted splits due to date.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    Invoice split criteria in billing document

    Symptom
    Key word: Invoice split
    From a number of deliveries or sales orders more than one billing document is created.
    Additional key words
    Invoice split
    Invoice separation
    Billing document split
    Split criteria
    Header partner
    Header fields
    Split
    VF01, VF04, VF06
    Cause and prerequisites
    The invoice split may have been carried out for the following reasons:
    a) Explicit setting in Customizing
    b) Different header partners
    c) Different header fields
    d) The billing date of all documents is equated in a data transfer routine (for example,
    by VBRK-FKDAT = SY-DATUM). This works when you are billing using VF01; a
    single billing document is generated. However, if you use VF04 or in case of a batch,
    several billing documents might be generated.
    Solution
    Please check the causes mentioned above:
    1. Explicit setting in Customizing:
    On the detail screen of the document flow table (TVCPF) in the entry field 'DATEN
    VBRK/VBRP' (as of Rel.2.2..: 'Data transfer') the routine '003' (single invoice) was
    entered and thus an invoice split was created.
    2. Different header partners
    The header partners in the billing documents created are not identical which causes an
    invoice split. With regard to partner processing, an invoice split also occurs if the entries
    in the partner table of the reference document and the billing document also differ only in
    one field (!) for the partner functions of the billing document header (in the standard
    system, these are SP, BP and PY).
    3. Different header fields
    The header fields in the billing documents created are not identical which causes an
    invoice split.
    Attention: Not all header fields in the billing document are visible on the header detail
    screen of the billing document.
    To analyze the cause of the split, as of Release 3.0 you can use the 'Split analysis' function
    in the Environment menu when displaying or creating the billing documents.

    Before Release 3.0, you can proceed as follows:

    Display the two billing documents that you want to combine in two windows

    Move to the header detail screen in both windows

    Use debugging mode in both windows

    Enter VBRK as the variable and press 'Choose' in both windows

    Now compare all VBRK fields with the exception of


    VBRK-KNUMV
    VBRK-NETWR
    VBRK-MWSBK
    VBRK-VBELN
    VBRK-RFBSK
    VBRK-ERNAM
    VBRK-AEDAT
    VBRK-ERDAT
    VBRK-ERZET.
    These fields should not cause a split. You can find the source code relevant for this in program
    LV60AF0X, FORM routine XVBRK_BEARBEITEN.
    4. When using transaction VF04 or Billing (background) the date of the billing document
    (e.g. the current date) must be entered (In VF04: settings, default data. In VF06 or
    background: variant with parametrization) to avoid an unwanted split due to the billing
    date.
    5. To avoid a split due to different header fields - except for the fields listed above - you
    have the option of using customer-specific data transport routines in the copying control
    of the relevant document types which initialize the corresponding fields. However, the
    information contained in these fields is then lost in the billing document.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy