120 User Guide — QAD EDI eCommerce
4409 Mandatory data field has not
been set: <subsystem>;
<exchange file name>;
<version>; <record sequence>;
<field name>; <file name>;
<error file>
Note: <filename> and
<error file> are not applicable
on outbound documents.
• The trading partner did not send
the data specified, or the SNF
file <filename> was not
complete.
• The data record field <field
name> for the <record
sequence> has been defined as
mandatory in the exchange file
document definition for the
<exchange file name>,
<version>, and direction when it
should be defined as optional.
• Have the trading partner
correct the problem and
resend the document.
• If this is a recurring error for
this exchange file name,
version, and direction, then
use Exchange Definition
Maintenance (35.15.6) to
select the appropriate
exchange file document
definition, go to the <record
sequence>, locate the <field
name>, and set Requirement
to Optional.
4410 Data field length outside
boundaries: <subsystem>;
<exchange file name>;
<version>; <record sequence>;
<field name>; <field length>;
<file name>; <error file>
Note: <filename> and
<error
file> are not applicable
on outbound documents.
EC subsystem is defined as using
variable-length fields. The number
of characters <field length> is not
within the minimum and maximum
values specified for the field.
Use Exchange Definition
Maintenance (35.15.6) to locate
the specified sequence number
<record sequence> for the
specified EC subsystem
<subsystem>, <exchange file
name>, <version>, and direction.
Locate the field name <field
name> for the record sequence
and adjust the minimum and
maximum values.
4411 EC Subsystem does not exist:
<subsystem>; <file name>;
<error file>
The specified EC subsystem
<subsystem> has not been defined.
• Use EC Subsystem Definition
Maint (35.13.1) to define the
subsystem and its control
codes.
• Use EC Subsystem/Exchange
Maint (35.13.3) to create the
data control codes.
4412 Unknown file format: <file
name>; <error file>
The file extension is used to
identify the subsystem name and
file format. If a subsystem cannot
be identified by the extension, then
the system attempts to locate the
subsystem definition of the default
subsystem defined in the control
program.
• Use EC Subsystem Definition
Maint (35.13.1) to define the
subsystem and its control
codes.
• Use EC Subsystem/Exchange
Maint (35.13.3) to create the
data control codes.
4413 Input control record is not in
sequence: <sequence number>
The SNF file was not complete. Have the trading partner correct
the problem and resend the
document.
4414 Exchange file record table record
does not exist: <exchange file
name>; <version>; <record
sequence number>
The record was deleted from the
exchange file document definition
after the EC subsystem/exchange
cross-reference was defined.
Use Exchange Definition
Maintenance (35.15.6) to
redefine the record sequence for
the specified exchange file name
and version.
4415 Current record sequence has
exceeded its loop occurrence:
<exchange file name>;
<version>; <record sequence>
There are more occurrences of the
record type within the data than
allowed by the exchange file
document definition.
Use Exchange Definition
Maintenance (35.15.6) to locate
the record sequence for the
specified exchange file name and
version. Increase the loop
occurrences allowed for the
record.
No. Message Cause Solution