SAP ABAP IMG Activity BW_BCT_ELM_STEPS (Define Processing for Steps)
Hierarchy
BI_CONT (Software Component) Business Intelligence Content
   BW-BCT-CRM (Application Component) Customer Relationship Management
     RS_BCT_ELM (Package) Business Content External List Management
IMG Activity
ID BW_BCT_ELM_STEPS Define Processing for Steps  
Transaction Code S_B10_84000024   (empty) 
Created on 20030123    
Customizing Attributes BW_BCT_ELM_STEPS   Define Processing for Steps 
Customizing Activity BW_BCT_ELM_STEPS   Define Processing for Steps 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BW_BCT_ELM_STEPS    

Use

In this activity, you define processing for the work step "Postal Check" or "Duplicate Check".

The RFC connection specifies the system in which the checks are to run. In the SAP standard, both checks run in one SAP CRM system. This means that the BW system must be able to access the SAP CRM system via an RFC connection.

You use the indicator parallel to set whether or not the data is to be processed within the individual steps in parallel or in sequence. The system only uses the settings of the other parameters when this indicator is set.

With parallel processing, data is collated in packages. An asynchronous RFC (aRFC) is started for each package. The package data is processed in this aRFC. The aFRCs run in dialog work processes.

The server group defines the group of application servers via which the dialog work processes are made available for parallel execution. Using server groups has the big advantage that the system bases its choice of instance to be used on the current system load. When setting up an aRFC with server groups, the system does not determine the instance on which a dialog work process is to be used in the execution until the time of execution. The system considers all instances belonging to the group.

The maximum number of aRFCs defines how many server group dialog work processes are used by the aRFCs running in parallel.

The package size defines how many data records are processed in an aRFC. The value of the package size cannot be set, it is 200 and is defined in coding.

Background

Setting Maximum Number of aRFCs

The throughput can decrease when using a larger number of parallel processes. This may happen due to lock conflicts (ENQUEUEs or database locks) or if system components are overloaded (CPU-, C drive- , ENQUEUE server load, database IO). The peak load on the system is greater for intensive parallel processing that with normal sequential processing. If the maximum capacity is reached for any of the above mentioned system components, this restricts the throughput of the entire process. The throughput lowers when additional processes are started.

The precise definition of the number of processes depends on the project in question and available system resources. No general rule exists here. We strongly recommend you use a stress test to establish the precise setting.

When beginning parallel processing, the required server group is started up and the dialog processes available at that time are displayed. If the number of dialog workprocesses available on the server group is smaller than the number specified by the user, the former is used as the reference value in the execution. If this is not the case, the system uses the process number specified by the user.

Entering the Server Group

Use transaction RZ12 to define a server group and instance assignment and to define temporarily the limits for the instance load situation. F1 help gives information about what each of the individual parameters mean.

When specifying the server group, you must use the correct case. Use F4 Help to avoid errors.

Almost all parameters are given as a percentage in RZ12. Exceptions include: Parameters for activating/deactivating the limits; parameters used to define the minimum number of free work processes; and parameters for the maximum wait time after the workload check in the system. There is only one record of valid parameters for each instance. Different values cannot be defined in different server groups for an instance.

Experience has shown that the parameter for the minimum number of free work processes should be set to >= 3, and that more work processes should be offered via the server group than can actually be used at the same time. This allows for unexpected surges in workload and helps minimize the danger of temporary resource constrictions.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 899   not to be assigned 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BW_BCT_ELM_STEPS 0 ARS0000023 Business Content and Extractors 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
ELMV_STEPS V - View SM30  
History
Last changed by/on SAP  20030123 
SAP Release Created in 320