1

Create Job to update the Catalogue Codes (Notification Codes)

• There is no automatic update so this job should be run after configuration update to the Catalogue Codes and then in each system after code changes have been transported.
• Can be run periodically in background to ensure Catalogue Code data is ‘fresh’

Program: /SOLTIUS/PM_REFRESH_CATALOGUES

2

Create Job to remove ‘old’ deletion flagged records from the Application Sync Tables

• This job keeps the table’s sizes to a minimum by removing records that have been flagged for deletion over X days ago. The default is 90 days.
• The assumption is that all devices have been synchronised within the period specified.
• Should be scheduled to run periodically, e.g. monthly.

Program: /SOLTIUS/PM_CLEAN

3

Create Job to Add Master Data to the Application Sync Tables.

• Checks to see whether all objects as specified in the BlueWorx profiles are in the sync tables. Adds any that are found to be missing.
• Missing entries are usually due to changes in profiles as changes to the objects themselves are picked up by the object change events.
• Can only be run in background.
• This job can be schedule to run periodically (i.e. daily) but for customers with a large number of profiles, large PM datasets, or constraints SAP resources we recommend:
  1. Generating on change from within the BlueWorx Admin Profile Config area now delivered (in SP7), or;
  2. Schedule a specific profile update after making changes to run after hours, to both limit disruption for BlueWorx users and minimise impact on SAP system resources
• Does not remove items that are no longer in the BlueWorx profiles.

Program: /SOLTIUS/PM_PROFILE_ADD_MD

4

Create Job to Validate Master Data in the Application Sync Tables.

• Checks the validity of data in the Master Data tables, by regenerating entries and comparing against those already in the table.
• Can only be run in background.
• Schedule once a month.
• Flags data which is not in profiles for deletion.  This can be turned off in your variant (Parameter: Skip Master Data Validity Chk) to improve performance if you have split this batch job by profile.  If the parameter is set, consider running Job to Validate Master Data periodically.

Program: /SOLTIUS/PM_PROFILE_RF_MD

5

Create Job to Process Inspection Results

• This job processes inspection results. Depending on the questions it can: Update Equipment and FL master data; Update Equipment and FL Classification data; Create Measurement Documents for Equipment and FL
• Should be scheduled to run periodically, e.g. nightly or twice daily. The frequency may be more often if operational requirements dictate

Program: /SOLTIUS/PM_INSP_PROCESS

6

Create Job to Update Material Balances

• This job processes refreshes the balances for all Materials – configured by Plant/ SLOC and Material Type
• This program should be run at least daily to catch up on material movements not made through BlueWorx

Program: /SOLTIUS/PM_UPD_MATERIAL_BAL

7

Create Job to Process Material Issues

• This job processes material issues since last run
• Suggest setting up to run multiple times per day and potentially with only one of the jobs set to reprocess errors

Program: /SOLTIUS/PM_PROCESS_MATERIALS

Run with parameter p_errors = ‘X’ to automatically retry processing issues (for example locked Material or Orders)

8

Create Job to Check Sync Times

• This job checks for application syncs that started but have not completed, marking them with error status.
• Should be run hourly

Program: /SOLTIUS/PM_SLOW_SYNC

9

Create BlueWorx Queue Processing Job

