4400

<directory> listed in control program does not exist

4401

User does not have write privileges to <directory>

User other than system administrator created. directory

System administrator did not grant read, write, create, modify, and delete rights to all users for the specified directory.

Contact the system administrator. Users must have read, write, create, modify, and delete rights to the specified directory.

Change the directory location.

4402

Mandatory exchange file data record is missing: <subsystem>; <record name>; <exchange file name>; <version>; <filename>; <error file>

Note: <filename> and <error file> are not applicable on outbound documents.

4403

No matching quote found in record. <record> (first 5 characters); <file name>; <error file>

The EC subsystem is defined as variable-format with a quote character surrounding alphanumeric data. A beginning quote character was found without a matching closing quote.

Have the trading partner correct the problem and resend the document.

Open the error file in a text editor and locate the subject record. Insert the closing quote character at the end of the data field. Then, use Document Import (35.1) to import the error file.

4404

Duplicate <record code> records: <subsystem>; <filename>; <error file>

A control or data record is repeated within the document without the data information. A control record can only appear once for a document. Data records are expected to follow the control records and come before the next document’s control record.

Have the trading partner correct the problem and resend the document.

Open the error file in a text editor and locate the duplicate control records. Verify that the data within the records are the same. If they are the same, remove one of the control records and use Document Import (35.1) to import the error file.

4405

Mandatory control record is missing in input file: <record code>; <subsystem>; <direction>; <filename>; <error file>

4406

Unknown or blank record code: <record code>; <subsystem>; <file name>; <error file>

The EC subsystem sent a record code that has not been defined as a control code or a data control code.

Open the error file in a text editor and determine if this code is for a data segment or a control segment. Then, define the segment as required.

4407

Control field length outside boundaries: <subsystem>; <record sequence>; <field name>; <field length>; <file name>; <error file>

The EC subsystem is defined as using variable-format control field lengths. The number of characters <field length> is not within the minimum and maximum values specified for the field.

Using EC Subsystem Definition Maint (35.13.1), locate the specified sequence number <record sequence>. Select the field name for the appropriate record sequence and adjust the minimum and maximum values.

4408

Mandatory control field has not been set: <subsystem>; <record sequence>; <field name>; <file name>; <error file>

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.

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.

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.

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.

4416

Invalid document transmission group name: <transmission group name>

The specified transmission group has not been defined.

Use Transmission Group Maintenance (35.13.13) to define the transmission group.

4417

Destination dir/file prefix is blank for transmission group: <transmission group name>

The directory or file prefix for the specified transmission group has been left blank.

Use Transmission Group Maintenance (35.13.13) to add the missing information.

4418

Exchange file repository master record not found

Database corruption.

Contact database administrator.

4419

EC Subsystem control record does not exist: <subsystem>; <transmission group name>

Control record codes have not been defined for the subsystem.

4420

Repository detail record does not exist for sequence

Database corruption.

Contact database administrator.

4421

EC Subsystem cross-reference record not available for: <subsystem>; <document type>; <record sequence number>

Cross-reference was not set up completely, or a record sequence was added to the exchange file document definition after the cross-reference was set up.

Use EC Subsystem/Exchange Maint (35.13.3) to create the data control code.

4422

Record code is blank for data records: <subsystem>; <document type>; <record sequence number>

Cross-reference was not set up completely, or a record sequence was added to the exchange file document definition after the cross-reference was set up.

Use EC Subsystem/Exchange Maint (35.13.3) to create the data control code.

4423

Unable to create directory <directory> for transmission group: <transmission group name>

User other than system administrator created directory.

System administrator did not grant read, write, create, modify, and delete rights to all users for the specified directory.

Contact the system administrator. Users must have read, write, create, modify, and delete rights to the specified directory.

Change the directory location.

4424

Unable to create directory: <directory>

User other than system administrator created directory.

System administrator did not grant read, write, create, modify, and delete rights to all users for the specified directory.

Contact the system administrator. Users must have read, write, create, modify, and delete rights to the specified directory.

Change the directory location.

4425

Mandatory control token limits are not met: <subsystem>; <record sequence>; <field name>; <token>; <field length>

EC subsystem is defined as using variable-length fields. The number of characters <field length> is not within the range of minimum and maximum values specified for the field.

Use EC Subsystem Definition Maint (35.13.1) to locate the specified sequence number <record sequence> for the specified EC subsystem <subsystem>. Locate the field name <field name> for the record sequence and adjust the minimum and maximum values.

