Functionality
This BAPI method is part of the Clinical System component ofIS-H*MED for hospitals.
It is used to create medical services for a patient who is alreadyknown in the system. You cannot create services for provisional patientmaster data using this method.

Notes
You must enter the client, institution and patient number for which youwish to create the service, as import parameters.
The following fields must be filled in the MEDICALSERVICE_INPUTtable:

• CLIENT (Client)


• INSTITUTION (Institution)


• PATIENTID (Patient Number)


• BPARTNER (Business Partner)


• SERVICE_STATUS (Service Status)


• PERFORM_OU (Performing Organizational Unit)


• SERVICEID (Service within Service Catalog)


• REQ_NURS_OU (Nursing Organizational Unit)


• ALTBILLCAT (Service Catalog Identification)

If you enter a case number which already exists for the patient (whichis optional), the system will create a case-related service. No otheroptional fields have an effect on the process of this function.
If you optionally enter the sequence number (SERVICE_SEQNO) ofthe service, the system will not interpret this when creating theservice. Following a successful update, the system will return thesequence number of the service, generated by the system, using thetables MEDICALSERVICE_OUTPUT and STATUS_OUTPUT.
During this method, the system will first check existing tables forerrors and consistency. If the system finds an error in a record, itwill log this internally and will not change the service in thedatabase.
You must use the internal description when entering the service status.The BAPI method is implemented for the following service statuses:

• Requested


• Performed


• Released


• Canceled


• Confirmed-Requested


• Unconfirmed-Requested

The parameter TESTRUN is optional. If it contains an "X", themodule will run in test mode. The test mode is used to checktransferred data (for consistency and errors). The system will returnto the user any errors determined during this check in the RETURN
table. The system will not write to the database in test mode.
Possible return values and their meanings are listed in the parameterdocumentation for the RETURN table.
You will require the following authorizations to execute this method:
On Patient level: N_NLEM_PATNR;
On Service level: N_NLEI_ANF, N_NLEI_ANP andN_NLEI_ERB.
The system will try to process, i.e. update, every transferredMEDICALSERVICE_INPUT record. If you are creating several datarecords and one service (i.e. its attributes) is incorrect, the systemwill still process all other data records. The system will not updatethe incorrect service. It will produce a relevant error message.

Description
This return parameter contains the worst message type which can occurin the return parameter RETURN. You can use this to execute asimple success analysis, without having to examine the structure or theRETURN table in detail. You can limit this to all cases whichcontain 'E' or 'A' here as the worst type.
The processing of the message types ' ', 'S', 'I' and 'W' issuccessfully completed. We could not process data for message types 'E'or 'A'.

Value range


• ' ': No message occurred


• 'S': Success message


• 'I': Information message


• 'W': Warning


• 'E': Error


• 'A': Abort

Description
In this field you must manually enter the client. When you create orchange objects, the system will check this entry to ensure that it isprocessing in the correct client.

Value range
All clients stored in the system.
This field is alpha-converted, which means that if you enter numbersonly, you can omit the leading blanks and leading zeroes.

Default
This value is not preassigned.

Description
In this field you must manually enter the responsible institution.

Value range
All institutions stored in the system.
This field is alpha-converted, which means that if you enter numbersonly, you can omit the leading blanks and leading zeroes.

Default
This value is not preassigned.

Description
Manual Entry of the Patient Number Within the Corresponding Client.

Value range
This field is alpha-converted, which means that if you enter numbersonly, you can omit the leading blanks and leading zeroes.

Default
This value is not preassigned.

Description
To check the consistency of data which should be updated, withoutmaking database changes, you can execute a test run.

Value range
This parameter must be set to 'X', to execute a test run withoutdatabase changes.

Default
The parameter is preassigned, not with 'X', but with SPACE. If thesystem does not transfer the parameter when calling, it will notexecute a test run, but will update the data in the database (updaterun).

Description
In this table you enter the data of the patient-related services youwish to create. As a rule the system will save these services with apatient reference. If you enter the case number (PATCASEID),which is optional, you can also create case-related services for thepatient.
The following attributes must be filled on order to create a service:


