SAP ADFSH_REVISION_CREATE Function Module for test module for creating revision
ADFSH_REVISION_CREATE is a standard adfsh revision create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for test module for creating revision 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 adfsh revision create FM, simply by entering the name ADFSH_REVISION_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADFSH_OTHER
Program Name: SAPLADFSH_OTHER
Main Program: SAPLADFSH_OTHER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ADFSH_REVISION_CREATE 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 'ADFSH_REVISION_CREATE'"test module for creating revision.
EXPORTING
I_FLOC = "Flight Scheduling: Actual Aircraft Registration
I_FRDATE = "Date and time, current (application server) date
I_TODATE = "Date and time, current (application server) date
I_FRTIME = "Dat and time, current application server time
I_TOTIME = "Dat and time, current application server time
I_FLTNR = "Flight Scheduling: Flight Number
I_AIRLN = "Flight Scheduling: Airline Code
I_SECNR = "Flight Scheduling: Sector Number
I_ACDATE = "Flight Scheduling: Actual Date of Flight
IMPORTING
E_REVNR = "Revision for Plant Maintenance and Customer Service
EXCEPTIONS
INVALID_PLANT = 1 ERROR = 2
IMPORTING Parameters details for ADFSH_REVISION_CREATE
I_FLOC - Flight Scheduling: Actual Aircraft Registration
Data type: ADFSH_ACTPLNROptional: No
Call by Reference: Yes
I_FRDATE - Date and time, current (application server) date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_TODATE - Date and time, current (application server) date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_FRTIME - Dat and time, current application server time
Data type: SY-UZEITOptional: No
Call by Reference: Yes
I_TOTIME - Dat and time, current application server time
Data type: SY-UZEITOptional: No
Call by Reference: Yes
I_FLTNR - Flight Scheduling: Flight Number
Data type: ADFSH_FLTNUMOptional: No
Call by Reference: Yes
I_AIRLN - Flight Scheduling: Airline Code
Data type: ADFSH_AIRCODEOptional: No
Call by Reference: Yes
I_SECNR - Flight Scheduling: Sector Number
Data type: ADFSH_SECNROptional: No
Call by Reference: Yes
I_ACDATE - Flight Scheduling: Actual Date of Flight
Data type: ADFSH_ACDATEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ADFSH_REVISION_CREATE
E_REVNR - Revision for Plant Maintenance and Customer Service
Data type: REVNIOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_PLANT - Invalid Plant
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR - Program Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADFSH_REVISION_CREATE 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_floc | TYPE ADFSH_ACTPLNR, " | |||
lv_e_revnr | TYPE REVNI, " | |||
lv_invalid_plant | TYPE REVNI, " | |||
lv_error | TYPE REVNI, " | |||
lv_i_frdate | TYPE SY-DATUM, " | |||
lv_i_todate | TYPE SY-DATUM, " | |||
lv_i_frtime | TYPE SY-UZEIT, " | |||
lv_i_totime | TYPE SY-UZEIT, " | |||
lv_i_fltnr | TYPE ADFSH_FLTNUM, " | |||
lv_i_airln | TYPE ADFSH_AIRCODE, " | |||
lv_i_secnr | TYPE ADFSH_SECNR, " | |||
lv_i_acdate | TYPE ADFSH_ACDATE. " |
  CALL FUNCTION 'ADFSH_REVISION_CREATE' "test module for creating revision |
EXPORTING | ||
I_FLOC | = lv_i_floc | |
I_FRDATE | = lv_i_frdate | |
I_TODATE | = lv_i_todate | |
I_FRTIME | = lv_i_frtime | |
I_TOTIME | = lv_i_totime | |
I_FLTNR | = lv_i_fltnr | |
I_AIRLN | = lv_i_airln | |
I_SECNR | = lv_i_secnr | |
I_ACDATE | = lv_i_acdate | |
IMPORTING | ||
E_REVNR | = lv_e_revnr | |
EXCEPTIONS | ||
INVALID_PLANT = 1 | ||
ERROR = 2 | ||
. " ADFSH_REVISION_CREATE |
ABAP code using 7.40 inline data declarations to call FM ADFSH_REVISION_CREATE
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 DATUM FROM SY INTO @DATA(ld_i_frdate). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_i_todate). | ||||
"SELECT single UZEIT FROM SY INTO @DATA(ld_i_frtime). | ||||
"SELECT single UZEIT FROM SY INTO @DATA(ld_i_totime). | ||||
Search for further information about these or an SAP related objects