Dip Profiles Documentation

Introduction to the Dynamic Item Processor
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
Dietm ar-Hopp-Allee 16
D-69190 W alldorf
SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 1 of 89

Copyright ! 2007 SAP AG. All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any means
without the prior written consent of SAP AG.
The information contained in this document is subject to change or revision without prior notice.

Contents
1 INTRODUCTION ...........................................................................................................5
2 OVERVIEW....................................................................................................................6
2.1 Business Processes ...................................................................................................6
2.1.1 Resource-Related Billing of Sales Documents, Service Orders and Projects.......6
2.1.2 Resource-Related Results Analysis......................................................................7
2.1.3 Quotation Creation and Resource-Related Billing for Service Orders ..................8
2.1.4 Pricing for Projects ..............................................................................................12
2.1.5 Resource-Related Down Payments....................................................................16
2.2 TechnicalProcess ....................................................................................................17
2.3 InitialScreen of DP91...............................................................................................20
2.4 The New User Interface ............................................................................................21
2.5 Archiving CO Line Items ...........................................................................................23
3 CUSTOMIZING............................................................................................................24
3.1 DIP Profil e (ODP1) ...................................................................................................24
3.1.1 Usage .................................................................................................................24
3.1.2 Characteristics ....................................................................................................26
3.1.3 Source Selection.................................................................................................32
3.1.4 Material Determination ........................................................................................35
3.1.5 Criteria for Source Selection and Material Determination ...................................38
3.1.6 Characteristics Filled by Standard Sources ........................................................42
3.1.7 Profile Check (ODP2) .........................................................................................43
3.1.8 Does and Don'ts if Changing the Profile .............................................................44
3.2 Apportionment Reason (ODP3) ................................................................................45
3.3 Cost Condition (ODP4) .............................................................................................45
3.4 Material s ...................................................................................................................46
3.5 Customizing in SD ....................................................................................................47
3.5.1 Sales Document Types.......................................................................................47
3.5.2 Item Categories...................................................................................................47
3.5.3 Item Category Usage and Item Category Assignments ......................................47
3.5.4 Copy Control .......................................................................................................48
3.5.5 Reasons for Rejection.........................................................................................48
3.5.6 Pricing and Pricing Procedure.............................................................................49
3.6 Customizing in Resul ts Anal ysis...............................................................................49
4 CUSTOMER ENHANCEMENTS .................................................................................50
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

4.4.3 Filter or change the selected data (EXIT_SAPLAD15_010) ...............................59

4.5 Defining and Popul ating Characteristics...................................................................60
4.5.1 Overview .............................................................................................................60
4.5.2 Independent Characteristics (CI_ATTRI2, EXIT_SAPLAD12_003) ....................60
4.5.3 Dependent Characteristics (CI_ATTRD, EXIT_SAPLAD12_004).......................61
4.6 Create User-Defined Sources (EXIT_SAPLAD15_005) ...........................................63
4.6.1 Overview .............................................................................................................63
4.6.2 Implementation of EXIT_SAPLAD15_005 ..........................................................63
4.7 Change Processing information (EXIT_SAPLAD15_015) ........................................66
4.8 Change Texts of Dynamic Item Structuring (EXIT_SAPLAD13_001) .......................68
4.9 Change Data in Sal es Document Items....................................................................70
4.9.1 Change Item Data...............................................................................................70
4.9.2 Add Partners .......................................................................................................72
4.9.3 Change Pricing Data ...........................................................................................72
4.10 Other Exits in SD ...................................................................................................73
4.11 Menu Exit (EXIT_SAPLAD14_006,EXIT_SAPLAD14_008)..................................73
4.12 Exits for Resul ts Anal ysis ......................................................................................75
4.13 Del ete Messages in Col lective Processing (BAdI AD01_RRB_COLLECTIVE1) ...75
4.14 Creating "Sol utions"with Customer Exits ..............................................................76
4.14.1 Use of service operation and short text in the debit memo request .................76
5 DIFFERENCES BETWEEN RELEASES.....................................................................80
5.1 New Functions in 4.7 ................................................................................................80
5.2 New Functions in 4.6C..............................................................................................81
5.3 New Functions in 4.6A/B ..........................................................................................82
6 COLLECTIVE RUN OF RESOURCE-RELATED BILLING (DP95,DP96,DP97)..83
7 CONVERSION FROM OLD TO NEW RESOURCE-RELATED BILLING (DP70).......84

7.1 Conversion of Bill
ing Fl
ow and Customizing ............................................................84
7.2 Conversion of Customer Enhancements ..................................................................85
7.3 Changes to the User Interface..................................................................................86
8 FIGURES.....................................................................................................................87
9 TABLES ......................................................................................................................88
10 CHANGES TO THIS DOCUMENT ...........................................................................89

10.1 Version 1.1.............................................................................................................89
10.2 Version 2.0.............................................................................................................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
exible handl ing of resource-related bil
ling. 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 consultants and people in companies customizing the dynamic item
processor. Additionall
y,this paper describes the wide range of possible enhancements for this
processor offered by customer enhancements to adapt the technicaltool to the company’ s
business processes.
The focus is on the technicalimplementation and customizing and not so much on the business
process for which there is only a short overview at the beginning. The technicalsettings are
cl
arified byexampl es of realbusiness processes.
Allfunctions 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.

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 just the powerfulpricing engine is used for generating pricing information. The main
processes covered by this toolare resource-rel ated bil ling and the calcul ation of sal
es prices. The
DIP can process singl e objects l
ike service orders or sal es orders but it can al so work on compl ex
structures l
ike projects or order networks. The processes are described in the fol lowing chapters.
2.1.1 Resource-Rel
ated Bil
ling of Sal
es Docum ents, Service Orders and
Projects
In Resource-rel ated bill

