SAP POSTING_INTERFACE_START Function Module for Initial information for internal accounting interface
POSTING_INTERFACE_START is a standard posting interface start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initial information for internal accounting interface processing and below is the pattern details for this FM, 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 posting interface start FM, simply by entering the name POSTING_INTERFACE_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: FIPI
Program Name: SAPLFIPI
Main Program: SAPLFIPI
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function POSTING_INTERFACE_START 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 'POSTING_INTERFACE_START'"Initial information for internal accounting interface.
EXPORTING
* I_CLIENT = SY-MANDT "Client
I_FUNCTION = "Function: BDC, Call Trans. Using, internal interface
* I_GROUP = ' ' "
* I_HOLDDATE = ' ' "only BDC: locking the session until the specified date
* I_KEEP = ' ' "
* I_MODE = 'N' "
* I_UPDATE = 'S' "Update mode (synchronous / asynchronous) (Call Trans.)
* I_USER = ' ' "
* I_XBDCC = ' ' "X-batch input if error in call transaction
EXCEPTIONS
CLIENT_INCORRECT = 1 FUNCTION_INVALID = 2 GROUP_NAME_MISSING = 3 MODE_INVALID = 4 UPDATE_INVALID = 5
IMPORTING Parameters details for POSTING_INTERFACE_START
I_CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FUNCTION - Function: BDC, Call Trans. Using, internal interface
Data type: RFIPI-FUNCTOptional: No
Call by Reference: No ( called with pass by value option)
I_GROUP -
Data type: APQI-GROUPIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_HOLDDATE - only BDC: locking the session until the specified date
Data type: APQI-STARTDATEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KEEP -
Data type: APQI-QERASEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE -
Data type: RFPDO-ALLGAZMDDefault: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDATE - Update mode (synchronous / asynchronous) (Call Trans.)
Data type: RFPDO-ALLGVBMDDefault: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_USER -
Data type: APQI-USERIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XBDCC - X-batch input if error in call transaction
Data type: RFIPI-XBDCCDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CLIENT_INCORRECT - Transferred client differs from the system client
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FUNCTION_INVALID - Transferred function is not supported
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GROUP_NAME_MISSING - Session name is missing (for batch input)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MODE_INVALID - Display mode not supported (for Call Trans.)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_INVALID - Update mode not supported (for Call Tr)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for POSTING_INTERFACE_START 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.| DATA: | ||||
| lv_i_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_client_incorrect | TYPE SY, " | |||
| lv_i_function | TYPE RFIPI-FUNCT, " | |||
| lv_function_invalid | TYPE RFIPI, " | |||
| lv_i_group | TYPE APQI-GROUPID, " SPACE | |||
| lv_group_name_missing | TYPE APQI, " | |||
| lv_i_holddate | TYPE APQI-STARTDATE, " SPACE | |||
| lv_mode_invalid | TYPE APQI, " | |||
| lv_i_keep | TYPE APQI-QERASE, " SPACE | |||
| lv_update_invalid | TYPE APQI, " | |||
| lv_i_mode | TYPE RFPDO-ALLGAZMD, " 'N' | |||
| lv_i_update | TYPE RFPDO-ALLGVBMD, " 'S' | |||
| lv_i_user | TYPE APQI-USERID, " SPACE | |||
| lv_i_xbdcc | TYPE RFIPI-XBDCC. " SPACE |
| CALL FUNCTION 'POSTING_INTERFACE_START' "Initial information for internal accounting interface |
| EXPORTING | ||
| I_CLIENT | = lv_i_client | |
| I_FUNCTION | = lv_i_function | |
| I_GROUP | = lv_i_group | |
| I_HOLDDATE | = lv_i_holddate | |
| I_KEEP | = lv_i_keep | |
| I_MODE | = lv_i_mode | |
| I_UPDATE | = lv_i_update | |
| I_USER | = lv_i_user | |
| I_XBDCC | = lv_i_xbdcc | |
| EXCEPTIONS | ||
| CLIENT_INCORRECT = 1 | ||
| FUNCTION_INVALID = 2 | ||
| GROUP_NAME_MISSING = 3 | ||
| MODE_INVALID = 4 | ||
| UPDATE_INVALID = 5 | ||
| . " POSTING_INTERFACE_START | ||
ABAP code using 7.40 inline data declarations to call FM POSTING_INTERFACE_START
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.| "SELECT single MANDT FROM SY INTO @DATA(ld_i_client). | ||||
| DATA(ld_i_client) | = SY-MANDT. | |||
| "SELECT single FUNCT FROM RFIPI INTO @DATA(ld_i_function). | ||||
| "SELECT single GROUPID FROM APQI INTO @DATA(ld_i_group). | ||||
| DATA(ld_i_group) | = ' '. | |||
| "SELECT single STARTDATE FROM APQI INTO @DATA(ld_i_holddate). | ||||
| DATA(ld_i_holddate) | = ' '. | |||
| "SELECT single QERASE FROM APQI INTO @DATA(ld_i_keep). | ||||
| DATA(ld_i_keep) | = ' '. | |||
| "SELECT single ALLGAZMD FROM RFPDO INTO @DATA(ld_i_mode). | ||||
| DATA(ld_i_mode) | = 'N'. | |||
| "SELECT single ALLGVBMD FROM RFPDO INTO @DATA(ld_i_update). | ||||
| DATA(ld_i_update) | = 'S'. | |||
| "SELECT single USERID FROM APQI INTO @DATA(ld_i_user). | ||||
| DATA(ld_i_user) | = ' '. | |||
| "SELECT single XBDCC FROM RFIPI INTO @DATA(ld_i_xbdcc). | ||||
| DATA(ld_i_xbdcc) | = ' '. | |||
Search for further information about these or an SAP related objects