),)LQDQFLDO$FFRXQWLQJ

:RUNIORZ6FHQDULRV

,
)

0
)

:
7

0
%
&
%

3
/
(
+

Release 4.0B

®
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*

&RS\ULJKW
© Copyright 1998 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within these materials. SAP AG shall not be liable for any special,
indirect, incidental, or consequential damages, including without limitation, lost revenues or lost
profits, which may result from the use of these materials. The information in this documentation is
subject to change without notice and does not represent a commitment on the part of SAP AG for
the future.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
OSF/Motif® is a registered trademark of Open Software Foundation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.
UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.
ADABAS® is a registered trademark of Software AG.
SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAP ArchiveLink®, SAPaccess®, SAPmail®,
SAPoffice®, SAP-EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB,
Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAP
AG.

,FRQV

,FRQ 0HDQLQJ
Caution

Example

Note

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV

&RQWHQWV

),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 
:RUNIORZ6FHQDULRVLQ)LQDQFH ),  
:RUNIORZ6FHQDULRVLQ$VVHW0DQDJHPHQW ),$$  
%XON&KDQJHVWR0DVWHU'DWD ),$$%XON&KDQJHVWR0DVWHU'DWD  
Technical Background (FI-AA Bulk Changes to Master Data) ................................................... 8
Preparation and Customizing (FI-AA Bulk Changes to Master Data) ........................................ 9
Operation and Connection to Application Functionality (FI-AA Bulk Changes to Master Data)13
0DVV5HWLUHPHQW ),$$0DVV5HWLUHPHQW  
Technical Background (FI-AA Mass Retirement) ..................................................................... 15
Preparation and Customizing (FI-AA Mass Retirement) .......................................................... 16
Operation and Connection to Application Functionality (FI-AA Mass Retirement) .................. 17
3URFHVVLQJ,QFRPSOHWH$VVHWV ),$$,QFRPSOHWH$VVHWV  
Technical Background (FI-AA Incomplete Assets)................................................................... 19
Preparation and Customizing (FI-AA Incomplete Assets)........................................................ 20
Operation and Connection to Application Functionality (FI-AA Incomplete Assets) ................ 21
7ULJJHULQJD:RUNIORZIURPD9DOLGDWLRQ ),6/  
7HFKQLFDO%DFNJURXQG ),6/  
Object Type VALIDATION (Validation in Special Purpose Ledger) ......................................... 24
Standard Task MsgDisplay (Display Validation Message)....................................................... 25
3UHSDUDWLRQDQG&XVWRPL]LQJ ),6/  
Performing Task-Specific Customizing .................................................................................... 27
Activating Event-Receiver Linkage ..................................................................................... 28

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*

),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
6HHDOVR
BC - Workflow Scenarios in Applications [Extern]

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
:RUNIORZ6FHQDULRVLQ)LQDQFH ),

:RUNIORZ6FHQDULRVLQ)LQDQFH ),
This section describes the workflow scenarios in Finance:

3DUNLQJ'RFXPHQWV>([WHUQ@

3D\PHQW5HOHDVH>([WHUQ@

)LQDQFLDO&DOHQGDU>([WHUQ@

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
:RUNIORZ6FHQDULRVLQ$VVHW0DQDJHPHQW ),$$

:RUNIORZ6FHQDULRVLQ$VVHW0DQDJHPHQW ),$$
%XON&KDQJHVWR0DVWHU'DWD ),$$%XON&KDQJHVWR0DVWHU'DWD >6HLWH@

0DVV5HWLUHPHQW ),$$0DVV5HWLUHPHQW >6HLWH@

3URFHVVLQJ,QFRPSOHWH$VVHWV ),$$,QFRPSOHWH$VVHWV >6HLWH@

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
%XON&KDQJHVWR0DVWHU'DWD ),$$%XON&KDQJHVWR0DVWHU'DWD

%XON&KDQJHVWR0DVWHU'DWD ),$$%XON&KDQJHVWR
0DVWHU'DWD

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
7HFKQLFDO%DFNJURXQG ),$$%XON&KDQJHVWR0DVWHU'DWD

7HFKQLFDO%DFNJURXQG ),$$%XON&KDQJHVWR0DVWHU
'DWD
First, you have to select the assets that you want to change. You make this selection using any
standard asset report. You then place the selected assets in a work list (function &UHDWHZRUNOLVW
in the list display of the report). Note that you can only select assets from a VLQJOH company
code. The function 8VHUVHOHFWLRQ in the report selection screen allows you to further limit the
selection. In addition to the standard reporting selection criteria, this function allows you to use
all the fields of the general data part of the master record as selection criteria.
You can also include individual assets in the worklist. You can add them to the worklist from the
asset master data transaction or the value display transaction under the menu option
(QYLURQPHQW.

The report for creating a worklist only shows assets that have APC amounts. In
order to select assets that have not been posted, you have to use the standard
report “unposted assets” (under “Day-to-day activities”).
You use substitutions in order to define the rules for determining under which circumstances
which master record fields receive what new contents (see FI-AA-System Administration Guide
[Extern]). When you create a work list, you can enter a substitution rule. When the work list is
processed, all the assets in the work list will be changed according to the defined substitution
rule. The system documents the changes, as it does manual changes, by creating change
documents.
The work list that is created opens a workflow. By means of the definition of the workflow, the
system determines which workers should carry out the following steps:
• manual checking and possible adding to the work list
• releasing the work list and posting the changes.
The system automatically sends the work list for processing to the specified employees. They
receive the work list in their R/3 Mailbox.

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$%XON&KDQJHVWR0DVWHU'DWD

3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$%XON&KDQJHVWR
0DVWHU'DWD
You can represent the organizational plan in the R/3 System by entering organizational units,
positions, and jobs. This organizational plan is used in the PD (Personnel Planning and
Development) System for employee management. The definition of the organizational plan also
plays a significant role in managing SAP Business Workflow. The system uses this
organizational plan to determine the employee who is responsible for a particular workflow task.
The workflow tasks are assigned to positions or to the organizational units they belong to. The
tasks
• bulk changes to master data
• posting mass retirement
• processing incomplete assets
are performed using SAP Workflow procedures. Therefore, you should define asset accounting
and its employees (system users) in the R/3 organizational plan. The tasks listed above are
defined as model Workflow tasks in the standard system. You do QRWhave to make any further
entries for the Workflow definitions. In order to carry out these tasks, you only need to assign the
standard tasks
• correct worklist and
• release worklist
to the organizational unit “Asset Accounting” (which you have defined) or to a position/job
belonging to it. For this purpose, there is also a corresponding activity in the Implementation
Guide for Asset Accounting (3UHSDUDWLRQVIRUSURGXFWLYHXVH → $XWKRUL]DWLRQV). The diagram
below shows an example of an organizational plan and the Workflow assignments:

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$%XON&KDQJHVWR0DVWHU'DWD

3' 2UJDQL]DWLRQDO 3ODQ

2UJDQL]DWLRQDO 8QLWV $FFRXQWLQJ

)LQDQFLDO &RVW
$FFRXQWLQJ $FFRXQWLQJ

 $VVHW
$FFRXQWLQJ

RU
3RVLWLRQ
$VVHW $FFRXQWLQJ
:RUNIORZ :RUN
/LVW

),$$
),$$ 6WDQGDUG
6WDQGDUG
WDVNV

