SAP ISU_SAMPLE_R214 Function Module for Aggr. Posting: Extend FI-AP Line Items









ISU_SAMPLE_R214 is a standard isu sample r214 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Aggr. Posting: Extend FI-AP Line Items 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 isu sample r214 FM, simply by entering the name ISU_SAMPLE_R214 into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_SAMPLE_R214 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 'ISU_SAMPLE_R214'"Aggr. Posting: Extend FI-AP Line Items
EXPORTING
IS_GROUPING = "Characteristics for Aggregation of Outgoing Payments
IS_POSTPARA = "Parameters for Outgoing Payment Account Data
IV_BUDAT = "Posting Date in Document
IV_BLART = "Document Type

CHANGING
CS_HEADER = "Header

EXCEPTIONS
VENDOR_MISSING = 1
.



IMPORTING Parameters details for ISU_SAMPLE_R214

IS_GROUPING - Characteristics for Aggregation of Outgoing Payments

Data type: INV_DFKKTHP_AGG
Optional: No
Call by Reference: Yes

IS_POSTPARA - Parameters for Outgoing Payment Account Data

Data type: INV_PARAM_REM_OUTBOUND_ACC
Optional: No
Call by Reference: Yes

IV_BUDAT - Posting Date in Document

Data type: BUDAT
Optional: No
Call by Reference: Yes

IV_BLART - Document Type

Data type: BLART
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ISU_SAMPLE_R214

CS_HEADER - Header

Data type: BAPIACHE09
Optional: No
Call by Reference: Yes

EXCEPTIONS details

VENDOR_MISSING - Vendor does not exist

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

Copy and paste ABAP code example for ISU_SAMPLE_R214 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_cs_header  TYPE BAPIACHE09, "   
lv_is_grouping  TYPE INV_DFKKTHP_AGG, "   
lv_vendor_missing  TYPE INV_DFKKTHP_AGG, "   
lv_is_postpara  TYPE INV_PARAM_REM_OUTBOUND_ACC, "   
lv_iv_budat  TYPE BUDAT, "   
lv_iv_blart  TYPE BLART. "   

  CALL FUNCTION 'ISU_SAMPLE_R214'  "Aggr. Posting: Extend FI-AP Line Items
    EXPORTING
         IS_GROUPING = lv_is_grouping
         IS_POSTPARA = lv_is_postpara
         IV_BUDAT = lv_iv_budat
         IV_BLART = lv_iv_blart
    CHANGING
         CS_HEADER = lv_cs_header
    EXCEPTIONS
        VENDOR_MISSING = 1
. " ISU_SAMPLE_R214




ABAP code using 7.40 inline data declarations to call FM ISU_SAMPLE_R214

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!