SAP IMA_PARTNER_BROKER_ONLY_VALIDS Function Module for IO: Extract all Valid Entries from the Broker History









IMA_PARTNER_BROKER_ONLY_VALIDS is a standard ima partner broker only valids SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IO: Extract all Valid Entries from the Broker History 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 ima partner broker only valids FM, simply by entering the name IMA_PARTNER_BROKER_ONLY_VALIDS into the relevant SAP transaction such as SE37 or SE38.

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



Function IMA_PARTNER_BROKER_ONLY_VALIDS 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 'IMA_PARTNER_BROKER_ONLY_VALIDS'"IO: Extract all Valid Entries from the Broker History
EXPORTING
* I_X_DATE = ' ' "
* I_X_DOC = ' ' "

TABLES
CT_DIMAPARBROK = "

EXCEPTIONS
NO_SORT_FLAG = 1
.



IMPORTING Parameters details for IMA_PARTNER_BROKER_ONLY_VALIDS

I_X_DATE -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_X_DOC -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for IMA_PARTNER_BROKER_ONLY_VALIDS

CT_DIMAPARBROK -

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

EXCEPTIONS details

NO_SORT_FLAG -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IMA_PARTNER_BROKER_ONLY_VALIDS 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_x_date  TYPE XFELD, "   SPACE
lv_no_sort_flag  TYPE XFELD, "   
lt_ct_dimaparbrok  TYPE STANDARD TABLE OF DIMAPARBROK, "   
lv_i_x_doc  TYPE XFELD. "   SPACE

  CALL FUNCTION 'IMA_PARTNER_BROKER_ONLY_VALIDS'  "IO: Extract all Valid Entries from the Broker History
    EXPORTING
         I_X_DATE = lv_i_x_date
         I_X_DOC = lv_i_x_doc
    TABLES
         CT_DIMAPARBROK = lt_ct_dimaparbrok
    EXCEPTIONS
        NO_SORT_FLAG = 1
. " IMA_PARTNER_BROKER_ONLY_VALIDS




ABAP code using 7.40 inline data declarations to call FM IMA_PARTNER_BROKER_ONLY_VALIDS

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.

DATA(ld_i_x_date) = ' '.
 
 
 
DATA(ld_i_x_doc) = ' '.
 


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!