Functionality
INCLUDE NBAPI_ISH
It enables you to create services (including assignments to physicians)for a given case.

Notes
INCLUDE NBAPI_PRECOND_AUTHORITIES
RESET N1
At case level: N_NLEI_FAL;
At service level: N_NLEI_ANF, N_NLEI_ANP and N_NLEI_ERB.
The services are always created with regard to the in-house servicecatalog. The in-house service catalog is determined using the date ofadmission or of the first visit for the case.
The generated service records are returned in the CASESERVICE_DATA
parameter table. The method attempts to generate (i.e. to update)each record passed to it. Records containing errors are flaggedaccordingly in the CASESERVICE_CDATA parameter table. In testmode, you can check the consistency of the data to be generated.
Since certain modifications result in further services being generated,(splitting of extended services caused by transfer of patient; servicegroups with automatic explosion), it can be the case that more servicesare generated than have been passed on. The services that have beenpassed on are assigned explicitly to the generated data.
INCLUDE BAPI_RET
INCLUDE NBAPI_WORST_RETURNED_MSGTY
INCLUDE NBAPI_CLIENT
INCLUDE NBAPI_INSTITUTION
INCLUDE NBAPI_PATCASEID
INCLUDE NBAPI_TESTRUN

Description
All of the generated assignments of physicians (general: businesspartners) to the generated case-related services are returned.

Description
All service assignments generated for the generated case-relatedservices are returned in this table.

Description
If you want to create further assignments of physicians to a service,you can specify these in this table. In such cases, the related datarecords must be linked via the RULETYPE and ACTIONSEQNOfields in the CASESERVICE_CDATA and CASESERVICE_CASSPARtables. You must specify an 'A' for "Create physician assignment" inthe ACTIONSEQNO field.

Description
If you wish to create additional assignments to other services for aa service, you can specify these in this table. The related data recordsmust be linked using the RULETYPE and ACTIONSEQNO fields in theCASESERVICE_CDATA and CASESERVICE_CASSSRV tables. You have to specify an'I' for "Insert" the assignment in the ACTION field.

Description
You specify the data for the case-related services to be created in thistable.
Specify the service code in the SERVICEID field and an 'I' (forinsert) in the ACTION field. You must leave the SERVICE_SEQNO
field empty. The system assigns this number when the services arecreated.
In the RULETYPE field, you must specify an identification key forthe rule type that is also passed on to the database. The rule typemust, however, be authorized for use in BAPIs. For more informationabout this, refer to the IS-H Implementation Guide in the SAPsystem by choosing Patient Accounting -> Service Rules ->Maintain Check Procedure.
You can specify attributes for the services to be created in the fieldsof the CASESERVICE_CDATA table for which there are alsocorresponding fields with the same name and the suffix "X" in thestructure. The corresponding attribute is only evaluated if the related"X field" contains an "X".
The services are always created with regard to the in-house servicecatalog. The in-house service catalog is determined using the date ofadmission or of the first visit for the case.
The following applies for the country version Switzerland:
Since the session code is stored in field WNDNR, it must be included atpositions 3 + 4 in the data passed in fieldCASESERVICE_CDATA-WOUND_NO , so as to be correctly recognized andsaved by the system.
The method attempts to generate each record passed on to it. Recordscontaining errors are flagged (by '!' in theCASESERVICE_CDATA-ACTION field) and skipped. Any errors thatoccur are collected in the RETURN parameter.
If you want to create further assignments of physicians to a service,you can specify these in the CASESERVICE_CASSPAR table. In suchcases, the related data records must be linked explicitly via theRULETYPE and ACTIONSEQNO fields. The ACTIONSEQNOfield contains a sequence number you are free to assign.

Description
The generated case-related services with the most importantcase-related service attributes are returned in this table.
Since certain services result in further services being generated,(splitting of extended services caused by transfer of patient orservice groups with automatic explosion), it can be the case that moreservices are generated than were passed on in the CASESERVICE_CDATA
structure or also further services could be modified (for example,by means of the linking of extended services).
To enable the service data that was passed on to be assigned to thegenerated data, in test mode the CASESERVICE_DATA-SERVICE_SEQNOfield contains a temporary (i.e. the number is greater than9000000000), but unique service number. In production mode, theCASESERVICE_DATA-SERVICE_SEQNO field contains the final service code.You also find the respective number in the correspondingCASESERVICE_CDATA record.
For services that may have been changed (for example, by the linking ofextended services), the CASESERVICE_DATA-SERVICE_SEQNO field alreadycontains the correct service code both in test and production mode.
The assignment of the services additionally generated to the datapassed on cannot be made as directly. In test mode, theCASESERVICE_DATA-SERVICE_SEQNO field contains a temporaryservice number (see above). In production mode, these services also havethe newly assigned service code.
The following applies for the country version Switzerland:
The session code is returned in positions 3 and 4 of the fieldCASESERVICE_DATA-WOUND_NO.
INCLUDE NBAPI_DOCCOLLCONTENT
INCLUDE NBAPI_DOCCOLLINFO
For the definition of the parameter DOCID, you should note in particularthat this is composed of the parameters RGART and LFDAK plus a 2-digitidentifier for the long text type. RGART is subject to alphaconversion,and there is no implicit conversion for LFDAK. The identifier '01'refers to the reason long text (BegTX), '02' refers to the comment longtext (RemTX). To ensure that the DocID is correct, it must always becreated by copying the values RGART and LFDAK from the structureBAPI2099DATA.
In such cases, a valid value would have the following format:
DOCINFO-DOCID(10) = BAPI2099DATA-RGART.
DOCINFO-DOCID+10(10) = BAPI2099DATA-LFDAK.
DOCINFO-DOCID+20 = '01'.

