Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
COCB (Package) R/3 Application Development: PP Orders Batch Management
Basic Data
| Data Element | CO_MAXSEL |
| Short Description | Maximum Number of Messages to Be Selected |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM06 | |
| 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 | Max. No. |
| Medium | 15 | Maximum Number |
| Long | 22 | Max. No. of Messages |
| Heading | 0 |
Documentation
Definition
Maximum number of process messages to be selected.
If you restrict the number of messages, system performance will be improved.
Note
With process messages that were created before Release 4.6A, the maximum number entered here for technical reasons refers to those messages that are selected solely according to selection criteria other than the order number. The order number is not taken into account.
If you enter an order number here, it is then used for detailed selection. Depending on the maximum number entered for the messages to be selected, the system may find no messages or less messages than actually exist for the process order.
To avoid this, you can use program RCOCBX02 to start a job for messages that were created before Release 4.6A. The system uses the order number to select these messages. The program makes changes in the logon client only.
Depending on the number of process messages in the logon client, the program runtime may be quite long. For this reason, we recommend scheduling the conversion in a background job. You can continue to work with your system as usual during the conversion.
History
| Last changed by/on | SAP | 19960902 |
| SAP Release Created in |