ing,the DIP is used to sel ect the resources actual ly used of a service
order or a sales order to generate debit memo requests. As this is very often a periodic process,
resource-related bil
ling keeps a document fl ow of the values al
ready billed or rejected . Only the
open val ues,cal culated by subtracting the al
ready billed and the rejected val ues from the total
values,are offered to the user onl
ine.
You can define which val ues should be billed, postponed, or rejected. You can al so define
manualprices for the bil ling. 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 rejected in previous runs, you can undo the rej ection via menu path:
Edit ! Undo Rej
ection. In the fol
lowing 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 possible 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 sales
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 bill
ing process incl
udes not only singl
e obj
ects (sales 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 sales order item,which isn’
t a bil
ling W BS el
ement the system is
looking upward in the hierarchy towards a bill
ing W BS Element. In standard,al
litems,which are
processed in DIP at the same time,have to own the same DIP Profil e. A&D solution is different,
there an enhancement was made to process severalitems with different DIP Profil e at the same
time.

For the bil

ling of service orders some additionalspecial
s has to be observed. They are described
in chapter 2.1.3.
Sales order
Sal
es order item(s) Service order
(al
lsal
es order items)
Yes Saved data exists? No
Read data from

Load saved data
sources
Create debit memo

Yes
request immediatel
y?
No
Edit onl
ine
Edit onl
ine
Sal es price
Sal
es prices Create debit
Save data basis Debit memo
(Conditions & memo request
(Dynam ic request
dynam ic items)
items)
Saved data
Debit memo request
Refresh data
Figure 1:Business Process ofResource-Related Billing
From SAP R/3 Enterprise 4.70,you can process resource-rel

ated bil
ling for internalorders with
revenues.
Direct resource-rel ated bill
ing is now possible for internalorders with revenues using a sal es
document without cost col lectors. The process is based on the current sol ution for resource-
related bil
ling for projects/W BS elements.
To use the new functions,you must define in Customizing for sales document items that account
assignments are possible for internalorders. To do this,go to:
Transaction SPRO ! SAP Reference IMG ! Control
ling ! Product Cost Control
ling ! Cost
Object Control l
ing ! Product Cost by Sal
es Order ! Control of Sal es-Order-Related
Production/Product Cost by Sal
es Order
2.1.2 Resource-Rel
ated Resul
ts Anal
ysis
Resource-related results 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:

1. Derive Cost of Sal es from Resource-Rel ated Bill

ing of Dynam ic Item s (valuation m ethod 14).The cost
of sales (COS) is the sum of the bil l
ed costs and the rej ected costs. The work in process (W IP) is the
cost not yet bil
led. The revenue affecting net incom e is the actualrevenue.
2. Derive Revenue from Resource-Rel ated Billing and Sim ul

ation of Dynam ic Item s (valuation m ethod
15). COS is the sum of the bil l
ed costs,the costs not yet bill
ed,and the rejected costs. The sim ulated
revenue for the costs not yet bill
ed is updated as revenue in excess of bill
ings. The revenue affecting
net incom e is the actualrevenue plus the revenue in excess of bil
lings.
COS and revenue affecting net income can be transferred to profitabil ity analysis using
settl
ement. The inventory val ues W IP and revenue in excess of bil
lings can be posted to financial
accounting and profit center accounting using settl
ement.
Note that the bil l
ed costs in resource-rel ated results anal ysis differ from the billed costs in
resource-rel ated bil
ling. Bil
led costs in resource-related bil
ling are costs transferred to debit/credit
memo requests. In resource-rel ated resul ts analysis,the costs are bil l
ed in a period if there is a
debit/credit memo and the posting date of the actualrevenues is inside the period of resul ts
analysis. Otherwise,the costs are not yet bil led.
Resource-related resul ts anal ysis differs in one point from other methods of resul ts anal ysis.
Costs are only considered as W IP or COS,if they are sel ected during resource related bil
ling. If
you narrow the selection,i.e. if you want to excl ude the overheads from the billing process,they
do not appear as W IP or COS in resul ts analysis.
Resource Related Billing

DI-Processor Debit Debit
Determ ination of Mem o Req. Mem o
open values
Objects Actual RRB Actual

Costs Doc. Flow Rev.
DI-Processor Results Settlem ent

Determ ination ofbilled Analysis Profitability Accounting
and unbilled costs (CoS,WiP) FinancialAccounting
Resource Related Results Analysis
Figure 2:Business Process ofResource-Related Results Analysis
2.1.3 Quotation Creation and Resource-Rel

ated Bil
ling for Service Orders
2.1.3.1 Normal Process for Quotation Creation
Quotations for service orders are created based on planned costs. The rest of the process is
simil
ar to resource-related bil
ling. You can change onl
ine which costs should be copied to the

pricing and the quotation. Of course,it makes no sense to say costs shoul d be bill
ed now,l ater,
or never. The changes affect onl y the basis for the calcul
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 ly,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
ling: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-related bil
ling'of the DIP profil e, but no actualresource-rel ated bil
ling takes
place.
Service order
Expl
icit creation of new pricing
Saved pricing exists? No
Yes:onl
yone Yes:mul
tipl
e
Sel
ection onl
ine
List of
pricings for
service order
Load pricing Create new pricing
Edit onl
ine
Sal es price Sal es prices
basis (conditions Quotation for service
Yes
(dynamic and dynamic order exists?
items) items)
No
Create quotation
Yes
immediatel y?
No
Edit onl
ine
Edit onl
ine
Sales price Sal
es prices
Save pricing basis (dynam ic (conditions and Create quotation Quotation
items) dynamic items)
Pricing for service

Quotation
order Refresh pricing
Save planned
revenues
Figure 3:Business Process ofQuotations forService Orders

2.1.3.2 Quoting and Billing of Service Products
The quoting and bil ling of service products is a specialbusiness process. The system creates a
debit memo request or a credit memo request with the service product as main item and the
resources to be billed as sub-items. The service product is either defined in the service order or it
is taken from the materialnumber of the sal es order items. W hether the main item or the sub-
items are relevant for bil
ling is defined by the billing form entered in the service order or the sal
es
order item:
" Fixed rate:The main item is normal l
y relevant for bil
ling. The price can come either from
automatical lydetermined pricing conditions or as a resul t of the summarized costs of the
sub-items (if the customizing is set so that costs are transferred to the debit/credit memo
request items).
" Costs:The sub-items are normal ly relevant for bil

ling. The price is the sum of the prices of
these items,which can be determined by pricing conditions or by their costs (if the
customizing is set so that costs are transferred to the debit/credit memo request items).
The dynamic item characteristic 'Product' has to be set as rel

evant to activate this business
process (see chapter 3.1.2).
Untilrelease 4.6C onl y one sal es order item with service product can be processed at a time. As
of SAP R/3 Enterprise Core 4.70 you can create a bil l
ing request to mul tipl
e sal
es order items
with service products. The individualitems can al so have different bill
ing forms at the same time.
It'
s not possible to create credit memo requests with fixed rate bil
ling.
2.1.3.3 Billing Form and Relevance for Billing
W hen using the service product process, the bil ling form in the sal es document item or the
service order infl
uences the rel evance for bil
ling of the sales document items. W hen you combine
quoting and bil l
ing of service products,the rel evance for billing can differ from the description in
chapter 2.1.3.2. Tabl e 1 shows an overview for the rel evance for bil
ling of the sales document
items.
Quotation creation Resource-Related Billing

Billing Quotation exists Quotation not exists
Form Main Item Sub-item Main Item Sub-item Main Item Sub-item
Fixed Not Rel
evant Not Not Rel evant Not
Rate rel
evant rel
evant relevant rel
evant
Relevant (None)
Costs Not Relevant Not Rel
evant Not Rel
evant
rel
evant rel
evant rel
evant
None Not Rel
evant Not Rel
evant Not Rel
evant
rel
evant rel
evant rel
evant
Table 1:Billing Form and Relevance forBilling
The rel evance for bil l

ing is an internal date for determining the right item category type.
Therefore,not the rel evance for billing determines if an item affects the totalquotation or bil
ling
value. In fact,the setting of the '
Statisticalval
ue'fiel
d in item category,found by the item category
assignment,determines the rel evance of the item for the totalprice. For relevant items,an item
category must be found which defines a not statisticalitem. For not rel evant items,an item

category must be found which defines a statistical item. How to set up the item category
assignments is described in chapter 3.5.3.

2.1.4 Pricing for Proj

ects
There are three business processes for Pricing for Proj ects. The first one is the pricing based on
an inquiry in SD and is run in its own transaction (DP81). The second one is the pricing based on
Easy Cost Pl anning integrated in the Proj ect Builder. The third one (transaction DP82) is pricing
similar to DP81,but without inquiry (avail able since rel ease R/3 4.6C). The needed data for DP82
is taken from proj ect definition as it’
s done in the second business process. The processes use
the DIP but the pricings created in Proj ect Builder cannot be edited in DP81 and vice versa.
2.1.4.1 Pricing for Projects Based on an Inquiry
As the titl
e of this chapter says,it is necessaryto create an inquiry which is account assigned to a
project before performing any pricing for proj ects. From the inquiry,the system takes the DIP
profil
e (entered in the inquiry item under Sal es B) to perform the pricing. Other data is taken from
the header,such as the partners and the sal es area for the determination of conditions and for
the quotation created l ater.
It is possible to create pricings not only for operative projects,but also for simul
ations. The only
limitation is that there must be at least the bil
ling W BS el ements in an operative project and the
pl anned revenues from the quotations must al ways be updated to the operative proj ect. To get
pl anned revenues for a simul ation,you have to use bil l
ing plans which can be created out of the
pricing.
There can be severaldifferent pricings for a proj ect in paral
lel
. The pricings are assigned to the
bil
ling W BS elements. The handl ing of different inquiries and existing pricings is supported bythe
system in such a way that you do not have to remember any inquiry numbers or pricing numbers.
You can work with proj ect definitions. If there is onl y one inquiry assigned to the proj ect,the
system uses this inquiry and does not displ ay a popup or things l ike that. The same happens if
you have onl y one saved pricing for your proj ect:It is opened for editing. If there are more than
one pricing,the system offers a popup where the users can sel ect the one to be l oaded.
There can be also severaldifferent quotations,but if you have activated the update of pl
anned
revenues from quotations,you have to consider chapter 2.1.4.3.

Expl
icit creation of new pricing
Bil
ling W BS Inquiry
Proj
ect defintion Inquiryitem(s)
element (al
linquiryitems)
Pricing exists for proj

ect
No
definition or W BS element?
Sel
ection onl
ine
Pricing exists for
inquiryitems? List of inquiries
for proj ect def.
Yes:mul
tipl
e or wbs el ement
No
Yes:mul
tipl
e
Sel
ection onl
ine Create new pricing
Yes:onl
yone List of
pricings
Yes:onl
yone
Load saved pricing
Edit onl
ine
Create debit memo
Yes Quotation
request immediatel
y?
No
Edit onl
ine Create Quotation Quotation
Sales price Sal

es prices
Save pricing basis (conditions and
(dynamic items) dynamic items) Create/
edit onl
ine
Bil
ling pl
an Bil
ling pl
an exists for
W BS el em ent?
Saved pricing
Refresh Pricing
Update pl
anned
No
revenues
Figure 4:Business Process ofPricing forProjects Based on an Inquiry
2.1.4.2 Pricing for Projects Based on Easy Cost Planning in Project Builder
Besides the process in the previous chapter,there is another business process for Pricing for
Proj ects using the centralmaintenance toolfor proj ects in R/3 - the Project Buil
der. The goalof
this integrated approach is to offer a facility for creating project structures,calcul
ating costs (using
Easy Cost Pl anning),and cal culating sal es prices in a singl e transaction.
Changes of the structures are refl ected in costing and pricing. Al
so changes of costing are
updating pricing if switching the view.

Simulations
Structures Billing
plan Transfer
Easy Cost
Planning Pricing
Figure 5:Business Process ofPricing forProjects in Project Builder
The big advantage of the pricing in Proj ect Builder is that there is no l
onger any need to create a
separate inquiry in SD. Some additionalval ues have to be maintained in the proj ect definition to
get the pricing to work. In the controldata section,the sal es area (sales organization,distribution
channel ,division) and the DIP profil e must be set. Additional l
y a sold-to party must be added to
the partners which requires a partner determination procedure. If you add other partners to the
project definition,they are also copied to the simulated or finalquotation. Note,however, that no
partners from the W BS el ements are copied.
In the DIP profil
e,onl y the source 'Easy Cost Pl anning'can be used for this process. As a resul
t,
in Project Builder it is not possible to perform a pricing based on costs pl anned on networks,
orders or the cost planning for projects (transaction CJ40).
If you copy a proj
ect to another proj
ect,the sal
es pricing isn’
t copied as wel
l.
Like in transaction DP81,you can create or update a bil l
ing plan based on your cal culated sales
price. The bill
ing plan wil
lbe saved even if you do not save the pricing for your proj
ect. The bil
ling
plan can al so be accessed from the Proj
ect Builder.
In Project Builder,each proj ect can have onl y one pricing. This is easier for the user to handl e,
but it means you must transfer proj ects to another simul ation if you want to create a different
pricing whil
e keeping the ol d one. Easy Cost Pl anning and the Pricing for Proj ects are transferred
together with the structures.

2.1.4.3 Update of Planned Revenues for Projects
The update of planned revenues for projects is not specificall

y related to the pricing,but as the
pricing is a way to cal
culate planned revenue automatical ly,it should be mentioned how the
system updates the planned revenues.
Process 1:with Billing Plan
Pricing forProjects Quotation(s) Manual
anned rev. total

sts
co
ed
nn
Pla
Pl
Project Pl
anned revenues on tim escal
e Billing Plan Sales order(s) Manual
M anual
an
an
ing Pl
ing Pl
Create Bill
ete Bill
Del
Process 2:without Billling Plan

Pricing forProjects
sts
d co
ne
an
Pl
Project Pl
anned revenues total Quotation(s) M anual
Pla
nn
ed
rev
en
ue
st
ota
l
Sales order(s) M anual
Figure 6:Business Process ofUpdate ofPlanned Revenues forOperative Projects
If you are using simul ations,the only way to get pl

anned revenues is by using bil
ling pl
ans. If you
have operative proj ects,the pl anned revenues can come either from sal
es documents (quotations
and sal es orders) or from billing pl
ans.
Thus there are two processes for the update. The first is the one with bil l
ing plans. If a W BS
element has a bil l
ing plan,the pl anned revenues come from the bil l
ing pl an distributed on the
time-scale. Pl anned revenues from sal es documents are not updated for the W BS el ement. The
second process is without bil ling plans. If the W BS el ement does not have a bil l
ing pl an,the
planned revenues are updated from the sal es document. The period of the pl anned revenues is
the period of the billing date in the quotation. The update happens onl y if the update for sal es
documents is activated in the customizing for proj ects. So,the creation or del etion of bil
ling pl
ans
is the switch between these two processes.
Another point is the CO version,to where the costs and revenues are updated. Revenues from
sales documents are al ways updated to version 0,but it is possible to define a version to where
the costs cal
cul ated using Easy Cost Pl anning are updated. You can al so choose a version for
the planned revenue update. If you set the switch,the update is to the same CO versions as the
costs from Easy Cost Pl anning,otherwise the planned revenues are updated to CO version 0.

You can find this switch at the same point in customizing l

ike the setting of the CO version for
EasyCost Planning.
2.1.4.4 Additional Programs for Pricing for Projects
There are two additionalprograms for pricing for proj

ects,which you can find in OSS notes.
1. Report STRUCT_QUOTATION_FROM_PRICING (Note 319646)
W ith this report,you can create a structured quotation for your proj ect pricings based on an
inquiry. The report creates main items for each of your inquiry items and appends the items from
your proj ect pricing as subitems.
You can enter a proj ect definition and a version key as parameters. The system searches al l
pricings for this proj
ect and shows a l ist of them on screen. You can select those pricings for
which you want to create a structured quotation. After creating the quotation,a resul tlist of the
quotation is displ ayed including al l errors occurred in processing. By clicking the quotation
number,the quotation wil lbe displ ayed.
W ith the transaction DP81 you can create a new sal es pricing. The items of this sal
es pricing are
assigned to the inquiry items by report “STRUCT_QUOTATION_FROM_PRICING”. The items of
the inquiry show a net val ue of 0. Below the inquiry items you can find the quotation items,which
are cal l
ed “Lower – Level– Items”in this context. In other words,you can see which inquiry item
causes the corresponding quotation item. Via col umn “Higher LevelItem”you can al so determine
the bel onging of the quotation items to the item of the inquiry.
Please be aware of how the system creates the quotation. It is not a singl e transaction unit.
Instead,the system creates a quotation with the first main item and its subitems. This unfinished
document is saved. The other main items and subitems are appended l ater. Since there are
severalcommitted database updates,an error between these updates can l eave an incompl ete
document in your system. If this happens,pl
ease del ete the document.
2. Report QUOTATION_FROM_PB_PRICING (300936)
In Rel ease 4.6C,pricing for projects is integrated into the Project Builder. For technicalreasons,it
is not possible to create a quotation from this integrated process. W ith this report,you can create
a quotation for the proj ect pricing created in the Proj ect Buil der. An item is created in the
quotation for each item of your pricing. You can enter a proj ect definition and a version key as
parameters. The system searches the pricing and creates the quotation. Afterwards, the
quotation is opened in edit mode. Since 4.70 it is possibl e to create a quotation in CJ20N directl
y.
2.1.5 Resource-Rel
ated Down Payments
As of SAP R/3 Enterprise PLM Extension 2.00 you can use the bil ling pl
an and down payment
request together with resource-rel
ated bil
ling. You can use the bil
ling pl
an to create DMRs or
down payment requests and DMRs in the desired order.
This enhancement offers you the fol
lowing advantages:
" You can create resource-rel
ated down payment requests based on work performed.
" You can use the bil

ling pl
an in the sal
es order to create DMRs.

Pl
ease pay al
so attention to the fol
lowing notes:
" Resource – rel
ated down payment processing (858877)
" Consul
ting note for resource – rel
ated down payments (858702)
" Customizing for the resource – rel

ated down payments (858703)
2.2 TechnicalProcess
The dynamic item processor makes a sel ection,summarization and grouping of data over several
l
evels. 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 coll
ect actualand/or pl anned revenues. These are in most cases service orders
or sales orders. The entry obj ect can be also the starting point of a compl ex "bil
ling structure",
which means,that al lobjects 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 example,for resource-rel ated bil
ling) 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 profile.
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 selection 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
directly 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
selection 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
selected data has a number of characteristics and val ues. In the DIP profile,you specify which
characteristics are relevant 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 bill
ing). Allnon-relevant characteristics are cleared and onl y the
relevant ones are used to define a characteristic vector for each source data l ine. The values 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 possible to
have dynamic items with quantity or amount onl y and also with both quantity and amount. So
sources can be roughl y differentiated into quantity-based sources (like statisticalline 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 rules are specified. These assignment rules are specified based on
one or more rel
evant characteristics.

In resource-related bil
ling,the next step is the selection of the al
ready bil
l ues. The total
ed val
values are balanced wi th the docum ent flow to determ ine the open values. The open values
can be then transferred to the bil
ling 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 sales document are summarized. Al l
dynamic items with equalmaterialnumber (from the materialdetermination) are summarized in
one sales document item. This summarization can be suppressed dependent on the materialor
the characteristics.
SD Dynam ic Item Processor
Sales doc. Source item s Dynam ic Item s Head Conditions

e.g.
-Sales Order, Sales docum ent item s
Characteristics Values MaterialA
-Service Order, Item 1
-Contract ... Item 1
Characteristics Values MaterialB
Item 2
Characteristics Values MaterialA MaterialA Conditions
Can be also Characteristics Values MaterialC

assigned to MaterialB Conditions
# Projects Characteristics Values MaterialC
# Internalorders MaterialC Conditions

Characteristics Values MaterialA
# Service orders
Item 2
Characteristics Values MaterialD
Characteristics Values MaterialA MaterialD Conditions
Characteristics Values MaterialD MaterialA Conditions
Sales Price Basis Sales Price

Sources can be
# Actualvalues
Cr
ea
# Planned values e.g. Debit Mem o

te
# Userdefined sources Request

sa
Sales Doc.
SD
les
Mat. A
do
cu
Mat. B
m
Mat. C
en
Mat. D
t
Mat. A
Figure 7:Overview ofthe Dynam ic Item Processor
In resource-related billing,the sales docum ent item are then distributed to the debit m em o
request or the credi t m em o request,if both sales document types are specified in the DIP
profil
e. If the quantity is negative,the sales document item is credited to the customer. If no
quantityis availabl
e,the sal es document item is credited if the amount is negative.
Both the quantity and the am ount can be copied to the sales docum ent item . For the
quantity,a sign in the materialdetermination line must be set. For the amount,a condition for
costs must be defined for the sal es document type. If the transaction currency is avail
abl
e,this
amount is copied to the sal es document item using the condition for costs. Otherwise the CO
area currency is used. However, it is al so possibl e to use always the CO area currency by
deactivating the bl
ocking of summarization over the transaction currency.

The system then sim ul ates the sales docum ent which is l
ater created. By simul
ating the sal
es
document the automatic conditions are determined. Al so,allauthorization checks are performed
for the creation of the sal
es document type.
ine processing,the user can change the val
In onl ues to be copied to the sales document in the
sales price basis view and the prices in the pricing procedure in the sal es price view. Every
change (for exampl e,of the amount to be bil
led) immediately updates the calculated price.
Finaly,the user performs the creation ofthe sales docum ent. Al
l lmanualprices are copied to
the sales document. In resource-rel
ated bil
ling,the document fl
ow for bil
led and rej
ected val
ues is
updated.

2.3 InitialScreen ofDP91
If you start transaction DP91,the initialscreen in figure 9 is shown. In this initialscreen you have
to enter a sal es document or contract number. You can al so use the search functional ity to find
the corresponding sal es order or contract. To reduce the number of cost records sel ected and
processed,you can set the period from which onwards the cost records are sel ected. This coul d
improve the performance significantl y. To do this,choose menu Extras ! Set Period.
A new pop-up window cal l
ed “Set Period”appears in which you enter the val
ues in “From Period”
and “From FiscalYear”. For more detail s on always displ ay “From Period” pay attention to
modificatoin note 433462.
Figure 8:InitialScreen ofResource-Related Billing Request DP91
The user parameter “Process Open Item Onl y”indicates that onl y the source data record that
have not been ful l
y bil l ed are processed. A dynamic item is not ful l
y bill
ed untilthe source
resource minus bill
ed and rej ected resources equal s zero. If the indicator is not selected,al l
dynamic items are processed. Unfortunatel y,to find out which records are ful ly bil
led,allrecords
have to be sel
ected first.
Together with “Process Open Items Onl y”please take notice of note 387659 for detail
s on set- /
get-parameter “Rej ected expenses as open items”. If the parameter is maintained with X,the
system considers rejected expenses to be open so that dynamic items with rej
ected amounts are
processed as wel l
.

2.4 The New UserInterface
As of Release 4.6,the user interface has been compl etel

y overhaul ed. The new and forthcoming
controltechnique was used to give the user a better overview of the severalsteps of the process.
The generalfunctionality of the user interface is described in the documentation.
A screen is now avail
abl e for the hierarchicaldispl
ay of the dynamic items cal
led “Expenses”.
Another screen shows the sales document structure,call
ed “Sales Price”.
In the Expense screen,you define from the structuring which and how many of the items are to
be bill
ed,rej
ected,and postponed. This result wil
linfl
uence the sal
es document.
In the Sales Price screen you define conditions for each item in the sal
es document. Starting from
Rel ease 4.6C,you can al so access the dynamic items.
The fol
lowing information is val
id for both screens:
" In expanding the hierarchicalstructure the system fol
lows this l
ogic. The same goes for
the col
lapse l
ogic:
$ Expand the node of this icon for one l

evel(The system s keeps in m ind the expand
l
evel. So,if there was al
ready a deeper expand,this expand l evelis shown again.)
$ Expand the com pl

ete sub tree of the sel
ected node.
$ Expand the com pl

ete tree.
" To adj
ust the width of any col umn simpl y cl
ick the header of the col
umn. This feature is
al
so valid 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.
" To store the sequence and the width of the col

umns,use the drop-down menu from the
l
ast button of the overview tree . This functional
ity is buil
t in Rel
ease 4.6C or see note
202603.
" The paging buttons directl

y above the hierarchy work for the tree onl
y. To page in the
tabl
e,use the paging buttons next to the tabl
e.
" The search function finds any entryin the hierarchy displ
aybut onl
ytext entries in the
tabl
e.
" Starting with Release 4.6C,it is possibl

e to refresh the stored data with new val
ues by
selecting from the menu “Ressource-rel . bil
ling”the entry “Refresh … ”.
" The old function for simul

ating a sal
es document is in the “Goto”menu (“Simul
ate sal
es
and distribution docs”).
The fol
lowing is val
id for the “Expenses”screen.
" To access the data of a characteristic,doubl e-click the textualdescription in the hierarchy
displ ay. Afterwards this characteristic is shown in the first l
ine of the tabl
e view. It wil
lstay
in this first l
ine,regardl
ess of paging down or up.

" Onl
ythe sel
ected characteristic and its direct successors are shown in the tabl
e view.
" If there is no textualdefinition for a characteristic,one wayto access the data is to select
the icon of the characteristic and doubl e-cl
ick it. The other way is to change the displ
ayed
text using the “Description”tab page in the settings screen.
" In the tabl

e view for “Amount”,“Quantity”or “Percentage”you maydoubl e-click one of the
activated columns of “to be bill
ed”,“postponed”or “rejected”. This deactivates the column
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.
" W ith the menu entry“Undo rej ection”in the “Edit”menu,it is possibl e to cal
lback
rej
ections made in earl ier cal
ls of the resource-related bil
ling process. A new screen
containing the rej
ections is shown. You can simul ate your entries. The screen behaves in
the same wayas the main screen.
" You can switch between different hierarchies without accessing the customizing with the
menu entry “Switch hierarchies … ”from the menu “Edit”. Allentries 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 “to”l
evel
s
$ Show or hide singl
e val
ues
If you sel
ect the user-defined settings and hit the settings are val
id for this cal
lof the DIP
only. 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 displayed on the tab screens,the fol
lowing information is al
so stored in the
database and applied 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 selected for the expense screen and the sal
es price screen
" W hich col

umns in the tabl
e view are active for entry

2.5 Archiving CO Line Item s
As of SAP R/3 Enterprise Core 4.70 you can archive CO l ine items for orders and proj
ects when
you bill them according to resources if you maintain the fol lowing customizing transaction
correspondingly. In this way,you can significantl
y improve the performance of your entire system
by reducing the number of records selected via source actualcosts – l ine items.
To be abl e to use the enhanced archiving function,you must enter residence times for the CO
l
ine items and residence times for dynamic item processor sources (DIP sources). To do this for
DIP sources, use the activity Residence Time of the DIP Source in the IMG for creating
quotations and bil
ling:
Transaction SPRO ! SAP Reference IMG ! Proj ect System ! Revenues and Earnings !
Integration with SD Documents ! Creating Quotation and Proj ect Bil
ling ! Residence Time of
the DIP Source. (Examples are given in documentation to customizing point).

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
also considered when setting up the business processes. As the DIP uses material s,allsettings
for them are al so important when working with the DIP. A smal ler part is the set-up of results
anal ysis.
This paper focuses on the set-up of the DIP profil
e and rel
ated customizing points.
3.1 DIP Profile (ODP1)
The DIP profil e contains the most important customizing for the DIP. Here,you define which data
is read,how this data is summarized,and how the items in the sal es document are created. The
DIP profil e itsel
f must be entered in the service order,the sales order item (in detailscreen '
Sal
es
B') or in the project definition.
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 possible to set up a profile with only 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
sales 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
correctly. You can find a short description of this in chapter 3.5.
The second usage is "Quotation Creation and Sales Pricing". Here,onl yone sales document type
can be specified for the created or simulated quotation. Normally,there should be no negative
items in this document,but if there are,the negative items are treated as they would be in the
singl
e document case of bil l
ing usage.
The 'W arranty check' indicator is onl y processed during bill
ing or quoting of a service order. It is
not processed during bil ling of service orders related to a sales 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 rejection is automaticall
yinserted in allcreated sales 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 selection screen (see 3.1.2.2). W hen the sign is set,you define
the items to be bil
led only bythe materialdetermination and not by the source sel ection.
Another business process where this sign is usefulis the bil ling of a project with different sal
es
document items - for exampl e,for bil
ling in different currencies or two different business partners.
Look at the fol
lowing situation:You set up two different order items account assigned to the same

W BS el ement. You want to bil ldifferent costs by using different profil

es with a different sel
ection.
If you billthe first items,everything l ooks allright,but when you bil lthe second item,the system
reopens the costs al ready bill
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 profiles and specify a materialdetermination,which finds a materialonl y for the costs you
want to billthrough this profile.
The disadvantages of this indicator shoul d also be mentioned. Performance can sl ow down
because the system reads data from the database,which in fact is not needed. Additional
ly,you
could 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.
Figure 9:DIP Profile:Usage

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
ly,the system distinguishes between two types of characteristics:
" Independent characteristics are fill
ed directl
y from the source data (if the source data
can provide the characteristic).
Exampl e:cost element,cost center.
" Dependent characteristics are derived from independent characteristics. For exampl
e,
the obj
ect type is derived from the obj
ect number.
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.
3.1.2.1 Use of Characteristics
At first,you have to define the relevant characteristics of your profile. Onl y these characteristics
are fill
ed from the sources. The relevant characteristics al so define the first summarization of the
source data to dynamic items. Al lsource data with equalrel evant characteristics is summarized to
one dynamic item. Therefore, the more characteristics are activated in the profil e, the more
dynamic items are created. This can resul t in a '
line item processing' :for exampl e,if you mark the
characteristics '
Document number'and ' Posting Row'as rel evant for source ' ActualCosts - Line
Items' ,you get one dynamic item for each CO l ine item . By selecting al lother characteristics
provided by this source as rel evant, you get the most detail ed dynamic items, but system
performance is not as good.
Most of the characteristics are optional,but some are required,dependent on the profil e usage. In
both cases,the ' Obj ect number' ,'Transaction currency' ,and '
Unit of measure'characteristics are
required. For usage ' Bil
ling and Resul ts Anal ysis', the '
Period' is an additional required
characteristic. This is because the document fl ow for resource-rel
ated bil
ling is stored periodical
ly.
The "Mat. Determination"indicator defines the characteristics to be used in the criteria for the
materialdetermination (see chapter 3.1.4). You can sel ect al
lcharacteristics here,but this may
make the materialdetermination unclear. It is better to sel
ect onl
y those characteristics you real
ly
need.
A very important indicator is the "No Summarization"indicator. Normal ly,the system summarizes
dynamic items to one sal es document item if they both have the same materialfound in material
determination. If this indicator is set,the system does not summarize two dynamic items if they
differ in this characteristic,even if they have the same materialnumber. Therefore,the indicator
has to be set for a characteristic if you want to use it in SD - for exampl e,to show the personnel
number in your invoices. If the indicator is cl eared,the system has to cl ear the characteristic in
the sal es document item because its val ue is clear. A better example is the characteristic "Unit of
measure"' . You can onl y show the quantity in the invoice,if you do not summarize using different
units (such as PC and H). Therefore, this indicator is set by defaul t for the characteristics
"Transaction currency"and "Unit of measure"but it can be switched off for both.

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 "Object number"is an internaltechnicalrepresentation of the processed cost obj ects.
It is a generic value never shown to the user on screen. However,it has the advantage of
processing al ldifferent object types (W BS elements,networks,sal es orders,service
orders,...) using onl y one fiel
d. Allconversions to representations familiar to the user are
done by the program,but it makes no sense to use the obj ect number in criteria for source
sel ection or materialdetermination.
" The "Material"has to be sel

ected as a rel
evant characteristic if you want to transfer it from
the source to the sal
es document item (see chapter 3.1.4 for this function).
" The "Product"invokes a quite different business process cal l

ed 'Quoting and Bil ling of
Service Products' . The system creates a dynamic item for the service product in the sales
order or service order and buil
ds a sal
es document structure with one main item and
severalsub-items. For more detail s,have a lookat chapter 2.1.3.2.
" The "Cost element"must be a rel

evant characteristic if you want to perform resource-
rel
ated results anal
ysis.
" The "Accounting Indicator"is used in confirmations for service orders. If it is copied to the
sal es document,it is shown automaticall
yunder view ' Sales 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.
" If you change the accounting indicator in resource rel ated bill
ing,the system updates the
pricing. If the change to the accounting indicator requires a new structure for the sal
es
document - for exampl e,if new items have to be created -,this is al
so done automatical l
y.
If you have defined other things,such as determination of the item category usage
dependent on the accounting indicator in a customer enhancement,you have to cal lmenu
item "Simul ate sal
es document"to activate the changes.
" If you are using the accounting indicator to determine different l

ine ids in resul
ts anal
ysis,
you shoul d know that the accounting indicator from the source data is used and not the
ones entered in the dial og of resource rel
ated bil
ling. Changes in dialog of resource
rel ated bil
ling affect onl
y one debit memo request created in the fol lowing.
" The "Billing Form"is taken from the input obj ect master data (sales order or service order).
It controls the business processes for bill
ing and quoting of service products. These
business processes can onl y workif the sales document item knows the bil ling form.
Therefore,pl ease markthe sign "No summarization"for this characteristic.
" Remember to sel ect the "No summarization"indicator for the "Transaction Currency"if you
want to copy the amount in transaction currency to the sales 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.

Figure 10:DIP Profile:Use ofCharacteristics
3.1.2.2 Structuring
W ith the structuring toolof the dynamic item processor,you can define a hierarchicaldispl ay of
your dynamic items on one or more of the profil e's relevant characteristics. It is even possible to
change this structure onl ine. Therefore,you have a toolfor the fl exibl
e displ ay of the costs to be
processed. In the DIP profil e,onl y the defaul
t structuring is defined. It is used when you start
working with an obj ect with this profil
e.
Sel ect the "Structuring"indicator if you want to use a characteristic for your hierarchicaloverview.
If you choose more than one characteristic you have al so to define a ' Sequence'number tel l
ing
the system in which order the structuring shoul d be done.

Next,you have to enter a set in the fiel d '

Set ID' . A set is a flexible structure for organizing
hierarchies al so used in report writer. To maintain sets,you can use transactions GS01 (create),
GS02 (change),and GS03 (view). You can al so use the green arrow in the col umn next to the set
name to create,change or displ ay a set. Just enter a set name and press the button. If the set
exists,it is opened for edit;otherwise you can create it. If you are in displaymode of customizing,
the set is opened in displ ay mode. Sets are always created with reference to a fiel d of a structure
or table in the ABAP data dictionary. Here,the program uses the structure AD01ATTR containing
allpossibl e characteristics of dynamic items. You shoul d also use this structure if you are using
the mentioned set maintenance transactions.
For some specialcharacteristics,you can al so use sets from accounting:cost element groups,
activity type groups, cost center groups or statisticalkey figure groups. They use the same
internaltechnol ogy but are marked as specialaccounting sets. Therefore,theycan be used in the
DIP,but sets generated for the same tabl e fiel
d using the generalset maintenance transactions
cannot be used in accounting.
The remaining fiel
ds define the exact outl
ine of your hierarchy:
" Partial sets tel
ls the system to expand the nodes of the set.
" Single values (Radio Button) displ

ays onl
y nodes for each val
ue of the characteristic.
" Upper Set shows the root node of the set onl
y.
" 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 only set the
Sequence and the To level. This is because the hierarchy is defined here external
ly,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 sales
order item. The profil
e has the cost
element as a relevant characteristic
and you al so want to structure
according to a cost el ement group.
The DIP creates four dynamic items
with cost elements 400000,405000,
410000,and 415000. Your set SET-
KSTAR is shown in Figure 11.
Figure 11:Exam ple Set forStructuring

The resul
t for each structuring setting is shown in Tabl
e 2.
Ex. Result
A
Additionally,the object num ber is added to the

structuring. The sequence is first object num ber,
second cost elem ent.
Table 2:Structuring Exam ples

Another exampl
e shows the possibil
ities of structuring using individualval
ues.
Situation:You are bil l
ing a sales 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 values'and use quite simpl e sets:They must have onl y one node with al l
values,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 materials have an initialactivity type. The sequence sorts the dynamic items first for the
values of the characteristic activity type. As the initialvalue is al
ways before a non-initialval ue,
the materials are displayed first.
Figure 12:Structuring Using Single Values

Figure 13:DIP Profile:Structuring by Characteristics
3.1.3 Source Sel

ection
In the sources view,the source data to be processed is specified. SAP del

ivers nine sources for
the different business processes.
" Actual costs - Line items: This is the most commonl yused source for resource-rel
ated
bil
ling. It offers the most detail
ed data to create the dynamic items.
" Actual costs - Totals records: This source can al so be used for resource-rel
ated billing. It
has the advantage of being faster than the l ine items,but you cannot use al lof the
characteristics offered bythe line item source.
" Statistical indicators - Line items: This is a source for actualstatisticalkey figures. It can
be used to bil l;for exampl e;kilometers.
" Statistical indicators - Totals records: The same as for the actualcosts - faster but with
fewer characteristics.

" Funds - Line items: The funds source can be used for bil
ling 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 lplanned costs.
" Planned Statistical indicators - Totals records: A source pricing or quotation creation
based on planned statisticalkey figures.
" 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 allsources,the system does not read val ues from settlement. 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 sales order,you have to assign the internalorder directly 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.
Technically, this is not done by business transactions. The system checks the cost el ement
category and excl udes allpostings of categories 11 (Revenues) and 12 (Sales deduction).
It is possibl
e to use a source more than once. If you do,you have to enter the selection criteria for
each source sel ection line 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 filled for the indicators,so you shoul d also use the
characteristic statisticalkeyfigure.
Figure 14:DIP Profile:Sources

You can use the Percentage fiel d to define a default for val
ues to be bil
led. If it is set to 75% ,the
col
umn with the val ues to be bill
ed is set to 75% ,the remaining 25% is set to the col umn with the
val
ues to be rej ected. If you perform the pricing or quotation creation process, the defaul t
percentage is used to fil l the "Transfer amount" col umn. These suggested val ues can be
overwritten by the user. The defaul t percentage is not used in resul
ts analysis.
The Apportionment reason can be used to write rej ected costs to a different l
ine ID in resul
ts
analysis. It can be onl
y set in the profile and is transferred directl
y to accrualfor allrej
ected costs
sel
ected by this source sel ection line. It is displ
ayed on the screen,but cannot be changed by the
user during resource-related billing or resul ts anal
ysis.
The l ast three col umns are onl y active for source Actual costs - Totals records. W ith the Costing
sheet and the Overhead key,overhead can be cal cul
ated during resource-rel ated bil
ling. W ith
this option,you can bil lother overheads as you are using internal ly. If the sign Only base is set,
onl y the calcul ated overheads are processed,but not the originalcosts sel ected by this source
line. Therefore,the actualcosts without overhead can be sel ected from the l ine items with one
source sel ection line. W ith another selection l
ine,overheads can be cal culated based on costs
read from total s records.
You can enter sel ection criteria for each source sel ection l ine. In the criteria view,al lrelevant
characteristics (except the obj ect number) are displ ayed. If no criterion is specified for a
characteristic,the system ignores val ues of this characteristic when reading the source data.
Therefore,no entry means al lval ues of this characteristic including the "initialval ue". Sets from
Report W riter and groups from accounting can be used. W ith the green arrow on the right,sets
with the set maintenance toolcan be created,changed,or viewed. The procedure is the same as
that described in chapter 3.1.2.2. If a source is used in more than one l ine,the sel ection criteria
must be set in such a way that sel ection does not overlap. For more detail s,see chapter 3.1.6.
Figure 15:DIP Profile:Sources -Selection Criteria
Some of the criteria can be used directl

y on the database to speed up sel ection and data transfer
amount between the database and the appl ication server. Al
lother criteria are checked on the
appl
ication server. W hich characteristics can be eval uated on the database depends from the

source. An overview can be found in chapter 3.1.6. It is al

so possibl
e to add sel
ection criteria by
means of a customer enhancement described in chapter 4.1.
Rememeber that if you narrow the sel ection of actualcosts in resource rel ated bill
ing,you get
only these costs in resul
ts anal ysis. In consequence,the COS in resul ts analysis can be small
er
than the totalcosts,even if resource rel ated bil
ling tel
ls you that al
lcosts are bil
led.
3.1.4 MaterialDetermination
The finalstep in the profil e definition is to set up of materialdetermination. For alldynamic items,
a materialhas to be found to process them further. The rul es for finding the materials 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
sales document items. Al ldynamic items with the same materialnumber are summarized to one
sales document item,if no other setting in the profile 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.
Figure 16:DIP Profile:MaterialDeterm ination -Indicator‘Use Quantity’
You can enter a number from the materialmaster in the 'Material/service' col umn.. You cannot
use any services from the service master here. It is best to use service materials here,because
the fewest data has to be maintained for them. For more information,l ook in chapter 3.4.
W ith the 'Material direct' indicator set,the characteristic materialof the dynamic items is used
instead of the materialspecified here. Pl ease make sure that the ' Material
'is switched on as a
relevant characteristic. Otherwise,this sign has no effect. If you are sure,that alldynamic items
assigned to such a l ine with this sign set have a materialnumber,you can l eave the material
column bl ank.

The 'Individual' indicator forces the system to create a singl eline for each dynamic item,even if
their materialnumbers are equal . This has no effect on the characteristics transferred to the sal
es
document items.
Figure 17:DIP Profile:MaterialDeterm ination -Criteria
Normal ly, the unit of measure of the dynamic items is used in the sal es document items.
Therefore,a conversion rate must be set in the materialfound here,if the unit of measure differs
from the base unit of the material
. Sometimes,your internalunit of measure is different from the
one you want to use in your bil l
ings;for exampl e,confirmations are done in minutes,but the
invoice shoul d show hours. If you set the 'Conversion quantity' indicator,the system uses the
sales unit from the materialand converts the quantity. If no sal
es unit is specified,the base unit is
used instead.
For allof your materialdetermination l ines,criteria can be set to define the rel ationship between
dynamic item characteristics and the materialof this l ine. In fact,criteria have to be specified,
because the case of onl y one material(where the criteria can be left blank) is rare. The criteria of
the lines shoul d not overl ap. If they do, the system wil lwork, but you get probabl y some
unexpected material s for your dynamic items because the first l ine whose criteria match the
characteristics of the dynamic item is taken.
In the criteria view for the materialdetermination l ine,al lcharacteristics are shown for which the
sign 'Materialdetermination'is set in the characteristics view. Unl ike in the sel ection criteria,a set
or a singl e value can be entered. W e recommend that you use sets,but as there is sometimes
the need to rel ate each single val ue of a characteristic to a material(for exampl e,each activity
type is bill
ed with a different material),you can al so enter single val ues. It is not possibl e to enter
both. The same concerns appl y to the sets as to the selection criteria or the structuring. W ith the
green arrow,you can al so maintain your sets.
Untilrel
ease 4.6C,if the dynamic item has a quantity,it can be transferred to the sal es document
item by setting the sign 'Use quantity'. In fact,the system transfers the quantity that resul
ts of the
summarization of the dynamic items. Therefore this indicator onl y takes effect if ' No
summarization'is set for the ' Unit of measure'in the characteristics view. If ' Use quantity'is
cleared for the particular materialdetermination l ine or '
No summarization'is cl eared for the unit

of measure,the system simul

ates the quantity 1 (if costs are greater than zero) or -1 (if costs are
l
ess than zero).
Since release 4.70 the controloptions for transferring quantity and costs are enhanced. The
originalsign “Use Quantity”was 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 sales and distribution document items.
You have the fol
lowing possibil
ities:
" Space -transfercosts only
The system transfers onl y the costs to be bil
led to the sal
es DMR and sets the quantity to
1 in the DMR item. Resource items are transferred if the costs do not equalto 0. Resource
items with a quantity not equalto 0,but costs that equalto 0 are not transferred. Resource
items with costs to be bil
led that are less than 0 are shown as credit memo items.
" X -transfercosts and quantity

The system transfers the costs and quantities to be bil l
ed. If no quantity exists,or if the
quantity is 0,the system sets the quantity to 1 in the DMR item. Resource items are
transferred if the quantityor the costs are not equalto 0. Resource items with quantities to
be bill
ed that are l ess than 0 are shown as credit memo items even ifthe costs > 0.
" A -forcosts <> 0:transfercosts and quantity

Resource items are transferred if the costs to be bil l
ed are not equalto 0. Resource items
with costs to be bil
led that are l
ess than 0 are shown as credit memo items. The system
transfers the costs and quantities to be bil
led. If a quantity does not exist or if the quantity
is 0,the system sets the quantityto 1 in the sal es and distribution document item.
" B -forquantity <> 0:transfercosts and quantity

The system transfers the costs and quantities to be bil
led if the quantityto be bil
led does
not equal0. Resource items with a quantityto be bil l
ed that is less than 0 are shown as
credit memo items.
" C -transferquantity only

The system transfers onlythe quantityto be bill
ed to the sales and distribution
document. Resource items are transfered if the quantityto be billed 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
led 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
ling request item to be generated. Dynamic items with costs or quantities to be bil
led < 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.

If you want to billbased on quantity,choose the option B or C. Pricing should be set so that net
val ue is determined from the quantity multipl
ied by the price. You can enter prices manual ly or
find them automatical l
y using pricing. You shoul d not use the option X if you bil lbased on
quantity,because the system sets the quantity to 1 for a quantity of 0 to be bil l
ed,in order to
transfer the costs.
If you want to transfer costs to the sal
es and distribution document,you must define additional
lya
cost condition for the type of sal es and distribution document to be created in Customizing
(ODP4).
The above options for the resource items in the resource-rel ated bil
ling document are val id
analogousl y for the pl anning expenditures to be transferred to sal
es pricing for proj
ects and
quotation creation for service orders.
Figure 18:DIP Profile:MaterialDeterm ination – IndicatorTransferQuantities /Costs
3.1.5 Criteria for Source Sel

ection and MaterialDetermination
For both the source sel ection and the materialdetermination,criteria can or must be entered. As
was already said in chapters 3.1.3 and 3.1.4,the criteria shoul d not overl ap if more than one
source selection line or materialdetermination l ine is specified in the profil
e. If onl
ycriteria for one
characteristic are used,this is quite easy. It is best to create a hierarchicalset with a top node
and subsets and use the subsets in the criteria. You can use the check and hel p functions of the
set maintenance toolto checkthat no val ue occurs more than once in the totalset.
If more than one characteristic is used for the criteria,it is important to know that a bl ank field for
a characteristic means ' allval ues incl uding the initialval ue'. Therefore if in one l ine a set is
specified for a characteristic but in another l
ine,the criterion for this characteristic is l
eft blank,an
overlap occurs. General ly, if a set is specified somewhere for a characteristic, in al lsource
selection lines or materialdetermination l ines,a set or val ue must be set for this characteristic.
Sometimes,sets with ' allval ues'and sets with the ' initialval ue'must be used to resol ve the
overlap.
Figure 19 Criteria Exam ple:MaterialDeterm ination
The fol
lowing exampl
e for a set-up of the materialdetermination shoul
d cl
arify this further.

W e want to billworked 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 element. These characteristics are marked as rel evant in the characteristics view of the
profil
e. W e bil
lallworked 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
materials for our bill
ing:LABOR,MATERIALS and OVERHEAD. In the materialdetermination
screen,three l ines with these materials are entered. For LABOR and MATERIALS,we set the
sign 'Use quantity'to transfer the quantity to the invoice. Only for the MATERIALS,we set the
sign 'Materialdirect'
,because we want to show in our invoice the used material s. Normally,the
MATERIALS coul d be cleared but we left it showing us for what this line 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 ly,
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 allof our
costs have a cost element,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
:
" For characteristic activity type (Fiel
d LSTAR of structure AD01ATTR):
$ NO-ACTIVITY-TYPE:Set with initialval
ue
$ ALL-ACTIVITY-TYPES:Set with al
lactivity types
" For characteristic materialnumber (Fiel

d MATNR of structure AD01ATTR):
$ NO-MATERIAL:Set with initialval
ue
$ ALL-MATERIALS:Set with al
lm aterial
s
Do not use the "Insert al
lvalues"'function from the set maintenance tool . The l
ine inserted bythis
function incl
udes the initialvalue. Instead,for exampl e,for the activity type,enter 000000 in
"From val ue"and ZZZZZZ in "To val ue".
The resul
ting materialdetermination criteria for the three l
ines are shown in Tabl
e 3.

