We would like to add 3 custom fields to the rotating item receiving screen and have them populate a corresponding set of custom fields in the asset records that are created during the receiving process. Currently, the rotating item receiving screen allows you to include the serial number of each asset that you receive and it copies that to the asset records that are created.
We looked into using a crossover domain but the rotaing item receiving screen uses the assetinput table which is a non-persistent object. Unfortunately, it doesn't appear that you can create a crossover domain for non-persistent objects. We also looked into extending the java class associated with the assetinput table but it is private as are many of its methods.
In general, we want the following "crossovers" to occur when we receive rotating items:
assetinput.customfield01 --> asset.customfield01
assetinput.customfield02 --> asset.customfield02
assetinput.customfield03 --> asset.customfield03
Does anyone have any ideas?
This topic has been locked.
2 replies Latest Post - 2013-02-20T10:40:59Z by maxmix
Pinned topic Adding Custom Fields to Rotating Item Receiving Screen in Maximo 7
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-20T10:40:59Z at 2013-02-20T10:40:59Z by maxmix
maxmix 2700038K0W83 PostsACCEPTED ANSWER
Re: Adding Custom Fields to Rotating Item Receiving Screen in Maximo 72013-02-20T10:40:59Z in response to mountainsHi,
nopersistent mbos can be customized to do this.
Override the execute method at the mbo level.
The really interesting piece is where your "crossover source" is persistent.
The assetinput as such is all empty and null so you'd have to prime it on each instantiation.
This is where logic is needed, and whatever the source is, this determines if a crossoverdomain is a good choice for that task or not.
Hope those thoughts helped...