4426

Optional control token limits are not met: <subsystem>; <record sequence>; <field name>; <token>; <field length>

EC subsystem is defined as using variable-length fields. The number of characters <field length> is not within the range of minimum and maximum values specified for the field.

Use EC Subsystem Definition Maint (35.13.1) to locate the specified sequence number <record sequence> for the specified EC Subsystem <subsystem>. Locate the field name <field name> for the record sequence and adjust the minimum and maximum values.

4427

EC Subsystem control field records not found: <subsystem>; <exchange file sequence number>

An outbound subsystem has not been defined.

Use EC Subsystem Definition Maint (35.13.1) to define the subsystem and its control codes.

4428

Document status record does not exist:

Database corruption.

Contact database administrator.

4429

Invoice history header record does not exist: <invoice number>; <sales order number>

Database corruption.

Data may have been archived.

Contact database administrator.

4430

Trading partner location cross-reference does not exist: <document name>; <version>; <site>; <address>

Trading partner has not been set up properly.

4431

Implementation record does not exist: <document name>; <doc vers>; <imp name>; <imp vers>; <record sequence or record name>

Setup of implementation definition not complete.

The specified record has been deleted.

Use Implementation Definition Maint (35.15.13) to create the required record.

4432

Repository master record does not exist:

Database corruption.

Contact database administrator.

4434

Variable not found while obtaining variable name <variable name> <variable type>

Variable defined for transformation is no longer available to transformation process.

Verify that definitions exist in the exchange or implementation definition records. If they exist, delete them and recreate them. If they do not exist, create them in the exchange or implementation definition records, then delete them.

4435

Variable not available to be set: <recid of variable>

Variable defined for transformation is no longer available. Possibly, it was deleted before loading the transformation definitions.

Restart the transformation. If it still does not work, contact database administrator to report possible data corruption.

4436

Variable not available while obtaining variable value: <recid of variable>

Variable defined for transformation is no longer available. Possibly, it was deleted before loading the transformation definitions.

Restart the transformation. If it still does not work, contact database administrator to report possible data corruption.

4437

Variable has not been assigned a value: <variable name> <variable qualifier>

Variable within transformation has not been assigned a value or initialized.

Verify that the variable <variable name> has been assigned a value before using it as a source for another target variable.

4438

Function or variable is not available: <variable/function name> <variable qualifier>

Value for function or variable did not return a valid value.

Correct the returning value from the function program or verify that the function program compiled properly.

4439

Value not available for variable: <variable/function name> <variable qualifier>

Value for function or variable did not return a valid value.

Transformation definition is requesting a value from a variable, but variable has not yet been assigned a value. Assign the variable as a target before using it as a source.

4440

Function not found: <function name>

Function defined within the transformation definitions does not exist within function definitions.

Check function definitions for the function requested from the transformation definition map. If the record exists, contact database administrator. Otherwise, create the record being requested.

Note: If the function has been saved to disk already and the function definition has been removed, do not reprocess it to the disk. This action overwrites the program currently on the disk.

4441

Function returned error: <returned value set by function>

Function did not perform correctly and was not able to return a value.

4442

Illegal target qualifier found: <target qualifier that is illegal>

An invalid target qualifier was mistakenly entered or allowed in transformation definitions.

Change the target qualifier to a valid target qualifier (I, O, or V). All others are considered illegal.

4443

Sequence number not processed <sequence number>

Either no repository exists, no trading partner information exists, or no map exists.

4444

Function has not been processed to disk: <function name>; <internal function name)

Transformation process tried to run the function from the disk and the program was not found.

4445

BILL-TO does not exist in address master <bill to address>

The application document repository has a BILL-TO address that has not been defined.

Use Customer Address Maintenance (2.1.1) to define the customer bill-to address.

4449

Sequence number not set from conditional write function

The conditional write function check-hash did not return a valid sequence number.

Note: The check-hash function is used only to write master records; for example, a new application document such as an order header or schedule header. This function is not used for lower data record writes. Use IF logic to perform lower-level conditional writes.

4450

Invoice history detail record does not exist: <invoice number>; <sales order number>

Database corruption.

Data may have been archived.

Contact database administrator.

4451

Turnaround Mapping record does not exist: <document name>; document version>;<Implementation name>;<Implementation version>;<record sequence>;<field name>