Line Material Criteria

1 LABOUR
2 MATERIALS
3 OVERHEAD
Table 3:Criteria Exam ple:MaterialDeterm ination Criteria
The exampl e can be easily enhanced,for exampl

e by spl
itting the LABOR l
ine to different bil
ling
material
s determined by the activity type.
If we want to spl
it the OVERHEAD into "real "overhead and "other"costs,we have to add the cost
el ement characteristic to the materialdetermination. Then we create a materialcal
led OTHER
COSTS and add this as a new l ine to the material
determination view. Next we create a cost el ement
group with the root TOTALCOSTS and two nodes
OHEADCOSTS and OTHERCOSTS. You enter the
overhead cost el ements (for exampl e,from 660000 to
669999) bel ow node OHEADCOSTS and al l other
cost elements bel ow OTHERCOSTS.
Figure 20 Set forSplitting Costs

Line Material Criteria

1 LABOUR
Optional
2 MATERIALS
Optional
3 OVERHEAD
4 OTHER COSTS
Table 4:Criteria Exam ple:Enhanced MaterialDeterm ination Criteria
The sets OHEADCOSTS and OTHERCOSTS are used to separate the overhead,but for al lother
selection criteria, a cost el ement group must al so be specified. Here we enter the set
TOTALCOSTS. The new settings are shown in Tabl e 4. At least, if the criterion of one
characteristic of two lines does not overl ap, the lines do not overl ap. Therefore, the set
TOTALCOSTS in l ines 1 and 2 coul d be removed,because these two l ines do not overlap and
they do not overl ap with the other l
ines. They have either a materialnumber or an activity type
which the dynamic items of l ine 3 and 4 do not have. Nevertheless,it is sometimes better to add
such unnecessary sets to make the criteria clearer.