• CLIENT (Client)


• INSTITUTION (Institution)


• PATIENTID (Patient Number)


• BPARTNER (Business Partner)


• SERVICE_STATUS (Service Status)


• PERFORM_OU (Performing Organizational Unit)


• SERVICEID (Service Within a Service Catalog)


• REQ_NURS_OU (Nursing Organizational Unit)


• ALTBILLCAT (Service Catalog Identification)

All other fields are optional and have no effect on the execution ofthe function.

Value range
NOTE: The SRV_TIME_LIMIT field may only contain a number valuebetween 0 and 255, otherwise the system will crash.

Default

Description
The system will return the generated services with the servicecharacteristics to this table.
The SERVICE_SEQNO field of the MEDICALSERVICE_OUTPUTtable contains the sequence number of the service. In test mode, thesystem will assign a temporary service number, which is recognizable asa value greater than 9000000000. In update mode the attribute willcontain service number newly assigned by the number range.
You can also find these service numbers in the STATUS_OUTPUTtable which you can use to create a connection between the service
record and the status record.

Value range

Default

Description
The system will return any errors which may have occurred to thistable.

Value range
The following error messages may occur:


• NC 035: Enter a valid institution.


• NC 071: Incorrect parameter specification when SERVICE_STATUS called.


• NC 601: Mandatory parameter MEDICALSERVICE_INPUT not filled (module
BAPI_MEDSRV_CREATEMULT_PATIENT).

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

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

<<)>SERVICE_STATUS>.

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

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

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

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


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


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

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

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

• NFCL 001: MAP_STRUCT_TO_INTERN: NLEI and NLEM data record do not match.


• NFCL 003: Internal service status for could not be
found.

• NFCL 004: External service status for could not be
found.

• NFCL 007: Service : No key fields can be
modified.

• NFCL 008: Service : Service code is empty.


• NFCL 009: Service is invalid or does not
exist.

• NFCL 010: You cannot assign the service to
this movement.

• NFCL 011: Service has status
and cannot have a reference to a movement.

• NFCL 012: Service has status
and must have a reference to a movement.

• NFCL 013: Service : Organizational unit
is not a valid Requesting Department Organizational Unit.

• NFCL 013: Service : Organizational unit
is not a valid Requesting Nursing Organizational Unit.

• NFCL 013: Service : Organizational unit
is not a valid Performing Organizational Unit.

• NFCL 014: Service : Error creating the
service - service assignment.

• NFCL 015: Service : Time stamp SRV_STARTDATE
is not correct or is empty.

• NFCL 016: Service : SRV_ANCHOR
is not contained in the domain.

• NFCL 016: Service : Field value
UNIT_TIME_LIMIT is not contained in the domain.

• NFCL 017: Service is linked to more than
one request.

• NFCL 018: Service : Cannot find request
.

• NFCL 019: You cannot change the request reference for service
.

• NFCL 022: Cannot read parameter N1ZOTYP for institution .


• NFCL 023: Service : Error <(>

<<)>sy-subrc> breaking down costs.

• NFCL 026: Cannot cancel service .


• NFCL 028: Service : Time limit value is
greater than 255.

• NFCL 029: Time interpretation does not exist in
institution .

• NFCL 031: Service is linked to more than
one preregistration.

• NFCL 033: Service : Cannot find
preregistration PREREG_SEQNO

• NFCL 034: Service has status
, but no request or preregistration.

• NFCL 035: Service : Room <(>

<<)>IDENTIFICATION_ROOM> is not valid.

• NFCL 036: Room does not match room
for service <(>
<<)>SERVICE_SEQNO>.

• NFCL 037: Degree of infection has not been assigned to
institution <(> <<)>INSTITUTION>.

• NFCL 038: Localization has not been defined for
institution <(> <<)>INSTITUTION>.

• NFCL 042: Service The linked appointment is
canceled.

• NFCL 043: Service : The linked appointment
is incorrect.

• NFCL 049: Request : Org. unit is not a valid
REQ_DEPT_OU

• NFCL 056: Service : Value <(>

<<)>PATIENT_CONSENT> of patient consent is not allowed.

