Documentation 2.0 en Us Integration Guide
Documentation 2.0 en Us Integration Guide
Integration guide
SE Suite 2.0
DC TE .E N 00022
Rev 16
SoftExpert Excellence Suite (SE Suite) is the most comprehensive corporate solution for integrated management
of excellence and business compliance.
SoftExpert Excellence Suite (SE Suite) offers a set of multilingual modules that are natively integrated and fully
Web-based to automate the processes required to improve and optimize the different business areas at
organizations. This boosts the quality of management, cuts operating costs and facilitates compliance with the
main market norms and regulations.
The solution also supplements and enhances the use of corporate management systems and is integrated with
main market ERPs through connectors that may be developed based on the company’s specific needs.
The information contained herein is subject to change without notice. If you find inconsistent information, please
report it in writing to our support.
The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise
noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and
events depicted in examples herein are fictitious. No association with any real company, organization, product,
domain name, e-mail address, logo, person, place, or event is intended or should be inferred.
C omplying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for
any purpose, without the express written permission of SoftExpert.
SoftExpert may have patents, patent applications, trademarks, copyrights, or other intellectual property rights
covering subject matter in this document. Except as expressly provided in any written license agreement from
SoftExpert, the furnishing of this document does not give you any license to these patents, trademarks,
copyrights, or other intellectual property.
This software and documentation may provide access to or information on content, products, and services from
third parties. SoftExpert is not responsible for and expressly disclaim all warranties of any kind with respect to
third-party content, products, and services. SoftExpert will not be responsible for any loss, costs, or damages
incurred due to your access to or use of third-party content, products, or services.
Chapter I
Introduction
This document aims at defining the technical specifications and criteria required for the integration of different
information systems with SoftExpert Excellence Suite (SE Suite).
§ Any person who needs to understand the integration architecture and its operation;
§ IT professionals (mainly an integrator or DBA) responsible for implementing the integration between a
§ IT professionals in charge of maintaining the integration architecture, who need to understand the
Integrations via the template made available in SE Suite should be executed by IT professionals knowledgeable about
web services or databases (preferably an integrator or DBA).
§ For integration via Web Services the user will need to have knowledge in the SOAP protocol, in tools construction, and
§ For integration via Database it will be necessary to manipulate the data of a particular table where the solution is
installed.
Objective
The integration architecture was designed as part of a SDK, following a standard for importing data from any
source into SE Suite, and for extracting data from the output obtained from the data import process to a given
destination.
ATTENTION
Although providing support for recent versions of third-party software packages and patches, SoftExpert has no control
over those software updates and, thus, cannot ensure compatibility with their products. In any case, contact the
supplier for product specifications and further details about compatibility.
Chapter II
Typographical conventions
This document uses the conventions described in the table below to distinguish the elements in the text.
Convention
Names of programs and selected tokens, such as command parameters and environment
Example
variables that need to be emphasized.
[Example] Elements that may be clicked in the user interface (such as buttons, for example).
Variables provided by the user and new tokens entered in the text, names of additional
Example
documents.
<Example> Variables provided by the user that replace the content between the < and > characters.
Example Examples of codes, examples, displayed or presented texts, and error messages.
Table 1.1 - Typographical conventions of this docum ent regarding the text.
# mkdir <folder_name>
This text box displays the content of the file being edited.
While using this manual, users will find different strategies used to call their attention to important information.
The images that indicate this information are displayed below:
Displays important details about a specific functionality that must be taken into consideration and/or that facilitate the use
of the system. A link will be made available if the functionality was already described elsewhere in the documentation.
Alert to indicate a functionality or action that, when not executed correctly, may harm a step of the system use.
Chapter III
Integration possibilities
1. Integration of portals and/or client legacy systems to start a workflow/process within SE Suite.
§ The integration may be carried out by using an external startup API, technically detailed in the
§ Or the SoftExpert startup Web Services may also be used. The SoftExpert Web Services are described
Other workflow actions are also released from the moment the WEB Service is used, such as activity execution,
filling in attributes and form fields, upload of attachments, etc. (Web Services online documentation
http://<domain>/se/ws/wf_ws.php).
§ For that, the client BI must access SE Suite tables directly and assemble the desired views. The data
4. Integration of client external systems to create and add several data into SE Suite.
§ For that type of demand, we make available interface tables and our own Web Services, both are
described in detail in the Integration via database and Integration via web services.
§ To do that, we have the external attributes option within the application. The details of how to
§ And, regarding the components based on SE Process, we have the external applications option, in
which the user can test external information, return some type of data, etc., either by using the Web
Service concept or even a customized application (by means of customization).
The same concept may be applied to load form field list data. In that case, there is no option for direct connection
with the external attribute, but small routines and a few connectors may be developed.
§ To do that, it is possible to use Web Service interfaces (if the external service contains them), export
to data files (TXT, CSV) for import through the external system, or then save the data directly into the
external system database.
§ And, if in the case of SE Process-based components, we have the option to configure external
applications where it is possible to configure the clients of Web Service natively (except for
authentication and architecture particularities, in which the specific client would have to be
implemented).
§ The restriction applies exclusively to the infrastructure made available for the tooling to be used. For
example, if the connection is direct between the databases, they should enable a DBLINK or be in the
same network (Dedicated VPN). If there is need for file transfer, the fileservers must be available in the
cloud, and so on.
§ The indicated orientation and architecture in these cases is the use of a Web Service.
§ May be performed by any SAP tooling (ABAP, XI, RFC, etc.), being them dependent mostly on the type
of contract the customer has. However, the practice is that implementations directly into SAP are
usually performed by the customer IT team or by SAP consultants.
The same understanding may be applied to any other ERP, i.e., the SoftExpert team must map the data
availability method of the ERP in question. From that, the methods mentioned above are directed to.
Chapter IV
The Interface data template section, displays each field as well as of the ADINTERFACE table and of the header
of the file for .xls import;
The Interface data load section, defines how the data load is done in the ADINTERFACE table;
The Definition of the XLS file structure defines how to use the .xls file, and how it should be filled in;
The Diagnosis and correction of errors section, describes how the correction of records that were not imported
successfully should be done;
The Published interface section, defines all the interfaces published in the system, and what should be filled in
each one of them;
The picture below represents the SE Suite data flow scheme. This diagram indicates possible ways of system
integration, and the flow of data after they are in the system interface (Middleware).
SE Suite makes available two operations in this architecture: 1 – Interface data import, 2 – Data output from
the operations executed during the data import. Both search for/make available data in the interface table.
Third-party information systems will only have access to this interface, preventing this information system from
interfering in the rest of the environment. No trigger should be generated in the interface, thus avoiding the
interruption of any database transaction, providing transparency to the responsibilities between SE Suite and
third-party software systems.
IMPORTANT!
All information about the data input in SE Suite will be performed through the interface made available and displayed in
this guide, not allowing the direct insertion of data into the SE Suite tables.
The ADINTERFACE table is the interface where all records from all imports are stored to be later imported.
Third-party information systems are responsible for inserting and searching for the data in this table. See
below the specifications of each field in this table.
ADINTERFACE
C DISOSYSTEM NUMERIC 10 C ode of the system which the import will be performed into.
C DSC HEDULE NUMERIC 10 C ode of the scheduling that executed the import.
Defines that only the FLFIELD01 field will be used for this
FGBLOBOPTION NUMERIC 2
import.
ADINTERFACE
ADINTERFACE
ADINTERFACE
ADINTERFACE
IMPORTANT!
§ Every record type will be saved in this table, even after the import or even if there are errors during the import;
§ What distinguishes one record from another is the system code (CDISOSYSTEM) and the import type you intend to
execute (FGOPTION);
§ The CDINTERFACE field, in addition to, being the primary and sequential key, is what defines the import sequence of
Both CDISOSYSTEM and FGOPTION, as well as the other fields related to the imports already published in SE
Suite, will be described in detail in the subsequent chapters. Each of these published imports has a different
quantity of data, both of required and complementary data.
Partners are in charge of developing and maintaining the programs responsible for loading the data into the
interface, due to specifications that depend on third-party software.
The programs that are responsible for loading the data must read the information from a source repository
(database, XLS, CSV and XML files, among others) and write this information in the ADINTERFACE interface
available in SESUITE. In the import process, users are responsible for deleting the processed records and for
treating exceptions and errors that may occur during the import through the system. Whereas in the data
output process, third-party software systems are responsible for deleting the records consumed in the
interface.
It is important to point out that the architecture does not store deleted information, either for an already
imported or a not yet imported record. Therefore, once a record is deleted from the system or directly from the
interface, there is no place in the Integration architecture to keep the deleted data.
The ADINTERFACE table may also be fed through an XLS file. For that, it is necessary to create a file with a
header containing the same fields existing in the ADINTERFACE table.
IMPORTANT!
All the fields must be placed in the header, even if not used. The fields must all be written with uppercase and follow the
order below:
CDINTERFACE, DSERROR, FGIMPORT, FGBLOBOPTION, FGOPTION, CDISOSYSTEM, QTHRINIT,
QTHRFINISH, DTEXECUTION, NRSEQUENCE, NMFIELD01, NMFIELD02, ..., NMFIELD101,
DSFIELD01, DSFIELD02, ..., DSFIELD15
The file must contain in its name the word seimport, and should be inside the C:\Inetpub\SE\web\import
file. When executing a scheduling, this folder is verified and, if there are one or more files, the integration
architecture will load the found records to the interface.
After import, the XLS file goes to the C:\Inetpub\SE\web\import\imported directory, if the data is captured
IMPORTANT!
Examples of names:
§ 20.05.seimport.xls
§ seimport.20.05.xls
§ _seimport_.xls
If the multi-database feature is being used, the domain and one more underline character must be added
before the word seimport. Examples of names for the domain www.softexpert.com:
§ 20.05.www.softexpert.com_seimport.xls
§ www.softexpert.com_seimport.20.05.xls
§ _www.softexpert.com_seimport_.xls
In addition to the XLS automatic search feature and insertion of data into the interface through the scheduling,
there is the possibility of loading the data through the system on the Import data screen (SE Configuration
Tool Import Tracking). On this screen, it is possible to work with three integration resources:
With the first, it is possible to export the data from the import tasks list through the export button, which
builds a file in the XLS format with the header containing all the interface data. Once exported, the data may
be edited and imported back into the system through the second button shown above, which imports the
data. The second resource, not only imports the data that were already in the import data list, but it also adds
new items, facilitating the import of specific data. This last one, exports a base spreadsheet that corresponds
to the correct template for file import
During the import process of the data contained in the interface table, there may be errors that usually occur
due to the existence of records with the same data in the database, or due to the absence of some data
required for that type of record.
If any error of this type has occurred, its verification may be performed through the Import tracking screen,
located in the SE Configuration component (Configuration Tool Import Tracking). On this screen, it is
possible to view the records that were, or not, successfully executed. It is possible to use the Filter by status
to filter the records and display only the ones with errors. The reason of the error is displayed in the "Error
description" column, making it possible to diagnose the problem and then fix it.
After verifying the description of the error and filtering the desired records, it is then possible to use the
"Export spreadsheet" button, located on the toolbar, to export the data set again and fix it.
All records listed in the grid will be exported. To only export records with errors, filter the data for only such records to
be displayed in the grid.
To correct them, open the generated XLS and correct the data according to the description of the error (e.g.: if
the error indicated that the record already exists, change the column that has the duplicated values). All
values in the DSERROR column will be deleted, and the ones in the FGIMPORT column will be updated to “1”.
Keep the values in the CDINTERFACE, FGOPTION, and CDISOSYSTEM columns the same, since they are used to
find the record to be replaced in the interface table.
After correcting the XLS, just use the "Import spreadsheet" button to replace the data in the ADINTERFACE
table. Note that after the file is sent to the server, the records that were updated will again be marked for
import and will be re-imported according to the Import scheduling set on the server.
For each group of items shown below, a unique identifier was created, which may be scheduled through the
scheduling screen (SE Configuration Tool Import Scheduling). This identifier is made up of the
abbreviation of the module and the abbreviation of the item to be imported.
§ Action
§ Administration
§ Storeroom
§ Asset
§ Calibration
§ SPC
§ Competence
§ Time control
§ Performance
§ Document
§ Inspection
§ Supply
§ Maintenance
§ PDM
§ Project
§ Survey
§ Waste
§ Risks
§ Test
§ Training
4.6.1 - Action
§ Data of an item:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/delete item
Import status:
1 - New;
3 - Finished;
4 - Error.
Measurable?
1- Yes;
NMFIELD05 NUMERIC 2
2- No.
Delete item
Import status:
1 - New;
3 - Finished;
4 - Error.
4.6.2 - Administration
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
18 - Delete company.
C ustomer company:
2 - No.
Supply company:
2 - No.
Manufacturing company:
2 - No.
Example:109;107.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
Default contact:
2 - No.
§ Activity data
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
22 - Delete activity.
Example of insertion/deletion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/delete
Import status:
1 - New;
3 - Finished;
4 - Error.
24 - Delete activity.
Note: Fields NMFIELD02 and NMFIELD03 - only one must be filled in.
Example of insertion/deletion:
This import template enables to add new attributes to the SE Suite components. Follow the standard
documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute type.
1 - List of values;
NMFIELD04 X TEXT 255
2 - Non-discrete;
3 - External.
List of values:
1 - Text;
2 - Numeric;
3 - Date;
NMFIELD05 X TEXT 255
5 - C urrency.
Non-discrete:
1 - Text;
2 - Numeric;
3 - Date;
4 - Memo;
5 - C urrency.
External:
1 - Text.
Selection mode.
1 - Zoom;
2 – C ombo.
1 - Multivalued
Example:109;107.
Field format:
2 - Regular expression.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
153
Attribute value.
· yyyy-mm-dd.
Example of insertion:
This import template enables to insert values to attributes already saved in SE Suite. Follow the standard
documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Supported databases:
1 - INTERBASE;
2 - MSSQL;
3 - MSSQL (ODBC );
7 - ORAC LE (ODBC );
8 - DB2 (ODBC );
9 - INFORMIX;
11 - MYSQL;
12 - POSTGRESQL;
The values accepted for the import of dates must follow one of the following standards:
§ YYYY-MM-DD
§ DD/MM/YYYY
This import template enables to associate an attribute value with a company from the SE Administration
component. Follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
The values accepted for the import of dates must follow one of the following standards:
§ YYYY-MM-DD
§ DD/MM/YYYY
§ Data of a department;
To insert each of these items, it is necessary to follow the standard documented below.
Insert department
Import status:
1 - New;
3 - Finished;
4 - Error.
Import status:
1 - New;
3 - Finished;
4 - Error.
Delete department
Import status:
1 - New;
3 - Finished;
4 - Error.
This import template enables to edit the following employee profile data:
§ Educational level;
§ Birth date;
§ Hire date;
§ Termination date;
§ Comments;
§ Address.
To edit each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - C omplete;
NMFIELD3 TEXT 255 2 - Unfinished;
The values accepted for the import of dates must follow one of the following standards:
§ YYYY-MM-DD
§ DD/MM/YYYY
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
Example:109;107.
§ Data of a position;
To insert each of these items, it is necessary to follow the standard documented below.
Insert position
Import status:
1 - New;
3 - Finished;
4 - Error.
Delete position
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Data of teams;
To insert each of these items, it is necessary to follow the standard documented below:
Insert/Edit/Delete teams
Import status:
1 – New;
3 – Finished;
4 – Error.
31 – Insert team;
FGOPTION X NUMERIC 2
32 – Edit team;
33 – Delete team.
1 – Departments;
NMFIELD04 X TEXT 255
2 – Users;
3 – Positions.
To insert each of these items, it is necessary to follow the standard documented below:
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
1 – Departments;
3 – Positions.
§ Data of a user;
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit user
Import status:
1 - New;
3 - Finished;
4 - Error.
NMFIELD01 X TEXT 255 Name used by the user to log into the system.
1 - English;
2 - Portuguese (Brazil);
5 - German;
6 - French;
7 - Romanian.
Import status:
1 - New;
3 - Finished;
4 - Error.
Default department:
2 - No.
Import status:
1 - New;
3 - Finished;
4 - Error.
Disable user
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Data of a user;
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit user
Import status:
1 - New;
3 - Finished;
4 - Error.
NMFIELD01 X TEXT 255 Name used by the user to log into the system.
1 - English;
NMFIELD04 TEXT 255
X 2 - Portuguese (Brazil);
3 - Spanish;
4 - Portuguese (Portugal);
5 - German;
6 - French;
7 - Romanian.
4.6.3 - Storeroom
§ Data of an attribute.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error;
Attribute type:
1 - List of values;
NMFIELD04 TEXT 255
X 2 - Non-discrete;
3 - External.
List of values:
1 - Text;
2 - Numeric;
NMFIELD05 X TEXT 255
3 - Date;
5 - C urrency.
Non-discrete:
1 - Text;
2 - Numeric;
3 - Date;
4 - Memo;
5 - C urrency.
External:
1 - Text.
1 - Zoom;
Accepted values:
1 - Multivalued.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Attribute value.
Use as default.
DB type:
1 – ITERBASE;
2 – MSSQL;
3 – MSSQL (ODBC );
7 – ORAC LE (ODBC );
8 – DB2 (ODBC );
9 – INFORMIX;
11 – MySQL;
12 – POSTGRESQL.
Field.
§ yyyy-mm-dd.
§ An input event.
To insert each of these items, it is necessary to follow the standard documented below.
Deletion
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Deletion:
§ An output event.
To insert each of these items, it is necessary to follow the standard documented below.
Deletion
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Deletion:
To insert each of these items, it is necessary to follow the standard documented below.
Deletion
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Deletion:
§ A saved storeroom.
To insert each of these items, it is necessary to follow the standard documented below.
Deletion
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Deletion:
§ Storeroom objects.
To insert each of these items, it is necessary to follow the standard documented below.
Deletion
Import status:
1 – New;
3 – Finished;
4 – Error;
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Attribute value.
§ yyyy-mm-dd.
Revision ID #.
Attribute value.
DSFIELD01 TEXT 4000 Mandatory information if the type of the
attribute value is MEMO.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Requester type:
1 – Department;
3 – Supplier;
4 – Process activity.
Activity ID #
NMFIELD05 TEXT 255 Note: Required only when the requester type is
process activity.
Example of Insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Addressee type:
1 – Department;
3 – Supplier;
4 – Delete.
User: user id #;
Delete - Disposal/Treatment:
disposal/treatment ID #.
Example of Insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Place type:
2 or NULL – No.
Example of Insertion:
§ Data of a storeroom.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Storeroom object:
2 – Waste;
NMFIELD04 TEXT 255
X 3 – PDM;
4 – Supply.
2 – C ustomer;
3 – Supplier.
Storeroom owner ID #.
If internal: Department ID #.
If customer: C ustomer ID #.
NMFIELD09 TEXT 255
If supplier: Supplier ID#.
Example of Insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Attribute value.
§ yyyy-mm-dd.
Revision ID #.
Attribute value.
DSFIELD01 TEXT 4000 Mandatory information if the type of the
attribute value is MEMO.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
2 or NULL – No.
2 or NULL – No.
2 or NULL – No.
2 or NULL – No.
2 or NULL – No.
2 or NULL – No.
4.6.4 - Asset
§ Data of an asset.
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete asset
Import status:
1 – New;
3 – Finished;
4 – Error;
Asset specification:
1 - Gage;
2 - Equipment;
NMFIELD05 X TEXT 255 4 - Others;
6 - Tooling;
7 – Tools;
11 – C omputer.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error;
Attribute value.
· yyyy-mm-dd.
§ Storage place.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error.
Active record
2 – No.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit
Import status:
1 – New;
3 – Finished;
4 – Error;
Plan type:
1 – Verification;
NMFIELD01 X¹ TEXT 255
2 – Preventive maintenance;
3 – C alibration.
Plan configuration:
E.g.: IDATIVO01;IDATIVO02;IDATIVO03
Date-based frequency:
2 – Disable.
Frequency type:
1 – Execution date;
NMFIELD11 X³ TEXT 255
2 – First use;
3 – Usage time.
Frequency unit:
1 – Day(s);
2 – Week(s);
NMFIELD13 X³ TEXT 255
3 – Month(s);
4 – Year(s);
5 – Working day(s).
Date visualization:
2 – Month/Year.
2 – Disable.
2 – Disable.
2 – To be started.
Example of insertion:
Example of editing:
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Team;
2 - Department;
4 - Position;
5 - User;
6 - All.
C ontrol to add:
2 - No.
C ontrol to edit:
C ontrol to delete:
2 - No.
2 - No.
C ontrol to list:
2 - No.
C ontrol to view:
2 - No.
Permission:
2 - Deny.
Access type ID #.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
Location type:
1 - Location;
NMFIELD04 TEXT 255
X 2 - User;
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Enable/disable assets
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Enable asset;
NMFIELD02 X TEXT 255
2 - Disable asset.
2 - No.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
2 - Supply.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Yes;
2 - No.
Revision control:
2 - No.
2 - Text;
3 - C ustomized.
2 - C ircular.
2 - Manual.
1 - Revisions;
NMFIELD12 TEXT 255
2 - Months;
3 - Years.
2 - Variable.
1 - AND;
2 - OR.
1 - AND;
2 - OR.
to 1):
1 - AND;
2 - OR.
1 - AND;
2 - OR.
4.6.5 - Calibration
§ Calibration data
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 – New;
3 – Finished;
4 – Error.
2 – Delete.
2 - C onditionally approved;
3 - Rejected.
1 – Approved;
2 - Rejected.
§ X 1 – Only the “C ertificate #” field is required during the deletion of the calibration activity.
Example of insertion:
Example of deletion:
Import status:
1 – New;
3 – Finished;
4 – Error.
2 – Descent point.
2 – C alibration.
C omplementary variable.
Example of editing:
Import status:
1 – New;
3 – Finished;
4 – Error.
2 – Pre-calibration.
C omplementary variable.
2 = Rejected.
2 = Rejected.
Example of insertion:
4.6.6 - SPC
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
2 - C haracteristic.
Format:
DEFEC T01:3;DEFEC T\;02:4
Import status:
1 - New;
3 - Finished;
4 - Error.
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete variable characteristic sample
Import status:
1 - New;
3 - Finished;
4 - Error.
2 – C haracteristic.
4.6.7 - Competence
§ CPTREG - Competence
§ Competencies
In order to add, edit and delete each of these items, it is necessary to follow the standard documented below.
Add/edit/delete data
Import status:
1 - New;
3 - Finished;
4 - Error;
2 - Deletion of competencies.
Example of addition/edition:
Example of deletion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Operation to be performed:
2 – Edit;
Project task ID #.
NMFIELD03 X TEXT 255
(Will only be validated if it is a project).
2 – Project;
3 – Nonproject task;
2 – Revenue;
Import type:
1 – Planning;
NMFIELD12 X NUMERIC 2
2 – Re-planning;
3 – Actual;
§ Planning:
§ Re-planning:
§ Actual:
§ Planning:
§ Re-planning:
§ Actual:
§ Planning:
§ Re-planning:
§ Actual:
§ Planning:
§ Re-planning:
§ Actual:
§ Resource values
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 – New;
3 – Finished;
4 – Error;
resource type.
Example of calendar and initial values of the cost and the billing association for the Labor resource type:
Example of calendar and initial values of the cost and the billing association for the Asset resource type:
§ Timesheet
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit timesheet
Column Required Type Precision Description
Import status:
1 – New;
3 – Finished;
4 – Error;
Hour type:
2 – Overtime;
Task type:
1 – Project task;
2 – Nonproject task;
4 – Meeting;
5 – Isolated action;
4.6.9 - Performance
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these indicators, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Indicator frequency:
1 - Yearly;
2 - Biannual;
3 - Four-month-period;
5 - Bimonthly;
6 - Monthly;
7 - Bi-weekly;
8 - Weekly;
9 - Daily;
10 - Based on event
1 - Sum;
3 - None;
4 - Manual.
1 - Yearly;
2 - Biannual;
3 - Four-month-period;
4 - Quarterly;
NMFIELD09 NUMERIC 2
5 - Bimonthly;
6 - Monthly;
7 - Bi-weekly;
8 - Weekly;
9 - Daily.
2 - No.
Example of insertion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
0 - No;
NMFIELD06 NUMERIC 2
1 - Yes (Score value) (Default);
2 - Yes (% value).
Example of insertion:
§ Scorecard indicators.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
0 - No;
NMFIELD06 NUMERIC 2
1 - Yes (Score value) (Default);
2 - Yes (% value).
View security:
2 - Restricted.
Fixed weight?
2 - No (Default).
Example of insertion:
§ Scorecard sub-indicators.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
2 - No.
Example of insertion:
This import has a particularity, the ADINTERFACE values are saved in the STINTERFACE, where the values are
validated before being inserted into the system. To verify whether the records were accepted in all processes,
access the Target value or Measurement value screen and press the Import button.
To insert each of these items, it is necessary to follow the standard documented below:
Insert/edit
Import status:
1 – New;
3 – Finished;
4 – Error.
Example of insertion/editing:
This import template enables to create a Scorecard based on a template, which must be created previously
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Scorecard type ID #.
NMFIELD04 TEXT 255 If null, it will use the scorecard type of the
scorecard template.
To insert each of these items to the spreadsheet, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
1 – Team
2 – Department
4 – Position
5 – User
6 – All
To insert each of these items to the spreadsheet, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Access type:
1 – Team
2 – Department
3 – Department/Position
4 – Position
NMFIELD02 NUMERIC 2
5 – User
6 – All
This import template enables to insert the default access security for Scorecard indicator/element. This security
is only used when the Scorecard is configured to have default security for indicator/element.
To insert each of these items to the spreadsheet, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
1 – Team
2 – Department
4 – Position
5 – User
6 – All
This import template enables to delete the default access security for Scorecard indicator/element.
To insert each of these items to the spreadsheet, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Access type:
1 – Team
2 – Department
3 – Department/Position
4 – Position
NMFIELD02 NUMERIC 2
5 – User
6 – All
4.6.10 - Document
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Access type:
2 - Department;
4 - Position;
5 - User;
6 - All.
Permission type:
1 - Allow;
NMFIELD03 TEXT 255
2 - Deny.
Permissions:
1 - Acknowledgment;
2 - Training;
3 - View;
4 - Edit;
5 - Delete;
6 - Print;
7 - Archive;
8 - Revise;
9 - Distribute copy;
NMFIELD04 TEXT 255
X 10 - C reate training;
11- C ancel;
12 - Save locally;
13 - Sign;
14 - Notification;
15 - Add comments;
16 - Evaluate applicability.
§ Data of a document
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Inherit;
NMFIELD05 TEXT 255
2 - Do not inherit.
§ Data of an attribute.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute type:
1 - List of values;
NMFIELD04 X TEXT 255
2 - Non-discrete;
3 - External.
List of values:
1 - Text;
2 - Numeric;
3 - Date;
5 - C urrency.
Non-discrete
NMFIELD05 TEXT 255
1 - Text;
2 - Numeric;
3 - Date;
4 - Memo;
5 - C urrency.
External
1 - Text.
Selection mode.
1 - Zoom;
NMFIELD06 TEXT 255
2 - C ombo.
1 - Multivalued.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error.
Attribute value.
§ yyyy-mm-dd.
Revision ID #.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute value.
Use as default.
DB type.
1 - ITERBASE
2 - MSSQL
3 - MSSQL (ODBC )
7 - ORAC LE (ODBC )
8 - DB2 (ODBC )
9 - INFORMIX
11 - MySQL
12 - POSTGRESQL
Field.
· yyyy-mm-dd.
§ Document
To insert each of these items, it is necessary to follow the standard documented below.
Cancel
Import status:
1 - New;
3 - Finished;
4 - Error;
Cancellation example:
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
0 - Uncompressed file.
NMFIELD06 TEXT 255
1 - GZ compression.
2 - ZIP compression.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ yyyy-mm-dd.
§ yyyy-mm-dd.
§ yyyy-mm-dd.
§ yyyy-mm-dd.
§ yyyy-mm-dd.
§ yyyy-mm-dd.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Team NMFIELD06
2 - Department NMFIELD07
4 - Position NMFIELD08
5 - User NMFIELD09
Revision step.
Possible values:
1 - Draft;
X TEXT 255
NMFIELD03 2 - Review;
3 - Approval;
4 - Release.
1 – Approved;
NMFIELD10 TEXT 255
2 – Rejected.
4.6.11 - Inspection
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit
Import status:
1 – New;
3 – Finished;
4 – Error.
14 – Insert;
FGOPTION X NUMERIC 2
15 – Edit;
16 – Delete.
1 – Allow;
Frequency type:
1 – Uncontrolled;
NMFIELD13 X4 TEXT 255 2 – Execution date;
Frequency unit:
1 – Days;
3 – Months;
4 – Years.
2 – No (default option).
Sample status:
1 – Blocked;
NMFIELD22 X7 TEXT 255
2 – Initial sample;
3 – Released.
2 – No (default option).
1 – Days;
3 – Months;
4 – Inspections.
Register averages/readings:
2 – Register readings.
Rule:
1 – Sampling plan;
3 – Defined size;
4 – Percentage.
Sampling plan:
1 – Simple;
NMFIELD29 X9 TEXT 255
2 – Double;
3 – Multiple.
Inspection level:
NMFIELD30 X9 TEXT 255 The available options are the same as the values
displayed on the inspection form data screen.
Work regime:
1 – Reduced;
NMFIELD31 X9 TEXT 255
2 – Normal;
3 – Tightened.
NQA:
NMFIELD32 X9 TEXT 255 The available options are the same as the values
displayed on the inspection form data screen.
2 – No (default option).
§ X 4 – Required when adding if the form object type allows the frequency to be controlled
§ X 6 – Required when adding if the form object type requires the inspection frequency to be entered
§ X 7 – Required when adding if the form object type requires the inspection frequency to be entered and the option to
control the initial sample is active
§ X 8 – Required when adding if the form object type requires the inspection frequency to be entered and the option to
control the initial sample and the validity are active.
§ X 9 – Required if the form object type requires filling out a sampling plan and the option of the sampling rule requires it
to be filled in.
Example of insertion:
Example of editing:
Example of deletion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit
Import status:
1 – New;
3 – Finished;
4 – Error.
20 – Insert characteristic;
FGOPTION X NUMERIC 2
21 – Edit characteristic;
22 – Delete characteristic.
Required:
2 – Not required.
Frequency unit:
1 – Days;
3 – Months;
4 – Inspections.
1 – Yes;
2 – No (default option).
Register averages/readings:
2 – Register readings.
Rule:
1 – Sampling plan;
3 – Defined size;
4 – Percentage.
Sampling plan:
1 – Simple;
NMFIELD09 X3 TEXT 255
2 – Double;
3 – Multiple.
Inspection level:
NMFIELD10 X3 TEXT 255 The available options are the same as the values
displayed on the inspection form data screen.
Work regime:
1 – Reduced;
NMFIELD11 X3 TEXT 255
2 – Normal;
3 – Tightened.
NQA:
NMFIELD12 X3 TEXT 255 The available options are the same as the values
displayed on the inspection form data screen.
2 – No (default option).
§ X 3 – Required if the selected sampling type option requires filling the field in.
Example of association:
Example of editing:
Example of disassociation:
To insert each of these items, it is necessary to follow the standard documented below.
Association
Import status:
1 – New;
3 – Finished;
4 – Error.
26 – Disassociate checklist.
Example of association:
Example of disassociation:
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 – New;
3 – Finished;
4 – Error.
11 – Add;
FGOPTION X NUMERIC 2 12 – Edit;
§ X 2 – Required for inspections where Object, Process, Process activity, or Supplier is part of the evaluation; otherwise,
they will be ignored.
Example of addition:
Example of editing:
Example of deletion:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete inspection qualification index
Import status:
1 – New;
3 – Finished;
4 – Error;
§ Receiving data
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete receiving
Import status:
1 – New;
3 – Finished;
4 – Error.
3 – Add;
FGOPTION X NUMERIC 2
4 – Edit;
5 – Delete.
§ X 2 – Required for inspections of Supplies, Services, and External finished products; ignored for other object types.
§ X 3 – Required, not required, or ignored, depending on the configurations set in the inspection form type.
§ X 4 – Required if the "Allow editing flow during receiving" option is checked in the inspection form, or ignored otherwise.
Example of addition:
Example of editing:
Example of deletion:
4.6.12 - Supply
This import template enables to import attributes into supply records and to determine their values.
To insert each of these items, it is necessary to follow the standard documented below:
Insert
Import status:
1 – New;
3 – Finished;
4 – Error.
§ yyyy-mm-dd.
Example:
§ Supply definition.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error.
2 – Delete supply.
NMFIELD03 X
1 TEXT 255 Supply type (ID #).
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Supply type.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error.
1 – Yes;
2 – No.
Revision control:
2 – No.
Revision template:
1 – ISO9000 based;
NMFIELD07 TEXT 255
2 – Workflow.
Route type:
1 – Fixed;
Revision ID #:
1 – Numeric;
3 – C ustomized.
C ycle:
1 – Numeric;
NMFIELD12 TEXT 255
2 – Text.
1 – Revisions;
NMFIELD14 TEXT 255
2 – Months;
3 – Years.
C hange:
1 – Text;
NMFIELD15 TEXT 255
2 – Numeric.
1 – Incremental;
NMFIELD16 TEXT 255
2 – C ircular.
1 – Automatic;
NMFIELD17 TEXT 255
2 – Manual.
1 – AND;
NMFIELD18 TEXT 255
2 – OR.
1 – AND;
NMFIELD19 TEXT 255
2 – OR.
1 – AND;
NMFIELD20 TEXT 255
2 – OR.
1 – AND;
NMFIELD21 TEXT 255
2 – OR.
2 – No.
4.6.13 - Maintenance
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete asset
Import status:
1 - New;
3 - Finished;
4 - Error.
Activity ID # (Generated
NMFIELD01 X TEXT 255
automatically if not entered).
Responsible technician:
identifier_of_attribute1=valued_of_att
ribute1;
identifier_of_attribute1=value1_of_att
ribute1,value2_of_attribute1,value3_
DSFIELD01 X3 TEXT 4000 of_attribute1.
§ X¹ - Required if the "Start date", "Start time" and/or "Actual percentage" field(s) is(are) filled in
Example of addition:
To insert each of these items, it is necessary to follow the standard documented below.
Insert Reading
Import status:
1 – New;
3 – Finished;
4 – Error;
Reading value.
X¹ - Required if the action is New meter reading. Not required if the action is New meter restart.
To insert each of these items, it is necessary to follow the standard documented below.
Insert Reading
Import status:
1 – New;
3 – Finished;
4 – Error;
If it is a subjective variable:
Reading value.
4.6.14 - PDM
§ ITCARTPAT - Import of the asset type association with the item characteristics
This import template enables to import attributes into the item records and to determine their values.
To insert each of these items, it is necessary to follow the standard documented below:
Import status:
1 – New;
3 – Finished;
4 – Error.
Attribute value.
§ yyyy-mm-dd.
Attribute value.
DSFIELD01 TEXT 4000 Required information if the type of the
attribute value is MEMO
Example:
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
2 - Supply.
This import template enables to insert and/or edit attribute type characteristics.
To insert each of these items, it is necessary to follow the standard documented below:
Import status:
1 – New;
3 – Finished;
4 – Error.
15 – Only inserts;
16 – Only edits;
FGOPTION X NUMERIC 2
17 – Insert and, if there is already a
record with the same ID #, edits the
existing record.
Special characteristic:
2 – No.
Example:
This import template enables to associate the asset type with the characteristic records in the item.
To insert each of these items, it is necessary to follow the standard documented below:
ITCARTPAT – Import of the asset type association with the item characteristics
Import status:
1 – New;
3 – Finished;
4 – Error.
This import template enables to insert and/or edit variable type characteristics:
To insert each of these items, it is necessary to follow the standard documented below:
Import status:
1 – New;
3 – Finished;
4 – Error.
18 – Only inserts;
19 – Only edits;
FGOPTION X NUMERIC 2
20 – Insert and, if there is already a
record with the same ID #, edits the
existing record.
Special characteristic:
2 – No.
Limits:
0 – Bilateral;
NMFIELD10 X TEXT 255
1 – Unilateral up;
2 – Unilateral down.
Example:
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
X 4 - Field required if “C ompany ID” and/or “C ompany name” are empty (valid also for deletion).
Import status:
1 - New;
3 - Finished;
4 - Error.
Example:
§ Data of an item:
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit/delete item
Import status:
1 - New;
3 - Finished;
4 - Error.
2 - Delete item.
Physical state:
1 – Solid;
3 – Gas;
4 – Sludge.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
7 – Insert/Edit association of
FGOPTION X NUMERIC 2 manufacturers with items;
X 4 - Field required if “C ompany ID” and/or “C ompany name” are empty. (also valid for deletion).
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Team;
2 - Department;
4 - Position;
5 - User;
6 - All.
C ontrol to add:
2 - No.
C ontrol to edit:
C ontrol to delete:
2 - No.
2 - No.
C ontrol to list:
2 - No.
C ontrol to view:
2 - No.
Permission:
2 - Deny.
Access type ID #.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
1 - Day;
3 - Month;
4 - Year.
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 - New;
3 - Finished;
4 - Error.
1 - Yes;
2 - No.
Revision control:
2 - No.
2 - Text;
3 - C ustomized.
2 - C ircular.
2 - Manual.
2 - Months;
3 - Years.
2 - Variable.
1 - AND;
2 - OR.
1 - AND;
2 - OR.
1 - AND;
2 - OR.
1 - AND;
2 - OR.
Watermark:
2 - No.
2 - No.
File type:
1 - Simple;
NMFIELD20 X TEXT 255
2 - Multiple;
3 - C omplex.
4.6.15 - Project
Insert
Operation to be performed:
2 - Edit
Project task ID #.
X TEXT 255
NMFIELD03 (Will only be validated if it is a project).
1 - Project task;
NMFIELD04 X NUMERIC 2
2 - Project;
3 - Nonproject task;
4 - Program;
Import type:
1 - Planning;
NMFIELD12 X NUMERIC 2
2 - Re-planning;
3 - Actual.
The values accepted for the import of dates must follow one of the following standards:
§ YYYY-MM-DD
§ DD/MM/YYYY
Planning:
Re-planning:
Actual:
Planning:
Re-planning:
Actual:
Planning:
Re-planning:
Actual:
Planning:
Re-planning:
Actual:
§ Resource values;
To insert each of these items, it is necessary to follow the standard documented below.
Import status:
1 – New;
3 – Finished;
4 – Error.
Calendar association and initial values of the cost and the billing for the Labor resource type:
Association of the calendar and initial value of the cost and the billing for the Asset resource type:
§ Timesheet;
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit timesheet
Import status:
1 - New;
3 - Finished;
4 - Error.
Hour type:
2 - Overtime.
Task type:
1 - Project task;
2 - Nonproject task;
4 - Meeting;
5 - Isolated action;
4.6.16 - Survey
§ Guest respondents who will be added to the survey. The survey must be previously created.
To insert each of these respondents, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
FGIMPORT X NUMERIC 2 2 – In progress;
3 – Finished;
4 – Error;
4.6.17 - Waste
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute value.
§ yyyy-mm-dd.
Revision ID #.
§ Data of an attribute.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute type:
1 - List of values;
NMFIELD04 X TEXT 255
2 - Non-discrete;
3 - External.
List of values:
1 - Text;
2 - Numeric;
3 - Date;
5 - C urrency.
Non-discrete:
NMFIELD05 TEXT 255
1 - Text;
2 - Numeric;
3 - Date;
4 - Memo;
5 - C urrency.
External:
1 - Text.
Selection mode.
1 - Zoom;
NMFIELD06 TEXT 255
2 - C ombo.
1 - Multivalued.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute value.
· yyyy-mm-dd.
Revision ID #.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Attribute value.
Use as default.
DB type.
1 - ITERBASE;
2 - MSSQL;
3 - MSSQL (ODBC );
7 - ORAC LE (ODBC );
8 - DB2 (ODBC );
9 - INFORMIX;
11 - MySQL;
12 - POSTGRESQL.
Field.
· yyyy-mm-dd.
4.6.18 - Risks
§ RISCONSEQUENCE – Consequence
§ RISCONTROL – Control
§ RISITEM – Element
§ RISOBJECTIVE – Objective
§ RISRISK – Risk
§ RISTREATMENT – Treatment
§ Values to attributes of a control. To insert more than one value into a multivalued attribute, repeat all data
To insert each of these respondents, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Attribute value
§ dd/mm/yyyy;
NMFIELD03 TEXT 255
§ dd/mm/yyyy;
§ hhhh:mm.
X 1 - The NMFIELD03 column is mandatory for all attributes, EXC EPT the ones of the Memo type, where the DSFIELD01
column should be filled in.
§ Values to attributes of a risk. To insert more than one value into a multivalued attribute, add another row
with the same data and only change the value of the attribute (NMFIELD03).
To insert each of these respondents, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
FGIMPORT X NUMERIC 2 2 – In progress;
3 – Finished;
4 – Error;
Attribute value
§ dd/mm/yyyy;
NMFIELD03 TEXT 255
§ dd/mm/yyyy;
§ hhhh:mm.
X 1 - The NMFIELD03 column is mandatory for all attributes, EXC EPT the ones of the Memo type, where the DSFIELD01
column should be filled in.
§ Best practices.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Consequences.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Consequence types.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Controls.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Implementation:
1 – Not implemented;
NMFIELD06 NUMERIC 2
2 – Partly implemented;
3 – C ompletely implemented;
Relevant:
2 – No;
Automation type:
1 – Automatic;
NMFIELD09 NUMERIC 2
2 – Semiautomatic;
2 – Manual;
C ontrol characteristic:
2 – Preventive;
Automation:
1 – Workflow;
NMFIELD11 NUMERIC 2
2 - Survey;
3 – Test;
Process ID #
NMFIELD12 TEXT 50 (It will only be considered if the control is
automated by Workflow)
Survey form ID #
NMFIELD13 TEXT 50 (It will only be considered if the control is
automated by Survey)
Test form ID #
NMFIELD14 TEXT 50 (It will only be considered if the control is
automated by Test)
Procedure ID # (Document)
NMFIELD15 TEXT 50 (It will only be considered if the control is
automated)
§ Control types.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Elements.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Element types.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Objectives.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Objective type.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Risks.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
Risk classification:
2 – Opportunity;
§ Risk types.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Risk sources.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Treatments.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
§ Treatment types.
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 - New;
3 - Finished;
4 - Error.
4.6.19 - Test
§ Guest respondents who will be added to the test. The test must be created beforehand.
To insert each of these respondents, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Example of Insertion:
4.6.20 - Training
To insert each of these items, it is necessary to follow the standard documented below.
Insert/edit
Import status:
1 – New;
FGIMPORT X NUMERIC 2 2 – In progress;
3 – Finished;
4 – Error;
129
Example:
§ Trainings
To insert each of these items, it is necessary to follow the standard documented below.
Insert
Import status:
1 – New;
3 – Finished;
4 – Error;
Example:
Chapter V
The Published Web services define all the Web Services published in the system, and what should be filled in
each one of them. It also contains an example of a client using the Java language.
IMPORTANT!
§ The use of integration via web services is not recommended to load large volumes of data.
§ It is recommended the creation of a specific user in the SE Suite to perform the integration via web services. This user
must have a license "Manager", it should not be synchronized with the AD and should not be used to access the
system on a daily basis, as it should be for the exclusive use for the integrations. That way it simplifies both the
management of the access permissions of that user to the integrations made available and the maintenance of the
history of performed integrations, which may be extracted by observing the records created by that user.
As an alternative for system integration, SoftExpert makes available several integration interfaces, following
the specification for SOAP Web Services. All services available in SE Suite are described in detail in this
document, providing knowledge and enabling the creation of integrations by third parties.
To provide ever greater aid in the creation of integrations, two JAVA classes are made available for each
service, one for service request and another one for service return, using Apache Axis 2 library. The path of the
classes for view is detailed in each service.
For authentication of Web Services Java or PHP, will be used the same resources made available by SE Suite for
login. Such authentication will be made through a servlet made available for that end, which will also be
responsible for redirecting the call to the final destination, the web service.
The component used to communicate with the Web services is compatible with SOAP 1.2.
Must make the request to webserviceproxy passing on the header of the request Authorization parameter,
containing the word value Basic, the value " " (blank space) and the user login and the password separated
by the ":" (two dots) separator in the base64:
The SE Suite default domain is "SE Suite". However, if using authentication via AD, the domain ID # must be used -
which is the same domain entered in the authentication server configuration in SE Configuration.
Score: For the draft of the php file of connection, it is necessary to insert through a tag location the WSDL
address for the connection as in the example below:
// WSDL URL
$wsdl = "http://$server/se/ws/dc_ws.php?wsdl";
$location = "http://$server/softexpert/webserviceproxy/se/ws/contnet.php";
This section will display the published Web Services. See the following sections:
§ Administration
§ Asset
§ Calibration
§ Document
§ Generic
§ Incident
§ Inspection
§ Maintenance
§ PDM
§ Performance
§ Physical file
§ Problem
§ Project
§ Request
§ SPC
§ Supply
§ Time control
§ Workflow
5.2.1 - Administration
Web Services
This section displays the interfaces available for SE Administration. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
Method Description
5.2.1.1 - addAttribProfileValue
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\AddAttribProfileValueRequestType.java
Return web\wwwroot\ws\java\admin\AddAttribProfileValueResponseType.java
Request
ID # Required Description
IDUSER X Employee ID #.
NMATTRIBUTE X Attribute ID #
Attribute value.
§ yyyy-mm-dd.
X 1 - Required when the attribute type is MEMO and the attribute type is INDETERMINATE.
Return
ID # Description
SUC C ESS: 1.
return
Failure: message describing the error.
5.2.1.2 - AddAttribute
§ Attribute data
To insert each of these items, it is necessary to follow the standard documented below:
Java class
Request web\wwwroot\ws\java\admin\AddAttributeRequestType.java
Return web\wwwroot\ws\java\admin\AddAttributeResponseType.java
Request
ID # Required Description
IDATTRIBUTE X Attribute ID #.
IDUSER X User ID #.
DSMASK Mask
Return
ID # Description
5.2.1.3 - addAttributeValue
§ Attribute values
To insert each of these items, it is necessary to follow the standard documented below
Java class
Request web\wwwroot\ws\java\admin\AddAttribValueRequestType.java
Return web\wwwroot\ws\java\admin\AddAttribValueResponseType.java
Request
ID # Required Description
IDATTRIBUTE X Attribute ID #.
IDUSER X User ID #.
Return
ID # Description
5.2.1.4 - AddCompany
§ Data of companies;
To insert each of these items, it is necessary to follow the standard documented below.
This method enables to associate attribute values with companies. To insert each of these items, it is
necessary to follow the standard documented below:
Java class
Request web\wwwroot\ws\java\admin\AddCompanyRequestType.java
Return web\wwwroot\ws\java\admin\AddCompanyResponseType.java
Request
ID # Required Description
dsaddress Address.
nmcity C ity.
idstate State.
nmcountry C ountry.
idphone Phone #.
idfax FAX #.
dscompany Description.
Return
ID # Description
5.2.1.5 - AddCompContact
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\AddCompContactRequestType.java
Return web\wwwroot\ws\java\admin\AddCompContactResponseType.java
Request
ID # Required Description
NMDEPARTMENT Department.
NMPOSITION Position.
IDPHONE Phone #.
IDFAX Fax #.
NMEMAIL E-mail.
Return
ID # Description
5.2.1.6 - AddMeasUnity
To insert each of these items, it is necessary to follow the standard documented below:
Java class
Request web\wwwroot\ws\java\admin\AddMeasUnityRequestType.java
Return web\wwwroot\ws\java\admin\AddMeasUnityResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.1.7 - AddUserDepartment
This method enables to add a relationship between user, department and position. For this addition, it is
necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\AddUserDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\AddUserDepartmentResponseType.java
Request
ID # Required Description
ID X User ID number
IDAREA X Department ID #.
IDFUNC X Position ID #.
Return
ID # Description
5.2.1.8 - ChangePositionStatus
This method enables to edit the status of a position from disabled to enabled and vice versa. For this
operation, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\ChangePositionStatusRequestType.java
Return web\wwwroot\ws\java\admin\ChangePositionStatusResponseType.java
Request
ID # Required Description
ID X Position ID #
Return
ID # Description
5.2.1.9 - compAtribAssoc
This method enables to associate attribute values with companies. To insert each of these items, it is
necessary to follow the standard documented below:
Java class
Request web\wwwroot\ws\java\admin\CompAtribAssocRequestType.java
Return web\wwwroot\ws\java\admin\CompAtribAssocResponseType.java
Request
ID # Required Description
IDATTRIBUTE X Attribute ID #
Return
ID # Description
5.2.1.10 - DeleteCompany
This method enables to delete companies. To delete each of these items, it is necessary to follow the standard
documented below.
Java class
Request web\wwwroot\ws\java\admin\DeleteCompanyRequestType.java
Return web\wwwroot\ws\java\admin\DeleteCompanyResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.1.11 - DeleteCompContact
This method enables to delete company contacts. To delete each of these items, it is necessary to follow the
standard documented below.
Java class
Request web\wwwroot\ws\java\admin\DeleteCompContactRequestType.java
Return web\wwwroot\ws\java\admin\DeleteCompContactResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.1.12 - DeleteDepartment
This method enables to delete a department. To delete it, it is necessary to follow the standard documented
below.
Java class
Request web\wwwroot\ws\java\admin\DeleteDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\DeleteDepartmentResponseType.java
Request
ID # Required Description
ID X Department ID #
Return
ID # Description
5.2.1.13 - DeleteMeasUnity
This method enables to delete measurement units. To delete each of these items, it is necessary to follow the
standard documented below.
Java class
Request web\wwwroot\ws\java\admin\DeleteMeasUnityRequestType.java
Return web\wwwroot\ws\java\admin\DeleteMeasUnityResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.1.14 - DeleteUser
This method enables to delete a user. To delete it, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\DeleteUserRequestType.java
Return web\wwwroot\ws\java\admin\DeleteUserResponseType.java
Request
ID # Required Description
ID X User ID number
Return
ID # Description
5.2.1.15 - DeleteUserAcessGroup
This method enables to delete a relationship between the user and access group. For this deletion, it is
necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\admin\DeleteUserDepartmentAcessGroupRequestType.jav
Request
a
Return web\wwwroot\ws\java\admin\DeleteUserAcessGroupResponseType.java
Request
ID # Required Description
ID X User ID #.
Return
ID # Description
5.2.1.16 - DeleteUserDepartment
This method enables to delete a relationship between the user, department, and position. For this deletion, it
is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\DeleteUserDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\DeleteUserDepartmentResponseType.java
Request
ID # Required Description
ID X User ID #.
IDAREA X Department ID #.
IDFUNC X Position ID #.
Return
ID # Description
5.2.1.17 - deleteUserLeader
This method enables to delete the leader associated with a user. To use it, it is necessary to follow the
standard documented below.
Java class
Return web\wwwroot\ws\java\admin\DeleteUserLeaderResponseType.java
Request
ID # Required Description
ID X User ID number
Return
ID # Description
5.2.1.18 - disableUser
This method enables to disable/enable a user. To use it, it is necessary to follow the standard documented
below.
Java class
Request web\wwwroot\ws\java\admin\DisableUserRequestType.java
Return web\wwwroot\ws\java\admin\DisableUserResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.1.19 - EditDepartment
This method enables to edit the data of a department. To edit these data, it is necessary to follow the
standard documented below.
Java class
Request web\wwwroot\ws\java\admin\EditDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\EditDepartmentResponseType.java
Request
ID # Required Description
ID X Department ID #
Return
ID # Description
5.2.1.20 - EditUser
This method enables to edit the data of a user. To edit it, it is necessary to follow the standard documented
below.
Java class
Request web\wwwroot\ws\java\admin\EditUserRequestType.java
Return web\wwwroot\ws\java\admin\EditUserResponseType.java
Request
ID # Required Description
ID X User ID number
C DLEADER Leader ID #.
Return
ID # Description
5.2.1.21 - editUserDepartment
This method enables to edit the relationship between the user, department, and position associated with a
user. If the user already has a default department, it will be replaced and the new one will be considered the
default. To use it, it is necessary to follow the standard documented below
Java class
Request web\wwwroot\ws\java\admin\EditUserDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\EditUserDepartmentResponseType.java
Request
ID # Required Description
ID X User ID number
IDAREA X Department ID #.
IDFUNC X Position ID #.
Return
ID # Description
5.2.1.22 - getAttribData
This method enables to search for the data of an attribute. To use it, it is necessary to follow the standard
documented below.
Java class
Request web\wwwroot\ws\java\admin\GetAttribDataRequestType.java
Return web\wwwroot\ws\java\admin\GetAttribDataResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: An array should be returned with the following attribute information:
5.2.1.23 - NewDepartment
This method enables to insert the data of a department. For this addition, it is necessary to follow the
standard documented below.
Java class
Request web\wwwroot\ws\java\admin\NewDepartmentRequestType.java
Return web\wwwroot\ws\java\admin\NewDepartmentResponseType.java
Request
ID # Required Description
ID X Department ID #
Return
ID # Description
5.2.1.24 - NewPosition/EditPosition
This method enables to insert/edit the data of a position. For this insertion/editing, it is necessary to follow the
standard documented below.
Java class
web\wwwroot\ws\java\admin\NewPositionRequestType.java
Request
web\wwwroot\ws\java\admin\EditPositionRequestType.java
web\wwwroot\ws\java\admin\NewPositionResponseType.java
Return
web\wwwroot\ws\java\admin\EditPositionResponseType.java
Request
ID # Required Description
ID X Position ID #.
Return
ID # Description
5.2.1.25 - NewUser
§ Data of a user;
If the user already exists and the department being entered is different from the one the user is already
associated with, the new department will be associated and considered as the default.
If the user already exists and a field is changed with the same department and function already registered,
the system will return an error informing that the user is already being used by this department and function.
To perform an audition, it should be informed in white the IDAREA and IDFUNC identifiers. If the objective is to
change the department and function, IDARE and IDFUNC can be informed so that the system can make this
change.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\admin\NewUserRequestType.java
Return web\wwwroot\ws\java\admin\NewUserResponseType.java
Request
ID # Required Description
IDAREA Department ID #.
IDFUNC Position ID #.
C DLEADER Leader ID #.
Return
ID # Description
5.2.1.26 - updateEmployeeProfile
§ Educational level;
§ Birth date;
§ Hire date;
§ Termination date;
§ Comments;
§ Address.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web/wwwroot/ws/java/administration/UpdateEmployeeProfileRequestType.jav
Request
a
web/wwwroot/ws/java/administration/UpdateEmployeeProfileResponseType.ja
Return
va
Request
ID # Required Description
1 - C omplete;
FGEDULEVELSTATUS
2 - Unfinished;
DSADDRESS Address
DSOBS C omments
Return
ID # Description
SUC C ESS: 1
return
Failure: Message describing the error.
The values accepted for the import of dates must follow one of the following standards:
§ YYYY-MM-DD
§ DD/MM/YYYY
5.2.2 - Asset
Web Services
This section displays the interfaces available for SE Asset. To insert each of these items, it will be necessary to
follow the standard documented in the upcoming sections.
Method Description
5.2.2.1 - del_objectType
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Del_objectTypeRequestType.java
Return web\wwwroot\ws\java\asset\Del_objectTypeResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.2 - delete_assetConfSite
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Delete_assetConfSiteRequestType.java
Return web\wwwroot\ws\java\asset\Delete_assetConfSiteResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.3 - import_asset
§ Data of an asset;
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_assetRequestType.java
Return web\wwwroot\ws\java\asset\Import_assetResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
Asset specification:
1 - Gage;
2 - Equipment;
FGAPPLIC ATION X 4 - Others;
6 - Tooling;
7 – Tools;
11 – C omputer.
IDMODEL Template.
§ For date fields, the value must have the format “Y-
MD”(Year-Month-Day).
DSOBSERVATION C omments
Return
ID # Description
5.2.2.4 - import_asset_oee
Java class
Request web\wwwroot\ws\java\asset\Import_asset_oeeRequestType.java
Return web\wwwroot\ws\java\asset\Import_asset_oeeResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.5 - import_asset_site
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_asset_siteRequestType.java
Return web\wwwroot\ws\java\asset\Import_asset_siteResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
Location type:
1 - Location,
TYPE X
2 - User,
3 - Location/User
USER X1 User ID #.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.6 - import_asset_state
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_asset_stateRequestType.java
Return web\wwwroot\ws\java\asset\Import_asset_stateResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
DSOBSERVATION C omments
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.7 - import_asset_status
§ Status of an asset;
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_asset_statusRequestType
Return web\wwwroot\ws\java\asset\Import_asset_statusResponseType
Request
ID # Required Description
IDOBJEC T X Asset ID #
Asset status;
FGASSTATUS X 1 – Enable;
2 – Disable.
RESERVE X 1 – Yes;
2 – No.
DSJUSTIFY X Explanation
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.8 - import_asset_structure_insert_update
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\asset\Import_asset_structure_insert_updateRequestTy
Request
pe.java
web\wwwroot\ws\java\asset\Import_asset_structure_insert_updateResponseT
Return
ype.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
IDREVISION X Revision ID #
VLQUANTITY X Quantity
2 - Supply.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.9 - import_assetConfSite
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_assetConfSiteRequestType.java
Return web\wwwroot\ws\java\asset\Import_assetConfSiteResponseType.java
Request
ID # Required Description
1 - Enabled
FGENABLED X
2 - Disabled
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.10 - import_attrib_assoc
To associate the attributes successfully, it is necessary follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_attrib_assocRequestType.java
Return web\wwwroot\ws\java\asset\Import_attrib_assocResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #.
IDATTRIBUTE X Attribute ID #
Attribute value.
Defaults for the input of date type data:
VALUE X
- dd/mm/yyyy;
- yyyy-mm-dd.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.11 - import_del_asset
§ Data of an asset;
To delete each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_del_assetRequestType.java
Return web\wwwroot\ws\java\asset\Import_del_assetResponseType.java
Request
ID # Required Description
IDBOJEC T X Asset ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.12 - import_del_asset_site
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_del_asset_siteRequestType.java
Return web\wwwroot\ws\java\asset\Import_del_asset_siteResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.13 - import_del_asset_state
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_del_asset_stateRequestType.java
Return web\wwwroot\ws\java\asset\Import_del_asset_stateResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.14 - Import_del_asset_structure
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_asset_del_structureRequestType.java
Return web\wwwroot\ws\java\asset\Import_asset_del_structureResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
IDREVISION X Revision ID #
2 - Supply.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.15 - import_objectSecurity
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_objectSecurityRequestType.java
Return web\wwwroot\ws\java\asset\Import_objectSecurityResponseType.java
Request
ID # Required Description
1 - Group of users,
2 - Department,
AC C ESSTYPE X 3 - Department/Position,
4 - Position,
5 - User,
6 - All
Permission type:
PERMISSION X 1 - Allow,
2 - Deny
Access type ID #.
IDAC C ESSTYPE X Example: If the type is by user, it will be the user ID. If the
type is by department, it will be the department ID #.
C ontrol to add:
INSERT X1 1 - Yes,
2 - No
C ontrol to edit:
EDIT X1 1 - Yes,
2 - No
C ontrol to delete:
DELETE X1 1 - Yes,
2 - No
Security control:
2 - No
Listing control:
LIST X1 1 - Yes,
2 - No
View control:
VIEW X1 1 - Yes,
2 - No
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.16 - import_objectType
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\Import_objectTypeRequestType.java
Return web\wwwroot\ws\java\asset\Import_objectTypeResponseType.java
Request
ID # Required Description
2 - No
2 - No
IDMASK Mask ID #
Revision ID # type:
1 - Text
FGEDITID 2 - Numeric
3 - C ustomized
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.2.17 - importPlanActivity
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\asset\ImportPlanActivityRequestType.java
Return web\wwwroot\ws\java\asset\ImportPlanActivityRequestType.java
Request
ID # Required Description
Action option:
FGOPTION X 21 – Add;
22 – Edit;
Plan type:
1 – Verification;
FGPLANTYPE X¹
2 – Preventive maintenance;
3 – C alibration.
Plan configuration:
E.g.: IDATIVO01;IDATIVO02;IDATIVO03
Date-based frequency:
FGDATEFREQUENC Y
1 – Enable;
2 – Disable.
Frequency type:
1 – Execution date;
FGFREQTYPE X³
2 – First use;
3 – Usage time.
QTFREQUENC E X³ Frequency
Frequency unit:
1 – Day(s);
2 – Week(s);
FGFREQUNIT X³
3 – Month(s);
4 – Year(s);
5 – Working day(s).
Date visualization:
FGDATEVIEW X³ 1 – Month/Day/Year;
2 – Month/Year.
FGMETERFREQUENC Y 1 – Enable;
2 – Disable.
VLMETERFREQUENC Y x4 Frequency
2 – Disable.
FGAUTOSTATUS x5 1 – Planning;
2 – To be started.
§ X²: Required when inserting if the plan configuration is copy of (FGPLANC ONF = 2).
§ X5: Required if the option to create an activity automatically is enabled (FGAUTOC REATE = 1).
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.3 - Calibration
Web Services
This section displays the interfaces available for SE Calibration. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.3.1 - import_calibration
§ Data of a calibration;
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\calibration\Import_calibrationRequestType.java
Return web\wwwroot\ws\java\calibration\Import_calibrationResponseType.java
Request
ID # Required Description
Responsibility:
RESP X § Internal service center: User ID
§ Third-party service center: Name
C ALRESULT 1 - Approved;
2 - C onditionally approved;
3 - Rejected;
1 - Approved;
2 - Rejected;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.3.2 - import_del_calibration
§ Data of a calibration;
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\calibration\Import_del_calibrationRequestType.java
Return web\wwwroot\ws\java\calibration\Import_del_calibrationResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.3.3 - import_point
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\calibration\Import_pointRequestType.java
Return web\wwwroot\ws\java\calibration\Import_pointResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
FGUPORDOWN X1 1- Rising
2- Descending
TYPE_VALUE X1 1- C alibration
2- Pre-calibration
Additional variable.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.3.4 - import_table
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\calibration\Import_tableRequestType.java
Return web\wwwroot\ws\java\calibration\Import_tableResponseType.java
Request
ID # Required Description
IDOBJEC T X Asset ID #
TYPE_VALUE X 1- C alibration
2- Pre-calibration
Additional variable.
RESULT 1 - Approved;
2 - Rejected;
RESULTDI 1 - Approved;
2 - Rejected;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.4 - Document
Web Services
This section displays the interfaces available for SE Document. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.4.1 - cancelDocument
This method enables to cancel a document. To use it, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/CancelDocumentRequestType.java
Return web/wwwroot/ws/java/document/CancelDocumentResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.4.2 - checkAccessPermission
This method enables to verify whether the user has permission to the document. To use it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/CheckAccessPermissionRequestType.java
Return web/wwwroot/ws/java/document/CheckAccessPermissionResponseType.java
Request
ID # Required Description
IDUSER X User ID #.
Permission type:
1 Edit;
2 Delete;
3 Revise;
4 Acknowledgment;
5 Distribute copy;
6 View;
7 C ancel;
PERMISSIONSTYPE X 8 Archive;
9 Print;
10 Training;
11 C reate training;
12 Save locally;
13 Sign;
14 Notification;
15 Add comment;
16 Evaluate applicability.
Return
ID # Description
5.2.4.3 - deleteAccessPermission
This method enables to remove the access permission to a specific document. To use it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/DeleteAccessPermissionRequestType.java
Return web/wwwroot/ws/java/document/DeleteAccessPermissionResponseType.java
Request
ID # Required Description
IDUSER X User ID #.
User type:
§ 1 User;
§ 2 Department;
USERTYPE X § 3 Position;
§ 4 Department/Position;
§ 5 Team;
§ 6 All.
Return
ID # Description
5.2.4.4 - deleteDocument
This method enables to delete a document. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/DeleteDocumentRequestType.java
Return web/wwwroot/ws/java/document/DeleteDocumentResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.4.5 - deleteRevision
This method enables to delete a specific revision of the document. To use it, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/document/DeleteRevisionRequestType.java
Return web/wwwroot/ws/java/document/DeleteRevisionResponseType.java
Request
ID # Required Description
IDREVISION X Revision ID #.
Return
ID # Description
5.2.4.6 - downloadEletronicFile
This method enables to download an electronic file. To use it, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/document/DownloadEletronicFileRequestType.java
Return web/wwwroot/ws/java/document/DownloadEletronicFileResponseType.java
Request
ID # Required Description
IDREVISION Revision ID #
Return
ID # Description
5.2.4.7 - editDocument
This method enables to edit a document. To use it, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/EditDocumentRequestType.java
Return web/wwwroot/ws/java/document/EditDocumentResponseType.java
Request
ID # Required Description
IDREVISION Revision ID #
Return
ID # Description
5.2.4.8 - getKeyWords
This method enables to search for keywords. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/GetKeyWordsRequestType.java
Return web/wwwroot/ws/java/document/GetKeyWordsResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.4.9 - getKeyWordsData
This method enables to search for keywords. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/GetKeyWordsDataRequestType.java
Return web/wwwroot/ws/java/document/GetKeyWordsDataResponseType.java
Request
ID # Required Description
Return
ID # Description
§ IDKEYWORD Keyword;
5.2.4.10 - listAccessPermission
This method enables to verify the access types the user has in the document. To use it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/ListAccessPermissionRequestType.java
Return web/wwwroot/ws/java/document/ListAccessPermissionResponseType.java
Request
ID # Required Description
IDUSER X User ID #.
Return
ID # Description
§ 1 Edit;
§ 2 Delete;
§ 3 Revise;
§ 4 Acknowledgment;
§ 5 Distribute copy;
§ 6 View;
§ 7 C ancel;
§ 8 Archive;
return
§ 9 Print;
§ 10 Training;
§ 11 C reate training;
§ 12 Save locally;
§ 13 Sign;
§ 14 Notification;
§ 15 Add comment;
§ 16 Evaluate applicability.
5.2.4.11 - listPendencyDocument
This method enables to list the pending documents in the draft, review, approval, or release steps of a
determined user. To use it, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/ListPendencyDocumentRequestType.java
Return web/wwwroot/ws/java/document/ListPendencyDocumentResponseType.java
Request
ID # Required Description
IDUSER X User ID #.
Return
ID # Description
5.2.4.12 - newAccessPermission
This method enables to add access permission to a determined document. To use it, it is necessary to follow
the standard documented below.
Java class
Request web/wwwroot/ws/java/document/NewAccessPermissionRequestType.java
Return web/wwwroot/ws/java/document/NewAccessPermissionResponseType.java
Request
ID # Required Description
IDUSER X User/department/position ID #.
User type:
§ 1 User;
§ 2 Department;
USERTYPE X § 3 Position;
§ 4 Department/Position;
§ 5 Team;
§ 6 All.
Permission type:
§ 1 Edit;
§ 2 Delete;
§ 3 Revise;
§ 4 Acknowledgment;
§ 5 Distribute copy;
§ 6 View;
§ 7 C ancel;
PERMISSION X § 8 Archive;
§ 9 Print;
§ 10 Training;
§ 11 C reate training;
§ 12 Save locally;
§ 13 Sign;
§ 14 Notification;
§ 15 Add comment;
§ 16 Evaluate applicability.
E.g.: 1,2,3
Action type:
PERMISSIONTYPE X § 1 Allow;
§ 2 Deny.
Return
ID # Description
5.2.4.13 - newDocument
This method enables to create a document. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/NewDocumentRequestType.java
Return web/wwwroot/ws/java/document/NewDocumentResponseType.java
Request
ID # Required Description
Document attributes.
Example:
identifier_of_attribute1=value_of_attribute1;
identifier_of_attribute2=value_of_attribute2;
identifier_of_attribute3=value_of_attribute3.
ATTRIBUTES
Example with a multivalued attribute:
identifier_of_attribute1=value1_of_attribute1,value2_of_att
ribute1,value3_of_attribute1.
Revision participants:
§ 1 User;
§ 2 Department;
§ 3 Position;
§ 4 Department/Position;
§ 5 Team;
§ 1-Draft;
§ 2-Review;
§ 3-Approval;
§ 4-Release.
Return
ID # Description
5.2.4.14 - newRevision
This method enables to create a new revision for the document. To use it, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/document/NewRevisionRequestType.java
Return web/wwwroot/ws/java/document/NewRevisionResponseType.java
Request
ID # Required Description
Revision participants:
§ 1 User;
§ 2 Department;
§ 3 Position;
§ 4 Department/Position;
§ 5 Team;
§ 1-Draft;
§ 2-Review;
§ 3-Approval;
§ 4-Release.
Example:
identifier_of_attribute1=value_of_attribute1;identifier_of_at
tribute2=value_of_attribute2;identifier_of_attribute3=value
_of_attribute3.
DOC UMENTDATA
Example with a multivalued attribute:
identifier_of_attribute1=value1_of_attribute1,value2_of_att
ribute1,value3_of_attribute1.
Note: For date fields, the value must have the Y-M-D (Year-
Month-Day) format.
Return
ID # Description
5.2.4.15 - releasePendencyDocument
This method enables to release a revision execution task of a determined user. To use it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/ReleasePendencyDocumentRequestType.java
Return web/wwwroot/ws/java/document/ReleasePendencyDocumentResponseType.java
Request
ID # Required Description
IDUSER X User ID #.
Return
ID # Description
§ 1 User;
§ 2 Department;
return
§ 3 Position;
§ 4 Department/Position;
§ 5 Team;
§ 6 All.
5.2.4.16 - searchAccessAudit
This method enables to run a search in the SE Document access audit. To use it, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/document/SearchAccessAuditRequestType.java
Return web/wwwroot/ws/java/document/SearchAccessAuditResponseType.java
Request
ID # Required Description
Return
ID # Description
1 - View document;
2 - Registered document;
3 - Deleted document;
4 - Registered revision;
5 - Deleted revision;
6 - C losed revision;
11 - C ancelled document;
12 - Released document;
15 - C anceled archiving;
16 - Digital signature;
§ IDREVISION: Revision ID #;
5.2.4.17 - searchCategory
This method enables to list all the categories saved in the system the authenticated user has view access to.
Java class
Request web/wwwroot/ws/java/document/SearchCategoryRequestType.java
Return web/wwwroot/ws/java/document/SearchCategoryResponseType.java
Request
ID # Required Description
No parameter is required.
Return
ID # Description
FAILURE: -1
5.2.4.18 - searchDocument
This method enables to search for documents. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/SearchDocumentRequestType.java
Return web/wwwroot/ws/java/document/SearchDocumentResponseType.java
Request
ID # Required Description
Attributes array:
Note: For date fields, the value must have the Y-M-D (Year-
Month-Day) format.
Return
ID # Description
§ ADHESION: Starting with version 2.0, this parameter became obsolete. During the
import, leave it blank.
5.2.4.19 - setAttributeValue
This method enables to assign a value to an attribute of determined document. To use it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/document/SetAttributeValueRequestType.java
Return web/wwwroot/ws/java/document/SetAttributeValueResponseType.java
Request
ID # Required Description
Revision ID #.
IDREVISION Note: If not entered, the current revision will be
considered.
IDATTRIBUTE X Attribute ID #.
Return
ID # Description
SUC C ESS returns '1', meaning the attribute was updated successfully.
return
FAILURE: returns a message with the error that occurred.
5.2.4.20 - uploadEletronicFile
This method enables to upload an electronic file. To use it, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/document/UploadEletronicFileRequestType.java
Return web/wwwroot/ws/java/document/UploadEletronicFileResponseType.java
Request
ID # Required Description
IDREVISION Revision ID #.
Files array:
Return
ID # Description
5.2.4.21 - viewDocumentData
This method enables to recover the data of a document. To use it, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/document/ViewDocumentDataRequestType.java
Return web/wwwroot/ws/java/document/ViewDocumentDataResponseType.java
Request
ID # Required Description
IDREVISION Revision ID #.
Return
ID # Description
5.2.5 - Generic
Web Services
This section displays the generic interfaces available for SE Suite. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.5.1 - addAreaToTeam
To add new departments to the team, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\AddAreaToTeamRequestType.java
Return web\wwwroot\ws\java\generic\AddAreaToTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.2 - addPositionToTeam
To add new positions to a team, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\AddPositionToTeamRequestType.java
Return web\wwwroot\ws\java\generic\AddPositionToTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.3 - addUserToTeam
To add new users to a team, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\AddUserToTeamRequestType.java
Return web\wwwroot\ws\java\generic\AddUserToTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.4 - createTeamByArea
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\CreateTeamByAreaRequestType.java
Return web\wwwroot\ws\java\generic\CreateTeamByAreaResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.5 - createTeamByPosition
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\CreateTeamByPositionRequestType.java
Return web\wwwroot\ws\java\generic\CreateTeamByPositionResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.6 - createTeamByUser
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\CreateTeamByUserRequestType.java
Return web\wwwroot\ws\java\generic\CreateTeamByUserResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.7 - editTeamByArea
To edit each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\EditTeamByAreaRequestType.java
Return web\wwwroot\ws\java\generic\EditTeamByAreaResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.8 - editTeamByPosition
To edit each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\EditTeamByPositionRequestType.java
Return web\wwwroot\ws\java\generic\EditTeamByPositionResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.9 - editTeamByUser
To edit each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\EditTeamByUserRequestType.java
Return web\wwwroot\ws\java\generic\EditTeamByUserResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.10 - removeAreaFromTeam
To delete each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\RemoveAreaFromTeamRequestType.java
Return web\wwwroot\ws\java\generic\RemoveAreaFromTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.11 - removePositionFromTeam
To delete each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\RemovePositionFromTeamRequestType.java
Return web\wwwroot\ws\java\generic\RemovePositionFromTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.12 - removeTeam
To delete each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\RemoveTeamRequestType.java
Return web\wwwroot\ws\java\generic\RemoveTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.5.13 - removeUserFromTeam
To delete each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\generic\RemoveUserFromTeamRequestType.java
Return web\wwwroot\ws\java\generic\RemoveUserFromTeamResponseType.java
Request
ID # Required Description
IDTEAM X Team ID #;
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.6 - Incident
Web Services
This section displays the web services available for SE Incident. To invoke each of these methods, it is
necessary to follow the standard documented in the upcoming sections.
Method Description
clearChildEntityRecord Deletes all records related to form entity descending from the incident
editChildEntityRecord Edits a record of the form entity, descending from the incident
newChildEntityRecord Adds a record to the form entity descending from the incident
5.2.6.1 - cancelIncident
Java class
Request web\wwwroot\ws\java\incident\CancelIncidentRequestType.java
Return web\wwwroot\ws\java\incident\CancelIncidentResponseType.java
Request structure
<cancelIncident>
<IncidentID>?</IncidentID>
<Explanation>?</Explanation>
</cancelIncident>
Request
ID # Required Description
IncidentID X Incident ID #
Explanation X Explanation
Return
ID # Description
5.2.6.2 - clearChildEntityRecord
This method deletes all records related to the form entity descending from the incident
Java class
Request web\wwwroot\ws\java\incident\ClearChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\ClearChildEntityRecordResponseType.java
Request structure
<clearChildEntityRecord>
<IncidentID>?</IncidentID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
</clearChildEntityRecord>
Request
ID # Required Description
IncidentID X Incident ID #
Return
ID # Description
5.2.6.3 - deleteChildEntityRecord
This method deletes a form entity record descending from the incident.
Java class
Request web\wwwroot\ws\java\incident\DeleteChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\DeleteChildEntityRecordResponseType.java
Request structure
<deleteChildEntityRecord>
<IncidentID>?</IncidentID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
</deleteChildEntityRecord>
Request
ID # Required Description
IncidentID X Incident ID #
Return
ID # Description
5.2.6.4 - editAttributeValue
Java class
Request web\wwwroot\ws\java\incident\EditAttributeValueRequestType.java
Return web\wwwroot\ws\java\incident\EditAttributeValueResponseType.java
Request structure
<editAttributeValue>
<IncidentID>?</IncidentID>
<AttributeList>
<!--1 or more repetitions:-->
<Attribute>
<AttributeID>?</AttributeID>
<!--Zero or more repetitions:-->
<AttributeValueList>
<AttributeValue>?</AttributeValue>
</AttributeValueList>
</Attribute>
</AttributeList>
</editAttributeValue>
Request
ID # Required Description
IncidentID X Incident ID #
AttributeID X Attribute ID #
Attribute value
§ Date: YYYY-MM-DD
§ Hour: HHHH:MM
Return
ID # Description
5.2.6.5 - editChildEntityRecord
This method edits a record of the form entity, descending from the incident.
Java class
Request web\wwwroot\ws\java\incident\EditChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\EditChildEntityRecordResponseType.java
Request structure
<editChildEntityRecord>
<IncidentID>?</IncidentID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editChildEntityRecord>
Request
ID # Required Description
IncidentID X Incident ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.6.6 - editEntityRecord
Java class
Request web\wwwroot\ws\java\incident\EditEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\EditEntityRecordResponseType.java
Request structure
<editEntityRecord>
<IncidentID>?</IncidentID>
<EntityID>?</EntityID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editEntityRecord>
Request
ID # Required Description
IncidentID X Incident ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.6.7 - executeActivity
Java class
Request web\wwwroot\ws\java\incident\ExecuteActivityRequestType.java
Return web\wwwroot\ws\java\incident\ExecuteActivityResponseType.java
Request structure
<executeActivity>
<IncidentID>?</IncidentID>
<ActivityID>?</ActivityID>
<ActionSequence>?</ActionSequence>
<UserID>?</UserID>
</executeActivity>
Request
ID # Required Description
IncidentID X Incident ID #
ActivityID X Activity ID #
UserID User ID
Return
ID # Description
5.2.6.8 - executeSystemActivity
Java class
Request web\wwwroot\ws\java\incident\ExecuteSystemActivityRequestType.java
Return web\wwwroot\ws\java\incident\ExecuteSystemActivityResponseType.java
Request structure
<executeSystemActivity>
<IncidentID>?</IncidentID>
<ActivityID>?</ActivityID>
</executeSystemActivity>
Request
ID # Required Description
IncidentID X Incident ID #
ActivityID X Activity ID #
Return
ID # Description
5.2.6.9 - newAssocDocument
Java class
Request web\wwwroot\ws\java\incident\NewAssocDocumentRequestType.java
Return web\wwwroot\ws\java\incident\NewAssocDocumentResponseType.java
Request structure
<newAssocDocument>
<IncidentID>?</IncidentID>
<ActivityID>?</ActivityID>
<DocumentID>?</DocumentID>
</newAssocDocument>
Request
ID # Required Description
IncidentID X Incident ID #
ActivityID X Activity ID #
DocumentID X Document ID #
Return
ID # Description
5.2.6.10 - newAttachment
Java class
Request web\wwwroot\ws\java\incident\NewAttachmentRequestType.java
Return web\wwwroot\ws\java\incident\NewAttachmentResponseType.java
Request structure
<newAttachment>
<IncidentID>?</IncidentID>
<ActivityID>?</ActivityID>
<FileName>?</FileName>
<FileContent>?</FileContent>
<UserID>?</UserID>
<AttachmentID>?</AttachmentID>
<AttachmentName>?</AttachmentName>
<Summary>?</Summary>
</newAttachment>
Request
ID # Required Description
IncidentID X Incident ID #
ActivityID X Activity ID #
UserID User ID
AttachmentID Attachment ID #
Summary Summary
Return
ID # Description
5.2.6.11 - newChildEntityRecord
This method adds a record to the form entity descending from the incident.
Java class
Request web\wwwroot\ws\java\incident\NewChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\NewChildEntityRecordResponseType.java
Request structure
<newChildEntityRecord>
<IncidentID>?</IncidentID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</newChildEntityRecord>
Request
ID # Required Description
IncidentID X Incident ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.6.12 - newIncident
Java class
Request web\wwwroot\ws\java\incident\NewIncidentRequestType.java
Return web\wwwroot\ws\java\incident\NewIncidentResponseType.java
Request structure
<newIncident>
<IncidentTypeID>?</IncidentTypeID>
<IncidentTitle>?</IncidentTitle>
<UserID>?</UserID>
</newIncident>
Request
ID # Required Description
UserID User ID
Return
ID # Description
5.2.7 - Inspection
Web Services
This section displays the interfaces available for SE Inspection. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
relateCharacteristicToInspConfig
C haracteristic relationship in inspection configuration
uration
relateChecklistToInspConfigurati
C hecklist relationship in inspection configuration
on
5.2.7.1 - createUpdateConfiguration
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\CreateUpdateConfigurationRequestType.jav
Request
a
web\wwwroot\ws\java\inspection\CreateUpdateConfigurationResponseType.ja
Return
va
Request
ID # Required Description
14 – Insert;
FGOPTION X
15 – Edit;
16 – Insert/Edit.
IDOBJEC T X1 Item/Supply ID #
FGALLOWEDITWF 1 – Allow;
1 – Block
Frequency type:
1 – Uncontrolled;
FGTYPEFREQUENC E X4 2 – Execution date;
Frequency unit:
1 – Days;
FGFREQUENC E X5 2 – Weeks;
3 – Months;
4 – Years
Inspection frequency:
1 - Skip-lot
FGINSPFREQ X6
2 - Total inspection
3 - No inspection
FGINITIALSMP 1 – Yes;
2 – No (default option)
Sample status:
1 – Blocked;
FGSTATUSINITIALSMP X7
2 – Initial sample;
3 – Released
DTDUEDATE X7 Deadline
FGVALIDITYRIA 1 – Yes;
2 – No (default option)
1 – Days;
2 – Weeks;
3 – Months;
4 – Inspections
Register averages/readings:
2
FGAVGREADING X 1 – Register averages;
2 – Register readings
Rule:
1 – Sampling plan;
3 – Defined size;
4 – Percentage
Sampling plan:
1 – Simple;
FGDEFAULSAMPLEPLAN X9
2 – Double;
3 – Multiple
Inspection level:
IDLEVEL X9
[01, 02, 03, S1, S2, S3, S4]
Work regime:
1 – Reduced;
FGSWITC HRULE X9
2 – Normal;
3 – Tightened
NQA:
[0.010, 0.015, 0.025, 0.04, 0.65, 0.1, 0.15, 0.25, 0.4, 0.65,
VLAQL X9
1, 1.5, 2.5, 4, 6.5, 10, 15, 25, 40, 65, 100, 150, 250, 400,
650, 1000]
FGFIXED X9 1 – Yes;
2 – No (default option);
§ X 4 – Required when adding if the form object type allows the frequency to be controlled.
§ X 6 – Required when adding if the form object type requires the inspection frequency to be entered.
§ X 7 – Required when adding if the form object type requires the inspection frequency to be entered and the option to
control the initial sample is active.
§ X 8 – Required when adding if the form object type requires the inspection frequency to be entered and the option to
control the initial sample and the validity are active.
§ X 9 – Required if the form object type requires filling out a sampling plan and the option of the sampling rule requires it
to be filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.7.2 - createUpdateDeleteQualityIndex
§ Index evaluation.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\CreateUpdateDeleteQualityIndexRequestTyp
Request
e.java
web\wwwroot\ws\java\inspection\CreateUpdateDeleteQualityIndexResponseTy
Return
pe.java
Request
ID # Required Description
Action option:
11 – Add
FGOPTION X 12 – Edit
IDINDEX X Index ID #
§ X 2 – Required for inspections where Object, Process, Process activity, or Supplier is part of the evaluation; otherwise,
they will be ignored.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.7.3 - createUpdateDeleteReceiving
§ Data of a receiving.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\CreateUpdateDeleteReceivingRequestType.j
Request
ava
web\wwwroot\ws\java\inspection\CreateUpdateDeleteReceivingResponseType.
Return
java
Request
ID # Required Description
Action option:
3 – Add;
FGOPTION X
4 – Edit;
5 – Delete.
§ X 2 – Required for inspections of Supplies, Services, and External finished products; ignored for other object types.
§ X 3 – Required, not required, or ignored, depending on the configurations set in the inspection form type.
§ X 4 – Required if the "Allow editing flow during receiving" option is checked in the inspection form, or ignored otherwise.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.7.4 - editQualificationIndexValue
This import template enables to edit the qualification index and send it to the next step:
§ Receiving data.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\EditQualificationIndexValueRequestType.j
Request
ava
web\wwwroot\ws\java\inspection\EditQualificationIndexValueResponseType.
Return
java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.7.5 - relateCharacteristicToInspConfiguration
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\RelateCharacteristicToInspConfigurationR
Request
equestType.java
web\wwwroot\ws\java\inspection\RelateCharacteristicToInspConfigurationR
Return
esponseType.java
Request
ID # Required Description
20 – Associate;
FGOPTION X
21 – Edit;
22 – Disassociate.
Required:
2 – Not required
NRVALIDITY X1 Validity
Frequency unit:
1 – Days;
FGVALIDITY X1 2 – Weeks;
3 – Months;
4 – Inspections
FGENABLEDPRINT 1 – Yes;
2 – No (default option)
1 – Register averages;
2 – Register readings
Rule:
1 – Sampling plan;
3 – Defined size;
4 – Percentage
Sampling plan:
1 – Simple;
FGSAMPLEPLAN X3
2 – Double;
3 – Multiple
Inspection level:
IDLEVEL X3
[01, 02, 03, S1, S2, S3, S4]
Work regime:
1 – Reduced;
FGSWITC HRULE X3
2 – Normal;
3 – Tightened
NQA:
[0.010, 0.015, 0.025, 0.04, 0.65, 0.1, 0.15, 0.25, 0.4, 0.65,
VLAQL X3
1, 1.5, 2.5, 4, 6.5, 10, 15, 25, 40, 65, 100, 150, 250, 400,
650, 1000]
FGFIXED X3 1 – Yes;
2 – No (default option);
§ X³ – Required if the selected sampling type option requires filling the field in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.7.6 - relateChecklistToInspConfiguration
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\inspection\RelateChecklistToInspConfigurationReques
Request
tType.java
web\wwwroot\ws\java\inspection\RelateChecklistToInspConfigurationRespon
Return
seType.java
Request
ID # Required Description
FGOPTION X 25 – Associate;
26 – Disassociate.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.8 - Maintenance
Web Services
This section displays the interfaces available for SE Maintenance. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.8.1 - insertMeterReading
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request InsertMeterReadingRequestType.java
Return InsertMeterReadingResponseType.java
Request
ID # Required Description
idobject X Asset ID #.
Reading value.
vlreadvalue X¹ Use point as decimal separator and do not used thousands
separator, for example “16000.000”.
X¹ - Required if the action is New meter reading. Not required if the action is New meter restart.
Return
ID # Description
SUC C ESS: 1.
return
Failure: message describing the error.
5.2.8.2 - insertVariableReading
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request InsertVariableReadingRequestType.java
Return InsertVariableReadingResponseType.java
Request
ID # Required Description
idobject X Asset ID #.
idvariable X Variable ID #.
If it is a subjective variable:
Reading value.
Return
ID # Description
SUC C ESS: 1.
return
Failure: message describing the error.
5.2.8.3 - createCorrectiveMaintenance
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\maintenance\CreateCorrectiveMaintenanceRequestType.
Request
java
web\wwwroot\ws\java\maintenance\CreateCorrectiveMaintenanceResponseType
Return
.java
Request
ID # Required Description
IDASSET X Asset ID #
Responsible technician:
Document attributes.
Example:
§ identifier_of_attribute1=valued_of_attribute1;
§ identifier_of_attribute2=value_of_attribute2;
§ identifier_of_attribute3=value_of_attribute3;
ATTRIBUTES X³
Example with a multivalued attribute:
§ identifier_of_attribute1=value1_of_attribute1,value2_of_
attribute1,value3_of_attribute1.
X¹ - Required if the "Start date" and/or "Start time" and/or "Actual percentage" field(s) is(are) filled in
Return
ID # Description
SUC C ESS: 1.
return
FAILUREReturns a message regarding the error that occurred
5.2.9 - PDM
Web Services
This section displays the interfaces available for SE PDM. To insert each of these items, it will be necessary to
follow the standard documented in the upcoming sections.
Method Description
relateAssetTypeToCharacteristic Import of the asset type association with the item characteristics
5.2.9.1 - addBom
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddBomRequestType.java
Return web\wwwroot\ws\java\item\AddBomResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
VLQUANTITY X Quantity
2 - Supply.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.2 - addCharacteristicAttrib
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddCharacteristicAttribRequestType.java
Return web\wwwroot\ws\java\item\AddCharacteristicAttribResponseType.java
Request
ID # Required Description
IDOBJEC T X Item ID #.
Special characteristic:
2 – No.
DSOBSERVATION C omments.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.3 - addCharacteristicVar
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddCharacteristicVarRequestType.java
Return web\wwwroot\ws\java\item\AddCharacteristicVarResponseType.java
Request
ID # Required Description
IDOBJEC T X Item ID #
Special characteristic:
2 - No;
Limits:
0 - Bilateral;
FGLIMIT X
1 - Unilateral up;
2 - Unilateral down;
DSOBSERVATION C omments
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.4 - addCustomer
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddCustomerRequestType.java
Return web\wwwroot\ws\java\item\AddCustomerResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.5 - addManufacturer
This method enables to associate a manufacturer with the item. To insert each of these items, it is necessary
to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddManufacturerRequestType.java
Return web\wwwroot\ws\java\item\AddManufacturerResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.6 - addSupplier
This method enables to associate and edit the supplier of the item.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddSupplierRequestType.java
Return web\wwwroot\ws\java\item\AddSupplierResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
1 - Day
3 - Month
4 - Year
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
5.2.9.7 - deleteBom
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\AddBomRequestType.java
Return web\wwwroot\ws\java\item\AddBomResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
2 - Supply.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.8 - deleteCustomer
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\DeleteCustomerRequestType.java
Return web\wwwroot\ws\java\item\DeleteCustomerResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.9 - deleteItem
§ Data of an item:
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\DeleteItemRequestType.java
Return web\wwwroot\ws\java\item\DeleteItemResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.10 - deleteManufacturer
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\DeleteManufacturerRequestType.java
Return web\wwwroot\ws\java\item\DeleteManufacturerResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #.
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.11 - deleteSupplier
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\DeleteSupplierRequestType.java
Return web\wwwroot\ws\java\item\DeleteSupplierResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
X 2 - Required if the “C ompany ID” and/or the “C ompany name” are not filled in.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.12 - import_attrib_assoc
For a successful association of attributes, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\Import_attrib_assocRequestType.java
Return web\wwwroot\ws\java\item\Import_attrib_assocResponseType.java
Request
ID # Required Description
IDOBJEC T X Item ID #
Attribute value.
According to FGDATATYPE:
VALUE X 1 - NMATTRIBUTE
2 - VLATTRIBUTE
3 - DTATTRIBUTE
IDREVISION Revision ID #
NMATTRIBUTE Memo
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.13 - newItem
§ Data of an item:
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\NewItemRequestType.java
Return web\wwwroot\ws\java\item\NewItemResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
Physical state:
1 Solid;
3 Gas;
4 Sludge
IDODOR Odor ID #
IDDANGEROUSNESS Hazard ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.14 - newItemType
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\item\NewItemTypeRequestType.java
Return web\wwwroot\ws\java\item\NewItemTypeResponseType.java
Request
ID # Required Description
FGUSEMASK X 1 - Yes;
2 - No.
1 - Yes;
2 - No.
Revision control:
FGUSEREVISION X 1 - Yes;
2 - No.
Revision ID #:
1 - Numeric;
FGREVID X1
2 - Text;
3 - C ustomized.
Approval type:
FGREVAPPROVALMODE X1
1 - Incremental;
2 - C ircular.
C losure type:
FGREVRELEASEMODE X1 1 - Automatic;
2 - Manual.
Retention frequency:
1 - Revisions;
FGREVRETENTIONMODE X1
2 - Months;
3 - Years.
Route type:
FGREVROUTETYPE X1 1 - Fixed;
2 - Variable.
2 - OR.
2 - OR.
2 - OR.
2 - OR.
Watermark:
2 - No.
2 - No.
File type:
1 - Simple;
FGFILETYPE X
2 - Multiple;
3 - C omplex.
is equal to 3).
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.9.15 - relateAssetTypeToCharacteristic
To insert each of these items, it is necessary to follow the standard documented below.
Java class
web\wwwroot\ws\java\item\RelateAssetTypeToCharacteristicRequestType.jav
Request
a
web\wwwroot\ws\java\item\RelateAssetTypeToCharacteristicResponseType.ja
Return
va
Request
ID # Required Description
IDOBJEC T X Item ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.10 - Performance
Web Services
This section displays the interfaces available for SE Performance. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.10.1 - addMeasuresInAdinterface
Java class
Request web/wwwroot/ws/java/strategy/AddMeasuresInAdinterfaceRequestType.java
Return web/wwwroot/ws/java/strategy/AddMeasuresInAdinterfaceResponseType.java
Request
ID # Required Description
Return
ID # Description
Web Services
In this section, the interfaces available for the SE Archive are displayed. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
5.2.11.1 - newPhysicalFileLoan
This method enables to add a record of a physical file loan. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/archival/NewPhysicalFileLoanRequestType.java
Return web/wwwroot/ws/java/archival/NewPhysicalFileLoanResponseType.java
Request
ID # Required Description
UserID X Requester ID #
DocumentID X Document ID #
C ategoryID X C ategory ID #
Return
ID # Description
Status FAILURE (in case of failure) / SUC C ESS (in case of success)
· 7 - Document processing;
Detail Message detailing the error or success in the execution of the method
RecordID Loan registration code created (in case of success) or empty (in case of failure)
5.2.12 - Problem
Web Services
This section displays the web services available for SE Problem. To invoke each of these methods, it is
necessary to follow the standard documented in the upcoming sections.
Method Description
clearChildEntityRecord Deletes all related records from form entity descending from problem
newChildEntityRecord Adds a record to the form entity descending from the problem
5.2.12.1 - cancelProblem
Java class
Request web\wwwroot\ws\java\problem\CancelProblemRequestType.java
Return web\wwwroot\ws\java\problem\CancelProblemResponseType.java
Request structure
<cancelProblem>
<ProblemID>?</ProblemID>
<Explanation>?</Explanation>
</cancelProblem>
Request
ID # Required Description
ProblemID X Problem ID #
Explanation X Explanation
Return
ID # Description
5.2.12.2 - clearChildEntityRecord
This method deletes all related records from the form entity descending from the problem.
Java class
Request web\wwwroot\ws\java\problem\ClearChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\problem\ClearChildEntityRecordResponseType.java
Request structure
<clearChildEntityRecord>
<ProblemID>?</ProblemID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
</clearChildEntityRecord>
Request
ID # Required Description
ProblemID X Problem ID #
Return
ID # Description
5.2.12.3 - deleteChildEntityRecord
This method deletes a form entity record descending from the problem.
Java class
Request web\wwwroot\ws\java\problem\DeleteChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\problem\DeleteChildEntityRecordResponseType.java
Request structure
<deleteChildEntityRecord>
<ProblemID>?</ProblemID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
</deleteChildEntityRecord>
Request
ID # Required Description
ProblemID X Problem ID #
Return
ID # Description
5.2.12.4 - editAttributeValue
Java class
Request web\wwwroot\ws\java\problem\EditAttributeValueRequestType.java
Return web\wwwroot\ws\java\problem\EditAttributeValueResponseType.java
Request structure
<editAttributeValue>
<ProblemID>?</ProblemID>
<AttributeList>
<!--1 or more repetitions:-->
<Attribute>
<AttributeID>?</AttributeID>
<!--Zero or more repetitions:-->
<AttributeValueList>
<AttributeValue>?</AttributeValue>
</AttributeValueList>
</Attribute>
</AttributeList>
</editAttributeValue>
Request
ID # Required Description
ProblemID X Problem ID #
AttributeID X Attribute ID #
Attribute value
§ Date: YYYY-MM-DD
§ Hour: HHHH:MM
Return
ID # Description
5.2.12.5 - editChildEntityRecord
This method edits a record of the form entity descending from the problem
Java class
Request web\wwwroot\ws\java\problem\EditChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\problem\EditChildEntityRecordResponseType.java
Request structure
<editChildEntityRecord>
<ProblemID>?</ProblemID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editChildEntityRecord>
Request
ID # Required Description
ProblemID X Problem ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.12.6 - editEntityRecord
Java class
Request web\wwwroot\ws\java\problem\EditEntityRecordRequestType.java
Return web\wwwroot\ws\java\problem\EditEntityRecordResponseType.java
Request structure
<editEntityRecord>
<ProblemID>?</ProblemID>
<EntityID>?</EntityID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editEntityRecord>
Request
ID # Required Description
ProblemID X Problem ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.12.7 - executeActivity
Java class
Request web\wwwroot\ws\java\problem\ExecuteActivityRequestType.java
Return web\wwwroot\ws\java\problem\ExecuteActivityResponseType.java
Request structure
<executeActivity>
<ProblemID>?</ProblemID>
<ActivityID>?</ActivityID>
<ActionSequence>?</ActionSequence>
<UserID>?</UserID>
</executeActivity>
Request
ID # Required Description
ProblemID X Problem ID #
ActivityID X Activity ID #
UserID User ID
Return
ID # Description
5.2.12.8 - executeSystemActivity
Java class
Request web\wwwroot\ws\java\problem\ExecuteSystemActivityRequestType.java
Return web\wwwroot\ws\java\problem\ExecuteSystemActivityResponseType.java
Request structure
<executeSystemActivity>
<ProblemID>?</ProblemID>
<ActivityID>?</ActivityID>
</executeSystemActivity>
Request
ID # Required Description
ProblemID X Problem ID #
ActivityID X Activity ID #
Return
ID # Description
5.2.12.9 - newAssocDocument
Java class
Request web\wwwroot\ws\java\problem\NewAssocDocumentRequestType.java
Return web\wwwroot\ws\java\problem\NewAssocDocumentResponseType.java
Request structure
<newAssocDocument>
<ProblemID>?</ProblemID>
<ActivityID>?</ActivityID>
<DocumentID>?</DocumentID>
</newAssocDocument>
Request
ID # Required Description
ProblemID X Problem ID #
ActivityID X Activity ID #
DocumentID X Document ID #
Return
ID # Description
5.2.12.10 - newAttachment
Java class
Request web\wwwroot\ws\java\problem\NewAttachmentRequestType.java
Return web\wwwroot\ws\java\problem\NewAttachmentResponseType.java
Request structure
<newAttachment>
<ProblemID>?</ProblemID>
<ActivityID>?</ActivityID>
<FileName>?</FileName>
<FileContent>?</FileContent>
<UserID>?</UserID>
<AttachmentID>?</AttachmentID>
<AttachmentName>?</AttachmentName>
<Summary>?</Summary>
</newAttachment>
Request
ID # Required Description
ProblemID X Problem ID #
ActivityID X Activity ID #
UserID User ID
AttachmentID Attachment ID #
Summary Summary
Return
ID # Description
5.2.12.11 - newChildEntityRecord
This method adds a record to the form entity descending from the problem.
Java class
Request web\wwwroot\ws\java\problem\NewChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\problem\NewChildEntityRecordResponseType.java
Request structure
<newChildEntityRecord>
<ProblemID>?</ProblemID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</newChildEntityRecord>
Request
ID # Required Description
ProblemID X Problem ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.12.12 - newProblem
Java class
Request web\wwwroot\ws\java\problem\NewProblemRequestType.java
Return web\wwwroot\ws\java\problem\NewProblemResponseType.java
Request structure
<newProblem>
<ProblemTypeID>?</ProblemTypeID>
<ProblemTitle>?</ProblemTitle>
<UserID>?</UserID>
</newProblem>
Request
ID # Required Description
UserID User ID
Return
ID # Description
5.2.13 - Project
Web Services
This section displays the interfaces available for SE Project. To insert each of these items, it will be necessary
to follow the standard documented in the upcoming sections.
Method Description
Returns an XML of the service reports in the approval step that were
returnRatApproval
not sent yet.
Returns an XML of the service reports in the approval step that were
returnRatApprovalOne
not sent yet.
5.2.13.1 - cancelRat
This method changes the status of the service report to cancelled. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/project/CancelRatRequestType.java
Return web/wwwroot/ws/java/project/CancelRatResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: 2
5.2.13.2 - editProgramCost
This method enables editing the cost of a program. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/NewProgramCostRequestType.java
Return web/wwwroot/ws/java/project/NewProgramCostResponseType.java
Request
ID # Required Description
ProgramId X Program ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.3 - editProgramRevenue
This method enables to edit the revenue of a program. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/EditProgramRevenueRequestType.java
Return web/wwwroot/ws/java/project/EditProgramRevenueResponseType.java
Request
ID # Required Description
ProgramId X Program ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.4 - editProjectCost
This method enables to edit the cost of a project. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/EditProjectCostRequestType.java
Return web/wwwroot/ws/java/project/EditProjectCostResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.5 - editProjectRevenue
This method enables to edit the revenue of a project. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/EditProjectRevenueRequestType.java
Return web/wwwroot/ws/java/project/EditProjectRevenueResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.6 - editProjectTaskRevenue
This method enables to edit the revenue of a project task. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/project/NewProjectTaskRevenueRequestType.java
Return web/wwwroot/ws/java/project/NewProjectTaskRevenueResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.7 - executeProjectTask
This method enables to execute a project task. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/NewAssocDocProjRequestType.java
Return web/wwwroot/ws/java/project/NewAssocDocProjResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Return
ID # Description
5.2.13.8 - newAssocDocProj
This method enables to associate a document with the project or with a project task. To edit it, it is necessary
to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/project/NewAssocDocProjRequestType.java
Return web/wwwroot/ws/java/project/NewAssocDocProjResponseType.java
Request
ID # Required Description
IDPROJEC T X Project ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Error message
5.2.13.9 - newProgramCost
This method enables to add the cost in a program. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/EditProjectTaskRevenueRequestType.java
Return web/wwwroot/ws/java/project/EditProjectTaskRevenueResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.10 - newProgramRevenue
This method enables to add the revenue in a program. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/NewProgramRevenueRequestType.java
Return web/wwwroot/ws/java/project/NewProgramRevenueResponseType.java
Request
ID # Required Description
ProgramId X Program ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.11 - newProjectCost
This method enables to add the cost in a project. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/NewProjectCostRequestType.java
Return web/wwwroot/ws/java/project/NewProjectCostResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.12 - newProjectRevenue
Java class
Request web/wwwroot/ws/java/project/NewProjectRevenueRequestType.java
Return web/wwwroot/ws/java/project/NewProjectRevenueResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.13 - newProjectTaskCost
This method enables to add the cost in a project task. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/project/NewProjectTaskCostRequestType.java
Return web/wwwroot/ws/java/project/NewProjectTaskCostResponseType.java
Request
ID # Required Description
ProjectId X Project ID #
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.13.14 - RatSent
This method makes the service report unavailable to be returned by the other services of returnRatApproval
and returnRatApprovalOne. For this action, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/project/RatSentRequestType.java
Return web/wwwroot/ws/java/project/RatSentResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: 2
5.2.13.15 - returnRatApproval
Returns an XML of the service reports in the approval step that were not sent yet. To edit it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/project/ReturnRatApprovalRequestType.java
Return web/wwwroot/ws/java/project/ReturnRatApprovalResponseType.java
Return
ID # Description
Returns an XML of all service reports in the approval step that were not sent yet.
return
FAILURE: -1
5.2.13.16 - returnRatApprovalOne
Returns an XML of the service reports in the approval step that were not sent yet. To edit it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/project/ReturnRatApprovalOneRequestType.java
Return web/wwwroot/ws/java/project/ReturnRatApprovalOneResponseType.java
Return
ID # Description
SUC C ESS: Returns an XML of a service report in the approval step that was not sent yet.
return
FAILURE: -1
5.2.13.17 - setRatAttributeValue
This method assigns a value to an attribute of the Service Report: If the attribute is not associated with a
Service Report, it will be then associated. For this action, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/project/SetRatAttributeValueRequestType.java
Return web/wwwroot/ws/java/project/SetRatAttributeValueResponseType.java
Request
ID # Required Description
IDATTRIBUTE X Attribute ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Error message
5.2.14 - Request
Web Services
This section displays the interfaces available for SE Request. To insert each of these items, it will be necessary
to follow the standard documented in the upcoming sections.
Method Description
5.2.14.1 - getKeyWordRequestStatus
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\servicer\GetKeyWordRequestStatusRequestType.java
Return web\wwwroot\ws\java\servicer\GetKeyWordRequestStatusResponseType.java
Request
ID # Required Description
IDREQUEST X Request ID #.
Return
ID # Description
1 – Issue
2 – Approval
3 – To be executed
return 4 – Being executed
5 – C losure
6 – Finished
7 – C ancelled
5.2.14.2 - newKeyWordRequest
§ Data of a request;
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\servicer\NewKeyWordRequestRequestType.java
Return web\wwwroot\ws\java\servicer\NewKeyWordRequestResponseType.java
Request
ID # Required Description
IDREQUEST X Request ID #
Request attributes.
Example:
ID#_OF_ATTRIBUTE1=VALUE_OF_ATTRIBUTE1;ID#_OF_AT
TRIBUTE2=VALUE_OF_ATTRIBUTE2;ID#_OF_ATTRIBUTE3=
VALUE_OF_ATTRIBUTE3.
ATTRIBUTES X
Example with a multivalued attribute. Note that the
separator for the values of the multivalued attributes is a
"," (comma):
ID#_OF_ATTRIBUTE1=VALUE1_OF_ATTRIBUTE1,VALUE2_O
F_ATTRIBUTE1,VALUE3_OF_ATTRIBUTE1.
Return
ID # Description
5.2.14.3 - sendRequestToApprov
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\servicer\SendRequestToApprovRequestType.java
Return web\wwwroot\ws\java\servicer\SendRequestToApprovResponseType.java
Request
ID # Required Description
Return
ID # Description
5.2.15 - SPC
Web Services
This section displays the interfaces available for SE SPC. To insert each of these items, it will be necessary to
follow the standard documented in the upcoming sections.
Method Description
5.2.15.1 - ChangeStatusSample
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/ChangeStatusSampleRequestType.java
Return web/wwwroot/ws/java/spc/ChangeStatusSampleResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.2 - DeleteAttCause
This method enables to delete the causes of defects of a sample (zeroes the causes).
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/DeleteAttCauseRequestType.java
Return web/wwwroot/ws/java/spc/DeleteAttCauseResponseType.java
Request
ID # Required Description
IDDEFEC T X Defect ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.3 - DeleteAttDefect
This method enables to delete the defects of a sample (zeroes the defects).
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/DeleteAttDefectRequestType.java
Return web/wwwroot/ws/java/spc/DeleteAttDefectResponseType.java
Request
ID # Required Description
IDDEFEC T X Defect ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.4 - DeleteSampleAtt
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/DeleteSampleAttRequestType.java
Return web/wwwroot/ws/java/spc/DeleteSampleAttResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.5 - DeleteSampleVar
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/DeleteSampleVarRequestType.java
Return web/wwwroot/ws/java/spc/DeleteSampleVarResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.6 - ImportAttCause
This method enables to change the number of causes of a defect of the attribute type sample of a data
collection.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/ImportAttCauseRequestType.java
Return web/wwwroot/ws/java/spc/ImportAttCauseResponseType.java
Request
ID # Required Description
IDDEFEC T X Defect ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.7 - ImportAttDefect
This method enables to change the number of defects of the attribute type sample of a data collection.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/ImportAttDefectRequestType.java
Return web/wwwroot/ws/java/spc/ImportAttDefectResponseType.java
Request
ID # Required Description
IDDEFEC T X Defect ID #
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.8 - ImportSampleAtt
This method enables to import an attribute type sample to a collection with attribute type characteristics.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/ImportSampleAttRequestType.java
Return web/wwwroot/ws/java/spc/ImportSampleAttResponseType.java
Request
ID # Required Description
IDOPERATOR Operator ID #
IDSHIFT Shift ID #
IDGAGE Gage ID #
NMLOT Lot
NMMO OF
Format:
DEFEC T01:3;DEFEC T\;02:4
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.15.9 - ImportSampleVar
This method enables to import a variable type sample to a collection with a variable type characteristic.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/spc/ImportSampleVarRequestType.java
Return web/wwwroot/ws/java/spc/ImportSampleVarResponseType.java
Request
ID # Required Description
IDOPERATOR Operator ID #
IDSHIFT Shift ID #
IDGAGE Gage ID #
NMLOT Lot
NMMO OF
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Returns a message regarding the error that occurred
5.2.16 - Supply
Web Services
This section displays the interfaces available for SE Supply. To insert each of these items, it will be necessary
to follow the standard documented in the upcoming sections.
Method Description
5.2.16.1 - addEditSupplyWarehouse
This method enables to associate/edit a storeroom with a supply. To insert each of these items, it is necessary
to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\AddEditSupplyWarehouseRequestType.java
Return web\wwwroot\ws\java\supply\AddEditSupplyWarehouseResponseType.java
Request
ID # Required Description
IDBOJEC T X Object ID #
Return
ID # Description
5.2.16.2 - addSupplyStructure
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\AddSupplyStructureRequestType.java
Return web\wwwroot\ws\java\supply\AddSupplyStructureResponseType.java
Request
ID # Required Description
IDBOJEC T X Asset ID #
IDREVISION X Revision ID #
VLQUANTITY X Quantity
Return
ID # Description
5.2.16.3 - createEditSupply
§ Data of a supply.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\CreateEditSupplyRequestType.java
Return web\wwwroot\ws\java\supply\CreateEditSupplyResponseType.java
Request
ID # Required Description
IDBOJEC T X Asset ID #
Return
ID # Description
5.2.16.4 - createSupplyType
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\CreateSupplyTypeRequestType.java
Return web\wwwroot\ws\java\supply\CreateSupplyTypeResponseType.java
Request
ID # Required Description
2 - No;
IDMASK Mask ID #
Revision ID #:
1 – Text;
FGEDITID 2 – Numeric;
3 – C ustomized;
IDREVISIONROUTEOBJTYPE Route ID #
Revision cycle:
2 - Text
Approval type:
FGREVAPPROVALMODEOBJT
1 - Incremental;
YPE
2 - C ircular
C losure type:
FGREVRELEASEMODEOBJTYP
1 - Automatic
E
2 - Manual
Return
ID # Description
5.2.16.5 - deleteSupply
§ Data of a supply.
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\DeleteSupplyRequestType.java
Return web\wwwroot\ws\java\supply\DeleteSupplyResponseType.java
Request
ID # Required Description
IDBOJEC T X Asset ID #
Return
ID # Description
5.2.16.6 - deleteSupplyStructure
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\DeleteSupplyStructureRequestType.java
Return web\wwwroot\ws\java\supply\DeleteSupplyStructureResponseType.java
Request
ID # Required Description
IDBOJEC T X Asset ID #
IDREVISION X Revision ID #
Return
ID # Description
5.2.16.7 - deleteSupplyWarehouse
To insert each of these items, it is necessary to follow the standard documented below.
Java class
Request web\wwwroot\ws\java\supply\DeleteSupplyWarehouseRequestType.java
Return web\wwwroot\ws\java\supply\DeleteSupplyWarehouseResponseType.java
Request
ID # Required Description
IDOBJEC T X Object ID #
Return
ID # Description
Web Services
This section displays the interfaces available for SE Time control. To insert each of these items, it will be
necessary to follow the standard documented in the upcoming sections.
Method Description
Returns an XML of the service reports in the approval step that were
returnRatApproval
not sent yet.
Returns an XML of the service reports in the approval step that were
returnRatApprovalOne
not sent yet.
5.2.17.1 - cancelRat
This method changes the status of the service report to cancelled. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/CancelRatRequestType.java
Return web/wwwroot/ws/workforce/project/CancelRatResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: 2
5.2.17.2 - editNonProjectTaskCost
This method to edit the cost of a nonproject task. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/workforce/EditNonProjectTaskCostRequestType.java
Return web/wwwroot/ws/java/workforce/EditNonProjectTaskCostResponseType.java
Request
ID # Required Description
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.17.3 - editNonProjectTaskRevenue
This method enables to edit the revenue of a nonproject task. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/EditNonProjectTaskRevenueRequestType.java
web/wwwroot/ws/java/workforce/EditNonProjectTaskRevenueResponseType.jav
Return
a
Request
ID # Required Description
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.17.4 - executeNonProjectTask
This method enables to execute a nonproject task. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/workforce/ExecuteNonProjectTaskRequestType.java
Return web/wwwroot/ws/java/workforce/ExecuteNonProjectTaskResponseType.java
Request
ID # Required Description
Fill-in option:
UsePlannedOrRescheduledDa
1 - Apply planned dates,
tes
2 - Apply rescheduled dates
Return
ID # Description
5.2.17.5 - newNonProjectTaskCost
This method enables to add the cost of a nonproject task. For this action, it is necessary to follow the standard
documented below.
Java class
Request web/wwwroot/ws/java/workforce/NewNonProjectTaskCostRequestType.java
Return web/wwwroot/ws/java/workforce/NewNonProjectTaskCostResponseType.java
Request
ID # Required Description
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.17.6 - newNonProjectTaskRevenue
This method enables to add the revenue of a nonproject task. For this action, it is necessary to follow the
standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/NewNonProjectTaskRevenueRequestType.java
Return web/wwwroot/ws/java/workforce/NewNonProjectTaskRevenueResponseType.java
Request
ID # Required Description
Step to add:
1- Planned;
Phase X
2- Rescheduled;
3- Actual.
Amount X Quantity
Description Description
Return
ID # Description
5.2.17.7 - RatSent
This method makes the service report unavailable to be returned by the other services of returnRatApproval
and returnRatApprovalOne. For this action, it is necessary to follow the standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/RatSentRequestType.java
Return web/wwwroot/ws/java/workforce/RatSentResponseType.java
Request
ID # Required Description
Return
ID # Description
SUC C ESS: 1
return
FAILURE: 2
5.2.17.8 - returnRatApproval
Returns an XML of the service reports in the approval step that were not sent yet. To edit it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/ReturnRatApprovalRequestType.java
Return web/wwwroot/ws/java/workforce/ReturnRatApprovalResponseType.java
Return
ID # Description
Returns an XML of all service reports in the approval step that were not sent yet.
return
FAILURE: -1
5.2.17.9 - returnRatApprovalOne
Returns an XML of the service reports in the approval step that were not sent yet. To edit it, it is necessary to
follow the standard documented below.
Java class
Request web/wwwroot/ws/java/workforce/ReturnRatApprovalOneRequestType.java
Return web/wwwroot/ws/java/workforce/ReturnRatApprovalOneResponseType.java
Return
ID # Description
SUC C ESS: Returns an XML of a service report in the approval step that was not sent yet.
return
FAILURE: -1
5.2.17.10 - setRatAttributeValue
This method assigns a value to an attribute of the Service Report: If the attribute is not associated with a
Service Report, it will be then associated. For this action, it is necessary to follow the standard documented
below.
Java class
Request web/wwwroot/ws/java/workforce/SetRatAttributeValueRequestType.java
Return web/wwwroot/ws/java/workforce/SetRatAttributeValueResponseType.java
Request
ID # Required Description
IDATTRIBUTE X Attribute ID #.
Return
ID # Description
SUC C ESS: 1
return
FAILURE: Error message
5.2.18 - Workflow
Web Services
This section displays the web services available for SE Workflow. To invoke each
of these methods, it is necessary to follow the standard documented in the upcoming sections.
Method Description
Deletes all related records from the form entity descending from
clearChildEntityRecord
workflow
newChildEntityRecord Adds a record to the form entity descending from the workflow
5.2.18.1 - cancelWorkflow
Java class
Request web\wwwroot\ws\java\workflow\CancelWorkflowRequestType.java
Return web\wwwroot\ws\java\workflow\CancelWorkflowResponseType.java
Request structure
<cancelWorkflow>
<WorkflowID>?</WorkflowID>
<Explanation>?</Explanation>
</cancelWorkflow>
Request
ID # Required Description
WorkflowID X Workflow ID #
Explanation X Explanation
Return
ID # Description
5.2.18.2 - clearChildEntityRecord
This method deletes all related records from the form entity descending from the workflow
Java class
Request web\wwwroot\ws\java\workflow\ClearChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\incident\ClearChildEntityRecordResponseType.java
Request structure
<clearChildEntityRecord>
<WorkflowID>?</WorkflowID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
</clearChildEntityRecord>
Request
ID # Required Description
WorkflowID X Workflow ID #
Return
ID # Description
5.2.18.3 - deleteChildEntityRecord
This method deletes a form entity record descending from the workflow.
Java class
Request web\wwwroot\ws\java\workflow\DeleteChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\workflow\DeleteChildEntityRecordResponseType.java
Request structure
<deleteChildEntityRecord>
<WorkflowID>?</WorkflowID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
</deleteChildEntityRecord>
Request
ID # Required Description
WorkflowID X Workflow ID #
Return
ID # Description
5.2.18.4 - editAttributeValue
Java class
Request web\wwwroot\ws\java\workflow\EditAttributeValueRequestType.java
Return web\wwwroot\ws\java\workflow\EditAttributeValueResponseType.java
Request structure
<editAttributeValue>
<WorkflowID>?</WorkflowID>
<AttributeList>
<!--1 or more repetitions:-->
<Attribute>
<AttributeID>?</AttributeID>
<!--Zero or more repetitions:-->
<AttributeValueList>
<AttributeValue>?</AttributeValue>
</AttributeValueList>
</Attribute>
</AttributeList>
</editAttributeValue>
Request
ID # Required Description
WorkflowID X Workflow ID #
AttributeID X Attribute ID #
Attribute value
§ Date: YYYY-MM-DD
§ Hour: HHHH:MM
Return
ID # Description
5.2.18.5 - editChildEntityRecord
Java class
Request web\wwwroot\ws\java\workflow\EditChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\workflow\EditChildEntityRecordResponseType.java
Request structure
<editChildEntityRecord>
<WorkflowID>?</WorkflowID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<ChildRecordOID>?</ChildRecordOID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editChildEntityRecord>
Request
ID # Required Description
WorkflowID X Workflow ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.18.6 - editEntityRecord
Java class
Request web\wwwroot\ws\java\workflow\EditEntityRecordRequestType.java
Return web\wwwroot\ws\java\workflow\EditEntityRecordResponseType.java
Request structure
<editEntityRecord>
<WorkflowID>?</WorkflowID>
<EntityID>?</EntityID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</editEntityRecord>
Request
ID # Required Description
WorkflowID X Workflow ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.18.7 - executeActivity
Java class
Request web\wwwroot\ws\java\workflow\ExecuteActivityRequestType.java
Return web\wwwroot\ws\java\workflow\ExecuteActivityResponseType.java
Request structure
<executeActivity>
<WorkflowID>?</WorkflowID>
<ActivityID>?</ActivityID>
<ActionSequence>?</ActionSequence>
<UserID>?</UserID>
</executeActivity>
Request
ID # Required Description
WorkflowID X Workflow ID #
ActivityID X Activity ID #
UserID User ID
Return
ID # Description
5.2.18.8 - executeSystemActivity
Java class
Request web\wwwroot\ws\java\workflow\ExecuteSystemActivityRequestType.java
Return web\wwwroot\ws\java\workflow\ExecuteSystemActivityResponseType.java
Request structure
<executeSystemActivity>
<WorkflowID>?</WorkflowID>
<ActivityID>?</ActivityID>
</executeSystemActivity>
Request
ID # Required Description
WorkflowID X Workflow ID #
ActivityID X Activity ID #
Return
ID # Description
5.2.18.9 - newAssocDocument
Java class
Request web\wwwroot\ws\java\workflow\NewAssocDocumentRequestType.java
Return web\wwwroot\ws\java\workflow\NewAssocDocumentResponseType.java
Request structure
<newAssocDocument>
<WorkflowID>?</WorkflowID>
<ActivityID>?</ActivityID>
<DocumentID>?</DocumentID>
</newAssocDocument>
Request
ID # Required Description
WorkflowID X Workflow ID #
ActivityID X Activity ID #
DocumentID X Document ID #
Return
ID # Description
5.2.18.10 - newAttachment
Java class
Request web\wwwroot\ws\java\workflow\NewAttachmentRequestType.java
Return web\wwwroot\ws\java\workflow\NewAttachmentResponseType.java
Request structure
<newAttachment>
<WorkflowID>?</WorkflowID>
<ActivityID>?</ActivityID>
<FileName>?</FileName>
<FileContent>?</FileContent>
<UserID>?</UserID>
<AttachmentID>?</AttachmentID>
<AttachmentName>?</AttachmentName>
<Summary>?</Summary>
</newAttachment>
Request
ID # Required Description
WorkflowID X Workflow ID #
ActivityID X Activity ID #
UserID User ID
AttachmentID
Summary Summary
Return
ID # Description
5.2.18.11 - newChildEntityRecord
This method adds a record to the form entity descending from the workflow.
Java class
Request web\wwwroot\ws\java\workflow\NewChildEntityRecordRequestType.java
Return web\wwwroot\ws\java\workflow\NewChildEntityRecordResponseType.java
Request structure
<newChildEntityRecord>
<WorkflowID>?</WorkflowID>
<MainEntityID>?</MainEntityID>
<ChildRelationshipID>?</ChildRelationshipID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?</RelationshipAttributeValue>
</RelationshipAttribute>
</Relationship>
</RelationshipList>
</newChildEntityRecord>
Request
ID # Required Description
WorkflowID X Workflow ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
RelationshipID Relationship ID #
§ Date: YYYY-MM-DD
§ Hour: HH:MM
§ Boolean: 0 or 1
Return
ID # Description
5.2.18.12 - newWorkflow
Java class
Request web\wwwroot\ws\java\workflow\NewWorkflowRequestType.java
Return web\wwwroot\ws\java\workflow\NewWorkflowResponseType.java
Request structure
<newWorkflow>
<ProcessID>?</ProcessID>
<WorkflowTitle>?</WorkflowTitle>
<UserID>?</UserID>
</newWorkflow>
Request
ID # Required Description
ProcessID X Process ID #
UserID User ID
Return
ID # Description
5.2.18.13 - newWorkflowUpdateData
Java class
Request web\wwwroot\ws\java\workflow\NewWorkflowUpdateDataRequestType.java
Return web\wwwroot\ws\java\workflow\NewWorkflowUpdateDataResponseType.java
Request structure
<newWorkflowUpdateData
<ProcessID>?</ProcessID>
<WorkflowTitle>?</WorkflowTitle>
<UserID>?</UserID>
<EntityList>
<Entity>
<EntityID>?</EntityID>
<EntityAttributeList>
<!--Zero or more repetitions:-->
<EntityAttribute>
<EntityAttributeID>?</EntityAttributeID>
<EntityAttributeValue>?</EntityAttributeValue>
</EntityAttribute>
</EntityAttributeList>
<RelationshipList>
<!--Zero or more repetitions:-->
<Relationship>
<RelationshipID>?</RelationshipID>
<RelationshipAttributeList>
<!--1 or more repetitions:-->
<RelationshipAttribute>
<RelationshipAttributeID>?</RelationshipAttributeID>
<RelationshipAttributeValue>?
</RelationshipAttributeValue>
</RelationshipAttribute>
</RelationshipAttributeList>
</Relationship>
</RelationshipList>
<EntityAttributeFileList>
<!--Zero or more repetitions:-->
<EntityAttributeFile>
<EntityAttributeID>?</EntityAttributeID>
<FileName>?</FileName>
<FileContent>?</FileContent>
</EntityAttributeFile>
</EntityAttributeFileList>
</Entity>
</EntityList>
<AttributeList>
<!--1 or more repetitions:-->
<Attribute>
<AttributeID>?</AttributeID>
<!--Zero or more repetitions:-->
<AttributeValueList>
<AttributeValue>?</AttributeValue>
</AttributeValueList>
</Attribute>
</AttributeList>
</newWorkflowUpdateData
Request
ID # Required Description
ProcessID X Process ID #
UserID X User ID
· Date: YYYY-MM-DD
· Hour: HH:MM
· Boolean: 0 or 1
RelationshipID Relationship ID #
· Date: YYYY-MM-DD
· Hour: HH:MM
· Boolean: 0 or 1
AttributeID Attribute ID #
· Date: YYYY-MM-DD
· Hour: HHHH:MM
Boolean: 0 or 1
Return
ID # Description
Chapter VI
Update history
The table below describes the main changes made to this document.
16 2.0.10 Dec/11/2017
ð Update of the following interfaces:
§ Risk RISC ONTROL – C ontrol
§ Risk RISRISK – Risk
§ Asset ASTOEE - Insertion of parameter data to calculate OEE
§ Asset ASTSEC U - Asset type security import
§ PDM ITSEC U - Item type security import
§ Project PROFINANC E - Financial import
§ Administration disableUser
§ Administration ADMUSRC OMP - Full import of user data
ð Addition of interface of the following components:
§ Administration ADMEMPLOYEEPROF – Edits the employee profile data
§ Time control editNonProjectTaskC ost
§ Time control editNonProjectTaskRevenue
§ Time control executeNonProjectTask
§ Time control newNonProjectTaskC ost
§ Time control newNonProjectTaskRevenue
§ Performance addMeasuresInAdinterface
§ Project editProgramC ost
§ Project editProgramRevenue
§ Project editProjectC ost
§ Project editProjectRevenue
§ Project editProjectTaskRevenue
§ Project executeProjectTask
§ Project newProgramC ost
§ Project newProjectRevenue
§ Project newProjectTaskC ost
§ Project setRatAttributeValue
ð Update of the webservices of the following components:
§ Administration DeleteUserAcessGroup
ð Inclusão de web services dos seguintes componentes:
§ Administration updateEmployeeProfile
§ Physical file newPhysicalFileLoan
ð C hange in Interface data template:
§ Added new NMFIELDs columns (From NMFIELD76 to NMFIELD 101) and DSFIELD
columns (from DSFIELD06 to DSFIELD15).
ð C hange in Definition of the XLS file structure
§ Added the new columns of the Interface data template.
15 2.0.9 OCT/18/2017
ð Update of the following interfaces:
§ Risk RIC ONTROLATTRIBUTE - C ontrol attribute value
§ Risk RIRISKATTRIBUTE – Risk attribute value
ð Update of the following interfaces:
§ Asset ASTSEC U - Asset type security import
§ Asset ASTTYPE - Import of asset types
ð Update of the webservices of the following components:
§ PDM addSupplier
ð Interfaces of SE Generic have been moved to SE Administration: ADMTEAM and
ADMTEAMASSOC .
14 2.0.9 SEP/19/2017
ð Addition of the following interfaces:
§ Asset ASTPLANAC T - Activity plan import
§ C ompetence C PTREG - C ompetence
§ Asset import_attrib_assoc
§ SPC ImportSampleAtt
§ PDM addBom
08 2.0.5 Oct/24/2016
ð Interface update:
§ Project PROFINANC E - Financial import
ð Interface insertion:
§ SPC SPC SAMPC HANGESTATUS – C hange sample status
ð Web service inclusion:
§ SPC C hangeStatusSample
07 2.0.5 Oct/11/2016
ð Interface insertion:
§ Administration ADMATRPROFVL - Employee profile attribute value
ð Web service inclusion:
§ Administration addAttribProfileValue
06 2.0.4 Aug/23/2016
ð Interface insertion:
§ Survey SRVGUESTUSER - Guest respondent
§ Test TSTGUESTUSER - Guest respondent
ð Update of the following interface:
§ Inspection IPQUAL - Import of the inspection qualifications
§ Inspection IPREC - Receiving inspection
05 2.0.4 Jul/06/2016
ð Inclusion of interfaces MNMAINTMETER – Meter reading and MNMAINTVARIABLE –
Variable reading.
ð Inclusion of the web services of the SE Maintenance component.
ð Update of the AddAttribute web service.
04 2.0.3 May/17/2016
ð Inclusion of the web services of the SE Time control component.
ð Inclusion of note in the Integration via web services section.
ð Update of the PRORESOURC E - Resource values import interface.
03 2.0.2 Feb/25/2016
ð Inclusion of note in the Basic HTTP authentication section.
ð Update of the following interface:
§ Training TRREG - Training record
ð Inclusion of the following interface:
§ Maintenance MNMAINTC ORREC T – C orrective maintenance import
ð Inclusion of the web services of the following components:
§ Incident
§ Problem
ð Update of the web services of the following components:
§ Administration
§ Asset
§ C alibration
§ Document
§ Inspection
§ PDM
§ Workflow
02 2.0.2 Dec/03/2015
ð Update of the component interfaces:
§ Risks
ð Update of the web services of the following components:
§ Administration
§ Asset
§ C alibration
§ SPC
§ Generic
§ Inspection
§ PDM
§ Request
01 2.0.1 Nov/20/2015
ð Update of the following interfaces:
§ Administration ADMATR - Import of attributes
§ Asset ASTAST - Import of assets and ASTASTATT - Asset attributes import
ð Update of the web services of the following components:
§ Administration
§ Asset
§ Document
§ PDM
00 2.0.0 Sep/01/2015
ð C reation of the document from the "SE Suite 1.3 - Integration guide" document.
SoftExpert is a Market leader in software and services for enterprise-wide business process
improvement and compliance management, providing the most comprehensive application suite
to empower organizations to increase business performance at all levels and to maximize
industry-mandated compliance and corporate governance programs
Founded in 1995 and with more than 2,000 customers and 300,000 users worldwide, SoftExpert
solutions are used by leading corporations in all kinds of industries, including manufacturing,
government and public sector, pharmaceutical sector, hospitals and laboratories, financial
services, high tech and IT, education, energy and utilities, logistics, retail, services, among
others.
Along with its extensive network of resellers spread across all continents, SoftExpert also
provides hosting, implementation, post-sales support, and validation services for its solutions to
ensure that customers realize the maximum value from their investments.