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.
I've been getting an ERROR on our inbound Purchase Order integration for
the past few days. This started after correcting an issue with duplicated
POLINENUM from the incoming flatfiles. Can anyone shed some light or some
guidance on how to address the "BMXAA1709E..." error?
29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
structure is 1. The primary object is PO. The key is
P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0} and
relationship {1}.
29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty for
parent {0} and relationship {1}.
psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty for
parent {0} and relationship {1}.
at
psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
at
psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
at
psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
at
psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
at
psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
at
psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
at
psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
at
psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
at
psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
at
psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
at
psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
at
psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
at
psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
Environment:
Maximo 7.1.1.5
Websphere 6.1
2005 SQL Server
Regards,
Dennis
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.
1.Check your flat file where PONUM is P201~0955123174.
2.Also Check the POLINENUM if it is null. Check your object structure, if should have the POLINE Object and the relationship should be listed on it.
3. Check the flatfile in notepad for any discrepancy.
Thanks,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> I've been getting an ERROR on our inbound Purchase Order integration for
> the past few days. This started after correcting an issue with duplicated
> POLINENUM from the incoming flatfiles. Can anyone shed some light or some
> guidance on how to address the "BMXAA1709E..." error?
>
> 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
> structure is 1. The primary object is PO. The key is
> P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0} and
> relationship {1}.
> 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
> psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
> at
> psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> at
> psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> at
> psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> at
> psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> at
> psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> at
> psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> at
> psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> at
> psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> at
> psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> at
> psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> at
> psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> at
> psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> at
> psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
>
> Environment:
> Maximo 7.1.1.5
> Websphere 6.1
> 2005 SQL Server
>
>
> Regards,
>
> Dennis
>
>
>
>
>
>
>
>
>
> 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.
>
>
>
>
Hi Dennis,
The below error :
--BMXAA1709E - Compare MBOSet is empty for
parent {0} and relationship {1}.
This means, that you have a rule where POLINE is having some rule or some kind of condition which is not able to process and compare the fields from PO object to POLINE.
Check your Processing rules conditions in your enterprise service, if you have some kind of exist or any condition which is checking some rule from PO to POLINE and is not able to find the POLINE corresponding to your rule in your XML or flatfile.
Also, it says the key is P201~0955123174. That means, check your condition against this PONUM.
Thanks,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> I've been getting an ERROR on our inbound Purchase Order integration for
> the past few days. This started after correcting an issue with duplicated
> POLINENUM from the incoming flatfiles. Can anyone shed some light or some
> guidance on how to address the "BMXAA1709E..." error?
>
> 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
> structure is 1. The primary object is PO. The key is
> P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0} and
> relationship {1}.
> 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
> psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
> at
> psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> at
> psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> at
> psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> at
> psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> at
> psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> at
> psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> at
> psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> at
> psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> at
> psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> at
> psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> at
> psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> at
> psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> at
> psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
>
> Environment:
> Maximo 7.1.1.5
> Websphere 6.1
> 2005 SQL Server
>
>
> Regards,
>
> Dennis
>
>
>
>
>
>
>
>
>
> 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.
>
>
>
>
Hi Victor,
Thank you for the explanation you presented, it sounds like your on to
something.
Prior to this error we were having issues with duplicated
poline.polinenum, which was addressed recently through a change in the
external system file download. We were getting duplicates because we are
issuing multiple PR's on a single PO. Before,
PRLINE.PRLINENUM=POLINENUM.POLINENUM through processing rules. The
original poline.ponum and poline.polinenum was derived originally from a
single field that held both of those information (PONUM+POLINENUM). This
was then split through the processing rules on the enterprise service. The
external system now sends the two values separately with poline.polinenum
being coded with sequential number, which makes my current processing rule
invalid.
Deleted my processing rule to stop it from overwriting incoming file and
that's when it started having this error.
Regards,
Dennis
"Victor" <vikas17.j@gmail.com>
Sent by: MAXIMO@yahoogroups.com
10/03/2011 11:34 AM
Please respond to
MAXIMO@yahoogroups.com
To
MAXIMO@yahoogroups.com
cc
Subject
[MAXIMO List] Re: Integration issues
Hi Dennis,
The below error :
--BMXAA1709E - Compare MBOSet is empty for
parent {0} and relationship {1}.
This means, that you have a rule where POLINE is having some rule or some
kind of condition which is not able to process and compare the fields from
PO object to POLINE.
Check your Processing rules conditions in your enterprise service, if you
have some kind of exist or any condition which is checking some rule from
PO to POLINE and is not able to find the POLINE corresponding to your rule
in your XML or flatfile.
Also, it says the key is P201~0955123174. That means, check your condition
against this PONUM.
Thanks,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> I've been getting an ERROR on our inbound Purchase Order integration for
> the past few days. This started after correcting an issue with
duplicated
> POLINENUM from the incoming flatfiles. Can anyone shed some light or
some
> guidance on how to address the "BMXAA1709E..." error?
>
> 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
> structure is 1. The primary object is PO. The key is
> P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0} and
> relationship {1}.
> 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty
for
> parent {0} and relationship {1}.
> psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty
for
> parent {0} and relationship {1}.
> at
> psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> at
> psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> at
>
psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> at
>
psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> at
> psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> at
> psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> at
>
psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> at
> psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> at
>
psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> at
> psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> at
> psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> at
> psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> at
> psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
>
> Environment:
> Maximo 7.1.1.5
> Websphere 6.1
> 2005 SQL Server
>
>
> Regards,
>
> Dennis
>
>
>
>
>
>
>
>
>
> 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.
Hi Dennis,
Please provide me with the following information :
1. What is the sequential number, are you using ?
2. Can you tell me more about your processing rule ?
If you have any written requirements or details for your interface, can you paste this part of the requirement in the message.
Thanks in advance,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> Hi Victor,
>
> Thank you for the explanation you presented, it sounds like your on to
> something.
> Prior to this error we were having issues with duplicated
> poline.polinenum, which was addressed recently through a change in the
> external system file download. We were getting duplicates because we are
> issuing multiple PR's on a single PO. Before,
> PRLINE.PRLINENUM=POLINENUM.POLINENUM through processing rules. The
> original poline.ponum and poline.polinenum was derived originally from a
> single field that held both of those information (PONUM+POLINENUM). This
> was then split through the processing rules on the enterprise service. The
> external system now sends the two values separately with poline.polinenum
> being coded with sequential number, which makes my current processing rule
> invalid.
> Deleted my processing rule to stop it from overwriting incoming file and
> that's when it started having this error.
>
> Regards,
>
> Dennis
>
>
>
>
>
> "Victor" <vikas17.j@...>
> Sent by: MAXIMO@yahoogroups.com
> 10/03/2011 11:34 AM
> Please respond to
> MAXIMO@yahoogroups.com
>
>
> To
> MAXIMO@yahoogroups.com
> cc
>
> Subject
> [MAXIMO List] Re: Integration issues
>
>
>
>
>
>
>
>
> Hi Dennis,
>
> The below error :
> --BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
>
> This means, that you have a rule where POLINE is having some rule or some
> kind of condition which is not able to process and compare the fields from
> PO object to POLINE.
>
> Check your Processing rules conditions in your enterprise service, if you
> have some kind of exist or any condition which is checking some rule from
> PO to POLINE and is not able to find the POLINE corresponding to your rule
> in your XML or flatfile.
>
> Also, it says the key is P201~0955123174. That means, check your condition
> against this PONUM.
>
> Thanks,
> Victor.
>
> --- In MAXIMO@yahoogroups.com, dennis_belandres@ wrote:
> >
> > I've been getting an ERROR on our inbound Purchase Order integration for
>
> > the past few days. This started after correcting an issue with
> duplicated
> > POLINENUM from the incoming flatfiles. Can anyone shed some light or
> some
> > guidance on how to address the "BMXAA1709E..." error?
> >
> > 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
> > structure is 1. The primary object is PO. The key is
> > P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0} and
> > relationship {1}.
> > 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty
> for
> > parent {0} and relationship {1}.
> > psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty
> for
> > parent {0} and relationship {1}.
> > at
> > psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> > at
> > psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> > at
> >
> psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> > at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> > at
> >
> psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> > at
> > psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> > at
> > psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> > at
> >
> psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> > at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> > at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> > at
> > psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> > at
> >
> psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> > at
> > psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> > at
> > psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> > at
> > psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> > at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> > at
> > psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
> >
> > Environment:
> > Maximo 7.1.1.5
> > Websphere 6.1
> > 2005 SQL Server
> >
> >
> > Regards,
> >
> > Dennis
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 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.
>
>
>
>
>
Victor,
Sequential number are just int hard coded from the external system and set
to increment by 1 for each PONUM instance.
The processing rule was created to pull out the requestedby information
from the prline table to poline. This field is basically being used to
notify requester that there parts has been receive when PO status changes
to close.
Anyway, I think we finally got it resolve by adding a field in the prline
table that creates a one-to-one relationship with the poline.
Thanks for all the efforts in trying to resolve my predicament.
Regards,
Dennis
"Victor" <vikas17.j@gmail.com>
Sent by: MAXIMO@yahoogroups.com
10/03/2011 02:59 PM
Please respond to
MAXIMO@yahoogroups.com
To
MAXIMO@yahoogroups.com
cc
Subject
[MAXIMO List] Re: Integration issues
Hi Dennis,
Please provide me with the following information :
1. What is the sequential number, are you using ?
2. Can you tell me more about your processing rule ?
If you have any written requirements or details for your interface, can
you paste this part of the requirement in the message.
Thanks in advance,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> Hi Victor,
>
> Thank you for the explanation you presented, it sounds like your on to
> something.
> Prior to this error we were having issues with duplicated
> poline.polinenum, which was addressed recently through a change in the
> external system file download. We were getting duplicates because we are
> issuing multiple PR's on a single PO. Before,
> PRLINE.PRLINENUM=POLINENUM.POLINENUM through processing rules. The
> original poline.ponum and poline.polinenum was derived originally from a
> single field that held both of those information (PONUM+POLINENUM). This
> was then split through the processing rules on the enterprise service.
The
> external system now sends the two values separately with
poline.polinenum
> being coded with sequential number, which makes my current processing
rule
> invalid.
> Deleted my processing rule to stop it from overwriting incoming file and
> that's when it started having this error.
>
> Regards,
>
> Dennis
>
>
>
>
>
> "Victor" <vikas17.j@...>
> Sent by: MAXIMO@yahoogroups.com
> 10/03/2011 11:34 AM
> Please respond to
> MAXIMO@yahoogroups.com
>
>
> To
> MAXIMO@yahoogroups.com
> cc
>
> Subject
> [MAXIMO List] Re: Integration issues
>
>
>
>
>
>
>
>
> Hi Dennis,
>
> The below error :
> --BMXAA1709E - Compare MBOSet is empty for
> parent {0} and relationship {1}.
>
> This means, that you have a rule where POLINE is having some rule or
some
> kind of condition which is not able to process and compare the fields
from
> PO object to POLINE.
>
> Check your Processing rules conditions in your enterprise service, if
you
> have some kind of exist or any condition which is checking some rule
from
> PO to POLINE and is not able to find the POLINE corresponding to your
rule
> in your XML or flatfile.
>
> Also, it says the key is P201~0955123174. That means, check your
condition
> against this PONUM.
>
> Thanks,
> Victor.
>
> --- In MAXIMO@yahoogroups.com, dennis_belandres@ wrote:
> >
> > I've been getting an ERROR on our inbound Purchase Order integration
for
>
> > the past few days. This started after correcting an issue with
> duplicated
> > POLINENUM from the incoming flatfiles. Can anyone shed some light or
> some
> > guidance on how to address the "BMXAA1709E..." error?
> >
> > 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
> > structure is 1. The primary object is PO. The key is
> > P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0}
and
> > relationship {1}.
> > 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty
> for
> > parent {0} and relationship {1}.
> > psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty
> for
> > parent {0} and relationship {1}.
> > at
> >
psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> > at
> >
psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> > at
> >
>
psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> > at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> > at
> >
>
psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> > at
> > psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> > at
> >
psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> > at
> >
>
psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> > at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> > at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> > at
> > psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> > at
> >
>
psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> > at
> > psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> > at
> > psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> > at
> > psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> > at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> > at
> > psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
> >
> > Environment:
> > Maximo 7.1.1.5
> > Websphere 6.1
> > 2005 SQL Server
> >
> >
> > Regards,
> >
> > Dennis
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 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.
>
>
>
>
>
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.
Hi Dennis,
I am glad you got it resolved.
Thanks ,
Victor.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> Victor,
>
> Sequential number are just int hard coded from the external system and set
> to increment by 1 for each PONUM instance.
>
> The processing rule was created to pull out the requestedby information
> from the prline table to poline. This field is basically being used to
> notify requester that there parts has been receive when PO status changes
> to close.
>
> Anyway, I think we finally got it resolve by adding a field in the prline
> table that creates a one-to-one relationship with the poline.
>
> Thanks for all the efforts in trying to resolve my predicament.
>
>
> Regards,
>
> Dennis
>
>
>
>
> "Victor" <vikas17.j@...>
> Sent by: MAXIMO@yahoogroups.com
> 10/03/2011 02:59 PM
> Please respond to
> MAXIMO@yahoogroups.com
>
>
> To
> MAXIMO@yahoogroups.com
> cc
>
> Subject
> [MAXIMO List] Re: Integration issues
>
>
>
>
>
>
>
> Hi Dennis,
>
> Please provide me with the following information :
>
> 1. What is the sequential number, are you using ?
> 2. Can you tell me more about your processing rule ?
>
> If you have any written requirements or details for your interface, can
> you paste this part of the requirement in the message.
>
> Thanks in advance,
> Victor.
>
> --- In MAXIMO@yahoogroups.com, dennis_belandres@ wrote:
> >
> > Hi Victor,
> >
> > Thank you for the explanation you presented, it sounds like your on to
> > something.
> > Prior to this error we were having issues with duplicated
> > poline.polinenum, which was addressed recently through a change in the
> > external system file download. We were getting duplicates because we are
>
> > issuing multiple PR's on a single PO. Before,
> > PRLINE.PRLINENUM=POLINENUM.POLINENUM through processing rules. The
> > original poline.ponum and poline.polinenum was derived originally from a
>
> > single field that held both of those information (PONUM+POLINENUM). This
>
> > was then split through the processing rules on the enterprise service.
> The
> > external system now sends the two values separately with
> poline.polinenum
> > being coded with sequential number, which makes my current processing
> rule
> > invalid.
> > Deleted my processing rule to stop it from overwriting incoming file and
>
> > that's when it started having this error.
> >
> > Regards,
> >
> > Dennis
> >
> >
> >
> >
> >
> > "Victor" <vikas17.j@>
> > Sent by: MAXIMO@yahoogroups.com
> > 10/03/2011 11:34 AM
> > Please respond to
> > MAXIMO@yahoogroups.com
> >
> >
> > To
> > MAXIMO@yahoogroups.com
> > cc
> >
> > Subject
> > [MAXIMO List] Re: Integration issues
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Dennis,
> >
> > The below error :
> > --BMXAA1709E - Compare MBOSet is empty for
> > parent {0} and relationship {1}.
> >
> > This means, that you have a rule where POLINE is having some rule or
> some
> > kind of condition which is not able to process and compare the fields
> from
> > PO object to POLINE.
> >
> > Check your Processing rules conditions in your enterprise service, if
> you
> > have some kind of exist or any condition which is checking some rule
> from
> > PO to POLINE and is not able to find the POLINE corresponding to your
> rule
> > in your XML or flatfile.
> >
> > Also, it says the key is P201~0955123174. That means, check your
> condition
> > against this PONUM.
> >
> > Thanks,
> > Victor.
> >
> > --- In MAXIMO@yahoogroups.com, dennis_belandres@ wrote:
> > >
> > > I've been getting an ERROR on our inbound Purchase Order integration
> for
> >
> > > the past few days. This started after correcting an issue with
> > duplicated
> > > POLINENUM from the incoming flatfiles. Can anyone shed some light or
> > some
> > > guidance on how to address the "BMXAA1709E..." error?
> > >
> > > 29 Sep 2011 14:20:34:110 [ERROR] Processing failed for POU. The object
>
> > > structure is 1. The primary object is PO. The key is
> > > P201~0955123174.BMXAA1709E - Compare MBOSet is empty for parent {0}
> and
> > > relationship {1}.
> > > 29 Sep 2011 14:20:34:126 [ERROR] BMXAA1709E - Compare MBOSet is empty
> > for
> > > parent {0} and relationship {1}.
> > > psdi.util.MXApplicationException: BMXAA1709E - Compare MBOSet is empty
>
> > for
> > > parent {0} and relationship {1}.
> > > at
> > >
> psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcesser.java:430)
> > > at
> > >
> psdi.iface.proc.ProcProcesser.processAssignments(ProcProcesser.java:333)
> > > at
> > >
> >
> psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProcesser.java:149)
> > > at psdi.iface.mic.MicSetIn.applyMboRules(MicSetIn.java:275)
> > > at
> > >
> >
> psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessImpl.java:896)
> > > at
> > > psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.java:505)
> > > at
> > >
> psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:374)
> > > at
> > >
> >
> psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:273)
> > > at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:151)
> > > at psdi.iface.mic.MicService.processDataIn(MicService.java:1189)
> > > at
> > > psdi.iface.mic.MicService.processExternalData(MicService.java:1095)
> > > at
> > >
> >
> psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:107)
> > > at
> > > psdi.iface.jms.JMSQueueCronTask.getMessage(JMSQueueCronTask.java:302)
> > > at
> > > psdi.iface.jms.JMSQueueCronTask.cronAction(JMSQueueCronTask.java:196)
> > > at
> > > psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
> > > at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
> > > at
> > > psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
> > >
> > > Environment:
> > > Maximo 7.1.1.5
> > > Websphere 6.1
> > > 2005 SQL Server
> > >
> > >
> > > Regards,
> > >
> > > Dennis
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 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.
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
>
>
> 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.
>
>
>
>
>