• NFCL 058: An instance of the class CL_ISHMED_SERVICE could not be
created.

• NFCL 059: Constructor Class CL_ISHMED_SERVICE: Transfer parameters were
incorrect.

• NFCL 060: Class CL_ISHMED_SERVICE: Parameter I_COPY_OF was incorrect.


• NFCL 061: Class CL_ISHMED_SERVICE: Parameter I_ENVIRONMENT was empty or
incorrect.

• NFCL 062: Class CL_ISHMED_SERVICE: Important data could not be found.


• NFCL 063: Class CL_ISHMED_SERVICE: When instantiating an unforeseeable
error occurred.

• NFCL 064: Service :The employee responsible is not
specified.

• NFCL 065: Service : The employee responsible is
not valid.

• NFCL 066: Desired time cannot be in the past when confirming.


• NFCL 067: Position type is not available in institution
<(> <<)>INSTITUTION>.

• NFCL 073: : The field STORN cannot be changed
with CHANGE.

• NFCL 078: Patient with provisional master data does not exist.


• NFCL 079: Service is linked to more than
one provisional patient.

• NFCL 083: Service : Provisional patient may
not be changed.

• NFCL 104: Preregistration service: Inconsistency between case <(>

<<)>PATCASEID> and patient .

• NFCL 146: Enter a valid client.


• NFCL 147: Enter a valid patient number.


• NFCL 148: Entries between MEDICALSERVICE_INPUT-SERVICE_SEQNO and
STATUS_INPUT-SERVICE_SEQNO are different.

• NFCL 148: Entries between MEDICALSERVICE_INPUT-PATIENTID and PATIENTID
are different.

• NFCL 159: Input value SRV_ARCHOR is not permitted in field
.

• NFCL 159: Input value UNIT_TIME_LIMIT is not permitted in field
.

• NFCL 161: Service can only be assigned to
an unconfirmed request.

• NFCL 163: Case does not belong to Patient <(>

<<)>PATIENTID>.

• NFCL 166: Service : <(>

<<)>APPT_ID> is invalid.

• NFCL 170: Service : <(>

<<)>PREREG_SEQNO> is not the same as the connected preregistration <(>
<<)>PREREG_SEQNO>.

• NFCL 171: Service : <(><<)>REQ_ID> is not
the same as the connected request .

• NFCL 173: Service : Preregistration

does not belong to patient .

• NFCL 200: Service will be updated without cancellation reason.


• NFCL 201: End date of validity cannot be calculated without &

<<)>UNIT_TIME_LIMIT> entry.

• NFCL 202: Correct desired time.


• NFCL 203: Preregistration is not valid.


• NFCL 204: Field may not be filled.


• NFCL 206: Service : Request does


• not belong to patient .


• NFCL 207: Request is invalid.


• NFCL 208: You can only enter a request or a preregistration.


• N1 014: Patient does not exist.


• N1 016: Patient is locked by (re-try later).


• N1 018: Patient canceled.


• N1 026: Case is canceled.


• N1 034: Case does not exist.


• N1 036: Enter a valid institution.


• N1 199: Organizational unit has not been released.


• N1 199: Organizational unit has not been released.


• N1 199: Organizational unit has not been released.


• N1 204: Organizational unit does not exist.


• N1 204: Organizational unit does not exist.


• N1 204: Organizational unit does not exist.


• N2 673: Institution does not exist.


• N2 674: Catalog does not exist.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• N2 679: Checkbox contains a non-permitted value.


• NF 036: Enter a valid cancellation reason.


• NF 615: Enter a valid employee.


• NF1 040: Surgery anchor service not found (Parameter N2ANKLOP).


• NF1 041: AN Anchor service not found (Parameter N1ANKLAN).


• NF1 048: ON the case is already
completed.

Description
The system will return the Service-Employee-Status assignment of thechanged service to this table.
The SERVICE_SEQNO attribute of the STATUS_OUTPUT tablecontains the sequence number of the service, which you can also find inthe corresponding data record of the MEDICALSERVICE_OUTPUTtable.

Value range