SAP CO_DR_TABLE_ARGUMENT_BUILDT Function Module for NOTRANSL: Aufbauen eines Tabellenargumentes per Tabelle 496Z aus Druckprog









CO_DR_TABLE_ARGUMENT_BUILDT is a standard co dr table argument buildt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufbauen eines Tabellenargumentes per Tabelle 496Z aus Druckprog 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 co dr table argument buildt FM, simply by entering the name CO_DR_TABLE_ARGUMENT_BUILDT into the relevant SAP transaction such as SE37 or SE38.

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



Function CO_DR_TABLE_ARGUMENT_BUILDT 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 'CO_DR_TABLE_ARGUMENT_BUILDT'"NOTRANSL: Aufbauen eines Tabellenargumentes per Tabelle 496Z aus Druckprog
  EXPORTING
   TABLE_T496Z_ENTRY =  "CIM order: Table-controlled table access

 IMPORTING
   ARGUMENT1 =  "User field with 20 characters
   ARGUMENT2 =  "User field with 20 characters
   ARGUMENT3 =  "User field with 20 characters
   ARGUMENT4 =  "User field with 20 characters
   ARGUMENT5 =  "User field with 20 characters
   ARGUMENT6 =  "User field with 20 characters

EXCEPTIONS
   ARGUMENT_TABLE_NOT_DEFINED = 1
.



IMPORTING Parameters details for CO_DR_TABLE_ARGUMENT_BUILDT

TABLE_T496Z_ENTRY - CIM order: Table-controlled table access

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

EXPORTING Parameters details for CO_DR_TABLE_ARGUMENT_BUILDT

ARGUMENT1 - User field with 20 characters

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

ARGUMENT2 - User field with 20 characters

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

ARGUMENT3 - User field with 20 characters

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

ARGUMENT4 - User field with 20 characters

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

ARGUMENT5 - User field with 20 characters

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

ARGUMENT6 - User field with 20 characters

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

EXCEPTIONS details

ARGUMENT_TABLE_NOT_DEFINED -

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

Copy and paste ABAP code example for CO_DR_TABLE_ARGUMENT_BUILDT 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_argument1  TYPE PLPO-USR01, "   
lv_table_t496z_entry  TYPE T496Z, "   
lv_argument_table_not_defined  TYPE T496Z, "   
lv_argument2  TYPE PLPO-USR01, "   
lv_argument3  TYPE PLPO-USR01, "   
lv_argument4  TYPE PLPO-USR01, "   
lv_argument5  TYPE PLPO-USR01, "   
lv_argument6  TYPE PLPO-USR01. "   

  CALL FUNCTION 'CO_DR_TABLE_ARGUMENT_BUILDT'  "NOTRANSL: Aufbauen eines Tabellenargumentes per Tabelle 496Z aus Druckprog
    EXPORTING
         TABLE_T496Z_ENTRY = lv_table_t496z_entry
    IMPORTING
         ARGUMENT1 = lv_argument1
         ARGUMENT2 = lv_argument2
         ARGUMENT3 = lv_argument3
         ARGUMENT4 = lv_argument4
         ARGUMENT5 = lv_argument5
         ARGUMENT6 = lv_argument6
    EXCEPTIONS
        ARGUMENT_TABLE_NOT_DEFINED = 1
. " CO_DR_TABLE_ARGUMENT_BUILDT




ABAP code using 7.40 inline data declarations to call FM CO_DR_TABLE_ARGUMENT_BUILDT

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 USR01 FROM PLPO INTO @DATA(ld_argument1).
 
 
 
"SELECT single USR01 FROM PLPO INTO @DATA(ld_argument2).
 
"SELECT single USR01 FROM PLPO INTO @DATA(ld_argument3).
 
"SELECT single USR01 FROM PLPO INTO @DATA(ld_argument4).
 
"SELECT single USR01 FROM PLPO INTO @DATA(ld_argument5).
 
"SELECT single USR01 FROM PLPO INTO @DATA(ld_argument6).
 


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!