SAP ABAP Data Element TRINF_UEB (Data transfer)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BF (Application Component) Basic Functions
⤷
VTR (Package) SD R/3 transport processing
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VTR (Package) SD R/3 transport processing
Basic Data
| Data Element | TRINF_UEB |
| Short Description | Data transfer |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GRPNO | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TFRM |
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 | Routine |
| Medium | 15 | Routine |
| Long | 20 | Routine |
| Heading | 3 | Rt. |
Documentation
Definition
Select a data transfer routine for the data transfer. There are 12 standard routines for data transfer from deliveries into shipment documents. They contain the following fields: forwarding agent, route, shipping type, special processing indicator, shipment type, and deadlines. Some of the routines copy a combination of these fields.
Due to the large number of deliveries in a shipment, there are consistency checks for the following items:
- Different entries in the fields of the selected deliveries
- The fields are already defined in the shipment document
- The fields are not in a reference delivery.
In each case, the system issues a message to inform the user about the problem.
History
| Last changed by/on | SAP | 19990326 |
| SAP Release Created in |
