SAP TPM_MIG_AD_EXTRACT_OTC_SINGLE Function Module for Extraction of OTC Transactions for Accrual/Deferral
TPM_MIG_AD_EXTRACT_OTC_SINGLE is a standard tpm mig ad extract otc single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extraction of OTC Transactions for Accrual/Deferral 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 tpm mig ad extract otc single FM, simply by entering the name TPM_MIG_AD_EXTRACT_OTC_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_TRG_MIGRATION_ERP07
Program Name: SAPLTPM_TRG_MIGRATION_ERP07
Main Program: SAPLTPM_TRG_MIGRATION_ERP07
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TPM_MIG_AD_EXTRACT_OTC_SINGLE 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 'TPM_MIG_AD_EXTRACT_OTC_SINGLE'"Extraction of OTC Transactions for Accrual/Deferral.
EXPORTING
IM_MODE = "Processing Mode
IM_PROTOCOL_HANDLER = "Protocol Manager
IM_COMPANY_CODE = "Company Code
IM_DEAL_NUMBER = "Financial Transaction
IM_REFRESH = "First call
IM_MIGR_CUST = "Customizing for Converting to Enterprise 2.0
IMPORTING
EX_CANCEL = "Benutzer hat Verarbeitung abgebrochen
CHANGING
CH_EXECUTION_RATE = "Execution Rate of Migration Step
IMPORTING Parameters details for TPM_MIG_AD_EXTRACT_OTC_SINGLE
IM_MODE - Processing Mode
Data type: TPM_MODEOptional: No
Call by Reference: Yes
IM_PROTOCOL_HANDLER - Protocol Manager
Data type: CL_PROTOCOL_HANDLER_TRPOptional: No
Call by Reference: Yes
IM_COMPANY_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
IM_DEAL_NUMBER - Financial Transaction
Data type: TB_RFHAOptional: No
Call by Reference: Yes
IM_REFRESH - First call
Data type: CHAR1Optional: No
Call by Reference: Yes
IM_MIGR_CUST - Customizing for Converting to Enterprise 2.0
Data type: TRGC_MIGR1Optional: No
Call by Reference: Yes
EXPORTING Parameters details for TPM_MIG_AD_EXTRACT_OTC_SINGLE
EX_CANCEL - Benutzer hat Verarbeitung abgebrochen
Data type: CHAR1Optional: No
Call by Reference: Yes
CHANGING Parameters details for TPM_MIG_AD_EXTRACT_OTC_SINGLE
CH_EXECUTION_RATE - Execution Rate of Migration Step
Data type: TPM_MIGRATION_EXECUTION_RATEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TPM_MIG_AD_EXTRACT_OTC_SINGLE 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_im_mode | TYPE TPM_MODE, " | |||
| lv_ex_cancel | TYPE CHAR1, " | |||
| lv_ch_execution_rate | TYPE TPM_MIGRATION_EXECUTION_RATE, " | |||
| lv_im_protocol_handler | TYPE CL_PROTOCOL_HANDLER_TRP, " | |||
| lv_im_company_code | TYPE BUKRS, " | |||
| lv_im_deal_number | TYPE TB_RFHA, " | |||
| lv_im_refresh | TYPE CHAR1, " | |||
| lv_im_migr_cust | TYPE TRGC_MIGR1. " |
|   CALL FUNCTION 'TPM_MIG_AD_EXTRACT_OTC_SINGLE' "Extraction of OTC Transactions for Accrual/Deferral |
| EXPORTING | ||
| IM_MODE | = lv_im_mode | |
| IM_PROTOCOL_HANDLER | = lv_im_protocol_handler | |
| IM_COMPANY_CODE | = lv_im_company_code | |
| IM_DEAL_NUMBER | = lv_im_deal_number | |
| IM_REFRESH | = lv_im_refresh | |
| IM_MIGR_CUST | = lv_im_migr_cust | |
| IMPORTING | ||
| EX_CANCEL | = lv_ex_cancel | |
| CHANGING | ||
| CH_EXECUTION_RATE | = lv_ch_execution_rate | |
| . " TPM_MIG_AD_EXTRACT_OTC_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM TPM_MIG_AD_EXTRACT_OTC_SINGLE
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