BAPISDBPL SAP (BAPI Structure of FPLA with English Field Names) Structure details
Description: BAPI Structure of FPLA with English Field Names
Structure field list including key, data, relationships and ABAP select examples
BAPISDBPL 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 FPLA 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_BAPISDBPL TYPE BAPISDBPL.
The BAPISDBPL table consists of various fields, each holding specific information or linking keys about BAPI Structure of FPLA with English Field Names data available in SAP. These include SD_DOC (Sales and Distribution Document Number), ITM_NUMBER (Item number of the SD document), BILL_PLAN (Billing plan number / invoicing plan number), BILLPLATYP (Billing plan category).. 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 BAPISDBPL 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 | ||||
| SD_DOC | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| ITM_NUMBER | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
| BILL_PLAN | Billing plan number / invoicing plan number | FPLNR | CHAR | 10 | Assigned to domain | FPLNR | |||
| BILLPLATYP | Billing plan category | FPTYP_FP | CHAR | 1 | FPTYP | ||||
| B_INPLATYP | Billing/Invoicing Plan Type | FPART | CHAR | 2 | Assigned to domain | FPART | |||
| SORT_FLD | Sort field | SORTL | CHAR | 10 | CHAR10 | ||||
| BILLSTADAT | Start date for billing plan/invoice plan | BEDAT_FP | DATS | 8 | DATUM | ||||
| BILLENDDAT | End date billing plan/invoice plan | ENDAT_FP | DATS | 8 | DATUM | ||||
| RULEDETHOR | Rule for Determining Horizon in Billing/Invoicing Plan | HORIZ_FP | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| RULEORISTA | Rule for Origin of Start Date of Billing/Invoicing Plan | BEDAT_FPK | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| RULEORIEND | Rule for Origin of End Date for Billing/Invoicing Plan | ENDAT_FPK | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| RULEORINEX | Rule for Origin of Next Billing/Invoice Date | PERIO_FP | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| LENSTANPER | Length of a standard period in the billing plan | FPLAE | NUMC | 3 | NUM3 | ||||
| STANBILLNO | Standard Billing/Invoicing Plan Number | RFPLN_D | CHAR | 10 | Assigned to domain | FPLNR | |||
| DATESFROM | Dates from | TADAT | DATS | 8 | DATUM | ||||
| BILLCREAIA | Billing/Invoice Creation in Advance | AUTTE | CHAR | 1 | XFELD | ||||
| RULEDATFRO | Rule for Origin of Start Dates | LODAR | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| RULEDETBIL | Rule for Determination of a Deviating Billing/Invoice Date | PERAF_FP | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| CALDEFDAYS | Calendar for Defining Days Relevant to Billing/Invoicing | FAKCA | CHAR | 2 | Assigned to domain | WFCID | |||
| DATESTO | Dates to | TBDAT | DATS | 8 | DATUM | ||||
| RULDATESTO | Rule for Origin of End Dates | TBDAR | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| ROUTING_NO | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
| CO_APLZL | General counter for order | CO_APLZL | NUMC | 8 | Assigned to domain | CO_APLZL | |||
| RESERV_NO | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
| RES_ITEM | Item Number of Reservation/Dependent Requirement | RSPOS | NUMC | 4 | RSPOS | RPO | |||
| PO_NUMBER | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| ITUNLIMIT | Item unlimited in value | FPLTU | NUMC | 6 | Assigned to domain | FPLTR | |||
| PAYCARDS1 | Payment cards: Status regarding requirements | AUST1_CC | CHAR | 1 | AUST1_CC | ||||
| PAYCARDS2 | Payment cards: Totals status - Call external system | AUST2_CC | CHAR | 1 | CCALL | ||||
| PAYCARDS3 | Payment cards: Overall status - Responses from ext. system | AUST3_CC | CHAR | 1 | REACT_SD | ||||
| PAYCARDS4 | Payment cards: Reserve | AUST4_CC | CHAR | 1 | CHAR1 | ||||
| PAYCARDS5 | Payment cards: Authorization block | AUST5_CC | CHAR | 1 | XFELD | ||||
| INTPROJNO | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
| AUTOCREATE | Automatic creation of correction dates in billing plan | AUTKOR | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPISDBPL using ABAP code?
As BAPISDBPL 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 BAPISDBPL as there is no data to select.How to access SAP table BAPISDBPL
Within an ECC or HANA version of SAP you can also view further information about BAPISDBPL 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