How is the field -Life to Date for Asset(ASSETMETER.LIFETODATE)-calculated?

The assetmeter.lifetodate (Life to Date for Asset) calculation is done in a java class (DeployedMeter.class) that can be found in the Maximo root directory, e.g:

\Maximo\applications\maximo\businessobjects\classes\psdi\app\meter folder.
In this class, the method (calculateAverageALL) will do the calculation.

It first gets the meter lifetodate.

Then it will check if (newDate !=null && newDate.before(earliestReadingDate))

If it is true, then it will set:

lifetodate = lifetodate - new Meter Reading

Otherwise, it will set:

lifetodate = lifetodate - oldest DB Reading

At last, it will return the Average ALL as:

return lifetodate / denominator

With the Denominator being the date Delta between earliest and recent time.

Cut And Paste Not Working In The Long Description Tool Bar.

Essentially it is just part of IE security that you maybe encountering. Below is instructions to help work around this limitation.

This is part of security with IE and the clipboard. To have them work
properly, the user has to take the following steps:

1) In Internet Explorer, select Internet Options under the Tools menu
option.
2) Go to the Security Tab and click on the Trusted Sites icon
3) The Sites button should now be enabled, click that to open the
Trusted Sites dialog box.
4) Add the Maximo address/url to the list of websites to be trusted.
5) Click Close and then OK on the previous dialog.
6) The next time you are in Maximo, the first time that you click on one
of the Copy/Cut/Paste icons, Internet Explorer will tell you that the
webpage is requesting access to clipboard and do you want to allow
it. Click the 'Allow Access' button to give Maximo access. The buttons
will now work properly.

http://www-01.ibm.com/support/docview.wss?uid=swg21623215&myns=swgtiv&mynp=OCSSLKT6&mync=E

Can we Edit the attribute which is marked “Must Be” in database configuration?

We cannot Edit the Attribute which is marked as “MUST BE”, in database configuration because it have to preexisting code within the application.

How To Use A Default Value In Application Designer

How To Use A Default Value In Application Designer:

Many time during the implementation I found that we get requirement to set Default value in application or in drop down list, especially when we have cloned application. The one way is to set the default value at database level using database configuration, but that do not work when we have cloned application and in both application we need two different value.  The other way is to set a default value in application using Application designer.

Steps for setting default value using application designer is as mentioned below.

Step 1:

 a) First of all create two objects Experience and ID proof in database configuration. Then add an attribute named as LABORCODE in both the objects.

b) Make Experience and Id proof as child object in it. Then give the relationship of both the objects in Labor objects as shown below:

Step 2: In application designer, from control palette add a default value control in labor application on table body.

Step 3: Set the properties of default value as shown below:

Step 4: Save the Record and Check the values entered in labor application.

Step 5: The record that uses a default value has been shown below:

If you want to set in existing attribute follow step 2 onward. 

ORA-27476: "MAXIMO.MAXIMOTSSYNC" does not exist when Upgrading Maximo 7.1.1.10 to Maximo 7.5.0

ORA-27476: "MAXIMO.MAXIMOTSSYNC" does not exist


This problem Mainly i faced during Upgrading Maximo 7.1.1.10 to Maximo 7.5.0.

Step 1 : Change to use DBMS_SCHEDULER

CREATE OR REPLACE PROCEDURE maximo_ts_job_call AS 
BEGIN 
dbms_scheduler.create_job( 
job_name => 'MAXIMOTSSYNC', 
job_type => 'STORED_PROCEDURE', 
job_action => 'maximo_ts_job', 
start_date => SYSDATE, 
repeat_interval => 'SYSDATE + 5/1440', 
enabled => TRUE); 
END; 
/ 
exec maximo_ts_job_call(); 



select job, substr(what,1,80) from user_jobs; 

Re-run Integrity checker 

Importing Job Plan and Tasks in Maximo

How can I import a jobplan, and have predecessor tasks appear?

Create a jobplan object structure.

Add JPTASKRELATION to the object structure, as a child of JOBPLAN.

Restrict JPTASKRELATIONID and JOBPLANID.

Rules for Job Plan Field is Not Editable / Why Job Plan Field is Not Editable Even In WAPPR status?

There are rules for setting JPNUM to be editable or not. The job plan is read only and not editable when:

1. If any work plan components exist (task work orders)
2. If there are any planned( labor, material, tool)
3. Parent or Task work orders have gone through approval status in the past

NOTE: The users must decide whether they want to either manually enter work plan or use job plan as a template for copying tasks to work orders.

To correct the problem via the front end, make a duplicate of the work order and then enter a job plan on the duplicate. Then start using the duplicate work order with job plan attached.