SD Billing Document Consolidation and Splitting

8/13/2019 SD Billing Document Consolidation and Splitting

1/42

Page 1 of 42 11/14/2013

SD Billing Document Consolidation

and Splitting

Technical Solution Guide


2/42

Page 2 of 42 11/14/2013

SD Billing Document Consolidation and Splitting

Consolidating or Splitting Billing Documents

Most organizations run the illing due list nightl! to create illing documents" #uite

often there are $uestions related to ho% and %h! certain deli&eries or orders comine'

or fail to comine' on illing documents" (his document %ill e)plain ho% the standard

s!stem %or*s and pro&ide e)amples of ho% the standard logic can e enhanced"

Creating Billing Documents

Before attempting to alter the processing logic of the illing program' it is %ise to

understand its asic functionalit!" Billing documents are creating using function module

+,-.,.C-C+(" (his function module is called from the illing document create

transaction ,01/SPM,506 and the illing due list ,04/SDB.77D76" n internal tale

is passed to this function that contains one or more source documents for %hich illing

is to occur" (hese documents are sorted ! customer' sales organization and illing

t!pe" (he result of this sort is se&eral susets of source documents that are grouped !the sort fields" or each suset' the illing logic attempts to create a illing document"

During the creation' the s!stem %ill populate illing document header and item fields

from the source document" +/3 contains configurale routines called Data (ransfer

+outines that can e de&eloped to alter the %a! fields are copied from a source

document to a destination document in this case' illing documents6" (hese routines

e)ecuteduringthisilingprocess"(hesuse$uentsection8Data(ransfer+outines9 e)plains

ho% these routines %or* in detail" nce the illing fields are populated' the logic

compares the fields to the pre&ious record" .f the asic fields are e$ual' the current

document %ill comine %ith the pre&ious document" .f the fields are different' a ne%

illing document %ill e created" (here are se&eral fields in illing documents that %illal%a!s e different and should not cause a split to occur" (he suse$uent section

8StandardCominationCriteria9e)plainsthislogic"

Relevant OSS Notes