%XON FKDQJHV
0DVV UHWLUHPHQW
2ZQHU 3(11<
,QFRPSO DVVHWV

'HILQLWLRQRIDQRUJDQL]DWLRQDOSODQ

A Workflow task can also be assigned directly to an R/3 user (see the FI-AA
Implementation Guide: “3UHSDUDWLRQVIRUSURGXFWLYHXVH”). In this way, you can
use the FI-AA Workflow scenarios ZLWKRXW having a defined PD organizational
plan.
Defining a substitution rule is also required for bulk changes, in addition to the organizational
assignments. For more information, see the FI-AA Implementation Guide under Master data.
The procedure for defining a substitution rule is defined there.
The diagram below shows the Customizing definition of a substitution rule. The cost center 8936
should replace the cost center 4711.

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$%XON&KDQJHVWR0DVWHU'DWD

6XEVWLWXWLRQ &267 
6WHS  &KDQJH FRVW FHQWHU  WR 
3UHUHTXLVLWH
$1/=! .267/  0RUH 

&RQWLQXH
6XEVWLWXWLRQV LI SUHUHTXLVLWH LV PHW
)LHOG &RQVWDQW YDOXH 6XE ([LW
&RVW FHQWHU 
(QWU\  RI 

'HILQLWLRQ RI SUHUHTXLVLWHV &RQVWDQW YDOXH RU XVHU H[LW

DFFRUGLQJ WR %RROHDQ UXOHV ZKHQ SUHFRQGLWLRQ LV PHW

6XEVWLWXWLRQUXOH

Please note that when you make a change to time-dependent data (such as the
assignment to a cost center), you always have to enter the time interval (valid
from/to date) in the substitution rule. When you enter a new “valid from” date in
the substitution, the system automatically opens a new time interval. You can
only change one time interval in each bulk change. It is QRW possible to change in
several time intervals in parallel.
Also note that when you make changes to the depreciation terms, you also have
to enter the depreciation area (AFABE) in the condition.

The following example shows a substitution rule for changing the cost center in
the asset master record. The cost center should be changed for all assets in the
asset class 1000 as of 1/1/1996 from “QKI” to “1”, if “QKI” is the valid cost center
after 12/31/1995:
&RQGLWLRQ:
<ANLA> $ANLKL = ’00001000’ and
<ANLZ> $KOSTL = ’QKI ’ and
<ANLZ> $BDATU > ’19951231’
6XEVWLWXWLRQ(when the condition is fulfilled)
Cost center: 1
Valid from: 1/1/1996

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$%XON&KDQJHVWR0DVWHU'DWD

Note that the “valid to” date (BDATU) in the condition has to be entered in the
form “year/month/day.”

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\ ),$$%XON&KDQJHVWR0DVWHU'DWD

2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\
),$$%XON&KDQJHVWR0DVWHU'DWD
This is the procedure for carrying out a bulk change:
1. Define a substitution rule for the bulk change (7RROV→%XONFKDQJHVUXOH
– Choose 1HZHQWULHV. Then enter the company code, a number and a description
for the substitution.
– Then choose *RWR→6XEVWLWXWLRQ. Choose 6XEVWLWXWLRQ→&UHDWH
– Define a substitution step ($GGHQWU\). In the resulting pop-up window, you have
to select the fields that should be changed in this step.
– Define the conditions for the substitution. Enter the values that you want the
fields to take over when the conditions are met. The system supports you in
creating substitution rules with the function )LHOGVIRUFRQGLWLRQNote the F1 help
for the syntax of the substitution conditions.
2. Select the assets that are to be changed. Either start any standard FI-AA report, or
use the function 7RROV→:RUNOLVW→*HQHUDWH. Start the report with the appropriate
limitations. Please note that you can only enter one company code when making
selections.
3. Select the function &UHDWHZRUNOLVW in the respective list display. Select the standard
task “Change asset (bulk change).”
4. In the next pop-up window, select the substitution rule that you want to use for the
bulk change.
5. Add the assets to the worklist ($GGWRZRUNOLVW). You can choose individual assets in
the master data transaction or in the value display transaction.
6. Process the worklist in your mail inbox (7RROV→:RUNOLVW→(GLW):
– Check the assets in the worklist that was created (3URFHVV). Delete any
individual asset lines from the worklist, if necessary.
– Release the worklist (5HOHDVH).
7. Check the results using the document change list ($VVHWV→&KDQJH 

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
0DVV5HWLUHPHQW ),$$0DVV5HWLUHPHQW

0DVV5HWLUHPHQW ),$$0DVV5HWLUHPHQW

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
7HFKQLFDO%DFNJURXQG ),$$0DVV5HWLUHPHQW

7HFKQLFDO%DFNJURXQG ),$$0DVV5HWLUHPHQW
The selection of the assets involved and the basic procedure for mass retirement is carried out
using the same functions as a bulk change to asset master data. You use a work list and R/3
workflow controls. For mass retirements, there are the standard workflow tasks “retirement with
revenue” and “retirement without revenue (scrapping).” When you create a worklist, you have to
make entries needed for posting the mass retirement (such as the posting date).
The diagram below shows the basic procedure for a mass retirement:

