Kontakt

Ansicht
Dokumentation

UTI_EVENT_2648 - FI-CA Event 2648: Utilities Actions

UTI_EVENT_2648 - FI-CA Event 2648: Utilities Actions

PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

Using the function modules called at event 2648, you can close additional actions that were initiated in event 2647. The fully created invoicing document and all posting documents to be created - including their document numbers - are available.

Add only the assigned document numbers to the internally recorded data that is to be updated to the database later.

Notes

The system processes the event during invoicing both in update mode and simulation mode. Keep this in mind if you update data that is processed in follow-on processes.

Programming Restrictions

To ensure the consistency of the system, note that you must not use the following language elements in events, unless they were explicitly declared to be allowed for the given event:

  • ,,COMMIT WORK
  • ,,ROLLBACK WORK
  • ,,CALL FUNCTION 'DEQUEUE ALL'
  • ,,Deletion of locks that you have not set yourself
  • ,,Implicit database commits triggered by RFC calls or by a WAIT statement

If you update additional data in an event and use the construction PERFORM commit routine ON COMMIT, note that:

  • ,,At the end of the commit routine, all internal tables from which data was updated must be initialized again to prevent a duplicate update in the next call.

  • ,,A PERFORM rollback routine ON ROLLBACK must also be called.
    In the rollback routine, initialize the same data that is initialized at the end of the commit routine.

If you want to carry out checks in an event, when you issue messages, note that warning messages cause background processing of the process to terminate. You should therefore avoid issuing warning messages if possible. At the most, issue warning messages if the value of SY-BATCH is initial.

Also avoid messages of type A (termination). In the course of background processing, such messages can be captured and processing can continue. However, at the same time the message triggers an implicit ROLLBACK WORK, which can cause data inconsistencies.

To ensure the consistency of your system, only use the information (such as variables and tables) in events that are made available on the interfaces of the events.

Changes that do not conform to these rules can lead to serious errors that violate the basic principles of accounting.

Parameters

  • I_INV_UNIT_PUBLIC
  • C_INVDOC

Function Group

  • FKKINV_EVENT




Parameters

C_INVDOC
I_INV_UNIT_PUBLIC

Exceptions

Function Group

UTI_INV

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3155 Date: 20240523 Time: 121739     sap01-206 ( 52 ms )