SAP FC_SUBITEM_SENDFLDNAME_GET Function Module for









FC_SUBITEM_SENDFLDNAME_GET is a standard fc subitem sendfldname get 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 fc subitem sendfldname get FM, simply by entering the name FC_SUBITEM_SENDFLDNAME_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FC_SUBITEM_SENDFLDNAME_GET 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 'FC_SUBITEM_SENDFLDNAME_GET'"
  EXPORTING
   I_SSITEM_DOMVAL =  "
*  I_SENDTAB =  "Sender Table
*  I_SENDLEDGER =  "Source ledger

 IMPORTING
   E_SSITEM_FNAME =  "
   E_SSITEM_PRT_FNAME =  "

EXCEPTIONS
   VALUE_INITIAL = 1    VALUE_INVALID = 2    SENDTAB_INVALID = 3    NO_SENDER_FIELD = 4    NO_SENDER_INFO_SPECIFIED = 5    SENDLEDGER_INVALID = 6
.




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_SAPLFCIN_100 Integration: User Exit for Identifier and Texts from Cons Org Units
EXIT_SAPLFCIN_110 Integration: User Exit for 'Parents' of Cons Org Units
EXIT_SAPLFCIN_200 Integration: User Exit for Definition of the Data Stream on Rollup
EXIT_SAPLFCIN_210 Integration: Output Fields of Incorrect Data Records in Rollup
EXIT_SAPLFCIN_220 Integration: Sender Fields for Organizational Units on Rollup
EXIT_SAPLFCIN_230 Integration: Sender Fields for Subitems on Rollup
EXIT_SAPLFCIN_240 Integration: Edit from Value Fields before Update with Rollup
EXIT_SAPLFCIN_250 Integration: Get Custom Subassignments

IMPORTING Parameters details for FC_SUBITEM_SENDFLDNAME_GET

I_SSITEM_DOMVAL -

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

I_SENDTAB - Sender Table

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

I_SENDLEDGER - Source ledger

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

EXPORTING Parameters details for FC_SUBITEM_SENDFLDNAME_GET

E_SSITEM_FNAME -

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

E_SSITEM_PRT_FNAME -

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

EXCEPTIONS details

VALUE_INITIAL - Value is initial

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

VALUE_INVALID - Invalid Value

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

SENDTAB_INVALID -

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

NO_SENDER_FIELD -

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

NO_SENDER_INFO_SPECIFIED -

Data type:
Optional: No
Call by Reference: Yes

SENDLEDGER_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FC_SUBITEM_SENDFLDNAME_GET 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_value_initial  TYPE STRING, "   
lv_e_ssitem_fname  TYPE FC_FIELDNAME, "   
lv_i_ssitem_domval  TYPE FCIN_SITEMSEND, "   
lv_i_sendtab  TYPE FC_TABNAME, "   
lv_value_invalid  TYPE FC_TABNAME, "   
lv_e_ssitem_prt_fname  TYPE FC_FIELDNAME, "   
lv_i_sendledger  TYPE FC_RLDNR, "   
lv_sendtab_invalid  TYPE FC_RLDNR, "   
lv_no_sender_field  TYPE FC_RLDNR, "   
lv_no_sender_info_specified  TYPE FC_RLDNR, "   
lv_sendledger_invalid  TYPE FC_RLDNR. "   

  CALL FUNCTION 'FC_SUBITEM_SENDFLDNAME_GET'  "
    EXPORTING
         I_SSITEM_DOMVAL = lv_i_ssitem_domval
         I_SENDTAB = lv_i_sendtab
         I_SENDLEDGER = lv_i_sendledger
    IMPORTING
         E_SSITEM_FNAME = lv_e_ssitem_fname
         E_SSITEM_PRT_FNAME = lv_e_ssitem_prt_fname
    EXCEPTIONS
        VALUE_INITIAL = 1
        VALUE_INVALID = 2
        SENDTAB_INVALID = 3
        NO_SENDER_FIELD = 4
        NO_SENDER_INFO_SPECIFIED = 5
        SENDLEDGER_INVALID = 6
. " FC_SUBITEM_SENDFLDNAME_GET




ABAP code using 7.40 inline data declarations to call FM FC_SUBITEM_SENDFLDNAME_GET

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!