Analyze Before Import

Analyzing an inbound integration package before importing is a very important step in understanding the contents of the package. An inbound integration package may contain new, modified or deleted information. Knowledge about these is helpful in avoiding the import of incompatible data and of invalid business objects with their invalid metadata and variables. This makes it possible to recreate a valid integration package free from such errors. There are three available analysis options which can run individually or in combinations of two or three.

Validate Against Schema

A type of analysis which studies the contents of the integration package by dissection, before importing to ensure that all business objects and the values on them have been defined by Asset Information Schema XML/IFSXMLSchema. This analysis neither refers to a database nor does it require having any settings defined. The entire integration package is parsed against the IFSXMLSchema to assess if there are any:

  1. Business objects unspecified by the schema.
  2. Properties of business objects, unspecified by the schema.
  3. Missing mandatory properties.
Type Of Event Example Of Error
Business objects unspecified by the schema Format warning: Stranger: Unrecognized Business Object Name!
Properties of business objects unspecified by the schema Data warning: Class (Motor) Property: 'Standard' refers to a non existing item! 
Missing mandatory properties Data Warning: Plant (Stranger Plant): Missing mandatory property: 'Description' 

Each business object is analyzed to ascertain that:

  1. Its mandatory fields have values.
  2. If its property refers to another business object, check if the latter business object exists in the integration package.

It is also possible to perform the schematic validation without logging on to IFS Asset Information Integration Manager. In the Analyze Inbound Integration Package window you can choose the xml that you want to analyze and execute this validation.

Business Object Instance Data Analyze

This analysis is between business objects in the inbound integration package and business objects in the database. It is possible to set up this analysis to display the following:

  1. Warnings - The error causing business object and its cause that cannot be imported.
  2. Modifications - Modified business objects together with its fields that received a modification.
  3. New - Any new business objects that are about to be imported.
  4. All - Warnings, modifications and new business objects.
Type Of Event Example Of Error
Warning Warning: PlantPlant - PlantPlant: Mandatory field DENOM1 is Missing!
Modification Modified: Plant Design Part- Plant Design Part [30903147] : Value for Site has been Modified
New New: Plant Class - New Plant Class [CONTROLLER] to be Imported

Document Import Warnings

Warnings will be issued if the corresponding document in the database is checked out.

Additional Validation Against Related Business Objects

This is the validation of a business object, (that has not been not exported), defined on another business object in order to check if the former business object has been defined in the database. E.g., the business object Supplier has been defined on design part. This related business object could be entered on a design part during the detail engineering phase, and the analyze feature validates that the entered supplier on the design part also exists in the supplier catalog. This then becomes a valid relation for the business object that will be imported.

Type Of Event Example Of Error
Warning Warning: Design Part [306a-205b-104c] Contains an Invalid Supplier ID : 001