Functionality
This BAPI method is part of the basic data in the Clinical Systemindustry-specific component.
It is used to create and change the IS-H*MED-relevant master data of aservice from the service catalog.

Notes
The client, institution, and service catalog in which the service willchanged or the IS-H*MED-relevant data supplemented, must be entered asimport parameters.
The following tables can be transferred to the BAPI for changing aservice:
Table name,,Description
SRVCAT_SRVDATA_TPK,,Service header data
SRVCAT_SRVDATA_TPM,,Medical enhancements to service catalogpositions
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 mustbe entered
To change a service, you must simply fill the SRVCAT_SRVDATA_TPKstructure. Entering other structures is optional. However, if they arealso supplied, you must at least fill all key fields. Key fields cannotbe changed when you change an IS-H*MED service.
If you wish to change a SRVCAT_* record, a corresponding record mustexist in the SRVCAT_SRVDATA_TPK structure.
For each field in the above tables (except key fields and fields whichcannot be changed), there is also a checkbox of the same name, butending with an "X". These checkboxes must be set to the value 'X', ifthe corresponding attribute should be written to the database. Theattributes of checkboxes which are not set to the value 'X', will notbe changed in the database.
This guarantees that existing fields are not inadvertently overwrittenin the database and also that their content is not deleted.
When the method runs, the system will first check the existing tablesfor errors and inconsistency. If the system finds even one error in arecord, it will log this internally and will not change the service inthe database. Any errors found in the check will be returned to theuser in the RETURN table.
The parameter TESTRUN is optional. If it is set to 'X', thesystem will run the BAPI in test mode. The test mode is used to checkthe transferred data. In test mode, when the system checks theconsistency of the data, the system will not write to the database.
In the parameter documentation of the RETURN table, you willfind the return values possible and their meanings.

Further information
If you wish to initially create a service in the system, you must usethe BAPI BAPI_HCSRVCAT_ADDITEM, provided by IS-H. You can thenuse the IS-H*MED BAPI BAPI_MEDSRVCAT_CHANGEITEM, to adapt orsupplement 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-BAPIBAPI_HCSRVCAT_CHANGEITEM.

Description
This return parameter contains the most severe message type generatedin the RETURN parameter. You can use this as a simple successanalysis, without having to examine the structure or the RETURNtable in detail. You can always limit this to the cases which contain'E' or 'A' here as the most severe type.
With message types ' ', 'S', 'I' and 'W' processing is successfullycompleted. With message types 'E' or 'A' the system could not processthe data.

Value range

• ' ': No message occurred


• 'S': Success message


• 'I': Information message


• 'W': Warning


• 'E': Error


• 'A': Abort

Description
You must manually enter the client in this field. When you create orchange objects the system will check this field to ensure processingoccurs in the correct client.

Value range
All clients stored in the system.
This field is alpha-converted, which means that you can omit theleading blanks or zeroes from entries which contain numbers only.

Default
No value is preassigned.

Description
You must manually enter the corresponding institution in this field.

Value range
All systems stored in the system.
This field is alpha-converted, which means that you can omit theleading blanks or zeroes from entries which contain numbers only.

Default
No value is preassigned.

Description
Manual entry of the service catalog number within the correspondinginstitution.

Value range
This field is alpha-converted, which means that you can omit theleading blanks or zeroes from entries which contain numbers only.

Default
No value is preassigned.

Description
If you only wish to check the consistency of data which is to beupdated, without making changes in the database, you can execute a testrun.

Value range
If you wish to execute a test run without database changes, you mustset this parameter to 'X'.

Default
This parameter is preset, but with SPACE rather than 'X'.
If the parameter is not supplied when the function is called, thesystem will not perform a test run, but will update data in thedatabase (update run).

Description
Any errors which may have occurred will be returned to this table.

Value range
The following error messages may occur:


• NC 035: Enter a valid institution


• NC 603: Current client is , but data is determined for client


• NC 605: Desired function not possible without value in field


• NFCL 146: Enter a valid client