/LVW RI DVVHWV WR EH UHWLUHG (QWULHV IRU

VXFK DV DVVHW OLVW DVVHW GLUHFWRU\ PDVV UHWLUHPHQW

$VVHW
&UHDWH ZRUN OLVW 3RVWLQJ GDWH
'RFXPHQW GDWH

 7UDQVDFWLRQ W\SH


$VVHW
$VVHW YDOXH GDWH
 'LVW RI UHYHQXH
6KRUW WH[W: Retire plant 0001 SURS WR $3&
:
7DVN ASSET_SALE SURS WR 1%9

5HYHQXH

'HIDXOW ZRUNIORZ VSHFLILFDWLRQV IRU

8VHU V 6$3RIILFH
DVVHW UHWLUHPHQW
LQER[
5HWLUHPHQW ZR UHYHQXH ASSET_SCRAP 2SWLRQ WR UHOHDVH
RU SURFHVV WKH
5HWLUHPHQW ZLWK UHYHQXH ASSET_SALE ZRUN OLVW

0DVVUHWLUHPHQW
The system carries out the retirement posting as follows. It creates a CATT (Computer Aided
Test Tool) run for the posting transactions involved. This run is started with the parameters of
the work list, and processed in the background. The system finds any assets for which errors
occurred during their retirement. The system writes these assets to a new work list and sends
them to the mailbox of the appropriate user. This person carries out subsequent processing of
the work list in the foreground, and corrects any errors.

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$0DVV5HWLUHPHQW

3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$0DVV5HWLUHPHQW
The model Workflow tasks are already defined in the standard system for the scenario “mass
retirement.” Just as for bulk changes, you do QRWhave to make any further entries for the
Workflow definitions. However, you do have to assign the standard tasks
• correct worklist and
• release worklist
to the “Asset Accounting” organizational unit that you defined, or to a position/job belonging to it,
or to an R/3 user.

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\ ),$$0DVV5HWLUHPHQW

2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\
),$$0DVV5HWLUHPHQW
The procedure for mass retirement is essentially the same as the procedure for bulk changes
(see Operation and Connection to Application Functionality (FI-AA Bulk Changes to Master Data)
[Seite 13]). However, when you create a worklist, you do not create a substitution rule. Instead
you enter
• the required dates
• transaction type
• revenue, and type of revenue distribution (proportional to book value/APC)

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3URFHVVLQJ,QFRPSOHWH$VVHWV ),$$,QFRPSOHWH$VVHWV

3URFHVVLQJ,QFRPSOHWH$VVHWV ),$$,QFRPSOHWH
$VVHWV
,0,QYHVWLWLRQVPDQDJHPHQW>([WHUQ@

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
7HFKQLFDO%DFNJURXQG ),$$,QFRPSOHWH$VVHWV

7HFKQLFDO%DFNJURXQG ),$$,QFRPSOHWH$VVHWV
There is an internal data field in the asset master record for the degree of completeness. The
possible values for this field are:
• the asset is complete (all required fields are maintained)
• the asset is incomplete, but can be posted to (all posting information is complete)
• the asset is incomplete and cannot be posted to
The system sets the degree of completeness field. As soon as an incomplete asset is created,
the system automatically initiates the appropriate workflow.

If you do not want to use R/3 Workflow, you can get a list of incomplete assets
using the standard report “Day-to-day activity → Unposted assets” (Asset
Accounting menu: ,QIRV\VWHP). Choose the function 8VHUVHOHFWLRQV in the initial
screen of the report, and use the degree of completeness of the asset (under
maintenance information) as the selection criterion for the report.

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$,QFRPSOHWH$VVHWV

3UHSDUDWLRQDQG&XVWRPL]LQJ ),$$,QFRPSOHWH$VVHWV
The model Workflow tasks are already defined in the standard system for the scenario “process
incomplete assets.” Just as for bulk changes, you do QRWhave to make any further entries for
the Workflow definitions. However, you do have to assign the standard task &KDQJH$VVHW to the
“Asset Accounting” organizational unit that you defined, or to a position/job belonging to it, or to
an R/3 user. In addition, you must activate the event linkage for the task “process incomplete
assets.” You do this in the same Customizing transaction that you use to make the
organizational assignments (FI-AA Implementation Guide: 3UHSDUDWLRQVIRUSURGXFWLYHXVH→
$XWKRUL]DWLRQV).

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\ ),$$,QFRPSOHWH$VVHWV

2SHUDWLRQDQG&RQQHFWLRQWR$SSOLFDWLRQ)XQFWLRQDOLW\
),$$,QFRPSOHWH$VVHWV
The system creates the worklist automatically, as soon as an incomplete asset is created.
The responsible user has to enter the missing information in the assets. You can call up the
asset change transaction directly from the worklist in order to do this.

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
7ULJJHULQJD:RUNIORZIURPD9DOLGDWLRQ ),6/

7ULJJHULQJD:RUNIORZIURPD9DOLGDWLRQ ),6/
'HILQLWLRQ
Validations allow you to check values and combinations of values as they are being entered into
the SAP R/3 System. Many values that are entered into the SAP R/3 System are automatically
checked against standard validations. Since some types of validations cannot be standardized,
you can create your own validations without making any changes to the standard system.
Once a validation is created and activated, the values entered into the SAP R/3 System are
checked against a Boolean statement (SUHUHTXLVLWH). The prerequisite statement determines if
the values entered should be checked. If the prerequisite statement is false, then the values are
valid and the transaction continues. If the prerequisite statement is true, the values are checked
against an additional Boolean statement (FKHFN statement). If the check statement is true, the
values are valid and the transaction continues. If the check statement is false, the system
displays a user-defined message. The message type (error, warning, or information) determines
whether the transaction continues.

You create a validation to prevent a posting being made to the administration cost
center 100 for revenue account 400010.
• 3UHUHTXLVLWHVWDWHPHQW
The account is 400010.
If the prerequisite statement is true, the data is validated against the
check statement.
• &KHFNVWDWHPHQW
The cost center is not 100.
The check statement is false when the posting is made to cost center
100. The data is not posted and the system displays a user-defined
system message, informing you that you cannot post data to the
combination account 400010/cost center 100.

8VH
Provided that the appropriate settings have been made in the validation definition and in
Customizing, you can trigger a workflow from the validation to inform a user(s) when the
validation fails. A work item then appears in the user’s integrated inbox. The work item can be
processed directly from the inbox. When the item is processed, the validation system message is
displayed. The user(s) who receives the work item via the workflow is thus informed when the
validation fails and can take further action, if necessary.

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
7HFKQLFDO%DFNJURXQG ),6/

7HFKQLFDO%DFNJURXQG ),6/
2EMHFW7\SHV
The interface between the R/3 functionality and the workflow system is implemented using the
object technology. The following information is primarily of a technical nature. You require this
information if you are interested in implementation or if you want to make your own modifications.
Object Type VALIDATION (Validation in Special Purpose Ledger) [Seite 24]
6HHDOVR
Object Orientation in SAP Business Workflow [Extern]

6WDQGDUG7DVNV
As single-step tasks provided by SAP, the standard tasks represent business activities from an
organizational point of view.
The standard task used here can also be used in other workflow scenarios without any
modifications.
Standard Task MsgDisplay (Display Validation Message) [Seite 25]
6HHDOVR
Tasks [Extern]

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
2EMHFW7\SH9$/,'$7,21 9DOLGDWLRQLQ6SHFLDO3XUSRVH/HGJHU

2EMHFW7\SH9$/,'$7,21 9DOLGDWLRQLQ6SHFLDO3XUSRVH
/HGJHU
'HILQLWLRQ
Object used to send a mail message to a user when a validation fails, that is, when the
prerequisite statement is true and the check statement is false.

You are making fast entry postings via batch input in Financial Accounting (FI).
As the data is being entered, the system checks the values against user-defined
validation rules. If the validation fails during document entry, a system message is
not displayed since the data is being entered via batch input. In such a situation,
you can use a workflow to ensure that the message triggered from the validation
is displayed in the inbox of a specific user(s).

6WUXFWXUH
The following attributes, method, and event are defined as elements of the object type
9$/,'$7,21 in the object repository:
• $WWULEXWHV: the validation name and step number, and information on the validation
message (message ID, message number, and message type)
• 0HWKRG: 0HVVDJH'LVSOD\
• (YHQW: WULJJHUHG.
This event is created whenever any validation fails and the 7ULJJHUZRUNIORZ indicator
is set in the validation definition.

/RFDWLRQRIWKH2EMHFW7\SHLQWKH2EMHFW5HSRVLWRU\
)LQDQFLDO$FFRXQWLQJ → 6SHFLDO3XUSRVH/HGJHU → 9DOLGDWLRQ6XEVWLWXWLRQDQG5XOHV

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
6WDQGDUG7DVN0VJ'LVSOD\ 'LVSOD\9DOLGDWLRQ0HVVDJH

6WDQGDUG7DVN0VJ'LVSOD\ 'LVSOD\9DOLGDWLRQ0HVVDJH
'HILQLWLRQ
In this standard task, the system message triggered from the validation is displayed in the inbox
of a specific user(s).

6WUXFWXUH
6WDQGDUGWDVN: 
$EEUHYLDWLRQ: 0VJ'LVSOD\
1DPH: 'LVSOD\YDOLGDWLRQPHVVDJH

