SAP EXIT_SAPL3IDC_001 Function Module for Customer Exit for HIDCTAX1 to read the Employee's Position









EXIT_SAPL3IDC_001 is a standard exit sapl3idc 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer Exit for HIDCTAX1 to read the Employee's Position 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 exit sapl3idc 001 FM, simply by entering the name EXIT_SAPL3IDC_001 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPL3IDC_001 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 'EXIT_SAPL3IDC_001'"Customer Exit for HIDCTAX1 to read the Employee's Position
  EXPORTING
   _PERNR =  "Personnel number
   _START_DATE =  "Start Date
   _END_DATE =  "End Date
   _PLANS =  "Position Key
   _STELL =  "Job Key
   _ORGEH =  "Organizational Unit
   _VDSK1 =  "Organizational Key
   _OTYPE =  "Object Type

CHANGING
   _POSITION =  "Char 80

EXCEPTIONS
   STANDARD_ERROR = 1    CUSTOMER_ERROR = 2
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
HR_ID_BRACKETS Calculate tax
HR_ID_CALC_TAX Tax Calculation routine for Indonesia
HR_ID_POSITION Function module to call user-exit for Employee Position (INDONESIA)
HR_ID_RATE Rate calculation for simple grossup
HR_ID_TAX_YEAR Determine begin/end date of tax year

IMPORTING Parameters details for EXIT_SAPL3IDC_001

_PERNR - Personnel number

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

_START_DATE - Start Date

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

_END_DATE - End Date

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

_PLANS - Position Key

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

_STELL - Job Key

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

_ORGEH - Organizational Unit

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

_VDSK1 - Organizational Key

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

_OTYPE - Object Type

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

CHANGING Parameters details for EXIT_SAPL3IDC_001

_POSITION - Char 80

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

EXCEPTIONS details

STANDARD_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CUSTOMER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPL3IDC_001 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__pernr  TYPE PA0001-PERNR, "   
lv__position  TYPE CHAR80, "   
lv_standard_error  TYPE CHAR80, "   
lv__start_date  TYPE PA0001-BEGDA, "   
lv_customer_error  TYPE PA0001, "   
lv__end_date  TYPE PA0001-ENDDA, "   
lv__plans  TYPE PS0001-PLANS, "   
lv__stell  TYPE PS0001-STELL, "   
lv__orgeh  TYPE PS0001-ORGEH, "   
lv__vdsk1  TYPE PS0001-VDSK1, "   
lv__otype  TYPE PS0001-OTYPE. "   

  CALL FUNCTION 'EXIT_SAPL3IDC_001'  "Customer Exit for HIDCTAX1 to read the Employee's Position
    EXPORTING
         _PERNR = lv__pernr
         _START_DATE = lv__start_date
         _END_DATE = lv__end_date
         _PLANS = lv__plans
         _STELL = lv__stell
         _ORGEH = lv__orgeh
         _VDSK1 = lv__vdsk1
         _OTYPE = lv__otype
    CHANGING
         _POSITION = lv__position
    EXCEPTIONS
        STANDARD_ERROR = 1
        CUSTOMER_ERROR = 2
. " EXIT_SAPL3IDC_001




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPL3IDC_001

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 PERNR FROM PA0001 INTO @DATA(ld__pernr).
 
 
 
"SELECT single BEGDA FROM PA0001 INTO @DATA(ld__start_date).
 
 
"SELECT single ENDDA FROM PA0001 INTO @DATA(ld__end_date).
 
"SELECT single PLANS FROM PS0001 INTO @DATA(ld__plans).
 
"SELECT single STELL FROM PS0001 INTO @DATA(ld__stell).
 
"SELECT single ORGEH FROM PS0001 INTO @DATA(ld__orgeh).
 
"SELECT single VDSK1 FROM PS0001 INTO @DATA(ld__vdsk1).
 
"SELECT single OTYPE FROM PS0001 INTO @DATA(ld__otype).
 


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!