You can via Admin settings (https://blueworx.freshdesk.com/a/solutions/articles/19000006709-maintain-core-settings-settings-tab > Sync Settings) optionally process master data change events in their entirety using a separately scheduled job. 

When on this removes the load from the SAP Event Queue which will just register an event for BlueWorx processing and not fully execute the evaluation and action.

After enabling the BlueWorx Admin setting schedule a job using the program below. You can use different schedules and variants to process some events at different times and according to your needs.

To get a list of the Events look at the Events FOLDER in the Class /SOLTIUS/PM_CHGOBJ.

Program: /SOLTIUS/PM_EVTQ_PROCESS

10

Create job to Process Master Data Validity

• Checks master data is in valid profiles.  If not, the master data record is flagged for deletion.
• All profiles are processed as for a master data record to be valid it must be valid in at least one profile.
• Optional parameter to skip profile generation.  This improves run time and is appropriate where you have other jobs which frequently update the profile data (likely).
• Run at most monthly.

Program: /SOLTIUS/PM_PROCESS_MD_VALIDIT

11

Create job to process Permit Updates (Support Pack 07+)

• This job updates SAP Permit information for Functional Locations, Equipment, and Work Orders.
• The frequency of the job depends on how often permit master data is updated.     Recommendation is to run nightly unless permit master data is very static.

Program: /SOLTIUS/PM_UPD_MD_PER

12

Create job to generate Order Inspections (Support Pack 07+)

• Only required when admin setting for background generation of order inspection is active.
• Should be run daily
• If this job cannot be run daily then use the parameter offset days so that all the inspections required before the next run are generated.  For example, if running the job weekly use a 7 day offset.
• Note that the admin parameter for days forward and back is used to time bound the inspections generated.  Each user profile is checked and the greater of the inspection admin parameter or the profile work order days forward and back is used as the generation horizon.

Program: /SOLTIUS/PM_INSP_ORDER_GEN

13

Create Refresh Feature Location and Rendering Job  (Support Pack 07 Update 06+)

As of Support Pack 7 Patch 06 a job can be configured to update the location and rendering of features based on the characteristic values of the equipment and functional locations they represent.

Only affects features belonging to layers with the switch ‘value based rendering’ or ‘update geometry from characteristic’ turned on

• Can only be run in background.
• Schedule once a month.
• Flags features that do not have valid location data  
• Note that if a BlueWorx licensed user is running this job they are required to have all feature permissions switched on in their user record in BlueWorx Administration. For a systems user running the job (for example WF-BATCH), they need to have the Auth Object ZBWXGEOUPD assigned to them.

Program: /SOLTIUS/EM_RF_FEATURES

Create Job to update permit master data

• There is no automatic update so this job should be run after configuration to update the permit master data in each system after code changes have been transported.
• Can be run periodically in background to ensure Permit data is ‘fresh’

Program: /SOLTIUS/PM_UPD_MD_PER

Create Geo Inheritance Refresh Job

• This job will generate and update the inheritance for features based on their install location. Flags any duplicate or no longer relevant inherited features as deleted. Change pointers on technical objects should handle most day to day updates.
• Only required when admin setting for inherit geo is active
• Should be scheduled to run once a month

• This job deletes transaction logs older than a specified number of days (default: 365 days)
• It is optional
• Transaction history is not retained in any other place, and running this job will permanently delete the BlueWorx transaction information
• It can be run directly or as a scheduled batch job

• This job deletes entries older than a specified number of days (default: 30 days).
• Recommended to run once a month.
• It can be run directly or as a scheduled batch job.

• This job deletes sync temporary data older than a specified number of hours, greater than or equal to 24 hours (default: 24 hours)
• Recommended to be run daily
• It can be run directly or as a scheduled batch job

• This job reads then re-saves Inspection Question header master data.
• The batch use will require Inspection Change and Authorisation Group authorisation if enabled.
• It can be run directly or as a scheduled batch job.
• Run monthly, reviewing the sp.
• Errors updating a Question are written to the job spool.

• It can be run directly or as a scheduled batch job.
• Run as often as meets your requirements. If SAP Standard Text is modified regularly then the batch job should be run either daily or weekly. 
• To display the SAP Standard Text data in BlueWorx, you will need to configure your Standard Text settings in BlueWorx Administration first. The SAP Standard Text switch must be switched on. Refer to Standard Text documentation here.

• It can be run directly or as a scheduled batch job.
• Should be run after an SAP time zone data change. 
• Schedule to run at least yearly. The default is to create time zone data for 20 years in the past and 20 years in the futures.

• It can be run directly or as a scheduled batch job.
• It should be run regularly, daily or weekly to preserve the performance of Master Data generation and update.
• The "Days Old" parameter should be set based on your longest running Master Data refresh job. For example if your longest running job is 4 hours then set to the minimum of 1 day.

Program: /SOLTIUS/PM_DEL_MD_RF_JOIN_DAT

• It can be run directly or as a scheduled batch job,
• It should be run regularly, daily or weekly to ensure timely running of events (in the rare case that an event remains locked),
• The parameters available allow the admin to remove all locks older a set amount of time.