SAP ABAP Data Element MEMBF (Purchase Requisition not yet Complete)
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 | MEMBF |
Short Description | Purchase Requisition not yet Complete |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | MEMBF | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Incomplete |
Medium | 15 | Incomplete |
Long | 20 | Incomplete |
Heading | 1 | S |
Documentation
Use
You can save incorrect or incomplete purchase orders in the SAP System using the Hold function.
You can then process or complete purchase orders that you have put "on hold" in this way at a later point in time.
A purchase order that is on hold is not transmitted to the vendor, but it is relevant to MRP.
The following functions are not possible for purchase orders that have been put on hold:
- Message output
- Release
- Posting of a goods receipt
- Posting of an invoice
Note:
Once a purchase order has been saved, it cannot later be processed using the Hold function.
Dependencies
Example
Supplementary Documentation - MEMBF 0001
Definition
Use
purchase orders on hold are also taken into account in the selection of purchasing documents.
Dependencies
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 470 |