Status Codes for Configuration Category

For the Configuration category, status codes have the Debug, Error, Info, and Warn roles.

Error Codes

The status codes of the Error role and the corresponding resolutions are listed in the following table:

Status Code Resolution
AER3-000123

Cannot get class descriptions for data record of IDoc class %1

Ensure that you have downloaded the class descriptions.
AER3-000125

Class descriptions cannot be obtained for received IDoc tree

Ensure that you have downloaded the class descriptions.
AER3-000126

%1 is not of a sequence type

Check the configuration of the sequence type.

The named sequence does not have a valid definition.

AER3-000127

Sequence %1 does not have a contained class description

A sequence is a sequence of objects of type T. The adapter could not determine T, probably because the definitions don’t exist in the configuration.
AER3-000128

Sequence %1 for the segment holder could not be obtained

Check the configuration and ensure that a valid definition exists for the named sequence.
AER3-000129

Segment %1 does not have attribute: %2

The data mentioned contains the named attribute, but the class definition does not. Check the configuration and how the IDoc is being created.
AER3-000130

Cannot obtain field class description for IDoc Segment

Check configuration.
AER3-000132

Cannot obtain class description for segment %1 attribute %2

Check the segment name and the attribute, and ensure that a definition exists in the configuration.
AER3-000137

The %1 record of the IDoc does not have a valid class description

Check the data first. Make any changes. Check the configuration for an appropriate definition.
AER3-000145

The class descriptions for IDoc base classes cannot be obtained from the registry

Ensure that you have downloaded the class descriptions.
AER3-000203

No class definition exists for %1

Check whether a valid class exists with that name in the repository .
AEADR3-600007

Absolute Path not Found. Field %1, Palette error. Unable to find specified absolute path. Make sure that you have specified the absolute path correctly

Check the absolute path of the Plugin directory.
AEADR3-600011

Error copying Configuration information/Inbound Connection Type does not support copying of connection information from Configuration view

Change the default type of client connections to Dedicated. Then you can use Design-Time parameters as the runtime parameters.
AEADR3-600012

Illegal Adapter Instance Name. Adapter Configuration names must have only alphanumeric characters with no embedded spaces and can be up to 80 characters long. Type in a valid name

Ensure you follows the following naming rules of the adapter configurations when rename adapter configurations:
  • Only alphanumeric characters
  • No more than 80 characters
  • No blank spaces
AEADR3-600013

Subject Names. Do you wish to regenerate subjects set to previous defaults?

Click YES to regenerate.
AEADR3-600016

Illegal Operation/The new nested name is in conflict with the name of the resource you are editing. Rename the existing resource or choose a different name

Rename the existing resource with a name different from the new nested name.
AEADR3-600023

Invalid Value. Field %1, Palette error. This is not a valid value

Enter a valid value in the field.
AEADR3-600024

Invalid Value. Palette error. Endpoint Reference cannot have null value

Specify a valid endpoint reference.
AEADR3-600028

Illegal Operation. Selected Resource Can Not Be Moved

No resolution.
AEADR3-600044

Error while pasting. Deserialization of R3 Connections Failed

Copy and paste connections again.
AEADR3-600045

Error while writing the Meta Url

Rewrite the Meta Url again.
AEADR3-600050

Not Checked out. Failed to update Schema. The associated Schema files are not checked out from source control

Check out schema files from the source control.
AEADR3-600051

Illegal child error occurred while processing connection - %1

Try the failed configuration again.
AEADR3-600052

Name conflict error occurred while processing connection - %1

Try the failed configuration again.
AEADR3-600053

Error occurred while applying changes to connection - %1

Try the failed configuration again.
AEADR3-600054

Not Checked out. Failed to update R3Connections. The connection file is not checked out from source control

Check out the connection file from source control.
AEADR3-600055

Error Renaming Service. Service name must only have alphanumeric characters and must be at most 80 characters long

Ensure you follows the following naming rules of the adapter configurations when rename adapter services:
  • Only alphanumeric characters
  • No more than 80 characters
  • No blank spaces
AEADR3-600056

Global Variables File:Read-Only. Global Variable files needs to be checked out in order to successfully create the adapter

Check out the Global Variables file from source control.
AEADR3-600057

Error During Rename : Read-Only File. The resource %1 could not be renamed. Rename requires the %2 should be checked out. Check out the resource and try renaming again. You can select the resource to be checked out by clicking on the Go To Resource button

Check out the resource and try renaming it again.
AEADR3-600058

Error During Delete : Read-Only File/The resource %1 could not be deleted. Delete requires the %2 should be checked out. Check out the resource and try deleting again. You can select the resource to be checked out by clicking on the Go To Resource button

Check out the resource and try deleting it again.
AEADR3-600059

Error During Creation of Service : Read-Only File. The service can not be created. Creation requires the %1 should be checked out. Check out the resource and try creating the service again. You can select the resource to be checked out by clicking on the Go To Resource button

Check out the resource and try creating the service again.
AEADR3-600062

RFC/BAPI: %1: Invalid parameter: %2, (%3) data type not allowed. Remove selection

When downloading a RFC/BAPI containing parameters referring to a table, complex, or nested type remove the selection. If this RFC/BAPI is required, create a custom module and use the internal tables and flat structures.

Debug Codes

The status code of the Debug role and the corresponding resolution are listed in the following table:

Status Code Resolution
AER3-DEBUG-CONFIGURATION

%1

Debug messages generated during the loading of configuration by the adapter. No action required.

Info Codes

The status codes of the Info role and the corresponding resolutions are listed in the following table:

Status Code Resolution
AER3-000007

Management is local

It is good practice to use a remote Manager when multiple adapter services are running in a load-balanced fashion to ensure that the failed transactions are not executed twice among the load-balanced group. When multiple adapter services are running in a load-balanced fashion and TIDManagement is set to local, duplicate messages are transferred occasionally.
AER3-000090

The Destination %1 in not defined, IDoc is logged to file %2

Indicates normal adapter operation. No action required.
AER3-970032

Server connection pool: gatewayHost=%1 gatewayService=%2 programID=%3 updated successfully, connection count=%4

The Hawk method, setInboundThreadPool, is invoked successfully. No action required.
AER3-970034

Client connection pool name: %1 updated successfully, connection count=%2

The Hawk method, setInboundThreadPool, is invoked successfully. No action required.

Warn Codes

The status codes of the Warn role and the corresponding resolutions are listed in the following table:

Status Code Resolution
AER3-970028 L

ogging being defaulted to SDK due to error:%1

Check whether the Log4j file exists and is correct.

The adapter is configured to use the extended logging, but error occurs in the Log4j file specified by the TRA property, adr3.trace.log4j.properties.

AER3-970030

Log4j logging refreshed from properties file: %1

The adapter is configured to use the extended logging, and the Hawk method, refreshExtendedLogging, is invoked. No action required.