SAP ABAP Data Element JBXBEW (EDT Documentation for Position Values)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
JBA (Package) Application developmnet IS-B General Development
⤷
⤷
⤷
Basic Data
| Data Element | JBXBEW |
| Short Description | EDT Documentation for Position Values |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 9 | Pos.Vals |
| Medium | 9 | Pos.Vals |
| Long | 13 | Posit.Values |
| Heading | 0 |
Documentation
I. General Information
Position values are stored in a flat structure, that is, there is no header/item structure for data transfer.
II. Receiver structure
The receiver structure contains the position indicator of the position object. The company code (BUKRS) is relevant for all position objects, as is the product type (GSART).
You must also fill out the position date (DBSTND) for all records.
Depending on the product type, you may also have to fill out the amount, quantity and rate fields.
The mode fields (SMODE) controls which function the system carries out for the transferred record ('I' for Insert, 'U' for Update).
III. Special Considerations
Repeated transfer of position values
You can only transfer position values once per position object and position date.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |