Template Inbound (receive data)
In order for incoming ENGDAT messages to be recognized as such and not be processed by other OFTP profiles, an active template must exist.
(1) Communication channel from the Partner Administration. This is the OFTP channel that is checked when messages are received.
(2) This information must be contained in the logical OFTP file name of incoming files. The route (also address code or receiver identification) consists of 5 arbitrary characters and serves the internal distribution of the data at the receiver. For inbound templates, the route must be unique per OFTP partner channel (otherwise the template cannot be saved). The route determines which template is used when receiving ENGDAT messages and 'inherits' properties such as the retention time of the data, for example, from the template.
(3) For each ENGDAT message, a new subdirectory containing the received files is created under this base folder.
(4) If the checkbox is set, the message is automatically confirmed with a CC4 message. For this, a valid route must be defined in the partner contact data under Developer.
(5) If this checkbox is set, all OFTP channels of the selected partner and not only this selected channel will be accepted. This is useful if, for example, a partner company from different locations sends data.
(6) The retention time is the time in days after the message has been received completely and without error. Older messages and their files are deleted automatically.
(7) If you want to send a report or a notification for new messages or errors to specific people via email, specify the addresses here. Multiple recipients have to be separated with semicolons (;).
(8) Optionally, you can specify a profile (time-driven Input Agent of type File with Trigger), which receives the files for further processing. Two variables are passed that can be used in the profile: MSG_CALL_VAR_SYS_ENGDAT_DIR for the current path and MSG_CALL_VAR_SYS_ENGDAT_REF for the ENGDAT reference number.
(9) Only the selected users (that also have the user right ENGDAT) are allowed to view/edit the inbound and outbound ENGDAT messages. Important note: If you set checkbox Is exclude list in the subdialogue, then all users except the selected ones are allowed to see/edit.
'Vacuum Cleaner' Template
Incoming ENGDAT messages for which there is no route, i.e. no template, can be assigned to a 'vacuum cleaner' template. For this, you have to create a template with direction Inbound and route ?????. For this specific template, the following applies.
The template is always saved as version 3 because this template determines itself, whether it has to switch to version 2 when data is received.
The profile assignment is ignored.
The channel assignment is ignored. Instead, the channel that delivers the data will be used.
Acknowledgement of receipt (4) is deactivated.
Messages that are received via this template can be found on page Inbound.
File Pattern
For V2 messages, the file name is ENG resp. EN2 + <yyMMddHHmmss> + <route> + <number of technical documents> + <current file counter>. yy stands for the year, MM for the month, dd for the day, HH for the 24 hours format, mm for minutes, ss for seconds. A valid file name for a message, e.g. from 21.1.2013 14:30:00, consisting of 3 documents (+ meta information = 4) is ENG130121143000PART1004001.
For V3 messages, the file name is ENG resp. EN3 + <yDDDHHmmss> + <route> + <number of technical documents> + <current file counter>, where DDD stands for the day in the year. A valid V3 file name would be ENG3021143000PART100040001.