Ansicht
Dokumentation

BAPI_MEDSRVCAT_CHANGEITEM - IS-H*MED: BAPI MEDSrvCat.ChangeItem - Changing Service Master Data

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

This BAPI method is part of the basic data in the Clinical System industry-specific component.

It is used to create and change the IS-H*MED-relevant master data of a service from the service catalog.

Example

Notes

The client, institution, and service catalog in which the service will changed or the IS-H*MED-relevant data supplemented, must be entered as import parameters.

The following tables can be transferred to the BAPI for changing a service:

Table name	Description
SRVCAT_SRVDATA_TPK	Service header data
SRVCAT_SRVDATA_TPM	Medical enhancements to service catalog positions
SRVCAT_SRVDATA_TPP	Resource profile for services
SRVCAT_SRVDATA_TPLOK	Radiology: Excluded localization
SRVCAT_SRVDATA_TPTA	Radiology: Excluded transport type
SRVCAT_SRVDATA_TPLAB	Radiology: Laboratory parameter which must be entered

To change a service, you must simply fill the SRVCAT_SRVDATA_TPK structure. Entering other structures is optional. However, if they are also supplied, you must at least fill all key fields. Key fields cannot be changed when you change an IS-H*MED service.

If you wish to change a SRVCAT_* record, a corresponding record must exist in the SRVCAT_SRVDATA_TPK structure.

For each field in the above tables (except key fields and fields which cannot be changed), there is also a checkbox of the same name, but ending with an "X". These checkboxes must be set to the value 'X', if the corresponding attribute should be written to the database. The attributes of checkboxes which are not set to the value 'X', will not be changed in the database.

This guarantees that existing fields are not inadvertently overwritten in the database and also that their content is not deleted.

When the method runs, the system will first check the existing tables for errors and inconsistency. If the system finds even one error in a record, it will log this internally and will not change the service in the database. Any errors found in the check will be returned to the user in the RETURN table.

The parameter TESTRUN is optional. If it is set to 'X', the system will run the BAPI in test mode. The test mode is used to check the transferred data. In test mode, when the system checks the consistency of the data, the system will not write to the database.

In the parameter documentation of the RETURN table, you will find the return values possible and their meanings.

Further information

If you wish to initially create a service in the system, you must use the BAPI BAPI_HCSRVCAT_ADDITEM, provided by IS-H. You can then use the IS-H*MED BAPI BAPI_MEDSRVCAT_CHANGEITEM, to adapt or supplement data relevant for IS-H*MED.

If you only wish to change service master data parts relevant to IS-H, you should also use the corresponding IS-H-BAPI BAPI_HCSRVCAT_CHANGEITEM.

Parameters

CLIENT
INSTITUTION
RETURN
SRVCATID
SRVDATA_TPK
SRVDATA_TPLAB
SRVDATA_TPLOK
SRVDATA_TPM
SRVDATA_TPP
SRVDATA_TPTA
TESTRUN
WORST_RETURNED_MSGTY

Exceptions

Function Group

1405

RFUMSV00 - Advance Return for Tax on Sales/Purchases   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5474 Date: 20240606 Time: 091822     sap01-206 ( 75 ms )