3.1.6 Characteristics Fil

led byStandard Sources
The characteristics are rel ated in many ways to the sources. First,not al
lsources can provide and
fil
lal
lcharacteristics. For exampl e,it is usel
ess to mark the statisticalkey figure as rel
evant if
none of the statisticalindicator sources is used.
Funds -Totals records
Planned costs -Totals
Technicalfield nam e
Statisticalind. -Line
Actualcosts -Totals
Statist. ind. -Totals
Easy cost planning

Planned Stat ind. -
Actualcosts -Line
Funds -Line item s
Totals records
records
records
records
item s
item s
Accounting indicator AP AP – – – – AP 2 – – BEMOT

Activity num ber* – – – – – – – – AP ASNUM
Activity type AP AP – – – – AP – AP LSTAR
Billing form 1 (AP) (AP) (AP) (AP) (AP) (AP) (AP) (AP) (AP) FAKTF
Business partner**SRM – – – – – – – – – SERV_AGENT_ID
Business process AP AP – – – – – – AP PRZNR
Category ID **SRM – – – – – – – – – CATEGORY_ID
Com m itm ent item – – – – AP AP – – – FIPOS
Cost center AP AP – – – – AP – AP KOSTL
Cost elem ent DB AP – – – – AP – AP KSTAR
Docum ent num ber AP – AP – AP – – – – BELNR
Item num ber**SRM – – – – – – – – – REF_OBJECT_ITEM
Log. system source **SRM – – – – – – – – – AWSYS

Material DB AP – – – – AP – AP MATNR
Object num ber DB DB DB DB DB DB DB DB AP OBJNR
Object type AP AP AP AP AP AP AP AP AP OBART
Period DB A/D DB A/D DB A/D A/D A/D AP 5 POPER
Personnelnum ber AP AP 4 AP – – – AP 4 – – PERNR
Plant DB AP – – – – AP – AP WERKS
Plant ofwork center – – – – – – – – AP AWERK
Posting row AP – AP – AP – – – – BUZEI
Product 3 (AP) (AP) (AP) (AP) (AP) (AP) (AP) (AP) (AP) PRODU
Product nam e **SRM – – – – – – – – – ORDERED_PROD
Service num ber* AP AP – – – – AP – AP ASNUM
Stat. key figure – – DB DB – – – DB – STAGR
Transaction currency DB DB – – DB AP DB – AP TWAER
Transaction num berSRM – – – – – – – – – REG_OBJECT_ID
Unit ofm easure DB 6 AP – AP – – AP AP AP MEINH
Value type DB DB DB DB DB DB DB DB – WRTTP

Version DB DB DB DB DB – DB DB – VERSN
WBS Elem ent ** – – – – – – – – – /CBAD/BILL_WBS
Work center – – – – – – – – AP ARBPL
Table 5:Characteristics
*) In rel
ease 4.6C,5.00,6.00 and 7.00 this characteristic is cal
led “ActivityNumber”. But in
release 4.70 it is cal
led “Service Number”.
**) These characteristics are not avail

abl
e in rel
eased 4.6C and 4.70
SRM
) Specialsource is used for data retrievalform SRM system. Fiel
ds are onl
yfil
led when this source is used.

W hen reading sources,some of the characteristics can be handl ed and eval uated directl
y at the
database l evelbut others cannot. Selection criteria,based on such characteristics are checked in
ABAP on the appl ication server. Source data which does not fit the criteria is removed from the
selection. Obviously,performance is better if the characteristic can be checked on the database.
For exampl e,for source "Actualcosts - Line items"' ,the cost element can be checked at the
database, whil e activity types have to be checked at the appl ication server. General l
y, al l
dependent characteristics are checked at the appl ication server.
Table 5 shows an overview of which source can provide the characteristics and how it handl
es
them.
Legend for Tabl

e 5:Characteristics
– Not provided
" DB Provided and sel ected on database l evel
" AP Provided and sel ected on application server l
evel
" A/DProvided,but onl ythe year is used to select 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
led for the specialdynam ic item of the service product. This specialdynam ic
item is fill
ed with the fol l
owing characteristics:Accounting indicator;Bil ling 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
ly
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 looks 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 light is displ
ayed. For the overlap check,a detail
screen shows which l ines are overlapping.
Since SAP R/3 Enterprise Core 4.70 a new anal ysis program for DIP profile is called 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,enables you to print the
entire profil
e,and simulates 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 able untilrel
ease 4.6C only.

Figure 21:Profile Check (ODP2A)
3.1.8 Does and Don'

ts if Changing the Profil
e
The settings in the DIP profil

e define your dynamic items. For the dynamic items,the document
flow of resource-rel
ated bil
ling is stored and also the pricing is stored with a l
ogicalconnection to
the dynamic item characteristics. Therefore if you change the profil e while having al
ready used it
in any business process,you wil lsee maj or impacts to your old data.
DON'
T...:
" Adding or removing an independent characteristic (marking or unmarking it as
characteristic) defines new dynamic items. As the ol d data is stored for the characteristic
vector before the change some important l ogicalconnections are l ost. In resource-related
bil
ling,the costs al ready bil
led are displayed twice:the totalsource val ue is shown as
unbilled and the bil l
ed values are shown as bil led but without a source val ue;they're open
with the opposite sign. You l oad a pricing for the project but if you press the refresh

button,the ol
d data disappears. You wil
lal
so l
oose al
lmanualprice changes to the
pricing.
" Narrowing the selection criteria of your sources coul

d cause probl ems simil ar to those if
you change the independent characteristics. If there is no source data for bil
led costs,
they are shown as open with negative val ues.
" 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.
" Changing the DIP profile can have the same impact as the l
ast points if the changing of
the profil
e incl
udes a change of rel
evant independent characteristics or source selection.
" If you use a user-defined independent characteristic,take care that the val
ue of it won’
t
change in the future.
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 billing.
" You can widen the selection criteria of a source sel

ection l
ine. This can onl
ycause
additionalunbil
led costs for orders or periods you thought alreadybil l
ed.
" You can split a source sel

ection l
ine into mul tipl
elines without probl
ems if the criteria of
the new l
ines are the same as the criteria of the oldline.
" You can change the materialdetermination in any way. You can al so change the
characteristics to be used for materialdetermination. The material s are newly determined
every time you start resource-related bil l
ing or any other business process. Remember
that a changed materialcan cause changed prices in an existing pricing of a proj ect. Al
so,
if you set the DI w/material sign in the profil
e usage,you coul dlose unbil
led dynamic
items if the materialdetermination fails after this change.
If it is real
ly 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 apply the new profil
e onl yto new orders.
3.2 Apportionm ent Reason (ODP3)
The apportionment reason is a val ue that can be used to write cost of sal es or work in process to
different line ids in resul ts analysis in transaction OKG5. The apportionment reason is entered in
the source sel ection line of the DIP profil e. So you can define different apportionment reasons for
the sel ected costs. It is copied directl y from the DIP profil e to results anal
ysis. Here,you can write
unbil l
ed costs from a source sel ection l ine to a different l
ine ID than your bil
led costs.
3.3 Cost Condition (ODP4)
Bil
ling or pricing can be based on quantities or amounts (costs). Therefore,these values must be
copied to the sal es document and the pricing procedure. W ith the sign ' Use Quantity'of the
materialdetermination l ine,the system knows,that the quantity shoul d be used in the sal es
document and pricing. If a materialprice is found,the price of your bil ling or quotation can be
calculated.

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 ling area,it can be set if allcurrencies or only the control l
ing
area currency is updated. There is stil lthe question which currency is copied to the pricing. If only
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 controlling 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
profile 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 profile. These materials are transferred to the sales document items,
regardless of whether the sal es document is real l
y created or just 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 sales area you are working in your business processes. At l
east,the views
"Basic Data 1"and "Sal es:sales 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

should be used directl y,these views must also be maintained in its materialmaster even if they
are onl
y used for pricing and are never sol
d or bil
led.
The possibil ity of transferring the quantity and its unit of measure from the dynamic items to the
sales 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 sales 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,
especially 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 Custom izing in SD
It is beyond the scope of this document to describe al

lpossibl
e customizing in SD that affects the
business process covered by the DIP. For that reason,this chapter deal s only with the parts
directly infl
uencing the DIP or respectivel
y the sal
es document created by the DIP.
3.5.1 Sal
es Docum ent Types
General ly allsal
es document types can be used in the DIP. There are no speciall imitations. SAP
delivers some sal es document types which can be used for the DIP:L2 and G2 for Resource-
rel
ated Billing;AE for Quotation Creation for Service Orders;AP for Pricing for Projects.
3.5.2 Item Categories
For the item categories,some of the processes need specialsettings.

W hen creating both debit and credit memo request in resource-rel ated bill
ing, you need two
different item categories. For the one to be determined for the credit memo request,the sign
'
Returns'must be set to l et the system know that the sal
es document item is a credit item.
For product processing,two different item categories must be al so defined . One of the item
categories is the statisticalone which is either used for the main item or the sub-items,depending
on the bil
ling form.
3.5.3 Item CategoryUsage and Item CategoryAssignments
For dynamic items there are two item usages defined:

" SEIN— Dynamic item is rel
evant for bil
ling
" SENI— Dynamic item is not rel

evant for bil
ling
One usage is set automaticall

y per item for the sal
es document items created by the dynamic
item processor. The usage SENI is onl
yused in product processing.
W ith the usage the item category assignments must be defined for each sal
es document type
and item category group.
Exampl e:You want to define the item category assignment for the business process Quotation
Creation from Service Order. You have al
ready customized the sal
es document ZQU and the item
categories ZQUN and ZQUS,where ZQUS is a statisticalitem category.

For the non-product processing,the assignment for item category group DIEN has to be:
Sal
es Document Item Category Usage Higher LevelItem Defaul
t Item
Type Group Category Category
ZQU DIEN SEIN ZQUN
For product processing the set-up is more compl ex,especial l

y the customizing is different for the
bil
ling forms. For bil
ling form "Fixed Rate"'the sub-items have to become statisticalitems:
Sal
t Item
ZQU DIEN SEIN ZQUN
ZQU DIEN SENI ZQUN ZQUS
For bil
ling form '
Costs'things l
ook j
ust the opposite because the main item must be the statistical
one:
Sal
t Item
ZQU DIEN SENI ZQUS
ZQU DIEN SEIN ZQUS ZQUN
The lines 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 only 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 sales 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.
3.5.5 Reasons for Rej

ection
The reason for rej ections can be used both in quotations and debit/credit memo requests. In the
last case, the customizing of the reasons can have an effect on the bil l
ing. The reason for
rejection has the sign OLI. This controls whether the bil led costs or resources are open again for
bil
ling when a reason for rejection is set in the debit or credit memo request.
If the sign is cl
eared for the reason,the costs or resources are stilltreated as already bill
ed. If the
sign is set,they are avail able again in the resource-rel
ated bil
ling process for new bil
ling (see al so
note 131288).

3.5.6 Pricing and Pricing Procedure
Pricing is done by simul ating a sales document in background. Therefore,the pricing procedure is
determined the same way l ike creating manuall
y a sales document with the same sal es area and
customer. Al lpricing options can be used in the DIP pricing.
Using the dynamic item characteristics for the pricing sometimes requires a littl
e effort to work.
Characteristics which are also known by SD (such as the pl ant) are transferred automatical l
y to
the sales document item. For other characteristics,customer enhancements have to be used.
Remember that onl y characteristics with the sign '
No summarization'set are transferred to the
sales document item and the user exits there.
It is possibl
e to change the sal es document to be created or used in the simul ation. This can be
done either in the profil
e,but also onl
ine. If this is done,al
lconditions of saved pricings gets l
ost if
the newl y determined pricing procedure does not know these condition types.
3.6 Custom izing in Results Analysis
There is no specialcustomizing necessary if you are using val

uation method 14 or 15.
You can use the apportionment reason and the accounting indicator to determine the l
ine IDs.

4 Custom erEnhancem ents
4.1 Overview
Customer enhancements for the dynamic item processor can be divided between directl y rel
ated
customer enhancements and those original l
y based in other appl ication but which can be call
ed
when the dynamic item processor is running. The enhancements in the second group are l ocated
mainly in SD and are cal
led when you simul ate or create a sal
es document. Such exits are cal l
ed
secondary customer enhancements whil e the direct enhancements are primary customer
enhancements. Very often,these enhancements must be used in combination to impl ement a
business process. An overview of enhancements is shown in Tabl e 6 and Tabl e 7.
4.2 Exits
Allthese exits are call

ed during the different business process at a certain time. Some of them
are onl
y called for specific business processes. An overview with the sequence of the exit-cal
ls is
shown in Figure 22.
Enh. Exit Description
AD010001 Change obj ect list and its hierarchy
EXIT_SAPLAD13_001 Change texts for DI structuring
EXIT_SAPLAD13_002 Typing nodes for singl e val ues
EXIT_SAPLAD15_001 Change obj ect list and hierarchy
AD010002 Delimit selection and/or fil ter determined data
EXIT_SAPLAD15_010 Source filter (not availabl e for allsources)
EXIT_SAPLAD1C_002 Change COSEL - sel ection structure
AD010003 Create user-defined DI characteristics
EXIT_SAPLAD12_003 Fil
luser-defined independent characteristics
EXIT_SAPLAD12_004 Fil
luser-defined dependent characteristics
CI_ATTRI2 Structure of user-defined independent charact.
CI_ATTRD Structure of user-defined dependent charact.
AD010005 EXIT_SAPLAD15_005 Read user-defined sources
AD010006 Menu exit:Change DI val ue
EXIT_SAPLAD14_006 Exit:DP processor menu (screen 100) *)
EXIT_SAPLAD14_008 Change text for menu exit *)
AD010007 EXIT_SAPLAD15_015 Change DI processing Information
V46H0001 SD customer functions for resource-rel ated bil
ling
EXIT_SAPLV46H_001 Customer function when creating item
EXIT_SAPLV46H_002 Customer function for partner changes
KKAG0004 Resul ts anal ysis with dynamic items
EXIT_SAPLADK0_001 Postprocessing:CO subkey dynamic items RA
EXIT_SAPLADK0_002 Postprocessing of Resul ts Anal ysis with Dis
CI_ADK0_RA2 Additionalfiel ds of CO subkey to be fil l
ed
ICSV0005 EXIT_SAPLISDI_001 Determining reason for rej ection - RRB
Table 6:Prim ary Custom erEnhancem ents
*) only avail
abl
e until rel
ease 4.6C, repl
aced by BAdI “SMOD_AD010006”, methods
“EXIT_SAPLAD14_006”and “EXIT_SAPLAD14_006”.

