SAP ABAP Data Element BEDHK (Origin of requirement type in requirement type determination)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
     ⤷ VZ (Package) Application development R/3 RV central functions

Basic Data

Data Element	BEDHK
Short Description	Origin of requirement type in requirement type determination

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	BEDHK
Data Type	NUMC	Character string with only digits
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	Source
Medium	15	Source
Long	20	Origin reqmt. type
Heading	3	Q

Documentation

Definition

In the standard release, the requirements type is determined according to a certain search strategy depending on the strategy group of the material.

In this field you can select an alternative search strategy (source):

• Source 0 = Material master strategy, then item category and MRP type
• Source 1 = Item type and MRP type strategy
• Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type

Example

Certain business transactions require a transaction based determination of the requirements class, as in the case consignment processing, for example. Here, it is not the material with its planning characteristics,but solely the transaction. Withdrawal of goods from the customer consignment stock, for example, would not lead to an availability check against planning at the plant, as planning strategy requires. Instead, a check must be carried out against special stock (source = 1 or 2).

History

Last changed by/on	SAP	19950901
SAP Release Created in