SAP ABAP Data Element POSBEWART (Movement Type)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA (Application Component) Cross-Application Components
⤷ WPOS_IDOC_ABA (Package) POS IDocs R/3 Inbound and POSDW
⤷ CA (Application Component) Cross-Application Components
⤷ WPOS_IDOC_ABA (Package) POS IDocs R/3 Inbound and POSDW
Basic Data
Data Element | POSBEWART |
Short Description | Movement Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR4 | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Mvmnt Type |
Medium | 15 | Movement Type |
Long | 20 | Movement Type |
Heading | 4 | Mvnt |
Documentation
Definition
Code for the type of goods movement
Use
External goods movements codes are supported. They are converted using a communication profile stored in the plant master.
Conversion of the goods movements can be switched on or off for each communication profile (see Customizing Conversion Parameters).
In addition, an external code can be assigned to an SAP code for each communication profile (see Customizing Conversion of POS Movement Types).
If there is no recognized movement type on the local system, you must at least enter either 'WE' or 'GR' in this segment field to identify a goods receipt. All other material movements require a unique movement type.
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in |