SAP FI_EDI_PAYEXT_SCB_DE Function Module for









FI_EDI_PAYEXT_SCB_DE is a standard fi edi payext scb de 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 fi edi payext scb de FM, simply by entering the name FI_EDI_PAYEXT_SCB_DE into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_EDI_PAYEXT_SCB_DE 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 'FI_EDI_PAYEXT_SCB_DE'"
  EXPORTING
   IM_EVENT =  "Time of Call
   IM_REGUH =  "Payment Data
   IM_REGUD =  "Form print transfer data
   IM_EDIDC =  "Control Record (IDoc)
   IM_FLAG_NO_REPLACE =  "

TABLES
   TAB_SCB_DATA =  "Central Bank Report: Report Segments in Payment IDoc
   TAB_REGUP =  "Processed items from payment program

EXCEPTIONS
   DONT_CREATE_IDOC = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLIEDP_001 FI-EDI: Outgoing Pmnt Advice - Save PEXR Segments
EXIT_SAPLIEDP_002 FI-EDI Outgoing Payments: Save PEXR Segments PAYEXT
EXIT_SAPLIEDP_003 FI-EDI Outgoing Payments: Save PEXR Segments DIRDEB
EXIT_SAPLIEDP_101 FI-EDI: Incoming Pmnt Advice - Extended Assgmt of IDOC -> Applicatn Data
EXIT_SAPLIEDP_102 FI-EDI: Incoming Pmnt Adivce - Closing Assgmt of IDOC -> Applicatn Data
EXIT_SAPLIEDP_201 FI-EDI: Inbound - Account Statement/Lockbox - Settlement Handling
EXIT_SAPLIEDP_202 FI-EDI: Inbound Account Statement/Lockbox, Segment Processing
EXIT_SAPLIEDP_203 FI-EDI: Inbound Account Statement/Lockbox, Changes to Payment Advice
EXIT_SAPLIEDP_301 FI-EDI Outbound Reference IDoc: Save IDCR Segments
EXIT_SAPLIEDP_401 FI-EDI: Deactivate Automatic Special Character
EXIT_SAPLIEDP_901 FI-EDI Outgoing Payment: New Partner House Bank
EXIT_SAPLIEDP_902 FI-EDI Outgoing Payment: End of Interim Payment Document (VBLNR)
EXIT_SAPLIEDP_903 FI-EDI Outgoing Payment: End Partner House Bank

IMPORTING Parameters details for FI_EDI_PAYEXT_SCB_DE

IM_EVENT - Time of Call

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

IM_REGUH - Payment Data

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

IM_REGUD - Form print transfer data

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

IM_EDIDC - Control Record (IDoc)

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

IM_FLAG_NO_REPLACE -

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

TABLES Parameters details for FI_EDI_PAYEXT_SCB_DE

TAB_SCB_DATA - Central Bank Report: Report Segments in Payment IDoc

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

TAB_REGUP - Processed items from payment program

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

EXCEPTIONS details

DONT_CREATE_IDOC -

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

Copy and paste ABAP code example for FI_EDI_PAYEXT_SCB_DE 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_im_event  TYPE CHAR3, "   
lt_tab_scb_data  TYPE STANDARD TABLE OF PAYEXT_SCB_EDIDD, "   
lv_dont_create_idoc  TYPE PAYEXT_SCB_EDIDD, "   
lv_im_reguh  TYPE REGUH, "   
lt_tab_regup  TYPE STANDARD TABLE OF REGUP, "   
lv_im_regud  TYPE REGUD, "   
lv_im_edidc  TYPE EDIDC, "   
lv_im_flag_no_replace  TYPE C. "   

  CALL FUNCTION 'FI_EDI_PAYEXT_SCB_DE'  "
    EXPORTING
         IM_EVENT = lv_im_event
         IM_REGUH = lv_im_reguh
         IM_REGUD = lv_im_regud
         IM_EDIDC = lv_im_edidc
         IM_FLAG_NO_REPLACE = lv_im_flag_no_replace
    TABLES
         TAB_SCB_DATA = lt_tab_scb_data
         TAB_REGUP = lt_tab_regup
    EXCEPTIONS
        DONT_CREATE_IDOC = 1
. " FI_EDI_PAYEXT_SCB_DE




ABAP code using 7.40 inline data declarations to call FM FI_EDI_PAYEXT_SCB_DE

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!