Fixed Assets Integration and Testing Guide

F I XED ASSETS & MAINTENANCE
Integration and Testing Guide
OFF THE BEATEN TRACK
REDHUAN D. OON
Sponsored by Sysnova
June 2011

ADempiere ERP Project Fixed Assets & Maintenance
“When I reached my deathbed, there is nothing left to reflect”

- red1
Most of the work here was done while encountering Australia for my very first time. The cover photo is taken
while jay-walking around Melbourne when I stayed with Steven Sackett, our ADempiere top contributor ac-
countant. The series of photos on the first chapter are:
1. I find Melbourne a very relaxed and wonderful city, with lots of amenities and a free tram that goes around
the city-centre. I also find many Asians studying or taking over the shops there. This is even more so in Syd-
ney
2. Prices are quite high, though okay if you work and earn there as the minimal wage is the highest at A$15 per
hour. But the appreciated exchange rate (thanks to China buying up their coal and other minerals for the
next 200 years) above the green-bag is hurting general Aussie businesses.
3. It is hard to hide the laid-back culture as Steven took me to his close buddy’s yacht club and look at his two
yachts.
4. At Sydney Harbour, I come into contact with the Stolen Generation for this first time.
5. I Wwoof-ed for the first time ever in Terrey Hills, Sydney, which involved shoveling compost into bags. Here,
my host family member takes the bags onto the truck to sell in the town.
This work stands on the shoulders of many giants and thus the best it can do is to be free for others to stand
back on, ad infinitum.
(www.red1.org)
copyle% Redhuan D. Oon 2011 2

TABLE OF CONTENTS
About Assets 4
Contributions to ADempiere 4
Gaps in Fixed Assets 5
Create Asset &om Invoice 7
Testing Fixed Assets 17
Getting Fixed Assets 23
Gaps in Asset Maintenance 24
Testing Asset Maintenance 32
Getting Asset Maintenance 34

F I X ED ASSETS & MAINTENANCE

Integration and Testing Guide
About Assets
Fixed Assets was originally not present in Compiere during the ADempiere fork in Septem-
ber 2006. What was known as Assets in Compiere that time is just ‘Assetization during
Shipment’ where Customers are tagged as to what products they purchased that we wish to
track by their generated and contolled serial numbers during shipment.
Images details please refer preface above
In suit, Asset Maintenance is also not further catered for other than as stated above, they
are tracked by who has owned what via normal purchase and shipment. There are stub fields
for specifying if the asset is owned, depreciated and disposed but nothing further happens
around such information.
Contributions to ADempiere
Fixed Assets that does proper classification was first contributed by Robert Klein:
1. Framework for Fixed Assets within Compiere/ADempiere
2. Allotting default accounts for posting of Fixed Assets transactions
3. Depreciation formulas
4. Transfers and Splits
5. Reporting
Robert’s work was integrated into the trunk for some time and is the basis i worked from.
Robert also contributed a very informative foundation guide called FixedAssetExtensionMan-

ual _0_0_5.pdf that can be downloaded from his OSLABS.org site or our project SVN. I
would heavily recommend this manual for the first time end-user.

Subsequently the next significant contribution is from Teo Sarca when he was working
from his previous company: Arhipac, Romania. However the framework of items in Fixed
Assets remained largely the same as contributed by Robert Klein. What Teo did was gener-
ally the refactoring of code with more use of Model classes as well as the more important
use of DocType conventions (Prepare and Complete of Documents) that can be eventually
used for WorkFlows.
However these contributions were not maintained and so we find Robert Klein’s work ei-
ther broken in few places or having some gaps. Teo’s work has not been integrated to the
trunk or synchronised with Robert’s, and also has few gaps within it when i was testing it.
My work here under sponsorship from Sysnova of Bangladesh is to do all that and see to
the other contribution called Asset Maintenance from Ramiro of OFBConsulting in
Chile:
1. Record logs for maintaining each asset
2. Logging by Calendar period (time schedule) or Meter (measurement)
3. Generating period maintenance work orders and tracking their completion
I thus made the necessary changes to integrate the latest Fixed Assets and Maintenance to
the latest trunk by way of Carlos Ruiz’s ADempiere361. This should also work with the main
ADempiere project trunk.
I will now elaborate on each contribution above as necessarily needed to be understood by

both developer and implementor from how i encountered them. Then i will go through how
the testing is done on them. Then lastly i will describe the steps to set it up for production
or further development purpose as well as the testing framework for continous quality as-
surance.
Gaps in Fixed Assets

As advised here by Heng Sin, the present Fixed Assets is too broken and the Teo's contribu-
tion is the one to pursue. However it is also not maintained and outdated with gaps in sam-
ple data and code which i have to handle before starting a base regression testing.
Nevertheless the former Fixed Assets worked with its Asset Creation from Invoice (Vendor).
Here i start listing the gaps encountered while upgrading the trunk to Teo’s and when re-
solved or upgraded will go to the QA chapter to go through the tests. I commit to a new
branches/FixedAssets to avoid overiding Teo’s work.

Below is when i first used the trunk base that already has Robert’s work and began putting
in Teo’s code branch. Immediately there were some gaps.
1. This has been reported in the project tracker (link to solution).
a. Invoice model conflict

i: Missing MInvoice.COLUMNNAME_C_CashPlanLine_ID (from CarlosRuiz 361)
ii: Missing MInvoice.COLUMNNAME_IsFixedAssetInvoice (Teo’s)
iii: Missing MInvoiceLine.COLUMNNAME_IsFixedAssetInvoice (Teo’s)
b. Include MInvoiceLine from version 361 to module FA to avoid classpath conflict
2. Missing sample data
a. Asset Type not accessible by role (just run Role Access Update)
b. Asset Group has no sample data with Accounting Defaults
c. Asset Group Acct has no Depreciation record needed by constraint > ===========>
Trx.commit: POSave_6d48560c-50&-4877-9bac-22aff(b503 [11]
org.postgresql.util.PSQLException: ERROR: insert or update on table "a_asset_group_acct" violates foreign key constraint
"adepreciation_aassetgroupacct"
Detail: Key (a_depreciation_id)=(1000003) is not present in table "a_depreciation".; State=23503; ErrorCode=0 (link to
solution)
3. Missing CalloutAsset. Solved with a blank stub committed in new branch (rev15275).
In order to keep track of the issues and changes raised you can go to the trackers that i
raised and maintained in Fixed Asset Tracker of SourceForge project space:
Many Romanian terms have also been translated wherever found within the code or output.
Teo’s Fixed Assets also does not create Asset from Invoice but via MatchInvoice process as
an lternative approach. Therefore i upgraded Robert’s CreateInvoicedAsset.java to work

with Teo’s better design. The intention is to ensure there is proper and common proof of
concept with such an Asset creation before proceeding further.
Create Asset from Invoice

We achieve this through the Invoice (Vendor) (or AP Invoice) window. See the InvoiceLine
tab been selected below.
i indicated that this is Asset Related and gave the Asset Group. The product was first cre-
ated prior, where i also grouped it to the same Asset Group so that it is considered a real as-
set. I select it as a Capital and the Asset field is left blank as it is not created yet. After it is
created you can use Expense and fill the Asset value for it to charge to.
However the concept of Asset by Teo is based on it as a ‘product’ and not an expense which
according to Steven Sackett of Adaxa is not entirely correct. This bug was recently pointed
out by Steven and thus still present in Teo’s ModelValidator. Thus you cannot charge an ex-
pense to the Asset via this AP Invoice approach yet.
Next you complete the Invoice and then go to the Inbound Charges From AP to create your
Asset.
Oh, one more thing. Your AssetGroup has to have a AssetGroupAccts tab populated to de-
fine this group's life usage, depreciation method and default accounts to post to.

After the Inbound Charges is executed you will get the above Asset window populated. This
window has more tabs than Robert Klein's particularly the Product (AssetProduct) tab and
Expense (DepreciationExpense) tab.
I have to make the extra code to get this populated and it does obtain a new Attribute Set
Instance or Serial No. to attach to this Asset. Note that there are other 3 empty fields. I will
edit the code to populate this too.

By the way, some of these tabs were not supposed to show if the Asset is not to 'depreciate'.
That has an issue as some tabs get corrupted in its display. So i removed all such DisplayLo-
gic - @IsDepreciated@='Y' so now all tabs appear permanently. Later we can try to solve this
small issue.
The Asset Balances is a tab for DepreciationWorkfile. Note the Romanian terms to be
translated and the Update depreciation process button to investigate what it will really do. I
assume that this is a check-sheet to do the real depreciation.

Now the above Accounting Setup only appears when you activate the Show Accounting in
Preferences. This tab shows the Accounting defaults taken from the AssetGroupAccts. This
will be used in the Depreciation processing.
This Activation/Addition (AssetAddition) tab is 'read-only' with a process button too. Also
needing some further investigation. From what i read of the code this document is impor-
tant and referred to in some processes.

The Expense tab (DepreciationExp) takes care of the Journal entries where a pair of records
are created. One record is of contra or minus value to the other record. So in our case we get
another record that has the value '-$120,000'.
There is a Process Depreciation Expense which does the actual accounts posting. However
on pressing it, the class associated, ro.ARH1pac.adempiere.fa.process.A_Depreciation_Exp_Process
is not found. In actual fact that class exist and it is just a typo ARH1 = arhi, and after that it
does run. According to Teo here, it is for single record testing and actual processing is done
in batch.
I also confirmed AssetAddition's role to process Depreciation Expense records. It will

match with the Invoice (this may be tested by Kittiu to see if it matches with Shipment re-
cord instead). As this Activation/Addition creates the Depreciation Expenses, the Build-
DepWorkFile and Balances tab are not needed to do it.

Below are the other changes that happened after the process. The Asset tab shows its status
changed from NEW to ACTIVATED. The InvoiceLine also shows the Asset ID reference.
For Accounting Consequences, i managed to get it via Post Depreciation Entry window:

The Depreciation Expense report suffers a deep wound here. Thanks to Carlos, it is solved.
Below is a sample report from the trial above. Notice that the first line is ticked green show-
ing it is been processed at the Asset > Expense tab. Not necessarily posted to accounts.
Now there is left only one last matter which is the Disposal of Assets which should be a full
loop.
This is how we do disposals:

1. You use the window Asset Activation/Disposal under the Split Transfers and Disposal
menu.
2. You create a record of the asset you wish to dispose.
2.1 Asset must not have its current month already depreciated or else it will give a "Already
Depreciated" status and not allow it through.
2.2 Asset must be an activated asset with depreciation expense records.
2.3 You cannot change the status manually which will give you the Changed Status error.
3. Give the values in the fields displayed.
4. Press 'Complete'
5. Account tab when active will show 'Posting' button, if it is not automated, you can post it
and view the accounts.
Below is what you should see. In this case i am disposing the Asset after some depreciation,
thus the variance is recorded. You may set the account date to a future date to allow the dis-
posal. Otherwise the system will detect your present period which should not be depreci-
ated yet.
With this we have achieved a close loop process on Fixed Assets and other processes or
needs are workable as there is framework wide integrity.
I noted that Teo's methods are not activated as Rob's methods are still displayed. I managed
to correlate Accelerated Variable and below i test it out.
Here i set the Depreciation method to Variable Accelerated (Accelerated Depreciation in

Teo's). Remember the percentage to depreciated for the first period of the year has to be in
0.05 (for 5%). Note that i set 4 years for Usable Life which automatically set 48 periods.

After Workfile Update Depreciation we get the following Depreciation Expenses records.
There are 48 expense records to depreciate the asset fully. Note that this method starts the
depreciation the 2nd year onwards (see next page). The first period of the year is depreci-
ated according to what percentage we set, which in this case is 5%.
Steven Sackett showed me some great

scenery around his place in Brighton.

It was natural disruption but I was in the ferry heading

to Manly Wharf and hanging around for 3 more weeks

Testing Fixed Assets

First we trace the steps to execute.
1. Creating Fixed Assets from Invoice. This will create the file data:
A_Asset
A_AssetAccts
A_Depreciation_Workfile
A_Asset_Addition
A_AssetChange
Looking inside the code, the MAsset ckass creates ASI for new Asset beforeSave() and for
creating from MAsset (MInventory inventory, MInventoryLine invLine, BigDecimal qty,
BigDecimal costs) but deprecates away Shipment : MAsset (MInOut shipment, MInOut-
Line shipLine, int deliveryCount)
Menu Call: From Invoice window at InvoiceLine is set Fixed Assets information
Process Name: Inbound Charges &om AP takes those completed invoices to create the
above.
Process classes: There are two classes i looked into. One is the incumbent from Robert
Klein called BuildDepWorkFile. The other is from Teo Sarca's A_Depreciation_Work-
file_Build which i investigated if it properly deprecates Robert's which it is doing. I used
that as the process, upgrading some parts to make it work.
The basic steps from those classes are as follows:
1. BuildDepWorkFile
//1. Delete previous Depreciation Expense records
//2. Initialize Depreciation Workfile records that fit the params
//3. Select where Asset from WorkFile and Depreciation Build falls within params, is depre-
ciated but not fully,
//4. For each Asset Workfile, get its accounting elements for the selected Asset
//5. for each Accounting Element, get its Depreciation and Depreciation Convention
//6. Record booked depreciation expense
//7. Set depreciation date and record in workfile, then save it.
//8. Calculate life to date depreciation
//9. Calculate necessary adjustment per period

v _ D e p _ E x p _ Ad j u s t m e n t =
DepreciationAdj.Dep_Adj(depreciation_method.getDepreciationTy pe(),rs2.getInt("A_Asset_ID") ,
(v_Dep_Exp_Inception.subtract(assetwk.getA_Accumulated_Depr())) , (Math.floor(DateAcctMonth)),
rs2.getString("PostingType") , rs2.getInt("A_ASSET_ACCT_ID"));
//10. Record necessary adjustments in new Depreciation Expense

//11. Create the two DR/CR DepExp recs.
Here i elaborate the first step:

====== CreateInvoicedAsset ===
0. Open Periods for Calendar Month
1. First action to create asset from invoice
1.1 at InvoiceLine, zoom create Building product to ProductCategory Buildings (new)
2. Called from Inbound Charges from AP, after completing Invoices that has isFixedAsset.
2.1 New Acct_Group Accts exists and isProcessed (Process Now field checked).
3. For Capital, Creates new A_Asset, A_AssetAcct, A_Depreciation_Workfile, A_Asset_Ad-
dition, A_AssetChange,
3.1 Journal Entries - DepreciationExpenses DR/CR (100000/price), (230/-price).
3.2 For Expenses, this is Teo's new way which uses new Document Depreciation Exp to
handle accounts posting.
//check assetgroupaccts.getA_Disposal_Revenue()/getA_Disposal_Loss() // deprecated by
Teo's
4. Update Depreciation to create Depreciation Expenses records according to the periods
(12 per year specified in Activate/Addition or Balance (WorkFile).
5. Process Depreciation (Expense record) consecutively during each period to post deprecia-
tion to defaulted accounts.
6.Disposal can be done at any period after depreciation.
Below is the Fitnesse testing done. Disposal is left out for future work as the target class
MAssetDisposed is not easily trackable via its TrxName.
Below is the Fitnesse Testing done on Fixed Assets. The code is committed as Fitnesse Fixed
Assets in Project SVN. Note that this test is dynamic allowing to set the Depreciation
Method to be either Straight Line or Variable Accelerated. The duration of Usage Life can
also be set, i.e. 2 years instead of the 20 years in database record for 'Building'.


We Asians are always followers of foreign ideas. I bet these chits

will get pirated before long. Later I learnt that shops are banning
Chinese from entering, to photograph and steal ideas.

I processed 2 months or periods of depreciation records. The user can do more by replicating the
rows here and setting the 'Periods From Today' value as shown below.

You can see that 2 set of accounting facts above are produced and the Workfile is at the 2nd pe-
riod with both depreciations accumulated. (Sorry about the accidentally repeated image below.)
You can see in the above history file of the actions that has taken place. During disposal there
should also be a change record 'DIS' but left out in Teo's MAssetDisposed class. This can be im-
plemented by looking at Rob K's AssetDisposed class.

Getting Fixed Assets

Source for Fixed Assets that i tested with integration and gaps resolving is committed to the
project space at http://sf.net/projects/adempiere under branches/Fixed Assets.
There is a latest FA.jar there to be used. Then you will need to apply the migration scripts
within the folder. There is a Readme text to give the steps.
For testing Fixed Assets, you can checkout the FitnesseFixedAssets and FitnesseStory pro-
jects. Again there is Readme text to guide.
In the testing there is regression testing checks that the ADempiere instance is backward
compatible with 361, Libero Manufacturing and Asset Maintenance. Under the branches/
Maintenance project you can apply the jar and migration scripts and still able to test the
Fixed Assets and backward compatible tests such as ‘Create New Product’, and ‘Make-
ToOrder’s.
This is the cabin that I stayed in for 10 days in the Terrey Hills farm. It
has an open kitchen all stocked up to last me quite well. But still I lost a
good 5 kilos after another 10 days of meditation with vegetarian food
minus dinners up in a Blue Mountains meditation centre.

Gaps in Asset Maintenance

The add-on module Asset Maintenance Management module from OFBConsulting has
good demo movies for me to reenact the menu structure and setup data which was missing.
As with others, it should be maintained and upgraded to work with latest trunk. Here i been
making notes on whatever gaps i found before creating QA testing framework like i been
doing for the rest. This task is also sponsored by Sysnova of Bangladesh. As expected, i am
making this integration onto the 361 Carlos Ruiz version. It should work with trunk versions
as they are merging most of the core code.
For a start, as reported here, the 2Pack zip needs a small tweak. A tracker is opened for this.
All work is tracked in this contribution thread. Again, like the module before this, i commit
a fresh branch as Branches/Maintenance in the SVN of the project space.
Instead of 2Pack which is difficult to maintain for ongoing development work i have con-
v e r t e d i t i n t o a c o m p l e t e m i g r a t i o n s c r i p t . ( Fi n d t h a t u n d e r
/migration./../00_Maintenance_2Pack_postgresql.sql}
When the module is finally added to the ADempiere instance, we can get the Menu struc-
ture and the new windows as shown on the next page.

There were numerous errors and bugs in the Maintenance module which is stated and cross
linked in the contribution tracker. A list of the issues with most of them resolved here
http://sourceforge.net/tracker/?func=detail&aid=3311667&group_id=176962&atid=879332.
Here is a note about debugging in Eclipse. You will have the Maintenance project build path
dependent on both FixedAssets and Adempiere. However it may not take the FA's class but
the Adempiere class first. We can set that right by controlling the build output path. You do
that by going to:
1. Maintenance project properties (by right clicking on it in Eclipse)

2. Order and Export tab.
3. Arrange the FixedAssets to be at the top of the stack
4. Tick FixedAssets to ensure it gets exported.
5. Give a good 'build project' to the projects.
After that the CreateInvoicedAsset will run properly (taking from FixedAssets rather than
adempiere361).
Maintenance Work Order

The maintenance system allows to generate work orders according to calendar date schedule
or to other meter
measurement readings
such as in KM (kilome-
ters). Here we show a
complete process using
the meter type. Later,
we inject Calendar pa-
rameters to view a dif-
ferently programmed
outcome.
Firstly we setup the

Meter window and a
Standard Job window.

Then we setup the Job Standard window for an asset.
We got to the task tab and setup the following specifying the task UOM and duration.
Next we define this standard job’s required resources.

With that done, we can go and define a proper maintenance job that takes from this stan-
dard template we just defined.
Note that we select the right Programming Type that we want. We also set the intervals of
readings. Then at the bottom we select the template we just defined above. This will popu-
late the other tabs with the same information. It is just a copy process or reusing the same
template as a convenience for other jobs that uses the same job specifications. But here in
the maintenance window we now tell the system to take note of the KM reading of an asset
and increment after each job. Users or maintenance crew can then take note of the next
reading to repeat the maintenance job. In the test later we shall see the sample output.
Now we are ready to start the job generation or called the Prognosis process. We do that by
clicking on the icon in the menu with the same name. The following dialog box shall appear.

Press start. You shall see a pop-up window below. The resulting row that appeared is pro-
duced by checking with the current system date, that the time-frame for a work order is due
or within the period defined.
Next you tick the checkbox on the left of the row and click on Generate OT. That shall
produce a work order for our next action.

Note that there is a Process Now button

but would not proceed if the underlying
tasks are not checked to be done or com-
pleted.
You can do that by selecting the options in the Status field and choose appropriately. Once
the task is considered completed, you can return to the higher tab and process it. A pop-up
dialog box will appear and just select Complete for DocAction and click on the green tick
button. Note the status and processed boxes are updated as shown below.

Next as promised, we switch the Maintenance system to a calendar based format. We select
that in the Programming Type field below. Note that the column display changes. There is
now a Date last run and a Date next run fields.
Prognosis process will generate the needed tasks to run. Note that the MP and Description
fields give different type of information

Check the Generate OT box on the left and click on the Generate OT button below.
Then open the Work Order OT window to view the latest work order. Note the text in the
Descripton and as usual you may process the tasks at the Tasks tab and return to this main
tab to Process Now.

Testing Asset Maintenance

Below are the screen output of the Fitnesse testing framework created for Asset Mainte-
nance contributed by OFB Consulting of Chile, and sponsored by Sysnova. The testing
framework is committed at branches/FitnesseMaintenance and the story script is in the
usual FitnesseStory branch. Please note that the original branch is duplicated and resolved
as a result during some of its code review by and committed as a new branches/Maintenance.

The above test data input is setting the Programming Type to be either M (meter) or C
(Calendar) which produces different calculation of maintenance logs.
You can see in the last image below where the maintenance record is requeried to show its
Next Run (for Calendar) and Next MP (for Meter) changed accordingly.

Note that the migration scripts in Branches/Maintenance are split to a new sub folder
‘TestData’ which you apply to get the test data with Asset sample setup. It is so that without
applying them you can run a Fixed Assets regression test which creates a similar Asset from
the same Invoice. This is done so that the user can ascertain the instance is backward com-
patible to Libero Mfg and FA.
Getting Asset Maintenance

Similar to other projects. there is a Maintenance.jar committed to the branches/
Maintenance folder in the SVN of the project space. The jar is compiled from the jardesc
make of the source. After running setup of the binary with all the other jars from Libero
Mfg and Fixed Assets you can apply the migration scripts to do backward testing of Fixed
Assets and others tests such in the Story script for it such as New product Standard Pric
Variance and MakeToOrder. In order to run Maintenance tests, you need to apply the
scripts from the testdata folder. Choose the right DB folder within that.

Fixed Assets Integration and Testing Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fixed Assets Integration and Testing Guide

Uploaded by

Copyright:

Available Formats

F I XED ASSETS & MAINTENANCE

Integration and Testing Guide

OFF THE BEATEN TRACK

“When I reached my deathbed, there is nothing left to reflect”

copyle% Redhuan D. Oon 2011 2

copyle% Redhuan D. Oon 2011 3

F I X ED ASSETS & MAINTENANCE

Images details please refer preface above

1. Framework for Fixed Assets within Compiere/ADempiere

2. Allotting default accounts for posting of Fixed Assets transactions

4. Transfers and Splits

Robert also contributed a very informative foundation guide called FixedAssetExtensionMan-

copyle% Redhuan D. Oon 2011 4

1. Record logs for maintaining each asset

2. Logging by Calendar period (time schedule) or Meter (measurement)

3. Generating period maintenance work orders and tracking their completion

I will now elaborate on each contribution above as necessarily needed to be understood by

Gaps in Fixed Assets

copyle% Redhuan D. Oon 2011 5

1. This has been reported in the project tracker (link to solution).

a. Invoice model conflict

2. Missing sample data

copyle% Redhuan D. Oon 2011 6

Create Asset from Invoice

copyle% Redhuan D. Oon 2011 7

copyle% Redhuan D. Oon 2011 8

copyle% Redhuan D. Oon 2011 9

copyle% Redhuan D. Oon 2011 10

I also confirmed AssetAddition's role to process Depreciation Expense records. It will

copyle% Redhuan D. Oon 2011 11

copyle% Redhuan D. Oon 2011 12

copyle% Redhuan D. Oon 2011 13

Here i set the Depreciation method to Variable Accelerated (Accelerated Depreciation in

copyle% Redhuan D. Oon 2011 14

Steven Sackett showed me some great

copyle% Redhuan D. Oon 2011 15

It was natural disruption but I was in the ferry heading

copyle% Redhuan D. Oon 2011 16

Testing Fixed Assets

The basic steps from those classes are as follows:

copyle% Redhuan D. Oon 2011 17

//10. Record necessary adjustments in new Depreciation Expense

Here i elaborate the first step:

copyle% Redhuan D. Oon 2011 18

copyle% Redhuan D. Oon 2011 19

We Asians are always followers of foreign ideas. I bet these chits

copyle% Redhuan D. Oon 2011 20

copyle% Redhuan D. Oon 2011 21

copyle% Redhuan D. Oon 2011 22

Getting Fixed Assets

copyle% Redhuan D. Oon 2011 23

Gaps in Asset Maintenance

copyle% Redhuan D. Oon 2011 24

1. Maintenance project properties (by right clicking on it in Eclipse)

Maintenance Work Order

Firstly we setup the

copyle% Redhuan D. Oon 2011 25

Then we setup the Job Standard window for an asset.

Next we define this standard job’s required resources.

copyle% Redhuan D. Oon 2011 26

copyle% Redhuan D. Oon 2011 27

copyle% Redhuan D. Oon 2011 28

Note that there is a Process Now button