POR FAVOR, LEA: ESTE DOCUMENTO CONTIENE INFORMACIÓN ACERCA DE LOS MEDICAMENTOS QUE CUBRIMOS EN ESTE PLAN

Procedure

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

SAP CRM menu Middleware  Monitoring  Transactional RFC  Display Transactional RFC Requests

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

Procedure

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

SAP CRM menu Middleware  Monitoring  Performance  Exceptions/Users  Exceptions  Dump Analysis

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).

3.3.4

Restart Replication

Use

While there are no restrictions for repeating data transfers from ECC to CRM, data transfers from CRM to CDB are more serious, because in this case the data has to be distributed. To avoid inconsistencies between the CDB and mobile application databases, a repeated initial data transfer from CRM to CDB is prevented. If you are sure that no mobile clients have been supplied with data or that no data can be extracted again, then a repeated initial data transfer from CRM to CDB can be carried out. To do this you have to change an entry in table

SMOFINICUS.

The table contains the following fields:

• ObjName: Name of object (corresponds to the object name from table SMOFOBJECT)

• BDoc Name: Name of the BDoc

• Data Dist.: determines whether data is distributed (selected) or only written to the CDB (empty)

• User Name: Name of changer.

Table SMOFINICUS is delivered empty. With initial data transfers from CRM to CDB data distribution is automatically selected. If you are sure that mobile clients have still not been supplied with data, then the selection for data distribution can be unselected for the required object using the view maintenance for table SMOFINICUS (transaction code SM30). Then a new initial data transfer can be started for this object.

Table SMOFINICUS replaces parameter CRM_USE_BULK_DURING_INIT of the configuration file SMOFPARSFA.

Procedure

In order to restart the replication you have to run the following steps: 1. Canceling download of objects

2. Deleting outbound queue 3. Deleting inbound queue 4. Restart download

.3.3.4.1 Canceling Download of Objects

Procedure

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

SAP CRM menu 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 the status: Waiting and Running. 4. Choose Execute.

5. On the Monitor Download Objects screen select the objects you want to cancel for download.

.3.3.4.2 Deleting Outbound Queue

Procedure

1. Access the activity using the following navigation option: Transaction code SMQ1

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 delete an outbound queue, select the queue and choose Delete selected objects.

.3.3.4.3 Deleting Inbound Queue

Procedure

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

SAP CRM menu Middleware  Monitoring  Queues  Display Inbound RFC Queues

2. To display a list of the queues, enter a queue name (for example *). 3. Choose Execute.

4. To delete an inbound queue, select the queue and choose Delete selected objects.

.3.4 Checking Delta Replication Events

Use

For all master data objects an automatic delta replication will be activated during the initial download, i.e. each modification of a master data object is automatically transferred from the ECC into the CRM system. Customizing data is not automatically replicated. You have to run the delta replication manually or run a background job periodically.

The initial load of an object normally performs the activation of delta events automatically. You have to activate the delta events manually only if you need the delta events but have not performed the initial load of an object, for example for sales documents.

If all relevant objects that will be used in the scenarios have been downloaded successfully, you can skip this activity.

Procedure

Transaction code SE16

SAP ECC menu Basis Tools  ABAP Workbench  Overview  Data Browser 2. In the table name field enter TBE31.

3. Choose Table Contents (Enter). 4. Choose Execute (F8).

5. Check the column FUNCT for the relevant entries. For sales documents the relevant entry is:

APPLK FUNCT

BC-MID CRS_SALES_COLLECT_DATA

If this entry is in the table, the delta replication for sales documents is switched on. In case you need to activate the delta events manually, run the following activity in the CRM system:

Transaction code R3AC4

SAP CRM menu Middleware  Data Exchange  Delta Load from OLTP R/3  Set up Delta Load

1. Choose Display  Change in order to switch to change mode. 2. Choose New Entries.

3. Enter the relevant object class in field Object Class and the RFC destination to the ECC system in the field Destination.

4. Save your entries.