SAP ABAP Data Element TARLS (IS-H: Service in Service Catalog)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       NPVS (Package) Application development patient management system
Basic Data
Data Element TARLS
Short Description IS-H: Service in Service Catalog  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type TARLS    
Data Type CHAR   Character String 
Length 10    
Decimal Places 0    
Output Length 10    
Value Table NTPK    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID TAL  
Default Component name SERVICEID   
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Service 
Medium 14 Service 
Long 20 Service 
Heading 10 Service 
Documentation

Definition

Code that uniquely identifies a service within a service catalog and an institution.

Supplementary Documentation - TARLS 0001

Use

Service that is to be used as a reference to copy when creating a new service.

Procedure

When creating a service, you can use a service which already exists as a reference. A number of pieces of master record information of this service are then transferred to the service master to be created.

Examples

Dependencies

Supplementary Documentation - TARLS 0002

Use

Please enter which service group you want to edit here. You can then assign other services to this service group (and also subordinate service groups).

Procedure

With the possible entries pushbutton function (F4), you can search for services using specific criteria. Leave the field empty and press "ENTER" if you want to receive a list of all service groups of the service catalog entered above.

Examples

Dependencies

Supplementary Documentation - TARLS 0003

Use

You can assign one or more services to the higher-level service group here. The services that were assigned as a result of this may also be service groups, so that a multi-level grouping can be defined.

Procedure

Examples

Dependencies

A service must be defined for the entire duration in which it is assigned to another service, that is, the master record of the service must exist continuously.

A service must be assigned uniquely within a grouping (more precisely: within a complete tree of an assignment type). Example: If you assign the services A and B to the service group C, you can, for example, assign neither the service C nor the service B to the service A.

Please also note the condition that there may be no overlapping with regard to the validity period of the assignment. Example: If you assign the service A to the service group B for the period 01/01/1990 - 31/12/1995, an assignment of the service A to the service group B for the period 07/01/1995 - 09/30/1997 would not be valid.

Supplementary Documentation - TARLS 0004

Use

Conversion: If an assignment to a service of a certain target charge is not to be carried out, a '&' can be entered here. Further processing (for example, statistics) ignores this service in the target charge and does not output a (terminating) error message. This way, you can distinguish between services for which a conversion is not intended to take place and services for which a conversion was unintentionally not carried out.

Procedure

Examples

Dependencies

Supplementary Documentation - TARLS 0005

Use

Service catalog determination can be carried out in relation to the service.

Procedure

Enter a valid service in the field or mask the field by entering an asterisk ('*') in the 1st position.

Dependencies

  • If you enter a different value to an asterisk, the entry is checked against the service master data table.
  • Service groups are not supported in service catalog determination.
  • Please note that no service-related rules are provided as a default. However, if you specify such rules, please check whether the parameter TF_LEIST (table TN00S) was activated in Customizing, since otherwise all service-related rules are ignored.

Please also refer to the access steps to the service catalog determination rules.

Supplementary Documentation - TARLS 0006

Use

Departmental per diem:
To determine the valid service catalog, proceed as follows:

  • If the current date is within the validity of the organizational unit, the current date is used for the determination.
  • If the current date is after the "valid to" date of the organizational unit, the "valid to" date of the organizational unit is used for the determination.
  • If the current date is before the "valid from" date of the organizational unit, the "valid from" date of the organizational unit is used for the determination.

Services are generated in admission/discharge as follows:

  • If the departmental OU is used for admission, then the departmental per diem assigned to it is automatically generated.
    This departmental per diem can then be seen in the service maintenance screen.
  • If the departmental OU is used for discharge, then all nursing charges with the charge types:
    • Nursing charge
    • Departmental per diem and
    • Intensive care per diem
      are delimited when the discharge is saved, and generated from the discharge date.
      No new insurance verification requests are generated. If the newly generated nursing charge can be assigned to an existing insurance verification request, then it is.
  • If the treatment catagory and departmental per diem are entered together, the system checks that they do not overlap. However, you should avoid entering treatment catagory and departmental per diem with the same services.
  • Departmental per diem charges in the case of interim and final billed cases are not generated if generating is within the billing period.

Procedure

Examples

Dependencies

Supplementary Documentation - TARLS 0007

Use

Here you can specify the service code of an individual service or of a service group from the in-house service catalog.

Procedure

If you do not know the service code, you can determine it by choosing Possible Entries for this field. The system sends a dialog box for you to specify criteria to search for specific services or service groups. The system outputs the services which match your criteria in a list. You can then select one or more services and transfer them into the case-related service entry transaction.

Examples

Dependencies

Supplementary Documentation - TARLS 0008

Use

The service you enter here refers to the alternative service catalog you define as the billing catalog. It corresponds to the service entered from the in-house service catalog and is used in further processing (e.g. invoicing).

By making an entry here, you deactivate the rules for billing catalog determination and service conversion with regard to this service.

Procedure

Only specify a service here if you do not want to use billing catalog determination and service conversion for this service.

Examples

Dependencies

If you make an entry here, you must also specify an alternative service catalog to which the service refers.

Supplementary Documentation - TARLS 0010

Use

You can restrict the transfer to particular services here.

Procedure

Check if you need this selection criterion.

Examples

If you want to carry out the transfer in several program runs, you can use this selection criterion.

Dependencies

Supplementary Documentation - TARLS 0020

Use

The IS-H service entered here is assigned to the activity type in CO in accordance with the account assignment rule.

Procedure

Enter a service from the in-house service catalog of your institution to which you want to assign one or more activity types in CO.

Examples

You want to assign the X-ray service 5000 from your in-house service catalog to the activity type XRAY in CO. To do this, you maintain the following entry:

Institution | Service catalog | Service | ... | Activity type | ...
---------------------------------------------------------------------
0001 | 01 | 5000 | | RAY |

If you want to assign several CO activity types to one IS-H service (e.g. patient day), you need to make one entry for each CO activity type:

Institution | Service catalog | Service | ... | Activity type| ..
---------------------------------------------------------------------
0001 | 01 | PFL | | PYSMIN |
0001 | 01 | PFL | | NRSDAY |
0001 | 01 | PFL | | MATCOST |

In the above exampel, a patient day in IS-H is mapped to the activity types physician minutes, patient day and material costs in CO.

Dependencies

You can only assign individual services to activity types in CO. You cannot specify service groups here.

Supplementary Documentation - TARLS 0030

Use

Specify a service code for the reason here.

(ADT field code 5036).

When you confirm your input by pressing enter, the system automatically transfers the field content along with the code #5021:# into the "Reason Text" field.

Alternatively, you can explicitly specify the field content in the "Reason Text" by using the code #5021:#.

Dependencies

The field is used in PPA billing (country version DE) only.

Example

Supplementary Documentation - TARLS 0040

Use

The service you enter here is simply used as a dummy service to determine the baserate during revenue accrual.

It is only recorded in the baserate determination table TNWCH83 and is not entered as a service for the case.

Dependencies

If you make an entry in this field, you must also specify a service catalog to which the service relates.

Example

Supplementary Documentation - TARLS 0099

Note

  • As a rule you can use specify an individual service here. Alternatively you can also use a service group in certain functions.
  • The service is coded on 10-characters maximum.
History
Last changed by/on SAP  20050224 
SAP Release Created in