SAP ABAP Data Element MEMORYTYPE (Category of Incompleteness)

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	MEMORYTYPE
Short Description	Category of Incompleteness

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	MM_MEMORYTYPE
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	MEMORYTYPE
Change document	☑
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Category
Medium	15	Incompl. Cat.
Long	20	Incompleteness
Heading	33	Category of Incompleteness

Documentation

Use

You can save incomplete purchase orders and purchase requisitions in the system as follows:

• Hold (H)
  You can store faulty or incomplete purchase orders and purchase requisitions in the SAP system using the Hold function. You can process further or complete purchase orders that are on hold at a later point in time.
• Park (P)
  You can park documents if they contain the data necessary for posting in Materials Management. You use the parking function if the budget data is to be checked and saved at a later point in time.
• Saved as complete
  These documents have been saved as complete.

Dependencies

You can save purchase requisitions and purchase orders in the following sequence:
Hold => Park => Save.
You can also directly park documents or directly save them as complete.
Note that you cannot subsequently park an already saved document. You cannot subsequently put a parked document on hold.

The following functions are not possible for documents that have been put on hold:

• Message output
• Release

Example

History

Last changed by/on	SAP	20100310
SAP Release Created in	700