Enh. Exit Description

MV45AFZZ User exits for modifications in
(Incl
ude) sal es document processing
USEREXIT_PRICING_PREPARE_TKOMK Include or assign a val ue to
an additionalheader fiel d in
the communication structure
KOMK taken as a basis for
pricing
USEREXIT_PRICING_PREPARE_TKOMP Include or assign a val ue to
an additionalitem fiel d in the
communication structure
KOMP taken as a basis for
pricing
KOMKAZ Structure with user defined
fields for pricing
communication header
KOMPAZ Structure with user defined
fields for pricing
communication item
USEREXIT_SAVE_DOCUMENT Update additionaltables
when saving a sal es
document
USEREXIT_READ_DOCUMENT Read additionaltables when
reading a sal es document
USEREXIT_DELETE_DOCUMENT Del ete additionaltabl es when
del eting a sal es document
VBAPKOZ Structure with user defined
fields for sales document
item
KKAG0005 EXIT_SAPLKKAG_007 Determination of time frame
and results anal ysis key
Table 7:Secondary Custom erEnhancem ents (Selection)

Onl
y resul
ts anal
ysis
Start resul
ts anal
ysis EXIT_SAPLKKAG_007
Onl
y bil
ling
Not for saved data

Check input obj
ect EXIT_SAPLISDI_001 (service orders onl
y)
Onl
y dial
ogue
Only when saving Determine obj

ects EXIT_SAPLAD15_001
sal
es docum ent
Al
ways Process standrad
sources Read standard source EXIT_SAPLAD1C_002
Fil
ter standard source
Create Pricing /Do not use saved data

EXIT_SAPLAD15_010
Load Pricing /Use saved data
EXIT_SAPLAD12_003
Derive dynamic items EXIT_SAPLAD12_004
Process customer sources EXIT_SAPLAD15_005
Onl
yfor new interface EXIT_SAPLAD12_004
Read bil
ling fl
ow
Materialdetermination EXIT_SAPLAD15_015
Structure dynamic items EXIT_SAPLAD13_001
Summarize to sal
es doc. items
Create header
es
SD exits for creating header

ate sal
document
EXIT_SAPLV46H_001
OtherSD exits for creating items
Simul
Create item s USEREXIT_PRICING_PREPARE_TKOM K

USEREXIT_PRICING_PREPARE_TKOM P
EXIT_SAPLV46H_002
EXIT_SAPLAD14_008
User dial
ogue EXIT_SAPLAD14_006
EXIT_SAPLADK0_001
Allexits l
ike simul
ation Save resul
ts anal
ysis EXIT_SAPLADK0_002
Create sal
es document USEREXIT_SAVE_DOCUMENT
USEREXIT_READ_DOCUM ENT
Change sal
es document Other SD exits for changing doc.
USEREXIT_SAVE_DOCUMENT
Figure 22:Calling Sequence ofCustom erEnhancem ents

4.3 BAdIs
As of SAP R/3 Enterprise Core 4.7 new Business Add-Ins (BAdIs) are avail
abl
e. These BAdIs are
developed for allcustomer 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 able onl
y as a BAdI. The BAdI methods are cal led at the same
pl
ace as the exits.
In addition to the BAdIs with functions from customer enhancements,new Business Add-Ins are
also delivered.
4.3.1 BAdIs within the Dynamic Item Processor (DI Processor):
" 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
lowing 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 values and change
characteristic val
ue texts. The enhancement contains the following 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)
" DIP_AD010002_SEL
This enhancement is used to restrict sel
ection. The enhancement contains
the fol
lowing method:
$ EXIT_SAPLAD1C_002:Change sel ection criteria
" DIP_AD010003_DC
This enhancement is used to create user-defined dependent characteristics for
determining dynamic items. The enhancement contains
the fol
lowing method:
$ EXIT_SAPLAD12_004:Fil luser-defined dependent characteristics

" DIP_AD010003_IC
This enhancement is used to create user-defined independent characteristics for
determining dynamic items. The enhancement contains the following method:
$ EXIT_SAPLAD12_003:Fil luser-defined independent characteristics
" DIP_AD010005
This enhancement is used to create user-defined sources for determining dynamic items.
The enhancement contains the following method:
$ EXIT_SAPLAD15_005:Read user-defined sources
" SMOD_AD010006
This enhancement is used to change the val ues in the dynamic items (amounts and
quantities). It contains the fol
lowing 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
lowing method:
$ EXIT_SAPLAD15_015:Change Dynam ic Item Processing Inform ation
" DIP_CHECK_INPUT_OBJ
This enhancement is used to checkthe access obj
ect in the DI processor. The
enhancement contains the following 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 selection data to other programs,which cal
led
resource-rel
ated bil
ling,for example. 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 ‘
01’for RRB
‘
11’for Sal
es Pricing
FROM_SELECTION_SCREE In sel ection screen entered
N sales order,service order,W BS
element,sal es order item.

" AD01_RRB_COLLECTIVE1
This enhancement is used to modify the output l
ist for col
lective processing for resource-
rel
ated bil
ling (DP95,DP96 and DP97). The enhancement contains the fol lowing 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
low-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
The BAdI “AD01_RRB_COLLECTIVE1”is cal
led in the fol
lowing transactions:DP95,
DP96 and DP97.
4.3.2 BAdIs for Restricting the Change Options for Users
" 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 lowing 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”)
4.3.3 BAdI for Docum ent Fl

ow Reporting
" AD01_RRB_REPORTING_1
This enhancement is used to fil
lother fiel
ds in document fl
ow reporting (DP98) for bil
ling
requests. The enhancement contains the fol lowing 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
low-up action when sel
ecting a fiel
d per doubl
e-cl
ick/hotspot
4.3.4 BAdIs with Infl

uence on Further Processing in SD:
" 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
lowing
enhancement components:
$ EXIT_SAPLV46H_001:Change the item fiel
ds
$ EXIT_SAPLV46H_002:Change partner

$ EXIT_SAPLV46H_003:Change header fiel

ds
" DIP_CREATE_FOLLOW_UP
This enhancement is used to determine whether a bil l
ing request is created in resource-
rel
ated bill
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
lowing enhancement components:
$ CREATE_FOLLOW _UP_SALES_DOC:Create fol
low-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 following enhancement components:
$ SET_SD_DIALOG_POPUPS:Activate dial
og boxes in SD sal
es docum ent
The foll
owing tabl
e contains the ol
d enhancements and the Business Add- Ins that repl
ace them.
The old enhancements are,however,stillavail
abl
e.
Previous Enhancem ent Business Add-In
AD010001 DIP_AD010001
AD010002 DIP_AD010002
DIP_AD010002_SEL
AD010003 DIP_AD010003_DC
DIP_AD010003_IC
AD010005 DIP_AD010005
AD010006 SMOD_AD010006
AD010007 DIP_AD010007
V46H0001 BADI_SD_V46H0001

4.4 Changing Selection Criteria orSelected Data
4.4.1 Change obj

ect l
ist and hierarchy(EXIT_SAPLAD15_001)
The exit has two parameter tabl es which can be changed. Tabl e ET_OBJECTS contains the
object list being processed, tabl e ET_RSTHIE the obj ect hierarchy. The obj ect l
ist can be
modified either by adding new obj ects or by removing obj ects from the l ist. In both cases the
object hierarchy must be adj usted,especial ly if you delete obj ects which are not l eaves in the
hierarchy. The l ogicalconnection between these two tabl es is done with fiel
ds OBJNR (CO obj ect
number) in ET_OBJECTS and NAME in ET_RSTHIE. If you are inserting or del eting objects in the
middle of the hierarchy,the fiel ds TLEVEL (hierarchy l evelof obj ect) and PARENT (reference to
parent obj ect ID) must be set correctl
yin table ET_HIERARCHY.
The exit is cal
led with the object l
ist for each input obj
ect. For example,if a sal
es document with
three items is processed,the exit is cal l
ed three times. Therefore,the exit has also the input
objects as import parameters.
Exampl
es:
1. PROBLEM:You are bil l

ing a service order network. Some of the orders should not be bill
ed.
This depends on the service order type.
SOLUTION:Read the master data for each order in the obj ect l
ist and checkthe service order
type. Remove from ET_OBJECTS and ET_RSTHIE al lorders,which are not to be bil
led.
2. PROBLEM: You want to perform an authorization check on the processed obj ects.
SOLUTION:Use either the input obj ect for your own authority checks or remove obj
ects from
the obj
ect l
ist if the user is not al
lowed to process them.
3. PROBLEM:You want to price your proj ect,but the structure for pricing differs from the l
ogistic
structure of the proj
ect.
SOLUTION:Change the hierarchy in ET_RSTHIE by adj usting fields ID,TLEVEL and
PARENT. Remember that such a hierarchy change is permanent for the transaction. If you
want to switch between the l ogisticalstructure of the project and your al ternative structure for
pricing,consider using additionalcharacteristics.
4.4.2 Change Sel

ection Criteria (EXIT_SAPLAD1C_002)
This exit is call

ed for each source sel ection line of the DIP profil
e except for those selection l ines
with user-defined sources. The sel ection criteria are stored in parameter tabl e ET_COSEL. The
COSEL structure of the parameter consists of a fiel d name (FIELD),a sign (SIGN),an option
(OPTION) and l ow and high val ue of the sel ection (LOW ,HIGH). The sign can be either ' I'for
include or ' E'for exclude. The option can be one of ABAP' s compare operands (EQ (equal ),BT
(between),CP (contains pattern,l ike),...). The low and high val ues must be fil l
ed for the option;
for exampl e,BT requires low and high val ues whil e EQ requires onl
ya low val ue. The fiel
d name
is the technicalfield name of a table fiel
d.
The ET_COSEL structure is al ready fil
led with al
lselection criteria of the sel
ection l
ine plus some
additionalcriteria dependent on the source. For exampl e,the source "' Actualcosts - Line items"
has a selection criteria for the val
ue type to select onl
y actualval ues from table COVP.

Although al lcriteria from the source sel ection line are fill
ed in ET_COSEL,your changes have
onl y an effect on sel ection if they are related to a fiel
d which is directly handled 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 evaluated l ater with other
criteria even if the activity type is a rel
evant characteristic.
For which fiel
ds the selection 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 Table Fields

Actualcost - COVP LEDNR,OBJNR,GJAHR,PERIO,W RTTP,VERSN,
Line items KSTAR,HRKFT,VRGNG,VBUND,PARGB,BEKNZ,
TW AER,MEINH,MEINB,W ERKS,MATNR
'
Actualcosts - COSSA LEDNR,OBJNR,GJAHR,W RTTP,VERSN,KSTAR,
Total
s records HRKFT,VRGNG,PAROB,USPOB,BEKNZ,TW AER
COSPA LEDNR,OBJNR,GJAHR,W RTTP,VERSN,KSTAR,
HRKFT,VRGNG,VBUND,PARGB,BEKNZ,TW AER
Stat. key fig. - COVPR LEDNR,OBJNR,GJAHR,PERIO,W RTTP,VERSN,
Line items STAGR,VRGNG,MEINH
Stat. key fig. - COSRA LEDNR,OBJNR,GJAHR,W RTTP,VERSN,STAGR,
Total s records VRGNG
Funds - Line V_COFP OBJNR,GJAHR,PERIO,W RTTP,VERSN,VRGNG,
items TW AER
Funds - Total s FMSUA LEDNR,OBJNR,GJAHR,W RTTP,GEBER,POSIT,
records VORGA,TW AER,BUKRS,GSBER
Pl anned costs - COSSA Equalto '
Actualcosts - Totals records'
Total s records COSPA
Pl anned stat. COSRA Equalto '
Stat. key fig. - Total
s records
key fig. - Total s
records
Easy Cost CKF_DIP_C None
Pl anning USTOMER_
EXIT
Table 8:Available Selection Fields forEXIT_SAPLAD1C_002

Exampl
es:
1. PROBLEM:You want to excl ude allmaterials from the sel

ection of source ' Actualcosts - Line
items'but you do not want to add the materialas a relevant characteristic.
SOLUTION:Add a l ine to ET_COSEL excl uding table records with a materialnumber:
DATA Z_COSEL LIKE LINE OF ET_COSEL.

IF I_DLISRC = '0001'
Z_COSEL-FIELD = 'MATNR'.
Z_COSEL-SIGN = 'E'.
Z_COSEL-OPTION = 'BT'.
Z_COSEL-LOW = '000000000000000000'.
Z_COSEL-HIGH = 'ZZZZZZZZZZZZZZZZZZ'.
APPEND Z_COSEL TO ET_COSEL.
ENDIF.
2. PROBLEM:You al so want to sel

ect settl
ed costs for bill
ing.
SOLUTION:Settl ed costs are excluded in the standard. Therefore the system al ways adds
l
ines which exclude them from the sel ection. The excl usion is done by fiel
ds BEKNZ and
VRGNG. Therefore,you have to remove al lentries in ET_COSEL referring to the exclusion of
settl
ed costs. This can be done with the fol
lowing code:
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)
Table 8 also shows a l ist of the tables 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 selection line,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 fields which you cannot access in EXIT_SAPLAD1C_002 or you can even
modify the values of the sel ected data.
Exampl
es:
1. PROBLEM:You want to excl ude allpostings with company code ' ABCD'in source '
Actual
costs - Line items'
SOLUTION: Just add the fol
lowing lines 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.

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 always minutes in the dynamic items.
SOLUTION: Check the sel ected data for postings with hours. For these lines,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.
4.5 Defining and Populating Characteristics
4.5.1 Overview
W ith the definition of own characteristics,you have a powerfultoolto enhance the structuring of
dynamic items,the creation of sal es document items and the pricing. User-defined characteristics
can be used with both standard sources and user-defined sources. This chapter describes how
they can be used to enhance functions using standard sources.
The most important thing when creating characteristics is that you know if the characteristics are
independent or dependent. The exact definition can be found in chapter 3.1.2. Independent
characteristics are fil
led from the source data. Their val
ue shoul
d not change when the same data
is read again. This is not so much a probl em with standard sources but this must be clear if you
create your own sources.
Dependent characteristics shoul d be real ly dependent on one or more independent
characteristics. Two dynamic items with equalval ues for certain characteristics A and B must
have also the same val ues in those characteristics C and D depending on A and B. The val ue of
dependent characteristics shoul d not be changed in the future!
Unlike dependent characteristics,independent characteristics are stored on the database in table
AD01DLI,which hol ds the dynamic items characteristics vector. W ith this vector,the document
fl
ow for resource-related bil
ling is stored. Therefore,it is cl
ear,that independent characteristics
should not change suddenl y for the same source data. A consequence of this woul d be that the
bil
led fl
ow can no longer be related to the originalsource data.
4.5.2 Independent Characteristics (CI_ATTRI2,EXIT_SAPLAD12_003)
To add an independent characteristic,create structure CI_ATTRI2 with fiel dname and type. W hen
activating the structure,the system starts changing the database tabl e AD01DLI which incl udes
this structure. After this has happened, you can access the characteristic in the DIP profil e
although it is not fil
led yet. For each selected data record and each user defined characteristic,
EXIT_SAPLAD12_003 is cal led. Here you can use the current processed source data record to fil
l
the characteristic.
Exampl
e:

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 willbe changed on the database.
$ Add the fol
lowing code to exit EXIT_SAPLAD12_003,fil
ling the characteristic ZZBUKRS:
FIELD-SYMBOLS <ZCOVP> LIKE COVP.

CASE I_TABNAME.
WHEN 'COVP'.
ASSIGN I_COST_VALUE TO <ZCOVP>.
CASE I_FIELDNAME.
WHEN 'ZZBUKRS'.
E_ATTRI_VALUE = <ZCOVP>-BUKRS.
ENDCASE.
ENDCASE.
4.5.3 Dependent Characteristics (CI_ATTRD,EXIT_SAPLAD12_004)
Creating dependent characteristics is quite simil

ar to independent ones,except that a different
exit must be used. To add a dependent characteristic,create structure CI_ATTRD with fiel dname
and type of your characteristic. This causes no changes on database tabl es. For fil
ling the
characteristic,EXIT_SAPLAD12_004 must be coded. For each source data record,the exit is
called once to fil
lalluser-defined dependent characteristics. The exit has as parameters a tabl e
with allavailabl
e fiel
ds (IT_FIELDS),a structure with the val
ues of the independent characteristics
(I_AD01ATTRI) and an export structure with the dependent characteristics (C_AD01ATTRD).
Exampl
e:
PROBLEM:You are bil l

ing service orders containing suborders of different order types. You do
not want to see a structuring after order number but a structuring after order type. Therefore you
need the order type as a dynamic item characteristic.
SOLUTION:
$ Create structure CI_ATTRD and add the fiel
d ZZAUFART with type AUFART to the structure.
Save and activate the structure.
$ Add the fol
lowing code to exit EXIT_SAPLAD12_004,which is fil
ling the characteristic
ZZAUART:

DATA: BEGIN OF ZT_AUFK OCCURS 0,

