Description
This method creates assets under an asset class.
Support
This method can only support creation of assets at company level.
Installation: ASP and Self host
Level | Yes or No |
|---|---|
Company Level | Yes |
Project and Shell Level | No |
Program Level | No |
Prototype
public XMLObject createAsset(String shortname, String authcode, string assetClassName, String copyFromAsset, String assetXML);
Parameters
Parameter | Description |
|---|---|
shortname | identifier of the company, company’s short name |
authcode | authentication key for the company, in text string |
assetClassName | Name of asset class (Buildings, IT Equipments etc..,) |
copyFromAsset | This can be another asset code or a template asset code. User can provide a null value if user does not want to copy from an asset or template. If user provides a value, system should first look under templates and if template does not exists then it should check under real assets |
assetXML | Content of the asset that needs to be created. This is based on Integration interface design for asset class in uDesigner. |
Return Value
See Return Values.
Sample Method
createAsset("acme", "acme_authcode", "Buildings","Buildings Temp 1","XML")
Additional Information
Same logic while creating new assets from UI will be used while creating an asset from integration. This includes validation logic, setting status of an asset, depreciation definitions etc..,
If user tries to create an asset without copying from another asset or template, then new asset will be created based on the data provided as part of web services payload. Note: No depreciation setup will be available for these newly created assets as payload does not take any depreciation setup information.
If user tries to create an asset by copying from another asset or template then new asset will be created based on the data provided as part of web services payload. Template or asset name provided as part of web services call will be used to copy depreciation setup only (depreciation data will not be copied). That means only deprecation information will be copied from the template or asset and not any data on the detail form of template.
All validations on asset detail form including required fields and user defined form validations will be honored while creating new assets through web services.
If depreciation is available for newly created assets then the depreciation schedule will be calculated, asset detail form will be updated as part of web services call.
Once asset is created, asset detail form will be in Finish Editing mode and data including depreciation information will be rolled up to asset class sheets, asset summary sheet and accounts sheet.
Data Element which is based on data definition viz.., SYS Numeric Logical Datasource, SYS Date Logical Datasource, SYS Business Process Datasource and SYS Project Cost Datasource will not be available as part of Integration.
Following data element are only available as part of createAsset
Asset Code and Asset Navigation Code: These two data elements are built automatically based on the definition
Net Book Value, Cumulative Depreciation, Current Period Depreciation and Calculations as of: Calculated based on asset depreciation setup