DBM Order Engine Cookbook

Dealer Business
Management
Order Engine
Customizing and Configuration of DBM Order
Engine
Date: September 2007
Release: DBM 6.00, SP02
SAP
Icons in Body Text

Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types
of information at a glance. For more information, see Help on Help
General Information
Classes and Information Classes for Business Information Warehouse on the first page of
any version of SAP Library.
Typographic Conventions
Type Style
Description
Example text
Words or characters quoted from the screen. These include field

names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, graphic titles, and table

titles.
EXAMPLE TEXT
Technical names of system objects. These include report names,

program names, transaction codes, table names, and key concepts of a
programming language when they are surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Output on the screen. This includes file and directory names and their
paths, messages, names of variables and parameters, source text, and
names of installation, upgrade and database tools.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Angle brackets indicate that you replace these
words and characters with appropriate entries to make entries in the
system.
EXAMPLE TEXT
Keys on the keyboard, for example, F2 or ENTER.
2007 SAP AG
Title: DBM Order Engine

Version: 1.0
Page 2 of 60
SAP
Table of Contents
INTRODUCTION..................................................................................................................5
1.1
1.2
PURPOSE OF THE DOCUMENT .........................................................................................5

OVERVIEW ......................................................................................................................5
CUSTOMIZING OF THE EVENTS AND ACTIONS..........................................................8

2.1
CUSTOMIZING - OVERVIEW .............................................................................................8
2.2
DEFINE EVENTS ..............................................................................................................9
2.2.1
Event Customizing ..............................................................................................10
2.2.1.1 Event........................................................................................................................ 10
2.2.1.2 Description............................................................................................................... 10
2.2.1.3 Access Sequence ................................................................................................... 10
2.2.1.4 Selection Level........................................................................................................ 10
2.2.1.5 Selection Dialog Box............................................................................................... 11
2.2.1.6 Delete Selection Flag ............................................................................................. 16
2.2.1.7 Event Mode Control ................................................................................................ 16
2.2.1.8 Event Automatic Save ............................................................................................ 16
2.2.1.9 Usage on Screen .................................................................................................... 17
2.2.1.10 Event Exit Flag........................................................................................................ 20
2.2.1.11 System Event Flag.................................................................................................. 20
2.2.1.12 Tools on Event level ............................................................................................... 21
2.2.2
Subsequent Event Customizing.........................................................................22
2.3
DEFINE ACTIONS ...........................................................................................................24
2.3.1
Action Customizing .............................................................................................26
2.3.1.1 Action....................................................................................................................... 26
2.3.1.2 Description............................................................................................................... 26
2.3.1.3 Execution Level....................................................................................................... 26
2.3.1.4 Update ..................................................................................................................... 27
2.3.1.5 Commit Level .......................................................................................................... 27
2.3.1.6 System Action Flag................................................................................................. 30
2.3.1.7 Dialog Flag .............................................................................................................. 30
2.3.1.8 Status ID.................................................................................................................. 30
2.3.1.9 Status Cancellation Flag ........................................................................................ 30
2.3.1.10 Document Flow Flag............................................................................................... 30
2.3.1.11 Document Flow Object Type.................................................................................. 30
2.3.1.12 Document Flow Sequence Number....................................................................... 34
2.3.1.13 Action BAdI Preparation...................................................................................... 35
2.3.1.14 Action BAdI Execution......................................................................................... 37
2.3.1.15 Action BAdI Finalize ............................................................................................ 40
2.3.2
Action Status Customizing .................................................................................44
2.4
DEFINE TABLE OF CRITERIA ..........................................................................................46
2.5
DEFINE ACCESS SEQUENCES .......................................................................................48
2.6
DEFINE ACTION CONTROL ............................................................................................49
2.7
DEFINE PROCEDURE FOR ORDER STATUS ....................................................................53
2.8
ASSIGN PROCEDURE FOR ORDER STATUS....................................................................54
2.9
DEFINE SCHEMA FOR MESSAGE SUBSTITUTION ............................................................54
2.10 VMS INTEGRATION .......................................................................................................57
2.11 DBM VERSIONIZER .......................................................................................................58
2007 SAP AG

Version: 1.0
Page 3 of 60
SAP
2007 SAP AG

Version: 1.0
Page 4 of 60
SAP
1 Introduction
1.1 Purpose of the document
As a Dealer Management System, this component (DBM) supports the industry-specific
sales and service processes of dealers and dealer organizations, as well as vehicle
importers, authorized dealers, and OEM vendors. This includes handling of new and used
vehicles sales, vehicle service, and parts management.
The component is distinguished by its multi-brand capability as well as its ability to manage
different locations, customer-specific settings with regard to language and country, such as
currency and taxes, mean that it can be deployed worldwide.
The component supports the integration of processes between the dealer and the Original
Equipment Manufacturer (OEM) within a vehicle order (vertical integration). Furthermore, it
also supports horizontal integration between dealers. For example, members of dealer
organizations can obtain an overview of the parts and vehicles in stock for the entire dealer
organization.
As a dealer, you can manage an order from its creation, through its completion, and right
down to its billing phase. Order Engine enables processes to be modeled flexibly. In this
way, you can meet different requirements that arise from the OEM or due to the size of a
company.
This document provides you with a description of the Order Engine concept in Dealer
Business Management (DBM) solution.
The target audience of this document is implementation consultants. It describes in detail
how the customer business process can be mapped in the DBM solution using events and
actions.
For reasons of simplicity, we use the term dealer throughout this document.
According to context, this term can refer to the car dealer or dealer organizations,
vehicle importers, authorized dealers, or OEM-dedicated vendors.
We also use the term, DBM Order, to refer to orders of all types, such as, Service
Order, Vehicle Order or Parts Order.
1.2 Overview
The Order Engine concept is new and used flexibly in DBM solution. It dealers to control
their business processes based on different criteria like Control Code, Order Type, Item
Category, etc.
2007 SAP AG

Version: 1.0
Page 5 of 60
SAP
The Order Engine concept uses the Events and Actions to control the business processes.
The criteria technique is used to determine actions for an event in a highly flexible manner.
We describe the criteria technique in detail in subsequent sections.
EVENTS
An event refers to a business process step or representation of multiple process steps.
An event is triggered directly by the user, an external interface, or indirectly, for example,
when creating a new order, adding new items to an order, or performing other business
steps.
An event can determine one or more actions.
If the user triggers an event, the Order Engine is called and it executes the determined
order actions in the sequence defined in Order Engine Customizing.
ACTIONS
An action refers to a self-contained business transaction. At the end of an order action, the
system can, for example, trigger an update, set the status, include a new document to
document flow, etc.
The actions can be classified into two groups:
- Business actions that create a dependant document and set a status
- Order actions that control and change the order
Each action results in an implementation where the business logic is implemented.
The link between events and actions is set in the Order Engine Action Control
customizing. For more information, see section 2.4.
2007 SAP AG

Version: 1.0
Page 6 of 60
SAP
The graphic below depicts the operational flow of the Order Engine.
ORDER ENGINE
2007 SAP AG

Version: 1.0
Page 7 of 60
SAP
2 Customizing of the Events and Actions

