Table list used by SAP ABAP Table TPOTA_VEH_RES_INPUT (Proxy Structure (Generated))
SAP ABAP Table
TPOTA_VEH_RES_INPUT (Proxy Structure (Generated)) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | TPOTA_VEH_RES_INPUT_BOOKING_CH | Specifies the booking channel type and whether it is the pri | ||
| 2 | TPOTA_VEH_RES_INPUT_CCRATE | Proxy Structure (Generated) | ||
| 3 | TPOTA_VEH_RES_INPUT_COMPANY_N1 | Proxy Structure (Generated) | ||
| 4 | TPOTA_VEH_RES_INPUT_COMPANY_NA | Proxy Structure (Generated) | ||
| 5 | TPOTA_VEH_RES_INPUT_CURRENCY_C | Proxy Structure (Generated) | ||
| 6 | TPOTA_VEH_RES_INPUT_CUSTOMER | Proxy Structure (Generated) | ||
| 7 | TPOTA_VEH_RES_INPUT_DROP_OFF_C | This element allows a user to pass in drop off charge data w | ||
| 8 | TPOTA_VEH_RES_INPUT_INVOICE_RE | This element allows a user to add in invoice remarks about t | ||
| 9 | TPOTA_VEH_RES_INPUT_MDRSUBSET | Proxy Structure (Generated) | ||
| 10 | TPOTA_VEH_RES_INPUT_MESSAGING | Proxy Structure (Generated) | ||
| 11 | TPOTA_VEH_RES_INPUT_MILEAGE | Proxy Structure (Generated) | ||
| 12 | TPOTA_VEH_RES_INPUT_OFF_LOC_SE | Information on requested off-airport location services, for | ||
| 13 | TPOTA_VEH_RES_INPUT_PICKUP_POI | Value of CodeType can be either L or C. L for Leisure and C | ||
| 14 | TPOTA_VEH_RES_INPUT_PICK_UP_LO | Code and optional string to describe a location point. | ||
| 15 | TPOTA_VEH_RES_INPUT_POS | Proxy Structure (Generated) | ||
| 16 | TPOTA_VEH_RES_INPUT_POSITION | Used to identify geospatial postion of the requesting entity | ||
| 17 | TPOTA_VEH_RES_INPUT_PROMOTIONA | Value of CodeType can be either L or C. L for Leisure and C | ||
| 18 | TPOTA_VEH_RES_INPUT_RATE_OVERR | Proxy Structure (Generated) | ||
| 19 | TPOTA_VEH_RES_INPUT_RATE_QUALI | Proxy Structure (Generated) | ||
| 20 | TPOTA_VEH_RES_INPUT_REQUESTOR | Proxy Structure (Generated) | ||
| 21 | TPOTA_VEH_RES_INPUT_RETURN_LOC | Code and optional string to describe a location point. | ||
| 22 | TPOTA_VEH_RES_INPUT_SOURCE | Proxy Structure (Generated) | ||
| 23 | TPOTA_VEH_RES_INPUT_SPECIAL_EQ | Proxy Structure (Generated) | ||
| 24 | TPOTA_VEH_RES_INPUT_SPECIAL_PR | Proxy Structure (Generated) | ||
| 25 | TPOTA_VEH_RES_INPUT_TOUR_CODE | Proxy Structure (Generated) | ||
| 26 | TPOTA_VEH_RES_INPUT_TPA_EXTEN1 | Allows extensions to an OTA Schema to accommodate bilateral | ||
| 27 | TPOTA_VEH_RES_INPUT_TPA_EXTEN2 | Allows extensions to an OTA Schema to accommodate bilateral | ||
| 28 | TPOTA_VEH_RES_INPUT_TPA_EXTEN3 | Allows extensions to an OTA Schema to accommodate bilateral | ||
| 29 | TPOTA_VEH_RES_INPUT_TPA_EXTEN5 | Allows extensions to an OTA Schema to accommodate bilateral | ||
| 30 | TPOTA_VEH_RES_INPUT_TPA_EXTENS | Allows extensions to an OTA Schema to accommodate bilateral | ||
| 31 | TPOTA_VEH_RES_INPUT_VEH_PREF | Proxy Structure (Generated) | ||
| 32 | TPOTA_VEH_RES_INPUT_VEH_PREFS | Proxy Structure (Generated) | ||
| 33 | TPOTA_VEH_RES_INPUT_VEH_RENTAL | Proxy Structure (Generated) | ||
| 34 | TPOTA_VEH_RES_INPUT_VEH_RES_R1 | Proxy Structure (Generated) | ||
| 35 | TPOTA_VEH_RES_INPUT_VEH_RES_RQ | The VehicleReservationRQAdditionalInfoType complex type iden | ||
| 36 | TPOTA_VEH_RES_INPUT_VEH_TYPE | This element allows a user to specify the type of vehicle th | ||
| 37 | TPOTA_VEH_RES_INPUT_WRITTEN_CO | This element allows a user to request written confirmation f |