• NFCL 148: Entries between - and <(>
  <<)>CLIENT> are different
  
  • NFCL 148: Entries between
  - and <(>
  <<)>INSTITUTION> are different
  
  • NFCL 148: Entries between
  - and <(>
  <<)>SRVCATID> are different
  
  • NFCL 148: Entries between
  - and <(>
  <<)>SERVICEID> are different
  
  • NFCL 152: Service has not been replaced
  
  
  • NFCL 156: Enter a valid service catalog identification
  
  
  • NFCL 157: Enter a valid service identification within a service catalog
  
  
  • NFCL 159: Input field is not permitted in
  
  
  • NFCL 209: Error while creating medical enhancements to service catalog
  items
  
  • NFCL 210: Error while changing medical enhancements for service catalog
  items
  
  • NFCL 212: Error while creating resource profile
  
  
  • NFCL 213: Error while changing resource profile
  
  
  • NF 161: Enter a valid priority
  
  
  • NF 249: Degree of infection is invalid
  
  
  • NF 572: Enter a valid position
  
  
  • NF1 026: Waiting list category is invalid
  
  
  • NF1 303: Error when creating the excluded localization (Radiology)
  
  
  • NF1 304: Error when changing the excluded localization (Radiology)
  
  
  • NF1 306: Error when creating the excluded transport types
  
  
  • NF1 307:Error when changing the excluded transport types
  
  
  • NF1 309: Error when creating the lab parameter
  
  
  • NF1 311: Error when changing the lab parameter
  
  
  • N1 016: Patient is locked by (re-try later)
  
  
  • N1 036: Enter a valid institution
  
  
  • N2 300: has no authorization in institution <(>
  
  <<)>INSTITUTION>
  
  • N2 588: Catalog is locked by
  
  
  • N2 613: Error while creating service
  
  
  • N2 614: Error while changing service
  
  
  • N2 664: Structure is empty
  
  
  • N2 668: Key fields (<()>) are missing from structure
  
  
  
  • N2 667: The key field is different from the import parameter
  
  
  • N2 669: The key fields of structure are not those of the
  higher-level structure
  
  • N2 673: Institution does not exist
  
  
  • N2 674: Catalog does not exist
  
  
  • N2 678: Value specified for is not permitted by check table <(>
  
  <<)>TABLE>
  
  • N2 677: Service text () contains illegal special characters
  
  
  • N2 679: Checkbox contains a non-permitted value ( )
  
  
  • N2 680: Structure contains entries with identical key
  fields.
  
  • N2 728:
  records contains errors. Not written to database.
  
  SV 009: An entry with the same key already exists

  Description
  In this table you supply the BAPI with the IS-H*MED header data of theservice you wish to create.
  The key fields CLIENT, INSTITUTION, SRVCATID, and SERVICEID must befilled. All other fields are optional.
  You can enter attributes for the services to be changed, in the fieldsof the SRVCAT_SRVDATA_TPK table. In addition to these fieldsthere is a field in the structure with the same name, but ending withan 'X'.
  The system will only evaluate the corresponding attribute if the
  relevant checkbox contains an 'X'.
  The system will process every transferred record providing no errorsoccur during processing. If such errors do occur, the system willcollect them in the RETURN parameter.

  Description
  In this table you supply the BAPI with the IS-H*MED data of the servicelaboratory parameter you wish to create.
  The key fields CLIENT, INSTITUTION, SRVCATID, and SERVICEID must befilled. All other fields are optional.
  You can enter attributes for the services to be changed, in the fieldsof the SRVDATA_TPLAB table. In addition to these fields there isa field in the structure with the same name, but ending with an 'X'.
  The system will only evaluate the corresponding attribute if therelevant checkbox contains an 'X'.
  The system will process every transferred record providing no errorsoccur during processing. If such errors do occur, the system willcollect them in the RETURN parameter.

  Description
  In this table you supply the BAPI with the data of the excludedlocalization of the service to be created.
  The key fields CLIENT, INSTITUTION, SRVCATID, SERVICEID, andLOCALIZATION must be filled.
  The system will process every transferred record providing no errorsoccur during processing. If such errors do occur, the system willcollect them in the RETURN parameter.

  Description
  In this table you supply the BAPI with the data of the medicalenhancement of the service to be created.
  The key fields CLIENT, INSTITUTION, SRVCATID, and SERVICEID must befilled. All other fields are optional.
  You can enter attributes for the services to be changed, in the fieldsof the SRVDATA_TPM table. In addition to these fields there is afield in the structure with the same name, but ending with an 'X'.
  The system will only evaluate the corresponding attribute if thecorresponding checkbox contains an 'X'.
  The system will process every transferred record, providing no errorsoccur during processing. Any such errors which do occur will becollected in the RETURN parameter.

  Description
  In this table you supply the BAPI with the data of the resourceprofiles of the service to be created.
  The key fields CLIENT, INSTITUTION, SRVCATID, SERVICEID, PLANOBJECT,and TASK must be filled.
  All other fields are optional.
  You can enter attributes for the services to be changed, in the fieldsof the SRVDATA_TPP table. In addition to these fields there is afield in the structure with the same name, but ending with an 'X'.
  The system will only evaluate the corresponding attribute if thecorresponding checkbox contains an 'X'.
  The system will process every transferred record, providing no errorsoccur during processing. Any such errors which do occur will becollected in the RETURN parameter.

  Description
  In this table you supply the BAPI with the data of the excludedtransport type of the service to be created.
  The key fields CLIENT, INSTITUTION, SRVCATID, SERVICEID, andTRANSPORT_TYPE must be filled.
  The system will process every transferred record providing no errorsoccur during processing. If such errors do occur, the system willcollect them in the RETURN parameter.