AUFNR LIKE AUFK-AUFNR,
AUART LIKE AUFK-AUART,
OBJNR LIKE AUFK-OBJNR,
END OF ZT_AUFK.
DATA Z_AUFK LIKE LINE OF ZT_AUFK.
DATA Z_AUFNR LIKE AUFK-AUFNR.
FIELD-SYMBOLS <ZFIELD> LIKE LINE OF IT_FIELDS.
LOOP AT IT_FIELDS ASSIGNING <ZFIELD>
WHERE NOT DER_FIELD IS INITIAL AND" Dependent char.
NOT SEL_ATTR IS INITIAL. " Char. is relevant
CASE <ZFIELD>-FIELDNAME.
WHEN 'ZZAUFART'.
READ TABLE ZT_AUFK
INTO Z_AUFK
WITH KEY OBJNR = I_AD01ATTRI-OBJNR.
IF SY-SUBRC <> 0.
Z_AUFNR = I_AD01ATTRI-OBJNR+2.
CLEAR Z_AUFK.
Z_AUFK-OBJNR = I_AD01ATTRI-OBJNR.
SELECT SINGLE AUFNR AUART OBJNR
FROM AUFK
INTO CORRESPONDING FIELDS OF Z_AUFK
WHERE AUFNR = Z_AUFNR.
APPEND Z_AUFK TO ZT_AUFK.
ENDIF.
C_AD01ATTRD-ZZAUFART = Z_AUFK-AUART.
ENDCASE.
ENDLOOP.
W hen sel ecting master data in such an exit,you MUST buffer the data as shown in this exampl e.
Imagine thousands of dynamic items going through this exit. If the master data for every item is
selected from the database,you get maj or performance probl
ems.

4.6 Create User-Defined Sources (EXIT_SAPLAD15_005)
4.6.1 Overview
Designing and coding user-defined sources is the best way to adapt the DIP to a specific
business process,al
though such solution invol
ves the most effort and manpower.
To impl
ement a user-defined source,perform the fol
lowing steps:
1. Create an entry for your source in tabl e AD01SRC. Use transaction SE16 (Data Browser),
enter AD01SRC as the tabl e name and choose Table -> Create entries. Your source'
s name
should start with one of the characters X,Y, Z, or 9. The text wil lappear in the source
selection screen of the DIP profil
e maintenance.
2. Create entries for your source in tabl e AD01SRCTAB. In this tabl e,you can specify the tabl es
to be read by the sources. It is al so possibl e to enter views or DDIC structures as tabl e
names. The tabl e is for documentation purposes onl y. The idea is that,in fact,a source
consists of different sub-sources. A sub-source can be used in more than one main source
with different sel ection criteria. Examples in standard are sources 0002 and 0021. Both have
the structures COSPA and COSSA as sub-sources. Internal l
y the program sets sel ection
criteria for the value type depending on the source. If source 0002 is used,val ue type ' 04'is
sel ected. If source 0021 is used,val ue type '01'is selected. W ith this technique,it is possible
to create a new source based on ol d sources j ust by combining the sub-sources. The tabl e
entries of AD01SRCTAB are al so a help for other exits like EXIT_SAPLAD12_003 because
here you can see which DDIC structure is behind the parameter I_COST_VALUE.
3. The third step is the coding of EXIT_SAPLAD15_005. The exit has various import and export
parameters. The originalinterface,introduced in Rel ease 4.5A,is quite compl exto implement.
Therefore,a new interface was devel oped and publ ished in note 216172 (since rel ease 4.70,
available in standard). The ol d interface is stil
lsupported and can be used as before. The new
interface offers a very simpl e interface,reducing your impl ementation effort and speeding up
the setup of your business process. The description of the ol d interface is no l
onger delivered
with this documentation. If you need a description of the ol d interface,go on the hunt for an
older version of this paper. It’ s recommend to use the new interface. It is less effort to
implement for you and it is less maintenance for me. Neverthel ess,be sure to fillonl y one
interface. The old interface requires the export tabl es ET_DLIV1 and ET_DLIA to be fil led. For
the new interface,you have to fil lonly export table ET_DATA. If you provide val ues for both,
the system wil ldump.
4.6.2 Impl
ementation of EXIT_SAPLAD15_005
In the exit,you have to select the source,move the val ues and allavail
abl
e characteristics l
ine by
line 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 profile (I_PROFNR),the usage of the
profil
e (I_USAGE),the currentl y processed source (I_DLISRC),the control ling area (I_KOKRS)
and the currency of the control ling 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 led for user-defined sources. The sel ection criteria can be
evaluated in the exit to speed up database accesses. If your source can eval uate al lor part of the

selection criteria,you should del ete them from CT_COSEL. Al lremaining selection criteria are
evaluated after the exit. The objects for which the source data has to be read are in parameter
table IT_OBJECTS. In this tabl e you can find the CO object number and the object currency.
Your output must go to tabl e ET_DATA. The structure of this tabl e is a combination of al l
availabl
e independent characteristics and the val ue fields. Move your source data to this table
and the rest is done by the dynamic item processor. You do not have to know which
characteristics are relevant in the current profil
e,j ust fil
lthe tabl
e with allcharacteristics,your
source can provide. The DIP wil lcl
ear allcharacteristics which are not rel
evant and summarize
the data accordingl y to the remaining characteristics. The dependent characteristics are defined
afterwards. In the value 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 led 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 ling area currency has to be moved to field W KGBTR.
Be aware that,if you use the new interface,the system determines the dependent characteristics.
Therefore exit EXIT_SAPLAD12_004 is cal led 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
ling 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 table AD01SRC with source keyZCOM and source text "Components of W BS". In
table AD01SRCTAB we add one record for source ZCOM with tabl e name ' RESB' . Next,the
foll
owing code has to be impl
emented in the exit module:
* 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.

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

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 line in your profil
e for
this source,the exit is cal l
ed more than once for the same obj ects. As there is also no evaluation
of selection 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
selection of RESB without the primary key or an index. To improve the performance,an index on
table 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.
4.7 Change Processing inform ation (EXIT_SAPLAD15_015)
Each dynamic item has its characteristic vector and val ues,cal l
ed the processing information.
The processing information hol ds data l ike the input object, the material from material
determination or the defaul t percentage from the source sel
ection line. Parts of the processing
information can be changed in EXIT_SAPLAD15_015. For exampl e,it is possibl
e to do your own
material determination l ogic in the exit. An overview of the changeabl e and unchangeabl e
characteristics is shown in Table 9.

Param eter Meaning

Changeabl e DEFPERCENT Defaul t percentage
processing AUMOT Apportionment reason
information INV_MAT Materialfrom materialdetermination
INV_SINGLE Sign:Create sal es document item for each dyn. Item
INV_QUANT Sign:Use quantity of dyn. Item in sales document item
FLMEH Sign:Convert to sal es unit
Unchangeabl e DLINR Dynamic item key
processing DLISRC Source of dynamic item
information VBELN Input obj ect:Sales document
VBPOS Input obj ect:Sales document item
AUFNR Input obj ect:Service order
PSPNR Input obj ect:W BS el ement
PRONR Input obj ect:Project definition
PROFNR Dynamic item processor profil e
FAKTF Bill
ing form
OBJNR Input obj ect:CO obj ect number
OBJNR_PD Input obj ect:CO obj ect number of proj
ect definition
TIMESTMP Timestamp of dynamic item
Table 9:Processing Inform ation ofDynam ic Item s forEXIT_SAPLAD15_015
The processing information is in parameter C_DLIM. Some additionalinformation is also provided

by the exit to be used as a basis to change the processing information. Parameter I_USAGE
gives the current usage of the DIP. I_DLIA contains the characteristics of the dynamic item. In
parameter I_DLIV1,the source val ues are stored. In parameter I_DLIV2,the totalflow of bill
ed
and rej ected val
ues can be found. The bill
ed val ues are in fiel
ds IN_XXXBTR,the rejected values
are in fiel
ds NO_XXXBTR. The other fiel ds of this structure are not used.
Exampl
e:
PROBLEM: General l
y, you want to summarize al ldynamic items of smal lparts in one debit
memo request item with materialSMALL-PARTS and without any quantity. Therefore you set-up
the materialdetermination so that for al
lcosts of smal lparts this materialis found and the sign to
use the quantity is switched off. But if the open costs exceed 10 euros in control l
ing area
currency,you want to show a separate l ine in your debit memo request with the quantity and the
originalmaterialnumber.
SOLUTION: First you have to make sure that the materialis a rel evant characteristic of your
dynamic items,because you want to use the originalmaterial . Next the exit has to check if the
open val ues exceeds the l
imit and sets the processing information accordingl y. The code looks
l
ike this:

DATA Z_OPEN LIKE I_DLIV1-WKGBTR.

IF C_DLIM-INV_MAT = 'SMALL-PARTS'.
Z_OPEN = I_DLIV1-WKGBTR " TOTAL COSTS
- I_DLIV2-IN_WKGBTR " SUBTRACT BILLED COSTS
- I_DLIV2-NO_WKGBTR. " SUBTRACT REJECTED COSTS
Z_OPEN = ABS( Z_OPEN ).
IF Z_OPEN > 10.
C_DLIM-INV_MAT = I_DLIA-MATNR.
C_DLIM-INV_SINGLE = 'X'.
C_DLIM-INV_QUANT = 'X'.
ENDIF.
ENDIF.
Note that a singl

e sal
es document item is now created for allchanged dynamic items ,even if
they have now equalvalues in C_DLIM-INV_MAT. If you al so want to summarize using this new
materialnumber,you should not set C_DLIM-INV_SINGLE.
4.8 Change Texts ofDynam ic Item Structuring (EXIT_SAPLAD13_001)
The texts displayed in the dynamic item overview screen are taken from different master data.
Text of the structure nodes are taken from either sets or singl
e val
ues master data if known by
the DIP. Texts of dynamic items are taken from the materialwhich was determined for the
dynamic item.
Especially when adding user-defined characteristics and using structuring after single val ues,the
system does not know where to get the text for the single val ues. Therefore,the system pl aces
the value itsel
f as text. EXIT_SAPLAD13_001 l ets you change texts both of nodes and dynamic
items. Changing the text of a dynamic item al so causes the texts in the sal es price view to
change. W hen creating the structure for the sales price view,the system takes the text of the
dynamic item,the sal es document item is based on. In fact it takes the text of the first dynamic
item belonging to the sales document item.
The fol
lowing rul
es shoul
d be fol
lowed:
" W hen the texts of dynamic items are being changed,alldynamic items which are l ater
summarized to the same sal es document item should get the same new text. The
summarization is mainl y based on the determined materialand the characteristics with
sign '
No summarization' .
" Texts of objects 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.
" The texts changed here are not copied to the l

ater created sal
es document items. The
texts are onl
yused in overview screen.
In the exit,parameter C_RSTTXT can be changed to your texts. Onl y the fiel
ds TEXT20 and
TEXT40 are displ ayed on screen and can be changed. Fiel d SPRAS contains the l anguage key.
The ID and TEXT10 fiel ds are only used internal ly. Parameter I_RSTHIE contains the node
information. Here the TYPE fiel d is important. It contains the type of the hierarchy node. A
dynamic item has type ' DLI',a set has type '
SET'and singl e val
ue nodes have different number
depending on the fiel d. Single val
ue nodes of user defined fields have '0000'as type. A compl ete
list of the node types can be found in Table 10. Node types for obj ects are not displayed as their
names shoul d not be changed. For alldynamic items,the exit provides the additionalparameters

I_DLIA with the dynamic item characteristics and I_DLIM with the dynamic item processing
information.
Exampl
e:
PROBLEM: You are bil ling 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 employee. In the sales 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
lows:
DATA L_NAME LIKE BAS_CHECK_PERNR-NAME.

IF I_RSTHIE-TYPE = 'DLI'.
IF NOT I_DLIA-PERNR IS INITIAL.
WRITE I_DLIA-PERNR TO C_RSTTXT-TEXT20.
CALL FUNCTION 'RP_CHECK_PERNR'
EXPORTING
BEG = SY-DATLO
PNR = I_DLIA-PERNR
IMPORTING
NAME = L_NAME
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC <> 0.
C_RSTTXT-TEXT40 = C_RSTTXT-TEXT20.
ELSE.
C_RSTTXT-TEXT40 = L_NAME.
ENDIF.
ENDIF.
ENDIF.


