Maintain number range object
- Short text
- Long text
- Number length domains
- Percent warnings
- Number range transaction
Object short text (length 20), number range maintenance dialog explanations
Object long text (length 60), number range maintenance dialog explanations
The domains determine the lengths of the numbers to be issued. They must be of type NUMC or CHAR, and have a field length of 1-20. Choose an appropriate domain from the Dictionary or create a new one.
This value specifies from what percent free interval a warning is issued when numbers are assigned. It must lie between 0.1 and 99,9.
If you enter a transaction code here, You can maintain the intervals for just this object by calling this code.
If you want differentiate a number range object, enter the data element according to whose value you want to differentiate:
- Data element sub-object (object types 4-8)
This data element must exist and be active in the Dictionary and have a check table. The domains must have a field length between 1 and 6.
Distinguishing by financial year
If the commercial object records are to be distinguished by financial year, mark the field:
- Until financial year flag. (all object types)
If the commercial objects are to be grouped by elements, you can specify, by completing the following fields, that the group table is to be maintained via the standard maintenance dialog. Otherwise you must program the assignment yourself.
- Group table (object types 2, 3, 5-8)
Enter the name of the table which contains the grouping element, e.g. for the material master, the material type table. The table must exist and be active in the Dictionary and contain the number range element field as key. If the groups depend on the sub-object, the sub-object must be part of the key. Otherwise the group table must not have any other key fields.
A group table can only be assigned to at most one number range object.
- Sub-object field in group table. (object types 7 and 8)
If the commercial object is differentiated by sub-object, and the groups are dependent on the sub-object, enter here the group table field which contains the sub-object value (object types 7 and 8). The sub-object field must be part of the key.
- No. range element field (object types 2, 3, 5-8)
If the commercial object is to be grouped, enter here the group table field which contains the value according to which groups are to be formed. The number range element field must be part of the key.
- Int./ext.no. range no. field (object types 3, 6, 8)
Enter here the group table fields for internal and external number ranges, if the application is to support both external and internal number assignment. A group table must be specified at the same time. The fields must have the format char (2) or num (2).
- No. range no. field (object types 2, 5, 7)
Enter here the group table field for the number ranges, if the application is to support only one number range (external or internal). The field must be part of the key and have the format char (2) or num (2).
Whether it is an external or internal number range is indicated when the interval for this number range is created.
Group maintenance element text display
If the element text is to be displayed during group maintenance, mark this field:
- Display element text
You must also maintain the following element text table entries with the text entries maintenance function:
- Element text table
- Language field
- Sub-object field
This field only appears in the interface when the groups are defined as being dependent on sub-objects.
- Element field
- Text field
When you have saved the input data, number range intervals can be created for the object.
Delete number range object
To be able to delete a number range object, you must first delete the number range intervals which belong to it.
Maintain number ranges
Have the end-user create number ranges with intervals, using the implementation guide. You can find information about this in the system administration document in the section on number ranges.
Transport number range objects
When number range objects are maintained, they are entered in a change request. When the transport is released, various consistency checks are made, to avoid the transport of objects with errors. Error messages or warnings appear in the transport log. If errors occur, the export or import is refused.