6.2.3 Messages specific to the InfoPackage control function and the process chain control function : Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference

KAJM2001-E

InfoPackage-ID or process-chain-ID cannot be omitted.

The required InfoPackage ID or process chain ID is not specified.

S:: The system aborts command execution.
O:: Specify the required InfoPackage ID or process chain ID and re-execute the command.

KAJM2002-E

In the release of the SAP BW system at the connection destination, this command is not supported. (release: release)

The executed command is invalid on the SAP BW system to which you want to connect.

For release in the message, the release of SAP Basis included in the connection destination SAP BW system is output.

S:: The system aborts command execution.
O:: Verify that the release of the SAP BW system at the connection destination supports the executed command.

KAJM2801-E

Cannot connect to the SAP BW system. (address: destination-name, host: host-name, system No.: system-number)

A communication error occurred when JP1/AJS3 for EAP attempted to establish an RFC connection with the SAP BW system.

Immediately after this message, a KAJM2802-E message appears indicating the name of the function where the error occurred and providing detailed information about the error.

The possible causes of the error are as follows:

The RFC connection information is incorrect (for example, the system number is incorrect and the host name cannot be resolved).
The SAP BW system is inactive.
The SAP BW system is too busy to accept an RFC request.
The network settings are incorrect.

S:

If retry is specified, the system attempts to reconnect to the SAP BW system.

If retry is not specified, the system aborts command execution.

O:

Consider specifying retry if no retry is specified (version 07-00 and earlier do not retry by default).

KAJM2802-E

Operation : function

detailed-information ...

An error occurred when the RFC API (communication function provided by SAP) was called.

A message appears that indicates the name of the function where the error occurred and detailed information about the RFC API error. The language used for the message depends on the language (-l option specification value) specified during the logon to the SAP BW system.

The meanings of the values in the message are as follows:

code: Integer for the RFC return code
group: Integer for identifying key
key: Code for identifying the error (127 bytes or less)
message: Text that describes the error (511 bytes or less)
abapMsgClass: ABAP message class (20 bytes or less)
abapMsgType: ABAP message type (1 byte or less)
abapMsgNumber: ABAP message number (3 bytes or less)
abapMsgV1: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV2: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV3: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV4: Detail field of the ABAP message (text of 50 bytes or less)

For these values, the values of the members in the RFC_ERROR_INFO structure are specified without changes. This structure stores RFC API error information. (For details about the RFC, see the manual for the SAP system.)

<Supplement>

This message is output as a detailed message of KAJM2801-E, KAJM2803-E, and KAJM2804-E.
The number of bytes for the detailed information about the RFC API error indicates the size in which \0 is not included.

S:

The system aborts command execution.

O:

Identify the cause of the error and correct the problem.

KAJM2803-E

A communication error occurred with the SAP BW system. (address: destination-name, host: host-name, system No.: system-number)

An error occurred when JP1/AJS3 for EAP called the RFC API (communication function provided by SAP).

Immediately after this message, a KAJM2802-E message appears indicating the name of the function where the error occurred and providing detailed information about the error.

The possible causes of the error are as follows:

The SAP BW system is inactive.
The SAP BW system is too busy to accept an RFC request.
The network settings are incorrect.

S:: The system attempts to reconnect to the SAP BW system if a communication error retry is specified. The system aborts command execution if no communication error retry is specified.
O:: Consider specifying retry if no retry is specified (version 07-00 and earlier do not retry by default).

KAJM2804-E

Cannot log on to the SAP BW system. (client: client, user: user-name, language: language-name)

A logon error occurred when JP1/AJS3 for EAP attempted to establish an RFC connection with the SAP BW system.

Immediately after this message, a KAJM2802-E message appears indicating the name of the function where the error occurred and providing detailed information about the error.

The possible causes of the error are as follows:

The RFC connection information is incorrect (for example, a non-existent user or an incorrect password is specified).
The user is locked out.
The user was not granted S_RFC permission correctly.
An extended password containing lower-case characters is defined in the SAP system based on SAP NetWeaver 7.0 and later, but connection information (the -p option or Passwd key of the r3defcon file) that does not correspond to the extended password is specified.

S:: The system aborts command execution.
O:: Check the SAP BW system logon information that was specified by the command.

KAJM2805-I

Now recovering connection with the SAP BW system. (address: destination-name, host: host-name, system No.: system-number, retry-time: retry-time-in-minutes min., retry-count: number-of-retries times)

The connection with the SAP BW system is now being recovered.

retry-time in the message is output when the RetryTime key specified in the command section of the environment setup file is valid. number-of-retries in the message is output when the RetryCount key in the command section of the environment setup file is valid.

S:: The system tries to reestablish connection with the SAP BW system. If reconnection is performed within the retry-time or number-of-retries limit, JP1/AJS3 for EAP continues command processing. Otherwise, the system aborts command execution.

KAJM2806-I

Connection was recovered with the SAP BW system. (address: destination-name, host: host-name, system No.: system-number)

Connection with the SAP BW system was recovered.

KAJM2807-E

Time-out occurred in the connection with the SAP BW system. (address: destination-name, host: host-name, system No.: system-number)

The connection with the SAP BW system could not be restored within the reconnection retry time.

S:: The system aborts command execution.
O:: Read the messages that are output before this message and the SAP BW system log to determine the cause of the error. Check whether the value of the retry count or the retry time (RetryCount key or RetryTime key in the command section of the environment setup file) is appropriate.

KAJM2808-E

This InfoPackage does not exist. (InfoPackage: InfoPackage-ID)

The specified InfoPackage is not defined in the SAP BW system.

S:: The system aborts command execution.
O:: Check whether the InfoPackage specified in the command is valid for the SAP BW system. If necessary, define the specified InfoPackage for the SAP BW system, and then execute the command again.

KAJM2821-I

The InfoPackage was started. (InfoPackage: InfoPackage-ID, request: request-number)

A request to start InfoPackage was successful and a request number was assigned in the SAP BW system. The InfoPackage request is registered on the SAP BW system side after this message is output.

JP1/AJS3 for EAP monitors completion of InfoPackage request registration and the end of execution according to the request registration monitoring time (default: completion monitoring time) and the completion monitoring time (default: unlimited) if completion monitoring is specified.

To check whether request registration is completed, use the administrator workbench of the SAP BW system.

KAJM2822-E

The InfoPackage cannot be started. (InfoPackage: InfoPackage-ID)

The specified InfoPackage could not be started.

S:: The system aborts command execution.
O:: Determine the cause by reading the messages displayed before this message as well as the SAP BW system log. If job XXX is not started (yet) appears in the detailed information of the KAJM0813-E message that appears before this message, the SAP BW system may have a problem. Check whether SAP Note 693703 has been applied to the connection destination SAP BW system. If not, apply it.

KAJM2823-I

Now monitoring InfoPackage-end. (monitoring time: monitoring-time-in-minutes min.)

InfoPackage execution completion monitoring has been started.

S:: The system continues with InfoPackage execution completion monitoring.

KAJM2824-E

InfoPackage-end monitoring is canceled because a timeout occurred. (InfoPackage: InfoPackage-ID, request: request-number)

InfoPackage completion monitoring is aborted because InfoPackage did not end within the monitoring time.

S:: The system aborts command execution.
O:: Use the SAP front-end software to check the status of InfoPackage. Abort execution of InfoPackage if necessary.

KAJM2825-E

Could not monitor InfoPackage-end. (InfoPackage: InfoPackage-ID, request: request-number)

InfoPackage completion monitoring failed.

S:

The system aborts command execution.

O:

Determine the cause by reading the messages displayed before this message as well as the SAP BW system log.

Use the SAP front-end software to check the status of InfoPackage. Abort the execution of InfoPackage if necessary.

If request XXX could not be generated appears in the KAJM0813-E message that appears before this message, a timeout error has occurred in registration monitoring of the data load request. Check whether the registration monitoring time value of the data load request (RequestMonitorTime key in the command section of the environment setup file) is appropriate.

KAJM2826-I

The InfoPackage has finished. (InfoPackage: InfoPackage-ID, request: request-number)

The InfoPackage has ended.

KAJM2827-E

Error occurred while executing the InfoPackage. (InfoPackage: InfoPackage-ID, request:request-number)

Detail: detailed-text

An error occurred during InfoPackage execution.

For detailed-text, a message appears indicating the error factor returned from SAP BW. The language used for the message depends on the language (-l option specification value) specified during logon to the SAP BW system.

S:

The system aborts command execution.

O:

Check the Details line to identify the cause of the error, and check the status of the InfoPackage with the SAP front-end software. Solve the problem and then execute the command again.

If Processing exceeded the specified time appears in detailed-text immediately after InfoPackage is executed, the SAP BW system may have a problem. Check whether SAP Notes 633981, 641466, 647855, and 655528 have been applied to the connection destination SAP BW system. If not, apply them.

KAJM2828-E

InfoPackage-end monitoring is canceled because a reconnection timeout occurred. (InfoPackage: InfoPackage-ID, request: request-number)

InfoPackage completion monitoring is aborted because the connection with the SAP BW system could not be restored within the reconnection retry time.

S:

The system aborts command execution.

O:

Read the messages that are output before this message and the SAP BW system log to determine the cause of the error. Check whether the value of the retry count or the retry time (RetryCount key or RetryTime key in the command section of the environment setup file) is appropriate.

Use the SAP front-end software to check the status of InfoPackage. Abort the execution of InfoPackage if necessary.

KAJM2829-I

Now waiting for the end of subsequent process of the InfoPackage. (waiting time: waiting-time sec.)

JP1/AJS3 for EAP delays termination of the command for the specified number of seconds (waiting time) set between the normal end of InfoPackage and the end of the job that executes InfoPackage.

S:: The system delays termination of the command for the specified number of seconds.

KAJM2841-I

The process chain was started. (process chain: process-chain-ID, log: log-ID)

The process chain has been started.

KAJM2842-E

The process chain cannot be started. (process chain: process-chain-ID)

The specified process chain does not exist or the definition is invalid.

S:

The system aborts command execution.

O:

Use the SAP front-end software to check the definition of the process chain.

Specify a correct process chain ID, and then re-execute the command. If the correct process chain is specified, use the SAP front-end software to check the definition of the process chain, correct any problems in the definition, and then re-execute the command.

KAJM2843-I

Now monitoring process-chain-end. (monitoring time: monitoring-time min.)

Completion monitoring for execution of the process chain started.

S:: The system continues startup of the process chain.

KAJM2844-E

Process-chain-end monitoring is canceled because a timeout occurred. (process chain: process-chain-ID, log: log-ID)

Monitoring is aborted because the process chain did not end during the specified monitoring time.

S:: The system aborts command execution.
O:: Use the SAP front-end software to check the status of the process chain. Abort execution of the process chain if necessary.

KAJM2845-E

Could not monitor process-chain-end. (process chain: process-chain-ID, log: log-ID)

Completion monitoring of the process chain failed.

S:

The system aborts command execution.

O:

Read the process chain log and the SAP BW system log to determine the cause of the error.

Use the SAP front-end software to check the status of the process chain. Abort execution of the process chain if necessary.

KAJM2846-I

The process chain has finished. (process chain: process-chain-ID, log: log-ID)

The process chain has ended.

KAJM2847-E

Error occurred while executing the process chain. (process chain: process-chain-ID, log: log-ID, status: status)

An error occurred during execution of the process chain. For status in the message, Completed but errors occurred or Cancelled is set.

S:: The system aborts command execution.
O:: Use the SAP front-end software to determine the cause of the process error indicated in the next message. Correct the error and then re-execute the command.

KAJM2848-E

message-class-message-number: message-text

JP1/AJS3 for EAP outputs the log (process chain log) that indicates the process containing the error returned from SAP BW.

The language used for the log depends on the language (-l option specification value) specified during logon to the SAP BW system.

S:: The system aborts command execution.
O:: Use the SAP front-end software to determine the cause of the process error indicated in the message. Correct the error and then re-execute the command.

KAJM2849-E

Process-chain-end monitoring is canceled because a reconnection timeout occurred. (process chain: process-chain-ID, log: log-ID)

Monitoring is aborted because reconnection was not performed during the specified reconnection retry time.

S:

The system aborts command execution.

O:

Read the messages that are output before this message and the SAP BW system log to determine the cause of the error. Check whether the value of the retry count or the retry time (RetryCount key or RetryTime key in the command section of the environment setup file) is appropriate.

Use the SAP front-end software to check the status of the process chain. Abort execution of the process chain if necessary.

KAJM2850-W

Failed to acquire a process chain log. (process chain: process-chain-ID, log: log-ID)

Acquisition of the process chain log failed.

S:

The system aborts command execution.

O:

Use the SAP front-end software to check the process where the error occurred.

Correct the error and then re-execute the command.

KAJM2852-E

message-class-message-number: message-to-be-inserted...

Conversion of the message text in the process chain log failed. The message shows the data (message-class, message-number, message-to-be-inserted) before the conversion.

S:: The system aborts command execution.
O:: Use the SAP front-end software (transaction SE91) to check the contents of the AP BW system message indicated in this message. Correct the error and then re-execute the command.