2.1 Customizing - Overview
As mentioned above, events and actions trigger the operations flow of the Order Engine.
To enable the customer to exploit the full flexibility and power of the Order Engine, DBM
provides the possibility to customize the events, actions and the sequence in which they
are executed.
To define the settings for the Order Engine in Customizing, choose Logistics Execution
Dealer Business Management (DBM)
Order
Order Control.
Based on your business process, you can configure the Order Engine using the following
settings under Order Control:
Define Events
Define Action Control
Define Procedure for Order Status
Assign Procedure for Order Status
Define Schema for Message Substitution
Enhancements
Further, under Enhancements, you can use the use the following settings:
Define Status ID
Define Action
BAdI: Action Preparation
BAdI: Action Execution
BAdI: Action Post-Processing
Define Table of Criteria
Define Access Sequence
You link VMS actions to a DBM action via Order Control VMS Extension. In Customizing,
choose Order Control
Order Control VMS Extensions and configure the following
settings:
Define Table of Criteria for Order Control - VMS Action Determination
Define Access Sequence for VMS Action Determination
Define VMS Action Control from Order Action
In addition, you can find the following configuration tools by choosing Order Control
Order Control Tools in Customizing:
2007 SAP AG

Version: 1.0
Page 8 of 60
SAP
Order Engine Version Generator

Order Engine Version Analysis
Order Control Customizing Checks
For a detailed description of the settings, see the respective sub-section under
Customizing.
The description of customizing settings in this document differs in sequence than

that you will find in the IMG.
2.2 Define Events

In this IMG activity, the Events are defined as a first step. An Event is a business process
step which is triggered by a user or an external Interface working on the DBM Order. An
example of an Event would be: Creation of a New Order; Adding a New Item, and so on.
System events play a particularly important role.
System events must not be changed in any way, as this may have unexpected
consequences. For example, if a System Event is deleted, the associated program
might terminate. System Events cannot be replaced. Enhancements are possible,
such as, additional actions or subsequent events.
To configure settings for Order Engine Events, choose Logistics Execution

Dealer
Order Order Control
Define Events in Customizing.
Business Management (DBM)
In customizing for Events, all defined Events are displayed. To view further details, select
an Event and then click Detail or, double-click on an Event.
In the Display View Events: Details screen, you can maintain customizing in the following
areas:
In the application screen area where it is possible to maintain information on the
event itself, such as, Event name, Event description, Selection level, and so on
In the structure under Subsequent Event where you can add, modify, or both,
subsequent events and specify their sequence of execution
2007 SAP AG

Version: 1.0
Page 9 of 60
SAP
2.2.1 Event Customizing

This section describes each element of the Event Details in detail and its influence upon
the Order Engine.
2.2.1.1 Event
Event the name of the event must be unique.
2.2.1.2 Description
Description free text that best describes the event. It should be maintained in all the used
languages.
2.2.1.3 Access Sequence

Access Sequence controls which criteria tables should be read, and in which sequence,
when the event is triggered. Based on criteria tables the Order Engine determines which
actions are assigned to the event (for more information, see the section under Define
Access Sequence).
2.2.1.4 Selection Level

Selection level defines the level in the Orders object hierarchy at which the selection is
made before execution of the event.
2007 SAP AG

Version: 1.0
Page 10 of 60
SAP
This field is used by the Order Engine in conjunction with the Selection Dialog Box (Event
Customizing). For an event, it is defined on the level the selection must be done. Based on
the selection level, the Order Engine flags the right entries and executes the event.
Possible entries, for the flag selection level, are:
0
1
2
3
4
7
Header
Job
Item
Split Header
Split Header and Job
Task
Possibility to redefine
the logic for selection
The levels described here are the standard selection levels delivered by SAP. These
selection levels cover most business processes. To cover customer-specific business
processes that cannot be mapped by the standard selection levels, we offer an
enhancement concept via BADI implementation. You can then redefine your selection
levels. See the example above.
2.2.1.5 Selection Dialog Box

Selection Dialog Box controls the Order Engine in order to display or not a selection
dialog window. This field is used in conjunction with the Selection Level (Event
Customizing).
If the flag is set to Never Display, 3 - Never Display - Select All If No
Selection Is Made or 4 - Never Display - Select all Always then no
selection dialog window will be displayed.
If the flag is set to 1 - If No Selection Is Made or 2 - Always Display then
a selection dialog window is displayed with the entry/entries you defined on Selection Level
(Event Customizing).
2007 SAP AG

Version: 1.0
Page 11 of 60
SAP
Possible entries, for the flag dialog box, are:

Never Display The selection of the entry/entries must be done in the DBM
order itself according to the Customizing for Selection Level (Event Customizing). If
the user doesnt select any entry, the Order Engine will display a message and the
action will be stopped.
For the event GDSMVT_CREATE the Selection Level is Item, then the user
must select the items that should be posted in DBM Order (on the Item tab page,
you must select the item(s) in the ALV grid), otherwise no item is selected and a
message is displayed.
2. Execute Event for the

selected item(s)
1. Select the item(s)
1 If No Selection Is Made the selection can be done in the DBM order

according to the Selection Level (Event Customizing) and then no selection dialog
window will appear. If you do not select any entry in the DBM order a selection
dialog window will appear and then you must select the entry/entries.
2007 SAP AG

Version: 1.0
Page 12 of 60
SAP
Subsequently the Order Engine executes the action(s) assigned to the event for all
the selected items.
For the event GDSMVT_CREATE the Selection Level is Item, then the user can
select the items to be posted, in the DBM Order. (You can select the Items from
the Item list). If you do not select the items in DBM, a selection dialog window will
appear, populated with all items from the order. You then select those items for
posting.
The user doesnt select the

item direct in DBM and press
on button Post GI.
A selection dialog is displayed
where the user selects the
items. The selected item(s) are
posted.
2007 SAP AG
The user selects the item

direct in DBM and press on
button Post GI. No dialog
selection is displayed and
the selected items are
posted.

Version: 1.0
Page 13 of 60
SAP
2 Always Display Independent of the Items selected in the DBM order itself,
a selection dialog window will always be displayed and the user must select the
entry/entries. Subsequently the Order Engine executes the action(s) assigned to
the event for all the selected items.
For the event GDSMVT_CREATE the Selection Level (Event Customizing) is

Item. When the event is triggered by the user, a selection dialog appears,
populated with the Items of the order which are relevant for Goods Movement. The
user selects the required Items for posting the Goods Movement.
Independent of the Items selected in the

DBM order itself, a selection dialog window
will always be displayed and the user must
select the entry/entries.
3 Never Display - Select All If No Selection Is Made The item

selection can be done inside the DBM order itself according to the Selection Level
(Event Customizing). If no Items are selected in the DBM order, the Order Engine
will automatically select all of them. Subsequently, the Order Engine executes the
action(s) assigned to the event for all the selected items.
2007 SAP AG

Version: 1.0
Page 14 of 60
SAP
For the event GDSMVT_CREATE, the Selection Level (Event Customizing) is

Item. Items, for which Goods Movement can be posted, are selected, and then the
Event is triggered. If no items are selected, then the Order Engine pre-selects all
respective Items by default for posting Goods Issue.
The user doesnt select the item

directly in the Item List and clicks
on Post GI. The order engine
selects, automatically, all the items
and posts them.
The user selects the item(s)

direct in Item List and clicks on
Post GI. No dialog selection
is displayed and the selected
items are posted.
4 Never Display - Select all Always Independent of selected Items

