Preactions and Actions
The purpose of Preactions and Actions is to:
- Preactions: Keep track of changes made to data in LS Central
- Actions: Keep track of how the changes should be distributed
Subjobs added to a scheduler job can be created with the By Action method with Action Table ID as the Preactions or Actions table.
If the Preactions table (99001612) is set in Action Table ID, all (modified) data in the table in the subjob is replicated. The locations the data is going to be replicated depends on different settings as the locations defined in the Include/Exclude list or to stores in a store group defined in the receiver group in the scheduler job card.
This is because the Preaction table contains information of modified records but does not contain the distribution information.
If the Actions table (99001509) is set in Action Table ID, in the subjob cards, that allows you define which records in the same table should be replicated to each location / store.
Note: When creating a new scheduler subjob using the method By Action, the Action Table ID is filled by default with the Preaction or Action table ID, depending on the value in Replicate using Preaction in Scheduler Setup. It is created with the Action Table ID as Preaction if the field is check marked, otherwise is set as Action. The Action Table ID can be changed manually in the subjob card.
See also
Where To: Defining Data Distribution Targets