(he follo%ing SS notes ma! e useful in understanding this process:

11152 .n&oice Split Criteria in Billing Documents

35;32 .n&oice Split ields from the Sales rder

30;


3/42

Page 3 of 42 11/14/2013


Standard Combination Criteria

=hen creating illing documents' the s!stem compares fields from the source

documents to determine if splitting should occur" (here are fields that must e

specificall! ignored during this process" or e)ample the document creation time

,B+>?+@(6 %ill al%a!s e different and a split should not occur ecause of this" (o

handle this' the main illing program contains a hard coded character string that

contains the field names of all fields to ignore during the source document comparison"

(he follo%ing screen shots demonstrate ho% this internal data string %or*s" =e ha&e

modified it in the illustration for demonstration purposes onl!" (his should ne&er e

done in a real s!stem' since the same result can e otained using data transfer

routines"

.n the follo%ing e)ample' %e ha&e selected t%o deli&eries for the same customer'

%ith different shipping conditions" (he fact that the shipping conditions are different

%ill cause a split to occur"


4/42

Page 4 of 42 11/14/2013


(he illing due list has split the deli&eries into t%o illing documents" (he Split anal!sis

utton can e pressed to see %hich fields caused the split"


5/42

Page A of 42 11/14/2013


.n this e)ample' a split occurs due to differences in three fields" ne of these fields is

the shipping conditions"


6/42


7/42

Page < of 42 11/14/2013


(o illustrate ho% the SM-(B string controls splitting' %e ha&e added ,SBDShipping conditions6 to the list" Changing this list is not recommended' %e ha&e done it

here temporaril! to demonstrate the functionalit! of the standard logic"


8/42

Page ; of 42 11/14/2013


(he same t%o in&oices are processed and the shipping condition is no longer causing

a split"


9/42

Page of 42 11/14/2013


Data Transfer Routines

(he correct %a! to control illing document consolidation and splitting is &ia Data

(ransfer +outines" (hese routines are created using transaction ,M and assignedin the Cop! Control configuration" +/3 contains se&eral standard routines and !ou

can create !our o%n ! cloning one of the standard routines" (he main purpose of

data transfer routines is to populate the fields of the document eing created %ith

data from the related preceding document"

Forcing a Split

(he illing document header tale ,B+>6 contains a special field that is used to force a

split to occur" (he @>+. field is a character string that contains concatenated fields

from the preceding documents" B! adEusting the contents of this string %ithin a data

transfer routine' !ou can force a split to occur"

Preventing a Split

(o pre&ent a split' the fields that cause a split to occur can e modified %ithin a data

transfer routine to contain the same &alue" or e)ample' t%o deli&eries that contain

different shipping conditions %ill split ecause the shipping conditions are copied to

the in&oice header ,B+>6" .f the field is cleared for each in&oice' the split %ill no

longer occur"


10/42

Page 10 of 42 11/14/2013


Standard Billing Document Data Transfer Routine (001)

(he data transfer routine elo% is one of the standard +/3 illing document routines"

.n this logic' the @> string is defined and populated %ith the distriution channel and

di&ision from the sales order header tale" dditional fields can e added to this string

and filled %ith &alues from an! of the data structures listed in the comments section"

(he concatenated @> string then mo&ed to the @>+. field of the illing document

header ,B+>6"


11/42

Page 11 of 42 11/14/2013


Implementing a new Data Transfer Routine

.mplementing a ne% routine re$uires oth de&elopment and configuration" (he routine

is created using transaction ,M" (he routine is then assigned &ia cop! controlconfiguration" (he easiest method used to create a ne% routine is to clone one of the

standard routines" (he follo%ing steps illustrate this procedure"

Step 1 Clone the standard routine

sing transaction ,M' na&igate to the data transfer routines for illing documents"

(he easiest %a! to create a ne% routine is to t!pe the ne% routine numer o&er one of

the e)isting routines and press enter" (he s!stem %ill create the ne% routine as a clone

of the one that %as o&er t!ped"


12/42

Page 12 of 42 11/14/2013


Step !ctivate the ne" routine

,M routines need to e acti&ated efore the! can e used"


13/42

Page 13 of 42 11/14/2013


Step # !ssign the ne" routine in cop$ control

Billing data transfer routines are assigned in cop! control at the item categor! le&el"


14/42

Page 14 of 42 11/14/2013


!ample " #revent an Invoice Split b$ Ship Condition

(he follo%ing e)ample demonstrates ho% to pre&ent illing document splits for a

specific field"

Business Re%uirement

(he illing due list in standard +/3 creates multiple illing documents for deli&eries

that contain different shipping conditions" (he client %ants these deli&eries to comine

into a single illing document"

Solution

(o sol&e this prolem' %e %ill create a custom Data (ransfer +outine" .n this routine'

%e %ill clear the shipping conditions field" B! clearing the field' it %ill contain the same

&alue for all deli&eries and %ill no longer cause a illing document split" (he side effectof this change is that the illing documents %ill no longer contain a shipping condition"


15/42

Page 1A of 42 11/14/2013


Step 1 Functionalit$ Prior to Changes

Belo% is the custom data transfer routine efore ma*ing an! changes" (his routine

%as cloned from the standard routine 001"


16/42

Page 15 of 42 11/14/2013


=e ha&e identified t%o deli&eries for the same customer' on the same da!' %ith

different shipping conditions" (he follo%ing screens displa! the functionalit! of the

standard illing due list logic prior to our change"


17/42

Page 1< of 42 11/14/2013


+unning the simulation' %e ha&e selected the t%o in&oices and e)ecuted the

split anal!sis"


18/42

Page 1; of 42 11/14/2013


(he result of the split anal!sis is a split ased on the shipping condition"


19/42

Page 1 of 42 11/14/2013


Step Coding the Data Transfer Routine Change

.n the custom data transfer routine' a single line of code is added that clears the

shipping conditions"


20/42


21/42

Page 21 of 42 11/14/2013


Because there %as no split' the in&oice detail screen appears %ith items from

each deli&er!"


22/42


23/42

Page 23 of 42 11/14/2013


Step 1 Functionalit$ Prior to Changes

Belo% is our custom data transfer routine efore ma*ing an! changes" (his routine

%as cloned from the standard routine 001"


24/42

Page 24 of 42 11/14/2013


=e ha&e identified t%o deli&eries for the same customer' on the same da!' %ith

different plants" (he follo%ing screens displa! the functionalit! of the standard illing

due list logic prior to our change"


25/42


26/42

Page 25 of 42 11/14/2013


Step Coding the Data Transfer Routine Change

.n the custom data transfer routine' the plant field =+>S6 is added to the comination

criteria field definition ,B+>?@>+.6" .n addition' logic is added to populate the field%ith the plant contained in the deli&er! item 7.PS?=+>S6" (his %ill cause the ,B+>?

@>+. field to differ %hen multiple plants are processed forcing the split to occur"


27/42

Page 2< of 42 11/14/2013


Step # Testing the Change

sing the same t%o deli&eries' %e e)ecute the illing due list again after changing

the routine in simulation mode"


28/42

Page 2; of 42 11/14/2013



split anal!sis"


29/42

Page 2 of 42 11/14/2013


(he result of the split anal!sis is a split ased on the comination criteria field @>+.6"

(he field contains a string that is the concatenation of the &alue80019'distriution

channel' di&ision and plant"


30/42


31/42

Page 31 of 42 11/14/2013


Step 1 Define an &ndicator in the Customer 'aster

n indicator in the Customer Master is needed to dri&e the consolidation logic"

Standard +/3 contains ten additional attriutes on >1 that can e used for an!purpose" or this proEect' %e %ill use >(+(+


32/42

Page 32 of 42 11/14/2013


Step Define the alues for !TR*

sing SM30' %e ha&e defined the follo%ing t%o &alues for the ne% field"


33/42


34/42


35/42

Page 3A of 42 11/14/2013


Step . Coding the Data Transfer Routine Change

.n the custom data transfer routine' the order numer field ,B76 is added to the

comination criteria field definition ,B+>?@>+.6" .n addition' logic is added topopulate the field %ith the sales order numer ased on the ne% indicator added to

the customer master" .f the indicator is set denoting that consolidation should occur6'

the order numer field %ill e empt!" .f the indicator is not set denoting that splitting

should occur6' the field %ill e filled" (his %ill cause the ,B+>?@>+. field to differ %hen

multiple orders are processed forcing the split to occur"


36/42

Page 35 of 42 11/14/2013


Step / Test1 (Create Separate Billing Documents)

(he indicator on the customer master is set so that separate illing documents are

created"


37/42

Page 3< of 42 11/14/2013


)ecute the illing due list using t%o deli&eries for the same customer on the same

da!" (hese deli&eries are related to different sales orders"


38/42

Page 3; of 42 11/14/2013



split anal!sis"


39/42

Page 3 of 42 11/14/2013


(he result of the split anal!sis is a split ased on the comination criteria field @>+.6"

(hefieldcontainsastringthatistheconcatenationofthe&alue80019'distriution channel'

di&ision' plant and sales order numer" .n this e)ample' the sales order numers are

different"


40/42

Page 40 of 42 11/14/2013


Step Test (Create a consolidated Billing Document)

(he indicator on the customer master is set so that illing document consolidation

occurs"


41/42


42/42

Page 42 of 42 11/14/2013


Because there %as no split' the in&oice detail screen appears %ith items from

each deli&er!"

SD Billing Document Consolidation and Splitting

Documents

Transcript of SD Billing Document Consolidation and Splitting