in the DBM order itself, the Order Engine will automatically select all items.
Subsequently, the Order Engine executes the action(s) assigned to the event for
all the selected items.
For the event GDSMVT_CREATE the Selection Level (Event Customizing) is

Item. When the event is triggered by the user, independent of the selected Items
in the DBM order itself, the Order Engine will select all relevant items automatically
for posting Goods Issue.
2007 SAP AG

Version: 1.0
Page 15 of 60
SAP
Independent of the selected Items in the

DBM order itself, the Order Engine will select
all of them.
2.2.1.6 Delete Selection Flag

Delete Selection Flag controls the Order Engine in order to determine whether the
previously selected entries should be reset, after the execution of the Event (and
subsequent events) is complete.
2.2.1.7 Event Mode Control

Event Mode Control Determines which events are allowed to be triggered based on the
order state, in conjunction with the status of the order and the order activity type (display
mode, change mode)
1 Always Active these events are always allowed (also in Display Mode)
2 Only Active in Change Mode (Status-Dependent)- these events are
allowed only in Change Mode and only if at least one status relevant action
assigned to the given event can be executed according to the Order status.
3 Always Active in Change Mode these events are always allowed in
Change Mode
2.2.1.8 Event Automatic Save

Event Automatic Save Controls whether the Order Engine needs to automatically save
the DBM Order before the execution of the current Event.
Possible entries for the flag Event Automatic Save, are:
Do Not Save the order is not saved before the execution of the actual event
1 Save Automatically the order is saved first before starting the current
event
2 Save After Query a pop-up window appears and the user must decide if
the order should be saved or not before executing the actual event. On
cancellation of the pop-up the order processing will be stopped.
2007 SAP AG

Version: 1.0
Page 16 of 60
SAP
If a dependant business object is created with an event, the flag must be set,
otherwise, inconsistencies may occur, for example, labor value added -> confirm ->
leave order without save
A confirmation was done for an item, that was never
saved.
2.2.1.9 Usage on Screen

Event Usage on Screen specify if the event has a corresponding control on UI.
Possible entries are:
0 Does Not Appear on the Interface the event has no corresponding
control on the UI level. The event is triggered internally either by another action or
by the UI through the users key stroke.
Event ITEM_CHANGE is triggered by pressing enter after selecting an item.
1 Separate Button on the Interface the event has a corresponding

button in the Application Toolbar. In this case the event can be triggered by the
user clicking on the button. The button is shown only if the event is allowed to be
executed (at least one action assigned to this event can be executed)
2007 SAP AG

Version: 1.0
Page 17 of 60
SAP
Event ITEM_DELETE has its own button on UI. The button is shown in the toolbar
of the ALV grid.
ITEM_DELETE
own button on UI
2 Displayed in the List of Events the event has a corresponding

entry in the list of events container. The list is built dynamically at run time using
this setting. In this case the event can be triggered by selecting it from the list of
events.
The event create notification (NOTIF_CREATE) is shown in the list of events. The
event is shown only if it can be executed (at least one action assigned to this event
2007 SAP AG

Version: 1.0
Page 18 of 60
SAP
can be executed) otherwise is hidden. The Order Engine controls the displaying or
hiding the event based on customizing.
List of Events
3 Dynamic Button on the Interface a button for the Event is

dynamically created in the application toolbar based on the description of the Event
button and icon.
If the Event can be executed (at least one action assigned to this event can be
executed) the button is shown. The generic code is translated, based on
customizing, to the name of the event and the Order Engine is called with the
event name as import parameter.
2007 SAP AG

Version: 1.0
Page 19 of 60
SAP
The corresponding UI button

is shown if the event can be
executed.
2.2.1.10
Event Exit Flag
Event Exit Flag Setting this flag triggers exit of the Order after the completion of the
execution of the Event.
Example: If you set this flag for event ORD_SAVE the order maintenance transaction will
be exited after saving.
2.2.1.11 System Event Flag

System Event Flag System Events are events which change the Order internally and are
delivered by SAP.
The flag indicates whether or not the event is a System Event. System Events play a
particularly important role.
2007 SAP AG

Version: 1.0
Page 20 of 60
SAP
System Events must not be changed, as this may have unexpected consequences.
For example, if they are deleted, the associated program might terminate.
System Events cannot be replaced as these events are hard-coded in the program
flow. System Events can, however, be enhanced by additional actions.
2.2.1.12 Tools on Event level

As of version DBM 6.00, SAP provides useful tools in analyzing the relationship between
events and actions. These tools can be grouped into three categories (each tool has a
corresponding button in the event customizing screen).
Tools on
event level
Event Tree gives a picture regarding the actions determined and subsequent
events assigned to the selected event. You can see which actions are triggered by
the selected event and for each action it shows the execution level, the status
assigned to it, status level and if a Commit should be done. With this feature you
see all relevant information regarding the event and assigned actions without
navigating to the action itself. You can also navigate to the implementation of the
Actions from the tree.
The event GDSMVT_CREATE has as subsequent event ORD_CLOSE and calls

the actions AVAIL_CHECK_B, GDSMVT_CREATE, GDSMVT_SYNC.
2007 SAP AG

Version: 1.0
Page 21 of 60
SAP
Check performs elementary checks on event level as defined in the check tool.
For example this tool checks if the event is already linked to an action or if the
event has an access sequence assigned to it.
Relevance it gives an overview regarding the criteria fields involved in
determining the actions assigned to the event.
For the event GDSMVT_CREATE the relevant criteria fields are sales document
category and technical item category.
2.2.2 Subsequent Event Customizing

Each subsequent event is, in fact, an event as described in the previous section see
Event Customizing. The subsequent event is used if in the business process it is
necessary to execute more than one event in a single step. The subsequent events can be
defined in the Subsequent Events folder.
2007 SAP AG

Version: 1.0
Page 22 of 60
SAP
Subsequent Events are called after the completion of an event to which they are
assigned. This is not the same as in the case of a recursive event call. Here, the event
A is called from another event B through an action assigned to the event B.
2007 SAP AG

Version: 1.0
Page 23 of 60
SAP
2.3 Define Actions

In this IMG activity, the user defines the Actions for order control (order actions). An action
describes a self-contained and closed business transaction.
System actions are delivered only by SAP and change the Order internally. System actions
play a particularly important role. They are required for critical operations of an Order, such
as, create, change, save, and so on.
System actions should not be changed or deleted. However, you can add new actions.
To configure settings for the Order Engine Action in Customizing, choose Logistics
Execution
Order
Order Control
Enhancements
Define Actions.
All defined actions are displayed and the user has the possibility to select the action, and
click on Details to modify the properties of the Action.
2007 SAP AG

Version: 1.0
Page 24 of 60
SAP
Double-click on the desired action or click Details of an action. An overview screen is

displayed in which you can view the primary properties of the Action.
The action maintenance screen consists of two specific areas for maintenance of
Customizing:
The Detail area where the user maintains the primary information regarding the
Action, such as, the action name, action description, execution level, status level,
and so on.
The Status node where the Order Engine status prerequisites are maintained and
these are used to determine whether an action can be executed or not (doubleclick on Status in the structure).
For each action the Order Engine performs some logical steps independent of the Order
Engine customizing executing the BAdIs implementations, in the sequence defined by
creation of BAdI, in BAdI implementation layer. BAdI implementations assigned to an
action can be part of the SAP standard delivery, or, if the process requires, they can be
those of the customers own BAdIs implementation (range of BAdI implementation layer
100-200).
The link between events and actions is created in Customizing under the Order Engine
Action Control.
2007 SAP AG

