SAP HR_IE_XML_SCHEMA Function Module for HR-GB: Output customized XML Schema
HR_IE_XML_SCHEMA is a standard hr ie xml schema SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HR-GB: Output customized XML Schema 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 hr ie xml schema FM, simply by entering the name HR_IE_XML_SCHEMA into the relevant SAP transaction such as SE37 or SE38.
Function Group: HR_IE_XML
Program Name: SAPLHR_IE_XML
Main Program: SAPLHR_IE_XML
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_IE_XML_SCHEMA 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_IE_XML_SCHEMA'"HR-GB: Output customized XML Schema.
EXPORTING
* MOLGA = '08' "Country Grouping
SAGRP = "Code Group - Coding
DOCTY = "Application
DSTYP = "Document Subtype
* DATE = '18000101' "Start Date
* CHECK_ONLY = ' ' "Output XML schema on screen
* BROWSER = 'X' "Output XML schema on screen
CHANGING
* FULLPATH = "Local file for upload/download
EXCEPTIONS
RUNTIME_ERROR = 1 SCHEMA_NOT_FOUND = 2 SUBSCHEMA_NOT_FOUND = 3
IMPORTING Parameters details for HR_IE_XML_SCHEMA
MOLGA - Country Grouping
Data type: MOLGADefault: '08'
Optional: No
Call by Reference: No ( called with pass by value option)
SAGRP - Code Group - Coding
Data type: PCAL_SAGRPOptional: No
Call by Reference: No ( called with pass by value option)
DOCTY - Application
Data type: T50V_XML-DOCTYOptional: No
Call by Reference: No ( called with pass by value option)
DSTYP - Document Subtype
Data type: P_DTYPEOptional: No
Call by Reference: No ( called with pass by value option)
DATE - Start Date
Data type: BEGDADefault: '18000101'
Optional: No
Call by Reference: No ( called with pass by value option)
CHECK_ONLY - Output XML schema on screen
Data type: XFELDDefault: ' '
Optional: No
Call by Reference: No ( called with pass by value option)
BROWSER - Output XML schema on screen
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for HR_IE_XML_SCHEMA
FULLPATH - Local file for upload/download
Data type: RLGRAP-FILENAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RUNTIME_ERROR - Runtime error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SCHEMA_NOT_FOUND - Schema valid in the time period not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSCHEMA_NOT_FOUND - A subschema is not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_IE_XML_SCHEMA 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_molga | TYPE MOLGA, " '08' | |||
| lv_fullpath | TYPE RLGRAP-FILENAME, " | |||
| lv_runtime_error | TYPE RLGRAP, " | |||
| lv_sagrp | TYPE PCAL_SAGRP, " | |||
| lv_schema_not_found | TYPE PCAL_SAGRP, " | |||
| lv_docty | TYPE T50V_XML-DOCTY, " | |||
| lv_subschema_not_found | TYPE T50V_XML, " | |||
| lv_dstyp | TYPE P_DTYPE, " | |||
| lv_date | TYPE BEGDA, " '18000101' | |||
| lv_check_only | TYPE XFELD, " ' ' | |||
| lv_browser | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'HR_IE_XML_SCHEMA' "HR-GB: Output customized XML Schema |
| EXPORTING | ||
| MOLGA | = lv_molga | |
| SAGRP | = lv_sagrp | |
| DOCTY | = lv_docty | |
| DSTYP | = lv_dstyp | |
| DATE | = lv_date | |
| CHECK_ONLY | = lv_check_only | |
| BROWSER | = lv_browser | |
| CHANGING | ||
| FULLPATH | = lv_fullpath | |
| EXCEPTIONS | ||
| RUNTIME_ERROR = 1 | ||
| SCHEMA_NOT_FOUND = 2 | ||
| SUBSCHEMA_NOT_FOUND = 3 | ||
| . " HR_IE_XML_SCHEMA | ||
ABAP code using 7.40 inline data declarations to call FM HR_IE_XML_SCHEMA
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_molga) | = '08'. | |||
| "SELECT single FILENAME FROM RLGRAP INTO @DATA(ld_fullpath). | ||||
| "SELECT single DOCTY FROM T50V_XML INTO @DATA(ld_docty). | ||||
| DATA(ld_date) | = '18000101'. | |||
| DATA(ld_check_only) | = ' '. | |||
| DATA(ld_browser) | = 'X'. | |||
Search for further information about these or an SAP related objects