Friday, 8 May 2020

ServiceNow Asset Data Load Pre checks or procedure


Pre-Checks
·         Look at the below attribute for data provided in Excel/Data sheet
Acquisition method
Asset tag
Assigned
Assigned to
Comments
Manufacturer
Cost
Cost center
Depreciation
Depreciation effective date
Disposal reason
Due
Installed
 Retired date
State
Invoice number
Managed by
Model
Model Category
Ordered
Purchased
Quantity
Request line
Resale price
Salvage value
Serial number
Stockroom
Substate
DR Option
Part Number
Room
Shared Workstation Reason
Vendor
Warranty expiration
Building
Support group
Beneficiary
Checked in
Checked out
Supported by
Order received
Department
Name
Workstation Classification
Due in
Expenditure type
GL account
Window
Justification
Lease contract
Location
Wave
Owned by
Parent
PO number
Scheduled retirement
Reserved for



·         Check for all the reference or choice field value is available in ServiceNow or Now
o   Assigned To
o   Supported By
o   Support Group
o   State
o   Sub State
o   Manufacturer
o   Model Category
o   Model
o   Location
o   DR Option
o   Name (Configuration Item)
·         Confirm that if any of the above attribute value is not available in ServiceNow, Should you create new value of it or not.
·         When you have proper data in hand start loading the data into ServiceNow using below steps
o   Create a Data load
§  System Import Set à Load Data
§  Create new Staging table to load the data
o   Create Transform Map
§  Map all the attribute from Source Table (Newly created Staging table) to target table (alm_hardware or alm_asset)
§  Select coalesces field to remove duplication
§  Select choice action properly
§  Create a transform map script if required
·         On Start
·         On Complete
·         On Before
·         On After
·         On choice Create
·         On Reject etc.
o   Run the data load
§  Select the transform map created above.

Transform used to load data in LYB ServiceNow


Post-Checks
·         Check for the below attribute whether data loaded properly or now.
o   Assigned To
o   Supported By
o   Support Group
o   State
o   Sub State
o   Manufacturer
o   Model Category
o   Model
o   Location
o   DR Option
o   Name (Configuration Item)
·         Check for the below table whether any unnecessary value created because of data load
o   User
o   Group
o   Location
o   Hardware CI
o   State Choice
o   Substate Choice etc.
·         Run Below script on alm_hardware and cmdb_ci_hardware table for duplicate CI using Serial Number

var dupRecords = [];
var gaDupCheck1 = new GlideAggregate('cmdb_ci_hardware');
gaDupCheck1.addAggregate('COUNT', 'serial_number');
gaDupCheck1.groupBy('serial_number');
gaDupCheck1.addHaving('COUNT', '>', 1);
gaDupCheck1.query();
while (gaDupCheck1.next()) {
               
    dupRecords.push(gaDupCheck1.serial_number.toString());
}
gs.print(dupRecords);

·         Delete all duplicate value created because of transform map.
·         If required use below script to delete duplicate value :  ( Run with high precautions)

var dup = new GlideAggregate(‘alm_hardware’);
dup.groupBy('serial_number');
dup.query();
while(dup.next()) {
                var dup1 = new GlideRecord('alm_ hardware’');
                dup1.addQuery('serial_number', dup.serial_number);
                dup1.query();
                dup1.next();
                while(dup1.next())
                                dup1.deleteRecord();
}
Further Reference for Data load or transform Maps.

1 comment:

  1. Thanks for such a pleasant post. This post loaded with lots of useful information. Keep it up. If you are looking for the best information and suggestions related to Property Tax Depreciation then visit AussieQS.

    ReplyDelete