Cuento Infantil

Please check the Delta Guide.

Several tools for monitoring can be used to check the status of the replication.

.3.3.3.1 Monitoring Download Status

Please check the Delta Guide.

Use

The list Monitor Objects shows the current download status (Running, Wait, Done) for previously selected objects.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code R3AM1

SAP CRM GUI menu Architecture and Technology  Middleware  Monitoring

 Data Exchange  Monitor Objects

2. Enter either an object name or an object name area or use the F4 input help.

Leave the selection empty if you want to display all objects.

3. Under Additional Selection Criteria you can select by the current status: Abort, Waiting, Running or Done.

4. Choose Execute.

5. On the Monitor Download Objects screen you get the following information that gives you hints about the correctness of the download for each object.

Field Value

Checkbox Set the indicator to select a transfer object for further processing.

Status The following values are possible:

• Red (waiting) i.e. not yet started or aborted

• Yellow (Running)

• Green (Done) Object name

Field Value

P (Parent) If this indicator is set, there is a superordinate object in the transfer.

Date Date of the last transfer block.

Time Start time of the last transfer block.

Block No. The block number indicates how many blocks have already been downloaded.

If, for example, the block size has been set to 100, then block number 15 means that 1,500 objects have already been posted on the CRM Server database.

Attempt This field shows the number of attempted transfers.

Source Site Specification of the RFC OLTP destination.

Destination Specification of the CRM system or CDB

6. If an object will not start (red light and status = Waiting), check if the object is dependent (field Subobject). Only if the parent object has been loaded successfully, can dependent objects be started, e.g. Material can only be downloaded once Customer has been downloaded, since there are materials dependent on customers.

7. If an object has not changed in the Monitor for a long time, (e.g. no increase in block numbers for the last five minutes), ascertain the reason first and then try to download the object again.

In this case you should run the following activities to detect the error.

.3.3.3.2 General Analysis Steps

Please check the Delta Guide.

Carry out the following steps:

1. Make sure the highest available Core Support Packages are installed in the OLTP in the same way as on the CRM server.

2. Check the setting for ERP table CRMRFCPAR (see chapter Maintaining Table CRMRFCPAR).

3. Check the RFC connections from CRM to ERP and vice versa.

.3.3.3.3 Monitoring Outbound Queue

Please check the Delta Guide.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SMQ1

SAP CRM GUI menu Architecture and Technology  Middleware  Monitoring  Queues  Display Outbound RFC Queues

2. To display a list of the queues, enter the client, queue name (for example *) and the queue destination (for example *).

3. Choose Execute.

4. To display the status, select the queue and choose Display selection (F7).

5. Call a specific outbound queue, select it and choose Display Selection (F7).

6. To display details on a queue, double-click the field Queue name.

7. If the queue was stopped because of capacity overload, use F6 to restart the queue.

8. If a second start of the queue is not successful, call the short dump analysis in the CRM system.

.3.3.3.4 Monitoring Inbound Queue

Please check the Delta Guide.

Procedure

1. To view the inbound queues in the CRM system and their status, choose one of the following navigation options:

Transaction code SMQ2

SAP CRM GUI menu Architecture and Technology  Middleware  Monitoring  Queues  Display Inbound RFC Queues

2. Enter the client and the queue name (for example *).

3. Choose Execute.

4. To display the status, select the queue and choose Display selection (F7).

5. When you double-click the field Status, additional detailed information is generated.

6. To display details on a queue, double-click the Queue name field.

7. On the queue details screen, a red entry in the field Status indicates an error.

8. If the queue has status STOP, this is a Customizing problem in the CRM application.

9. When you double-click on the status field entry detailed information is displayed.

.3.3.3.5 Analyzing BDoc Messages

Please check the Delta Guide.

Use

By analyzing the BDoc messages you get information about incorrect settings in the CRM system that influence the replication.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SMW01

SAP CRM GUI menu Architecture and Technology  Middleware  Monitoring

 Message Flow  Display BDoc Messages 2. Specify date and time of the relevant period of time.

3. Choose Execute.

4. BDOC messages with status beginning with E (red traffic light) need manual correction and retry.

5. Select the message and choose Errors.

6. Here you find notes regarding CRM setting problems.

.3.3.3.6 Checking Transactional RFC Requests

Please check the Delta Guide.

Procedure

1. Access the activity using the following navigation option:

Transaction code SM58

2. On the initial screen Transactional RFC, specify dates for the display period.

3. Fill in the remaining fields. Alternatively, enter *.

4. Choose Execute.

5. To display further details, drill down in the log.

.3.3.3.7 Analyzing ABAP Dumps

Please check the Delta Guide.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code ST22

SAP CRM GUI menu Architecture and Technology  Middleware  Monitoring

 Performance  Exceptions/Users  Exceptions  ABAP Runtime Errors

2. Specify the period (today, yesterday).

3. Choose Display list (F8).

4. To display the ABAP short dump description, select one of the short dumps and choose Dump analysis (F2).