SAP ABAP Data Element PIECE_LIST (Select Piece Lists)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CTS-ORG (Application Component) Transport Organizer
⤷
SCTS_REQ (Package) CTS: Request Editing
⤷
⤷
Basic Data
| Data Element | PIECE_LIST |
| Short Description | Select Piece Lists |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR_LG_01 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 20 | Piece List |
| Heading | 45 | Piece list |
Documentation
Definition
The following attributes differentiate piece lists from other request types:
- You can select their name freely (the SAP System prevents conflicts with the naming conventions for regular request types).
- You cannot release them.
- They have an object directory entry, and are therefore assigned to a development class.
- Like other objects in the ABAP Workbench, you can include them in regular change requests (LIMU COMM <objectlist>) and transport them.
- When you transport a request which includes a piece list, the piece list is transported, but not the objects entered in the piece list. If you also want to transport these objects, you must include them directly in the object list of the request.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |