Ansicht
Dokumentation

MEASUREM_DOCUM_RFC_SINGLE_001 - RFC MeasDocument: Individual Processing, Create

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Functionality

This RFC makes possible the following remote calls for creating measurement documents:

(1) Remote dialog (WITH_DIALOG_SCREEN = 'X')

(2) API without dialog (WITH_DIALOG_SCREEN = ' ')

By using the parameter CREATE_NOTIFICATION, you can control whether another maintenance notification should be generated for the measurement document.

If a notification should be generated, a notification type can be assigned using the parameter NOTIFICATION_TYPE, which is set in Customizing of the target system. The standard notification type "M2" = "Malfunction report" is displayed as default.

A priority, which must likewise be set in Customizing of the target system, can also be assigned to the notification.

The following data is transferred to the notification from the measurement document or measuring point:

• Measuring point object of the measuring point (for example, functional location or equipment)

• "Assembly" field of the measuring point (should be included in the bill of material of the measuring point object)

• Measurement time in the field "Malfunction start" (date and time) for the notification

• Counter-reader in the field "Notifier" of the notification

• Short text. If the measurement document does not contain a short text, but an evaluation code (IMRG-VLCOD) was specified, the text belonging to it is copied into the short text of the notification.

• Evaluation code, as long as its catalog type is the same as the catalog type set for "Problems" (V_TQ80_C-FEKAT) for the respective notification type.

Example

Notes

(1)

If the field "Measurement position" for the measuring point is maintained with a unique value, the measuring point can also be identified using the measurement position. In this case, use the parameter SECONDARY_INDEX.

(2)

The following applies for the parameters RECORDED_VALUE und RECORDED_UNIT:

(2.1)

Both parameters are to be transferred in external format: RECORDED_VALUE is to be transferred in CHAR format. If the field contains decimal places, this must be separated with a comma or period according to the setting made in the user master.

RECORDED_UNIT is interpreted depending on the log-on language and is case sensitive.

(2.2)

If the parameter RECORDED_UNIT is transferred as a blank value, the system assumes that the measurement unit of the measuring point MEASUREMENT_POINT should be used.

(3)

If the measurement document table IMRG has been extended to include customer-defined fields by creating the customizing include CI_IMRG, these fields can be filled using the parameter USER_DATA.

(4)

If the parameter CHECK_CUSTOM_DUPREC is transferred with 'X', the system checks whether a non-canceled measurement document already exists for the measuring point and time stamp (READING_DATE + READING_TIME).

If this is the case, a new measurement document is not generated. Instead, the system returns the parameter CUSTOM_DUPREC_OCCURED with 'X'. The data of the existing measurement document is returned in the parameters MEASUREMENT_DOCUMENT, COMPLETE_DOCUMENT and NOTIFICATION. Therefore, the exception TIMESTAMP_DUPREC can not be set in this case, and not for counters either.

If you want to allow more than one measurement document per time stamp (seconds), you must create the Customizing include CI_IMRG with the field ZZ_CUST_ID. You can define the field ZZ_CUST_ID with any format. The field is then automatically available in the database table IMRG and the parameter USER_DATA is used during the above-mentioned DupRec-check as a refinement of the time stamp. This means that you can, for example, transfer to the field ZZ_CUST_ID an internal counter per measuring point and time stamp, or a renewal of the time stamp in micro/nano-seconds, or the number of the original document from the external system.

Further information

You can use the function module EXIT_SAPLIMR0_001 (SAP enhancement IMRC0001) for subsequent customer-specific processing.

Parameters

CHECK_CUSTOM_DUPREC
CODE_CATALOGUE
CODE_GROUP
CODE_VERSION
COMMIT_WORK
COMPLETE_DOCUMENT
CREATE_NOTIFICATION
CUSTOM_DUPREC_OCCURED
DIFFERENCE_READING
LINEAR_DATA
LINEAR_DATA_EXP
MEASUREMENT_DOCUMENT
MEASUREMENT_POINT
NOTIFICATION
NOTIFICATION_PRIO
NOTIFICATION_TYPE
ORIGIN_INDICATOR
PREPARE_UPDATE
PROCESSING_STATUS
QUALITY_CHAR_RESULTS
READER
READING_AFTER_ACTION
READING_DATE
READING_TIME
RECORDED_UNIT
RECORDED_VALUE
SECONDARY_INDEX
SHORT_TEXT
USER_DATA
VALUATION_CODE
WAIT_AFTER_COMMIT
WITH_DIALOG_SCREEN

Exceptions

CODE_NOT_FOUND
INDEX_NOT_UNIQUE
INVALID_DATE
INVALID_QUALITY_INFO
INVALID_TIME
NOTIF_GENER_PROBLEM
NOTIF_PRIO_NOT_FOUND
NOTIF_TYPE_NOT_FOUND
NO_AUTHORITY
POINT_INACTIVE
POINT_LOCKED
POINT_NOT_FOUND
PROCESSING_STATUS_INVALID
TIMESTAMP_DUPREC
TIMESTAMP_IN_FUTURE
TYPE_NOT_FOUND
UNIT_UNFIT
UPDATE_FAILED
VALUE_MISSING
VALUE_NOT_FLTP
VALUE_OVERFLOW
VALUE_UNFIT

Function Group

IMR0

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Length: 5884 Date: 20240523 Time: 041231     sap01-206 ( 136 ms )