Description
Any errors that may have occurred are returned in this table.

Value range
The following error messages can occur:

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


• NC 604: Unit of measure cannot be changed. Catalog value applies.


• NS 016: Institution does not exist


• NS 017: Company code does not exist


• MC 600: System error occurred during lock administration


• MC 601: Object requested is currently locked by user


• MC 602: The requested object is locked by another transaction


• MC 603: Lock table overflow


• DA 300: No active nametab exists for


• NE 505: You are not authorized to create services


• N1 117: Institution does not exist


• N1 034: Case does not exist


• N1 613: You are not authorized to process this case in institution


• N1 601: Number of parameters in check object is
invalid

• N1 602: Specified object not maintained in user
master

• N1 603: No profile is entered in user master


• N1 604: Authorization for not
found in user master

• N1 606: You are not authorized to carry out actions in the SAP System


• N1 605: The user master is incorrectly set up (SY-SUBRC =
)

• N1 026: Case is cancelled


• N1 002: Case has no further movements


• N1 114: On , no entry for system parameter in
inst. (time-dep.)

• NE 532: Invalid rule type


• NE 508: Invalid action (only permitted)


• NE 509: Enter a service


• NE 510: Invalid entry in field LNRLS


• NE 522: Multiplication factor is empty


• N3 675: Enter a service for the alternative service catalog


• N3 676: Enter the corresponding service catalog for the service/column


• 00 126: Negative values not allowed


• N3 677: Enter either alternative price or alt. service catalog / column


• N3 266: Specify a valid function for the business partner


• N3 267: Enter a business partner for the function


• N3 269: Service : Business partner already has
the function

• N3 338: Specify a valid service code


• N0 466: Service catalog is not defined in institution


• N3 404: Service does not exist


• N0 084: Column is not defined in service catalog


• N2 077: Enter a valid assignment type


• N2 041: Organizational unit does not exist


• 00 002: Please enter a valid value


• NE 501: Service // is not
defined

• N1 563: Movement number of case does not exist


• N3 071: Business partner does not exist (check entry)


• N3 270: Function does not exist (check entry)


• N3 284: Provisional billing carried out for the case - limited changes
possible

• N3 456: Final billing done for case . Billable services
cannot be maintained.

• N3 864: Service is blocked for entry


• NE 511: Alternative service text not allowed for service


• N3 608: No entry for service in service catalalog


• NE 512: Enter a non-billable service group


• NE 513: Enter assignment type for service group


• N3 886: Specify an alternative price for service


• N3 887: An alternative price is not allowed for service


• N3 769: Entering extended services for outpatient cases is not
supported

• NE 515: System error: RNLSR does not correspond to NLEI


• N1 563: Movement number of case does not
exist

• NE 516: Invalid movement assignment of an extended service


• NE 517: Extended services must be for longer than one second


• N3 320: Immediate service: A time interval in invalid here.


• N3 006: Start date is after end date


• N3 302: Service in service catalog only valid
between and

• N3 625: Service : Admission date is after start date


• N3 626: Service : Dischage date is before end date


• NE 518: Complete time specification for service


• N3 313: Extended service, a quantity specification is invalid here


• N3 376: You cannot enter planned services in the past


• N3 768: Check the service status


• NE 507: You are not authorized to enter services for OU


• N3 874: Service was already fully billed for on


• N3 309: Time overlap with identical service


• NE 519: Number range interval not found


• NE 520: Number assignment failed


• NF 575: Enter a valid localization

The following warning messages can occur:

• N3 684: Case final billed. Billable services cannot be entered.


• NE 514: Assignment type ignored by the system


• N3 768: Check the service status


• N3 779: Movement has "planned" status, service has "actual" status


• N3 331: Movement has "planned" status. Extnd. svces. must have
"planned" status.