Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCS (Package) R/3 application development: Logistics Information Warehouse
Basic Data
Data Element | MC_CM_PSIZE |
Short Description | Packet Size of Data Processing in Copy Management |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MC_PSIZE | |
Data Type | NUMC | Character string with only digits |
Length | 6 | |
Decimal Places | 0 | |
Output Length | 6 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Pack. Size |
Medium | 15 | DP packet size |
Long | 27 | Data processing packet size |
Heading | 10 | Pack. Size |
Documentation
Definition
When "Data packet size" is selected, the system displays the number of data records that will be read from the database table in the source info structure for later processing in Copy Management.
The packet size has a direct influence on the commit frequency of the program (the frequency of the DB commit). In turn, these affect the number of rollback segments required, and how big the rollback area will need to be to run the copy job. In the rollback area, information about data changes for a possible DB rollback are stored.
A large (small) data packet causes a low (high) commit frequency and therefore generally requires a large (small) rollback area ("many" ("few") rollback segments).
Therefore program termination for example ("DBIF_RSQL_ERROR") can be counteracted by the following parametrization:
- "Snapshot too old": Increase the size of the data packets
- "Rollback-Segment too small": Reduce the size of the data packets
A data packet size of 10,000 is preset; if no value is entered, 1,000 records are selected for each.
When reading external data via Functional Enhancement RMCAF000, the packet size is available as an import parameter I_PSIZE of the customer exit EXIT_RMCAF000_001. A packet size of 50,000 is preset here.
It is only possible to configure the packet size in the expert mode; in all other cases, 1,000 is used.
History
Last changed by/on | SAP | 19980728 |
SAP Release Created in |