ObjWhereClause
Standard SQL WHERE statements are used for the Object WHERE Clause and can include up to 2048 characters when a batch assignment server task is started using the command-line interface. However, when you start a batch assignment server task from the Component Requests screen, you can only specify up to 100 characters. Also, when using wildcards in the object WHERE clause, make sure you use the correct wildcard specific to your database.
The Object WHERE Clause can be used to restrict which records are retrieved and processed in batch assignment. The following conditions apply:
Assignment Object = Account
Object Where Clause = where pr_postn_id in (select row_id from s_postn where name = 'Sales Rep')
The Object WHERE Clause assumes the base table is coming from the assignment object specified.
For example, if you start batch assignment specifying the assignment object as Account and the Object Where Clause is where row_id = '1-232'
, then batch assignment attempts to assign only the row_id = '1-232'
from the S_ORG_EXT table.
The following is an example of a batch assignment using the command-line interface:
start task for component AsgnBatch with AsgnObjName= "Account", AsgnMode="MatchAssign", ObjWhereClause="where name like 'B%'"
This command batch assigns accounts starting with B.
Optionally, you can use the command-line interface and the Object WHERE Clause to run only a select number of assignment rule groups. The following is an example of this:
start task for comp asgnbatch with asgnobjname="Account", objwhereclause="where name like 'B%'", asgnkey="12-4DR56"
In this example, 12-4DR56 is the row Id of an assignment rule group, and only those rules belonging to this group are evaluated when this parameter is passed in the request.
NOTE: When using the command-line interface, use double quotation marks for the ObjWhereClause parameter; otherwise, it is treated as a SRVRMGR command option that changes the case.