Explanation: No Variants were found which correspond to the selection criteria. Possible reasons: - variant does not exist - parameter value not equal to selection criteria
Explanation:Multiple running instances of one unique process chain are not allowed within the BW system (The Automation Engine checks this on AE side).&01 name of process chain&02 RunID of the UC4 object that started the process chain
Explanation: The corresponding BDC session was created without the option KEEP. Therefore, the session will immediately be deleted when it has successfully been processed. In this case the session statistics can not be checked.
Explanation: R3_CREATE_VARIANT has successfully been created. &01 - name of report &02 - name of variant
Explanation: R3_CREATE_VARIANT could not successfully be created. &01: Report name &02: Variant name Solution: The previous messages within the activation log and/or the SAP system log may show up the cause.
Explanation: A SAP Console Event has been started but the XBP interface has not been activated in the Agent. Solution: Activate XBP in the Agent's INI file.
Explanation: A SAP Console Event has been started but the specified XBP version is not suitable. Solution: Configure XBP Version=3.0 in the Agent's INI file.
Explanation: The SAP Console Event cannot be started because there is too much time difference between Server and Agent. Solution: Syncronize Server time und Agent time.
Explanation: This is a diagnostic trace message. &01: Object type &02: Time used &03: Count of active objects
Explanation: This is a diagnostic trace message. &01 - Agent load, value in percent
Explanation: A non-XI element was found in a SAP job of type XI. Solution: Adjust this Job object's script accordingly.
"Explanation: This job is not of type XI. Thus, UC4 elements for SAP XI cannot be used. Solution: Adjust the Job object's script accordingly or change the Job type to XI in the ""SAP"" tab."
Explanation: BW is not enabled in the initfile. Solution: - entry in the initfile: [SAP_BW] enabled=1 - BW must be licenced.
Explanation:BCA is not enabled in the INI file.Solution:- entry in the initfile:[SAP_BCA]enabled=1- BCA must be licenced.
Explanation: The statement has an illegal parameter. &01: name of the illegal parameter. &02: name and value of the parameter that make the other parameter illegal. Solution: Correct the job script.
Explanation: A parameter is missing in the statement. &01: Name of the missing parameter &02: Name and value of the parameter which requires the missing parameter. Solution: Correct the job script.
Explanation: Information about the interception and parent-child settings. &01: Interception setting (ON/ON3/OFF) &02: Parent child setting (ON/OFF)
Explanation: Information about the Criteria Profile which has just been activated. &01: Name/number of the activated Criteria Profile.
Explanation: The activation of a Criteria Profile failed. &01: Name/number of the Criteria Profile that could not be activated.
Explanation: The agent cannot retrieve a return code for the Job. &01: Name of the Job. &02: Job count of the Job. &03: Jobstep number.
Explanation: Information about the Job's return code. &01: Name of the Job &02: Jobcount of the Job &03: Jobstep number &04: Return code
Explanation: The execution of this function is not allowed by the setting of INTERCEPTION. &01: Function that cannot execute. Solution: set the INTERCEPTION mode to 2.0.
Explanation: RSPC_API_CHAIN_GET_STATUS returns E_MANUAL_ABORT='X' &01: Name of the process chain &02: Logical ID of the process chain
Explanation: RSPC_API_CHAIN_GET_STATUS returns SAP status. (Parameter E_STATUS) &01: Name of the process chain &02: Logical ID of the process chain &03: SAP status of the process chain
Explanation: The process chain doesn't exist. &01: Technical designation of the process chain. (BW_ACTIVATE_CHAIN ID)
Explanation: No ABAP connection has been assigned to the Agent. Solution: Assign an ABAP connection object to the Agent.
Explanation: The process chain doesn't exist. &01: Technical designation of the process chain. (BW_RESTART_CHAIN ID) &02: LOGID of BW_RESTART_CHAIN
Explanation: The agent can't restart the job.
Explanation: A job was started with a login object without client. Solution: Login object must have a logininfo <client>,<user>. (Example: 001,LE)
Explanation: The connection object was newly taken from the server. &01: Name of the connection object. &02: Parameter name and value.
Explanation: A script statement has a parameter that has an invalid value. '&01' Name of the parameter '&02' Invalid value Solution: Check the value of the given parameter.
Explanation: BW diagnostic message &01: moduleName() &02: chain &03: logId &04: status &05: manualAbort &06: runid
Explanation: BW diagnostic message
Explanation: BW diagnostic message &01: UC4 Jobname &02: UC4 Run# &03: chain name &04: child UC4 Jobname &05: child chain name &06: child chain logId &07: child status &08: child UC4 Run#
Explanation: BW diagnostic message &01: UC4 Jobname &02: UC4 Run# &03: chain name &04: child UC4 Jobname &05: child SAP Jobname &06: child SAP Jobcount &07: child status &08: child UC4 Run#
Explanation: BW diagnostic &01: chain name &02: logId
Explanation: BW diagnostic message &01: SAP Jobname &02: SAP Jobcount
Explanation: BW diagnostic message &01: moduleName &02: chain name &03: logId &04: status &05: runid
Explanation: BW diagnostic message &01: moduleName &02: SAP Jobname &03: SAP Jobcount &04: status &05: runid
Explanation: session couldn't be found &01: QID that was searched for
Explanation: the found session. &01: QID that was searched for
Explanation: Information about an installed SAP Component &01: Component name &02: Version &03: Patch &04: Description
Explanation: So that we'll see in the agentlog by the next crash if there was a big joblog. Parameter: &01: size of joblog in bytes.