TR Workflow

™

TR - Treasury: WorkflowScenarios

HE

LP

.BC

BM

TW

FM

TR

Re lease 4 .6B

TR - Treasury: Workflow Scenarios SAP AG

2 December 1999

Copyright

© Copyright 2000 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks ofMicrosoft 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.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks ofInformix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute ofTechnology, 545 Technology Square, Cambridge, MA 02139.

JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto,CA 94303 USA.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.comBusiness Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAPBusiness Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, ManagementCockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other products mentioned are trademarks or registeredtrademarks of their respective companies.

SAP AG TR - Treasury: Workflow Scenarios

December 1999 3

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Tip


4 December 1999

Contents

TR - Treasury: Workflow Scenarios ..................................................................5Workflow Scenarios in Treasury.................................................................................................. 6Datafeed (TR-TM) ........................................................................................................................... 7

Preparation and Customizing (TR-TM Datafeed)....................................................................... 8Financial Transaction Release (TR-TM) ...................................................................................... 9


TR - Treasury: Workflow Scenarios

December 1999 5

TR - Treasury: Workflow ScenariosSee also:BC - Workflow Scenarios in the Applications [Ext.]


Workflow Scenarios in Treasury

6 December 1999

Workflow Scenarios in TreasuryThe following workflows are available in Treasury Management:

• Datafeed workflow

Available as datafeed support.

• Release workflow (Financial transaction (TR-TM))

Available as release support.

• Business partner release workflow

Available as support for business partner release.

• Workflow for master data release in the loans area

See also:Datafeed (TR-TM) [Page 7]

Financial Transaction Release (TR-TM) [Page 9]

Business Partner Release [Ext.]

Release (Master Data in Loans) [Ext.]


Datafeed (TR-TM)

December 1999 7

Datafeed (TR-TM)PurposeYou can use the datafeed interface to incorporate current market data in your financialtransactions via an open interface.

The datafeed workflow helps you to recognize and eliminate any errors straight away that mighthave occurred during data transfer or Customizing.

When you transfer data in a batch (scheduling a job), the data cannot be checked immediately.This is why

• you may find incorrect data in the database or

• the link to the market data provider was defective and no data was received.

If an error occurs, this workflow is started and a mail is sent to the relevant processor.

Process flowIf an error occurs, a mail is sent to the various processing agents. They can display the errordirectly from their inbox and correct it.

Different processing agents are responsible for the two different types of errors that occur:

• the Treasury department is responsible for Customizing errors

• the System Administration is responsible for data transfer errors.


Preparation and Customizing (TR-TM Datafeed)

8 December 1999

Preparation and Customizing (TR-TM Datafeed)IntegrationWorkflow template WS20000083 is delivered with the system for the datafeed interface.

Activities1. Event linkage for 'PROTOCOL' event from object BUS1094

If an error occurs during market data transfer, the PROTOCOL event is started.

You must activate this event linkage in the workflow.

2. You must assign organizational objects (organizational units, jobs, positions) to tasks TS20000200 (display market data) and TS 20000205 (display technical errors).You can store these organizational objects in the HR Organizational Management or via theworkbench.When you create organizational objects, you have to assign jobs or positions to them, In turn,you can assign users to the positions.

Organizational unit X → position Y → user

or organizational unit X → job Y → position Z → user


Financial Transaction Release (TR-TM)

December 1999 9

Financial Transaction Release (TR-TM)PurposeA Treasury transaction usually undergoes a series of processing steps. A release can benecessary, for example, when a Treasury transaction has been entered fully and has to bechecked by a superior (entry release). It may also be necessary to release a transaction after ithas been settled, in other words, before it is posted (posting release). All release procedures areultimately authorization or control procedures with organizational attributes. The workflow hastherefore been conceived with the aim of supporting Treasury transaction releases.

The Treasury transaction release strategy is supported initially for the application componentsmoney market, foreign exchange, derivatives and securities.

Prerequisites• Define release procedures and release conditions in Customizing for basic functions by

choosing Define Release Procedure.

• Define an organizational model for the standard role.

Users must be found in the system to make the individual approvals. To do this, a standardrole has been incorporated into the workflow definition. It has, however, not yet been filled.To define approval levels for users, you create a responsibility in the standard task andassign it to a user or a position.

• Enter the organizational model for standard role 20000035 for missed deadlines.

• Activate the workflow definition. You have to activate the event linkage of workflow templateWS20000092 so that you can start the workflow.

To do this, see the section on BC Organizational Management in the SAP Library:

Standard Roles [Ext.]

• Defining Roles Using Function Modules [Ext.]

• Defining Roles Using Organizational Data [Ext.]

• Using Responsibilities to Define Roles [Ext.]

Process FlowThe TR transaction release mainly comprises the following components:

• Integration of organizational management in the SAP Business Workflow (organizationalplan, task distribution according to the person responsible/job descriptions, dynamic taskdistribution at runtime from the context of the workflow and the processed objects).

• Integration of release management in the SAP Business Workflow (process structure ofthe release, consideration of release strategies that can be customized in Treasury at theruntime of the workflow).

If you want to incorporate the settlement release supported by the workflow, you have to makethe related settings in Customizing.


Financial Transaction Release (TR-TM)

10 December 1999

You can choose between a one-step, two-step and three-step release strategy. The release canbe performed by one, two or three people. In other words, it supports the dual control principleinvolving two or three employees.

You can determine which procedure you want to choose in Customizing depending on thecompany code, the product type and the transaction type. This is why you create releaseprocedures and release conditions.

You have to define the processing agents in standard role AC20000034. You can maintain oneor several agents for each release step and for each release procedure.

If a release is rejected, the last processing agent is informed by the release point and thetransaction can be changed or reversed. You then have to release it again.

You also have the option of displaying a reporting overview showing you which release wasprocessed when and by whom for each Treasury transaction.

Overview graphic: Essential release features

3rd approvalor rejection

1st approval or rejection




Start of workflow release for Treasury transaction

Start of workflow release for Treasury transaction

1st approvalor rejection

1st approvalor rejection

End of workflow release for Treasury transactionEnd of workflow release for Treasury transaction

If rejected, the Treasury transaction can still bechanged or reversed

If rejected, the Treasury transaction can still bechanged or reversed

AG

A

A

G

G

G

G

G

A

A

A

Single-level approval Dual-level approval Three-level approval

2nd approvalor rejection

3rd approvalor rejection

2nd approval or rejection

2nd approval or rejection

TR Workflow

Documents

Transcript of TR Workflow