Shared Top Border

Enterprise Resource
Planning Portal

 

Advertise | Founder BLOG

ERPGenie.COM ABAP Tips and Tricks Database

THE ultimate
ERP website

 

Forums | Vote for us |

Google    Other Search Options

Login

Login to view more content!!!





Lost Password?
No account yet? Register

Main Menu

Home
Search
What's New
Sample Code
Tips and Tricks
Utilities
Downloads
Site Map
Feedback

ABAP Resources

Publications
Latest Job Postings
Submit Resume
ABAP Books
ABAP Training
News
Events
Forums

Registered Access

Poll

What area of ABAP are you interested in?
 

Last 5 Contributions

5 Most Popular Contributions

Home arrow Tips and Tricks arrow Workflow arrow Org units in workflow steps?
Org units in workflow steps? PDF Print E-mail
User Rating: / 0
PoorBest 
Written by Anon.   
Thursday, 19 April 2007

Why should I not assign org units to steps in the workflow builder?

 

Using org objects such as positions or org units in the WF builder is not a good idea in most cases. Aside from number range mismatches when you transport, if your department splits or changes you need a transport for what should be a simple maintenance task.
There are a few ways around it. The simplest is to not assign any agents in the WF but to assign your recipients as possible agents of the task (which you can assign in each system, including PRD). If WF cannot determine actual (because you've left it blank), it will send the task to all possibles. Just be very careful not to declare them as general tasks because it will then go to ALL people in the system.
Alternatively create a simple responsibility rule with a dummy responsibility and use that in your WF. If you're feeling adventurous you could even design a 'meta-rule' with multiple responsibilities for different tasks/steps. This way you can maintain multiple steps' agents in one rule.

Related Items:
 
< Prev   Next >
[ Back ]

Google Search

WEB
ERPGenie.COM
EDIGenie.COM
WorkflowGenie.COM

Latest Downloads

file icon ABAP Tips - System Fields, Program Types, Screen Types, ...
(Tips and Tricks)
file icon Developing a BAPI and Calling it with JCo
(Whitepapers)
file icon Taking you through ALE
(Whitepapers)
file icon SAP Order Status tables and Doc Flow table
(Tips and Tricks)
file icon SAP Quick Viewer
(Tips and Tricks)

Popular Downloads

file icon E-Book - ABAP Programs (1471)
file icon ABAP Tips and Tricks (1169)
file icon ABAP FAQ (976)
file icon Using ALV Grid in Reports (730)
file icon ALV Report Template (659)

Statistics

Contribution Activity
Utilities: 38
Tips and Tricks: 332
Sample Code: 164
Total Contributions: 548

Member Activity
Members: 6125 since 2/1/2007!
New: 7 since yesterday!
Visitors: 985333

Newest Members

Welcome our newest members:

Google Ads

Shared Bottom Border

Contact Us | Polls | Add URL | Contribute | Privacy | Terms | Feedback

Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job
Financials Consultant | Consultant Review | Gallia Consulting | Supply Chain Project | SAP Financials Forum
GenieHoldings.COM, Inc. | Genie Press | WorkflowGenie | ESAGenie | ERPTopSites | ABAP Tips and Tricks | SAP Solutions Database
EDIGenie | Searching Survivor

©2001-2008 Genieholdings.COM, Inc. All rights reserved. ERPGenie.COM, EDIGenie.COM, WorkflowGenie.COM and ESAGenie.COM are Trademarks of Genieholdings.COM, Inc.

All product names are trademarks of their respective companies. GenieHoldings.COM, Inc. and it's websites are in no way affiliated with SAP AG.
 SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are registered trademarks of SAP AG in Germany and in several other countries.
 Every effort is made to ensure content integrity. Use information on this site at your own risk.