2.3 Replicating Conditions
2.3.4 Object Management
2.3.4.1
Changing Block Size Use
The block size specifies the number of object instances that will be selected and forwarded in a single operation. The block size is set by the system. The default value only has to be changed if there are problems (for example, memory overflow when making selection in the ERP system).
Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AC1
SAP CRM GUI menu Architecture and Technology à Middleware à Data Exchange à Object Management à Business Objects
2. On the Object Overview screen select the object for which the block size should be changed and choose Filters.
3. Choose Display à Change (Ctrl + F2).
4. Change the entry in the field Block Size.
5. Save (Ctrl + S) your entries.
2.3.4.2
Defining Filters for Objects Use
Under Filter Settings you can set filters for a business object. For Customizing and condition objects the filters can be defined only using tables/structures and the table-related filter symbol. If you use more than one filter entry per object, filters to the same table field are linked with an OR. Filters to different table fields are linked by AND.
The filter condition VKORG = 0001, VTWEG = 01 results in objects that fulfill both conditions at the same time.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AC1 SAP CRM GUI
menu
Architecture and Technology à Middleware à Data Exchange à Object Management à Business Objects 2. Select a business object and choose Details.
3. Choose Filter Settings.
4. Enter the data for the following fields:
Field Procedure
Source site Use the input help to select the site you want to set the filter criteria for. For example, for an initial data transfer from SAP ERP, this is the ERP System from which the data is to be transferred.
Note: The selection is dependent on the allowed flow contexts (SMOFINICON).
Table Use the input help to select a table, for example, KNA1 for customer master.
Field Use the input help to select a field.
OP (Operator) Select an operator.
LOW Specify the lower limit for the filter condition. If the field you selected is a date field, enter the date with the format YYYYMMDD. Leading zeros should be used as values for example, for customer and material numbers.
HIGH Specify the upper limit.
Incl./Excl. Specify whether the stated value/interval range should be included or not.
Inclusive: the resulting set lies within the range.
Exclusive: The resulting set lies outside the range.
Inactive Set your filter conditions to active.
5. Save (Ctrl + S) your entries.
The Generate Filter pushbutton located below the menu is only used for regenerating filter modules for selected objects, and should only be used in exceptional cases.
• The fields for filtering are available predefined for the objects. You will find the values allowed for each object when you make your selection.
• Some objects are delivered with predefined filters. SAP recommends that you do not change or delete. If necessary, you should define new filters. The purpose of filters is to reduce the size of the dataset transferred. You can find the predefined filters in the change functions of the Adapter Framework and in table SMOFFILTAB.
• Filter conditions are only stored locally and are not contained in the transport of
adapter objects. In this way filters are not transported from the development system to the production system. This is because filter conditions are site-specific and are defined differently in the development system to the production system. New filter settings have to be defined in each system.
2.3.4.3
Improving Performance during Replication Use
The initial download of objects such as the material master data can lead to performance problems.
Procedure
In order to improve performance, apply SAP Note 350176.
2.3.4.4
Monitoring and Error Analysis for Replication
Several tools for monitoring can be used to check the status of the replication.
Monitoring Download Status
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
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.
2.3.4.5
Monitoring Outbound Queue Procedure
1. This is used in cases when the queues are stuck in replication. With this you can identify the queues and do the debugging for those.
2. 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
3. To display a list of the queues, enter the client, queue name (for example *) and the queue destination (for example *).
4. Choose Execute.
5. To display the status, select the queue and choose Display selection (F7).
6. Call a specific outbound queue, select it and choose Display Selection (F7).
7. To display details on a queue, double-click the field Queue name.
8. If the queue was stopped because of capacity overload, use F6 to restart the queue.
9. If a second start of the queue is not successful, call the short dump analysis in the CRM system.
2.3.4.6
Monitoring Inbound Queue Procedure
1. This is used in cases when the queues are stuck in replication. With this you can identify the queues and do the debugging for those.
2. 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
3. Enter the client and the queue name (for example *).
4. Choose Execute.
5. To display the status, select the queue and choose Display selection (F7).
6. When you double-click the field Status, additional detailed information is generated.
7. To display details on a queue, double-click the Queue name field.
8. On the queue details screen, a red entry in the field Status indicates an error.
9. If the queue has status STOP, this is a Customizing problem in the CRM application.
10. When you double-click on the status field entry detailed information is displayed.
2.3.4.7
Analyzing BDoc Messages Use
By analyzing the BDoc messages you get information about incorrect settings in the CRM system that influences 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.
2.3.4.8
Checking Transactional RFC Requests
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.
2.3.4.9
Analyzing ABAP Dumps 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).
2.3.4.10
Restart Replication Use
After detecting and solving the replication error you have to restart the replication.
There are no restrictions for repeating data transfers from ERP to CRM.
Procedure
In order to restart the replication you have to run the following steps:
1. Canceling download of objects in transaction R3AM1.
2. Deleting outbound queue in transaction SMQ1.
3. Deleting inbound queue in transaction SMQ2.
4. Restart download using transaction R3AS.
2.3.4.11
Cancelling Download of 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 the status: Waiting and Running.
4. Choose Execute.
5. On the Monitor Download Objects screen select the objects you want to cancel for download.
6. Choose the Cancel symbol.
2.3.4.12
Deleting Outbound Queue 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 delete an outbound queue, select the queue and choose Delete selected objects.
2.3.4.13
Deleting Inbound Queue
Procedure
Transaction code SMQ2
SAP CRM GUI menu Architecture and Technology à 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.
2.3.4.14
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 ERP 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
1. Access the activity using one of the following navigation options:
Transaction code SE16
SAP ERP GUI menu 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 GUI menu Architecture & Technology Middleware à Data Exchange à Delta Load à 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 ERP system in the field Destination.
4. Save your entries.
3 Configuration settings for Marketing master Data
Purpose
This configuration guide provides the information you need to set up the lean campaign management.