Ansicht
Dokumentation

RNILST00 - Transfer Data to Create Services

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Description

You can use this program to create services. On the basis of the Customizing settings made in Data Transfer - Define Structures and Data Transfer - Define Record Types the program reads and processes a sequential dataset.

If you initially only wish to test the importing of the sequential dataset, you can run the program in test mode. This does not create a batch input session, but fields and their contents are displayed on the respective screens. The test mode is particularly suitable for checking the structure definition of the sequential dataset.

Note

Tab pages were fully implemented for the service master in IS-H Release 4.03. You cannot, however, create a batch input session for the new tab pages Extras and Planning values. You use the service master BAPIs to import these (and all other) values. For further information about BAPIs, refer to the Release Note IS-H-BAPIs for IS-H Release 4.03.

Note that the service master BAPIs available to you since IS-H Release 4.03 greatly increase the possibilities for processing service master data.

The Create session flag determines whether a batch input session is created, or if data is updated directly (technical info: "Call transaction using..."). If data is to be updated directly, and an error occurs, a batch input session is also created. However, data that is correct is updated. You can then process the session (to add data that is missing, for example, or to determine the cause of the error).

Requirements

If the length of a record of the sequential dataset exceeds 1024 bytes, then the length of the buffer variable REC must be correspondingly changed in INCLUDE program RNILSI10.

A structure definition must exist for the sequential dataset (see IMG activity above). In addition, you must enter the service catalog ID in IS-H and the complete name of the sequential dataset when starting the program. If the sequential dataset contains different record types, you have to flag the relevant option on the selection screen, and specify the offset and the length of the record type ID.

Using different record types, you control the transfer of any long text for a service. The long text can be stored eithir in the Long text field or the Note field of the first entry screen. To transfer long text to the system, you must make a corresponding entry in the structure definition. That is, all fields must have record type 'TAR', with the exception of the long text fields. You must use the record type LTX for the long text field (NTPT-LTEXT) and the type BT for the comments field (NTPT-KTEXT). Seventy characters can be transferred for each BTX or LTX line (of the sequential dataset). If you want to transfer more than 70 characters, you can simply append further records of the corresponding record type. The names of the record types are predefined; here, the program interprets TAR as the main record type (that is, this record type initiates a block which only ends when TAR is read again) and LTX and BTX as assigned record types. The procedure is much simpler there is no long text transfer. In such cases, you do not have to specify the record types.

Example Data Record for Transfer of Three Lines of Long Text for Service Code 204:

TAR 204,circular bandage,95,12.60,5.70,18.30,29.80

LTX compression bandage head/shoulder/hip/trunk

LTX also first emergency bandage for fractures

LTX also with plaster/starch fixation

The Valuation formula option lets you specify the formula to be used for pricing services in the same way as in the maintenance transaction.

You can set the corresponding indicators of the transaction using the options Extended service and Billable for all of the services imported.

If the service record does not contain a valid start date, or if you want a different date, you can enter a value in the Valid from field. The same applies to the valid-to date.

If you do not enter a date on the selection screen of the program, and do not transfer the date from the sequential dataset, the system uses the default date for services as specified in Customizing (institution-specific, time independent control parameters: Default start date when creating service master and Default end date when creating service master). In this case, the structure definition must not contain an entry for the corresponding date field.

Any conversions of the field formats that are necessary can be carried out as follows:
Define a corresponding form routine. You make all changes to the format with the first parameter. The second parameter contains the record currently being imported from the sequential dataset. The conversion is to be structured so that a valid input format is achieved for the respective entry field. You enter the name of the form routine in the Form routine field, and the program name in the Program field when maintaining the structure definition.

Output

If you select Test mode, data is not updated. If you select Error log, any screen fields with their respective field contents are displayed if errors occur.

If errors occurred and caused a batch input session to be generated, you can edit this session using transaction SM35 (or by choosing System -> Services -> Batch input -> Edit), that is analyze and process, it if necessary.

Example

Examples of form routines can be found in program RNILSI20.

An example of a structure definition is stored in tables TNT2 and TNT2S under the identifier RNLST. This can be used to copy from.

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 6783 Date: 20240531 Time: 062322     sap01-206 ( 116 ms )