Version: 1.0
Page 25 of 60
SAP
2.3.1 Action Customizing

This chapter describes each element of an Order Engine Action, and its influence upon the
Order Engine.
The picture below illustrates the main screen of the Action Customizing.
2.3.1.1 Action
Action the name of the action must be unique
2.3.1.2 Description
Description free text that best describes the action. A description of an action is important
for the action log.
2.3.1.3 Execution Level

Execution Level - controls the Order Engine to execute the Action once for the selected
level. The execution is done at the following levels:
1 Header Level
2 Job Level
3 Item Level
5 Split Header Level
2007 SAP AG

Version: 1.0
Page 26 of 60
SAP
7 Task Level
The execution level influences the implementation of the Action. Therefore, a change of the
execution level is normally not possible without replacing/rewriting the BAdI implementation
for the Action since the implementation relies on the initial selected entries.
2.3.1.4 Update
The Update field provides information to the Order Engine on whether a commit should be
performed or not.
1 - Commit
2 - Commit Work and Wait
No Commit
The flag is useful, for instance, if one of the BADI implementations assigned to the action
call standard BAPI, as in such cases it would be necessary to execute a Commit. The
Order Engine checks if the flag Update is set to Commit or Commit Work and Wait,
and if no errors occurred during any of the Actions implementations, then the Order Engine
carries out a commit as is customized.
If the flag Update is set to No Commit the Order Engine does not commit the changes.
These changes would be committed only when a subsequent Action is customized to
Commit.
If an Action requires a database update from the previous action to be completed, than you
must set COMMIT WORK AND WAIT. Example: Creation of material reservation and
posting of a material document.
If a BAPI can be called more than once without commit, it is possible to choose NO
COMMIT and then commit when saving the order.
Independent of the Update flag setting, the Order Engine checks if errors occurred during
an Action execution. In the case of errors, the processing stops and error messages are
displayed.
Commit is always carried out by the Order Engine, no commit statement is allowed in any
Action implementation.
2.3.1.5 Commit Level

The commit level controls the level on which the Order Engine commits. If the flag Update
is set to No Commit, the commit level setting is not taken into account. The commit level
ensures order consistency in case actions create further standard documents. All
processes must be in the same LUW and the commit must be done together.
2007 SAP AG

Version: 1.0
Page 27 of 60
SAP
After every Action the commit will be done after each executed selected
level. Selected level is determined in conjunction with execution level for an action.
For Action CBOOK_WORK the execution level is item. This means that the user
selects the required items on the UI and triggers the event CBOOK_WORK. The
Order Engine will execute the action CBOOK_WORK for each selected item. The
Order Engine will commit repeatedly after each execution of the action for the item.
1 End of an Action the commit will be done at the end of the action. If the
execution level of the action is not header, the action is executed for all selected
items and the commit is done at the end of the action. This commit level is useful if
a single commit is required after the action is executed for all the selected objects.
2 End of an Event the commit will be done at the end of the event.. As
indicated above, an event can be associated with one or more actions. If the event
is associated with more than one action then the Order Engine will execute all the
actions and than do a Commit, if all the actions were successfully executed.
3 After all subsequent Events the Commit will be done after the
execution of all subsequent events.
2007 SAP AG

Version: 1.0
Page 28 of 60
SAP
The graphic below depicts commit control of the Order Engine.
Event
A
Action
A
Level
space
Item 10
Commit
Level 1
Item 20
Commit
Commit
Action
B
Action
C
Level 2
Commit
Subsequent Event A
Subsequent Event B
Level 3
Commit
Event
B
Event
n
When using the setting After all subsequent Events, make sure that all actions
assigned to an event have the same commit level. The Order Engine will otherwise
return an error message.
During external calls with NO_COMMIT all actions should have a commit level 3 if
relevant for a commit.
2007 SAP AG

Version: 1.0
Page 29 of 60
SAP
2.3.1.6 System Action Flag

System actions are delivered by SAP and change the Order internally.
System Action Flag - indicates if the action is a system action or not. System actions are
delivered by SAP and play a particularly important role. They are required for critical
functions like order creation, changing, saving etc, for an order.
System actions should not be changed or deleted. However, you can enhance system
actions with additional execution implementations. You can also enhance system
actions by adding checks in the prepare BAdIs implementation.
2.3.1.7 Dialog Flag

Dialog flag indicates if the function module(s) associated with the Action are allowed to
call a screen or not. For instance RFC function modules shouldnt be associated with an
action which has the field Dialog Flag set.
2.3.1.8 Status ID
The Status ID is the status set for the executed action. The status set by an action could
have an influence on the execution possibility of other actions. For more information, see
the section, Action Status Customizing. For the definition of status level, see Action Status
Customizing.
2.3.1.9
Status Cancellation Flag
Status Cancellation Flag indicates to the Order Engine whether the Action carries out a
reversal of an action status. If this flag is set, then the Order Engine reverses the status of
the action (set the status back to A).
Example: The action GDSMVT_CANCEL cancels the standard documents and sets the
status GDSMVT_CREATE back to initial.
2.3.1.10 Document Flow Flag

Document Flow Flag indicates if the action is relevant for document flow or not. If this flag
is set, the Order Engine will write the document flow, based on the customizing of object
type and sequence number. For more information, see the next section.
2.3.1.11 Document Flow Object Type

Document Flow Object Type - specifies a generic description of an object.
In the object type definition, objects are defined by specification of their components.
An object type has the following components:
2007 SAP AG

Version: 1.0
Page 30 of 60
SAP
Basic data, such as name, creator

Key fields for uniquely identifying an object
Attributes as properties of an object
Methods with parameters and exceptions as valid activities on an object
Events for describing status changes
Implementation in the program
The Object Relationship Service creates the link between the DBM order and the standard
document based on the Document Flow Object Type. With the link created, you can then
define which field and structure from DBM order are associated with the standard
document.
You can find a definition and description of the object types in the tables,
/DBM/OE_DOCFLOW and /DBM/OE_DOCFLOWT, respectively.
Document flow object types delivered by SAP include:
OBJTYPE
SEQ
/DBM/ORDER
TNAME
FNAME
TCODE
BEZEI
BKPF
FB03
Downpayment Request
BKPF
/DBM/SPLHDR_COM
DOCNUM
FB03
Accounting document
BUS2012
ME23N
Pur. Order
BUS2017
Goods Movement
BUS2017
BUS2032
/DBM/VBEP_COM
MBLNR
MB03
MB03
Goods Receipt
/DBM/SPLIT_COM
SDVBELN
VA03
SD Order
BUS2072
/DBM/VBAP_COM
BELNR_K_IN
KSB5
Controlling Document
BUS2072
/DBM/SPLIT_COM
BELNR_E_IN
KSB5
BUS2072
/DBM/SPLIT_COM
BELNR_E_IN
KSB5
BUS2072
/DBM/SPLIT_COM
DOCNUM
KSB5
Cancel Controlling
Document
Time Management
BUS2075
/DBM/VBAK_COM
AUFNR
KO03
Internal Order
BUS2075
/DBM/SPLHDR_COM
AUFNR_REC
KO03
Internal Order
BUS2075
/DBM/SPLHDR_COM
DOCNUM
KKF3
CO Production Order
BUS2093
/DBM/VBEP_COM
RSNUM
MB23
Reservation
BUS2105
/DBM/VBAP_COM
BANFN
ME53
Purchase Requisition
BUS2222
/DBM/SPLIT_COM
DOCNUM
WTY
Warranty Claim
BUS2400
/DBM/VBAP_COM
DOCNUM
/DBM/ORDER03
DBM Order
CACSDOC
/DBM/SPLHDR_COM
DOCNUM
CACSMD513
Commission Document
QMSM
/DBM/SPLHDR_COM
DOCNUM
IQS3
Notification task
VBRK
/DBM/SPLIT_COM
DOCNUM
VF03
Billing Document
VBRK
/DBM/SPLIT_COM
DOCNUM
VF03
VBRK
/DBM/SPLIT_COM
DOCNUM
VF03
Cancel Billing Document

