Ansicht
Dokumentation

BAPI_MEDDOC_GETSTATUSLIST - IS-H*MED: Get Next Status or Status Network

BAPI_MEDDOC_GETSTATUSLIST - IS-H*MED: Get Next Status or Status Network

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This method retrieves the next status, the data of the status transferred or the status network of the document type. For medical documents, you can define different status networks for each document type in the customizing function. You can set up the status network so that a status has one or more next statuses.

These can contain the following status information:

  • You can make a selection for the system to retrieve the next status with a release indicator (GET_RELEASE_STATUS). When Releasing a Document, you can only set one status with a release indicator. If the system determines that a next status with a release indicator is not included, a corresponding error message will appear. If more than one release status exists as a next status, no message will appear. The table STATUSDATA contains the corresponding number of entries.
  • You can make a selection so that the system retrieves the next status without a release indicator (GET_NORELEASE_STATUS). If the system determines that no next status without an indicator should be included, an error message is returned. If more than one status without a release indicator exists as the next status, no message is displayed. The table EXT_STATUSDATA contains the corresponding number of entries.
  • You can make a selection so that the system retrieves the next status (GET_NEXT_STATUS). The system will then search for all next statuses, independent of their release indicator. If the system determines that a next status should not be included, a corresponding error message will appear. If more than one next status exists, no message will appear. The table STATUSDATA contains the corresponding number of entries.
  • If the system should retrieve a next status, that is, if either GET_NEXT_STATUS, GET_NORELEASE_STATUS or GET_RELEASE_STATUS is selected, the system will require a status. You can include either the internal status (STATUSINTERN) or the external language-dependent status (STATUSEXTERN). If no status is included, the system will retrieve the first status(es) of the status network, that is, the status that can be allocated when creating a document.
  • You can make a selection directing the system to transfer data for a status (GET_STATUS_DATA). You can include either the internal status (STATUSINTERN) or the external language-dependent status (STATUSEXTERN). The system exports the status data In the table STATUSDATA .
  • You can make a selection so that the first status of the status network is retrieved, i.e. the status that is allocated while creating a document (GET_STATUS_CREATE). You should remember that a status network can have several primary / initial statuses.
  • If GET_NEXT_STATUS, GET_RELEASE_STATUS, GET_STATUS_DATA and GET_STATUS_CREATE are not selected, the system will export the entire status network of the document type.

If you select more than one option, the system will use the following priority:

  1. Get Release Status
  2. Get Unreleased Status
  3. Get Next Status
  4. Get Status Data
  5. Get Creation Status
  6. Export Status Network of the Document Type

Example

Notes

Further information





Parameters

DOCUMENTTYPE
GET_NEXT_STATUS
GET_NORELEASE_STATUS
GET_RELEASE_STATUS
GET_STATUS_CREATE
GET_STATUS_DATA
RETURN
STATUSDATA
STATUSEXTERN
STATUSINTERN
WORST_RETURNED_MSGTY

Exceptions

Function Group

1400

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4905 Date: 20240523 Time: 171133     sap01-206 ( 81 ms )