Ansicht
Dokumentation

BAPI_HCSRVCAT_ADDITEM - IS-H BAPI HCSrvCat.AddItem - Create Service Master Data

BAPI_HCSRVCAT_ADDITEM - IS-H BAPI HCSrvCat.AddItem - Create Service Master Data

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

It is used to create a new service.

You must specify the import parameters 'client', 'institution' and 'catalog' in which the service should be created.

The parameter TESTRUN is optional. If it is flagged ('X'), the module is executed in test mode. Test mode serves to check the data passed to the function module. Errors detected during the check are returned to the user in the table RETURN. Data is not written to the database in test mode.

The following tables can be passed to the function module:

SRVCAT_SRVDATA : Header data of the service
SRVCAT_COLDATA : Columns of the service
SRVCAT_TXTDATA : Description of the service (service text)
SRVCAT_PLNDATA : Planned values for the service
SRVCAT_ADDDATA : Additional data for special services
(e.g. FR, PS)
SRVCAT_ADDDATCH : Add. data service master Switzerland
SRVCAT_ADDDATCH_AG : Service master Switzerland => age asgmt
SRVCAT_ADDDATCH_KU : Service master Switzerland => excluding
service assignment
SRVCAT_ADDDATCH_QL : Service master Switzerland => qualitative
grade assignment
SRVCAT_ADDDATCH_QT : Service master Switzerland => quantitative
grade assignment
SRVCAT_ADDDATCH_SP : Service master Switzerland => division asgmt
SRVCAT_ADDDATCH_N1 : Service breakdown Switzerland
SRVCAT_ADDDATCH_N1T: Service breakdown - texts Switzerland
SRVCAT_ADDDATCH_W1 : Service master Switzerland => IV qualifier
assignment
SRVCAT_ADDDATFR : Additional data for service master France
SRVCAT_ADDDATFR_AK : Assignment service master France =>
activity + phase
SRVCAT_ADDDATFR_AS : Assignment service master France =>
associated service and code
SRVCAT_ADDDATFR_GH : Assignment service master France => GHS
SRVCAT_ADDDATFR_LA : Assignment service master France =>
service exclusion
SRVCAT_ADDDATFR_MC : Assignment service master France =>
modification codes
SRVCAT_ADDDAT_IT : Additional data for service master Italy

You must only fill the structure SRVCAT_SRVDATA to create a service. The specification of other structures is optional. If you also specify such structures can, all key fields must be filled. The specification of the key field "client" is optional.

When the method executes, all available tables are first checked for errors and consistency. If an error is detected in a record, it is logged internally and records related to this service are not written to the database.

Example:

An error is detected for a record of the service BASICNURSINGCHARGE in the structure SRVCAT_COLDATA. Consequently, none of the records for BASICNURSINGCHARGE are written to the database, even if there are no errors for this service in the structures SRVCAT_SRVDATA, SRVCAT_COLDATA, etc. For this reason, it is recommended to first execute the module in Test mode. To do this, set the parameter TESTRUN. In this mode, all test routines are run. Errors that occur are logged in the table RETURN, but are not written to the database.

In test mode, those records that would not be written to the database in a live run are logged as well.

The authorization check is performed using the authorization object N_EINR_TCO (NT01 is the transaction code for this object in SAP IS-H).

You can create as many (column) intervals as you like for a service. The specification of SRVCAT_COLDATA records for an SRVCAT_SRVDATA record is optional. If a column record is passed as well, all columns defined in Customizing for IS-H (IS-H table NTSI) must be specified for each time interval of the structure SRVCAT_COLDATA - regardless of whether they are filled with values. This specification should help prevent inconsistencies in the database caused by different time intervals for individual columns.

The system checks whether all columns were specified for an interval and whether the individual intervals overlap.
If the individual intervals do not overlap, there are no restrictions with respect to the intervals.
It is recommended that you do not leave gaps between the time intervals and to use the highdate (12/31/9999) for the upper limit (SRVCAT_COLDATA-ENDDATE) of the most recent interval.
It is recommended that you specify the highdate (12/31/9999) for the end date (ENDDATE) of the last interval in the table SRVCAT_COLDATA If you do not make this specification, slight problems with respect to delimitation can arise when services are created manually and problems can also arise when extended services are billed for. However, since you may well require in particular extended services to be discontinued at a given date, a highdate is not automatically written in the columns.
It is recommended that you also specify the start date for the records. If this date is not specified explicitly, the date from Customizing for IS-H is used for SRVCAT_SRVDATA and SRVCAT_COLDATA and 01/01/1990 is used for SRVCAT_ADDDATA and SRVCAT_PLNDATA. This may give rise to error messages of the type "end date before system date" that can initially appear incomprehensible.

Please note: The field COL_VALUE in the table SRVCAT_SRVDATA is a special type of field to which charge factor values or monetary amounts can be assigned. For this reason, the field must be filled completely. This means you also have to specify leading zeros. The system automatically sets the decimal point. For instance, the specification "000000010050" corresponds to 100.50 DEM or, depending on the catalog currency, 10050 Lira.