The implementation definition does not have a Table Name and Index Name specified for a field with Src/Dest set to T.

Use Implementation Definition Maint (35.15.13) to add the missing information.

4452

Field(s) # cannot be blank

Blank field number.

Enter field number.

4453

Control record cannot be deleted

The control record is being used and therefore cannot be deleted.

Remove all references to the control record before deleting.

4454

Invalid default subsystem

Subsystem has not been defined.

Enter a valid subsystem set up in EC Subsystem Definition Maint (35.13.1).

4455

Directory does not exist: <directory name>; attempting to create

Warning issued when specifying directory path names in eCommerce Control and Transmission Group Maint.

If you want to use this path, ignore warning. If incorrect, manually delete unneeded directory and modify path as needed.

4456

Positive/negative integer expected from check-hash function: <returned value>

The write function was called with a function that returned an invalid sequence number.

Verify that the conditional write is on a record defined as sequence number 1. Also verify that the function being used is the check-hash function.

4460

Additional error message can be found in <file name>

Errors were discovered after control was passed to the gateway program. Error messages have been captured and written to <file name>.

Open the file with a viewer or editing program and review the error messages.

4464

Processing flat file. Please hold.

Normal status message during an EDI session and is for information only.

No action necessary.

4465

Transformation occurring. Please hold.

Normal status message during an EDI session and is for information only.

No action necessary.

4466

Processing application documents. Please hold.

Normal status message during an EDI session and is for information only.

No action necessary.

4469

No matching else or endif within record seq <record sequence> and action type <event type>

An If statement used in transformation did not have an Else or closing Endif statement within the record sequence and event type.

Use Transformation Definition Maint (35.15.17) to change the transformation definitions to include a closing Else or Endif within the same record and event type.

4470

Else with no matching if within record seq <record sequence> and action type <action type>

An Else statement used in transformation did not have an If beginning statement within the record sequence and event type.

Use Transformation Definition Maint (35.15.17) to change the transformation definitions to include a beginning If within the same record and event type.

4471

No closing endif within record seq <record sequence> and action type <action type>

An If or Else statement in the transformation definitions is not closed by an Endif statement within the record sequence and event type.

Use Transformation Definition Maint (35.15.17) to change the transformation definitions to include a closing Endif within the same record and event type.

4472

No invoices were exported

One or more invoices were selected on the invoice export that were unable to cross-reference the site and address to retrieve a valid implementation file name and version number.

Check the following intruding Partner Parameter Maint (35.17.10) for the address and site of the invoice being exported:

In addition, check to see that the address and site are entered in the correct Trading Partner Maintenance (35.13.7) record.

4473

Code does not exist in validation codes table <document name>;<document version>;<implemention name>;<implementation version>;<record sequence>;<field sequence>;<field name>

The implementation definition has Validate set to Yes for this field name and the code has not been defined in Data Validation Maintenance (35.13.21).

Do one of the following:

4474

Cannot delete record; related record found in # # #

This error is displayed while trying to delete a record or field in Exchange Definition Maintenance,
Application Definition Maintenance or Implementation Definition Maintenance when it is being used in a transformation map.

Delete the record or field from the transformation map.

4475

A seq in a many-to-many list failed. All sequences were deleted: <list of bad sequences>

A map defined as many-to-many had either a single or multiple document sequence fail, which caused all of the related input documents to fail.

Correct the error in the failed document, then reprocess the files as a group.

4477

<file name> file record cannot have 2 records with the same name

When entering a file definition the record names within the file must be unique.

If duplicate record names occur in a file, the record name must be unique. But it can be cross-referenced in EC Subsystem/ Exchange Maint (35.13.3) to the same record code using the Break Level field.

4478

Cannot delete exchange file record; used in map:

Exchange file definition is being used in an active transformation map; deletion is not allowed.

Definition can only be deleted if it is not in use.

4479

No files to process.

This error message is displayed under one of the following conditions:

Make sure that SNF flat file exists in the inbound directory and that Exchange Document Status / Application Document Status records exists for reprocessing.

4480

No files selected, procedure canceled

This error message is displayed when no files are selected during Document Import (35.1) or when no sequences are selected using Import Reprocessing (35.9.21), Export Reprocessing (35.9.23), or Session Report (35.7).

Make sure that SNF flat files are selected during Document Import, and that Exchange / Application Document sequences are selected during import/export processing and session report.

4481

<function name> function not defined

A function name has been used that has not been defined.

Define function in 35.15.21 eCommerce Function Maint

4482

<##> not found. Press down arrow to get selection

This error message is displayed in Transformation Definition Maintenance (35.15.17) when no action type (read, write, and so on) is specified in the Type field.

Make sure that at least one action type is selected before leaving the Type field.

4483

Trading Partner name cannot be blank.

A valid trading partner name must be entered

Enter a valid trading partner name.

4484

Cannot use target qualifier <qualifier> with action type <action type>.

This error message is displayed when action types such as Read, Clear, Write, New, Loop, Loopend, Repeat, Repeatend, Else (without If) are selected, and when the Target Qualifier is not O (output) or I (Input).

Make sure that the record or field from Input or Output is selected.

4485

Cannot find Trading Partner record.

This error message is displayed in Data Cross-Reference Maintenance (35.13.16) when an entered Trading Partner ID does not exist.

Make sure that the entered Trading Partner ID exists in Trading Partner Maintenance (35.13.7).

4486

Document definition does not exist.

Invalid application document definition name.

Use correct application document name or add using Application Definition Maintenance (35.15.10).

4487

Document record definition does not exist.

Invalid application document record name.

Use correct application document record name OR add the record to the application document definition using Application Definition Maintenance (35.15.10).

4488

File <gateway program name> not found for gateway document: <document name> version: <document version>

This error message is displayed when the Gateway Report Program specified in Application Definition Maintenance (35.15.10) is blank.

Make sure that the proper Gateway Report Program is specified in Application Definition Maintenance.

4489

Document field definition does not exist.

Invalid application document field name.

Use correct application document field name or add the field using Application Definition Maintenance (35.15.10).

4490

Function cannot contain spaces.

Function name with spaces.

Remove spaces from function name.

4491

Data type not defined. Must be AN, I, R, D, or L.

Invalid data type entered.

Enter valid data type—AN, I, R, D, or L.

4492

Process function to disk?

This prompt displays when a new function has been defined in eCommerce Function Maintenance (35.15.21).

4493

Sequence value of <sequence value> is not numeric. It will be discarded.

This error message is displayed in various programs.

Specify a numeric value when using these functions.

4494

Processed function <function name> to disk

This status message displays when a new function has been defined in eCommerce Function Maintenance (35.15.21) and you have answered Yes to the Process to disk prompt.

No action needed; message indicates that the .p program source code has been written to the user function directory with the name of the function. To make the function operational, add logic to the code that calculates the return value.

4496

Enter the data type for new # variable (#)

This prompt displays when a new variable has been specified in Transformation Definition Maint (35.15.17).

Enter the data type for the new variable: AN, I, R, D, or L.

4497

BILL-TO does not exist in address master <bill to address>

The application repository has a BILL-TO address that has not been defined.

Use Customer Address Maintenance (2.1.1) to define the customer bill-to address.

4498

Document record <document sequence number> skipped; not supported.

This error message is displayed during Shipment ASN Export (35.4.1) when Implementation Definition Maint (35.15.13) has record names other than the following: HDR, HDR-EXT, HDR-USER-FLDS, CTR-USER-FLDS, ITM, ITM-EXT, ITM-USER-FLDS, CTR-DATA, ITM-CHARGES, CTR-ITEM-LID, TARE-HDR, TARE-DET, ITM-SEQ, ITM-SUMM, CTR-SUMM, CTR-TARE-SUMM, and PLT-SUMM

Use only valid record names when setting up implementation definitions for outbound ASNs.

4700

Status record in use: <record id>

This error message is displayed when during Shipment ASN Export (35.4.1) the sequence in the
application document status master record is locked by another user.

This check is done as a precautionary measure. This situation does not arise in a normal condition.

4701

Turnaround data repository does not exist

This warning message is displayed when the QAD-defined function GetTadData is unable to locate a turnaround data record for the passed parameter.

Make sure that turnaround data exists in the turnaround data repository master table for the data passed as parameters.

4702

Schedule has not been printed

Status message information only

No action.

4703

Implementation record does not exist: <document name>;<document version>;<implementation name>;<implementation version>

Invalid implementation record name.

Use correct implementation record name or add using Implementation Definition Maint (35.15.13).

4704

Sequence <sequence number> is invalid for reprocessing.

Reprocessing EDI and this record cannot reprocess.

Rerun the EDI import or export process to reprocess this record.

4706

