SAP ABAP Data Element EKGEN (Buyer approval following change to requisition item)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ MM-PUR (Application Component) Purchasing
⤷ MEDCM (Package) Purchasing: Change Management
⤷ MM-PUR (Application Component) Purchasing
⤷ MEDCM (Package) Purchasing: Change Management
Basic Data
Data Element | EKGEN |
Short Description | Buyer approval following change to requisition item |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EKGEN | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | Buyer app. |
Medium | 15 | Buyer approval |
Long | 20 | Buyer approval |
Heading | 20 | Buyer approval |
Documentation
Definition
Specifies whether or not the buyer is to approve changes to a purchase requisition.
Use
This indicator can be used to determine whether buyer approval is necessary, as follows:
- No buyer approval
Changes to a purchase requisition need never by approved by a buyer. - Buyer approval if RFQs issued or procurement initiated in respect of the requisition
If the requisition has already been converted into a follow-on document and is subsequently changed, buyer approval of the changes is necessary. - Buyer approval as of version 1
Changes to a requisition item must always be approved by a buyer from version 1 upwards even if no follow-on document yet exists. - Control via enhancement
Enhancement MEREQ003 enables you to specify the effects that changes to a purchase requisition are to have.
Dependencies
Example
History
Last changed by/on | SAP | 20010830 |
SAP Release Created in | 46C |