Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MGA (Package) Application development R/3 material master from 3.0
IMG Activity
| ID | MASS_V_PARALLEL | Mass Processing - Set Up Parallel and Asynchronous Processing |
| Transaction Code | S_EBJ_98000150 | (empty) |
| Created on | 20121108 | |
| Customizing Attributes | MASS_V_PARALLEL | Mass Processing - Set Up Parallel and Asynchronous Processing |
| Customizing Activity | MASS_V_PARALLEL | Mass Processing - Set Up Parallel and Asynchronous Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MASS_V_PARALLEL |
Use
In this Customizing activity, you define the settings for parallel and asynchronous processing for the various applications.
Parallel processing can be used to significantly improve the runtime. The parallel processing runs in packages. The work packages are distributed to the individual work processes of the server group.
The user can utilize asynchronous processing to carry on working in one mode while the changes to the data are made in another mode.
Asynchronous and parallel processing can be combined. Processing in the test run is always carried out in synchronous mode, independent of the settings made here.
Requirements
Standard settings
Activities
- Select the application. The following applications are supported:
- Mass maintenance for article BUS1001001
- Mass maintenance for GTINs
- Mass maintenance for characteristic values
The default setting for all applications is used if there is no entry specifically for the chosen application.
- Define the server group on which the processing should run.
- Set the maximum number of parallel processes.
- Set the maximum utilization of the server group in percent. This value restricts the maximum number of parallel processes, in relation to the work processes of the server group that are available at runtime.
- Set the package size. This is the number of objects that should be processed per parallel process. This concerns the minimum package size. The packages are internally formed, taking SAP blocking logic into account. It is therefore a possibility that more objects will need to be processed in a package.
The following conditions apply to the entries you make for the maximum number of parallel processes, and the maximum utilization of the server group:
- At least one of these two parameters must be maintained.
- If both parameters are maintained, the number of parallel processes is defined using the parameter that applies first.
- If only one parameter is maintained, the number of parallel processes is defined using only this parameter.
When defining the package size, you should start with the values listed below, then measure the runtime and moderately increase/decrease the values as appropriate. Then measure the runtime again. The optimum package size needs to be redetermined for each system. The specified values are therefore recommendations, which you need to review for your system.
- For the article: 25
- For the GTIN: Value not yet determined
- For the characteristic value: Value not yet determined
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | MASS_V_PARALLEL | 0 | HLA0006031 | Material Master |
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 |
| MASS_V_PARALLEL | V - View | SM30 |
History
| Last changed by/on | SAP | 20121108 |
| SAP Release Created in | 617 |
