SAP PTRA_DB_ADDRESS_SAVE Function Module for









PTRA_DB_ADDRESS_SAVE is a standard ptra db address save 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 ptra db address save FM, simply by entering the name PTRA_DB_ADDRESS_SAVE into the relevant SAP transaction such as SE37 or SE38.

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



Function PTRA_DB_ADDRESS_SAVE 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 'PTRA_DB_ADDRESS_SAVE'"
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
I_TRIPNUMBER = "Trip Number
I_PERIODNUMBER = "Number of Trip Period
I_PERIODVERSION = "Sequential Number of Period
* I_LANGUAGE = SY-LANGU "Language Key
* I_TRIP_ACTION = 'MOD' "Function Code for Function Module HRTRV_IF_MODIFY_TRIP
I_HEAD = "General Information and Period Data of a Trip
* IT_ZIEL = "Table for DB Structure PTK05
* IT_KMVER = "Table for DB Structure PTK10

EXCEPTIONS
DATABASE_ERROR_TRIP_CHAIN = 1 ERROR_OCCURRED = 2
.



IMPORTING Parameters details for PTRA_DB_ADDRESS_SAVE

I_EMPLOYEENUMBER - Personnel Number

Data type: BAPIEMPL-PERNR
Optional: No
Call by Reference: Yes

I_TRIPNUMBER - Trip Number

Data type: BAPITRIP-TRIPNO
Optional: No
Call by Reference: Yes

I_PERIODNUMBER - Number of Trip Period

Data type: BAPITRVXXX-PERIOD
Optional: No
Call by Reference: Yes

I_PERIODVERSION - Sequential Number of Period

Data type: PTRV_PERIO-PDVRS
Optional: No
Call by Reference: Yes

I_LANGUAGE - Language Key

Data type: BAPITRVXXX-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

I_TRIP_ACTION - Function Code for Function Module HRTRV_IF_MODIFY_TRIP

Data type: PTRV_TRIP_ACTION
Default: 'MOD'
Optional: Yes
Call by Reference: Yes

I_HEAD - General Information and Period Data of a Trip

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

IT_ZIEL - Table for DB Structure PTK05

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

IT_KMVER - Table for DB Structure PTK10

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

EXCEPTIONS details

DATABASE_ERROR_TRIP_CHAIN -

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURRED - Errors have occurred

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PTRA_DB_ADDRESS_SAVE 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_employeenumber  TYPE BAPIEMPL-PERNR, "   
lv_database_error_trip_chain  TYPE BAPIEMPL, "   
lv_i_tripnumber  TYPE BAPITRIP-TRIPNO, "   
lv_error_occurred  TYPE BAPITRIP, "   
lv_i_periodnumber  TYPE BAPITRVXXX-PERIOD, "   
lv_i_periodversion  TYPE PTRV_PERIO-PDVRS, "   
lv_i_language  TYPE BAPITRVXXX-LANGU, "   SY-LANGU
lv_i_trip_action  TYPE PTRV_TRIP_ACTION, "   'MOD'
lv_i_head  TYPE HEAD_PERIO, "   
lv_it_ziel  TYPE PTRV_UTIL_ZIEL_T, "   
lv_it_kmver  TYPE PTRV_UTIL_KMVER_T. "   

  CALL FUNCTION 'PTRA_DB_ADDRESS_SAVE'  "
    EXPORTING
         I_EMPLOYEENUMBER = lv_i_employeenumber
         I_TRIPNUMBER = lv_i_tripnumber
         I_PERIODNUMBER = lv_i_periodnumber
         I_PERIODVERSION = lv_i_periodversion
         I_LANGUAGE = lv_i_language
         I_TRIP_ACTION = lv_i_trip_action
         I_HEAD = lv_i_head
         IT_ZIEL = lv_it_ziel
         IT_KMVER = lv_it_kmver
    EXCEPTIONS
        DATABASE_ERROR_TRIP_CHAIN = 1
        ERROR_OCCURRED = 2
. " PTRA_DB_ADDRESS_SAVE




ABAP code using 7.40 inline data declarations to call FM PTRA_DB_ADDRESS_SAVE

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 BAPIEMPL INTO @DATA(ld_i_employeenumber).
 
 
"SELECT single TRIPNO FROM BAPITRIP INTO @DATA(ld_i_tripnumber).
 
 
"SELECT single PERIOD FROM BAPITRVXXX INTO @DATA(ld_i_periodnumber).
 
"SELECT single PDVRS FROM PTRV_PERIO INTO @DATA(ld_i_periodversion).
 
"SELECT single LANGU FROM BAPITRVXXX INTO @DATA(ld_i_language).
DATA(ld_i_language) = SY-LANGU.
 
DATA(ld_i_trip_action) = 'MOD'.
 
 
 
 


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!