SAP EXTERNAL_TAX_DOC_USER_EXITS Function Module for Get customer data proposal through new User-Exit









EXTERNAL_TAX_DOC_USER_EXITS is a standard external tax doc user exits SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get customer data proposal through new User-Exit 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 external tax doc user exits FM, simply by entering the name EXTERNAL_TAX_DOC_USER_EXITS into the relevant SAP transaction such as SE37 or SE38.

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



Function EXTERNAL_TAX_DOC_USER_EXITS 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 'EXTERNAL_TAX_DOC_USER_EXITS'"Get customer data proposal through new User-Exit
EXPORTING
* I_INPUT_USER = "tax input user from pricing
I_T007A = "
I_TTXD = "External system information
I_HEADER_INFO = "
I_INPUT_DATA = "

IMPORTING
USER_PROPOSED_FIELDS = "
.



IMPORTING Parameters details for EXTERNAL_TAX_DOC_USER_EXITS

I_INPUT_USER - tax input user from pricing

Data type: TAX_USER_PRICING
Optional: Yes
Call by Reference: Yes

I_T007A -

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

I_TTXD - External system information

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

I_HEADER_INFO -

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

I_INPUT_DATA -

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

EXPORTING Parameters details for EXTERNAL_TAX_DOC_USER_EXITS

USER_PROPOSED_FIELDS -

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

Copy and paste ABAP code example for EXTERNAL_TAX_DOC_USER_EXITS 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_input_user  TYPE TAX_USER_PRICING, "   
lv_user_proposed_fields  TYPE TAX_ALLOWED_FIELDS, "   
lv_i_t007a  TYPE T007A, "   
lv_i_ttxd  TYPE TTXD, "   
lv_i_header_info  TYPE EXTAX_DOC, "   
lv_i_input_data  TYPE EXTAX_ITEM_IN. "   

  CALL FUNCTION 'EXTERNAL_TAX_DOC_USER_EXITS'  "Get customer data proposal through new User-Exit
    EXPORTING
         I_INPUT_USER = lv_i_input_user
         I_T007A = lv_i_t007a
         I_TTXD = lv_i_ttxd
         I_HEADER_INFO = lv_i_header_info
         I_INPUT_DATA = lv_i_input_data
    IMPORTING
         USER_PROPOSED_FIELDS = lv_user_proposed_fields
. " EXTERNAL_TAX_DOC_USER_EXITS




ABAP code using 7.40 inline data declarations to call FM EXTERNAL_TAX_DOC_USER_EXITS

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!