BAPI_OIGSS SAP (TD Shipment stages) Structure details
Dictionary Type: Structure
Description: TD Shipment stages
Description: TD Shipment stages
Structure field list including key, data, relationships and ABAP select examples
BAPI_OIGSS is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "TD Shipment stages" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BAPI_OIGSS TYPE BAPI_OIGSS.
The BAPI_OIGSS table consists of various fields, each holding specific information or linking keys about TD Shipment stages data available in SAP. These include TSNUM (Stage of transport number), TSTYP (Stage category), TSRFO (Stage of transport sequence), VEHICLE (TD Vehicle Number).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP BAPI_OIGSS structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| SHNUMBER | TD shipment number | OIG_SHNUM | CHAR | 10 | Assigned to domain | ALPHA | OIG_SHNUM | OIS | |
| TSNUM | Stage of transport number | TSNUM | NUMC | 4 | Assigned to domain | TSNUM | |||
| TSTYP | Stage category | TSTYP | CHAR | 1 | TSTYP | ||||
| TSRFO | Stage of transport sequence | TSRFO | NUMC | 4 | TSRFO | ||||
| VEHICLE | TD Vehicle Number | OIG_VHLNMR | CHAR | 10 | Assigned to domain | ALPHA | OIG_VHLNMR | OIV | |
| ELUPD | Change Indicator | ELUPD | CHAR | 1 | ELUPD | ||||
| ROUTE | Route for shipment stage | ROUTES | CHAR | 6 | Assigned to domain | ROUTE | |||
| VSART | Shipping type for shipment stage | VERSARTS | CHAR | 2 | Assigned to domain | VERSART | |||
| LAUFK | Leg indicator for shipment stage | LAUFS | CHAR | 1 | LAUFK | ||||
| ADRNA | Departure point: Address | ADRNA | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| KNOTA | Departure Point | KNOTA | CHAR | 10 | Assigned to domain | KNOTN | |||
| VSTEL | Shipping point at point of departure | VSTELA | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
| LSTEL | Point of departure: Loading point at shipping point | LSTELA | CHAR | 2 | Assigned to domain | LSTEL | |||
| WERKA | Plant at point of departure | WERKSA | CHAR | 4 | Assigned to domain | WERKS | |||
| LGORTA | Departure point: Storage location in plant | LGORTA | CHAR | 4 | Assigned to domain | LGORT | |||
| KUNNA | Departure point: Customer | KUNNA | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| LIFNA | Vendor number of departure point | LIFNA | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| ADRNZ | Destination address | ADRNZ | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| KNOTZ | Destination point | KNOTZ | CHAR | 10 | Assigned to domain | KNOTN | |||
| VSTEZ | Shipping point at destination | VSTELZ | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
| LSTEZ | Destination: Loading point at shipping point | LSTELZ | CHAR | 2 | Assigned to domain | LSTEL | |||
| WERKZ | Plant at destination point | WERKSZ | CHAR | 4 | Assigned to domain | WERKS | |||
| LGORTZ | Destination: Storage location in plant | LGORTZ | CHAR | 4 | Assigned to domain | LGORT | |||
| KUNNZ | Customer number for destination point | KUNNZ | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| LIFNZ | Vendor number of destination point | LIFNZ | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| TDLNR | Number of forwarding agent in the shipment stage | TDLNRS | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | F4_CARRIERS | |
| DISTZ | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| DISTZ_UOM | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| TOTTIME | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| TOTTIME_UOM | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| DRVTIME | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| DRVTIME_UOM | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| ADRKNZA | Point of departure: Origin indicator of address | ADRKNZA | CHAR | 1 | ADRKNZ | ||||
| KUNABLA | Point of departure: Customer's unloading point | KUNABLA | CHAR | 25 | TEXT25 | ||||
| ADRKNZZ | Destination: Origin indicator of address | ADRKNZZ | CHAR | 1 | ADRKNZ | ||||
| KUNABLZ | Destination: Customer's unloading point | KUNABLZ | CHAR | 25 | TEXT25 | ||||
| FRKRL | Shipment costs relevance | FRKRL | CHAR | 1 | FRKRL | ||||
| SKALSM | Pricing procedure in stage of shipment | KALSM_TRAB | CHAR | 6 | Assigned to domain | KALSM | |||
| FBSTA | Status of shipment costs calculation | FBSTA | CHAR | 1 | FBSTA | ||||
| ARSTA | Status of shipment costs settlement | ARSTA | CHAR | 1 | ARSTA | ||||
| VEH_IND | TD-F: Vehicle stage indicator with first and last node | OIG_VEHIND | CHAR | 1 | OIG_VEHIND | ||||
| CARR_ROUT | TD-F carrier is copied from route / stage table | OIG_CRROUT | CHAR | 1 | XFELD | ||||
| TSTYP_TXT | Description of stage type | OIG_TYPTXT | CHAR | 30 | CHAR30 | ||||
| DEPFLAG | TD-F flag if stage is used as dep. or destination point | OIG_STGFLG | CHAR | 1 | CHAR1_X | ||||
| DESTFLAG | TD-F flag if stage is used as dep. or destination point | OIG_STGFLG | CHAR | 1 | CHAR1_X | ||||
| FRKRLFLAG | TD-F flag: if SCD-relevance is set for TSTYP | OIG_FRKFLG | CHAR | 1 | CHAR1_X | ||||
| DESCNODEA | Description | BEZEI30 | CHAR | 30 | TEXT30 | ||||
| DESCNODEZ | Description | BEZEI30 | CHAR | 30 | TEXT30 | ||||
| UPDATEFLAG | Transaction type | TRTYP | CHAR | 1 | TRTYP | ||||
| UOM_ISO2SAP | Convert Unit of measure from ISO to SAP | OIK_ISO2SAP | CHAR | 1 | OIK_ISO2SAP |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_OIGSS using ABAP code?
As BAPI_OIGSS is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BAPI_OIGSS as there is no data to select.How to access SAP table BAPI_OIGSS
Within an ECC or HANA version of SAP you can also view further information about BAPI_OIGSS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects