Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference

8.3.2 Trouble related to the InfoPackage control function or the process chain control function

This subsection explains problems that may occur while you are using the InfoPackage control function or the process chain control function.

Organization of this subsection

(1) Trouble with connection to the SAP BW system

(2) Trouble with InfoPackage control

(3) Trouble with process chain control

(1) Trouble with connection to the SAP BW system

This section deals with the trouble that may occur with the connection to the SAP BW system.

If you cannot find the cause of a problem here, the problem may be caused by the RFC API provided by SAP. If detailed information about the RFC API error is output in a KAJM2802-E message, collect the information and contact the SAP BW system administrator.

(a) The SAP BW system cannot be connected or an error occurs during the communication with the SAP BW system.

The probable causes are described below.

• The SAP BW system definition information is incorrect.
  First, check whether the specified SAP BW system IP address (or host name or SAP router address) is valid. If the specified IP address is invalid, specify a valid IP address and reconnect the SAP BW system.
  If the specified IP address is valid, there may be a problem with the setup. Check whether correct setup data was entered.
  
• The communication port is defined incorrectly.
  Check whether a port number corresponding to the system ID is defined in the services file. If no port number corresponding to the system ID is defined in the services file, define a port number that corresponds to the system ID.
  
• A temporary communication error has occurred.
  A temporary communication error may have occurred because the network load was increased or no more communication ports were available. You can resolve a temporary communication error and restore the connection with the SAP BW system by retrying.
  If retries are not specified for communication errors, use the RetryCount key or the RetryTime key in the command section of the environment setup file to execute retries.
  

(b) Logon to the SAP BW system fails.

The probable causes are described below.

• The user information for logging on to the SAP BW system is incorrect.
  Check whether the user information (client number, user name, and password) entered in the logon process is valid for the SAP BW system. If the user information entry for logon is invalid, log on again to the SAP BW system using user information valid for the SAP BW system.
  
• The specified user is not authorized to log on from an external system.
  Use either of the following procedures to acquire authorization to log on from an external system.
  
  • Log on again with the name of a user who is authorized to log on from an external system.
  • Ask the SAP BW system administrator to grant authority to log on from an external system.
• The release of the SAP BW system you attempted to log on to is not valid.
  Check whether the release of the SAP BW system you tried to log on to is a supported version.
  

(2) Trouble with InfoPackage control

This subsection describes the problems that may occur while you are controlling InfoPackage.

If you cannot find the cause of a problem here, the problem may be caused by the external management interface provided by SAP. If a KAJM0812-E message appears, a problem with the external management interface is likely. Obtain the name of the function of the external management interface with the problem and the exception code from the message, and contact the SAP BW system administrator.

(a) InfoPackage cannot be started in the SAP BW system.

The probable causes are described below.

• InfoPackage has not been scheduled to be executable by background processing.
  Check whether the InfoPackage definition in the SAP BW system (Schedule page) allows InfoPackage to be executed by background processing. To start InfoPackage in the background, set immediate execution as the startup condition.
  
• The destination to which InfoPackage external data is to be read is not an application server.
  When you execute InfoPackage in the background, you need to set an application server to read the data. Check whether the InfoPackage definition in the SAP BW system (External Data page) defines an application server as the destination to which InfoPackage external data is to be read.
  
• The InfoPackage definition is being updated.
  Use the SAP front-end software to check whether the definition of InfoPackage you wish to start is not being updated.
  
• The user who has logged on is not authorized to execute InfoPackage.
  When you create a user that executes InfoPackage, create the user based on the permission profile (S_BI-WHM_RFC) for background users that is prepared by the SAP BW system.
  Use either of the following procedures to obtain permission to execute InfoPackage:
  
  • Log on again with a user name that is allowed to execute InfoPackage.
  • Ask the SAP BW system administrator to grant permission to execute InfoPackage.
• SAP BW system resources are insufficient.
  To execute InfoPackage, you need one background work process (BGD) and one dialog work process (DIA). Make sure that a work process for executing InfoPackage in the SAP BW system is allocated and then restart InfoPackage.
  
• The SAP BW system has a known problem.
  If Job XXX is not started (yet) appears as the detailed information in a KAJM0813-E message that appears before KAJM2822-E message, there may be a problem with the SAP BW system. Check whether SAP Note 693703 has been applied to the connection destination SAP BW system. If not, apply the note.
  

(b) Completion monitoring of InfoPackage fails.

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

(c) The started InfoPackage ends abnormally in the SAP BW system.

The probable causes are described below.