5HIHUHQFH2EMHFW0HWKRG$WWULEXWHV
2EMHFWW\SH: 9$/,'$7,21
0HWKRG: 0HVVDJH'LVSOD\
$WWULEXWHV: &RQILUPHQGRISURFHVVLQJ

$JHQW$VVLJQPHQW
At runtime, this standard task is addressed to the agents specified in Customizing. For more
information, see Performing Task-Specific Customizing [Seite 27].
There is no role definition for this standard task. If you want to use role definitions to display the
validation message in the inbox of different groups of persons, you have to create a workflow for
this standard task.

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
3UHSDUDWLRQDQG&XVWRPL]LQJ ),6/

3UHSDUDWLRQDQG&XVWRPL]LQJ ),6/
)HDWXUHV
$SSOLFDWLRQ6SHFLILF&XVWRPL]LQJ
If you want to trigger a workflow from any validation, you must set the 7ULJJHUZRUNIORZ indicator
in the validation definition. The workflow is started when the prerequisite statement is true and
the check statement is false. A mail message is then sent to the inbox of the recipient(s).
For more information, see the 0DLQWDLQ9DOLGDWLRQ activity in Customizing for 6SHFLDO3XUSRVH
/HGJHU by choosing 7RROV → 0DLQWDLQ9DOLGDWLRQ6XEVWLWXWLRQ5XOHV.

$VVLJQ$JHQWVDQG$FWLYDWH(YHQW/LQNDJH
In addition to the general workflow Customizing, which ensures that the workflow system
operates correctly, you also need to carry out specific customizing activities for the validation
workflow. You have to assign the standard task to its possible agents and activate the linkage
between the triggering event and the receiver of the event.
6HHDOVR
Performing Task-Specific Customizing [Seite 27]
Activating Event-Receiver Linkage [Seite 28]

 -XQH
 6$3$* ),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV
3HUIRUPLQJ7DVN6SHFLILF&XVWRPL]LQJ

3HUIRUPLQJ7DVN6SHFLILF&XVWRPL]LQJ
In Customizing for %XVLQHVV:RUNIORZ, you must assign the standard task  ('LVSOD\
YDOLGDWLRQPHVVDJH) to its possible agents. This assignment determines which users can display
the validation message from their inbox. The standard task cannot be processed if the
assignment has not been made.

3URFHGXUH
1. Execute the 3HUIRUPWDVNVSHFLILFFXVWRPL]LQJ activity in Customizing for %XVLQHVV
:RUNIORZ (%DVLV&RPSRQHQWV → %XVLQHVV(QJLQHHULQJ:RUNEHQFK → :RUNIORZ
0DQDJHPHQW).
2. Under )LQDQFLDO$FFRXQWLQJ → 6SHFLDO3XUSRVH/HGJHU → 9DOLGDWLRQ6XEVWLWXWLRQ
DQG5XOHV, expand the $VVLJQWDVNVWRDJHQW branch.
3. Assign the standard task  ('LVSOD\YDOLGDWLRQPHVVDJH) to the agents who
should process the validation message.

Alternatively, you can classify the standard task as a JHQHUDOWDVN. The agents of
a general task are DOOXVHUV in the system. The standard task can therefore be
processed by any user.

-XQH 
),)LQDQFLDO$FFRXQWLQJ:RUNIORZ6FHQDULRV 6$3$*
$FWLYDWLQJ(YHQW5HFHLYHU/LQNDJH

$FWLYDWLQJ(YHQW5HFHLYHU/LQNDJH
The event WULJJHUHG of the object type 9$/,'$7,21 is the triggering event of the standard task
 ('LVSOD\YDOLGDWLRQPHVVDJH) and is entered as such in the event linkage table in the
standard system.
In order for the standard task to be started, the linkage between the triggering event and the
standard task (as the receiver of the event) must be activated in Customizing for %XVLQHVV
:RUNIORZ.

3URFHGXUH
1. Execute the 3HUIRUPWDVNVSHFLILFFXVWRPL]LQJ activity in Customizing for %XVLQHVV
:RUNIORZ (%DVLV&RPSRQHQWV → %XVLQHVV(QJLQHHULQJ:RUNEHQFK → :RUNIORZ
0DQDJHPHQW).
2. Activate the event linkage for the standard task  ()LQDQFLDO$FFRXQWLQJ →
6SHFLDO3XUSRVH/HGJHU → 9DOLGDWLRQ6XEVWLWXWLRQDQG5XOHV → $FWLYDWHHYHQW
OLQNDJH).

 -XQH