SERV_DATA SAP (IS-H: Internal Structure for Transferring Services (NP37)) Structure details
Description: IS-H: Internal Structure for Transferring Services (NP37)
Structure field list including key, data, relationships and ABAP select examples
SERV_DATA is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "IS-H: Internal Structure for Transferring Services (NP37)" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_SERV_DATA TYPE SERV_DATA.
The SERV_DATA table consists of various fields, each holding specific information or linking keys about IS-H: Internal Structure for Transferring Services (NP37) data available in SAP. These include FALNR (IS-H: Case Number), REFOPDATA (IS-H: Sequence Number of Movement), REFPRDATA (IS-H: Sequence Number of Surgical Procedure Code), LEIST (Service in Service Catalog).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP SERV_DATA structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
| REFOPDATA | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
| REFPRDATA | IS-H: Sequence Number of Surgical Procedure Code | ISH_LNRIC | CHAR | 10 | ALPHA | ISH_LNRIC | |||
| LEIST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
| ABTYP | IS-H: Billing Category for Individual Billing Control | LEI_ABTYP | CHAR | 4 | Assigned to domain | ISH_ABTYP | |||
| LEVON | Date when Service Performance Starts | BEGDTLEI | DATS | 8 | RI_DATUM | ||||
| BEGZT | IS-H: Time when Service Performance Starts | BEGZT_LS | TIMS | 6 | UHRZT | ||||
| GPAR1 | IS-H: Business Partner | GPARTNER | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
| ROLT1 | IS-H: Function of Business Partner in Rel. to Service | ISH_ROLTPE | CHAR | 2 | Assigned to domain | ALPHA | ISH_ROLTPE | ||
| GPAR2 | IS-H: Business Partner | GPARTNER | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
| ROLT2 | IS-H: Function of Business Partner in Rel. to Service | ISH_ROLTPE | CHAR | 2 | Assigned to domain | ALPHA | ISH_ROLTPE | ||
| MENGE | Service Quantity | I_MENG_LS | NUMC | 4 | LEISMENGE | ||||
| STALS | IS-H: Service Status (Planned/Performed) | STATUS_LS | CHAR | 1 | STATUS_LS | ||||
| ABRKZ | Service Can Be Billed For | ABRKZ | CHAR | 1 | ABRKZ_LS | ||||
| HCOKZ | IS-H: Service Relevant for CO | ISH_HCOKZ | CHAR | 1 | XFELD | ||||
| ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ERBOE | IS-H: Organizational Unit that Performs the Service | ERBOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ENTKY | Charge Key for Paragraph 301/DALE-UV | ENTKEY | CHAR | 2 | ENTKEY | ||||
| ENZKY | IS-H: Add. Key for Charge Type for FR/Case, Proc.Surcharges | NZUSKEY | CHAR | 1 | NZUSKEY | ||||
| ENTG2 | IS-H: Charge Type According to ยง301 | ENTGART2 | CHAR | 5 | ENTGART2 | ||||
| REFKY | Reference Code for Service from External System | REFKY | CHAR | 20 | ALPHA | ISH_REFKY | |||
| TARAS | IS-H: Multiplication Factor as CHAR Field | NC_TARAS | CHAR | 8 | CHAR8 | ||||
| TARIF | IS-H: Identification of Alternative Service Catalog | ABW_TARIF | CHAR | 2 | Assigned to domain | ALPHA | TARID | TAK | |
| TARLS | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
| TARSP | IS-H: Column in Service Catalog | TARSP | CHAR | 2 | Assigned to domain | ALPHA | TARSP | ||
| TBTRAG | IS-H: Price (per quantity unit) as CHAR field | NC_TBTRAG | CHAR | 14 | CHAR14 | ||||
| ANART | IS-H: Analysis Type for Service (DKG-NT Germany) | ANALYSEART | CHAR | 1 | ANALYSEART | ||||
| ERBTY | Type of Service Performance | TYP_ERBR | CHAR | 1 | TYP_ERBR | ||||
| KTRKZ | IS-H: Service is Cost Object | ISH_KTRKZ | CHAR | 1 | XFELD | ||||
| LEITX | IS-H: Service Short Text (May Differ from Service Master) | TEXT_LEI | CHAR | 40 | LEIKTXT | ||||
| REMRK | IS-H: User's Comment on Service | ISH_REMRK | CHAR | 40 | ISH_REMRK | ||||
| PZAHL | IS-H: Charge Factor as CHAR Field for Data Transfer | NC_PZAHL | CHAR | 10 | CHAR10 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SERV_DATA using ABAP code?
As SERV_DATA is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on SERV_DATA as there is no data to select.How to access SAP table SERV_DATA
Within an ECC or HANA version of SAP you can also view further information about SERV_DATA and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects