SAP FVD_API_CORR_GET_FORMATED_NAME Function Module for Name Format
FVD_API_CORR_GET_FORMATED_NAME is a standard fvd api corr get formated name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Name Format 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 fvd api corr get formated name FM, simply by entering the name FVD_API_CORR_GET_FORMATED_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_API_CORR_ADDRESS
Program Name: SAPLFVD_API_CORR_ADDRESS
Main Program: SAPLFVD_API_CORR_ADDRESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_API_CORR_GET_FORMATED_NAME 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 'FVD_API_CORR_GET_FORMATED_NAME'"Name Format.
EXPORTING
I_RECEIVER = "BP: General Data I
* I_LANGUAGE = SY-LANGU "Language Key of Current Text Environment
IMPORTING
E_NAME_FORMATED = "Name Formatted According to Country-Specific Rules
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for FVD_API_CORR_GET_FORMATED_NAME
I_RECEIVER - BP: General Data I
Data type: BUT000Optional: No
Call by Reference: Yes
I_LANGUAGE - Language Key of Current Text Environment
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_API_CORR_GET_FORMATED_NAME
E_NAME_FORMATED - Name Formatted According to Country-Specific Rules
Data type: RFVD_CORR_FORMATED_NAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_API_CORR_GET_FORMATED_NAME 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_receiver | TYPE BUT000, " | |||
| lv_internal_error | TYPE BUT000, " | |||
| lv_e_name_formated | TYPE RFVD_CORR_FORMATED_NAME, " | |||
| lv_i_language | TYPE SYLANGU. " SY-LANGU |
|   CALL FUNCTION 'FVD_API_CORR_GET_FORMATED_NAME' "Name Format |
| EXPORTING | ||
| I_RECEIVER | = lv_i_receiver | |
| I_LANGUAGE | = lv_i_language | |
| IMPORTING | ||
| E_NAME_FORMATED | = lv_e_name_formated | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " FVD_API_CORR_GET_FORMATED_NAME | ||
ABAP code using 7.40 inline data declarations to call FM FVD_API_CORR_GET_FORMATED_NAME
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_i_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects