IV46068: CUSTOM MAPPED FIELDS ON ACTIVITY AND UDF OBJECTS FAIL TO EXPORT FROM MAXIMO TO P6

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Custom mapped fields on activity and UDF objects fail to export
    from Maximo to P6
    
    Envir: BS75, Oracle, Websphere 7.29, OS win2008
    
    Application: Work Order Tracking (PV)
    
    ---------------
    
    Overview
    
    Client is attempting to map other fields from the workorder
    across to Primavera.They use the Organization app functionality
    to map custom fields.
    
    This fails for unknown exception and development confirmed a
    bug.Development provided a workaround to client.
    
    ---------------
    Steps to Reproduce
    ---------------
    Setup Mappings
    
    1. Goto the Organzation (PV) application
    
    2. Action Menu >> Primavera custom mappings
    
    2. Configure Primavera custom map fields to the Activity object
    (UDF Type)
    
    Examples:
    
    DESCRIPTION MXFIELD  MXMBO  MXTYPE PVMAPID PVFIELD
    PVOBJECT PVTYPE  TRANSACTIONTYPE
    
    Locations LOCATION WORKORDER String 1 Location
    Activity UDF_Text EXPORT
    
    WOPriority WOPRIORITY WORKORDER Integer 2 WO Priority
    Activity UDF_Integer EXPORT
    
    PARENT  PARENT  WORKORDER String 3 Parent
    Workorder Activity UDF_Text EXPORT
    
    DownTime DOWNTIME WORKORDER String 5 Shutdown?
    Activity UDF_Text EXPORT
    
    WONUM  WONUM  WORKORDER String 4 Job Number
    Activity UDF_Text EXPORT
    
      WORKTYPE WORKORDER String 6 Work Type
    Activity UDF_Text EXPORT
    
    
    3. Configure the Organzation (PV) application, Site (tab)
    options to use these mappings for the site you are using.
    
    ---------------
    Export the workorder:
    
    4. Goto Work order Tracking (PV) application
    
    5. select a workorder record with a status of wsched
    
    6. On the Primavera (tab) and Export (subtab) export the
    workorder to Primavera
    
    7. Checkbox "Workorders export to activities checked
    
    8. Export the workorder
    
    Exception:
    
    BMXAA4214E - An unknown error has occurred.
    Please contact your system administrator....
    
    ---------------
    Escalated to development:
    ---------------
    
    Confirmed as an issue, please raise an APAR.
    
    A workaround is to convert the custom mappings to use the
    ACTIVITY CODES as the Primavera object.
    
    Instead of Activities and UDF. The end user result is pretty
    much the same and activity codes have also the description and
    can be used in the column view as well.
    
    Also, there's no need to export WONUM to Primavera, since the
    default export creates the WONUM as the Activity ID.
    
    
    ---------------
    Developers workaround:
    ---------------
    
    Add "Project Activity Codes" instead of the custom map fields.
    
    1. Don't configure the custom field mappings in the
    Organization (PV) application.
    
    2. On the Work order tracking (PV) application, (tab)
    Primavera, (Subtab) Export
    
    3. On the table window "Project Activity Codes" add entries for
    the fields.
    
    Examples:
    
    DESCRIPTION MXFIELD  MXMBO
    Locations LOCATION WORKORDER
    WOPriority WOPRIORITY WORKORDER
    PARENT  PARENT  WORKORDER
    DownTime DOWNTIME WORKORDER
    Work Type WORKTYPE WORKORDER
    
    These will be exported and can be used the same way.
    
    ---------------
    Client desc:
    
    We have recently gone live with Maximo 7.5 and have installed
    the Primavera adapter for P6 as part of our environment. The
    interface has been working ok up until now, we have been able
    to export and import work orders as projects to P6.
    
    I have recently added Primavera Custom Maps to map work order
    fields to user defined fields in P6. When testing this, none of
    the field mappings worked, the result was blank fields in P6.
    
    Now when I try to export a work order to P6 I get an
    error on exporting and errors in the log file as attached.
    

Local fix

  • Developers workaround:
    
    Add "Project Activity Codes" instead of the custom map fields.
    
    1. Don't configure the custom field mappings in the
    Organization (PV) application.
    
    2. On the Work order tracking (PV) application, (tab)
    Primavera, (Subtab) Export
    
    3. On the table window "Project Activity Codes" add entries for
    the fields.
    
    Examples:
    
    DESCRIPTION MXFIELD  MXMBO
    Locations LOCATION WORKORDER
    WOPriority WOPRIORITY WORKORDER
    PARENT  PARENT  WORKORDER
    DownTime DOWNTIME WORKORDER
    Work Type WORKTYPE WORKORDER
    
    These will be exported and can be used the same way.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Maximo Adapter for Primavera 7.5.0.0 and Oracle          *
    * Primavera Integration API 8.2                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CUSTOM MAPPED FIELDS ON ACTIVITY AND UDF OBJECTS FAIL TO     *
    * EXPORTFROM MAXIMO TO P6                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Read the Technote number 1646803                             *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV46068

  • Reported component name

    MAXIMO PRIMAVER

  • Reported component ID

    5724R4400

  • Reported release

    750

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-23

  • Closed date

    2013-08-13

  • Last modified date

    2013-08-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Maximo Adapter for Primavera
Primavera Integration

Software version:

750

Reference #:

IV46068

Modified date:

2013-08-13

Translate my page

Machine Translation

Content navigation