/AIN/CL_DEV_CONDITION_MODIFY - Update condition for rule determination
General Material Data General Material DataThis documentation is copyright by SAP AG.
Functionality
This activity updates the rule determination conditions. You use the activity to trigger subsequent rules based on the updated conditions.
The activity has one parameter: ACTION_TYPE_BY_MESSAGE:
The action type is determined by the document. If no document is selected, it is determined by the business process or the device group role.
Relationships
The activity placement should be last in the rule, after any other activities.
A condition table with appropriate key fields must exist. The rule processor uses this table to the determine the next rule to be processed.
You define condition tables in the Auto-ID Infrastructure IMG by choosing Conditions and Rules → Conditions and Message Types →Define Condit. Types, Applic. Log, & Monitoring for Msg. Type.
Example
The following example shows how to trigger different rules in a fixed reader scenario that depends onthe action type within the assigned document. In this situation an outbound delivery with action type LOAD can trigger the LOAD rule, whereas an inbound delivery with action type UNLOAD can trigger the UNLOAD rule.
Assume that rule R1only contains the activity DEVICE_CONDITION_MODIFY. (R1 is assigned in IMG Customizing activity Define Conditions for Fixed Device Messages.)
You assign a new action-type-dependent condition table to the fixed reader message type in the Auto-IDIMG using Define Condit. Types, Applic. Log, & Monitoring for Msg. Type. In this condition table, rule R2 is assigned to action type AT1 and rule R3 is assigned to action type AT2.
If a document containing AT1 is now assigned to the fixed reader device group, it triggers rule R2 (forexample, LOAD). If a document containing AT2 is assigned to the fixed reader device group, it triggers rule R3 (for example, UNLOAD).
Notes
Further information
General Data in Customer Master RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 2133 Date: 20120526 Time: 040433 triton ( 3496 ms )






