Results 1 to 1 of 1

Thread: Enhancements for copying Work Orders and related data objects

  1. #1
    Admin_attu is offline Admin
    Join Date
    Aug 2006
    Posts
    231
    Rep Power
    10

    Enhancements for copying Work Orders and related data objects

    If your organization creates Work Orders (Maintenance Orders), then some or perhaps all of the changes documented in this forum posting may be relevant.
    The Gold Client standard configuration has contained two data types named PM - WORK ORDERS and PP - MAINTENANCE ORDERS for quite some time. These two data types share the primary object - Work Order - and they have a few other similarities as well, but they also have some uniqueness about them. Ideally, these two data types should collect the data in relation to both data types (no uniqueness basically) and so now our standard has been enhanced in what is basically a merging of these data types. Some additional enhancements were included during this time as well. If you are interested in updating your Gold Client configuration, please follow the changes documented below.
    Note: the number of config changes here are quite numerous. If you have questions or require support, please submit a support ticket.

    Section 1: Add new tables to QM - QUALITY NOTIFICATIONS
    1.1: Add table relations IHPA-QMEL, JCDS-QMEL, QNOTIF_HEADER_DS-QMEL, and QNOTIF_TASK_DS-QMEL using the details in the screen captures below; be sure to include the common fields for each table relation

    Name:  Capture.PNG
Views: 314
Size:  99.6 KB
    Name:  Capture1.PNG
Views: 58
Size:  33.9 KB

    Section 2: Repair and add new data type links to QM - QUALITY NOTIFICATIONS
    2.1: Correct the linkage details for CA - OBJECT STATUS from using Recipient Table JEST and to use JSTO instead

    Name:  Capture2.PNG
Views: 58
Size:  73.1 KB

    Section 3: Create five new data types using the details displayed in the screen captures below; be sure to include the common fields for each table relation
    3.1: PM - MAINTENANCE ORDER HEADER

    Name:  Capture3.PNG
Views: 63
Size:  91.1 KB

    3.3: PM - NOTIFICATIONS

    This data type can be created simply by selecting data type QM - QUALITY NOTIFICATIONS and using the 'Copy' function located on the Data Echo framework toolbar; the result should be what is displayed in the screen capture below

    Name:  Capture4.PNG
Views: 59
Size:  39.2 KB

    3.4: QM - REFERENCE NOTIFICATIONS

    This data type can be created simply by selecting data type QM - QUALITY NOTIFICATIONS and using the 'Copy' function located on the Data Echo framework toolbar; the result should be what is displayed in the screen capture below

    Name:  Capture5.PNG
Views: 93
Size:  67.8 KB

    Section 4: Add a total of sixteen new data type links

    4.1: PM - WORK ORDERS - create links to the data types below; note that several of these linkages contain an asterisk which indicates that the use of concatenation is necessary

    4.1.1: CA - CHANGE DOCUMENTS

    Name:  Capture6.PNG
Views: 55
Size:  96.7 KB
    Name:  Capture7.PNG
Views: 58
Size:  93.1 KB
    Name:  Capture8.PNG
Views: 58
Size:  78.8 KB
    Name:  Capture9.PNG
Views: 61
Size:  116.4 KB

    4.2.4: PM - NOTIFICATIONS

    Note: this link is set as inactive in our standard because there is an active link already from PM - WORK ORDERS to PM - NOTIFICATIONS and having it be active here would likely lead to copying this data redundantly

    Name:  Capture10.PNG
Views: 62
Size:  119.0 KB
    Name:  Capture11.PNG
Views: 56
Size:  83.7 KB
    Name:  Capture12.PNG
Views: 56
Size:  40.5 KB

    4.5: QM - QUALITY NOTIFICATIONS

    4.5.1: QM - REFERENCE NOTIFICATIONS

    You can also create this same link from PM - NOTIFICATIONS to QM - REFERENCE NOTIFICATIONS if desired

    Name:  Capture13.PNG
Views: 58
Size:  31.0 KB

    Section 5: Add new tables to existing data type PM - WORK ORDERS

    5.1: Add table relations AFKO_KAL-AFKO, JCDS-AUFK and PMCOQT-AUFK using the details in the screen captures below; be sure to include the common fields for each table relation

    Name:  Capture14.PNG
Views: 62
Size:  92.7 KB

    Section 6: Misc changes that may need to be deployed

    6.1: PM - WORK ORDERS

    6.1.1: Delete the data type link to CA - OBJECT STATUS

    This link should not be needed since Status tables JEST and JSTO should already be included within this data type. This change simply removes an unnecessary redundancy. See the screen captures below where the first one shows these tables related from table AUFK; if your config contains these same relations then you can safely delete the link to CA - OBJECT STATUS.

    Name:  Capture15.PNG
Views: 56
Size:  60.6 KB

    6.1.2: Delete the data type link to LINK - WORK ORDER TO MAINT PLAN

    This link is no longer needed as it has been replaced by the data type link PM - MAINTENANCE ORDER HEADER to PM - MAINTENANCE PLANS

    Name:  Capture16.PNG
Views: 56
Size:  40.0 KB

    6.2: PM - NOTIFICATIONS

    6.2.1: Delete the link to MM - PURCHASING DOCUMENTS

    6.2.2: Delete the link to PP - PRODUCTION ORDERS

    Name:  Capture17.PNG
Views: 53
Size:  34.5 KB

    6.3: PP - MAINTENANCE ORDERS; this data type can now safely be deleted once all of the config changes above have been deployed successfully.

    Note: it is not necessary to delete this data type; doing so simply leaves your configuration in a more pristine state but if you prefer to take a conservative approach, leave it be
    Last edited by Admin_attu; 11-07-2017 at 07:19 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •