SAP REXA_CALLBACK_EVENT_0600_INV Function Module for

Search SAP Function Modules

REXA_CALLBACK_EVENT_0600_INV is a standard rexa callback event 0600 inv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for rexa callback event 0600 inv FM, simply by entering the name REXA_CALLBACK_EVENT_0600_INV into the relevant SAP transaction such as SE37 or SE38.

Function Group: REXA_CALLBACK_EVENTS
Program Name: SAPLREXA_CALLBACK_EVENTS
Main Program: SAPLREXA_CALLBACK_EVENTS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REXA_CALLBACK_EVENT_0600_INV pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'REXA_CALLBACK_EVENT_0600_INV'"
  EXPORTING
*  I_DPAYC =  "Administrative Data for Payment Run
*  I_PAYING_PARTNER =  "Business Partner Number
*  I_PAYING_ACCOUNT =  "Contract Account Number
*  I_PARA =  "Payment Program - Parameters
*  I_BASICS =  "Mass Activities: Global Values for All Mass Activities
*  I_XBLART = ' ' "

TABLES
   T_0600 =  "Items and Changable Fields (*_0600)
*  T_MESSA =  "Messages for the Job Log
*  T_MESSA_KK =  "FI-CA: Messages with Log Class from Application Log

.

IMPORTING Parameters details for REXA_CALLBACK_EVENT_0600_INV

I_DPAYC - Administrative Data for Payment Run

Data type: DPAYC
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PAYING_PARTNER - Business Partner Number

Data type: FKKOP-GPART
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PAYING_ACCOUNT - Contract Account Number

Data type: FKKOP-VKONT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARA - Payment Program - Parameters

Data type: FKKPY_PARA
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BASICS - Mass Activities: Global Values for All Mass Activities

Data type: FKK_MAD_BASICS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XBLART -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for REXA_CALLBACK_EVENT_0600_INV

T_0600 - Items and Changable Fields (*_0600)

Data type: FKKPY_0600
Optional: No
Call by Reference: No ( called with pass by value option)

T_MESSA - Messages for the Job Log

Data type: MESSA
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_MESSA_KK - FI-CA: Messages with Log Class from Application Log

Data type: MESSA_KK
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for REXA_CALLBACK_EVENT_0600_INV Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM REXA_CALLBACK_EVENT_0600_INV

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects