Note: You can run the Work Management Interface only if the SAP-Work Management Interface license is active.
The Work Management Adapter facilitates integration with SAP’s planning and scheduling modules for Condition Assessment activities. The adapter allows you to manage scheduled work in SAP and Meridium.
If an SAP Maintenance Plan has a task List that has an Operations and Object Lists that meets the criteria defined in the /MIAPM/TASK_CNF table, when you run the Work Management Adapter in the Administration Center, task(s) record will be created in Meridium Enterprise APM. The corresponding task record will be created based on the task configuration done in SAP.
If you later modify that Maintenance Plan and then run the Work Management Adapter again, the corresponding task record will be updated automatically in Meridium Enterprise APM. Likewise, if you add an Order to the Maintenance Plan, the corresponding task record will also be updated automatically in Meridium Enterprise APM.
After executing the Work Management Adapter, it creates tasks in Meridium Enterprise APM using the following items in SAP:
• Operations
• Object list
For example, suppose you have a maintenance plan with two operations and two object lists. When you run the adapter, six tasks will be created and associated with the particular asset in Meridium Enterprise APM as show in the following image:
When transferring Work Management data from SAP into Meridium Enterprise APM, the Desired Interval field is populated with a null value. The Next Date field will populate with the next execution date of the task (Meridium) or operation (SAP) when transferred to Meridium Enterprise APM.
Note: Last Date and Next Date values are calculated in SAP, not in Meridium Enterprise APM.
The following chart includes the possibilities for the Last Date and Next Date fields upon transferring data from SAP into Meridium Enterprise APM task records:
Workflow Step | Step Narrative | Last Date Field | Next Date Field |
---|---|---|---|
Plan is created, but not scheduled, and the Work Management Job is run. | The tasks of a Plan are created in Meridium when the Work Management Job is run. | Null |
Null |
Plan is scheduled, but not called, and the Work Management Job is run. | The Plan is scheduled. The task created above should be updated in Meridium. | Null | If the Plan is On Hold, the field will contain the next execution date. Otherwise, the field is Null. |
Plan is called for the first time, and the Work Management Job is run. | The task previously created will be updated with information from the Work Order from SAP. | Null | Next execution date of task. Work Order started. |
Task is executed in Meridium. | An inspection event is linked to the task. The inspection Hours field is set, and the inspection is closed. A confirmation record is created. | Date is set to date of Confirmation. | Next execution date of task. Work Order started. |
The Work Management Adapter allows the SAP user to create Meridium Inspection or Calibration tasks from operations on the task list of single cycle maintenance plans and strategy plans. However, not all strategy plan types are supported. The following table lists what types are supported:
SAP Plan Type |
Supported by the Work Management Adapter |
---|---|
Single Cycle: Time-Based |
Supported |
Single Cycle: Performance-Based |
Supported |
Strategy Plan: Time-Based |
Supported |
Strategy Plan: Performance-Based |
Supported |
Multiple Counter Plan |
Not Supported |
If a task record was created from SAP data and you later modify the SAP data in a way that causes that task record to become obsolete, you can run the Work Management Job in SAP to resolve the differences.
When you run the adapter, the tasks are validated against the data in SAP. SAP will search for the task records with an Equipment or Functional Location, Maintenance Plan, Maintenance Plan Item, Task List, and Operation combination to check if the task is valid. If it finds one that is not valid:
The value in the Reason field will be pre-pended with the following:
<Date> - <User ID> - task was discontinued due to changes in SAP. Previous task ID was 'previous task ID.'
Where <Date> is the date on which the task ID was set to **DISCONTINUED** and <User ID> is the user name that is specified in the /MIAPM/PARAMS database table in SAP.
For example, suppose a Calibration task record was created from an Operation with the control key ZMI2. If you later change the control key and run the report, the Calibration task record will be discontinued.
Note: When a task ID in a task record has already been set to **DISCONTINUED**, if you run Work Management Adapter again and the task data is still not valid, the task record will be skipped. In other words, its Reason field will not contain more than one instance of the text **DISCONTINUED**.
Note: If you modify the SAP data so that it corresponds to the existing task record again, running the adapter will cause Meridium Enterprise APM to update the discontinued task record instead of creating a new task record. The value in the Reason field in the updated task record will be pre-pended with the following: <Date> - <User ID> - Changes in SAP have caused this task to become active again, where <Date> is the date on which the task record was updated and <User ID> is the user name that is specified in the /MIAPM/PARAMS database table in SAP.
When the scheduled item that Meridium Enterprise APM delivers for the purpose of creating SAP Orders is executed, the Meridium Enterprise APM system performs a calculation on the Next Date and Call Horizon values in all task records. The calculated result is passed into the query Get tasks for Work Order Generation. If the result meets the criteria defined for the query column ([Task].[Next Date] - [Task].[Call Horizon]), the task record meets the remaining criteria defined in the query, and the task does not already contain a value in the Work Order Number field, an Order will be created from the task record.
Using the baseline query, an SAP Order will be created if the task record meets all query criteria (e.g., the Maintenance Plan field does not contain a value) and the calculated result meets the following criteria:
Task Next Date - Task Call Horizon = A date between the Last Executed Date and the Next Execution Date of the scheduled item.
Suppose the scheduled item contains the following values:
Last Executed Date |
Next Execution Date |
---|---|
July 1, 2008 1:00:00 A.M. | July 2, 2008 1:00:00 A.M. |
Based on these values, an SAP Maintenance Order will be created automatically if the Next Date of the task record minus its Call Horizon is between July 1, 12:00:00 A.M. and July 2, 12:00:00 A.M.
Suppose a task record contains the following values:
Next Date |
Call Horizon |
---|---|
July 11, 2008 3:00:00 A.M. | 10 |
Using these task record values, if you subtract the Call Horizon, 10 days, from the Next Date, July 11, 2008 3:00:00 A.M., the result is July 1, 2008 3:00:00 A.M.
Because July 1, 2008 3:00:00 A.M. falls between the Last Executed Date of July 1, 2008 1:00:00 A.M. and July 2, 2008 1:00:00 A.M., the task record will be used to generate an Order (assuming that the task record meets the remaining query criteria).
In other words:
July 11, 2008 3:00:00 A.M. (Task Next Date) - 10 (Call Horizon) = July 1, 2008 3:00:00 A.M. (A date between the Last Executed Date and the Next Execution Date of the scheduled item)
Note: If the scheduled item is being executed for the first time, Meridium Enterprise APM assumes a Last Executed Date of 1/1/1900. Also, if the Call Horizon field does not contain a value, the value is treated as zero (0).
Copyright © 1993-2015 Meridium, Inc. All rights reserved.