SAP TRG_EXPORT_DATA_EIGENANTEIL Function Module for









TRG_EXPORT_DATA_EIGENANTEIL is a standard trg export data eigenanteil 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 trg export data eigenanteil FM, simply by entering the name TRG_EXPORT_DATA_EIGENANTEIL into the relevant SAP transaction such as SE37 or SE38.

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



Function TRG_EXPORT_DATA_EIGENANTEIL 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 'TRG_EXPORT_DATA_EIGENANTEIL'"
EXPORTING
RECEIPT_CREATED = "
DEFAULT_KM_SATZ = "
VU_EA_DOPP_ANZ = "Own Contribution: No. of Days with Outb./Return Trip b. Move
VU_EA_EINF_ANZ = "Own Contribution: No. of Days wth Outb./Return Trip b. Move
VU_EA_ENTFERN = "Own Contribution: Distance to Place of Work before Move
VU_EA_KM_SATZ = "Own Contribution: KM Rate to Place of Work Before Move
NU_EA_DOPP_ANZ = "Own Contrib.: No. of Days wth Outb. and Ret. Trip after Move
NU_EA_EINF_ANZ = "Own Contrib.: No. of Days with Outb. or Ret. Trip after Move
NU_EA_ENTFERN = "Own Contribution: Distance to Place of Work after Move
NU_EA_KM_SATZ = "Own Contribution: KM Rate to Place of Work after Move
.



IMPORTING Parameters details for TRG_EXPORT_DATA_EIGENANTEIL

RECEIPT_CREATED -

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

DEFAULT_KM_SATZ -

Data type: PTPPD_APPEND-VU_EA_KM_SATZ
Optional: No
Call by Reference: Yes

VU_EA_DOPP_ANZ - Own Contribution: No. of Days with Outb./Return Trip b. Move

Data type: PTP42-VU_EA_DOPP_ANZ
Optional: No
Call by Reference: Yes

VU_EA_EINF_ANZ - Own Contribution: No. of Days wth Outb./Return Trip b. Move

Data type: PTP42-VU_EA_EINF_ANZ
Optional: No
Call by Reference: Yes

VU_EA_ENTFERN - Own Contribution: Distance to Place of Work before Move

Data type: PTP42-VU_EA_ENTFERN
Optional: No
Call by Reference: Yes

VU_EA_KM_SATZ - Own Contribution: KM Rate to Place of Work Before Move

Data type: PTP42-VU_EA_KM_SATZ
Optional: No
Call by Reference: Yes

NU_EA_DOPP_ANZ - Own Contrib.: No. of Days wth Outb. and Ret. Trip after Move

Data type: PTP42-NU_EA_DOPP_ANZ
Optional: No
Call by Reference: Yes

NU_EA_EINF_ANZ - Own Contrib.: No. of Days with Outb. or Ret. Trip after Move

Data type: PTP42-NU_EA_EINF_ANZ
Optional: No
Call by Reference: Yes

NU_EA_ENTFERN - Own Contribution: Distance to Place of Work after Move

Data type: PTP42-NU_EA_ENTFERN
Optional: No
Call by Reference: Yes

NU_EA_KM_SATZ - Own Contribution: KM Rate to Place of Work after Move

Data type: PTP42-NU_EA_KM_SATZ
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRG_EXPORT_DATA_EIGENANTEIL 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_receipt_created  TYPE C, "   
lv_default_km_satz  TYPE PTPPD_APPEND-VU_EA_KM_SATZ, "   
lv_vu_ea_dopp_anz  TYPE PTP42-VU_EA_DOPP_ANZ, "   
lv_vu_ea_einf_anz  TYPE PTP42-VU_EA_EINF_ANZ, "   
lv_vu_ea_entfern  TYPE PTP42-VU_EA_ENTFERN, "   
lv_vu_ea_km_satz  TYPE PTP42-VU_EA_KM_SATZ, "   
lv_nu_ea_dopp_anz  TYPE PTP42-NU_EA_DOPP_ANZ, "   
lv_nu_ea_einf_anz  TYPE PTP42-NU_EA_EINF_ANZ, "   
lv_nu_ea_entfern  TYPE PTP42-NU_EA_ENTFERN, "   
lv_nu_ea_km_satz  TYPE PTP42-NU_EA_KM_SATZ. "   

  CALL FUNCTION 'TRG_EXPORT_DATA_EIGENANTEIL'  "
    EXPORTING
         RECEIPT_CREATED = lv_receipt_created
         DEFAULT_KM_SATZ = lv_default_km_satz
         VU_EA_DOPP_ANZ = lv_vu_ea_dopp_anz
         VU_EA_EINF_ANZ = lv_vu_ea_einf_anz
         VU_EA_ENTFERN = lv_vu_ea_entfern
         VU_EA_KM_SATZ = lv_vu_ea_km_satz
         NU_EA_DOPP_ANZ = lv_nu_ea_dopp_anz
         NU_EA_EINF_ANZ = lv_nu_ea_einf_anz
         NU_EA_ENTFERN = lv_nu_ea_entfern
         NU_EA_KM_SATZ = lv_nu_ea_km_satz
. " TRG_EXPORT_DATA_EIGENANTEIL




ABAP code using 7.40 inline data declarations to call FM TRG_EXPORT_DATA_EIGENANTEIL

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 VU_EA_KM_SATZ FROM PTPPD_APPEND INTO @DATA(ld_default_km_satz).
 
"SELECT single VU_EA_DOPP_ANZ FROM PTP42 INTO @DATA(ld_vu_ea_dopp_anz).
 
"SELECT single VU_EA_EINF_ANZ FROM PTP42 INTO @DATA(ld_vu_ea_einf_anz).
 
"SELECT single VU_EA_ENTFERN FROM PTP42 INTO @DATA(ld_vu_ea_entfern).
 
"SELECT single VU_EA_KM_SATZ FROM PTP42 INTO @DATA(ld_vu_ea_km_satz).
 
"SELECT single NU_EA_DOPP_ANZ FROM PTP42 INTO @DATA(ld_nu_ea_dopp_anz).
 
"SELECT single NU_EA_EINF_ANZ FROM PTP42 INTO @DATA(ld_nu_ea_einf_anz).
 
"SELECT single NU_EA_ENTFERN FROM PTP42 INTO @DATA(ld_nu_ea_entfern).
 
"SELECT single NU_EA_KM_SATZ FROM PTP42 INTO @DATA(ld_nu_ea_km_satz).
 


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!