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.
This thread is old but in Maximo 7.5 I have found you need to set an Inbound Setting Restrictions on the column you want to Autonumber in the Obect Structure definition.
Find the column on the MBO in question then check the Override.
What I can not find documented is that 7.5 gives a Override and a Restricted check box. Once Override is checked you can then select Restricted. Previous Maximo 7 had just the Restricted checkbox.
How do the 2 work together? I have checked both and seem to be getting what I need as it now auto populates my ASSETNUM and JPNUM on different Object Structures.
Curiouse if anyone knows?
Miller
--- In MAXIMO@yahoogroups.com, Chris Lawless <lawlessc@...> wrote:
>
> You don't want to populate WONUM from the sequence, the sequence is for
> WORKORDERID which should be populated automatically by Maximo. I think that
> what the original poster wants is the next WONUM in sequence which comes
> from the AUTOKEY table.
>
> On Fri, Jul 2, 2010 at 9:23 AM, sriram s <sriram_maximo@...> wrote:
>
> >
> >
> > Hi ,
> >
> > This we can achieve thru SET rule under enterprise service for that WONUM
> > field.
> > Just put the value as woseq.nextval in the set rule.
> > So with this one automatically it ll give new value whenever we r
> > populating
> > workorder record from MIF.
> >
> > Regards
> > Sriram
> >
> > ________________________________
> > From: Cameron Brown <cam.brown@...<cam.brown%40rementerprise.com>
> > >
> > To: MAXIMO@yahoogroups.com <MAXIMO%40yahoogroups.com>
> > Sent: Thu, 1 July, 2010 2:00:48 AM
> > Subject: RE: [MAXIMO List] Can WONUM be autopopulated through the MIF
> >
> >
> > Hi John.
> >
> > Which version of Maximo are you using? I was trying to do this in Maximo
> > 7.1.1.5 and IBM support advised me that it was not possible without
> > custom code.
> >
> > They said that in version 7.1.1.6 there were supposed to be changes
> > which allowed you to pass NULL values but I have not tested this.
> >
> > http://www-01.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&q1=flat
> > +file&uid=swg21413859&loc=en_US&cs=utf-8&lang=en
> >
> > Here is the information that IBM sent me, hope it helps (again, I have
> > not verified that this works in 7.1.1.6)
> >
> > The key generation is performed during initialization of a new MBO.
> > When a transaction is sent in via the MIF with an Action of Add,
> > AddChange, or null ( = AddReplace), and the record does not exist for
> > replacing or changing, then an empty MBO is instantiated and the
> > autonumbered attributes are set from the autokey table. Then the MIF
> > fills in the remaining attributes from the values sent in, and validates
> > and saves.
> >
> > For null or AddChange actions, you must provide the data keys (e.g.
> > WONUM & SITEID for a workorder) so that the MIF processing class can
> > query the record to determine if it exists and must be changed/replaced,
> > or added if not found. Thus you must send in a null value wonum
> > attribute for a new workorder so that the query can be constructed.
> >
> > For interface tables, there is no mechanism to identify if a null value
> > in an iface column means "set to null" or "don't send in attribute". So
> > the design of the MIF (and MEA before that) treats all null-valued
> > columns in the iface table as "don't send in attribute". For this
> > reason you must use the Add action in order to send in a new record via
> > iface tables.
> >
> > -----------------------
> > Some customers who wish to distinguish MIF-added data from UI-entered do
> > so by supplying the wonum on the inbound transaction with a prefix
> > letter that is not used by the autokey mechanism, which also avoids
> > conflict with generated wonums.
> >
> > Cam
> >
> > From: MAXIMO@yahoogroups.com <MAXIMO%40yahoogroups.com> [mailto:
> > MAXIMO@yahoogroups.com <MAXIMO%40yahoogroups.com>] On Behalf
> > Of John Ballnik
> > Sent: Wednesday, June 30, 2010 1:36 AM
> > To: MAXIMO@yahoogroups.com <MAXIMO%40yahoogroups.com>
> > Subject: [MAXIMO List] Can WONUM be autopopulated through the MIF
> >
> > Gang,
> >
> > I'm trying to populate the WORKORDER.WONUM field for an incoming record
> > via the MIF and I keep getting the following error:
> >
> > Required field Work Order is blank
> >
> > The field is blank in the interface table and I would assume that the
> > field would autopoulate once it's processed since I have an AUTOKEY
> > attached to it. Has anyone been able to do this successfully?
> >
> > thanks,
> > John B
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>