Siebel Assignment Manager Administration Guide > Running Assignment Manager >

About Running Assignment Manager in Reporting Mode

Reporting mode provides the assignment administrator the ability to perform trial assignments and what-if analysis. When running Assignment Manager in reporting mode, assignments are written into results tables, known as reporting tables, rather than into the actual database tables. This allows the administrator the opportunity to preview possible assignment before actual assignments are made.

You can run Assignment Manager in reporting mode either from the UI or using the Siebel Server Manager command-line interface, known as the srvrmgr program. In either mode, you initiate a reporting mode request using either the Assignment Server (AsgnSrvr) or the Batch Assignment (BatchAsgn) server component. You pass the Reporting Mode (RptMode) parameter, specifying one of the following values:

• Snapshot. Reporting is turned on. Assignment Manager performs assignment validations and writes resulting candidates to the reporting team tables.
• Delta. Reporting is turned on. Assignment Manager performs assignments, compares existing assignment team table and writes the results to the reporting team tables.

For example, the following command tells Assignment Manager to read from and write to only the reporting tables where the reporting team tables store a snapshot of the results:

start task for comp asgnsrvr with asgnobjname="Opportunity", objwhereclause="where name='James Opty'",rptmode = "Snapshot"

NOTE:  By default, reporting is turned off. That is, when the Regular Assignment server component parameter is set to False, no assignment takes place. However, irrespective of whether reporting is turned on or off, Assignment Manager can write evaluation results to actual assignment tables.

Using Siebel Tools, you specify key columns through properties on the assignment object. Assignment Manager reads these key columns to differentiate between candidates. Assignment Manager stamps these key values; that is, Assignment Manager sets the key value for each record, to keep track of what employees, positions, or organizations are added in a specific assignment execution.

Then, when submitting an assignment request, you can pass one of the following values for stamping:

• Person Key Value (PersonKeyVal) for employees and positions
• Organization Key Value (OrgKeyVal) for organizations

For example, the following command tells Assignment Manager to execute in reporting delta mode where it merges the team from this run to the current team in the regular tables, and then writes the results to the reporting table. However, it only executes the rule against the Account 1 account, updates or changes positions who have the key value 12-RG2, and stamps all new positions with the value 12-RG2.

start task for comp asgnsrvr with asgnobjname="Account", objwhereclause="where NAME like 'Account 1'",UseKeyVal="Key Value", PersonKeyVal="12-RG2", RptMode="Delta

The Key Column in the S_ACCNT_POSTN results table holds either the rule group ID or a key value to distinguish candidates. You use the UseKeyValue parameter to indicate whether Assignment Manager uses the key value to filter and stamp candidates and what the key value should be. The choices are:

• Rule Group. Assignment Manager automatically using the rule group from which a particular candidate passes and stamps that rule group ID on the key column you defined.
• Key Value. User supplies either a Person Key Value (for employees and positions), or an Organization Key Value (for organizations) along with the request, then Assignment Manager stamps that value.

For example, assume you run AsgnSrvr with rule group 1 (RG1), and the result is that Position 1 is added to Account1. Next, you run rule group 2 (RG2) and Position 2 is added to Account1. If you do not want a second AsgnSrvr run to touch or change anything from the first run, you run AsgnSrvr with the UseKeyValue server component parameter set to either Rule Group or Key Value.

• If UseKeyValue = Rule Group, Assignment Manager saves the rule group ID in the Key Column property in the Assignment Object Extension object. In addition, Assignment Manager does not delete any positions who's key column value does not match the rule group ID.
• If UseKeyValue = Key Value, you need to also pass along another parameter as well—either PersonKeyVal or OrgKeyVal.

  In this case, because you are working with account positions, Assignment Manager passes the PersonKeyVal parameter.

When you run AsgnSrvr again, you might run the following command:

start task for comp asgnsrvr with asgnobjname="Account", objwhereclause="where NAME like ' Account 1'",UseKeyVal="Key Value", PersonKeyVal="12-RG2", RptMode="Delta"

Later on, if you make changes to RG2 and want to run another assignment request, you can use the same command. Only the positions on the account team with a key value of 12-RG2 change.

For more information on using the command-line interface, see Siebel System Administration Guide.

Related Topic

Configuring Assignment Manager to Use Reporting Tables and Columns