SAP CNV_TDMS_HCM_POST_TRANSFER Function Module for TDMS4HCM: Call CNV_TDMS_HCM_CHECK_PLOGI_GEN from Control
CNV_TDMS_HCM_POST_TRANSFER is a standard cnv tdms hcm post transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TDMS4HCM: Call CNV_TDMS_HCM_CHECK_PLOGI_GEN from Control 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 cnv tdms hcm post transfer FM, simply by entering the name CNV_TDMS_HCM_POST_TRANSFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_TDMS_HCM
Program Name: SAPLCNV_TDMS_HCM
Main Program: SAPLCNV_TDMS_HCM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_TDMS_HCM_POST_TRANSFER 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 'CNV_TDMS_HCM_POST_TRANSFER'"TDMS4HCM: Call CNV_TDMS_HCM_CHECK_PLOGI_GEN from Control.
EXPORTING
* IV_MULTIPLICATION = "TDMS4HCM: Multiplication factor
* IM_PACKID = "Package Number to Specify CMIS and TDMS Packages
TABLES
IT_PP_KEYS = "TDMS4HCM: Key table: old and new
ET_MESSAGES = "Application Log: APPL_LOG_WRITE_MESSAGES interface
* ET_PP_PDSNR = "Application Log: APPL_LOG_WRITE_MESSAGES interface
* ET_PP_NRANGE = "Application Log: APPL_LOG_WRITE_MESSAGES interface
* ET_MESSAGES_LOG = "Message log : BALMI
* IT_CNVHCM_PACKPAR = "TDMS4HCM: Chosen parameters for a given pack ID
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for CNV_TDMS_HCM_POST_TRANSFER
IV_MULTIPLICATION - TDMS4HCM: Multiplication factor
Data type: CNV_HCM_MULTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_PACKID - Package Number to Specify CMIS and TDMS Packages
Data type: CNV_MBT_PACKIDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_TDMS_HCM_POST_TRANSFER
IT_PP_KEYS - TDMS4HCM: Key table: old and new
Data type: CNVHCM_PP_KEYSOptional: No
Call by Reference: Yes
ET_MESSAGES - Application Log: APPL_LOG_WRITE_MESSAGES interface
Data type: BALMIOptional: No
Call by Reference: Yes
ET_PP_PDSNR - Application Log: APPL_LOG_WRITE_MESSAGES interface
Data type: PDSNROptional: Yes
Call by Reference: Yes
ET_PP_NRANGE - Application Log: APPL_LOG_WRITE_MESSAGES interface
Data type: BALMIOptional: Yes
Call by Reference: Yes
ET_MESSAGES_LOG - Message log : BALMI
Data type: BALMIOptional: Yes
Call by Reference: Yes
IT_CNVHCM_PACKPAR - TDMS4HCM: Chosen parameters for a given pack ID
Data type: CNVHCM_PACKPAR_SOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - CL_HRCE_MASTERSWITCHES Not Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_TDMS_HCM_POST_TRANSFER 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_not_found | TYPE STRING, " | |||
| lt_it_pp_keys | TYPE STANDARD TABLE OF CNVHCM_PP_KEYS, " | |||
| lv_iv_multiplication | TYPE CNV_HCM_MULT, " | |||
| lv_im_packid | TYPE CNV_MBT_PACKID, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BALMI, " | |||
| lt_et_pp_pdsnr | TYPE STANDARD TABLE OF PDSNR, " | |||
| lt_et_pp_nrange | TYPE STANDARD TABLE OF BALMI, " | |||
| lt_et_messages_log | TYPE STANDARD TABLE OF BALMI, " | |||
| lt_it_cnvhcm_packpar | TYPE STANDARD TABLE OF CNVHCM_PACKPAR_S. " |
|   CALL FUNCTION 'CNV_TDMS_HCM_POST_TRANSFER' "TDMS4HCM: Call CNV_TDMS_HCM_CHECK_PLOGI_GEN from Control |
| EXPORTING | ||
| IV_MULTIPLICATION | = lv_iv_multiplication | |
| IM_PACKID | = lv_im_packid | |
| TABLES | ||
| IT_PP_KEYS | = lt_it_pp_keys | |
| ET_MESSAGES | = lt_et_messages | |
| ET_PP_PDSNR | = lt_et_pp_pdsnr | |
| ET_PP_NRANGE | = lt_et_pp_nrange | |
| ET_MESSAGES_LOG | = lt_et_messages_log | |
| IT_CNVHCM_PACKPAR | = lt_it_cnvhcm_packpar | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CNV_TDMS_HCM_POST_TRANSFER | ||
ABAP code using 7.40 inline data declarations to call FM CNV_TDMS_HCM_POST_TRANSFER
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.Search for further information about these or an SAP related objects