SAP ABAP Data Element KEYARG (IS-HCM: Key Value for Data Retrieval for Dispatch Order)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ 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	KEYARG
Short Description	IS-HCM: Key Value for Data Retrieval for Dispatch Order

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	TEXT20
Data Type	CHAR	Character String
Length	20
Decimal Places	0
Output Length	20
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Key Value
Medium	14	Key Value
Long	20	Key Value
Heading	20	Key Value

Documentation

Definition

NC301S Key1 - Key6 Description of Use

With §301:

1. When the patient master is modified, the case number (field FALNR) can be empty. If, however, an insurance provider (field KOSTR) could be determined, NC301S entries are created in which the message type AUFN with the patient number (PATNR) is located in Key1.
2. If there is a change of insurance provider, the start date of the new insurance provider assignment is entered in Key5 of ENTL of the old insurance provider. This date is also entered in Key5 of the new insurance provider in AUFN in internal format (yyyymmdd). For both messages, Key4 contains the sequence number of the relevant case-related insurance relationship and Key6 contains the sequence number of each other case-related insurance relationship.
3. With invoices (type RECH, type AMBO)
1. Key1 contains the document number of the invoice (SD) or, in the case of cancellation events, the document number of the cancellation document (SD).
   However with zero invoices or when the final billed indicator is reset it contains NUL<casenumber>.
2. Key2 contains the document number of the canceled invoice (SD) in the case of cancellation events.
3. Key3 contains the dunning level.
   In the special case of zero-value invoices (RECH with document number prefix "NUL") for presenting action messages, the document number of the last invoice transmitted up to the key date of message creation is stored here.
4. Key4 contains the respective standard code for the billing type (procedure-specific code) and not the billing indicator (field ABRKZ); the billing type of the canceled invoice in the case of cancellation events (may also correspond to a credit memos defined by §301).
5. With AMBO, the internal billing type for outpatient surgeries ("15") is also entered in Key5.
4. With IV extension notifications (type VERL)
1. Key1 may contain the constant GC_EXCEEDS_DURATION, indicating that the new end date of a generated IV request exceeds the length of stay and, consequently, the length of stay has to be modified in the application.
2. Key2 contains the (estimated) discharge date in the internal format (yyyymmdd).
5. With medical grounds (type MBEG)
1. Key1 contains the sequence number of the medical grounds (MBEG), if entered
2. Key2 contains the sequence number of the associated request
6. With copayment credit memos (type ZGUT(80) for copayments that are transferred after final billing during the collection procedure)
1. Key1 contains the company code.
2. Key2 contains the document number of the transfer posting document.
3. Key3 contains the fiscal year.
7. With copayment credit memos for collection (type ZGUT(90), when a copayment transfer posting received after final billing for the case is cancelled)
1. Key1 contains the company code.
2. Key2 contains the cancellation document number for the transfer posting document.
3. Key3 contains the fiscal year of the cancellation document.
4. Key4 contains the document number of the cancelled transfer posting document.
5. Key5 contains the fiscal year of the cancelled transfer posting document.
8. With copayment postings back for receivables (type ZGUT(90) when a dunned unpaid copayment receivable is posted back)
1. Key1 contains the company code.
2. Key2 contains the document number of the back posting document.
3. Key3 contains the fiscal year from the back posting document.
4. Key4 contains the document number of the copayment receivable.
5. Key5 contains the fiscal year of the copayment receivable.
6. Key6 contains the SD invoice number from which the copayment receivable was deducted.
9. The following applies for errored inbound messages (always event N301E1) and should also be adhered to for other SAP-external EDI procedures):
1. Key1: Indicator file error (2) or message error (3/4) (see mnc301d1, gravity constants)
2. Key2: Dependent on Key1 either the file number or the message number (lf301d(!) or lf301)
3. Key3: with FEHL message types: Contains the FEHL message receiver ID.
   

With §302:

1. For single invoices (type SLGA, SLLA)
1. Key1 contains the document number of the invoice (SD) or, in the case of cancellation events, the document number of the cancellation document (SD).
2. Key2 contains, in the case of cancellation events, the document number of the canceled invoice (SD).
3. Key4 contains the EDI-procedure specific processing indicator for invoice (01) or cancellation document (04).
   

With NPMI:

1. Submitted requests
1. Key1: External patient ID (UIN/FIN)
2. Risk factor message
1. Key1: External patient ID (UIN/FIN)
2. Key2: Patient number (NPAT-PATNR)
3. Key3: Request(1), Addition/Update(A) or Deletion(D) (dispatch)
   

With MRUC: L4/L5 Statistics

1. Key1: The first two positions: specialty type, remaining positions: specialty
2. Key2: (only relevant for message structure) the current diagnosis key for each QTY segment etc.
3. Key3: (only relevant for message structure) the index of the present diagnosis or surgery to be processed with reference to the transfer table.
   

With DRG for SG:

1. Key1: contains the start date (month+year) for message type aggregate
2. Key2: contains the end date (month+year) for message type aggregate
   

General:

1. Key6: Contains the name of the person to have last modified the message in the NC301M table (using the RNC301UE program)
   

History

Last changed by/on	SAP	20050224
SAP Release Created in