• The display setting is incorrect for the end of InfoPackage with a warning.
  If Processing exceeded the specified time appears as the detailed text in a KAJM2827-E message, a timeout error may have occurred in the monitoring of the request that was generated by InfoPackage in the SAP BW system after InfoPackage ended with a warning. The InfoPackage probably ended abnormally.
  If InfoPackage ends with a warning, check whether the signal color changes to green or red. Open the Monitor window of the administrator workbench, and choose Settings -> Evaluation of requests (traffic lights). In the opened dialog box, check whether is judged to be successful (green lights) or is thought to have errors (red lights) is selected in If no data is available in the system, the request and If warning arise during processing, the request.
  
• The SAP BW system has a known problem.
  If Processing exceeded the specified time appears as the detailed text in a KAJM2827-E message immediately after execution of InfoPackage, there may be a problem with the SAP BW system. Check whether SAP Notes 633981, 641466, 647855, and 655528 have been applied to the connection destination SAP BW system. If not, apply the notes.
  

(d) The job following InfoPackage ends abnormally.

JP1/AJS3 for EAP cannot monitor the completion of a QM action (enables the loaded data) that is executed after loading of the InfoPackage data or the completion of subsequent InfoPackage processing (such as deleting duplicated requests). If resource contention occurs between these types of processing and the succeeding job, the succeeding job may end abnormally.

To prevent an abnormal end, you need to set the job that executes InfoPackage so that it ends after a QM action or the subsequent InfoPackage processing. To do so, use the -qmwait_time option of the jbwipsta command to set a period of time (wait time) between the normal end of InfoPackage and the end of the job that executes InfoPackage.

(e) A file named dev_rfc.trc or dev_rfc was created in the JP1/AJS3 for EAP work directory.

If an error occurs during SAP BW system custom job execution or JP1/AJS3 for EAP command execution, the RFC trace file (file named dev_rfc.trc or dev_rfc) is created in the JP1/AJS3 for EAP work directory. The RFC trace file records the trace information (error information) about the communications with the SAP BW system.

The RFC trace file is needed only when a serious error occurs. We recommend that you periodically delete the RFC trace file when no serious error has been encountered.

(3) Trouble with process chain control

This subsection describes the problems that may occur while you are controlling process chains.

If you cannot find the cause of a problem here, the problem may be caused by the external management interface provided by SAP. If a KAJM0812-E message appears, a problem with the external management interface is likely. Obtain the name of the function of the external management interface with the problem and the exception code from the message, and contact the SAP BW system administrator.

(a) The process chain for the SAP BW system cannot be started.

The probable causes are described below.

• The user who has logged on does not have permission to execute the process chain.
  To execute a process chain using the jbwipsta command, you need permission to log on from an external system (S_RFC) as well as permission to execute each process in each process chain in the background.
  Perform either of the following procedures to obtain permission to execute process chains:
  
  • Log on again with a user name that is allowed to execute process chains.
  • Ask the SAP BW system administrator to grant a permission to execute process chains.
• The definition of the process chain is incomplete.
  Check the definition of the process chain you attempted to start in the SAP BW system. Check whether the process chain is defined so it can be started correctly. Then re-execute the command.
  

(b) The started process chain ends abnormally in the SAP BW system.

The probable causes are described below.

• The user who has logged on does not have permission to execute the process chain.
  To execute a process chain using the jbwipsta command, you need permission to log on from an external system (S_RFC) as well as permission to execute each process in each process chain in the background.
  Perform either of the following procedures to obtain permission to execute process chains:
  
  • Log on again with a user name that is allowed to execute process chains.
  • Ask the SAP BW system administrator to grant permission to execute process chains.
• The process chain is being updated.
  Use the SAP front-end software to check whether the definition of the processes in the process chain is being updated.
  

If a process chain executed by JP1/AJS ends abnormally, perform either of the following procedures to restore the job:

• Re-execute processing from the beginning of the process chain.
  Re-execute the job for the abnormally ended process chain from JP1/AJS.
  
• Re-execute processing from the process where the error occurred.
  Use the SAP front-end software to check the status of the process chain that ended abnormally and re-execute the processing from the process where the error occurred. Allow JP1/AJS to execute the subsequent jobs when the re-executed process chain is completed.
  

(c) A file named dev_rfc.trc or dev_rfc was created in the JP1/AJS3 for EAP work directory.

If an error occurs during the execution of a custom job for the SAP BW system or a JP1/AJS3 for EAP command, an RFC trace file named dev_rfc.trc or dev_rfc is created in the work directory of JP1/AJS3 for EAP. The RFC trace file contains the trace information about the communication with the SAP BW system (information about the item that caused the error).

The RFC trace file is required for serious errors. If no serious errors occur, we recommend that you delete the RFC trace file periodically.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.