STMINPUTEVENT - Input event import

This import template allows inserting:

• Input event data.

For the insertion of each one of these items, the standard documented below must be followed.

Insert

Column	Required	Type	Precision	Description
OIDINTERFACE	X	TEXT	32	Primary key - Identifies an item to be imported into SoftExpert Suite.
FGIMPORT	X	NUMERIC	2	Import status: 1 - New; 2 - In progress; 3 - Finished; 4 - Error.
CDISOSYSTEM	X	NUMERIC	10	Code of the system for which the integration will be performed: 180 - Code of the SoftExpert Storeroom component.
FGOPTION	X	NUMERIC	2	Code of the operation to be performed: 7 - Insert new input event.
NMFIELD01	X	TEXT	255	Event ID #.
NMFIELD02	X	TEXT	255	Requester type: 1 - Department; 2 - User; 3 - Supplier; 4 - Process activity.
NMFIELD03	X	TEXT	255	Issuer ID #, according to the previous type
NMFIELD04		TEXT	255	Activity ID # Note: Required only when the requester type is process activity.
NMFIELD05		TEXT	255	Source responsibility ID #.
NMFIELD06		TEXT	255	Source date.
NMFIELD07		TEXT	255	Storeroom ID #.
NMFIELD08		TEXT	255	Destination responsibility ID #.
NMFIELD09		TEXT	255	Destination date
NMFIELD10		TEXT	255	Approval route ID #.
DSFIELD01		TEXT	4000	Event description.
DSFIELD02		TEXT	4000	Attribute value. Information required if the attribute value is of the MEMO type. Example: identifier_of_attribute1=value_of_attribute1; identifier_of_attribute2=value_of_attribute2; identifier_of_attribute3=value_of_attribute3. Example with a multivalued attribute: identifier_of_attribute1=value1_of_attribute1, value2_of_attribute1, value3_of_attribute1 Note: For attributes with a numeric value, the decimal place separator must be ".". For date fields, the value must have the “Y-M-D” (Year-Month-Day) format.