Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Version 2.0
2007-08-10
Introduction to the
Dynamic Item
Processor
SAP R/3 Release 4.5B/4.6B/4.6C/4.7/ECC
SAP AG
Di
etm ar-Hopp-Allee 16
D-69190 W alldorf
SAP AG
Page 1 of 89
SAP AG
Page 2 of 89
Contents
1
INTRODUCTION ...........................................................................................................5
OVERVIEW....................................................................................................................6
CUSTOMIZING............................................................................................................24
4.1 Overview...................................................................................................................50
4.2 Exits ..........................................................................................................................50
4.3 BAdIs ........................................................................................................................53
4.3.1 BAdIs within the Dynamic Item Processor (DI Processor): .................................53
4.3.2 BAdIs for Restricting the Change Options for Users ...........................................55
4.3.3 BAdI for Document Flow Reporting ....................................................................55
4.3.4 BAdIs with Influence on Further Processing in SD:.............................................55
4.4 Changing Sel
ection Criteria or Sel
ected Data ..........................................................57
4.4.1 Change object list and hierarchy (EXIT_SAPLAD15_001) .................................57
4.4.2 Change Selection Criteria (EXIT_SAPLAD1C_002) ...........................................57
SAP AG
Page 3 of 89
5.1
5.2
5.3
7.1
7.2
7.3
(DP95,DP96,DP97)..83
Conversion of Bill
ing Fl
ow and Customizing ............................................................84
Conversion of Customer Enhancements ..................................................................85
Changes to the User Interface..................................................................................86
FIGURES.....................................................................................................................87
TABLES ......................................................................................................................88
10
10.1
10.2
SAP AG
Page 4 of 89
1 Introduction
The Dynamic Item Processor (DIP) offers an integrated way to process cost- or quantity-based
data at the interface between CO and SD. In SAP R/3,ERP,and ECC,the DIP is used for the
fl
exibl
e handl
ing of resource-rel
ated bil
l
ing. But it is al
so used for resul
ts anal
ysis,quotations for
service orders and pricing for proj
ects.
This paper is aimed mainl
y at consul
tants and peopl
e in companies customizing the dynamic item
processor. Additional
l
y,this paper describes the wide range of possibl
e enhancements for this
processor offered by customer enhancements to adapt the technicaltool to the company
s
business processes.
The focus is on the technicalimpl
ementation and customizing and not so much on the business
process for which there is onl
y a short overview at the beginning. The technicalsettings are
cl
arified byexampl
es of realbusiness processes.
Al
lfunctions described here are based on the dynamic item processor in R/3 Rel
ease 4.6C. In
chapter 5,you can find an overview on the differences between 4.5A/B and after rel
ease 4.6C.
The enhancements after rel
ease 4.6C are summarized in chapter 5.1. In this chapter,you wil
lfind
cross-references to the respective enhancements.
Pl
ease understand that we del
iver this paper onl
y in Engl
ish. No other l
anguages are avail
abl
e.
SAP AG
Page 5 of 89
2 Overview
2.1 Business Processes
The Dynamic Item Processor is a toolfor the sel
ection,summarization and grouping of cost or
quantity based data for CO obj
ects. This data is transferred to SD,where sal
es documents can
be created or j
ust the powerfulpricing engine is used for generating pricing information. The main
processes covered by this toolare resource-rel
ated bil
l
ing and the cal
cul
ation of sal
es prices. The
DIP can process singl
e obj
ects l
ike service orders or sal
es orders but it can al
so work on compl
ex
structures l
ike proj
ects or order networks. The processes are described in the fol
l
owing chapters.
2.1.1 Resource-Rel
ated Bil
l
ing of Sal
es Docum ents, Service Orders and
Proj
ects
In Resource-rel
ated bil
l
ing,the DIP is used to sel
ect the resources actual
l
y used of a service
order or a sal
es order to generate debit memo requests. As this is very often a periodic process,
resource-rel
ated bil
l
ing keeps a document fl
ow of the val
ues al
ready bil
l
ed or rej
ected . Onl
y the
open val
ues,cal
cul
ated by subtracting the al
ready bil
l
ed and the rej
ected val
ues from the total
val
ues,are offered to the user onl
ine.
You can define which val
ues shoul
d be bil
l
ed, postponed, or rej
ected. You can al
so define
manualprices for the bil
l
ing. This data can be saved for further processing without creating a
debit memo request. W hen you reopen this saved data,you can continue with your work. It is
even possibl
e to refresh the data which means that al
lmanualchanges are kept but the original
costs are read again.
If amounts were rej
ected in previous runs, you can undo the rej
ection via menu path:
Edit ! Undo Rej
ection. In the fol
l
owing pop-up,you can enter amounts,quantities or percentage.
In the finaldebit memo request additionaldata can be entered (i.e. texts for each item).
It is al
so possibl
e to create both a debit memo request and a credit memo request. So,val
ues
which were bil
l
ed wrongl
y to the customer can be easil
y credited to him. If onl
y a debit memo
request has to be created, val
ues to be credited appear as negative val
ues in the sal
es
document.
Debit or credit memo request items and their corresponding resources can be rej
ected or
reopened in the sal
es document by setting an appropriate reason for rej
ection. The reason for
rej
ection can be customized,that the costs are avail
abl
e again as open for bil
l
ing (see note
131288).
The bil
l
ing process incl
udes not onl
y singl
e obj
ects (sal
es order,service order). It is al
so possibl
e
to bil
lan order network (sub orders assigned to a main service order or an order network
assigned to a sal
es order) and even a whol
e proj
ect. In the l
ast case, the proj
ect must be
assigned to a sal
es order via W BS el
ement.
If a W BS El
ement is entered in sal
es order item,which isn
t a bil
l
ing W BS el
ement the system is
l
ooking upward in the hierarchy towards a bil
l
ing W BS El
ement. In standard,al
litems,which are
processed in DIP at the same time,have to own the same DIP Profil
e. A&D sol
ution is different,
there an enhancement was made to process severalitems with different DIP Profil
e at the same
time.
SAP AG
Page 6 of 89
Yes
Sal
es order item(s)
Service order
No
Yes
No
Edit onl
ine
Save data
Edit onl
ine
Sal
es price
basis
(Dynam ic
items)
Sal
es prices
(Conditions &
dynam ic items)
Saved data
Create debit
memo request
Debit memo
request
2.1.2 Resource-Rel
ated Resul
ts Anal
ysis
Resource-rel
ated resul
ts anal
ysis is a variation of resul
ts anal
ysis that uses the DIP to cal
cul
ate
the resul
ts anal
ysis data.
There are two val
uation methods for resource-rel
ated resul
ts anal
ysis:
SAP AG
Page 7 of 89
Objects
Debit
Mem o Req.
Actual
RRB
Costs
Doc. Flow
DI-Processor
Determ ination ofbilled
and unbilled costs
Debit
Mem o
Actual
Rev.
Results
Analysis
(CoS,WiP)
Settlem ent
Profitability Accounting
FinancialAccounting
SAP AG
Page 8 of 89
pricing and the quotation. Of course,it makes no sense to say costs shoul
d be bil
l
ed now,l
ater,
or never. The changes affect onl
y the basis for the cal
cul
ation of the prices,such as the quantity
of work hours intended to be used for the order. You can al
so add or change prices. Final
l
y,you
create the quotation. Note that it is onl
ypossibl
e to create one quotation for a service order. If you
want to create another one,you have to cancelthe ol
d one.
There is one maj
or difference from resource-rel
ated bil
l
ing:it is possibl
e to create severalpricings
before you create the finalquotation. At the start of the transaction,you can sel
ect one of the
pricings to change or create a new one. After you create the quotation,no new pricings can be
created and no further changes can be made to the existing ones.
In the service order master data,it is possibl
e to accept the service order afterwards. W hen you
accept the service order,the quotation is copied to the sal
es document type,specified in the
usage '
resource-rel
ated bil
l
ing'of the DIP profil
e, but no actualresource-rel
ated bil
l
ing takes
pl
ace.
Service order
Expl
icit creation of new pricing
Yes:onl
yone
No
Yes:mul
tipl
e
Sel
ection onl
ine
List of
pricings for
service order
Load pricing
Edit onl
ine
Sal
es price
basis
(dynamic
items)
Sal
es prices
(conditions
and dynamic
items)
Yes
No
Create quotation
immediatel
y?
Yes
No
Edit onl
ine
Edit onl
ine
Save pricing
Sal
es price
basis (dynam ic
items)
Sal
es prices
(conditions and
dynamic items)
Refresh pricing
Create quotation
Quotation
Quotation
Save pl
anned
revenues
SAP AG
Page 9 of 89
"
Quotation creation
Billing
Form
Fixed
Rate
Costs
None
Main Item
Not
rel
evant
Rel
evant
Not
rel
evant
Not
rel
evant
Sub-item
Rel
evant
(None)
Rel
evant
Rel
evant
Resource-Related Billing
Quotation exists
Quotation not exists
Main Item Sub-item Main Item Sub-item
Not
Not
Rel
evant Not
rel
evant
rel
evant
rel
evant
Not
rel
evant
Not
rel
evant
Rel
evant
Rel
evant
Not
rel
evant
Not
rel
evant
Rel
evant
Rel
evant
SAP AG
Page 10 of 89
category must be found which defines a statistical item. How to set up the item category
assignments is described in chapter 3.5.3.
SAP AG
Page 11 of 89
SAP AG
Page 12 of 89
Expl
icit creation of new pricing
Bil
l
ing W BS
el
ement
Proj
ect defintion
Inquiry
(al
linquiryitems)
Inquiryitem(s)
No
Sel
ection onl
ine
Pricing exists for
inquiryitems?
List of inquiries
for proj
ect def.
or wbs el
ement
Yes:mul
tipl
e
No
Yes:mul
tipl
e
Sel
ection onl
ine
Yes:onl
yone
List of
pricings
Yes:onl
yone
Edit onl
ine
Create debit memo
request immediatel
y?
Yes
Quotation
No
Edit onl
ine
Save pricing
Create Quotation
Sal
es price
basis
(dynamic items)
Sal
es prices
(conditions and
dynamic items)
Quotation
Create/
edit onl
ine
Bil
l
ing pl
an
Saved pricing
Bil
l
ing pl
an exists for
W BS el
em ent?
Refresh Pricing
Update pl
anned
revenues
No
SAP AG
Page 13 of 89
Simulations
Structures
Easy Cost
Planning
Billing
plan
Transfer
Pricing
SAP AG
Page 14 of 89
ed
nn
Pla
Manual
sts
co
Pl
anned revenues on tim escal
e
Billing Plan
Sales order(s)
Manual
Del
ete Bill
ing Pl
an
Create Bill
ing Pl
an
M anual
Project
Quotation(s)
Pl
anned rev. total
Pricing forProjects
d
ne
an
Pl
Project
sts
co
Pl
anned revenues total
Pla
nn
ed
Quotation(s)
M anual
rev
en
ue
st
ota
l
SAP AG
Page 15 of 89
2.1.5 Resource-Rel
ated Down Payments
As of SAP R/3 Enterprise PLM Extension 2.00 you can use the bil
l
ing pl
an and down payment
request together with resource-rel
ated bil
l
ing. You can use the bil
l
ing pl
an to create DMRs or
down payment requests and DMRs in the desired order.
This enhancement offers you the fol
l
owing advantages:
"
"
SAP AG
Page 16 of 89
Pl
ease pay al
so attention to the fol
l
owing notes:
"
Resource rel
ated down payment processing (858877)
"
Consul
ting note for resource rel
ated down payments (858702)
"
2.2 TechnicalProcess
The dynamic item processor makes a sel
ection,summarization and grouping of data over several
l
evel
s. You can use the DIP profil
e to customize how this is done. Every input obj
ect must have a
DIP profil
e.
The technicalprocess starts with the selection ofthe objects to be processed. The input obj
ect
must be abl
e to col
l
ect actualand/or pl
anned revenues. These are in most cases service orders
or sal
es orders. The entry obj
ect can be al
so the starting point of a compl
ex "bil
l
ing structure",
which means,that al
lobj
ects connected in a hierarchicalway to this entry obj
ect are processed
together. So it is al
so possibl
e to process a service order network,a sal
es order with assigned
internalorders or a proj
ect assigned to a sal
es order. The l
ast is different from the others
because,when you use proj
ects (for exampl
e,for resource-rel
ated bil
l
ing) costs and revenues are
handl
ed on the proj
ect. The sal
es document is onl
y for carrying the necessary SD data (sal
es
organization,partners) and the DIP profil
e.
The second step in the technicalprocess is the selection ofthe source data to be processed. In
most cases,pl
anned or actualcosts of the obj
ects are sel
ected,but it is al
so possibl
e to use
statisticalkey figures,cash,or user defined externalsources. Additional
l
y,these sources can be
combined and used together. For each source,sel
ection criteria can be specified. Theyare either
handl
ed directl
y at the database (exampl
e:the sel
ection of cost el
ements) or in the DIP itsel
f
(exampl
e:the sel
ection of cost centers). The first way has the big advantage of reducing the data
transfer from the database to the appl
ication server. W hich way is used depends on the sel
ection
characteristic and the source. It is possibl
e that one source can handl
e a sel
ection parameter
directl
y on the database l
evel
,but the other source has to handl
e it on the appl
ication server.
W hen you define your own sources,it is very important that this source can handl
eal
ot of the
sel
ection characteristics directl
y on the database side to achieve a good performance.
After the sel
ection,the sum m arization ofthe source data to dynam ic item s takes pl
ace. Al
l
sel
ected data has a number of characteristics and val
ues. In the DIP profil
e,you specify which
characteristics are rel
evant for the creation of dynamic items. Some characteristics are sel
ected
by defaul
t and cannot be removed:obj
ect,transaction currency,unit of measure,and posting
period (onl
y for resource-rel
ated bil
l
ing). Al
lnon-rel
evant characteristics are cl
eared and onl
y the
rel
evant ones are used to define a characteristic vector for each source data l
ine. The val
ues of
equalcharacteristic vectors are summarized. The DIP processes four val
ues:quantity,amount in
CO area currency,amount in transaction currency and amount in obj
ect currency. It is possibl
e to
have dynamic items with quantity or amount onl
y and al
so with both quantity and amount. So
sources can be roughl
y differentiated into quantity-based sources (l
ike statisticall
ine items) and
cost-based sources (l
ike actuall
ine items). These sources can be used together in a singl
e DIP
profil
e.
Every dynamic item is then assigned to a materialnumber by the m aterialdeterm ination. In the
DIP profil
e the assignment rul
es are specified. These assignment rul
es are specified based on
one or more rel
evant characteristics.
SAP AG
Page 17 of 89
In resource-rel
ated bil
l
ing,the next step is the sel
ection of the al
ready bil
l
ed val
ues. The total
values are balanced wi
th the docum ent flow to determ ine the open values. The open val
ues
can be then transferred to the bil
l
ing documents.
The next step is the sum m arization ofthe dynam i
c item s to sales docum ent item s. It is cl
ear
that onl
y dynamic items with val
ues to be transferred to the sal
es document are summarized. Al
l
dynamic items with equalmaterialnumber (from the materialdetermination) are summarized in
one sal
es document item. This summarization can be suppressed dependent on the materialor
the characteristics.
Dynam ic Item Processor
SD
Sales doc.
e.g.
-Sales Order,
-Service Order,
-Contract ...
Item 1
Source item s
Dynam ic Item s
Characteristics
Values
MaterialA
Characteristics
Values
MaterialB
Characteristics
Values
MaterialA
Characteristics
Values
MaterialC
Characteristics
Values
MaterialC
Characteristics
Values
MaterialA
Characteristics
Values
MaterialD
Characteristics
Values
Characteristics
Values
Head
Conditions
Item 2
Can be also
assigned to
# Projects
# Internalorders
# Service orders
MaterialA
Conditions
MaterialB
Conditions
MaterialC
Conditions
MaterialA
MaterialD
Conditions
MaterialD
MaterialA
Conditions
Item 2
Sales Price
te
ea
Cr
les
sa
Sources can be
# Actualvalues
# Planned values
# Userdefined sources
Sales Doc.
SD
m
cu
do
Mat. A
Mat. B
Mat. C
t
en
Mat. D
Mat. A
SAP AG
Page 18 of 89
SAP AG
Page 19 of 89
SAP AG
Page 20 of 89
"
To adj
ust the width of any col
umn simpl
y cl
ick the header of the col
umn. This feature is
al
so val
id for the sal
es price screen. It is avail
abl
e since rel
ease 4.6C.
"
The search function on the overview tree finds any description you type,regardl
ess of
strings or numbers.
"
The icon
"
displ
ays a screen with the l
egend for al
lused icons in the overview tree.
l
ast button of the overview tree
202603.
. This functional
ity is buil
t in Rel
ease 4.6C or see note
"
"
"
"
The ol
d function for simul
ating a sal
es document is in the Gotomenu (Simul
ate sal
es
and distribution docs).
The fol
l
owing is val
id for the Expensesscreen.
"
SAP AG
Page 21 of 89
"
Onl
ythe sel
ected characteristic and its direct successors are shown in the tabl
e view.
"
"
In the tabl
e view for Amount,Quantityor Percentageyou maydoubl
e-cl
ick one of the
activated col
umns of to be bil
l
ed,postponedor rej
ected. This deactivates the col
umn
and activates the col
umn that was formerl
y inactive.
"
If you doubl
e-cl
ick any other col
umn,you get the detailscreen for this characteristic.
"
"
You can switch between different hierarchies without accessing the customizing with the
menu entry Switch hierarchies from the menu Edit. Al
lentries marked for structuring
in the DIP profil
e are accessibl
e. You have the same possibil
ities as in customizing:
$ Change the sequence of the characteristics
$ Change the set and their attributes (part sets,upper sets,singl
e set)
$ Change the from and tol
evel
s
$ Show or hide singl
e val
ues
If you sel
ect the user-defined settings and hit
onl
y. If you sel
ect the save button
,the settings are written to the database and are avail
abl
e
whenever you access the DIP in the future,regardl
ess of whether you store the data from the
DIP.
Besides the data displ
ayed on the tab screens,the fol
l
owing information is al
so stored in the
database and appl
ied in the next cal
lof the DIP:
"
The height of the hierarchy controlfor the expense screen and the sal
es price
screenW hich tab strip was sel
ected for the expense screen and the sal
es price screen
"
W hich col
umns in the tabl
e view are active for entry
SAP AG
Page 22 of 89
SAP AG
Page 23 of 89
3 Custom izing
The main part of customizing for the DIP is done in the DIP profil
e. However,as the DIP creates
(or simul
ates) sal
es documents in SD,the customizing of sal
es documents and pricing shoul
d be
al
so considered when setting up the business processes. As the DIP uses material
s,al
lsettings
for them are al
so important when working with the DIP. A smal
l
er part is the set-up of resul
ts
anal
ysis.
This paper focuses on the set-up of the DIP profil
e and rel
ated customizing points.
3.1.1 Usage
The DIP knows two different usages. The usage can be used to handl
e different business
processes with the same profil
e.
The first usage is "Billing and Results Analysis". Two sal
es document types can be specified:one
for debit memo requests,the other for credit memo requests. The decision on which items are
debited or credited is based on the sign of quantity and amount. If onl
y one sal
es document for
debit memo requests is specified,al
litems are debited,but negative quantities or amounts with
opposite signs. It is not possibl
e to set up a profil
e with onl
y an entryfor the credit memo request,
nor shoul
d you specify a sal
es document type of a credit memo request in the col
umn of the
sal
es document type for the debit memo request. If you are using both credit memo requests and
debit memo requests,take care to customize your sal
es document types and the item categories
correctl
y. You can find a short description of this in chapter 3.5.
The second usage is "Quotation Creation and Sales Pricing". Here,onl
yone sal
es document type
can be specified for the created or simul
ated quotation. Normal
l
y,there shoul
d be no negative
items in this document,but if there are,the negative items are treated as they woul
d be in the
singl
e document case of bil
l
ing usage.
The 'W arranty check' indicator is onl
y processed during bil
l
ing or quoting of a service order. It is
not processed during bil
l
ing of service orders rel
ated to a sal
es document item. If the indicator is
set, the user exit in enhancement ICSV0005 is cal
l
ed where a reason for rej
ection can be
specified. This reason for rej
ection is automatical
l
yinserted in al
lcreated sal
es document items.
W ith the 'DI w/material' indicator,you can controlhow the system processes dynamic items for
which no materialwas found during the materialdetermination. If the indicator is cl
eared,the
systems raises an error about the missing material
. If the indicator is set,dynamic items without a
materialare removed and no error message is given. This indicator is very usefulfor reducing the
customizing effort in the source sel
ection screen (see 3.1.2.2). W hen the sign is set,you define
the items to be bil
l
ed onl
y bythe materialdetermination and not by the source sel
ection.
Another business process where this sign is usefulis the bil
l
ing of a proj
ect with different sal
es
document items - for exampl
e,for bil
l
ing in different currencies or two different business partners.
Look at the fol
l
owing situation:You set up two different order items account assigned to the same
SAP AG
Page 24 of 89
W BS el
ement. You want to bil
ldifferent costs by using different profil
es with a different sel
ection.
If you bil
lthe first items,everything l
ooks al
lright,but when you bil
lthe second item,the system
reopens the costs al
ready bil
l
ed with the opposite sign,because it finds fl
ow entries of your
obj
ects but not the originalcost. To overcome this probl
em,you set the '
DI w/material'indicator in
both profil
es and specify a materialdetermination,which finds a materialonl
y for the costs you
want to bil
lthrough this profil
e.
The disadvantages of this indicator shoul
d al
so be mentioned. Performance can sl
ow down
because the system reads data from the database,which in fact is not needed. Additional
l
y,you
coul
d m iss som e ofcosts you want to bil
lbecause no message is shown when the material
determination fail
s. Keep this in mind when working with this setting.
SAP AG
Page 25 of 89
3.1.2 Characteristics
The characteristics section is the most important part of the DIP profil
e. Here,you set up which
characteristics are used and how they are used. The settings here al
so have an effect on the
amount of data processed and therefore on the performance. You al
so set the defaul
t structuring
for dial
og processing.
General
l
y,the system distinguishes between two types of characteristics:
"
"
You can add your own characteristics of both types by using customer enhancements (see
chapter 0). The user defined characteristics are processed l
ike any SAP characteristic.
For information on which characteristics are provided by the different sources, see chapter
3.1.2.2.
SAP AG
Page 26 of 89
The '
Structuring'indicator marks the characteristics for the defaul
t structuring in the sal
es price
basis view. Structuring is described in chapter 3.1.2.2.
Some of the characteristics have a meaning not apparent at first gl
ance:
"
"
"
"
"
The "Accounting Indicator"is used in confirmations for service orders. If it is copied to the
sal
es document,it is shown automatical
l
yunder view '
Sal
es B'of the sal
es document
item. Remember to set the '
No summarization'indicator for the characteristic;otherwise it
is not copied to the sal
es document item.
"
"
"
"
Remember to sel
ect the "No summarization"indicator for the "Transaction Currency"if you
want to copy the amount in transaction currency to the sal
es document item.
"
Remember to sel
ect the "No summarization"indicator for the "Unit of Measure"
characteristic if you want to copythe quantity to the sal
es document items.
SAP AG
Page 27 of 89
SAP AG
Page 28 of 89
"
"
"
From level /To level can be used together withPartial sets to displ
ay a part of the set.
"
Single values (Checkbox) can be used together withPartial sets or Upper set to displ
ay
set nodes and nodes for the val
ue of the characteristic.
The settings for the Object number differs from other characteristics. You can onl
y set the
Sequence and the To level. This is because the hierarchy is defined here external
l
y,i.e. by a
proj
ect structure or an order network.
The behavior of the settings becomes cl
earer with a smal
lexampl
e:
Situation: You are bil
l
ing a sal
es
order item. The profil
e has the cost
el
ement as a rel
evant characteristic
and you al
so want to structure
according to a cost el
ement group.
The DIP creates four dynamic items
with cost el
ements 400000,405000,
410000,and 415000. Your set SETKSTAR is shown in Figure 11.
SAP AG
Page 29 of 89
The resul
t for each structuring setting is shown in Tabl
e 2.
Ex.
A
Result
E
F
G
Additionally,the object num ber is added to the
structuring. The sequence is first object num ber,
second cost elem ent.
SAP AG
Page 30 of 89
Another exampl
e shows the possibil
ities of structuring using individualval
ues.
Situation:You are bil
l
ing a sal
es order item. You want to bil
lmaterialand l
abor to your customer.
The profil
e has materialnumber and activity type. You want to see in structuring a sum for each
materialand each activity. Therefore,we use these two characteristics for structuring. W e set for
both the sign '
Singl
e val
ues'and use quite simpl
e sets:They must have onl
y one node with al
l
val
ues,but excl
uding the initialval
ue. The sequence of the structuring is first activitytype,second
materialnumber. The resul
t for this exampl
e is shown in Figure 12. You are probabl
y wondering
why the material
s appear before the activity types al
though the structuring is the other way
around. The reason for this behavior is the initialval
ue of the characteristics. The dynamic items
of the material
s have an initialactivity type. The sequence sorts the dynamic items first for the
val
ues of the characteristic activity type. As the initialval
ue is al
ways before a non-initialval
ue,
the material
s are displ
ayed first.
SAP AG
Page 31 of 89
"
"
Statistical indicators - Line items: This is a source for actualstatisticalkey figures. It can
be used to bil
l
;for exampl
e;kil
ometers.
"
Statistical indicators - Totals records: The same as for the actualcosts - faster but with
fewer characteristics.
SAP AG
Page 32 of 89
"
Funds - Line items: The funds source can be used for bil
l
ing payments and down
payments. These payments refer to CO val
ue types 57 and 61.
"
Funds - Totals records: Faster but with fewer characteristics than the l
ine items.
"
Planned costs - Totals records: This source can be used for pricing or quotation creation.
The system reads al
lpl
anned costs.
"
"
Easy Cost Planning: This source can be used for pricing for proj
ects. In fact,it is the onl
y
source that can be used for pricing in Proj
ect Buil
der. It is al
so possibl
e to sel
ect the data
from EasyCost Pl
anning for a pricing based on an inquiry.
"
Intercompany Line Items (since Extension 2.00): This source is used for transaction DP93
only.
For al
lsources,the system does not read val
ues from settl
ement. The reasons are the internal
settl
ements when processing proj
ects. If you want to bil
lcosts from an internalorder whose costs
are settl
ed to a sal
es order,you have to assign the internalorder directl
y to the sal
es order. The
system then recognizes this connection and reads the costs from the sal
es order and the internal
order. Another way to overcome this probl
em (by using a customer enhancement) is described in
chapter 4.1 (see note 204874,too).
For the cost sources, al
l revenues postings are excl
uded automatical
l
y from the sel
ection.
Technical
l
y, this is not done by business transactions. The system checks the cost el
ement
category and excl
udes al
lpostings of categories 11 (Revenues) and 12 (Sal
es deduction).
It is possibl
e to use a source more than once. If you do,you have to enter the sel
ection criteria for
each source sel
ection l
ine to prevent the source data being read twice. You can al
so combine
different sources in one profil
e. However,you have to take care to use characteristics from al
l
sources to recognize the data. For exampl
e,if you combine actualcosts and statisticalindicators,
the characteristic cost el
ement cannot be fil
l
ed for the indicators,so you shoul
d al
so use the
characteristic statisticalkeyfigure.
SAP AG
Page 33 of 89
SAP AG
Page 34 of 89
3.1.4 MaterialDetermination
The finalstep in the profil
e definition is to set up of materialdetermination. For al
ldynamic items,
a materialhas to be found to process them further. The rul
es for finding the material
s are
specified in this part of the profil
e. The material
s can either be l
isted here or they can come from
the source if provided.
In addition,the materialnumber found here al
so affects on the summarization of dynamic items to
sal
es document items. Al
ldynamic items with the same materialnumber are summarized to one
sal
es document item,if no other setting in the profil
e switches the summarization off,for exampl
e,
the 'No Summarization' indicator in the characteristics view (chapter 3.1.2.1),
As of SAP R/3 Enterprise Core 4.70 it
s possibl
e to increase the MaterialDetermination Lines
per DIP profil
e. You can define more than 999 materialdetermination l
ines in the DIP profil
e now.
SAP AG
Page 35 of 89
SAP AG
Page 36 of 89
Since rel
ease 4.70 the controloptions for transferring quantity and costs are enhanced. The
originalsign Use Quantitywas therefore renamed as Transfer Quantity/Costs.
The sign Transfer Quantity/Costs determines how the quantity/costs from the source are
transferred to the items in the sal
es document.
In the DMR the resource items have either costs or quantities or costs and quantities. Depending
upon your business processes and the type of resource item (working time, material
s, and
del
ivery route) you can bil
lexpenditures based on quantityor costs and then determine the prices
correspondingl
y. In addition, you must define whether costs and/or quantities shoul
d be
transferred to the sal
es and distribution document items.
You have the fol
l
owing possibil
ities:
"
"
"
"
"
C -transferquantity only
The system transfers onl
ythe quantityto be bil
l
ed to the sal
es and distribution
document. Resource items are transfered if the quantityto be bil
l
ed does not equal
0. Resource items with costs not equalto 0,but quantities equalto 0 are not
transfered. Resource items with a quantityto be bil
l
ed that is l
ess than 0 are shown as
credit memo items.
Rem ark:The term resource item is not the same as dynamic item in this case,but rather it is a
bil
l
ing request item to be generated. Dynamic items with costs or quantities to be bil
l
ed < 0 can
be shown as debit memos if they are summarized with other dynamic items,so that the total
costs and quantityis greater than 0.
If you want to bil
lbased on costs,choose the space,X or A option. Pricing shoul
d be set so that
the net val
ue is determined from costs pl
us surcharge.
SAP AG
Page 37 of 89
SAP AG
Page 38 of 89
W e want to bil
lworked hours,used material
s,and overhead to our customer. To do this, we use
the source '
Actualcosts - Line items'which provides the characteristic activity type,material
,and
cost el
ement. These characteristics are marked as rel
evant in the characteristics view of the
profil
e. W e bil
lal
lworked hours with the same materialto reduce the compl
exity of the exampl
e.
The materialin the invoice shoul
d be the same as in our source data. Next we create three
material
s for our bil
l
ing:LABOR,MATERIALS and OVERHEAD. In the materialdetermination
screen,three l
ines with these material
s are entered. For LABOR and MATERIALS,we set the
sign '
Use quantity'to transfer the quantity to the invoice. Onl
y for the MATERIALS,we set the
sign '
Materialdirect'
,because we want to show in our invoice the used material
s. Normal
l
y,the
MATERIALS coul
d be cl
eared but we l
eft it showing us for what this l
ine is used. The material
determination view is shown in Figure 19.
Next,we have to think how we can identify the different costs from our source data and assign
them to the right material
. Labor costs have an activity type and a cost el
ement but no material
number. Materialcosts have a cost el
ement and a materialnumber but no activity type. Final
l
y,
overhead costs have onl
y a cost el
ement,but neither an activity type nor a materialnumber. In
fact,our overhead summarizes al
lother costs,but this keeps the exampl
e simpl
e. As al
lof our
costs have a cost el
ement,we sel
ect the '
Materialdetermination'indicator onl
y for activity type
and materialin the characteristics view of our profil
e. These are the characteristics we use for our
materialdetermination.
Now,as we know how to identify our costs,we create some sets for our characteristics using the
set maintenance tool
:
"
"
SAP AG
Page 39 of 89
Line
1
Material
LABOUR
MATERIALS
OVERHEAD
Criteria
SAP AG
Page 40 of 89
Line
1
Material
LABOUR
Criteria
Optional
MATERIALS
Optional
OVERHEAD
OTHER COSTS
SAP AG
Page 41 of 89
Actualcosts -Line
item s
Actualcosts -Totals
records
Statisticalind. -Line
item s
Technicalfield nam e
Accounting indicator
Activity num ber*
Activity type
Billing form 1
Business partner**SRM
Business process
Category ID **SRM
Com m itm ent item
Cost center
Cost elem ent
Docum ent num ber
Item num ber**SRM
AP
AP
(AP)
AP
AP
DB
AP
AP
AP
(AP)
AP
AP
AP
(AP)
AP
(AP)
(AP)
AP
AP
(AP)
AP
AP 2
AP
(AP)
AP
AP
(AP)
AP
AP
(AP)
AP
AP
AP
BEMOT
ASNUM
LSTAR
FAKTF
SERV_AGENT_ID
PRZNR
CATEGORY_ID
FIPOS
KOSTL
KSTAR
BELNR
REF_OBJECT_ITEM
DB
DB
AP
DB
AP
DB
AP
(AP)
AP
DB
DB 6
AP
DB
AP
A/D
AP 4
AP
(AP)
AP
DB
AP
DB
AP
DB
AP
AP
(AP)
DB
DB
AP
A/D
(AP)
DB
AP
DB
AP
DB
AP
(AP)
DB
DB
AP
A/D
(AP)
AP
AP
DB
AP
A/D
AP 4
AP
(AP)
AP
DB
AP
DB
AP
A/D
(AP)
DB
AP
AP
AP
AP
AP 5
AP
AP
(AP)
AP
AP
AP
AWSYS
MATNR
OBJNR
OBART
POPER
PERNR
WERKS
AWERK
BUZEI
PRODU
ORDERED_PROD
ASNUM
STAGR
TWAER
REG_OBJECT_ID
MEINH
Value type
Version
WBS Elem ent **
Work center
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
DB
AP
WRTTP
VERSN
/CBAD/BILL_WBS
ARBPL
Table 5:Characteristics
*)
In rel
ease 4.6C,5.00,6.00 and 7.00 this characteristic is cal
l
ed ActivityNumber. But in
rel
ease 4.70 it is cal
l
ed Service Number.
**)
SRM
SAP AG
Page 42 of 89
Not provided
" DB Provided and sel
ected on database l
evel
" AP
Provided and sel
ected on appl
ication server l
evel
" A/DProvided,but onl
ythe year is used to sel
ect on database l
evel
Rem arks for Tabl
e 5:
1. The bil
l
ing form is not taken from the source. It is taken from the sal
es order item or the service
order.
2. The accounting indicator is taken from the service order for source "Pl
anned costs - Total
s
records".
3. The product is onl
y fil
l
ed for the specialdynam ic item of the service product. This specialdynam ic
item is fil
l
ed with the fol
l
owing characteristics:Accounting indicator;Bil
l
ing form ;Unit of m easure;
Obj
ect num ber;Period;Product;Transaction currency;Pl
ant.
4. Al
though the program coul
d fil
lthis characteristic,the source data itsel
f does not provide it norm al
l
y
in 4.6C.
5. The period is derived from target start date of the operation for source EasyCost Pl
anning.
6. The fiel
d MEINB is taken from tabl
e COVP to fil
lthe unit of measure.
3.1.7 Profil
e Check (ODP2)
W ith the profil
e check report,the settings and consistency of profil
es can be checked. The check
report l
ooks for overl
apping criteria and tests if al
lsets exist and if they are defined for the fiel
ds
they were used for. If an error is detected,a red l
ight is displ
ayed. For the overl
ap check,a detail
screen shows which l
ines are overl
apping.
Since SAP R/3 Enterprise Core 4.70 a new anal
ysis program for DIP profil
e is cal
l
ed via
transaction ODP2. The new program checks for consistency in the profil
e,too. However,it can
check onl
y one profil
e per program run. It now offers more information,enabl
es you to print the
entire profil
e,and simul
ates materialdetermination
If you want the check consistency for mul
tipl
e profil
es at the same time,you can use the program
found in transaction ODP2A which was avail
abl
e untilrel
ease 4.6C onl
y.
SAP AG
Page 43 of 89
SAP AG
Page 44 of 89
button,the ol
d data disappears. You wil
lal
so l
oose al
lmanualprice changes to the
pricing.
"
"
It is cl
ear that you shoul
d not remove a source sel
ection l
ine or change a source in a l
ine.
The source is an impl
icit rel
evant characteristic. Therefore you shoul
d not change from
source "'
ActualCosts - Line Items"to "ActualCosts - Total
s records"or vice versa.
"
"
DO...:
"
You can add or remove any dependent characteristic. This has no direct impact on the
dynamic items or the document fl
ow of resource-rel
ated bil
l
ing.
"
"
"
If it is real
l
y necessary to change the profil
e,it is often best to copy the ol
d one and process ol
d
orders with the ol
d one and appl
y the new profil
e onl
yto new orders.
SAP AG
Page 45 of 89
However,there are al
so some business processes where the costs are the basis for the pricing.
Here,the costs must be copied to a condition of the pricing procedure. W ith transaction ODP4,
such a condition type can be specified for each sal
es document type of your debit/credit memo
requests or quotations. Take care that this condition is in the pricing procedure which is not onl
y
determined by the sal
es document type but al
so by other criteria l
ike sal
es area or customer in
transaction OVKK.
It is al
so possibl
e to copy both the quantity and the costs to the pricing procedure. The onl
y thing
to do is to set the "Use Quantity"indicator and specify a cost condition. A probl
em with rounding
errors arises if these val
ues get too l
arge. The system tries to find a price unit for the items.
Sometimes,it can happen that the price unit exceeds 99,999,which marks the maximum price
unit. Now the price unit is set to this l
imit and by mul
tipl
ying the quantity with the price unit,a smal
l
difference occurs.
Exampl
e:A dynamic item has a quantity of 123,456,789 hours and an amount of 987,654,321.00
euros. The system creates a price unit of 80,000 euros per 10,000 hours. By mul
tipl
ying the hours
by the price unit,the condition in the pricing procedure displ
ays 987,654,312.00 euros as the
condition val
ue.
The system can update three currencies of your costs:control
l
ing area currency,obj
ect currency,
and transaction currency. In control
l
ing area,it can be set if al
lcurrencies or onl
y the control
l
ing
area currency is updated. There is stil
lthe question which currency is copied to the pricing. If onl
y
the control
l
ing area currency is updated,the amount in this currency is copied. If the transaction
currency is al
so updated, it depends on the setting of the sign '
No summarization'for the
characteristic '
Transaction currency'in the DIP-profil
e. If it is set, the amount in transaction
currency is copied. If it is not set,the amount in control
l
ing area currency is copied. Bysetting the
sign '
No summarization'for the transaction currency,the system creates different sal
es document
items if the transaction currency differs in the dynamic items. Therefore,the transaction currency
and the amount can be copied to the sal
es document item.
Regardl
ess of the transferred currency,the amount is converted to the sal
es document currency.
The price date is used as the date for the change rate.
3.4 Materials
Material
s are used both on the input and on the output side of the DIP. Therefore,some things
must be considered when creating material
s which are used by the DIP.
On the input side,material
s can be read from sources and used as a characteristic,if the source
provides the materialnumber. However,al
though a source coul
d provide the materialnumber as
a characteristic,it is not certain that you woul
d real
l
y get it. For exampl
e, you want the material
number of your proj
ect pl
anning in a sal
es pricing. To get the pl
anned costs,you set up your DIP
profil
e with source "Pl
anned costs -Total
s records". This source can provide the materialnumber,
but for pl
anned costs,the materialnumber is onl
y updated to the cost tabl
es if the "Material
origin"'indicator is switched on in the materialmaster. The sign can be found in view "Costing 1"
of the materialmaster.
On the output side, it is necessary to define material
s which can be used in the material
determination of the DIP profil
e. These material
s are transferred to the sal
es document items,
regardl
ess of whether the sal
es document is real
l
y created or j
ust created as a simul
ation in
background to get the pricing. Therefore,some of the sal
es view must be maintained in the
materialmaster for the sal
es area you are working in your business processes. At l
east,the views
"Basic Data 1"and "Sal
es:sal
es org.1"must be maintained in the materialmaster if the material
is to be used in the materialdetermination. If the materialwhich was provided by the source
SAP AG
Page 46 of 89
shoul
d be used directl
y,these views must al
so be maintained in its materialmaster even if they
are onl
y used for pricing and are never sol
d or bil
l
ed.
The possibil
ity of transferring the quantity and its unit of measure from the dynamic items to the
sal
es document items requires the proper set-up of the materialused to bil
lthis quantity. Here it
can happen that the unit of measure of the dynamic item is not equalto the base unit of measure
or the sal
es of the materialmaster. General
l
y,the program woul
d stop with an error message if
no conversion is defined between these units. Take care that your conversion is set up correctl
y,
especial
l
y for the easy convertibl
e units l
ike hours,minutes,and seconds.
The '
Generalitem category group'('
Basis Data 1'
) is important for the item category assignment
in SD customizing.
3.5.1 Sal
es Docum ent Types
General
l
y al
lsal
es document types can be used in the DIP. There are no speciall
imitations. SAP
del
ivers some sal
es document types which can be used for the DIP:L2 and G2 for Resourcerel
ated Bil
l
ing;AE for Quotation Creation for Service Orders;AP for Pricing for Proj
ects.
"
SAP AG
Page 47 of 89
For the non-product processing,the assignment for item category group DIEN has to be:
Sal
es Document
Type
ZQU
Item Category
Group
DIEN
Usage
Higher LevelItem
Category
SEIN
Defaul
t Item
Category
ZQUN
Sal
es Document
Type
ZQU
ZQU
Item Category
Group
DIEN
DIEN
Usage
SEIN
SENI
Higher LevelItem
Category
ZQUN
Defaul
t Item
Category
ZQUN
ZQUS
For bil
l
ing form '
Costs'things l
ook j
ust the opposite because the main item must be the statistical
one:
Sal
es Document
Type
ZQU
ZQU
Item Category
Group
DIEN
DIEN
Usage
SENI
SEIN
Higher LevelItem
Category
ZQUS
Defaul
t Item
Category
ZQUS
ZQUN
The l
ines of the l
ast two tabl
es must be added for each item category group you want to use in
the dynamic item processor to cover al
lbusiness processes.
3.5.4 CopyControl
For the copy control
,nothing specialhas to be customized. The onl
y thing to mention is that no
customizing for the copy of sal
es document items must be done,because the system copies onl
y
the sal
es document header to the new sal
es document type. From the item of the original
document,onl
ythe account assignment is copied to the new items.
SAP AG
Page 48 of 89
SAP AG
Page 49 of 89
4.2 Exits
Al
lthese exits are cal
l
ed during the different business process at a certain time. Some of them
are onl
y cal
l
ed for specific business processes. An overview with the sequence of the exit-cal
l
s is
shown in Figure 22.
Enh.
AD010001
Exit
EXIT_SAPLAD13_001
EXIT_SAPLAD13_002
EXIT_SAPLAD15_001
AD010002
EXIT_SAPLAD15_010
EXIT_SAPLAD1C_002
AD010003
AD010005
AD010006
AD010007
V46H0001
EXIT_SAPLAD12_003
EXIT_SAPLAD12_004
CI_ATTRI2
CI_ATTRD
EXIT_SAPLAD15_005
EXIT_SAPLAD14_006
EXIT_SAPLAD14_008
EXIT_SAPLAD15_015
EXIT_SAPLV46H_001
EXIT_SAPLV46H_002
KKAG0004
ICSV0005
EXIT_SAPLADK0_001
EXIT_SAPLADK0_002
CI_ADK0_RA2
EXIT_SAPLISDI_001
Description
Change obj
ect l
ist and its hierarchy
Change texts for DI structuring
Typing nodes for singl
e val
ues
Change obj
ect l
ist and hierarchy
Del
imit sel
ection and/or fil
ter determined data
Source fil
ter (not avail
abl
e for al
lsources)
Change COSEL - sel
ection structure
Create user-defined DI characteristics
Fil
luser-defined independent characteristics
Fil
luser-defined dependent characteristics
Structure of user-defined independent charact.
Structure of user-defined dependent charact.
Read user-defined sources
Menu exit:Change DI val
ue
Exit:DP processor menu (screen 100) *)
Change text for menu exit *)
Change DI processing Information
SD customer functions for resource-rel
ated bil
l
ing
Customer function when creating item
Customer function for partner changes
Resul
ts anal
ysis with dynamic items
Postprocessing:CO subkey dynamic items RA
Postprocessing of Resul
ts Anal
ysis with Dis
Additionalfiel
ds of CO subkey to be fil
l
ed
Determining reason for rej
ection - RRB
SAP AG
Page 50 of 89
Enh.
MV45AFZZ
(Incl
ude)
Exit
USEREXIT_PRICING_PREPARE_TKOMK
USEREXIT_PRICING_PREPARE_TKOMP
KOMKAZ
KOMPAZ
USEREXIT_SAVE_DOCUMENT
USEREXIT_READ_DOCUMENT
USEREXIT_DELETE_DOCUMENT
VBAPKOZ
KKAG0005
EXIT_SAPLKKAG_007
Description
User exits for modifications in
sal
es document processing
Incl
ude or assign a val
ue to
an additionalheader fiel
d in
the communication structure
KOMK taken as a basis for
pricing
Incl
ude or assign a val
ue to
an additionalitem fiel
d in the
communication structure
KOMP taken as a basis for
pricing
Structure with user defined
fiel
ds for pricing
communication header
Structure with user defined
fiel
ds for pricing
communication item
Update additionaltables
when saving a sal
es
document
Read additionaltables when
reading a sal
es document
Del
ete additionaltabl
es when
del
eting a sal
es document
Structure with user defined
fields for sal
es document
item
Determination of time frame
and results anal
ysis key
SAP AG
Page 51 of 89
Onl
y resul
ts anal
ysis
Start resul
ts anal
ysis
EXIT_SAPLKKAG_007
Determine obj
ects
EXIT_SAPLAD15_001
EXIT_SAPLAD1C_002
Fil
ter standard source
EXIT_SAPLAD15_010
EXIT_SAPLAD12_003
EXIT_SAPLAD12_004
EXIT_SAPLAD15_005
Onl
yfor new interface
EXIT_SAPLAD12_004
Onl
y bil
l
ing
Not for saved data
Onl
y dial
ogue
Only when saving
sal
es docum ent
Process standrad
sources
Al
ways
Read bil
l
ing fl
ow
Materialdetermination
EXIT_SAPLAD15_015
EXIT_SAPLAD13_001
Simul
ate sal
es
document
Summarize to sal
es doc. items
Create header
Create item s
EXIT_SAPLV46H_001
OtherSD exits for creating items
USEREXIT_PRICING_PREPARE_TKOM K
USEREXIT_PRICING_PREPARE_TKOM P
EXIT_SAPLV46H_002
User dial
ogue
EXIT_SAPLAD14_008
EXIT_SAPLAD14_006
Create sal
es document
Al
lexits l
ike simul
ation
USEREXIT_SAVE_DOCUMENT
Change sal
es document
USEREXIT_READ_DOCUM ENT
Other SD exits for changing doc.
USEREXIT_SAVE_DOCUMENT
Save resul
ts anal
ysis
EXIT_SAPLADK0_001
EXIT_SAPLADK0_002
SAP AG
Page 52 of 89
4.3 BAdIs
As of SAP R/3 Enterprise Core 4.7 new Business Add-Ins (BAdIs) are avail
abl
e. These BAdIs are
devel
oped for al
lcustomer enhancements and have the same status as customer enhancements,
which are stil
lsupported. Onl
y the customer enhancement AD010006 was migrated to BAdI
SMOD_AD010006 and is avail
abl
e onl
y as a BAdI. The BAdI methods are cal
l
ed at the same
pl
ace as the exits.
In addition to the BAdIs with functions from customer enhancements,new Business Add-Ins are
al
so del
ivered.
DIP_AD010001
This enhancement is used to change the obj
ect l
ist and the hierarchy setup. Furthermore
you can change texts for structuring dynamic items.
It contains the fol
l
owing methods:
$ EXIT_SAPLAD13_001:Change text in dynam ic item structuring
(Further inform ation can be found in chapter 4.6)
$ EXIT_SAPLAD15_001:Change obj
ect l
ist and hierarchy
(Further inform ation can be found in chapter 4.2.1)
"
DIP_AD010001_FLD
This enhancement is used for structuring according to singl
e val
ues and change
characteristic val
ue texts. The enhancement contains the fol
l
owing methods:
$ EXIT_SAPLAD13_002:Typing nodes for singl
e val
ues
$ EXIT_SAPLAD13_003:Change text for characteristic val
ues
"
DIP_AD010002
This enhancement is used for fil
tering read data. The enhancement is not avail
abl
e for al
l
sources. The enhancement contains the fol
l
owing method:
$ EXIT_SAPLAD15_010:Source fil
ter (not for al
lsources)
(Further inform ation can be found in chapter 4.2.3)
"
DIP_AD010002_SEL
This enhancement is used to restrict sel
ection. The enhancement contains
the fol
l
owing method:
$ EXIT_SAPLAD1C_002:Change sel
ection criteria
(Further inform ation can be found in chapter 4.2.2)
"
DIP_AD010003_DC
This enhancement is used to create user-defined dependent characteristics for
determining dynamic items. The enhancement contains
the fol
l
owing method:
$ EXIT_SAPLAD12_004:Fil
luser-defined dependent characteristics
(Further inform ation can be found in chapter 4.3.3)
SAP AG
Page 53 of 89
"
DIP_AD010003_IC
This enhancement is used to create user-defined independent characteristics for
determining dynamic items. The enhancement contains the fol
l
owing method:
$ EXIT_SAPLAD12_003:Fil
luser-defined independent characteristics
(Further inform ation can be found in chapter 4.3.2)
"
DIP_AD010005
This enhancement is used to create user-defined sources for determining dynamic items.
The enhancement contains the fol
l
owing method:
$ EXIT_SAPLAD15_005:Read user-defined sources
(Further inform ation can be found in chapter 4.4)
"
SMOD_AD010006
This enhancement is used to change the val
ues in the dynamic items (amounts and
quantities). It contains the fol
l
owing methods:
$ EXIT_SAPLAD14_006:Function real
ized using the custom er-specific m enu entry
$ EXIT_SAPLAD14_008:Menu text for the custom er-specific m enu entry
"
DIP_AD010007
This enhancement is used to change dynamic item processing information (such as
materialdetermination). It contains the fol
l
owing method:
$ EXIT_SAPLAD15_015:Change Dynam ic Item Processing Inform ation
(Further inform ation can be found in chapter 4.5)
"
DIP_CHECK_INPUT_OBJ
This enhancement is used to checkthe access obj
ect in the DI processor. The
enhancement contains the fol
l
owing methods:
$ CHECK_SALES_ORDER_ITEM:Checksal
es order item
$ CHECK_SERVICE_ORDER:Checkservice order
(Pl
ease take notice of note 401942 for detail
s on BAdI:Check entry obj
ect in dynam ic
item processor)
"
DIP_GET_SEL_DATA
This enhancement is used for transferring sel
ection data to other programs,which cal
l
ed
resource-rel
ated bil
l
ing,for exampl
e. It consists of one method:
$ GET_SELECTION_DATA:Transfer sel
ection data to other program s
Param eters of m ethod GET_SELECTION_DATA:
Parameter
Description
IT_INPUT_OBJECTS
01for RRB
11for Sal
es Pricing
FROM_SELECTION_SCREE
N
SAP AG
In sel
ection screen entered
sal
es order,service order,W BS
el
ement,sal
es order item.
Page 54 of 89
"
AD01_RRB_COLLECTIVE1
This enhancement is used to modify the output l
ist for col
l
ective processing for resourcerel
ated bil
l
ing (DP95,DP96 and DP97). The enhancement contains the fol
l
owing methods:
$ FILL_ADDITIONAL_FIELDS:Change or add to output l
ist
This m ethod provides the opportunityto reduce the am ount of m essages bydel
eting certain
types of m essages.
$ CHANGE_FIELDCAT:Change fiel
d catal
og of output l
ist
$ USER_SELECTION:Determ ine fol
l
ow-up action when sel
ecting a fiel
d per doubl
e-cl
ick/hotspot
$ CHANGE_LINE_SIZE:Change num ber of l
ines for printing
DIP_INFLUENCE_GUI
W ith this Business Add-In you can stipul
ate whether the GUI is displ
ayed in displ
ay or
change mode. The enhancement contains the fol
l
owing method:
$ SET_MODE_CONDITION_SCREEN:Set processing m ode for the condition screen
"
DIP_SET_USERSETTINGS
This enhancement is used to make user settings and prevent users from changing these
settings themsel
ves. The enhancement contains the fol
l
owing methods:
$ SET_USER_SETTINGS:Set user settings
$ DEFINE_NON_ALTERABLE_SETTINGS:Define non-al
terabl
e settings
(Pl
ease take notice of note 446477 for detail
s on Fixed setting of the user settings for DP80/DP90)
AD01_RRB_REPORTING_1
This enhancement is used to fil
lother fiel
ds in document fl
ow reporting (DP98) for bil
l
ing
requests. The enhancement contains the fol
l
owing methods:
$ FILL_ADDITIONAL_FIELDS:Change or add to output l
ist
$ CHANGE_FIELDCAT_LAYOUT:Change fiel
d catal
og/l
ayout of output l
ist
$ USER_SELECTION:Determ ine fol
l
ow-up action when sel
ecting a fiel
d per doubl
e-cl
ick/hotspot
BADI_SD_V46H0001
This enhancement is used for changing the header and item data and adds
further partners for items. The enhancement contains the fol
l
owing
enhancement components:
$ EXIT_SAPLV46H_001:Change the item fiel
ds
$ EXIT_SAPLV46H_002:Change partner
SAP AG
Page 55 of 89
"
DIP_CREATE_FOLLOW_UP
This enhancement is used to determine whether a bil
l
ing request is created in resourcerel
ated bil
l
ing,or whether the expenditure shoul
d be added to an existing sal
es order or
contract as a sub-item as it
s done in standard for repair orders. The enhancement has the
fol
l
owing enhancement components:
$ CREATE_FOLLOW _UP_SALES_DOC:Create fol
l
ow-up docum ent or enhance existing
docum ent
"
DIP_SET_SD_DIALOG
This enhancement is used to activate SD dial
og boxes during sal
es document simul
ation
and creation. The enhancement contains the fol
l
owing enhancement components:
$ SET_SD_DIALOG_POPUPS:Activate dial
og boxes in SD sal
es docum ent
The fol
l
owing tabl
e contains the ol
d enhancements and the Business Add- Ins that repl
ace them.
The ol
d enhancements are,however,stil
lavail
abl
e.
SAP AG
Business Add-In
DIP_AD010001
DIP_AD010002
DIP_AD010002_SEL
DIP_AD010003_DC
DIP_AD010003_IC
DIP_AD010005
SMOD_AD010006
DIP_AD010007
BADI_SD_V46H0001
Page 56 of 89
SAP AG
Page 57 of 89
Al
though al
lcriteria from the source sel
ection l
ine are fil
l
ed in ET_COSEL,your changes have
onl
y an effect on sel
ection if they are rel
ated to a fiel
d which is directl
y handl
ed on the database
side. I.e. for source '
Actualcosts - Line items'you cannot add a sel
ection criterion for activity
types, but you can add one for cost el
ements - even if the cost el
ement is not a rel
evant
characteristic. Any added sel
ection criterion for activity type is not eval
uated l
ater with other
criteria even if the activity type is a rel
evant characteristic.
For which fiel
ds the sel
ection criteria can be changed depends on the source and the tabl
es read
by the source. An overview is shown in Tabl
e 8.
Source
Actualcost Line items
Table
COVP
'
Actualcosts Total
s records
COSSA
COSPA
COVPR
COSRA
V_COFP
FMSUA
COSSA
COSPA
COSRA
Fields
LEDNR,OBJNR,GJAHR,PERIO,W RTTP,VERSN,
KSTAR,HRKFT,VRGNG,VBUND,PARGB,BEKNZ,
TW AER,MEINH,MEINB,W ERKS,MATNR
LEDNR,OBJNR,GJAHR,W RTTP,VERSN,KSTAR,
HRKFT,VRGNG,PAROB,USPOB,BEKNZ,TW AER
LEDNR,OBJNR,GJAHR,W RTTP,VERSN,KSTAR,
HRKFT,VRGNG,VBUND,PARGB,BEKNZ,TW AER
LEDNR,OBJNR,GJAHR,PERIO,W RTTP,VERSN,
STAGR,VRGNG,MEINH
LEDNR,OBJNR,GJAHR,W RTTP,VERSN,STAGR,
VRGNG
OBJNR,GJAHR,PERIO,W RTTP,VERSN,VRGNG,
TW AER
LEDNR,OBJNR,GJAHR,W RTTP,GEBER,POSIT,
VORGA,TW AER,BUKRS,GSBER
Equalto '
Actualcosts - Totals records'
Equalto '
Stat. key fig. - Total
s records
CKF_DIP_C None
USTOMER_
EXIT
SAP AG
Page 58 of 89
Exampl
es:
1. PROBLEM:You want to excl
ude al
lmaterial
s from the sel
ection of source '
Actualcosts - Line
items'but you do not want to add the materialas a rel
evant characteristic.
SOLUTION:Add a l
ine to ET_COSEL excl
uding tabl
e records with a materialnumber:
DELETE ET_COSEL
WHERE FIELD = 'BEKNZ'
OR ( FIELD = 'VRGNG'
AND (
LOW = 'KOAO'
OR LOW = 'KOAL'
OR LOW = 'KOAP'
OR LOW = 'KOAM' ) ).
4.4.3 Fil
ter or change the sel
ected data (EXIT_SAPLAD15_010)
Tabl
e 8 al
so shows a l
ist of the tabl
es read by the different sources. The data of these tabl
es
read by the different sources can be fil
tered or modified in EXIT_SAPLAD15_010. For each
source sel
ection l
ine,the exit is cal
l
ed with the data read by this source sel
ection l
ine. In the exit
you can either fil
ter on fiel
ds which you cannot access in EXIT_SAPLAD1C_002 or you can even
modify the val
ues of the sel
ected data.
Exampl
es:
1. PROBLEM:You want to excl
ude al
lpostings with company code '
ABCD'in source '
Actual
costs - Line items'
SOLUTION: Just add the fol
l
owing l
ines of code in the exit,excl
uding the company code,
which is not needed.
IF I_DLISRC = '0001'.
DELETE T_COVP
WHERE BUKRS = 'ABCD'.
ENDIF.
SAP AG
Page 59 of 89
2. PROBLEM:Your confirmations are done in minutes and hours. The different unit of measures
causes the system to create more dynamic items and more items in the debit memo request.
You
want
to
have
al
ways
minutes
in
the
dynamic
items.
SOLUTION: Check the sel
ected data for postings with hours. For these l
ines,convert the
quantityto minutes.
IF I_DLISRC = '0001'.
LOOP AT T_COVP
WHERE MEINB = 'H'.
T_COVP-MBGBTR = T_COVP-MBGBTR * 60.
T_COVP-MEINB = 'MIN'.
MODIFY T_COVP.
ENDLOOP.
ENDIF.
SAP AG
Page 60 of 89
PROBLEM:You want to use the company code of your actualcosts as a characteristic of the
dynamic items.
SOLUTION:
$ Create structure CI_ATTRI2 and add the fiel
d ZZBUKRS with type BUKRS to the structure. Save
and activate the structure. Tabl
e AD01DLI wil
lbe changed on the database.
$ Add the fol
l
owing code to exit EXIT_SAPLAD12_003,fil
l
ing the characteristic ZZBUKRS:
SAP AG
Page 61 of 89
SAP AG
Page 62 of 89
4.6.2 Impl
ementation of EXIT_SAPLAD15_005
In the exit,you have to sel
ect the source,move the val
ues and al
lavail
abl
e characteristics l
ine by
l
ine to the interface tabl
e and l
eave it. It is not necessary to summarize the data or create the
dynamic items in the exit. This is al
ldone by the dynamic item processor.
As import parameters,you get the currentl
y processed profil
e (I_PROFNR),the usage of the
profil
e (I_USAGE),the currentl
y processed source (I_DLISRC),the control
l
ing area (I_KOKRS)
and the currency of the control
l
ing area (I_KW AER). The sel
ection criteria of the currentl
y
processed source sel
ection l
ine can be found in parameter CT_COSEL. Exit
EXIT_SAPLAD1C_002 is not cal
l
ed for user-defined sources. The sel
ection criteria can be
eval
uated in the exit to speed up database accesses. If your source can eval
uate al
lor part of the
SAP AG
Page 63 of 89
sel
ection criteria,you shoul
d del
ete them from CT_COSEL. Al
lremaining sel
ection criteria are
eval
uated after the exit. The obj
ects for which the source data has to be read are in parameter
tabl
e IT_OBJECTS. In this tabl
e you can find the CO obj
ect number and the obj
ect currency.
Your output must go to tabl
e ET_DATA. The structure of this tabl
e is a combination of al
l
avail
abl
e independent characteristics and the val
ue fiel
ds. Move your source data to this tabl
e
and the rest is done by the dynamic item processor. You do not have to know which
characteristics are rel
evant in the current profil
e,j
ust fil
lthe tabl
e with al
lcharacteristics,your
source can provide. The DIP wil
lcl
ear al
lcharacteristics which are not rel
evant and summarize
the data accordingl
y to the remaining characteristics. The dependent characteristics are defined
afterwards. In the val
ue fiel
ds of ET_DATA,you can transfer the amount and the quantity to the
dynamic item processor. Fiel
d MEGBTR has to be fil
l
ed with the quantity. The amount in
transaction currency has to be moved to fiel
d W TGBTR,the amount in obj
ect currency has to be
moved to fiel
d W OGBTR,and the control
l
ing area currency has to be moved to fiel
d W KGBTR.
Be aware that,if you use the new interface,the system determines the dependent characteristics.
Therefore exit EXIT_SAPLAD12_004 is cal
l
ed after creating dynamic items from the data
provided by the exit.
Exampl
e:
PROBLEM:You want to read the materialcomponents of W BS el
ements. The quantityshoul
d be
the required quantity. The amount shoul
d be taken from the totalprice of the component.
SOLUTION:Create a source that reads the components of your obj
ects. The price is converted
into obj
ect currency and control
l
ing area currency. The quantity is taken from the requirements
quantity of the component. The components are stored in database tabl
e RESB. Therefore we
add an entryto tabl
e AD01SRC with source keyZCOM and source text "Components of W BS". In
tabl
e AD01SRCTAB we add one record for source ZCOM with tabl
e name '
RESB'
. Next,the
fol
l
owing code has to be impl
emented in the exit modul
e:
* Local data
DATA: BEGIN OF ZT_WBS OCCURS 0,
" Table with WBS elements
PSPNR LIKE PRPS-PSPNR,
" internal WBS number
OBJNR LIKE AD01OBJ-OBJNR,
" CO object number
OWAER LIKE AD01OBJ-OWAER,
" object currency
END OF ZT_WBS.
DATA Z_WBS LIKE LINE OF ZT_WBS.
DATA Z_OBJECT LIKE LINE OF IT_OBJECTS.
DATA ZT_RESB TYPE TABLE OF RESB.
" Components
DATA Z_DATA LIKE LINE OF ET_DATA.
FIELD-SYMBOLS <ZRESB> LIKE LINE OF ZT_RESB.
* Check if table is relevant for the current source
CALL FUNCTION 'AD1C_SOURCE_TABLE_CHECK'
EXPORTING
I_TABNAME
= 'RESB'
I_DLISRC
= I_DLISRC
EXCEPTIONS
TABLE_NOT_RELEVANT = 1.
CHECK SY-SUBRC IS INITIAL.
* Collect the relevant objects
LOOP AT IT_OBJECTS INTO Z_OBJECT.
CHECK Z_OBJECT(2) = 'PR'.
" Process only WBS elements
Z_WBS-PSPNR = Z_OBJECT-OBJNR+2.
Z_WBS-OBJNR = Z_OBJECT-OBJNR.
SAP AG
Page 64 of 89
Z_WBS-OWAER = Z_OBJECT-OWAER.
APPEND Z_WBS TO ZT_WBS.
ENDLOOP.
* Continue only if WBS elements exist
CHECK NOT ZT_WBS[] IS INITIAL.
* Read components of objects
SORT ZT_WBS BY PSPNR.
SELECT *
FROM RESB
INTO TABLE ZT_RESB
FOR ALL ENTRIES IN ZT_WBS
WHERE PSPEL = ZT_WBS-PSPNR.
SORT ZT_RESB BY PSPEL.
LOOP AT ZT_RESB ASSIGNING <ZRESB>.
CLEAR Z_DATA.
* Get object number for WBS element of component
IF <ZRESB>-PSPEL <> ZT_WBS-PSPNR.
READ TABLE ZT_WBS INTO Z_WBS
WITH KEY PSPNR = <ZRESB>-PSPEL
BINARY SEARCH.
ENDIF.
* Fill characteristics
Z_DATA-KSTAR = <ZRESB>-SAKNR.
" Cost element
Z_DATA-MATNR = <ZRESB>-MATNR.
" Material number
Z_DATA-MEINH = <ZRESB>-MEINS.
" Unit of measure
Z_DATA-OBJNR = Z_WBS-OBJNR.
" Object number
Z_DATA-TWAER = <ZRESB>-WAERS.
" Transaction currency
Z_DATA-WERKS = <ZRESB>-WERKS.
" Plant
Z_DATA-WRTTP = '01'.
" Value type 01 = Planned
* ...
" Any other (ind.) char.
* Fill values
* Quantity
IF NOT Z_DATA-MEINH IS INITIAL.
Z_DATA-MEGBTR = <ZRESB>-BDMNG.
ENDIF.
* Amount
* - Transaction currency
IF NOT Z_DATA-TWAER IS INITIAL.
Z_DATA-WTGBTR = <ZRESB>-GPREIS * <ZRESB>-BDMNG
/ <ZRESBY-PEINH.
ENDIF.
* - Object currency
IF Z_DATA-WTGBTR <> 0.
IF Z_DATA-TWAER <> Z_WBS-OWAER.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
EXPORTING
DATE
= <ZRESB>-BDTER
FOREIGN_AMOUNT
= Z_DATA-WTGBTR
FOREIGN_CURRENCY = Z_DATA-TWAER
LOCAL_CURRENCY
= Z_WBS-OWAER
TYPE_OF_RATE
= 'P'
IMPORTING
LOCAL_AMOUNT
= Z_DATA-WOGBTR
EXCEPTIONS
SAP AG
Page 65 of 89
NO_RATE_FOUND
= 1.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ELSE.
Z_DATA-WOGBTR = Z_DATA-WTGBTR.
ENDIF.
ENDIF.
* - Controlling area currency
IF Z_DATA-WTGBTR <> 0.
IF Z_DATA-TWAER <> I_KWAER.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
EXPORTING
DATE
= <ZRESB>-BDTER
FOREIGN_AMOUNT
= Z_DATA-WTGBTR
FOREIGN_CURRENCY = Z_DATA-TWAER
LOCAL_CURRENCY
= I_KWAER
TYPE_OF_RATE
= 'P'
IMPORTING
LOCAL_AMOUNT
= Z_DATA-WKGBTR
EXCEPTIONS
NO_RATE_FOUND
= 1.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ELSE.
Z_DATA-WKGBTR = Z_DATA-WTGBTR.
ENDIF.
ENDIF.
* Append values in export table
APPEND Z_DATA TO ET_DATA.
ENDLOOP.
The exampl
e shoul
d work as shown here,al
though it has some disadvantages. First,there is no
buffering of the sel
ected data. If you have more than one source sel
ection l
ine in your profil
e for
this source,the exit is cal
l
ed more than once for the same obj
ects. As there is al
so no eval
uation
of sel
ection criteria,the same data woul
d be read more than once. A good buffering l
ogic woul
d
be very usefulhere,but is obviousl
y much more work. The second probl
em of this coding is the
sel
ection of RESB without the primary key or an index. To improve the performance,an index on
tabl
e RESB for fiel
d PSPEL coul
d be created. Much better woul
d be the using of tabl
e RSPSP.
This is an index tabl
e for the components (and reservations) for W BS el
ements.
SAP AG
Page 66 of 89
Param eter
DEFPERCENT
AUMOT
INV_MAT
INV_SINGLE
INV_QUANT
FLMEH
Unchangeabl
e DLINR
processing
DLISRC
information
VBELN
VBPOS
AUFNR
PSPNR
PRONR
PROFNR
FAKTF
OBJNR
OBJNR_PD
TIMESTMP
Changeabl
e
processing
information
Meaning
Defaul
t percentage
Apportionment reason
Materialfrom materialdetermination
Sign:Create sal
es document item for each dyn. Item
Sign:Use quantity of dyn. Item in sal
es document item
Sign:Convert to sal
es unit
Dynamic item key
Source of dynamic item
Input obj
ect:Sal
es document
Input obj
ect:Sal
es document item
Input obj
ect:Service order
Input obj
ect:W BS el
ement
Input obj
ect:Proj
ect definition
Dynamic item processor profil
e
Bil
l
ing form
Input obj
ect:CO obj
ect number
Input obj
ect:CO obj
ect number of proj
ect definition
Timestamp of dynamic item
SAP AG
Page 67 of 89
"
Texts of obj
ects cannot be modified. Often they have l
onger names than the structures
provide by the exit. Texts of obj
ects are read after the exit.
"
SAP AG
Page 68 of 89
I_DLIA with the dynamic item characteristics and I_DLIM with the dynamic item processing
information.
Exampl
e:
PROBLEM: You are bil
l
ing working hours of empl
oyees. For each empl
oyee the hours are
summarized in one sal
es document item. To achieve this,the '
No summarization'indicator is set
for the personalnumber characteristic . As the empl
oyees change often,you bil
lthe working
hours by one materialfound by materialdetermination. In the dynamic item structure view,you
can use a structuring by the personnelnumber singl
e val
ues to get an overview of the working
hours per empl
oyee. In the sal
es price view,the text of the materialis displ
ayed. You want to see
here the personalnumber,too.
SOLUTION:Change the texts of dynamic items to the personalname and personalnumber. The
code can l
ookas fol
l
ows:
SAP AG
Page 69 of 89
$
)
%&
%*&
2
6
;
$
D
)
2
H
6
J
;
$
$
$$
D
N O
QR
%&
7&89&
7<&9&
?< @
9A
C%<&
?%9&
E @
7
C&7
C<&
:<?
%&:7
%C<&
%9B?
:%&
G<&9
77<&
!"!#
! '
!(!"
+ ,
,
+ '
-!.
/ ,
01#!
% ,
3 ,
.4.5!
:1 ,
"! 5#!
7!#"+ '="1(>!#
B" ,
/ (!+1#!
#+"+ ,
" 1##!".
?+!# ,
+ '="1(>!#
(( ,
(!"F,
!(
G+ '
1! .5!
7 '
+"
%1" ,
"0F,
"I ,
+#
C#- !"!#
7 '
+" /LK #- !"!#
% ,
3 ,
.4"1(>!#
>
M ! .5!
3!# ,
"
7 ,
"0 5!# ,
I
P ."+( ,
F,
!(
!
SAP AG
Page 70 of 89
C_VBAPKOM-ZZAUFART = I_SDSM_DLI-ZZAUFART.
1. PROBLEM:You have entered a manualdiscount condition ZDIS in the sal
es order item. The
discount shoul
d be used for al
litems in debit memo requests created by resource rel
ated
bil
l
ing. In standard,the system does not copy the conditions from the predecessor document
to
the
debit
memo
request.
SOLUTION: Parameter C_VBAPKOM has fiel
ds KSCHLX, KBETRX, KW AERX, KPEINX,
KMEINX (where X goes from 1 to 4) for adding conditions to the sal
es document items. To
sol
ve the probl
em, the conditions from the predecessor have to be read and added to
parameter C_VBAPKOM. Add the fol
l
owing coding in EXIT_SAPLV46H_001:
SAP AG
Page 71 of 89
SAP AG
Page 72 of 89
4.10 OtherExits in SD
There are a l
ot of other exits in SD. To expl
ain them al
lexceeds the scope of this paper. One
probl
em which often occurs is to save your additionalcharacteristics with the sal
es document. For
the personnel number,it is quite easy,because it can be stored with the partner rol
es. If you
have other characteristics which cannot be moved to SAP standard fiel
ds,you have to save them
in your own tabl
es. This can be done in the exits for reading,saving and del
eting of sal
es
documents.
Exampl
e:
PROBLEM: You want to store the val
ue of fiel
d ZZAUFART together with the sal
es document
item.
SOLUTION: First you have to create a tabl
e containing at l
east the fiel
ds MANDT, VBELN,
POSNR and ZZAURT. The first three fiel
ds must be simil
ar to tabl
e VBAP and are the keyof your
tabl
e ZZVBAPADD. Create al
so two function modul
es for l
oading and saving this tabl
e. The l
ast
one has to be an update function modul
e. In USEREXIT_READ_DOCUMENT,you have to cal
l
your read modul
e to get the additionaldata. In USEREXIT_SAVE_DOCUMENT the data has to
be saved using your update modul
e. Final
l
y USEREXIT_DELETE_DOCUMENT must be used to
remove your additionaldata if the sal
es document is del
eted.
SUTWVYXWZ
eUf_gUh\iUj
f_yUz\h\i\{
[\V\]U^UT_^a`
k_l\m n_oqp\r
|\wU}_pLlq~LrYWoU}UtWv\w\p\rLr\v\m\v
S yU_U\
Un\\_pUamLpU_mU_wL\lYt_n_U_o
U\\
Un\\_pUamLrYWoU}UtWv\w\p\rLUn\\_pU_\w
b\]YX_c_V\d
sYtWu\v\w\oLx
sYs\\lUn\_m
YUn_vU_mYWm\w
pU_\pU_m\v\\p\o
U=U\t\t\__
l\o\mU}_lU_p
=_p_Up\\m
|Y|U_vU_o\v\\mYWlU=Un\\_pU_\w
YUWUp\\mLUn\\_pU_\w
\lU_mU_lYt\t\__LvU_p\vLUn\\_p_\w
SAP AG
Page 73 of 89
SUTWVYXWZ
j_h
h_Uz\\\_\yU{\_e
h_Uz\\\ [ {Uj_z\f
h_Uz\\\\ b\ \yU{\_e
h_Uz\\\\\{ [ g\
h_Uz\\\_yU [ g\
h_Uz\\\\\_gUh_g
h_Uz\\\_\\\eU_
h_Uz\\\_\\Yj_z b
h_Uz\\\_\\Uz_Yj
h_Uz\\\_\\Uz_g\
h_Uz\\\_\\Ui_y\
h_Uz\\\_\\Uz_g\
h_Uz\\\ [ {_\eU_
h_Uz\\\ [ {_Yj_z b
h_Uz\\\ [ {_Uz_Yj
h_Uz\\\ [ {_Uz_g\
h_Uz\\\ [ {_Uz_g\
h_Uz\\\ [ {_Ui_y\
h_Uz\\\\_y\Uz_g\
h_Uz\\\\_y\Uz_g\
h_Uz\\\\_y\Ui_y\
h_Uz\\\_\\U bU
h_Uz\\\_\\U b
h_Uz\\\_\\U b
h_Uz\\\_\\U b
h_Uz\\\_\\U [U
h_Uz\\\_\\U [
h_Uz\\\_\\U [
h_Uz\\\\_y\Uz_g\
h_Uz\\\\_y\Uz_g\
h_Uz\\\\_y\Ui_y\
h_Uz\\\_\\U_y\e
h_Uz\\\ [ {_U_y\e
S i_Uh\iUj
[qV\]U^UT_^_`
kal\r\p \n_U_pU
n\\_pU_\wLl\~Lv\\lUn\_mL\vYt_n_p\o
qUWmLl\~L\p\v\oUn\_pLl\~LUn_vU_mYWmYWp\o
n\\_pU_\wLl\~ _p\\pU\n_p\o
sq\\lUn\_mY__4__rYW\v\m\lU
s}\}_lU_mYWlU_\pU_m _p\v\o\lU
kal\m n_o\p\r
sq\lUn\_mL~U_l\Lo\lUn\_\p
sq\lUn\_m4__\lYW\p\r
sq\lUn\_mLlU}_pU
sq\lUn\_mLm\l U\t\t
sq\lUn\_mLm\l }_l\o\mU}_lU_p
sq\lUn\_mLm\l _p_Up\\m
n_vU_mYWm\wL~U_l\Lo\lUn\_\p
n_vU_mYWm\w4__\lYW\p\r
n_vU_mYWm\wLlU}_pU
n_vU_mYWm\wLm\l U\t\t
n_vU_mYWm\wLm\l }_l\o\mU}_lU_p
n_vU_mYWm\wLm\l _p_Up\\m
pU_\pU_m\v\\pLm\l U\t\t
pU_\pU_m\v\\pLm\l }_l\o\mU}_lU_p
pU_\pU_m\v\\pLm\l _p_Up\\m
ap\\pU\n_pLl\~ _l\r\p
kal\m n_o\p\r
U ]U^_`\V\]UUXWVL
U_
U_
U_
U_
U_
U_
U_
U_
U_
U_
pU_\pU_m\v\\pLm\l U\t\t
pU_\pU_m\v\\pLm\l }_l\o\mU}_lU_p
pU_\pU_m\v\\pLm\l _p_Up\\m
sq\lUn\_m _v\oYWoL~\lUL}_pU_\pU_m\v\\p\o
n_vU_mYWm\w _v\oYWoL~\lUL}_pU_\pU_m\v\\p\o
WUU=k_l\r\p4WoLr\wU_v\YW4Wm\p\
"
"
Exampl
e:
PROBLEM:You want to give the user the possibil
ity to postpone al
ldynamic items with an open
amount l
ess than 10 euros.
SOLUTION:Set the open val
ue of the dynamic items to the postpone col
umn.
SAP AG
Page 74 of 89
SAP AG
Page 75 of 89
DELETE ct_collective_result.
ENDIF.
ENDLOOP.
ENDM ETHOD.
4.14.1 Use of service operation and short text in the debit memo request
Resource rel
ated bil
l
ing is a quite usualprocess to bil
lservice orders. These orders are structured
by service operations and materialcomponents. For the l
ast,it'
s quite easy to have them l
isted in
the bil
l
ing,because the materialnumber is updated to the actualcosts source and it'
s al
so a
standard characteristic of the DIP. The bigger probl
em in bil
l
ing service orders is the displ
ay of
the service operations in the invoice. The order confirmation is done on operations'l
evel
,but it'
s
not obviousl
y visibl
e in the costs source. You can find there a l
ot of CO and FI stuff,but the
confirmation is encrypted in some of those strange fiel
ds. In this chapter,we impl
ement a sol
ution
to bring the service operations'text into the short text of the debit memo request item.
First of al
l
,we have to know about the l
ink from the CO l
ine item to the service operation. If a
confirmation is posted,the confirmation number and counter can be found in COVP-REFBN and
COVP-AW ORG. W ith this information we can read the confirmation from tabl
e AFRU and find
there the routing number (AFRU-AUFPL) and the generalorder counter (AFRU-APLZL). This
l
eads us straight to the service operations in tabl
e AFVC where the operation number (AFVCVORNR) and short text (AFVC-LTXA1) is stored. Now,you may have the intention to impl
ement
the operation number and the short text as independent characteristics. But this can l
ead into
troubl
e,if these val
ues are changed in the service order after they are bil
l
ed. The system woul
d
create different dynamic items and the previousl
y bil
l
ed val
ues have no connection to the source
costs anyl
onger.
Therefore, we use a different approach with a sol
ution based on both independent and
dependent characteristics.
1. First,we define two independent characteristics ZZAUFPL (type CO_AUFPL) and ZZAPLZL
(type CO_APLZL) and fil
lthem in EXIT_SAPLAD12_003.
SAP AG
Page 76 of 89
SAP AG
Page 77 of 89
3. Third,we have to bring the operation number and text into the short text of the debit memo
request item. For this,sign No summarization'must be set in the DIP profil
e for characteristics
ZZVORNR and ZZVORTX and the fol
l
owing code must be added to EXIT_SAPLV46H_001:
IF
IF
SAP AG
Page 78 of 89
SAP AG
Page 79 of 89
Document Fl
ow Eval
uations for Order
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can eval
uate the document
fl
ow of bil
l
ed resources/expenses for a customer order,service order,contract,or proj
ect
using a new program. The program displ
ays the bil
l
ed,rej
ected,and open
resources/expenses in a structure overview simil
ar to the expenditure view in resourcerel
ated bil
l
ing. You can change the structure interactivel
y. The bil
l
ing requests are l
isted in
detailfor each resource item. You can navigate to the bil
l
ing request directl
yfrom the
resul
t overview. Many other functions,such as fil
tering,enabl
e you to make a fl
exibl
e
eval
uation. You eval
uate the document fl
ow using the transactions DP99A,DP99B and
DP99C. These transactions differ onl
y in their sel
ection options.
"
Document Fl
ow Eval
uation for Bil
l
ing Request
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can displ
ayexpenditures bil
l
ed
using the document fl
ow from a debit memo request or a credit memo request. W hen you
use the transaction DP98,you receive a corresponding l
ist with al
lbil
l
ed resource items
for the bil
l
ing request. You have to enter the debit memo request and credit memo request
number respectivel
y,in the sel
ection screen.
"
"
"
"
"
New Anal
ysis Program for DIP Profil
e
Further detail
s see chapter 3.1.7
SAP AG
Page 80 of 89
"
"
"
Enhancement Col
l
ective Processing for Resource-Rel
ated Bil
l
ing
Further detail
s see chapter 6
"
Resource-Rel
ated Down Payments and Bil
l
ing Pl
an
Further detail
s see chapter 2.1.5
"
InitialScreen of RRB
Further detail
s see chapter 2.3
"
"
"
SAP AG
Page 81 of 89
"
"
SAP AG
Page 82 of 89
"
SAP AG
Page 83 of 89
SAP AG
Page 84 of 89
"
"
New fil
ter criteria:For this issue,you have now a wide varietyof possibil
ities. First you can
add sel
ection criteria in the source sel
ection part of the DIP profil
e. Next you can add
database sel
ection criteria or fil
ter the data after database sel
ection in enhancement
AD010002. It is al
so possibl
e to remove obj
ects from the sel
ection in enhancement
AD010001. Final
l
y,you can use enhancement AD010007 in combination with the sign '
DI
w/Material
'in the usage part of the profil
e to remove al
ldynamic items without a material
determined.
"
"
"
Create a debit memo request with main item and sub-items:This can be repl
aced by the
business process with the service product.
SAP AG
Page 85 of 89
"
"
Of course,you can al
so use the BAdIs described in chapter 4.3 instead of the corresponding
enhancement/exit.
SAP AG
Page 86 of 89
8 Figures
Figure 1:Business Process of Resource-Rel
ated Bil
l
ing ........................................................ 7
Figure 2:Business Process of Resource-Rel
ated Resul
ts Anal
ysis ...................................... 8
Figure 3:Business Process of Quotations for Service Orders................................................ 9
Figure 4:Business Process of Pricing for Proj
ects Based on an Inquiry............................. 13
Figure 5:Business Process of Pricing for Proj
ects in Proj
ect Buil
der .................................. 14
Figure 6:Business Process of Update of Pl
anned Revenues for Operative Proj
ects........ 15
Figure 7:Overview of the Dynamic Item Processor ............................................................... 18
Figure 8:InitialScreen of Resource-Rel
ated Bil
l
ing Request DP91 .................................... 20
Figure 9:DIP Profil
e:Usage ..................................................................................................... 25
Figure 10:DIP Profil
e:Use of Characteristics ........................................................................ 28
Figure 11:Exampl
e Set for Structuring..............................................................................28
Figure 12:Structuring Using Singl
e Val
ues ............................................................................ 31
Figure 13:DIP Profil
e:Structuring by Characteristics ........................................................... 32
Figure 14:DIP Profil
e:Sources................................................................................................ 33
Figure 15:DIP Profil
e:Sources - Sel
ection Criteria............................................................... 34
Figure 16:DIP Profil
e:MaterialDetermination - Indicator
Use Quantity
............................ 35
Figure 17:DIP Profil
e:MaterialDetermination - Criteria ....................................................... 36
Figure 18:DIP Profil
e:MaterialDetermination Indicator Transfer Quantities /Costs...... 38
Figure 19 Criteria Exampl
e:MaterialDetermination .............................................................. 38
Figure 20:Set for Spl
itting Costs ......................................................................................39
Figure 21:Profil
e Check (ODP2A) ........................................................................................... 44
Figure 22:Cal
ling Sequence of Customer Enhancements.................................................... 52
SAP AG
Page 87 of 89
9 Tables
Tabl
e 1:Bil
ling Form and Rel
evance for Bil
l
ing...................................................................... 10
Tabl
e 2:Structuring Exampl
es.................................................................................................. 30
Tabl
e 3:Criteria Exampl
e:MaterialDetermination Criteria ................................................... 40
Tabl
e 4:Criteria Exampl
e:Enhanced MaterialDetermination Criteria ................................ 41
Tabl
e 5:Characteristics............................................................................................................. 42
Tabl
e 6:Primary Customer Enhancements............................................................................. 50
Tabl
e 7:Secondary Customer Enhancements (Sel
ection).................................................... 51
Tabl
e 8:Availabl
e Sel
ection Fiel
ds for EXIT_SAPLAD1C_002............................................ 58
Tabl
e 9:Processing Information of Dynamic Items for EXIT_SAPLAD15_015................... 67
Tabl
e 10:Node Types of Structuring ....................................................................................... 70
Tabl
e 11:Parameter I_MODE of EXIT_SAPLAD14_006...................................................... 73
Tabl
e 12 :Parameter ET_VALUES of EXIT_SAPLAD14_006............................................... 74
SAP AG
Page 88 of 89
"
"
"
"
"Figure 22:Cal
l
ing Sequence of Customer Enhancements"revised.
"
"
"
"
"
"
"
"
"
"
"
"
"
"
Chapter 6. Col
l
ective Run of Resource-Rel
ated Bil
l
ing (DP95,DP96,DP97) revised
"
SAP AG
Page 89 of 89