Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | NUMKA |
| Short Description | Number range in case of internal number assignment for ALE |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMKR | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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.rng.ALE |
| Medium | 15 | No. range ALE |
| Long | 20 | Number range ALE |
| Heading | 5 | NoRgA |
Documentation
Definition
This number range is only to be maintained in the case of contract types that are distributed among local systems.
If contracts are distributed among local systems, local release orders are then also generated. In this case, the release order documentation is updated both in the local system and in the central one.
For the release order documentation in the central system, the PO number from the local system is not unique. This PO number must therefore be supplemented by a new number, which is assigned to it in the central system.
The original PO number is also recorded in the release order documentation.
This number range is provided for the new PO number that is to be assigned. A separate number range, which is not used by any other document type, should be set up for this purpose.
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
