Kontakt

Ansicht
Dokumentation

N1_PERFORM_SRV_SAVE - BAdI: Service Performance/Release - Before Commit

N1_PERFORM_SRV_SAVE - BAdI: Service Performance/Release - Before Commit

RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

You can use this BADI to update your own data when performing or releasing services or creating services with the 'performed' or 'released' status. The BADI transfers the medical data for the service (i.e. the data records NLEI and NLEM), as well as the connection records between the services (table NLLZ).

You should note that the system will transfer performed, released and new services with this status to the BAdI. If. therefore, you only wish to create additional data (i.e. additional services for billing, etc.) for released services, then you must query the status of the services in the BAdI. You can find this status in the LSSTAE field of the NLEM table.

If you use this BAdI, you must adhere to the following rules:

Under NO circumstances should you perform a COMMIT WORK or a ROLLBACK WORK.

You can only execute an update task asynchronously (i.e. with the "IN UPDATE TASK" addition).

You cannot produce a dialog box (e.g. CALL SCREEN, etc.) in this BAdI.

This BAdI is NOT suitable for checks which should prevent the performance/release of services! You should use the BAdI N1_PERFORM_SRV_CHECK for this.

You cannot display your own messages in this BAdI. You should use the C_ERRORHANDLER parameter for this.

If you do not follow these rules you may cause serious data errors when performing/releasing!

The BAdI is not activfe as standard.

The BAdI cannot be used multiple times.

The BAdI is filter-dependent. The filter type is the data element ISH_COUNTRY (country version of IS-H).

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

To check the service status you should proceed as follows:

You will find the service status in the NLEM-LSSTAE field. However, this field contains the external, i.e. customer-specific status, which you cannot query. To determine the internal status, which you can query, you must read the table N1LSSTA with NLEM-LSSTAE.

Example:

SELECT SINGLE * FROM N1LSSTA

WHERE EINRI = NLEM-EINRI

AND LSSTAE = NLEM-LSSTAE.

In the N1LSSTA-LSSTA field you will then see the abbreviation of the internal service status. You can see the values possible in the field's domain (e.g. the abbreviation of the service status "Released" = QU).

Methods: EXIT_PERFORM_SAVE

________________________________________________________________________






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4853 Date: 20240606 Time: 214452     sap01-206 ( 72 ms )