Pro Forma Billing
Document
2007 SAP AG

Version: 1.0
Page 31 of 60
SAP
The following example of action customizing explains the Document Flow customizing for
the action BILLING_CREATE (that is, create standard billing document).
When the action (BILLING_CREATE) is triggered, the Order Engine is notified that a
business document was created during this action (the flag document flow is set). The
Order Engine is also notified of the object type to which this document should be assigned
(Object Type = VBRK).
As described in the overview section of this document, the Order Engine performs the
following steps, sequentially:
2007 SAP AG

Version: 1.0
Page 32 of 60
SAP
Get selected items
Determine the Actions
Check if the action can

be executed
CALL BADI ->
PREPARE
Calls each Actions

implementation
CALL BADI ->
EXECUTION
Set/Reset action status

CALL BADI ->
FINALIZE
Create Document in
Document Flow
CALL BADI ->
FINALIZE
Commit
The Order Engine checks if a document should be added to the Document Flow. Based on
the object type (reading the table /DBM/OE_DOCFLOW) the document number is identified
in DBM communication structures (in our example the billing document is stored in table
/dbm/split_com-docnum see the table above).
The action which creates a document flow entry is responsible to write the relevant
document number in the field structure defined in table /dbm/oe_docflow (in our
2007 SAP AG

Version: 1.0
Page 33 of 60
SAP
example the billing document is passed over the structure /dbm/split_com, field
docnum see the table above).
2.3.1.12 Document Flow Sequence Number

Document Flow Sequence Number the sequence number which is assigned internally by
the system if several entries are stored for the same object type. The object type and
sequence number will identify uniquely, which entry should be selected by the Order
Engine when the action is triggered. In the table /DBM/OE_DOCFLOW, it is possible to
have more entries for the same object type, but pointing to different structures.
In table /DBM/OE_DOCFLOW there are two entries for the object type BUS2075 Internal Order, once for internal order assigned to header (/DBM/VBAK_COMAUFNR), and once for internal order assigned to split header (/DBM/SPLHDR_COMAUFNR_REC) but with different sequence number. This results in two different
actions, respectively: INT_ORD_CREATE and INTORD_CREATE_RE. In
Customizing, these are the same object type, however, they have different sequence
numbers. Each of the actions has a different implementations and the action
implementation itself determines which structure must be updated with the internal
order number.
2 different actions having the

same Object Type, but
different Sequence Number.
First will update the structure
/dbm/vbak_com-aufnr and the
second will update
/dbm/splhdr_com-aufnr-rec
with the internal order number
The action will update

the structure
/dbm/vbak_com-aufnr
with internal order
number
2007 SAP AG

Version: 1.0
The function module

will update the
structure
/dbm/splhdr_comaufnr_rec with
internal order
number
Page 34 of 60
SAP
2.3.1.13
Action BAdI Preparation
In this IMG activity, you can create a BAdI Implementation that is executed before an order
action is executed.
As described earlier, the Order Engine performs certain steps for each action. One of these
steps is to execute checks at the beginning of an action. If a BAdI implementation was
created for the executed action than the method PREPARE is executed.
The customer can implement their own checks by creating a new BAdI implementation.
The easiest way to create a BAdI implementation is directly in Customizing click Checks.
The names of the new BAdI implementation and Class name must be entered, and the
system will automatically create a new BAdI implementation and the corresponding class.
The BAdI filter values are also automatically added with the Action name as a filter value.
BAdI definition /DBM/BADI_OE_ACTION_PREPARE is part of the enhancement spot
/DBM/ORDER_ENGINE_IMPL and is called several times (before the event, action, and
from the user interface).
Filter parameter CHECK_STEP defines at which step(s) an implementation is called. At the
beginning of an Action the CHECK_STEP filter value has value 0.
The creation of the BAdI can be done also via BAdI builder.
Always check the DBM Order for Syntax Errors after the implementation and
activation of a BAdI.
If you create your own BAdI implementations, than you must consider the following:
Only the exception classes /DBM/CX_OE_ACTION_DENIED and
/DBM/CX_OE_INTERNAL_ERROR are available at this time.
Do not run database updates in this BAdI.
Example of Prepare BAdI implementation
2007 SAP AG

Version: 1.0
Page 35 of 60
SAP
Filter values are automatically added and can be modified manually in the BAdI builder:
CHECK_STEP = 0 AND (ACTION = Action Name 1 OR ACTION = Action Name 2)
The class was automatically created with the name entered:
In other words the Order Engine gets the BAdI implementations based on the filter values
and for each BAdI implementation executes the method, prepare.
2007 SAP AG

Version: 1.0
Page 36 of 60
SAP
2.3.1.14
Action BAdI Execution
In this IMG activity, you can create a BAdI Implementation that is executed during an order
action.
The BAdI execution represents the action itself. Depending upon the business process, an
Action could have one or more execution BAdI implementations assigned to it. The BAdI
Implementation Layer determines the sequence. Any new customer BAdI implementations
are executed after standard action BAdI implementations.
There are certain standard BAdI implementations, without filter, which are executed with
every action:
/DBM/ORD_AC_EXE_VMS_BEFORE
/DBM/ORD_AC_EXE_VMS_AFTER
You can implement your own coding by creating a new BAdI implementation. The easiest
way to create a BAdI implementation is directly in Customizing click Execution.
The creation of the BAdI can also be done via the BAdI bilder.
The BAdI definition /DBM/BADI_OE_ACTION_EXECUTE is part of the enhancement spot
/DBM/ORDER_ENGINE_IMPL and the action name is used as a filter value.
When creating your own BAdI implementations, you must consider the following:
2007 SAP AG

Version: 1.0
Page 37 of 60
SAP
Exception class /DBM/CX_OE_ACTION_ERROR indicates an error during action

processing. The processing of the event stops immediately, the message log is
displayed, and the control returns to the user. Use the following statements to
trigger the exception in an Action:
Data: lv_dummy.
message eNNN into lv_dummy.
io_order->bal_add_symessage( ).
raise exception /dbm/cx_oe_action_error.
Exception class /DBM/CX_OE_INTERNAL_ERROR usually leads to an abort of
order processing and should only be used if an unexpected program situation or
data inconsistencies occur.
Use the following statements to trigger the exception:
Data: lv_dummy.
message aNNN into lv_dummy.
raise exception /dbm/cx_oe_internal_error.
Only check for the SCLTD indicator.

