SAP ABAP Data Element MEMER (Purchase order 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
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | MEMER |
Short Description | Purchase order 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 | ||
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 | I |
Documentation
Use
You can use the Hold function to store faulty or incomplete purchase orders in the SAP System.
You can then continue processing or complete these POs that you have put "on hold" in this way at some later date.
A PO that is on hold is not transmitted to the vendor. It is, however, MRP-relevant.
The following functions are not not possible in the case of a PO that is on hold:
- Message output (printing or transmission of documents in message form)
- Posting a goods receipt
- Posting an invoice
Note:
If a PO has been saved, it cannot later be processed using the Hold function.
Dependencies
Example
Supplementary Documentation - MEMER 0001
Definition
Use
Purchase orders that have been put on hold are also taken into account in the selection of purchasing documents.
Dependencies
Example
History
Last changed by/on | SAP | 20010918 |
SAP Release Created in |