BAPI1300PLNDAX SAP (IS-H BAPI Planned Values per Service and OU; with Checkboxes) Structure details
Description: IS-H BAPI Planned Values per Service and OU; with Checkboxes
Related tables to BAPI1300PLNDAX
Access table BAPI1300PLNDAX
Structure field list including key, data, relationships and ABAP select examples
BAPI1300PLNDAX 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 "IS-H BAPI Planned Values per Service and OU; with Checkboxes" 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_BAPI1300PLNDAX TYPE BAPI1300PLNDAX.
The BAPI1300PLNDAX table consists of various fields, each holding specific information or linking keys about IS-H BAPI Planned Values per Service and OU; with Checkboxes data available in SAP. These include INSTITUTION (Institution), SRVCATID (IS-H: Service Catalog Identification Key), SERVICEID (Service in Service Catalog), REQ_DEPT_OU (Departmental Organizational Unit That Requests the Service).. 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 BAPI1300PLNDAX 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 |
| CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| INSTITUTION | Institution | EINRI | CHAR | 4 | TN01 | ALPHA | EINRI | EIN | |
| SRVCATID | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | TNK01 | ALPHA | TARID | TAK | |
| SERVICEID | Service in Service Catalog | TARLS | CHAR | 10 | NTPK | ALPHA | TARLS | TAL | |
| REQ_DEPT_OU | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | NORG | ALPHA | ORGID | ||
| ENDDATE | End Date of a Planned Value | ISH_LPENDT | DATS | 8 | DATUM | ||||
| BEGDATE | Start Date of a Planned Value | ISH_LPBEDT | DATS | 8 | DATUM | ||||
| BEGDATEX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| PLAN_AMNT | Planned Quantity of Service | ISH_LPMNG | NUMC | 4 | NUMC4 | ||||
| PLAN_AMNTX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| PLAN_DAYS | IS-H: Planned days | ISH_PTAGE | NUMC | 6 | NUMC6 | ||||
| PLAN_DAYSX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| PLAN_DAYS_SH | IS-H: Planned Number of Days with Discount | ISH_STAGE | NUMC | 6 | NUMC6 | ||||
| PLAN_DAYS_SHX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| AGREE_AMNT | IS-H: Agreed Number in Accordance with V2/V3 | ISH_LVMNG | NUMC | 4 | NUMC4 | ||||
| AGREE_AMNTX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| DEMAND_AMNT | IS-H: Required Number in Accordance with V2/V3 | ISH_LFMNG | NUMC | 4 | NUMC4 | ||||
| DEMAND_AMNTX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| DEMAND_EXTRA | IS-H: Agreed surcharges or discounts, BAPI planned values | ISH_BAPI_PLN_PRICE | DEC | 23(4) | BAPICURR | ||||
| DEMAND_EXTRAX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| CURRKEY | IS-H: Currency Key | RI_WAERS | CUKY | 5 | Assigned to domain | WAERS | |||
| CURRKEY_ISO | IS-H: ISO Currency Service Price | ISH_BAPI_SRVPR_CURR_ISO | CHAR | 3 | ISOCD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPI1300PLNDAX using ABAP code?
As BAPI1300PLNDAX 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 BAPI1300PLNDAX as there is no data to select.How to access SAP table BAPI1300PLNDAX
Within an ECC or HANA version of SAP you can also view further information about BAPI1300PLNDAX 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