Hierarchy
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | EROUN |
Short Description | Routine number, buyer's negotiation sheet |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EROUN | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table | T160P |
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 | Routine |
Medium | 15 | Routine |
Long | 20 | Routine |
Heading | 3 | Rt. |
Documentation
Definition
Number that indicates which statistical data is to be included on the buyer's negotiation sheet.
Use
The routine number indicates a program-internal processing routine that selects and analyzes the relevant statistics. Routine numbers that start with "1" analyze vendor data, those that start with "2" analyze material data, and those that start with "3" analyze info records.
Procedure
List the possible routines using the F4 key, then choose a routine.
Dependencies
The processing routines are defined in program RM06EVB1.
You can write your own processing routine in program RM06EVBZ. All routines in this program are called up by the main program RM06EVB0.
When assigning a name for the FORM routine, note the following naming convention:
READ_DATA_nnn (nnn = routine number)
This means that the FORM routine must start with "READ_DATA_" and end with the routine number.
History
Last changed by/on | SAP | 19980218 |
SAP Release Created in |