Sequence <sequence number> does not exist

This error message is displayed during import or export reprocessing when an entered application document sequence does not exist in the application document status table.

Enter a valid application sequence.

4707

Map does not exist with name: <map name>

The trading partner setup has specified a Document Map (transformation definition name) that does not exist.

For the document type and trading partner being processed, enter a valid Document Map name in Trading Partner Maintenance (35.13.7).

4708

Two parameters within same function cannot have the same name

When entering the parameter names in EC Function Maintenance (35.15.21), each parameter name must be unique.

Correct the parameter name being entered.

4709

Function exists on disk! Overwrite?

Creating a new function where the .p program for the function exists in the user’s function directory.

Answering Yes to this prompt causes the system to overwrite the .p function program in the user’s function directory with the newly created shell .p program. Answer No and enter a new function name to keep the existing .p program.

4710

Function name cannot be blank

Blank function name

Enter a function name.

4711

<definition record name> Definition record does not exist

The file definition record name that has been entered cannot be found.

Enter a valid file definition record name

4712

Please confirm delete of EC Subsystem/Exchange File Cross-Ref

Warning message prompt.

Enter Yes to delete.

4713

Transformation Function does not exist

A function name has been used that has not been defined.

Define function in eCommerce Function Maint (35.15.21).

4714

Record Code <record code> already exists

A record code that has already been used cannot be entered.

Entering a different Break Level allow sduplicate record codes.

4715

Record Name already exists

Record Name must be unique

Enter unique record name.

4716

Field Name already exists

Field names must be unique within a record.

Enter unique field name.

4717

Please confirm delete of Control Record Fields

Confirmation prompt.

Enter Yes to proceed with the deletion.

4718

Invalid token name

Name entered is not a valid token name.

Enter a valid token name.

4719

Cannot flush record until header record has been flushed.

The header record must always be the first record written. Attempting to write another record before the header results in this message.

Correct the transformation write logic.

4720

Variable <variable name> cannot be source; has not been targeted for update

Using a variable as a source before it has a value assigned to it.

Correct the transformation to initialize the variable before using it as the source in an event action statement.

4721

Adding new control record field

Message

Status message

4722

Adding new control record

Message

Status message

4723

Invalid number of characters in record code

The value entered for the record code has exceeded the specified record code length.

Enter an allowable record code or expand the allowable length of the record code in the EC Subsystem Definition Maint (35.13.1).

4724

Record code length must be between 1 and 4

The record code length entered is greater than the field length limit.

In eB2 and later the record code field length is expanded to 20.

4725

Cannot delete a Qad designed function: #

Attempting to delete a QAD-provided function.

Deleting a QAD function is not allowed.

4726

Cannot change File Name or Version

Attempting to change a file name or version is not allowed.

Cannot change file name or version.

4727

Order does not exist for incoming schedule: <Ship from>;<ship to>;<item>;<PO>

Schedule load EDI gateway cannot find scheduled order for this incoming release

Enter order for this ship-from/ ship-to for item/PO in Customer Scheduled Order Maintenance (7.3.13).

4728

Record code is blank for control record: <subsystem>; <direction>; <record sequence number>

The specified EC subsystem <subsystem> has not been defined.

4729

Mandatory data record is missing: <document name>; <document version>; <implementation name>; <implementation version>; <record name>

4730

Data field length outside boundaries: <document name>;<document version>;<implementation name>;<implementation version>;<record sequence>; <field name>;<field length>

The data in <record sequence> is greater than the maximum allowed in the implementation definition for the specified field.

Correct the invalid data or change field length in Implementation Definition Maint (35.15.13).

4731

Created <directory name> successfully

Status message

Information only

4732

Master table locked, document not processed

This error message is displayed when during the export of the following gateways, the sequence in the Application Document Status Master record is locked by another user:

This check is done as a precautionary measure. This situation does not arise in a normal condition. If this message displays, make sure that no other process or user is locking this record.

4733

Data field length outside boundaries: <document name>;<document version>;<implementation name>;<implementation version>;<record sequence>; <field name>;<field length>

The data in <record sequence> is greater than the maximum allowed in the implementation definition for the specified field.

Correct the invalid data or change field length in Implementation Definition Maint (35.15.13).

4734

Loop occurrence must be 1 or greater

This error message is displayed in the following programs when the Loop Occurrence value of the current record is less than or equal to zero:

Make sure that the Loop Occurrence of the current record is greater than or equal to zero.

