Optimizer job failure

[Former Member]

Hi,

We have encountered a similar failure in Optimizer background job for two days in a row. The Optimizer fails with an error which says "An Exception occurred in communication object.".

Please let me know if running a consistency check on APO database would be of any help to resolve this issue. Thank you.

Rishikesh

[former_member209769]

Hi Rishikesh,

You could check if your optimizer server is reachable properly from SCM.

The issue coud most likely lie in Basis domain.

There is a SAP document on Optimizer setup, but unfortunately I can't attach it here.

I am copy pasting some things that could be checked by Basis team (Choose the Optimizer below that you use):

1. Log on to the SAP SCM System.

2. Call transaction SM59.

The Display and maintain RFC destinations screen appears.

3. Open the node for TCP/IP connection.

4. For the first optimizer server, you have to adapt the following RFC entries:

- OPTSERVER_CTM01

- OPTSERVER_DPS01

- OPTSERVER_SNP01

- OPTSERVER_SEQ01

- OPTSERVER_VSR01

- OPTSERVER_MMP01

- OPTSERVER_CS01

For the second optimizer server, the RFC entry names end with 02 (for example,

OPTSERVER_CTM02) and so on.

To adapt an RFC entry:

a. Double-click the destination name OPTSERVER_<Optimizer>01.

The RFC Destination OPTSERVER_<Optimizer>01 screen appears.

b. Depending on the server you must do the following to check the RFC entries:

A) Standalone Optimizer Server:

i. Choose Start on Explicit host.

ii. In the Program field check your program path (see table Program Paths of RFC Entries below).

iii. Check the name of your Target Host.

iv. Enter the number of the gateway host and the corresponding gateway service SAPGW<GW_NO>. You can find out the required parameters on your target host as follows:

a. On your target host, call transaction SMGW

b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)

v. Confirm with O.K.

B) Optimizer and SAP SCM on Same Server:

i. Choose Start on Application server.

ii. In the Program entry field check your program path (see table Program Paths of RFC Entries below).

If your SAP SCM server is an Unicode system, you must do the following in addition to the above setting for each OPTSERVER_<Optimizer>01 destination:

a. Choose the tab MDMP & Unicode.

b. In the group frame Communication Type With Target System you must select the flag Non-Unicode and the flag Inactive for the MDMP Settings box.

I hope this would be helpful in some basic check.

If your basis team is not able to resolve the issue, then better to reach out to SAP through OSS.

Thanks - Pawan