BAPI_ORDER_TRIGGER_POINT SAP (Trigger Point Data) Structure details
Description: Trigger Point Data
Related tables to BAPI_ORDER_TRIGGER_POINT
Access table BAPI_ORDER_TRIGGER_POINT
Structure field list including key, data, relationships and ABAP select examples
BAPI_ORDER_TRIGGER_POINT 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 "Trigger Point Data" 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_ORDER_TRIGGER_POINT TYPE BAPI_ORDER_TRIGGER_POINT.
The BAPI_ORDER_TRIGGER_POINT table consists of various fields, each holding specific information or linking keys about Trigger Point Data data available in SAP. These include VALID_FROM_DATE (Valid-From Date), DELETION_INDICATOR (Deletion Indicator), CREATED_BY (Milestone created by), CREATED_ON (Milestone created on).. 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: Can be enhanced (character-type or numeric)
SAP BAPI_ORDER_TRIGGER_POINT 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 |
| MILESTONE_NUMBER | Milestone number | MLST_ZAEHL | NUMC | 12 | NUM12 | ||||
| VALID_FROM_DATE | Valid-From Date | DATUV | DATS | 8 | DATUM | ||||
| DELETION_INDICATOR | Deletion Indicator | LKENZ | CHAR | 1 | XFELD | ||||
| CREATED_BY | Milestone created by | MLST_USERH | CHAR | 12 | UNAME | ||||
| CREATED_ON | Milestone created on | MLST_DATEH | DATS | 8 | DATUM | ||||
| CHANGED_BY | Milestone changed by | MLST_USERV | CHAR | 12 | UNAME | ||||
| CHANGED_ON | Milestone changed on | MLST_DATEV | DATS | 8 | DATUM | ||||
| STD_NET_WORK | Standard network number | CN_PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | STDN | |
| STD_NET_TYPE | Standard network type | CN_PLNTY | CHAR | 1 | Assigned to domain | PLNTY | PTY | ||
| ALT_NET_WORK | Alternative to a standard network | CN_PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| IND_FUNCTIONS | Indicator: Milestone is used for milestone functions | MLST_WFLOW | CHAR | 1 | FLAG | ||||
| DESCRIPTION | Description | MLST_KTEXT | CHAR | 40 | TEXT40 | ||||
| OPERATION | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
| ORDER_NUMBER | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_ORDER_TRIGGER_POINT using ABAP code?
As BAPI_ORDER_TRIGGER_POINT 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_ORDER_TRIGGER_POINT as there is no data to select.How to access SAP table BAPI_ORDER_TRIGGER_POINT
Within an ECC or HANA version of SAP you can also view further information about BAPI_ORDER_TRIGGER_POINT 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