BAPISDDELSCHED_EX SAP (BAPI Structure of VBLB with english field names) Structure details
Dictionary Type: Structure
Description: BAPI Structure of VBLB with english field names
Description: BAPI Structure of VBLB with english field names
ABAP Code to SELECT data from BAPISDDELSCHED_EX
Related tables to BAPISDDELSCHED_EX
Access table BAPISDDELSCHED_EX
Related tables to BAPISDDELSCHED_EX
Access table BAPISDDELSCHED_EX
Structure field list including key, data, relationships and ABAP select examples
BAPISDDELSCHED_EX 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 "BAPI Structure of VBLB with english field names" 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_BAPISDDELSCHED_EX TYPE BAPISDDELSCHED_EX.
The BAPISDDELSCHED_EX table consists of various fields, each holding specific information or linking keys about BAPI Structure of VBLB with english field names data available in SAP. These include DOC_NUMBER (Sales Document), ITM_NUMBER (Sales Document Item), INT_DEL_SCHED_NR (Internal delivery schedule number), REL_TYPE (Release type).. 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: Not classified
SAP BAPISDDELSCHED_EX 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 |
| OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
| DOC_NUMBER | Sales Document | VBELN_VA | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| ITM_NUMBER | Sales Document Item | POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
| INT_DEL_SCHED_NR | Internal delivery schedule number | ABRLI | NUMC | 4 | Assigned to domain | ABRLI | |||
| REL_TYPE | Release type | ABART | CHAR | 1 | ABART | ||||
| EDI_DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
| CUM_QUAN_REC | Cumulative Quantity Received by Customer | ABKFZ | QUAN | 15(3) | MENGV15 | ||||
| DL_SCHED_VL_FROM | Dlv. sched. valid from | ABRAB | DATS | 8 | DATUM | ||||
| DL_SCHED_VL_TO | SA rel. valid to | ABRBI | DATS | 8 | DATUM | ||||
| DLVSCHEDNO | Customer number for forecast / JIT dlv. sched. | LABNK | CHAR | 17 | TEXT17 | ||||
| DLVSCHEDDATE | Delivery Schedule Date | ABRDT | DATS | 8 | DATUM | ||||
| SCHED_L_DATE_KEY | Date key for schedule line dates | TERSL | CHAR | 1 | TERSL | ||||
| DAT_LAST_DEL_REC | Date of last delivery posted by the customer | LFDKD | DATS | 8 | DATUM | ||||
| LAST_DEL_REC | Last delivery confirmed by the customer | LFNKD | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
| PR_GO_AHEAD_ST | Start of production go-ahead | ABFDA | DATS | 8 | DATUM | ||||
| PR_GO_AHEAD_END | End of production go-ahead | ABFDE | DATS | 8 | DATUM | ||||
| MAT_GO_AHEAD_ST | Start of material go-ahead | ABMDA | DATS | 8 | DATUM | ||||
| MAT_GO_AHEAD_END | End of material go-ahead | ABMDE | DATS | 8 | DATUM | ||||
| LIN_DEL_SCHED_NR | Last internal release order number | ABLLI | NUMC | 4 | Assigned to domain | ABRLI | |||
| PR_GO_AHEAD_HI | Highest cumulative production go-ahead quantity | HIFFZ | QUAN | 15(3) | MENG15 | ||||
| PR_GO_AHEAD_HINR | Internal schedule no.for highest prod.go-ahead cml.qty | HIFFZLI | NUMC | 4 | Assigned to domain | ABRLI | |||
| MT_GO_AHEAD_HI | Highest cumulative material go-ahead quantity | HIMFZ | QUAN | 15(3) | MENG15 | ||||
| MT_GO_AHEAD_HINR | Internal schedule number for highest mat.go-ahead cml.qty | HIMFZLI | NUMC | 4 | Assigned to domain | ABRLI | |||
| REC_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| REC_TIME | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
| CREATED_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| DL_GO_AHEAD_HI | Highest delivery go-ahead cumulative quantity | HILFZ | QUAN | 15(3) | MENG15 | ||||
| DL_GO_AHEAD_HINR | Internal schedule number for highest dlv.go-ahead cml.qty | HILFZLI | NUMC | 4 | Assigned to domain | ABRLI | |||
| JIT_HORIZON | JIT horizon | ABHOR | DATS | 8 | DATUM | ||||
| CU_FISC_YEAR | Customer fiscal year | GJKUN | NUMC | 4 | GJAHR | GJAHR | |||
| CU_FISC_YEAR_NYC | Customer fiscal year which is not yet closed | VJKUN | NUMC | 4 | GJAHR | GJAHR | |||
| MAT_GO_AHEAD_ACT | Actual cumulative material go-ahead quantity | AKMFZ | QUAN | 15(3) | MENG15 | ||||
| PR_GO_AHEAD_ACT | Actual cumulative production go-ahead quantity | AKFFZ | QUAN | 15(3) | MENG15 | ||||
| DL_GO_AHEAD_ACT | Actual cumulative delivery go-ahead quantity | AKLFZ | QUAN | 15(3) | MENG15 | ||||
| HIGH_PRIO_ST_KEY | Key for high priority stock | KRITB | CHAR | 1 | CHAR1 | ||||
| REQ_STATUS_KEY | Requirements status key | BSTAS | CHAR | 1 | CHAR1 | ||||
| CONSUMPPNT | Customer point of consumption | VBRST | CHAR | 14 | CHAR14 | ||||
| LAST_ELF_REC | Last dlv. note sent by ext. service agent to the customer | LFEDL | CHAR | 20 | CHAR20 | ||||
| DAT_LAST_ELF_REC | Date of last delivery sent by external agent to customer | EDLDT | DATS | 8 | DATUM | ||||
| QN_LAST_DEL_REC | Last delivery quantity received by the customer | LFMKD | QUAN | 13(3) | MENG13 | ||||
| SALES_QTY_NUM | Numerator (factor) for conversion of sales quantity into SKU | UMVKZ | DEC | 5 | UMBSZ | ||||
| SALES_QTY_DENOM | Denominator (Divisor) for Conversion of Sales Qty into SKU | UMVKN | DEC | 5 | UMBSN | ||||
| USR01 | Additional data field 1 for delivery schedules | USR01_D | CHAR | 35 | TEXT35 | ||||
| USR02 | Additional data field 2 for delivery schedules | USR02_D | CHAR | 35 | TEXT35 | ||||
| USR03 | Additional data field 3 for delivery schedules | USR03_D | CHAR | 35 | TEXT35 | ||||
| USR04 | Additional data field 4 for delivery schedules | USR04_D | CHAR | 10 | CHAR10 | ||||
| USR05 | Additional data field 5 for delivery schedules | USR05_D | CHAR | 10 | CHAR10 | ||||
| CUM_QUAN_ZERO_ST | Cumulative quantity reached on date zero setting made | CYEFZ | QUAN | 15(3) | MENGV15 | ||||
| DATE_ZERO_ST | Date on which cumulative received quantity set to zero | CYDAT | DATS | 8 | DATUM | ||||
| MAT_GO_AHEAD_VP | Material go-ahead - validity period | MFLAUF | NUMC | 3 | NUM3 | ||||
| MAT_GO_AHEAD_UVP | Material go-ahead - unit validity period | MFEIN | CHAR | 1 | EHFR | ||||
| PR_GO_AHEAD_VP | Production go-ahead - validity period | FFLAUF | NUMC | 3 | NUM3 | ||||
| PR_GO_AHEAD_UVP | Production go-ahead - Unit validity period | FFEIN | CHAR | 1 | EHFR | ||||
| DLVSCHEDDATE_ORG | Delivery schedule date of creation | ABRDT_ORG | DATS | 8 | DATUM | ||||
| LAST_PUS_REC | Last pick-up sheet sent by the customer | LFMAIS | CHAR | 20 | BSTNK | ||||
| DAT_LAST_PUS_REC | Date of last pick-up sheet | MAIDT | DATS | 8 | DATUM | ||||
| CH_ON | Changed On | AEDAT | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPISDDELSCHED_EX using ABAP code?
As BAPISDDELSCHED_EX 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 BAPISDDELSCHED_EX as there is no data to select.How to access SAP table BAPISDDELSCHED_EX
Within an ECC or HANA version of SAP you can also view further information about BAPISDDELSCHED_EX 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