Bookshelf Home | Contents | Index | Search | PDF

Siebel Assignment Manager Administration Guide > Running Assignment Manager > Running Assignment Manager in Batch Mode >

Running Multiple Instances of Assignment Manager in Batch Mode

---

When there are many objects that need to be assigned, you can run multiple instances of Assignment Manager in batch mode to improve performance. First, develop a strategy for specifying multiple batches using the Object Where Clause parameter in the Batch Assignment component. Then, start multiple instances of Batch Assignment specifying the appropriate Object Where Clause for each instance.

For example, you can run one instance of Batch Assignment for accounts that changed today and a different instance of Batch Assignment for accounts that changed yesterday. Use the Object Where Clause parameter to specify the following:

For the batch that processes accounts changed today:

Object Where Clause: WHERE LAST_UPD = SYSDATE

For the batch that processes accounts changed yesterday:

Object Where Clause: WHERE LAST_UPD = SYSDATE - 1

To process mutually exclusive sets of records when running multiple instances of Assignment Manager simultaneously for the same assignment object, you should specify an Object Where Clause for each assignment task. For more information about the Object Where Clause parameter, see ObjWhereClause.

There are several instances where you should not run multiple simultaneous batch jobs:

If multiple Assignment batches are executed for the same object, then the results can potentially vary and may not be as desired
If the batch jobs update rows on the same table or tables
If one batch job updates records in a table or tables used by another batch job as input
If the batch jobs use workload criteria to assign the same object

NOTE:  If multiple assignment batches are executed for the same object using workload criteria, the results can potentially vary and may not be as desired.

Examples of when you should not run multiple simultaneous batch jobs include:

Contact and Contact Denormalization because the same tables are updated
Account and Contact Denormalization because Contact Denormalization uses Account team as input
Opportunity and Contact Denormalization because Contact Denormalization uses Opportunity team as input

NOTE:  The ASGN_PROC_ID column in the S_ORG_EXT table is no longer used. If you have updated this column to run multiple batches of Batch Assignment in previous versions, note that as of version 6.0 you can no longer do so.

Bookshelf Home | Contents | Index | Search | PDF