SAP HR_ERC_CREATE_APPLICATION Function Module for
HR_ERC_CREATE_APPLICATION is a standard hr erc create application 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 hr erc create application FM, simply by entering the name HR_ERC_CREATE_APPLICATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: HR_ERC_APPL_BAPI
Program Name: SAPLHR_ERC_APPL_BAPI
Main Program: SAPLHR_ERC_APPL_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_ERC_CREATE_APPLICATION 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 'HR_ERC_CREATE_APPLICATION'".
EXPORTING
CANDIDATE = "
* TECH_APPL_SOURCE = 'M' "Technical Application Source
APPLICATIONDATE = "Application Date
POST_INST_GUID = "Global Key for Posting Instances
* APPL_STATUS = '1' "Application Status
* REASON_CODE = "Status reason
* SCLAS = "
* SOBID = "ID of Related Object
* APPL_SOURCE = "Source of Candidate's Application
* APPL_SOURCE_INFO = "Freeform Text for Application Source
IMPORTING
APPLICATION = "Application Object
TABLES
RETURN = "Return Parameter(s)
IMPORTING Parameters details for HR_ERC_CREATE_APPLICATION
CANDIDATE -
Data type: HROBJECTOptional: No
Call by Reference: Yes
TECH_APPL_SOURCE - Technical Application Source
Data type: RCF_TECH_APPL_SOURCEDefault: 'M'
Optional: Yes
Call by Reference: Yes
APPLICATIONDATE - Application Date
Data type: RCF_APPLICATION_DATEOptional: No
Call by Reference: Yes
POST_INST_GUID - Global Key for Posting Instances
Data type: RCF_PINST_GUIDOptional: No
Call by Reference: Yes
APPL_STATUS - Application Status
Data type: RCF_APPLICATION_STATUSDefault: '1'
Optional: Yes
Call by Reference: Yes
REASON_CODE - Status reason
Data type: RCF_REASON_CODEOptional: Yes
Call by Reference: Yes
SCLAS -
Data type: SCLASOptional: Yes
Call by Reference: Yes
SOBID - ID of Related Object
Data type: SOBIDOptional: Yes
Call by Reference: Yes
APPL_SOURCE - Source of Candidate's Application
Data type: RCF_APPL_SOURCEOptional: Yes
Call by Reference: Yes
APPL_SOURCE_INFO - Freeform Text for Application Source
Data type: RCF_APPL_SOURCE_INFOOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HR_ERC_CREATE_APPLICATION
APPLICATION - Application Object
Data type: HROBJECTOptional: No
Call by Reference: Yes
TABLES Parameters details for HR_ERC_CREATE_APPLICATION
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_ERC_CREATE_APPLICATION 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: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_candidate | TYPE HROBJECT, " | |||
| lv_application | TYPE HROBJECT, " | |||
| lv_tech_appl_source | TYPE RCF_TECH_APPL_SOURCE, " 'M' | |||
| lv_applicationdate | TYPE RCF_APPLICATION_DATE, " | |||
| lv_post_inst_guid | TYPE RCF_PINST_GUID, " | |||
| lv_appl_status | TYPE RCF_APPLICATION_STATUS, " '1' | |||
| lv_reason_code | TYPE RCF_REASON_CODE, " | |||
| lv_sclas | TYPE SCLAS, " | |||
| lv_sobid | TYPE SOBID, " | |||
| lv_appl_source | TYPE RCF_APPL_SOURCE, " | |||
| lv_appl_source_info | TYPE RCF_APPL_SOURCE_INFO. " |
|   CALL FUNCTION 'HR_ERC_CREATE_APPLICATION' " |
| EXPORTING | ||
| CANDIDATE | = lv_candidate | |
| TECH_APPL_SOURCE | = lv_tech_appl_source | |
| APPLICATIONDATE | = lv_applicationdate | |
| POST_INST_GUID | = lv_post_inst_guid | |
| APPL_STATUS | = lv_appl_status | |
| REASON_CODE | = lv_reason_code | |
| SCLAS | = lv_sclas | |
| SOBID | = lv_sobid | |
| APPL_SOURCE | = lv_appl_source | |
| APPL_SOURCE_INFO | = lv_appl_source_info | |
| IMPORTING | ||
| APPLICATION | = lv_application | |
| TABLES | ||
| RETURN | = lt_return | |
| . " HR_ERC_CREATE_APPLICATION | ||
ABAP code using 7.40 inline data declarations to call FM HR_ERC_CREATE_APPLICATION
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.| DATA(ld_tech_appl_source) | = 'M'. | |||
| DATA(ld_appl_status) | = '1'. | |||
Search for further information about these or an SAP related objects