Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | DCSTP |
| Short Description | Number of documents per processing package |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC3 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | No. docs |
| Medium | 15 | No. documents |
| Long | 20 | Number of documents |
| Heading | 20 | Number of documents |
Documentation
Definition
Number of documents that are processed together in a processing step.
Use
The value indicates how many documents are loaded from the database to the main memory. It has a significant effect on memory consumption. Controlled memory usage is a basic requirement of parallel processing, that is, executing the program in parallel per processor.
Note that the number of document items relevant for the arrangement (that is, their condition records) actually determines how much memory is used. For technical reasons, however, each item of a document must be processed in one step.
For performance reasons, the value entered depends on the number of document items and, if appropriate, the number of follow-on documents.
A value that is too low, e.g. 1 (processing per document) reduces database performance. A value that is too high requires a lot of memory. This can cause problems in parallel processing (parallel execution of the report).
With 32-BIT technology, a value of 400 MB for maximum memory usage is sensible. This can be achieved with about 2500 document items per processing step. With an estimated number of 25 items per document, this means a package size of 100 documents. If not all document items are relevant for the arrangement, there is a correspondingly smaller number of items. The package size is somewhere between 100 and 2500 items. In the case of very large documents (large number of items), it may be necessary to reduce the value. A purchase order with 100 000 items (all of which are relevant for the condition record) requires about 500 MB main memory, for example. A value of 1 should therefore be entered.
In case of doubt, measurements/controls must be carried out.
History
| Last changed by/on | SAP | 19991014 |
| SAP Release Created in |
