- P21 - Third Party App
- P21 - Data
- P21 - EDI
- P21 - Project
- P21 - Process Issues
- P21 - Dynachange
- P21 - Forms
- P21 - Performance
- P21 - Report/Portal
- P21 - General
- Unassigned
SISM Scheduled Task Creation
The following is the process of creating the SISM scheduled job task in P21. The key to making this work properly is to properly setup two steps. The first is the Schedule Import Service setup. All tasks which are turned on will get started by the SISM task. This SISM task is the second step. Once this task is defined and made active, all active jobs will get executed according to the time interval define in the SISM setup. The key is to have both steps setup AND active to make it work. If one, or the other step is not active, the jobs will not run.
A few checks and balances need to be done before the task is created.
First, always verify the database name, and the folders, which are setup.
Verify they are pointing to the test folders:
Determine if there are any active jobs:
select *
from scheduled_import_master
where active = 'Y'
There should be none. This example is using the P21USPlayPP database. You should view other Play database, to make sure there are no other SISM tasks running. Failure to turn off a running SISM, then starting up another, will cause a conflict, resulting in two jobs picking up files. This will result in partial or corrupted imports.
Then view all of the jobs that are inactive.
select *
from scheduled_import_master
Be aware of the EDI jobs. As long as they are not made active, nothing to be concerned about.
Next, you should setup only what you need. Go to the Schedule Import Service Setup:
For RMA's select the following options:
Ensure everything show folders point to test, then click on the "Active" option, then "Save".
Run the query again. There should be one task enabled.
select *
from scheduled_import_master
where active = 'Y'
Next, create the SISM Job. Have it run every 15 seconds:
Files | ||
---|---|---|
DataImage54.png 94.9 KB |
||
DataImage65.png 86.7 KB |
||
DataImage68.png 130 KB |
||
DataImage99.png 124.6 KB |