Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
Basic Data
Data Element | ABR_REL |
Short Description | IS-H:Head Office for HC Smart Card, not Relevant for Billing |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | HO_NOT_RELEVANT | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Assignment |
Medium | 14 | Import HC Card |
Long | 20 | Not Relevant f.Bill. |
Heading | 3 | HSC |
Documentation
Definition
If this indicator is set, invoices are not addressed to the head office specified in the Head Office field, but to the branch currently operating as the insurance provider.
The system only requires the head office to find the subordinate branch offices (insurance providers) in the hierarchy when determining the insurance provider during healthcare smart card import.
The field can only be selected if there is a valid entry in the Head Office field.
Example
The health insurer number of the head office features on the insured's healthcare smart card.
When the healthcare smart card in imported, the head office is determined, but the responsible branch office should be entered for the patient.
For the system to be able to determine the related branch offices, you need to have made an entry in the Head Office field for the respective insurance providers (branch offices).
If invoices should only be sent to the branch offices, you have to set the above indicator, otherwise they will be sent to the head office.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |