SAP PAL_CONVERT_TO_SUB_TRANSACTION Function Module for Conversion of Flows to Business Subtransactions
PAL_CONVERT_TO_SUB_TRANSACTION is a standard pal convert to sub transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion of Flows to Business Subtransactions 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 pal convert to sub transaction FM, simply by entering the name PAL_CONVERT_TO_SUB_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPM_DERIVED_FLOWS
Program Name: SAPLFPM_DERIVED_FLOWS
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PAL_CONVERT_TO_SUB_TRANSACTION 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 'PAL_CONVERT_TO_SUB_TRANSACTION'"Conversion of Flows to Business Subtransactions.
EXPORTING
I_TAB_FLOWS = "Flows
IMPORTING
C_TAB_SUB_TRANSACTIONS = "Teilgeschäftsvorfälle
IMPORTING Parameters details for PAL_CONVERT_TO_SUB_TRANSACTION
I_TAB_FLOWS - Flows
Data type: TRSEK_TAB_FLOWSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PAL_CONVERT_TO_SUB_TRANSACTION
C_TAB_SUB_TRANSACTIONS - Teilgeschäftsvorfälle
Data type: TRSEK_TAB_SUB_TRANSACTIONSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PAL_CONVERT_TO_SUB_TRANSACTION 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_tab_flows | TYPE TRSEK_TAB_FLOWS, " | |||
| lv_c_tab_sub_transactions | TYPE TRSEK_TAB_SUB_TRANSACTIONS. " |
|   CALL FUNCTION 'PAL_CONVERT_TO_SUB_TRANSACTION' "Conversion of Flows to Business Subtransactions |
| EXPORTING | ||
| I_TAB_FLOWS | = lv_i_tab_flows | |
| IMPORTING | ||
| C_TAB_SUB_TRANSACTIONS | = lv_c_tab_sub_transactions | |
| . " PAL_CONVERT_TO_SUB_TRANSACTION | ||
ABAP code using 7.40 inline data declarations to call FM PAL_CONVERT_TO_SUB_TRANSACTION
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