Example: air traffic controller

SD Billing Document Consolidation and Splitting

SD Billing Document Consolidationand SplittingTechnical Solution GuideThe Smith Consulting Group, Box 703 Flanders, NJ and R/3are the trademarks or registered trademarks of SAP AG in Germany and in several other 2005 The Smith Consulting Group, Inc. All Rights Billing Document Consolidation and Splitting6/19/2005 Page2of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights or Splitting Billing Billing OSS Combination Transfer a a Billing Document Data Transfer Routine (001)..11 Implementing a new Data Transfer 1 Clone the standard 2 Activate the new 3 Assign thenew routine in copy 1 Prevent an Invoice Split by Ship 1 Functionality Prior to 2 Coding the Data Transfer Routine 3 Testing the 2 Billing Document Split by 1 Functionality Prior to 2 Coding the Data Transfer Routine 3 Testing the 3 Consolidated Invoi

SD Billing Document Consolidation and Splitting 6/19/2005 Page 3 of 43 Technical Solution Guide Copyright © 2005 The Smith Consulting Group, Inc.

Tags:

  Document, Billing, Consolidation, Sd billing document consolidation and splitting, Splitting

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of SD Billing Document Consolidation and Splitting

1 SD Billing Document Consolidationand SplittingTechnical Solution GuideThe Smith Consulting Group, Box 703 Flanders, NJ and R/3are the trademarks or registered trademarks of SAP AG in Germany and in several other 2005 The Smith Consulting Group, Inc. All Rights Billing Document Consolidation and Splitting6/19/2005 Page2of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights or Splitting Billing Billing OSS Combination Transfer a a Billing Document Data Transfer Routine (001)..11 Implementing a new Data Transfer 1 Clone the standard 2 Activate the new 3 Assign thenew routine in copy 1 Prevent an Invoice Split by Ship 1 Functionality Prior to 2 Coding the Data Transfer Routine 3 Testing the 2 Billing Document Split by 1 Functionality Prior to 2 Coding the Data Transfer Routine 3 Testing the 3 Consolidated Invoicing by 1 Define an Indicator in the Customer 2 Define the Values for 3 Make the KATR7 Field Available to the Data Transfer 4 Coding the Data Transfer Routine 5 Test1 (Create Separate Billing Documents).

2 37 Step 6 Test2 (Create a consolidated Billing Document )..41SD Billing Document Consolidation and Splitting6/19/2005 Page3of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights or Splitting Billing DocumentsMost organizations run the Billing due list nightly to create Billing documents. Quite oftenthere are questions related to how and why certain deliveries or orders combine, or fail tocombine, on Billing documents. This Document will explain how the standard systemworks and provide examples of how the standard logic can be Billing DocumentsBefore attempting to alter the processing logic of the Billing program, it is wise tounderstand its basic functionality.

3 Billing documents are creating using function function module is called from the Billing documentcreate transaction (VF01/SAPMV60A) and the Billing due list (VF04/SDBILLDL). Aninternal table is passed to this function that contains one or more source documents forwhich Billing isto occur. These documents are sorted by customer, sales organization andbilling type. The result of this sort is several subsets of source documents that aregrouped by the sort fields. For each subset, the Billing logic attempts to create a billingdocument. During the creation, the system will populate Billing Document header anditem fields from the source Document .

4 R/3 contains configurable routines called DataTransfer Routines that can be developed to alter the way fields are copied from a sourcedocument to a destination Document (in this case, Billing documents). These routinesexecute during this Billing process. The subsequent section Data Transfer Routines explains how these routines work in detail. Once the Billing fields are populated, the logiccompares the fields to the previous record. If the basic fields are equal, the currentdocument will combine with the previous Document . If the fields are different, a newbilling Document will be created. There are several fields in Billing documentsthat willalways be different and should not cause a split to occur.

5 The subsequent section Standard Combination Criteria explains this OSS NotesThe following OSS notes may be useful in understanding this process:11162 Invoice Split Criteria in Billing Documents36832 Invoice Split Fields from the Sales Order308733 Billing Split Due to the Person NumberSD Billing Document Consolidation and Splitting6/19/2005 Page4of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights Combination CriteriaWhen creating Billing documents, the system compares fields from the source documentsto determine if Splitting should occur. There are fields that must be specifically ignoredduring this process.

6 For example the Document creation time (VBRK-ERZET) willalways be different and a split should not occur because of this. To handle this, the mainbilling program contains a hard coded character string that contains the field names of allfields to ignore during the source Document comparison. The following screen shotsdemonstrate how this internal data string works. We have modified it in the illustrationfor demonstration purposes only. This should never be done in a real system, since thesame result can be obtained using data transfer the following example, we have selected two deliveries for the same customer, withdifferent shipping conditions.

7 The fact that the shipping conditions are different willcause a split to Billing Document Consolidation and Splitting6/19/2005 Page5of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights Billing due list has split the deliveries into two Billing documents. The Split analysisbutton can be pressed to see which fields caused the Billing Document Consolidation and Splitting6/19/2005 Page6of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights this example, a split occurs due to differences in three fields. One of these fields is theshipping Billing Document Consolidation and Splitting6/19/2005 Page7of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.

8 All Rights SAPMV60A contains a hard coded list of fields that are excluded fromconsideration in the Splitting logic. The following screen displays these fields as they arecoded in the TOP include (MV60 ATOP). This subset of fields may differ depending onthe R/3 Billing Document Consolidation and Splitting6/19/2005 Page8of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights illustrate how the AUSNAHME_TAB string controls Splitting , we have addedVSBED (Shipping conditions) to the list. Changing thislist is not recommended, we havedone it here temporarily to demonstrate the functionality of the standard Billing Document Consolidation and Splitting6/19/2005 Page9of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.

9 All Rights same two invoices are processed and the shipping condition is no longer causing Billing Document Consolidation and Splitting6/19/2005 Page10of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights Transfer RoutinesThe correct way to control Billing Document Consolidation and Splitting is via DataTransfer Routines. These routines are created using transaction VOFM and assigned inthe Copy Control configuration. R/3 contains several standard routines and you cancreate your own by cloning one of the standard routines. The main purpose of datatransfer routines is to populate the fields of the Document being created with data fromthe related preceding a SplitThe Billing Document header table (VBRK) contains a special field that is used to force asplit to occur.

10 The ZUKRI field is a character string that contains concatenated fieldsfrom the preceding documents. By adjusting the contents of this string within a datatransfer routine, you can force a split to a SplitTo prevent a split, the fields that cause a split to occur can be modified within a datatransfer routine to contain the same value. For example, two deliveries that containdifferent shipping conditions will split because the shippingconditions are copied to theinvoice header (VBRK). If the field is cleared for each invoice, the split will no Billing Document Consolidation and Splitting6/19/2005 Page11of43 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.