SAP USS_FILL_TABLE_VALUES Function Module for









USS_FILL_TABLE_VALUES is a standard uss fill table values 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 uss fill table values FM, simply by entering the name USS_FILL_TABLE_VALUES into the relevant SAP transaction such as SE37 or SE38.

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



Function USS_FILL_TABLE_VALUES 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 'USS_FILL_TABLE_VALUES'"
EXPORTING
TABLE_NAME = "
* I_PARTNER_TYPE = "Business Partner Category

IMPORTING
TABLE_VALUES = "
.



IMPORTING Parameters details for USS_FILL_TABLE_VALUES

TABLE_NAME -

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

I_PARTNER_TYPE - Business Partner Category

Data type: BUS_PARTNER-TYPE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for USS_FILL_TABLE_VALUES

TABLE_VALUES -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for USS_FILL_TABLE_VALUES 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_table_name  TYPE STRING, "   
lv_table_values  TYPE STRING, "   
lv_i_partner_type  TYPE BUS_PARTNER-TYPE. "   

  CALL FUNCTION 'USS_FILL_TABLE_VALUES'  "
    EXPORTING
         TABLE_NAME = lv_table_name
         I_PARTNER_TYPE = lv_i_partner_type
    IMPORTING
         TABLE_VALUES = lv_table_values
. " USS_FILL_TABLE_VALUES




ABAP code using 7.40 inline data declarations to call FM USS_FILL_TABLE_VALUES

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 TYPE FROM BUS_PARTNER INTO @DATA(ld_i_partner_type).
 


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!