Never change the SLCTD or SLCTD_EXT indicator.
If processing is successful, you should return value /DBM/CL_ORDER_ENGINE=>
C_ACTION_OK in the return parameter CV_SUCCESS. Otherwise, processing
continues with the next subobject (for example, item). In this case no status would
be set, no document flow would be updated, and so on.
An Action BAdI implementation MUST NOT have a COMMIT WORK or COMMIT
WORK AND WAIT statements inside. The commit is done at the action level based
on the Action customizing (see subchapter 2.3.1.4 Update in Action Customizing).
The events, having assigned actions which commits, MUST NOT be called
recursively, over Order Engine, inside other action BAdI implementation, unless the
ms_oe_control-no_commit flag is set. Not following this rule might result in
serious data inconsistencies.
Use the class /DBM/CL_ORD_AX_EMPTY_ACTION in case an action sets only a
status and has no particular implementation
Example of Execution BAdI implementation
2007 SAP AG

Version: 1.0
Page 38 of 60
SAP
Filter values are automatically added and can be modified manually in BAdI builder:
ACTION = Action Name 1 OR ACTION = Action Name 2
In other words, the Order Engine gets the BAdI implementations based on the filter values
and for each BAdI implementation, executes the method execution.
2007 SAP AG

Version: 1.0
Page 39 of 60
SAP
To support customers who have already implemented the actions over the Action function
modules, we have provided the class /DBM/CL_ORD_AX_ACFMOD. All new Action
classes which call the old DBM 5.00 function modules should inherit from this class and
call the method call_action_fm.
We recommend that you develop new actions directly in the method and not inside
function modules, which will be called via class /DBM/CL_ORD_AX_ACFMOD.
2.3.1.15
Action BAdI Finalize
In this IMG activity, you can create a BAdI Implementation that is executed after an order
action has been executed.
Again, the Order Engine performs certain steps for each action that is successfully
executed. One of these steps is to add additional information at the end of an action (set
status, write in document flow, and so on). If a finalize BAdI implementation was created for
the executed action, than the method FINALIZE is executed.
2007 SAP AG

Version: 1.0
Page 40 of 60
SAP
An action could have one or more finalize BAdI implementations assigned to it. The BAdI
Implementation Layer determines the sequence. Any new customer BAdI implementation
will be executed after standard action BAdI implementation.
There are certain standard BAdI implementations, without filter, which are executed with
every action:
/DBM/ORD_AC_FIN_STATUS
/DBM/ORD_AC_FIN_DOCUMENT_FLOW
The BAdI definition /DBM/BADI_OE_ACTION_FINALIZE is part of the enhancement spot
/DBM/ORDER_ENGINE_IMPL and the action name is used as a filter value.
You can implement your own checks by creating a new BAdI implementation. The easiest
way to create the BAdI implementation is directly in customizing click Post-Processing.
The creation of the BAdI can also be done via the BAdI builder.
The following is an example of Finalize BAdI implementation.
2007 SAP AG

Version: 1.0
Page 41 of 60
SAP
Filter values:
ACTION = Action Name 1 OR ACTION = Action Name 2 OR .
The finalize method will be executed if one of the illustrated actions above is triggered.
2007 SAP AG

Version: 1.0
Page 42 of 60
SAP
In other words, the Order Engine gets the BAdI implementations based on the filter values
and, for each BAdI implementation executes the method finalize.
If you create your own BAdI implementations, you must consider the following:
Only exception class /DBM/CX_OE_INTERNAL_ERROR is available at this time. It
usually leads to an abort of order processing and should only be used if an
unexpected program situation or data inconsistencies occur.
Use the following statements to trigger the exception:
data: lv_dummy.
message aNNN into lv_dummy.
raise exception /dbm/cx_oe_internal_error.
The BAdI is only processed if the action is executed successfully.
Never update any order data in this BAdI.
Status changes and document flow is updated (but not stored on the database).
The commit work may be performed afterwards.
Do not execute events in finalize implementations.
Under which circumstance should a new Action be created and when should a new
Action BAdIs implementation be added?
There is no rule for determining the best approach. Instead, we provide here in this
document, examples and simple cases as a guide for mapping a business process.
2007 SAP AG

Version: 1.0
Page 43 of 60
SAP
An action describes a self-contained business transaction. We therefore recommend

that you create an individual action that covers a step in the business process.
An action BAdI implementation performs a logical operation on the order data and is
not a singular entity describing a business process unit.
If a BAdI implementation can be described as a business process, then there must be
a 1:1 relation between the action and the BAdI implementations.
If several BAdI implementations, working in conjunction, describe the whole business
process, than create and assign all necessary Action BAdI implementations in the
correct sequence to an action.
If a system action does not cover the customers business process completely, than a
new Action BAdI implementation can be created and assigned to the System Action to
enhance the existing process.
2.3.2 Action Status Customizing

This section describes how to control the execution of an action based on Order status.
The following Order status types are possible:
Not Relevant
A
Not Edited
Partially Processed
Completely Processed
The Order Engine performs, among other steps, a status request. Based on the Order
status, the Order Engine checks whether or not the current Action can be executed.
In other words, each Action can influence the execution of other actions based on the
status type it sets on the Order. The status types defined in Customizing are preconditions
for the execution of an Action.
Status level: the level at which the status object is created.
Check level: is the level determined by the Order Engine. The status check is carried out
on the basis of the following check levels:
Selection level of the event
2007 SAP AG

Version: 1.0
Page 44 of 60
SAP
Execution level of the action

Status level of the prerequisite status
How can the customizing above be read, from Order Engines perspective?
The action BILLING_CREATE (Create an Invoice) is executed if the statuses:
BILLING_CREATE is (Not Edited OR Partially Processed)
AND CBOOK_WORK is (not relevant OR Completely Processed)
AND CONFIRM is (not relevant OR Completely Processed)
AND GDSMVT_CREATE is (not relevant OR Completely Processed)
AND ORD_SAVE is (Completely Processed)
AND RELEASE is (not relevant OR Completely Processed)
AND TIMEBOOK_CONFIRM is (not relevant OR Completely Processed).
In other words, the action BILLING_CREATE can be executed if certain steps, from a
business point of view, have already been executed. You must first execute the following
steps, for example, before you can create an invoice for a DBM Order:
An invoice was not already created
An invoice was created for a different split-job
Labor Items are booked
Parts Items are posted (Goods Issued)
The DBM Order is confirmed
The above steps are influenced by the execution of other Actions. This gives you full
flexibility to map business processes to Order Engine Actions and thereby control their
execution. For example, CBOOK_WORK action (confirm labor items) is executed if the
order was released; the RELEASE action is executed if the internal order was created;
and, so on.
2007 SAP AG

Version: 1.0
Page 45 of 60
SAP
The order can be

released if the internal
order was created and
the status for the action
itself is not edited OR
partially processed.
The user can confirm the labour

items if the order was confirmed
and the status fort he action itself
is not edited OR partially
processed.
Necessary steps for the first precondition CBOOK_WORK
This same algorithm applies to all preconditions.
2.4 Define Table of Criteria

