Ansicht
Dokumentation

RN1FAM00 - Transfer Data for Outpatient Admission (NP40/NP41)

Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Description

With this report you can import outpatient cases with a batch input by
way of the transaction NP40. For errant records, a batch input session
fo9 the transaction NP40 (create outpatient case) will be created.

Here a sequential dataset will be read and processed using the structure information tables TNT2 and TNT2S. If you would like to test the import of the sequential dataset, you can run the report in the test mode. Here, no batch input session will be created, but only the field values will be displayed on the appropriate screens. The test mode is especially intended for checking the structuraal definition of the sequential dataset.

Requirements

If the length of a record in the seq. dataset is greater than 1024 Bytes, then the length of the buffer-variable REC in the include report RNIFAM02 will be changed appropriately.

A structural definition must exist for the sequential dataset (tables TNT2 and TNT2S). At the start of the report, you also have to enter the record identifier of the records to be processed along with the full name of the sequential dataset. If the sequential dataset contains different types of records, then the appropriate field must be checked off in the selection screen and the offset and the length of the record type indicator must be entered. If the internal number assignment is not in use, please make sure that the external number being used falls within the appropriate number range (definition in table TNKRS).

Possibly necessary conversions of the field formats can be executed in the following manner:
Define an appropriate form routine in the report RNILSI20. All changes in the format can be executed with the field symbols which you assign successively to the formal parameter. Conversion should be designed so that a valid entry format for each entry field is satisfied. You can enter the name of the form routine into the field TNT2-FORM of the table TNT2.

To read the patient nummer from the patient-case relationship table, the
indicator 'Refresh pat.no.' must be checked off in the selection screen.

To change a case or create a new one, the indicator must be read from
the seq. file. You also have to check off the indicator
'Check Update/Insert ind.'
The 'Update/Insert ind.' must occupy the last position in the seq. file,
and has to be entered at 'Position of Update/Insert ind.'

Output

If the field "Test mode" is checked off, then no batch input session will be created. On the screen you will receive only output from the screens filled-in. If you check off the "Error log", possible errors will be logged for you. The "Total log" shows you all screen fields with each of the field contents.

If you have created a batch input session, you can edit this with the transaction SM35 (System -> Services -> Batch-Input -> Edit), that is, analyze it and if necessary process it.

Example

Examples of form routines can be taken from the report RNILSI20.

An example of the structural description of a data record for creating an outpatient case is located under the identifier RNFAM in the tables TNT2 and TNT2S.

Here different data records are referred to, differentiated by the record type (FAM, LEI, VER, BHS, BM1-BM3). For every record of type FAM, there can be as many records of the other record types as is desired. The BM* records be used for creating unstructured information in the form of long text (in Sapscript format). Here a comments field in the corresponding screen is selected from the batch input report and filled in line by line from an internal table. Also, an undefined amount of records of the type "BHS" (treatment certificate), "VER" (insurance) and of the type "LEI" (service), can exist for a record "FAM" (this record type is coded internally in the report as a main record type). Should a dependent coverage exist in the insurance relationship, then at least the last name of the main isured person should be given.

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

Length: 4201 Date: 20240531 Time: 020025     sap01-206 ( 101 ms )