If a field of a structure is to be used, for which a field with the same name and the suffix "_ISO" exists, the user can decide which of the two fields is to be filled. The _ISO field is for values (e.g. measures) compliant with the ISO standard; the corresponding field without the suffix "_ISO" is intended for values compliant with the SAP standard. If the _ISO field is specified, this value is automatically converted into the SAP value. However, the ISO and SAP standards are identical in the vast majority of cases.

The fields CURRKEY and CURRKEY_ISO of the table SRVCAT_PLNDATA are exclusively export fields. They are filled by the system and user input is ignored (SRVCAT_PLNDATA always contains the local currency).

If you do not specify the fields pertaining to the person who made changes (DELETION_USER, DELETION_DATE, CREATION_USER, CREATION_DATE, UPDATE_USER, UPDATE_DATE in SRVCAT_SRVDATA, SRVCAT_COLDATA and SRVCAT_TXTDATA; UPDATE_USER, UPDATE_DATE in SRVCAT_ADDDATA; CREATION_DATE, CREATION_USER, CREATION_TIME, UPDATE_DATE, UPDATE_USER, UPDATE_TIME in SRVCAT_ADDDATCH, SRVCAT_ADDDATCH_AG, SRVCAT_ADDDATCH_KU, SRVCAT_ADDDATCH_QL, SRVCAT_ADDDATCH_QT, SRVCAT_ADDDATCH_SP, SRVCAT_ADDDATFR, SRVCAT_ADDDATFR_AK, SRVCAT_ADDDATFR_AS, SRVCAT_ADDDATFR_GH, SRVCAT_ADDDATFR_LA , SRVCAT_ADDDATFR_MC, and SRVCAT_ADDDAT_IT), they are automatically filled with system data (this only applies to DELETION_USER and DELETION_DATE if the deletion flag DELETION_IND is set).

SRVCAT_SRVDATA-SERVICEID and -EXTID (if it exists) are converted to upper-case. No other fields are converted to upper-case, SRVCAT_TXTDATA-SERVICEID or SRVCAT_SRVDATA-UPDATE_USER!

SAPscript Long Text Connection

You could use the table parameters DOCINFO and DOCCONTENT to transfer SAPscript long texts when creating service master data. Table DOCINFO contains the meta data and DOCCONTENT contains all the text lines. The meta data references the text lines by means of line areas and the first (DOCFIRSTLINE) and last (DOCLASTLINE) line numbers must be specified.

  • DOCID
    Unique key for the text. Comprises: institution (4 characters), catalog (2 characters), service (10 characters), and the text type (2 characters). It is important that you adhere to these character lengths and fill in any blanks.
    Example: 000203000000000401 ,,(In this case: institution "2“, catalog "3“, service "4“, and text type "1“.
  • Text type for a SAPscript long text for the service long text:
    01 for long text
    02 comment long text:
    (See also: data element ISH_LONGTXTYPE)

  • LANGUAGE
    SAP language key
  • LANGU_ISO
    System ignores this.
  • DOCFIRSTLINE
    Line number of first line in table DOCCONTENT for this key.
  • DOCLASTLINE
    Line number of last line in table DOCCONTENT for this key.
  • DOCFORMAT
    ASC for ASCII or SCR for SAPscript format

All the parameters are mandatory, apart from LANGU_ISO and errors will occur if they do not contain values.

The system overwrites the corresponding fields in table SRVCAT_TXTDATA if a long text is specified for them. The system automatically selects the long text indicator.





Parameters

CLIENT
DOCCONTENT
DOCINFO
INSTITUTION
RETURN
SRVCATID
SRVCAT_ADDDATA
SRVCAT_ADDDATAT
SRVCAT_ADDDATCH
SRVCAT_ADDDATCH_AG
SRVCAT_ADDDATCH_KO
SRVCAT_ADDDATCH_KU
SRVCAT_ADDDATCH_MX
SRVCAT_ADDDATCH_N1
SRVCAT_ADDDATCH_N1T
SRVCAT_ADDDATCH_QL
SRVCAT_ADDDATCH_QT
SRVCAT_ADDDATCH_SP
SRVCAT_ADDDATCH_W1
SRVCAT_ADDDATCN
SRVCAT_ADDDATFR
SRVCAT_ADDDATFR_AK
SRVCAT_ADDDATFR_AS
SRVCAT_ADDDATFR_GH
SRVCAT_ADDDATFR_LA
SRVCAT_ADDDATFR_MC
SRVCAT_ADDDAT_IT
SRVCAT_ADDPEPP
SRVCAT_ADDPEPPA
SRVCAT_COLDATA
SRVCAT_PLNDATA
SRVCAT_SRVDATA
SRVCAT_TXTDATA
TESTRUN
WORST_RETURNED_MSGTY
WRITE_CHANGEDOC

Exceptions

Function Group

1300

PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 14808 Date: 20240523 Time: 112134     sap01-206 ( 211 ms )