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.
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
Can you not change the value to null with a rule on the enterprise service?
On Tuesday, December 3, 2013, wrote:
>
>
>
> Does anybody know how to exclude PO.REVISIONNUM from Object Structure
> MXPO? Attribute is a required field. Even after setting it not to be
> required through database configuration utility it persist as read-only
> field and cannot be excluded. IBM stated that this might be due to value in
> primarykeycolseq. Still waiting for update from their developer.
> This attribute was added after upgrading to 7.5 and now my inbound
> integration is broke since it now requires that field.
> Option to modify incoming source file is not an option since the original
> developer no longer works with the company.
> Recreation of source file can be done but will require months to develop.
> We are manually working on manual data transformation until fix.
> I appreciate any assistance.
>
> Environment
> Application Server: WebSphere 7
> Database: MS SQL 2008 R2
> Maximo: Maximo 7.5.0.5
>
>
>
> Regards,
>
> Dennis Belandres
> Maximo Administrator
> DENSO MANUFACTURING TN, INC.
> TEL: (865) 982-7000 Ext. 6320
>
>
>
>
>
>
>
> ------------------------------
>
>
> The information contained in and transmitted with this Email may be
> privileged, proprietary, confidential and protected from disclosure. No
> privilege is hereby intended to be waived. This Email is intended only for
> the person to whom it is addressed. If you are not the intended
> recipient/addressee, any use of the Email and/or its contents, including,
> but not limited to, dissemination, distribution or copying is strictly
> prohibited and may be unlawful, and you must not take any action in
> reliance on it. If you receive this Email in error, please immediately
> notify the sender and delete the original message and any copies of it from
> your computer system. We deny any liability for damages resulting from the
> use of this Email by the unintended recipient, including the recipient in
> error.
>
>
>
Hello,
You can develop an user exit JAVA class to intercept the incoming message (and add requirement elements e.g. revisionnumber with some default value) before it is handed over to MBO for processing. This does not involve changing any existing code. This user exit class needs to be registered to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com" <dennis_belandres@denso-diam.com> wrote:
Does anybody know how to exclude PO.REVISIONNUM
from Object Structure MXPO? Attribute is a required field. Even after setting
it not to be required through database configuration utility it persist
as read-only field and cannot be excluded. IBM stated that this might be
due to value in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading
to 7.5 and now my inbound integration is broke since it now requires that
field.
Option to modify incoming source file
is not an option since the original developer no longer works with the
company.
Recreation of source file can be done
but will require months to develop. We are manually working on manual data
transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
________________________________
The information contained in and transmitted with this Email may be privileged,
proprietary, confidential and protected from disclosure. No privilege is
hereby intended to be waived. This Email is intended only for the person
to whom it is addressed. If you are not the intended recipient/addressee,
any use of the Email and/or its contents, including, but not limited to,
dissemination, distribution or copying is strictly prohibited and may be
unlawful, and you must not take any action in reliance on it. If you receive
this Email in error, please immediately notify the sender and delete the
original message and any copies of it from your computer system. We deny
any liability for damages resulting from the use of this Email by the unintended
recipient, including the recipient in error.
Hello,
You can develop an user exit JAVA class to intercept the incoming message (and add requirement elements e.g. revisionnumber with some default value) before it is handed over to MBO for processing. This does not involve changing any existing code. This user exit class needs to be registered to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com" <dennis_belandres@denso-diam.com> wrote:
Does anybody know how to exclude PO.REVISIONNUM
from Object Structure MXPO? Attribute is a required field. Even after setting
it not to be required through database configuration utility it persist
as read-only field and cannot be excluded. IBM stated that this might be
due to value in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading
to 7.5 and now my inbound integration is broke since it now requires that
field.
Option to modify incoming source file
is not an option since the original developer no longer works with the
company.
Recreation of source file can be done
but will require months to develop. We are manually working on manual data
transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
________________________________
The information contained in and transmitted with this Email may be privileged,
proprietary, confidential and protected from disclosure. No privilege is
hereby intended to be waived. This Email is intended only for the person
to whom it is addressed. If you are not the intended recipient/addressee,
any use of the Email and/or its contents, including, but not limited to,
dissemination, distribution or copying is strictly prohibited and may be
unlawful, and you must not take any action in reliance on it. If you receive
this Email in error, please immediately notify the sender and delete the
original message and any copies of it from your computer system. We deny
any liability for damages resulting from the use of this Email by the unintended
recipient, including the recipient in error.
Chris,
I have attempted this route but integration still error out since field is
not included in the incoming file.
Regards,
Dennis Belandres
Chris Lawless <lawlessc@gmail.com>
Sent by: MAXIMO@yahoogroups.com
12/03/2013 07:50 PM
Please respond to
MAXIMO@yahoogroups.com
To
"MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
cc
Subject
Re: [MAXIMO List] Inbound integration issue
Can you not change the value to null with a rule on the enterprise
service?
On Tuesday, December 3, 2013, wrote:
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
Pankaj,
IBM mentioned this as one of the potential solution. But to be honest with
you, I have no idea where to start on how to do this. If you can guide me
through this process that would be great.
The other thing that was mentioned was to use xsl to modify xml... have no
clue on how to this either.
Regards,
Dennis Belandres
Pankaj Bhide <pankajbhide@yahoo.com>
Sent by: MAXIMO@yahoogroups.com
12/03/2013 06:53 PM
Please respond to
MAXIMO@yahoogroups.com
To
"MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
cc
Subject
Fw: [MAXIMO List] Inbound integration issue
Hello,
You can develop an user exit JAVA class to intercept the incoming message
(and add requirement elements e.g. revisionnumber with some default value)
before it is handed over to MBO for processing. This does not involve
changing any existing code. This user exit class needs to be registered
to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com"
<dennis_belandres@denso-diam.com> wrote:
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
Try using xslt
http://www-01.ibm.com/support/docview.wss?uid=swg21637035
the real problem is creating the script which always looks like gibberish to me , however there are some tools out there that create the code in the background
http://www.altova.com/download-trial.html#
try mapforce
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of dennis_belandres@denso-diam.com
Sent: 04 December 2013 13:13
To: MAXIMO@yahoogroups.com
Subject: Re: Fw: [MAXIMO List] Inbound integration issue
Pankaj,
IBM mentioned this as one of the potential solution. But to be honest with
you, I have no idea where to start on how to do this. If you can guide me
through this process that would be great.
The other thing that was mentioned was to use xsl to modify xml... have no
clue on how to this either.
Regards,
Dennis Belandres
Pankaj Bhide <pankajbhide@yahoo.com<mailto:pankajbhide@yahoo.com>>
Sent by: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
12/03/2013 06:53 PM
Please respond to
MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
To
"MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>" <MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>>
cc
Subject
Fw: [MAXIMO List] Inbound integration issue
Hello,
You can develop an user exit JAVA class to intercept the incoming message
(and add requirement elements e.g. revisionnumber with some default value)
before it is handed over to MBO for processing. This does not involve
changing any existing code. This user exit class needs to be registered
to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com<mailto:dennis_belandres@denso-diam.com>"
<dennis_belandres@denso-diam.com<mailto:dennis_belandres@denso-diam.com>> wrote:
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014731724#77777777-0000-0000-0000-000014731912
have a look at the zip file in here
altova should allow you read the wsdl from maximo
http://maxdemo/meaweb/wsdl/EXTSYS1_MXPOInterface.wsdl
and read an example file of your input xml
Rgds Ian
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Ian Wright
Sent: 04 December 2013 14:16
To: MAXIMO@yahoogroups.com
Subject: RE: Fw: [MAXIMO List] Inbound integration issue
Try using xslt
http://www-01.ibm.com/support/docview.wss?uid=swg21637035
the real problem is creating the script which always looks like gibberish to me , however there are some tools out there that create the code in the background
http://www.altova.com/download-trial.html#<http://www.altova.com/download-trial.html>
try mapforce
From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of dennis_belandres@denso-diam.com<mailto:dennis_belandres@denso-diam.com>
Sent: 04 December 2013 13:13
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: Re: Fw: [MAXIMO List] Inbound integration issue
Pankaj,
IBM mentioned this as one of the potential solution. But to be honest with
you, I have no idea where to start on how to do this. If you can guide me
through this process that would be great.
The other thing that was mentioned was to use xsl to modify xml... have no
clue on how to this either.
Regards,
Dennis Belandres
Pankaj Bhide <pankajbhide@yahoo.com<mailto:pankajbhide@yahoo.com>>
Sent by: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
12/03/2013 06:53 PM
Please respond to
MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
To
"MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>" <MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>>
cc
Subject
Fw: [MAXIMO List] Inbound integration issue
Hello,
You can develop an user exit JAVA class to intercept the incoming message
(and add requirement elements e.g. revisionnumber with some default value)
before it is handed over to MBO for processing. This does not involve
changing any existing code. This user exit class needs to be registered
to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com<mailto:dennis_belandres@denso-diam.com>"
<dennis_belandres@denso-diam.com<mailto:dennis_belandres@denso-diam.com>> wrote:
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
****************************************************************************************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
****************************************************************************************************************************************************************************************
Ian,
Thank you for all the assistance.
Downloaded trial version of MapForce and currently trying to go through
tutorials.
I'll send you an update as soon as I can.
Regards,
Dennis Belandres
Ian Wright <ian.wright@gdfsuezep.co.uk>
Sent by: MAXIMO@yahoogroups.com
12/04/2013 09:28 AM
Please respond to
MAXIMO@yahoogroups.com
To
"MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
cc
Subject
RE: Fw: [MAXIMO List] Inbound integration issue
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014731724#77777777-0000-0000-0000-000014731912
have a look at the zip file in here
altova should allow you read the wsdl from maximo
http://maxdemo/meaweb/wsdl/EXTSYS1_MXPOInterface.wsdl
and read an example file of your input xml
Rgds Ian
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Ian Wright
Sent: 04 December 2013 14:16
To: MAXIMO@yahoogroups.com
Subject: RE: Fw: [MAXIMO List] Inbound integration issue
Try using xslt
http://www-01.ibm.com/support/docview.wss?uid=swg21637035
the real problem is creating the script which always looks like gibberish
to me , however there are some tools out there that create the code in the
background
http://www.altova.com/download-trial.html#
try mapforce
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
dennis_belandres@denso-diam.com
Sent: 04 December 2013 13:13
To: MAXIMO@yahoogroups.com
Subject: Re: Fw: [MAXIMO List] Inbound integration issue
Pankaj,
IBM mentioned this as one of the potential solution. But to be honest with
you, I have no idea where to start on how to do this. If you can guide me
through this process that would be great.
The other thing that was mentioned was to use xsl to modify xml... have no
clue on how to this either.
Regards,
Dennis Belandres
Pankaj Bhide <pankajbhide@yahoo.com>
Sent by: MAXIMO@yahoogroups.com
12/03/2013 06:53 PM
Please respond to
MAXIMO@yahoogroups.com
To
"MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
cc
Subject
Fw: [MAXIMO List] Inbound integration issue
Hello,
You can develop an user exit JAVA class to intercept the incoming message
(and add requirement elements e.g. revisionnumber with some default value)
before it is handed over to MBO for processing. This does not involve
changing any existing code. This user exit class needs to be registered
to the inbound interface.
Pankaj
On Tuesday, December 3, 2013 3:41 PM, "dennis_belandres@denso-diam.com"
<dennis_belandres@denso-diam.com> wrote:
Does anybody know how to exclude PO.REVISIONNUM from Object Structure
MXPO? Attribute is a required field. Even after setting it not to be
required through database configuration utility it persist as read-only
field and cannot be excluded. IBM stated that this might be due to value
in primarykeycolseq. Still waiting for update from their developer.
This attribute was added after upgrading to 7.5 and now my inbound
integration is broke since it now requires that field.
Option to modify incoming source file is not an option since the original
developer no longer works with the company.
Recreation of source file can be done but will require months to develop.
We are manually working on manual data transformation until fix.
I appreciate any assistance.
Environment
Application Server: WebSphere 7
Database: MS SQL 2008 R2
Maximo: Maximo 7.5.0.5
Regards,
Dennis Belandres
Maximo Administrator
DENSO MANUFACTURING TN, INC.
TEL: (865) 982-7000 Ext. 6320
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and
Wales with a registered office address at: 40 Holborn Viaduct, London,
EC1N 2PB.
****************************************************************************************************************************************************************************************
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
****************************************************************************************************************************************************************************************
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.