In this IMG activity, it is possible to control the granularity level at which the Events and the
Actions are linked. For this purpose, you can generate new tables of criteria.
We strongly recommend that you do not change the shipped tables. If you were to
delete the tables, for example, the system events and actions will not work. Define
Custom criteria tables if you wish to customize table criteria.
To define the Order Engine table of criteria in Customizing, choose Logistics Execution
Order
Order Control
Define Table of Criteria.
If you select add/modify table of criteria in the structure, an overview screen appears.
All defined Criteria Tables are displayed.
2007 SAP AG

Version: 1.0
Page 46 of 60
SAP
Select the required key fields from the available fields

Save the settings
In the Header view, select a condition table and choose Goto -> Details or double-click
on a criteria table.
To generate a new criteria table, choose Generate.
Choose Table Maint. Generator and enter the required data, for generation of the
table maintenance dialog
In this example the criteria table Z_OE_EVAC_VEP will be analyzed. Based on this
customizing it is possible to control the Order Engine to map the Actions to an Event
according to certain criteria.
Fields used for selection of events.
2007 SAP AG

Version: 1.0
Page 47 of 60
SAP
2.5 Define Access Sequences

In this IMG activity, the Access Sequence for the criteria tables can be defined. The Access
Sequence is the sequence in which the criteria tables are accessed to determine the
actions for an event.
For this customizing, it is possible to control the sequence in which the Order Engine
searches for actions in the selected criteria tables. If no suitable entry is found in the first
criteria table, the Order Engine checks the next criteria table and, so on. A criteria table
that is not a part of the Access Sequence would never be accessed for any matching
entries for the criteria event.
To define the Order Engines access sequence in Customizing, choose Logistics Execution
Order
Order Control
Enhancements
Define Access Sequence.
The Access Sequence GDSM has assigned the following criteria tables:
2007 SAP AG

Version: 1.0
Page 48 of 60
SAP
When the Event GDSMVT_CREATE is triggered, the Order Engine reads only the criteria
tables assigned to the Access Sequence GDSM and determines the actions assigned to
the event; the other criteria tables are disregarded. If the One Table Flag is set the criteria
technique stops scanning further tables as soon as a matching entry is found in a table. In
other words, the criteria technique scans the tables mentioned in the access sequence until
a matching entry is found. As soon as the system finds a matching entry, it stops. If you do
not set this indicator, the system scans all the tables in the access sequence.
2.6 Define Action Control

In this IMG activity, you link the Events to Actions.
To control an action by linking to an event in Customizing, choose Logistics Execution
Order
Order Control
Define Action Control.
In the following, we describe how created events and actions are linked.
2007 SAP AG

Version: 1.0
Page 49 of 60
SAP
Suppose the business process needs to have different actions assigned to the same event,
the dependency being on Sales Document Category and Technical Item Category. In the
example below, the event is GDSMVT_CREATE and the assignment of the actions are
defined for the criteria table /DBM/OE_EVAC_VTI .
If possible all actions should be defined in the same table.

All determined actions of all criteria tables are used except in case the single tab flag is set.
You have the possibility to navigate between Events and Actions.
The graphic below depicts the navigation from the event GDSMVT_CREATE to all related
actions this is an easy way to see all actions assigned to an event, especially if the
actions are in different criteria tables.
2007 SAP AG

Version: 1.0
Page 50 of 60
SAP
In the following, we show the navigation from the action ORD_CLOSE to all related events
this is an easy way to see all events assigned to an action, especially if the events are in
different criteria tables.
2007 SAP AG

Version: 1.0
Page 51 of 60
SAP
2007 SAP AG

Version: 1.0
Page 52 of 60
SAP
2.7 Define Procedure for Order Status

In this IMG activity, it is possible to define Custom order status types and also to define
conditions that control status determination.
You can freely define and calculate the order status in the DBM order based on a
combination of order status types.
The following rules apply for the calculation of the order status:
The list of order status types is sorted in ascending order.
The specific order status is a candidate if its conditions are true with respect to the
order that has just been checked.
If all the conditions apply to the next order status in the list, this order status
becomes the new candidate.
If an order status does not contain any conditions, it automatically becomes the
candidate.
The specific condition is true if the action status in the DBM order is blank, larger
than or equal to the value in the condition.
If one of the conditions is false, the calculation stops and the next status is
checked.
If there is no candidate, the system sets the order status to blank.
Select and double

click
OR
Action status in order

not processed (A)
not processed (A)
partly processed (B)
2007 SAP AG
Action status in condition

A
B or C
C

Version: 1.0
True or False
True
False
False
Page 53 of 60
SAP
completely processed (C)
A, B or C
True
2.8 Assign Procedure for Order Status

In this IMG activity, you define the assignment of an existing schema/ procedure to a sales
organization and plant.
Before you proceed with this activity, you must customize the procedure for order status
(see Define Procedure for Order Status)
By assigning a procedure for order status you ensure that the order status of the DBM
order is calculated within the bounds of specific sales organizations and plants and
according to the specific schema/procedure.
Schema SAP was previously

defined (see Define Procedure for
Order Status chapter)
It is not possible to use different status schema, for example, for different order types, as all
orders are displayed in the order transaction and a selection would not be possible any
longer as the same status (e.g. 1000) could have completely different meanings.
2.9 Define Schema for Message Substitution

In this IMG activity, you can define a schema for message substitution.
If you do not want to use the system messages that are displayed when you execute
actions, you can replace them.
2007 SAP AG

Version: 1.0
Page 54 of 60
SAP
These are the rules for substitution entries:

The amount of parameters in messages must be equal
The message type cannot be substituted by a less important one. Allowed
substitutions are:
o 'A' with 'A'
o 'E' with 'A' or 'E'
o 'W' with 'A', 'E' or 'W'
o 'I', 'S' with any
You can set a flag to define the importance of the message:
0 Display / Important
1 Hide / Not important
Important messages always appear in the message dialog box after the action has been
completed.
Messages that are not important are not displayed when the dialog box appears. Instead,
these messages are saved to the action log. The All messages option in the dialog box
allows you to display all messages, including those less important. There is a similar option
in the action log history.
You can assign this schema to a specific order type under Define Order Type.
2007 SAP AG

Version: 1.0
Page 55 of 60
SAP
If you do not define any substitution rules, (there is no schema or, the message is not in the
schema), the system applies the following:
Message type 'A', 'E', 'W' - importance flag 0: Display / Important
Message type 'I', 'S' - importance flag 1: Hide / Not important
You can also define settings for the importance flag without message substitution.
2007 SAP AG

Version: 1.0
Page 56 of 60
SAP
2.10 VMS Integration

Define Table of Criteria for Order Control - VMS Action Determination
In this IMG activity, you define the fields that the system uses to determine the VMS action
for an order control action.
Define Access Sequence for VMS Action Determination
In this IMG activity, you can define the access sequence for determining a VMS action from
an order action.
Define VMS Action Control from Order Action
In this IMG activity, you can define the relationship between VMS actions and order control
actions.
The Order Engine action with fields from the /dbm/oe_vmac criteria tables determine three
additional fields: Check Action, Execute Action and a Flag for determining the time of the
VMS action execution (before or after the Order Engine action execution).
If no VMS action is determined for a Check Action than no check for whether a VMS action
is allowed would be performed.
The VMS Execute Action is intended to be executed by default after the execution of the
configured Order Engine action. If the flag for Execute before OE action is checked, then
the Execute Action is executed before the Order Engine action.
Some VMS actions require action specific data. The BAdI which makes these data
available is the /DBM/BADI_VEHICLE_ACTIONS. The BAdI has the method
2007 SAP AG

