Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Re: [MAXIMO List] Import user defined fields for METERDATA using MIF

From: ewald caspari (2012-02-15 18:36)

Hi,
did I understand right, that you added the fields to the interface tables? I don't know with max 7, but in max 6 you had to insert them into the 'normal' data table and then re create the interface tables.
Regards
Ewald
------------------------------------------
Shannon,
Thanks for the reply. Yes and Yes. I've added thefields to METERREADING and IFACEMETERDATA. Per your suggestion, I did check the inbound restrictions on both theMETERDATA object (in DBCONFIG) and the MXMETERDATA object structure and, inboth, those two fields were not restricted. Add/Modify Alias also did not turn up any clues; no conflictsthere. Following is a more descriptivesynopsis of the issue that I posed to IBM...

Problem description:
We're trying to import meter reading data using the MIFand an
interface table. Specifically, we're trying to import two user-defined
fiellds, DEPTID and FUELSITE (both ALN values) byspecifying them in
the interface table and have the values carry through tothe
destination METERREADING table. We're using the Enterprise Service
MXMETERInterface where the interface table is set toIFACEMETERDATA.
The object structure MXMETERDATA, used in the MXMETERInteface,is based
on the source object METERDATA. We have created the two user-defined
filelds in the IFACMETERDATA object (used for theintegration table),
the METERDATA integration object and the METERREADINGobject (the
destination object). The two fields have been included on the
MXMETERDATA object structure (using Select Action >Exclude/Include
Fields and selecting the two fields on the Non-PersistentFields tab).

When we add valid meter reading records to the interfacetable and
specify values in the two user-defined fields, the meterreadings get
imported successfully into METERREADING, however, thevalues for DEPTID
and FUELSITE are null.

Is there something special that I need to do to get thosefields to
carry through?


From: ahohnstein (2012-02-15 22:08)

Sorry, to clarify, the attributes were added to the objects and the interface table was created using the External Systems > Select Action > Create Interface Tables.
--- In MAXIMO@yahoogroups.com, "ewald caspari" <dienst@...> wrote:
>
> Hi,
> did I understand right, that you added the fields to the interface tables? I don't know with max 7, but in max 6 you had to insert them into the 'normal' data table and then re create the interface tables.
>
> Regards
> Ewald
>
> ------------------------------------------
>
> Shannon,
> Thanks for the reply. Yes and Yes. I've added thefields to METERREADING and IFACEMETERDATA. Per your suggestion, I did check the inbound restrictions on both theMETERDATA object (in DBCONFIG) and the MXMETERDATA object structure and, inboth, those two fields were not restricted. Add/Modify Alias also did not turn up any clues; no conflictsthere. Following is a more descriptivesynopsis of the issue that I posed to IBM...
>
> Problem description:
> We're trying to import meter reading data using the MIFand an
> interface table. Specifically, we're trying to import two user-defined
> fiellds, DEPTID and FUELSITE (both ALN values) byspecifying them in
> the interface table and have the values carry through tothe
> destination METERREADING table. We're using the Enterprise Service
> MXMETERInterface where the interface table is set toIFACEMETERDATA.
> The object structure MXMETERDATA, used in the MXMETERInteface,is based
> on the source object METERDATA. We have created the two user-defined
> filelds in the IFACMETERDATA object (used for theintegration table),
> the METERDATA integration object and the METERREADINGobject (the
> destination object). The two fields have been included on the
> MXMETERDATA object structure (using Select Action >Exclude/Include
> Fields and selecting the two fields on the Non-PersistentFields tab).
>
> When we add valid meter reading records to the interfacetable and
> specify values in the two user-defined fields, the meterreadings get
> imported successfully into METERREADING, however, thevalues for DEPTID
> and FUELSITE are null.
>
> Is there something special that I need to do to get thosefields to
> carry through?
>
>
>
>
>