> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/connectors/areas/business-systems/sap/sap-bapi/basic-api/bapi-bapi_monitor_getlist.md). # BAPI: BAPI\_MONITOR\_GETLIST This BAPI returns information for BAPI's relating to the position in the BAPI application tree. Giving an \* in the first input parameter will give a full list of all BAPI's.\ The other parameters can be left blank thus letting the system using default values. It is possible to select BAPI's for a list of application nodes by sending in a table COMPONENTS2SELECT with rows of nodes in the field COMPONENT. This BAPI together with the first (ZNCFLOW\_APPLICATION\_COMPONENT) will give you enough information to draw the complete Application tree containing all BAPI's. | **Field** | **Description** | **Type** | **Spec** | **Example** | | ----------------- | -------------------------------------- | -------- | ---------- | ----------------------------- | | OBJECTTYPE | Object type | I | CHAR10 | \* (will result in full list) | | SHOW\_RELEASE | Release /Reference Release to Display | I | CHAR4 | Use default | | BAPIS\_POTENTIAL | Display Potential BAPIs | I | CHAR1 | Use default | | BAPIS\_NEW | Display New BAPIs in Release | I | CHAR1 | Use default | | BAPIS\_OLD | Display BAPIs from Previous Releases | I | CHAR1 | Use default | | RELEASED\_BAPI | Release Status of BAPIs | I | CHAR1 | Use default | | RELEASED\_FUNC | Release Status of Function Modules | I | CHAR1 | Use default | | RETURN | Return messages | O | BAPIRET2 | | | COMPONENTS2SELECT | Application Components/Areas to Select | T | BAPIMONCOM | | | SYSTEMS2SELECT | Original System of BAPIs to Select | T | BAPISRCSYS | Use default | | BAPILIST | List of Selected BAPIs | T | BAPIMONSTR | | **Structure: BAPIRET2** | **Field** | **Description** | **Spec** | **Example** | | ------------ | ------------------------------------------------------------ | -------- | ----------- | | TYPE | Message type: S Success, E Error, W Warning, I Info, A Abort | CHAR1 | | | ID | Message Class | CHAR30 | | | NUMBER | Message Number | NUMC3 | | | MESSAGE | Message text | CHAR220 | | | LOG\_NO | Application log: log number | CHAR20 | | | LOG\_MSG\_NO | Application log: Internal message serial number | NUMC6 | | | MESSAGE\_V1 | Message Variable | CHAR50 | | | MESSAGE\_V2 | Message Variable | CHAR50 | | | MESSAGE\_V3 | Message Variable | CHAR50 | | | MESSAGE\_V4 | Message Variable | CHAR50 | | | PARAMETER | Parameter Name | CHAR32 | | | ROW | Lines in parameter | INT4 | | | FIELD | Field in parameter | CHAR30 | | | SYSTEM | Logical system from which message originates | CHAR10 | | **Table: COMPONENTS2SELECT** | **Field** | **Description** | **Spec** | **Example** | | --------- | ------------------------ | -------- | ----------- | | COMPONENT | Application component ID | CHAR24 | | **Table: BAPILIST** | **Field** | **Description** | **Spec** | **Example** | | ---------- | ----------------------------------------------- | -------- | ------------------------------------------ | | OBJECTTYPE | Object Type | CHAR10 | SFLIGHT | | OBJECTNAME | Object name | CHAR32 | Flight | | BAPINAME | Method name of BAPI | CHAR32 | GetDetail | | ABAPNAME | Function module name | CHAR30 | BAPI\_FLIGHT\_GETDETAIL | | COMP | Application component ID | CHAR24 | BC-DWB | | CREA\_REL | Release at Creation | CHAR4 | 610 | | CREATOR | Author | CHAR12 | SAP | | UDATE | Changed On | CHAR8 | 18.09.2001 | | CHANGER | Last changed by | CHAR12 | SAP | | SOURCESYS | Name of the SAP system | CHAR8 | SAP | | BAPI\_AG | Application area or BAPI work group responsible | CHAR5 | Basis | | ISINTERFAC | Interface object type | CHAR1 | | | BAPI\_REL | Release status of BAPI method | CHAR1 | X | | FUNC\_REL | Release status of function module | CHAR1 | R | | OBSOLETE | Release in which the status was set to obsolete | CHAR4 | | | FM\_DOCU | Documentation on function module exist | CHAR1 | | | BO\_DOCU | Documentation for business object exist | CHAR1 | | | MESTYPE | Message type | CHAR30 | | | VERB | Object type component | CHAR32 | GETLIST | | BO\_TEXT | Description | CHAR80 | Flight with connection data (SAP training) | | BAPI\_TEXT | Description | CHAR80 | Find list of flights | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.novacuraflow.com/connectors/areas/business-systems/sap/sap-bapi/basic-api/bapi-bapi_monitor_getlist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.