Version: 1.0
Page 57 of 60
SAP
EXECUTE_FURTHER_ACTIONS to control the contents of the DBM vehicle buffer, before

the vehicle action is carried out. You can change the contents of the following parameters:
IV_ACTION - Action
IO_ORDER - DBM Order
IS_VLCDIAVEHI - VELO: Dialog Structure for Vehicles
CS_VLCACTDATA_HEAD - VELO: Transfer Structure for Actions (Header Data)
CS_VLCACTDATA_ITEM - VELO: Transfer Structure for Actions (Item Data)
CT_VLCADDDATA - VELO: Vehicle Additional Data
2.11 DBM Versionizer

The DBM Versionizer is a tool designed to help consultants during implementation to take
snapshots of the customizing as a version. This helps keep track of the customizing
changes made during the project and enables easy comparison with the delivered
customizing. For more information, see SAP note 1039310.
In short, the DBM Versionizer is the Version Management for customizing tables in DBM.
The only difference is that the user needs to explicitly generate a Version as a snapshot.
The basis for using the Versionizer is the Usage. A usage could be defined as an
application entity that groups together all the customizing tables relevant for that
application. For example, the usage OE would refer to a group of all the tables normally
referred to as the Order Engine Customizing. A Version Generated for this usage would
take a snap shot of all the tables for this usage, and store this in an XML format. This data
can be re-read in the future. For more information on other Usages, see SAP note
1039310.
In Customizing, choose Logistics Execution
Dealer Business Management
Order
Order Control Tools
Order Engine Version Generator.
An Application Version (snapshot of the current customizing) is generated is taken
by executing the report /DBM/VT_VERSION_GENERATE. The only selection
criterion for the Version Generation is the usage for which the version generation is
required.
The Application Version generated is specific to the user, and is not accessible for
the other users.
In Customizing, choose Logistics Execution
Dealer Business Management
Order
Order Control Tools
Order Engine Version Analysis.
The Version Analyzer, henceforth referred to as the Versionizer, provides all the
features referred to earlier, and remains the point from where all the versions are
accessed and can be compared.
The Versionizer is mainly used for comparing two different Versions. These
Versions are referred to as the Reference Version and the Comparison Version.
2007 SAP AG

Version: 1.0
Page 58 of 60
SAP
All delta information is provided in the direction of Reference to Comparison

versions. That is, an entry in the Reference Version that is missing in the
Comparison Version, is shown as a deleted entry (red) in the reference version
display. Vice-Versa, an entry in the Comparison Version that is missing in the
Reference Version, is shown as a new entry (green) in the comparison version
display.
Below is a screenshot of the Version Analyzer.
2007 SAP AG

Version: 1.0
Page 59 of 60
SAP
Features available in the Versionizer

Display of a certain version - It is possible to access the various version types by
selecting the Version Type and the Version Number.
Comparison between two Versions As explained earlier, the Version Analyzer can
be used to compare two different versions.
Logs The Versionizer displays exception messages for all the differences between
the loaded versions. This can be accessed through the button Display Logs.
Sync-Navigation- To enable ease in comparing tables, a synchronized navigation is
provided that can be used for scrolling both the reference and the comparison
version together, both horizontally or Vertically.
Filter Among all the tables in the usage, it is possible to filter the display, with only
those tables that have different table contents. This can be done via the check-box
Filter On: Only tables with different contents
Customizing It is possible to find the navigation path to a certain customizing table,
via the button Find Customizing.
Quick Filter A Quick filter is provided, that can be used to control the display of the
table entries when comparing two versions. This can be used to control whether to
display Identical Entries or Changed Entries or New/Deleted Entries.
Activation Some usages allow activation of a certain version for a user. This is
enabled for the usage OE currently. Activation of a certain version would then
enable the user to use that Versions customizing while using the DBM Order. The
current customizing of the client would then be ignored. Activation of a Version is
done by selecting the Version as a reference Version and then clicking on the
Activate button. This can be used for instance to check if a certain symptom is
due to recent change in the customizing, by activating the customizing from a
previous version (taken before the customizing changes were made). A Version
once activated should be deactivated subsequently by the Deactivate button.
XML Display All the generated version snapshots are stored in an XML format. All
the version, therefore, are enabled to be displayed in an XML format. This can be
done by the checkbox Display as XML. From the XML display mode, it is possible
to download the table contents in an XML format, onto a local text file.
2007 SAP AG

Version: 1.0
Page 60 of 60

DBM Order Engine Cookbook

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DBM Order Engine Cookbook

Transféré par

Droits d'auteur :

Formats disponibles

Dealer Business

Icons in Body Text

Words or characters quoted from the screen. These include field

Emphasized words or phrases in body text, graphic titles, and table

Technical names of system objects. These include report names,

Keys on the keyboard, for example, F2 or ENTER.

Title: DBM Order Engine

PURPOSE OF THE DOCUMENT .........................................................................................5

CUSTOMIZING OF THE EVENTS AND ACTIONS..........................................................8

Title: DBM Order Engine

Title: DBM Order Engine

Title: DBM Order Engine

Title: DBM Order Engine

Title: DBM Order Engine

2 Customizing of the Events and Actions

Title: DBM Order Engine

Order Engine Version Generator

The description of customizing settings in this document differs in sequence than

2.2 Define Events

To configure settings for Order Engine Events, choose Logistics Execution

Title: DBM Order Engine

2.2.1 Event Customizing

2.2.1.3 Access Sequence

2.2.1.4 Selection Level

Title: DBM Order Engine

2.2.1.5 Selection Dialog Box

Title: DBM Order Engine

Possible entries, for the flag dialog box, are:

2. Execute Event for the

1. Select the item(s)

1 If No Selection Is Made the selection can be done in the DBM order

Title: DBM Order Engine

The user doesnt select the

The user selects the item

Title: DBM Order Engine

For the event GDSMVT_CREATE the Selection Level (Event Customizing) is

Independent of the Items selected in the

3 Never Display - Select All If No Selection Is Made The item

Title: DBM Order Engine

For the event GDSMVT_CREATE, the Selection Level (Event Customizing) is

The user doesnt select the item

The user selects the item(s)

4 Never Display - Select all Always Independent of selected Items

For the event GDSMVT_CREATE the Selection Level (Event Customizing) is

Title: DBM Order Engine

Independent of the selected Items in the

2.2.1.6 Delete Selection Flag

2.2.1.7 Event Mode Control

2.2.1.8 Event Automatic Save

Title: DBM Order Engine

2.2.1.9 Usage on Screen

Event ITEM_CHANGE is triggered by pressing enter after selecting an item.

1 Separate Button on the Interface the event has a corresponding

Title: DBM Order Engine

2 Displayed in the List of Events the event has a corresponding

Title: DBM Order Engine

3 Dynamic Button on the Interface a button for the Event is

Title: DBM Order Engine

The corresponding UI button

Event Exit Flag

2.2.1.11 System Event Flag

Title: DBM Order Engine

2.2.1.12 Tools on Event level

The event GDSMVT_CREATE has as subsequent event ORD_CLOSE and calls