!"!#
$ %& ! '
!(!"
) %*& + ,
,
+ ' -!.
/ ,
01#!
2 %& % ,
3 ,
.4.5!
6 7&89& :1 ,
"! 5#!
; 7<&9& 7!#"+ '="1(>!#
?< @
9A B" ,
/ (!+1#!
$ C%<& #+"+ ,
" 1##!".
D ?%9& ?+!# ,
+ '="1(>!#
) E @
7 (( ,
(!"F,
!(
2 C&7 G+ '
1! .5!
H C<& 7 '
+"
6 :<? %1" ,
"0F,
"I ,
+#
J %&:7 C#- !"!#
; %C<& 7 '
+" /LK #- !"!#
$ %9B? % ,
3 ,
.4"1(>!#
$ :%& >
M ! .5!
$$ G<&9 3!# ,
"
D 77<& 7 ,
"0 5!# ,
I
N O P ."+( ,
F,
!(
QR !
Table 10:Node Types ofStructuring
4.9 Change Data in Sales Docum ent Item s
It is often necessary to change sales document item data before the item is created or to move
additionaldata from dynamic items to sal es document items - for exampl e,if you want to move
the personnel number to a partner rol e of the sal es document item. Remember that
characteristics are onl y copied to the sales document item where the "No summarization"
indicator is set.
4.9.1 Change Item Data
W ith the first exit you can modify the sal es document item data before the item is created.
EXIT_SAPLV46H_001 offers two import parameters and 1 changing parameter. In I_VBAKKOM
you can find the sal es document header information. In parameter I_SDSM_DLI the information
of the dynamic item is stored. This is not the information from the dynamic item, but the
condensed information of al ldynamic items summarized to this sal es document item. Here you
can al so find the val ue of the dynamic item characteristics if they coul d be copied to the sal es
document item. Final ly,in parameter C_VBAPKOM the communication data for the creation of
sales document items is stored. Al l possibl e data from I_SDSM_DLI is al ready moved to
C_VBAPKOM if the fiel dnames are equal . If you want to modify existing fiel
ds or move additional
fiel
ds (such as user-defined characteristics) to C_VBAPKOM,you can do it here.
Exampl
e:
1. PROBLEM: You want to have use your own characteristic ZZAUFART in structure
C_VBAPKOM.

SOLUTION:Add the field ZZAUFART to structure VBAPKOZ. Additional

ly add the fol
lowing
coding in EXIT_SAPLV46H_001:
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 allitems in debit memo requests created by resource rel ated
bill
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
solve 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:
CONSTANTS LC_KSCHL LIKE KONV-KSCHL

VALUE 'ZDIS'.
STATICS L_VBAK LIKE VBAK.
STATICS L_KONV LIKE KONV.
IF L_VBAK-VBELN <> C_VBAPKOM-VGBEL.
CLEAR L_VBAK.
* Read the predecessor header
SELECT SINGLE VBELN KNUMV
FROM VBAK
INTO CORRESPONDING FIELDS OF L_VBAK
WHERE VBELN = C_VBAPKOM-VGBEL.
ENDIF.
IF L_KONV-KNUMV <> L_VBAK-KNUMV
OR L_KONV-KPOSN <> C_VBAPKOM-VGPOS.
CLEAR L_KONV.
* Read condition LC_KSCHL from predecessor
SELECT SINGLE KNUMV KPOSN KSCHL KBETR KWAER KPEIN KMEIN
FROM KONV
INTO CORRESPONDING FIELDS OF L_KONV
WHERE KNUMV = L_VBAK-KNUMV
AND KSCHL = LC_KSCHL
AND KPOSN = C_VBAPKOM-VGPOS.
ENDIF.
IF NOT L_KONV-KSCHL IS INITIAL.
* Fill condition
C_VBAPKOM-KSCHL4 = L_KONV-KSCHL.
C_VBAPKOM-KBETR4 = L_KONV-KBETR.
C_VBAPKOM-KWAER4 = L_KONV-WAERS.
ENDIF.
This sol
ution has some limitations. First of al
l,you can copy onl
y up to three conditions from the
predecessor. C_VBAPKOM-KSCHL1 is reserved for the cost condition. In Rel ease 4.5,the other
three conditions are used by the manualconditions of the DIP. So if you have defined three
manualconditions and the cost condition,you have nothing l eft to add the conditions of the
predecessor.

The above sol ution is working fine for percentage discounts or surcharges. It's not so easy to use
it for other conditions because RRB creates new items with probabl y different unit of measures
coming from the dynamic item sources. So you need to think more deepl y about the sol ution.
4.9.2 Add Partners
For a modification of the partner rol es of a sal es document item, you can use
EXIT_SAPLV46H_002. Here you can add,del ete,or change the partners. Here,you have once
again the parameters I_VBAKKOM and I_SDSM_DLI with the same meaning as in
EXIT_SAPLV46H_001. Additional l
y the import parameter I_VBAPKOM is provided with the
information after the creation of the sal
es document item. The partner rol es can be found in
parameter XVBPAKOM.
Exampl
e:
PROBLEM:You bil llabor hours and you want to have the personalnumber of the empl
oyee who
has done this l
abor in the partner rol
es of sal
es document item.
SOLUTION:Create a partner rol
e ZP for the empl
oyee and impl
ement the fol
lowing coding:
IF NOT I_SDSM_DLI-PERNR IS INITIAL.

CLEAR XVBPAKOM.
XVBPAKOM-POSNR = I_VBAPKOM-POSNR.
XVBPAKOM-PARVW = 'ZP'.
XVBPAKOM-PERNR = I_SDSM_DLI-PERNR.
APPEND XVBPAKOM.
ENDIF.
4.9.3 Change Pricing Data
If it is not enough to have your characteristic in the sal

es document item,you can also forward it
to the pricing if you have maintained conditions based on dynamic items characteristics. You can
move fiel ds from the sal es document to the pricing communication structure in
USEREXIT_PRICING_PREPARE_TKOMP and USEREXIT_PRICING_PREPARE_TKOMK which
can both be found in Incl ude MV45AFZZ. Pricing structure KOMK contains the header fiel ds,
structure KOMP contains the item fiel ds.
Exampl
e:
PROBLEM:You want to use the personalnumber in pricing.
SOLUTION: The fiel d PERNR exists al ready in structure KOMP. Therefore,you have onl
y to
define access sequences and condition tabl
es containing PERNR. Add the fol l
owing code to
USEREXIT_PRICING_PREPARE_TKOMP:
READ TABLE XVBPA

WITH KEY POSNR = VBAP-POSNR
PARVW = 'ZP'.
IF SY-SUBRC = 0.
TKOMP-PERNR = XVBPA-PERNR.
ENDIF.

4.10 OtherExits in SD
There are a lot of other exits in SD. To explain them allexceeds the scope of this paper. One
problem 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 similar to table VBAP and are the keyof your
tabl
e ZZVBAPADD. Create al so two function modul es for loading 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 module to get the additionaldata. In USEREXIT_SAVE_DOCUMENT the data has to
be saved using your update modul e. Finally USEREXIT_DELETE_DOCUMENT must be used to
remove your additionaldata if the sales document is del eted.
4.11 Menu Exit (EXIT_SAPLAD14_006,EXIT_SAPLAD14_008)
There is often the need to perform specialoperations on the data currently being processed or to
start additionaltasks out of the dial
og. For exampl e,you want to set al litems to billl
ater if the
open amount is smal l
er than 10 euros.
Such functions can be performed by the menu exit which is cal l
ed from the dynamic item
structure overview screen. The exit can be accessed by the user under menu '
Edit'
. To activate
the exit,you have to set first a name for the menu item by EXIT_SAPLAD14_008. This is easily
done by giving a text string to export parameter I_MENU_TEXT.
If the user selects the menu item,EXIT_SAPLAD14_006 is cal l
ed. The exit provides several
information. Parameter I_MODE offers some generalinformation about the current input state on
screen (see Tabl e 11). From parameter table IT_MARK onl y the fields ID (node number) and
MARK are used,indicating that the user has marked a node or item on screen. The node or item
has to be marked in the tabl e controland not in the hierarchy tree. Parameter IT_RSTHIE
contains the hierarchy structure with ID, TYPE and NAME. The ID is the same as in
EXIT_SAPLAD13_001. The name is the name displ ayed on the screen and depends,therefore,
on the actualuser settings.
SUTWVYXWZ [\V\]UÛT_â` b\]YX_c_V\d
eUf_gUh\iUj k_l\m n_oqp\r sYtWu\v\w\oLx
f_yUz\h\i\{ |\wU}_pLlq~LrYWoU}UtWv\w\p\rLr\v\m\v sYs\\lUn\_m
YUn_vU_mYWm\w
pU_\pU_m\v\\p\o
S yU_U\ Un\\_pUamLpU_mU_wL\lYt_n_U_o U=U\t\t\__
l\o\mU}_lU_p
=_p_Up\\m
U\\ Un\\_pUamLrYWoU}UtWv\w\p\rLUn\\_pU_\w |Y|U_vU_o\v\\mYWlU=Un\\_pU_\w
YUWUp\\mLUn\\_pU_\w
\lU_mU_lYt\t\__LvU_p\vLUn\\_p_\w
Table 11:Param eterI_MODE ofEXIT_SAPLAD14_006

SUTWVYXWZ [qV\]UÛT_^_` U ]U^_`\V\]UUXWVL

j_h kal\r\p \n_U_pU
h_Uz\\\_ \yU{\_e n\\_pU_\wLl\~Lv\\lUn\_mL¡\vYt_n_p\o
h_Uz\\\ [ {Uj_z\f ¢qUWmLl\~L\p\v\oUn\_pLl\~L£Un_vU_mYWmYWp\o
h_Uz\\\\ b\¤ \yU{\_e n\\_pU_\wLl\~ _p\¡\pU\n_p\o
h_Uz\\\\¥\{ [ g\ sq\\lUn\_mY__4__rYW\v\m\lU ¦U§_¨
h_Uz\\\_yU [ g\ s}\}_lU_mYWlU_\pU_m _p\v\o\lU
h_Uz\\\\\_gUh_g kal\m n_o\p\r
h_Uz\\©\_ \ª\«\eU_ sq\lUn\_mL~U_l\Lo\lUn\_\p
h_Uz\\©\_ \ª\«Yj_z b sq\lUn\_m4__¡\lYW\p\r
h_Uz\\©\_ \ª\«Uz_Yj sq\lUn\_mLlU}_pU
h_Uz\\©\_ \ª\«Uz_g\ sq\lUn\_mLm\l U\t\t ¦U§_¨
h_Uz\\©\_ \ª\«Ui_y\ sq\lUn\_mLm\l }_l\o\mU}_lU_p ¦U§_¨
h_Uz\\©\_ \ª\«Uz_g\ sq\lUn\_mLm\l _p_Up\\m ¦U§_¨
h_Uz\\¬\ [ {_«\eU_ n_vU_mYWm\wL~U_l\Lo\lUn\_\p
h_Uz\\¬\ [ {_«Yj_z b n_vU_mYWm\w4__¡\lYW\p\r
h_Uz\\¬\ [ {_«Uz_Yj n_vU_mYWm\wLlU}_pU
h_Uz\\¬\ [ {_«Uz_g\ n_vU_mYWm\wLm\l U\t\t ¦U§_¨
h_Uz\\¬\ [ {_«Uz_g\ n_vU_mYWm\wLm\l }_l\o\mU}_lU_p ¦U§_¨
h_Uz\\¬\ [ {_«Ui_y\ n_vU_mYWm\wLm\l _p_Up\\m ¦U§_¨
h_Uz\\\\_y\Uz_g\ pU_\pU_m\v\\pLm\l U\t\t ¦U§_¨
h_Uz\\\\_y\Uz_g\ pU_\pU_m\v\\pLm\l }_l\o\mU}_lU_p ¦U§_¨
h_Uz\\\\_y\Ui_y\ pU_\pU_m\v\\pLm\l _p_Up\\m ¦U§_¨
h_Uz\\®\_ \ª\«U bU¯ ap\¡\pU\n_pLl\~ _l\r\p
h_Uz\\®\_ \ª\«U b kal\m n_o\p\r
h_Uz\\®\_ \ª\«U b ©
h_Uz\\®\_ \ª\«U b ¬
h_Uz\\®\_ \ª\«U [U¯
h_Uz\\®\_ \ª\«U [
h_Uz\\®\_ \ª\«U [ ©
h_Uz\\®\\_y\Uz_g\ ¤ pU_\pU_m\v\\pLm\l U\t\t
h_Uz\\®\\_y\Uz_g\ ¤ pU_\pU_m\v\\pLm\l }_l\o\mU}_lU_p
h_Uz\\®\\_y\Ui_y\ ¤ pU_\pU_m\v\\pLm\l _p_Up\\m
h_Uz\\®\_ \ª\«U¥_y\e sq\lUn\_m _v\oYWoL~\lUL}_pU_\pU_m\v\\p\o
h_Uz\\®\ [ {_«U¥_y\e n_vU_mYWm\w _v\oYWoL~\lUL}_pU_\pU_m\v\\p\o
S i_«Uh\iUj ¨°WUU=k_l\r\p4WoLr\wU_v\YW4Wm\p\
Table 12 :Param eterET_VALUES ofEXIT_SAPLAD14_006
Parameter ET_VALUES contains the nodes'val ues. An overview of the fields'meaning is shown
in Table 12,where you can al
so find the changeabl
e fiel
ds of this tabl
e. Although you can change
'bil
l'
,'rej
ect'and 'postpone'value of the amount,quantity and percentages,the fol lowing rul
es
have to be observed:
" The system checks the changes in the foll
owing order:percentages,control ling area
currency,quantity,transaction currency,object currency. The first changed value
overwrites the others.
" The sum of 'bil

l'
,'postpone'and 'reject'is always equalto the open val
ue. So if the sum is
not equal,the reject col
umn gets the difference between the open value and the sum of
the bil
land postpone val ue.
" The accounting indicator can be changed together with the val
ues.
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.

FIELD-SYMBOLS <VALUE> LIKE LINE OF ET_VALUES.

LOOP AT ET_VALUES
ASSIGNING <VALUE>
WHERE DYNP3-WXGNYI < 10.
<VALUE>-DYNP3-WXGNOW = 0.
<VALUE>-DYNP3-WXGLAT = <VALUE>-DYNP3-WXGNYI.
<VALUE>-DYNP3-WXGNOT = 0.
<VALUE>-DYNP4-MEGNOW = 0.
<VALUE>-DYNP4-MEGLAT = <VALUE>-DYNP4-MEGNYI.
<VALUE>-DYNP4-MEGNOT = 0.
<VALUE>-DYNP5-RATNOW = 0.
<VALUE>-DYNP5-RATLAT = 100.
<VALUE>-DYNP5-RATNOT = 0.
ENDLOOP.
4.12 Exits forResults Analysis
For documentation of the exits in resul

ts anal
ysis,see OSS notes 191546 and 189716.
4.13 Delete Messages in Collective Processing List (BAdI

AD01_RRB_COLLECTIVE1)
There is often the need to reduce the number of messages shown in the message list and result list in
collective processing (DP95,DP96,DP97). E.g. messages with ID VPK1310,AD01261and AD01
263 as well as AD01243shouldn’t be shown in both lists. The BAdI-implementation could be look
as follows:
METHOD fill_additional_fields.
DATA: l_error_list LIKE LINE OF ct_error_list,

l_collective_result LIKE LINE OF ct_collective_result,
l_tabix LIKE sy-tabix.
LOOP AT ct_error_list INTO l_error_list.
IF ( l_error_list-arbgb = 'AD01' AND

( l_error_list-txtnr = '261' OR l_error_list-txtnr = '263' ) )
OR l_error_list-arbgb = 'VPK1' AND l_error_list-txtnr = '310'
OR l_error_list-arbgb = 'AD01' AND l_error_list-txtnr = '243'.
DELETE ct_error_list.
l_tabix = sy-tabix - 1.
DELETE ct_error_list INDEX l_tabix.
ENDIF.
ENDLOOP.
LOOP AT ct_collective_result INTO l_collective_result.

IF l_collective_result-st_text = 'Item Could Not Be Processed'
OR l_collective_result-st_text = 'Items Cannot Be Processed'
OR l_collective_result-st_text = 'No relevant items exist'
OR l_collective_result-st_text = 'No expenditure items found'.

DELETE ct_collective_result.
ENDIF.
ENDLOOP.
ENDM ETHOD.
4.14 Creating "Solutions"with Custom erExits
A col l
ection of customer enhancements were provided to adj ust the DIP to your needs. The exits
itsel
f should hel p to solve a lot of probl
ems. But sometimes it' s necessary to combine the exits for
a certain business process. In this chapter, sol utions are described for the most common
probl ems,which are not covered by our standard del ivery. Most of them are based on questions
customers and consul tants send to SAP via OSS or mail . W e want to say thank you for giving us
a closer lookto the probl ems out in the world.
4.14.1 Use of service operation and short text in the debit memo request
Resource rel ated bil

ling 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 billing,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 ling 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 visible 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 all
,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
leads us straight to the service operations in table AFVC where the operation number (AFVC-
VORNR) 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
trouble,if these values are changed in the service order after they are bil
led. The system woul d
create different dynamic items and the previousl y bil
led 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 fillthem in EXIT_SAPLAD12_003.
STATICS Z_AFRU TYPE AFRU.

FIELD-SYMBOLS <ZCOVP> TYPE COVP.
CASE I_TABNAME.
WHEN 'COVP'.
ASSIGN I_COST_VALUE TO <ZCOVP>.
CASE I_FIELDNAME.

WHEN 'ZZAUFPL' OR 'ZZAPLZL'.

IF Z_AFRU-RUECK <> <ZCOVP>-REFBN
OR Z_AFRU-RMZHL <> <ZCOVP>-AWORG.
CLEAR Z_AFRU.
SELECT RUECK RMZHL AUFPL APLZL
FROM AFRU
INTO CORRESPONDING FIELDS OF Z_AFRU
WHERE RUECK = <ZCOVP>-REFBN
AND RMZHL = <ZCOVP>-AWORG.
ENDSELECT.
ENDIF.
CASE I_FIELDNAME.
WHEN 'ZZAUFPL'.
E_ATTRI_VALUE = Z_AFRU-AUFPL.
WHEN 'ZZAPLZL'.
E_ATTRI_VALUE = Z_AFRU-APLZL.
ENDCASE.
ENDCASE.
ENDCASE.
2. Second,we define two dependent characteristics ZZVORNR (type VORNR) and ZZVORTX
(type LTXA1) and fil
l them in EXIT_SAPLAD12_004. These two CHARACTERISTICS
DEPEND ON ZZAUFPL AND ZZAPLZL.
STATICS Z_AFVC TYPE AFVC.

FIELD-SYMBOLS <ZFIELD> TYPE AD01FIELDS.
LOOP AT IT_FIELDS ASSIGNING <ZFIELD>
WHERE NOT DER_FIELD IS INITIAL AND" DEPENDENT CHAR.
NOT CHAR_REL IS INITIAL. " CHAR. IS RELEVANT
WHEN 'ZZVORNR' OR 'ZZVORTX'.
CHECK NOT I_AD01ATTRI-ZZAUFPL IS INITIAL
AND NOT I_AD01ATTRI-ZZAPLZL IS INITIAL.
IF Z_AFVC-AUFPL <> I_AD01ATTRI-ZZAUFPL
OR Z_AFVC-APLZL <> I_AD01ATTRI-ZZAPLZL.
SELECT AUFPL APLZL VORNR LTXA1
FROM AFVC
INTO CORRESPONDING FIELDS OF Z_AFVC
WHERE AUFPL = I_AD01ATTRI-ZZAUFPL
AND APLZL = I_AD01ATTRI-ZZAPLZL.
ENDSELECT.
ENDIF.
WHEN 'ZZVORNR'.
C_AD01ATTRD-ZZVORNR = Z_AFVC-VORNR.
WHEN 'ZZVORTX'.
C_AD01ATTRD-ZZVORTX = Z_AFVC-LTXA1.
ENDCASE.
ENDCASE.
ENDLOOP.

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 NOT C_VBAPKOM-ZZVORNR IS INITIAL

OR NOT C_VBAPKOM-ZZVORTX IS INITIAL.
CONCATENATE C_VBAPKOM-ZZVORNR C_VBAPKOM-ZZVORTX
INTO C_VBAPKOM-ARKTX
SEPARATED BY SPACE.
ENDIF.
4. Fourth,we want to see the operation number and text al

so in the sal
es price view and in each
dynamic item instead of the materialmaster short text. This can be achieved by coding
EXIT_SAPLAD13_001:
IF NOT I_DLIA-ZZVORNR IS INITIAL

OR NOT I_DLIA-ZZVORTX IS INITIAL.
CONCATENATE I_DLIA-ZZVORNR I_DLIA-ZZVORTX
INTO C_RSTTXT-TEXT40
SEPARATED BY SPACE.
ENDIF.

You may have noticed that in this exampl e,some data read from database tabl es is buffered in
static variables to reduce database and network l oad while running the transaction. This buffering
is sufficient for smal l
er service orders with few operations and confirmations. If you have bigger
service orders with l ots of operations and confirmations,you shoul d think about impl ementing
internalbuffer tabl es for the AFVC and AFRU entries. These gl obalbuffer tabl es shoul d be
defined in separate function groups,so they can be accessed by the different exits by cal ling
function modul es. This al
lows also an impl ementation without using dependent characteristics for
the operation number and text. The texts in EXIT_SAPLAD13_001 and EXIT_SAPLV46H_001
are then filled directly by the buffered operation data and not by the characteristics ZZVORNR
and ZZVORTX.

5 Differences between Releases

The dynamic item processor was first shipped in R/3 with Rel ease 4.5. Of course,there have
been further devel opments after release 4.5B. This paper describes the state of the DIP in
Release 4.6C. In the fol
lowing,you can find an overview of the changes since R/3 Rel
ease 4.5.
5.1 New Functions in 4.7
" Document Fl ow Evaluations 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 billed,rej ected,and open
resources/expenses in a structure overview simil ar to the expenditure view in resource-
related billing. You can change the structure interactivel y. The billing requests are l
isted in
detailfor each resource item. You can navigate to the bil ling request directl
yfrom the
resul t overview. Many other functions,such as fil tering,enabl e you to make a flexible
eval uation. You eval uate the document fl ow using the transactions DP99A,DP99B and
DP99C. These transactions differ onl y in their selection options.
" Document Fl ow Evaluation for Bill

ing Request
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can displ ayexpenditures bil led
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
led resource items
for the bil
ling request. You have to enter the debit memo request and credit memo request
number respectivel y,in the selection screen.
" Performance Improvement Resul ts Anal ysis Using Dynamic Items

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) additionaldata is updated in the
document fl ow of resource-rel ated bil
ling,which are eval uated in the resul ts analysis
methods 14 and 15 (resul ts analysis methods based on dynamic items). The additional
database fiel ds significantl
y improve the performance of these resul ts anal ysis methods,
because resul ts analysis must no l onger eval uate the document fl ow of sal es and
distribution documents (SD documents) to determine the posting date of the revenues
assigned to bil l
ed expenditures.
The enhanced function is active for newl y created bill
ing documents onl y. For existing
document fl ow entries,you can adj ust the old document fl ow entries for the new l ogic with
the program RDPRAFKDAT,therebyimproving performance in period-end cl osing. You do
not need to make any other settings to activate this function.
" New Business Add – Ins (BAdIs)

Further detail
s see chapter 4.3
" Improved ControlOptions for Transferring Quantity and Costs

Further detail
s see chapter 3.1.4
" Increase of MaterialDetermination Lines per DIP Profil

e
Further detail
s see chapter 3.1.4
" New Anal ysis Program for DIP Profil

e
Further detail
s see chapter 3.1.7

" Creating Quotation from the Project Buil

der
Further detail
s see chapter 2.1.4.2
" Archiving CO Line Items

Further detail
s see chapter 2.5
" Enhancement Col lective Processing for Resource-Rel

ated Bil
ling
Further detail
s see chapter 6
" Resource-Rel ated Down Payments and Bil

ling Pl
an
Further detail
s see chapter 2.1.5
" InitialScreen of RRB

Further details see chapter 2.3
5.2 New Functions in 4.6C
" New and enhanced business processes

$ Pricing for Proj
ects is now integrated in Proj ect Builder,based on new source '
Easy Cost
Planning' . Now it is possibl
e to create pricings without an operative proj
ect.
$ Pricing for Proj
ects based on an inquiry can be based on '
Easy Cost Pl
anning'
.
$ Existing pricings or saved data of resource-rel
ated bil
ling can be refreshed from sources keeping
al
lm anualchanges.
" New functions in the user interface

$ In sales price view,you have now the sam e possibil ity to change the values postponed,rej ected,
or to be bill
ed . You can see here the dynam ic item s the sal es docum ent item s (pricing item s)
are based on.
$ The hierarchy change in sales price basis is now possibl
e for al
lrelevant characteristics of the
dynam ic item profil
e. Therefore you can add or rem ove characteristics from structuring.
" New functions in customizing
$ W ith sign '
DI w/Material '(DIP profil
e,view ' Usage' ). it is now possibl
e to have the system
rem ove al ldynam ic item s where m aterialdeterm ination fail ed.
$ There are severalnew characteristics del
ivered:PersonalNum ber,Activity Num ber,Business
Process,W ork Center,Plant of W ork Center,
$ W ith sign '
Conversion quantity'(DIP profil e,view '
Materialdeterm ination'),It is now possible to
convert autom atical lyin the sales docum ent item the quantityof the dynam ic item into sales unit
or the base unit of the determ ined m aterial.
$ You can now enter singl
e val
ues in the m aterialdeterm ination criteria.
$ W here ever you can enter a set in custom izing,you are now abl
e to j
um p directl
y to the set
m aintenance toolfor creating,changing or viewing a set.
$ Source '
Easy Cost Pl
anning for W BS el
em ents was added.
The navigation in DIP profil
e was enhanced. You see now al
lthe tim e which profil
e or l
ine you are
viewing or changing.
" New customer enhancements

$ Enhancem ent AD010007 was added with exit EXIT_SAPLAD15_015. It can be used to change
the DI processing inform ation (i.e. the m aterialdeterm ination).
$ Exit EXIT_SAPLAD13_001 was added to enhancem ent AD010001. It can be used to change the
texts of dynam ic item structuring.

5.3 New Functions in 4.6A/B
" New and enhanced business processes

$ The pricings of projects or service orders are now stored in their own database tabl
es. Therefore,
it’
s now possible to create m ore than one pricing per object.
$ The pricing is now better integrated. Prices are updated im m ediatel
y if the user changes any on
screen.
$ Pricing for Proj
ects allows you to create or update bil
ling pl
ans of your proj
ect byusing the
calculated sales price from pricing.
$ It is now possibl
e to perform Pricing for Proj
ects with sim ul
ations.
$ In pricing or resource-rel
ated bil
ling,you can now enter a price date.
$ The l ogic of the '
From period'in resource-rel
ated bil
ling was changed l
etting you define a real
interval.
$ Costs rej
ected earlier are no l
onger displ
ayed if you are rerunning resource-rel
ated bil
ling. The
rej
ected costs can be reopened onl ine.
" New functions in user interface

$ The user interface was com pl
etel
y redesigned. There are now two different views on your
pricing.
$ The sal es price basis view (sim il
ar to the overview screen in Rel
ease 4.5) displ
ays the structure
of your resources. The input m ode (i.e. am ount quantityor percentage) is now directl
yaccessibl e
on screen. There is now a navigation tree for the structure.
$ The sales price view displ
ays the structure of the later created sal
es docum ents. In this view you
access the pricing procedure and adj ust the conditions.
$ To achieve better handl
ing, transactions DP80 and DP90 were spl
it into DP80,DP81,DP90,
and DP91:
$ DP80:Create quotation for service order.
$ DP81:Pricing for Proj
ects
$ DP90:Resource-rel
ated bil
ling for service order and sal
es docum ents
$ DP91:Resource-rel
ated bil
ling for sal
es docum ents
$ The new entry screens are enhanced for better navigation. You can now create a sal es
docum ent im m ediatel
ywithout entering the overview screen. Most of the settings are accessibl
e
on the entry screen.
$ In DP81,the user can now enter a proj
ect definition or a W BS el
em ent. The retrievalof the sal
es
docum ents is done bythe system .
" New functions in customizing

$ As there is no possibil
ity (and need) to enter m anualconditions on dynam ic item l evel
. The
custom izing in ODP4 was reduced to the definition of the condition for the costs.
$ It'
s possible to switch off the '
No sum m arization'indicator for the unit of m easure and the
transaction quantity. This al l
ows m uch m ore condensed item s in the sal es docum ent when bil
ling
am ounts onl y.

6 Collective Run ofResource-Related Billing

(DP95,DP96,DP97)
Using transaction DP95,you can start the report for col
lective run for resource-rel
ated bil
ling.
W ith the col
lective run,you can:
$ Create directl
y debit/credit m em o requests from the source data.
$ Create a saved extract which can be later processed either in DP90/DP91 or once
again in DP95. This saved extract represents a kind of '
snapshot'.
$ Refresh a saved extract from source by keeping m anualchanges.
$ Create a sal
es docum ent on basis of a saved extract. The extract can be created either in
DP90/DP91 or byperform ing DP95.
There are some additionalsettings to be specified l ike price date or the date range of sel
ection.
The report can be run in the foreground or as a batch j
ob.
The report returns three l ists. An overview l
ist shows the settings and the number of processed
input objects. In a detaill
ist,you can see a l ist of al
lprocessed obj ects with the generated sal
es
documents. If an error occurs,there is an additionalerror l ist displ
aying an overview where the
error has happened
If you do not run the report in batch,you can navigate to the source order and to the created
debit/credit memo requests bydoubl e cl
icking the col
umn of the l
ist.
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you have additionalsel ection options for
sales orders or service orders when col lectivel
y processing resource-rel
ated bil
ling. You can find
this improved coll
ective processing in the foll
owing programs:
" The transaction DP96 offers an improved sel
ection of sal
es orders.
" The transaction DP97 extends the sel

ection options for service orders.

7 Conversion from Old to New Resource-Related Billing

(DP70)
W ith the Dynamic Item Processor introduced with R/3 Rel ease 4.5,there was al so introduced a
new business process for resource-rel ated bil
ling,described in this paper. The new resource-
related bil
ling replaces the old one al
so knows under transaction code VA90. The ol d resource-
related billing wil
lbe shipped up to and incl uding Release 4.6C. Later rel eases starting with
Rel ease 4.70 willno longer incl
ude VA90.
If you are upgrading from a release before 4.5,you can stil luse old VA90 in Rel
ease 4.5 and 4.6.
It is possibl
e to run both processes in parallel. This al
lows you to upgrade your system and del ay
the conversion of your resource-rel ated bil
ling process. If your new system is otherwise running
wel l
,you can do a smooth shift to the new DP90/DP91 without anypressure.
In fact,SAP recommends that you finish bil l
ing ol
d orders with VA90 and bil lonl y new orders with
DP90. This way of upgrade makes the fl ow conversion unnecessary and preventing al so from
rounding differences in the converted fl
ow because the new flow is stored differently in DP90.
Neverthel ess,you want to or you have to migrate to the new resource-rel ated bil
ling,because you
are bil
ling proj
ects. As proj ects are objects with l
ong l
ives,migration is recommended to prevent
the existence of two different business process running side by side for a l
ong time.
Pl
ease take notice of note 442170 for detail
s on “Quickconversion from VA90 to DP90”.
7.1 Conversion ofBilling Flow and Custom izing
To convert your order from VA90 to DP90,you can use the fl ow conversion report accessible
using transaction DP70. Al though its reports al
low an automatic conversion of the document fl
ow,
you have to do some manual tasks in the conversion process because, for exampl e, the
customizing settings are not converted.
For a compl
ete conversion,carryout the fol
lowing steps:
1. Set up your customizing for new resource-rel ated bill

ing. This incl
udes the DIP profile
(ODP1), the specification of cost conditions (ODP4) and the definition of a new resul ts
analysis key if you are using resource-rel
ated results anal
ysis.
2. Run transaction DP70 to convert the flow of bil

led costs. DP70 al
so sets the DIP profil
e in the
sal
es order item or the service order.
3. Change the resul

ts anal
ysis keyin your sal
es order item,service order or proj
ect.
Note that proj

ects bil
led on a resource-related basis are al
so converted by running DP70 with the
sales order used for bil
ling the proj
ect. Most manualwork in the conversion process has to be
done by setting up the materialdetermination (if you want to use the al ready existing material
determination see note 442170). The biggest difference between VA90 and DP90 is the l ack of
any time dependency for the materialdetermination. If you need one, you now have to use
enhancement AD010007.
The conversion report can transfer the fl
ow of actualcosts and statisticalkey figures. For the first
one,you must have a source sel ection line for '
ActualCosts - Line Items'in your profile,for the

second one the source ' ActualStatisticalKey Figures - Line Items'is necessary. There is no
conversion of bil
led items added by using the VA90 enhancement KSDIEX01,but you can use
report RDPFLOW 00 as a templ ate for your conversion.
Each l ine item is converted into dynamic items by deriving the rel evant characteristics of the DIP
profil
e. Therefore it is now possibl e that for different debit memo request items to be billed by the
same dynamic item al though they had a different expenditure ID in VA90. Owing to the
summarization l ogic of the DIP,different expenditure items are now probabl y mapped to the
same dynamic item. Costs from purchase order are al ready summarized by VA90. This
summarization can no l onger be kept in DP90. The conversion report distributes the sum of bil led
costs of an purchase order item to the l ine items,the summarized val ue is based. The ol dest l
ine
items are fil l
ed first. The distribution is also done with respect to the account assignment if you
are using purchase orders with mul tipl
e account assignments.
VA90 always selects al
lcosts. Therefore,your new profil
e should not narrow the sel
ection,except
you narrowed the selection in VA90 by using KSDIEX01. Otherwise when first accessing DP90,
you would get not al
lthe costs you selected,but only the source costs bil
led, with the opposite
sign.
7.2 Conversion ofCustom erEnhancem ents
The new dynamic item processor does not support the exits of VA90. For the most common
business processes impl
emented in enhancement KSDIEX01 and in the form routines of program
RV45HFZZ the fol l
owing repl
acement strategies are recommended:
" Materialdetermination different from SAP standard l
ogic:You can use now enhancement
AD010007 (see al so note 442170).
" Creating additionalattributes for the items selected in standard:Instead of adding fiel
ds to
structure EBINFO,you can now create independent and dependent characteristics in
enhancement AD010003. Note that the ' No summarization'indicator must be set for your
characteristics if you want to use them in SD.
" New fil

ter criteria:For this issue,you have now a wide varietyof possibil ities. First you can
add selection 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 selection in enhancement
AD010001. Final ly,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.
" Reading your own items for bil l

ing:Use enhancement AD010005 to add your own
sources. In the DIP,it is no l
onger necessary to define your own l
ogic for a key of an
expenditure item (EXPID). Additional l
yyou do not have to care about the flow update.
" Summarizing the item information to be transferred:W ith the incl

uded summarization
possibilities,it is no l
onger necessary to add your own summarization l
ogic. You can easil y
switching characteristics on and off which you want to summarize over or not. If you stil
l
want to do some additionalsummarization before the creation of dynamic items,you can
use exit EXIT_SAPLAD15_010 of enhancement AD010002.
" Create a debit memo request with main item and sub-items:This can be repl
aced by the
business process with the service product.

" Form routine USEREXIT_IN_REQ_ITEM is repl

aced by exit EXIT_SAPLV46H_001 of
enhancement V46H0001.
" Form routine USEREXIT_IN_REQ_ITEM_PARTNER is repl

aced by exit
EXIT_SAPLV46H_002 of enhancement V46H0001.
Of course,you can al
so use the BAdIs described in chapter 4.3 instead of the corresponding
enhancement/exit.
7.3 Changes to the UserInterface
The biggest change in the user interface is that there is now the additionalscreen,where the user
can define the resources to be bil led, rejected, or postponed. This offers a l ot of scope for
improved processing of resource-rel ated billing. For exampl e,you do not have to create a debit
memo request for costs never to be bil led. You can rej ect the costs in the new overview screen.
Neverthel ess,it is possibl
e to create a debit memo request directl y from the entry screen with the
button 'Save Bil ling Request'accessibl e by the same key (F5) as in VA90. To go directl y to the
debit memo request in change mode,you have to set al so in the user settings the sign 'Show
bil
ling request after saving' . The onl y difference: The debit memo request is now saved on
database before It is opened again in change mode.
The 'Posting date from'on the input screen is repl
aced by '
Period from' . The option '
Statisticalkey
figure'has now to be handl ed by an additionalsource sel ection line in the DIP profil e. The
possibil
ity of an object sel
ection l
ist is not incl
uded in DP90. If you need this function,you must
use enhancement AD010001 or AD010002.

8 Figures
Figure 1:Business Process of Resource-Rel ated Bil ling ........................................................ 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 ling 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

9 Tables
Tabl
e 1:Billing Form and Rel evance for Bil ling...................................................................... 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

10 Changes to this docum ent
10.1 Version 1.1
" Chapter 2.2.1 revised.
" Added chapter "2.1.4.4 AdditionalPrograms for Pricing for Proj

ects"
" Added some hints for characteristics "Accounting indicator"and "Bil

ling form"to chapter
"3.1.2.1 Use of Characteristics".
" Added some hints to chapter "3.1.3 Source Sel

ection".
" "Figure 22:Cal

ling Sequence of Customer Enhancements"revised.
" Description of new interface of exit EXIT_SAPLAD15_005 added to chapter 4.6.
" Added another exampl

e to chapter "4.9.1 Change Item Data".
10.2 Version 2.0
" Chapter "2.1.3.2 Quoting and Bil

ling of Service Products"revised.
" Chapter “2.1.1 Resource-Rel

ated Bil
ling of Sal
es Documents,Service Orders and
Proj
ects”updated
" Chapter “2.1.3.2 Quoting and Bil

ling of Service Products”updated.
" Chapter 2.1.4.2 Addition:Report “Struct_Quotation_For_Pricing”
" New chapter “2.1.5 Resource-Rel

ated Down Payments”added.
" New chapter “2.4 Archiving CO Line Items”added.
" Chapter “3.1.4 MaterialDetermination”revised
" Chapter “3.1.7 Profil

e Check (ODP2)”updated.
" New Chapter “4.1 BAdIs”
" Added new chapters 4.1.1 – 4.1.4 (severalBAdIs)
" Removed the description of the ol

d interface of EXIT_SAPLAD15_005 from chapter 4.6.
" Chapter “5.1 New Function in 4.7”added
" Chapter “6. Col

lective Run of Resource-Rel
ated Bil
ling (DP95,DP96,DP97) revised
" Chapter “7. Conversion from Ol

d to New Resource-Rel
ated Bil
ling”

Dip Profiles Documentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dip Profiles Documentation

Uploaded by

Copyright:

Available Formats

Introduction to the Dynamic Item Processor

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 1 of 89

Copyright ! 2007 SAP AG. All rights reserved.

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 2 of 89

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 3 of 89

4.4.3 Filter or change the selected data (EXIT_SAPLAD15_010) ...............................59

7 CONVERSION FROM OLD TO NEW RESOURCE-RELATED BILLING (DP70).......84

10 CHANGES TO THIS DOCUMENT ...........................................................................89

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 4 of 89

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 5 of 89

2.1 Business Processes

In Resource-rel ated bill

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 6 of 89

For the bil

Yes Saved data exists? No

Read data from

Create debit memo

Figure 1:Business Process ofResource-Related Billing

From SAP R/3 Enterprise 4.70,you can process resource-rel

Resource-related results anal

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 7 of 89

1. Derive Cost of Sal es from Resource-Rel ated Bill

2. Derive Revenue from Resource-Rel ated Billing and Sim ul

Resource Related Billing

Objects Actual RRB Actual

DI-Processor Results Settlem ent

Resource Related Results Analysis

Figure 2:Business Process ofResource-Related Results Analysis

2.1.3 Quotation Creation and Resource-Rel

2.1.3.1 Normal Process for Quotation Creation

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 8 of 89

Saved pricing exists? No

Load pricing Create new pricing

Pricing for service

Figure 3:Business Process ofQuotations forService Orders

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 9 of 89

2.1.3.2 Quoting and Billing of Service Products

" Costs:The sub-items are normal ly relevant for bil

The dynamic item characteristic 'Product' has to be set as rel

2.1.3.3 Billing Form and Relevance for Billing

Quotation creation Resource-Related Billing

The rel evance for bil l

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 10 of 89

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 11 of 89

2.1.4 Pricing for Proj

2.1.4.1 Pricing for Projects Based on an Inquiry

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 12 of 89

Pricing exists for proj

Load saved pricing

Sales price Sal

Figure 4:Business Process ofPricing forProjects Based on an Inquiry

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 13 of 89

Figure 5:Business Process ofPricing forProjects in Project Builder

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 14 of 89

2.1.4.3 Update of Planned Revenues for Projects

The update of planned revenues for projects is not specificall

anned rev. total

Process 2:without Billling Plan

Sales order(s) M anual

Figure 6:Business Process ofUpdate ofPlanned Revenues forOperative Projects

If you are using simul ations,the only way to get pl

SAP AG IntroductionDIP_2.0.doc Version 2.0 – 2007-09-28 Page 15 of 89

You can find this switch at the same point in customizing l

2.1.4.4 Additional Programs for Pricing for Projects