SAP P01T_GET_STEUERNUMMER Function Module for
P01T_GET_STEUERNUMMER is a standard p01t get steuernummer 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 p01t get steuernummer FM, simply by entering the name P01T_GET_STEUERNUMMER into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRST_ELSTER
Program Name: SAPLHRST_ELSTER
Main Program: SAPLHRST_ELSTER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function P01T_GET_STEUERNUMMER 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 'P01T_GET_STEUERNUMMER'".
EXPORTING
WERKS = "
BTRTL = "
* DATUM = "
IMPORTING
STNAG = "
BLAND = "
EXCEPTIONS
T5D0P_ENTRY_NOT_FOUND = 1 WRONG_CHAR_IN_TAXNUMBER = 2 MISSING_ENTRY_FOR_TAXNUMBER = 3 MISSING_ENTRY_FOR_TAXOFFICE = 4 MISSING_ENTRY_FOR_STATE = 5
IMPORTING Parameters details for P01T_GET_STEUERNUMMER
WERKS -
Data type: PERSAOptional: No
Call by Reference: No ( called with pass by value option)
BTRTL -
Data type: BTRTLOptional: No
Call by Reference: No ( called with pass by value option)
DATUM -
Data type: DOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for P01T_GET_STEUERNUMMER
STNAG -
Data type: P01T_AGSNROptional: No
Call by Reference: Yes
BLAND -
Data type: BULNDOptional: No
Call by Reference: Yes
EXCEPTIONS details
T5D0P_ENTRY_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_CHAR_IN_TAXNUMBER -
Data type:Optional: No
Call by Reference: Yes
MISSING_ENTRY_FOR_TAXNUMBER -
Data type:Optional: No
Call by Reference: Yes
MISSING_ENTRY_FOR_TAXOFFICE -
Data type:Optional: No
Call by Reference: Yes
MISSING_ENTRY_FOR_STATE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for P01T_GET_STEUERNUMMER 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_stnag | TYPE P01T_AGSNR, " | |||
lv_werks | TYPE PERSA, " | |||
lv_t5d0p_entry_not_found | TYPE PERSA, " | |||
lv_bland | TYPE BULND, " | |||
lv_btrtl | TYPE BTRTL, " | |||
lv_wrong_char_in_taxnumber | TYPE BTRTL, " | |||
lv_datum | TYPE D, " | |||
lv_missing_entry_for_taxnumber | TYPE D, " | |||
lv_missing_entry_for_taxoffice | TYPE D, " | |||
lv_missing_entry_for_state | TYPE D. " |
  CALL FUNCTION 'P01T_GET_STEUERNUMMER' " |
EXPORTING | ||
WERKS | = lv_werks | |
BTRTL | = lv_btrtl | |
DATUM | = lv_datum | |
IMPORTING | ||
STNAG | = lv_stnag | |
BLAND | = lv_bland | |
EXCEPTIONS | ||
T5D0P_ENTRY_NOT_FOUND = 1 | ||
WRONG_CHAR_IN_TAXNUMBER = 2 | ||
MISSING_ENTRY_FOR_TAXNUMBER = 3 | ||
MISSING_ENTRY_FOR_TAXOFFICE = 4 | ||
MISSING_ENTRY_FOR_STATE = 5 | ||
. " P01T_GET_STEUERNUMMER |
ABAP code using 7.40 inline data declarations to call FM P01T_GET_STEUERNUMMER
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