4735

End loop cannot be less than current loop sequence

This error message is displayed when adding a record using the following programs if the Loop End Sequence of the current record is less than the Record Sequence:

Make sure that the Loop End Sequence of the current record is greater than or equal to the Loop End Sequence.

4736

Directory does not exist: <directory name>; Create it?

Control program is initially doing setup or the specified path is incorrect.

Use one of the following methods:

4737

Transmission group name cannot be blank

Blank transmission group is not allowed for outbound documents.

Enter a valid transmission group name.

4739

Extension already defined

The file extension must be unique for each EC Subsystem.

Enter a unique file extension.

4740

Exchange file document status record does not exist

This error message is displayed when the Sequence Number entered in Exchange Doc Status Inquiry (35.9.1) does not exist in the Exchange Document Status Master table.

Enter a valid Exchange Sequence.

4742

Distribution dump file created

Status message

Status message

4743

Transformation definition <transformation definition> flagged as nonrunnable

The transformation definition record has the Can Run field set to No.

In Transformation Definition Maint (35.15.17), change the transformation definition by setting Can Run to Yes.

4745

Exchange file definition does not exist

The exchange file definition name cannot be found.

Enter valid exchange file definition name.

4746

Minimum length greater than maximum length

Entering a minimum field length that is greater than the maximum field length is not allowed.

Change either the minimum or maximum length to allowable range.

4747

Cross reference already exists

Cross-reference must be unique.

Enter a unique cross-reference.

4748

Variable <variable name> could not be validated with the value <value>

This error is displayed when transformation processing tries to validate the data written to a field by looking up in EDI eCommerce Validation Master (edval_mstr). This validation is done when a Write is performed in an inbound document and when a Read is performed on an outbound document.

Make sure that validation codes are set up correctly in Data Validation Maintenance (35.13.21).

4749

Trading partner parameter does not exist for site <site id> / address <address id>

The system is unable to find a parameter record for the trading partner.

An abnormal situation, because Trading Partner Maint (35.13.7) automatically creates the trading partner parameter record when the site and address are entered.

Delete the site and address entry in Trading Partner Maint, then reenter the line to create a TP parameter record. Go to Trading Partner Parameter Maint (35.13.10) to verify that the record has been added.

4750

Trading partner parameter states document should not be exported

At least one of the documents that have been selected for export does not have the trading partner parameter set to Yes for exporting the specified document type.

Using Trading Partner Parameter Maint (35.13.10) to ensure that the export parameters have been set to Yes to allow the EDI export.

4751

Using default shipment document: Shipping Notice

Normal status message

Normal status message

4752

Document definition is not defined correctly # / #

This error message is displayed when the application document definition record does not exist.

Make sure that application document definition being used does exist in Application Definition Maintenance (35.15.10).

4753

Skipping Shipment <shipment number>

The ASN export is skipping this shipper for export because the Trading Partner Parameter not being set properly to export ASN for this site / address.

Can be a normal situation if shippers are selected for export that should not be exported. Correct the Trading Partner Parameter 35.13.10 setup if shippers are being skipped that should be exported.

4754

Using default invoicing document: Invoice

Normal status message

Normal status message

4755

Skipping Invoice <invoice number>

The Invoice export is skipping this invoice for export because a trading partner parameter is not set to export invoices for this site/address.

Can be a normal situation if invoices are selected for export that should not be exported.

If this is not the case, correct the Trading Partner Parameter (35.13.10).

4756

Implementation does not exist:

The implementation file definition specified in the transformation definition (document map) does not exist

Correct the implementation file specification. In Transformation Definition Maintenance (35.15.17), make sure that the Implementation file name and version number are the same as an entry in Implementation Definition Maintenance 35.15.13. The application document definition must also be the same

4757

Function returned warning: <warning description>

Transformation has called a function that has encountered an error that is not fatal and returns a warning with a description of the error condition.

Analyze the warning description to determine any corrective action if necessary.

4761

Document HEADER record does not exist:

Reference from the status table to an application header record has failed.

Normally this is a problem with exporting a document. Check the application definition and version being used in TP Parameter setup. Try re-exporting.

4766

Record written out of sequence

This is displayed when an error occurs while creating records in Application Data Repository Detail table; for example, when trying to create duplicate records in
Application Data Repository Detail. This situation should not happen in a normal environment. This is done just as a precaution.

Correct the transformation logic.