SAP FM_FG_GET_PARTNER_FROM_CMMTSTR Function Module for Get customer and vendor from commitment string
FM_FG_GET_PARTNER_FROM_CMMTSTR is a standard fm fg get partner from cmmtstr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get customer and vendor from commitment string 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 fm fg get partner from cmmtstr FM, simply by entering the name FM_FG_GET_PARTNER_FROM_CMMTSTR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_SV
Program Name: SAPLFMFG_SV
Main Program: SAPLFMFG_SV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_FG_GET_PARTNER_FROM_CMMTSTR 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 'FM_FG_GET_PARTNER_FROM_CMMTSTR'"Get customer and vendor from commitment string.
EXPORTING
I_CMMTSTR = "FM Commitment String For Budgetary Ledger
* I_GLX_ACCIT = "FI: Interface to Accounting: Item Information
* I_ACCHD = "Interface to Accounting: Header Information
CHANGING
* C_LIFNR = "Account Number of Vendor or Creditor
* C_KUNNR = "Customer Number 1
* C_VBUND = "Company ID
* C_IPFLAG = "Single-Character Flag
IMPORTING Parameters details for FM_FG_GET_PARTNER_FROM_CMMTSTR
I_CMMTSTR - FM Commitment String For Budgetary Ledger
Data type: FMCMMTSTROptional: No
Call by Reference: Yes
I_GLX_ACCIT - FI: Interface to Accounting: Item Information
Data type: ACCIT_GLXOptional: Yes
Call by Reference: Yes
I_ACCHD - Interface to Accounting: Header Information
Data type: ACCHDOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for FM_FG_GET_PARTNER_FROM_CMMTSTR
C_LIFNR - Account Number of Vendor or Creditor
Data type: LIFNROptional: Yes
Call by Reference: Yes
C_KUNNR - Customer Number 1
Data type: KUNNROptional: Yes
Call by Reference: Yes
C_VBUND - Company ID
Data type: VBUNDOptional: Yes
Call by Reference: Yes
C_IPFLAG - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FM_FG_GET_PARTNER_FROM_CMMTSTR 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_c_lifnr | TYPE LIFNR, " | |||
| lv_i_cmmtstr | TYPE FMCMMTSTR, " | |||
| lv_c_kunnr | TYPE KUNNR, " | |||
| lv_i_glx_accit | TYPE ACCIT_GLX, " | |||
| lv_c_vbund | TYPE VBUND, " | |||
| lv_i_acchd | TYPE ACCHD, " | |||
| lv_c_ipflag | TYPE CHAR1. " |
|   CALL FUNCTION 'FM_FG_GET_PARTNER_FROM_CMMTSTR' "Get customer and vendor from commitment string |
| EXPORTING | ||
| I_CMMTSTR | = lv_i_cmmtstr | |
| I_GLX_ACCIT | = lv_i_glx_accit | |
| I_ACCHD | = lv_i_acchd | |
| CHANGING | ||
| C_LIFNR | = lv_c_lifnr | |
| C_KUNNR | = lv_c_kunnr | |
| C_VBUND | = lv_c_vbund | |
| C_IPFLAG | = lv_c_ipflag | |
| . " FM_FG_GET_PARTNER_FROM_CMMTSTR | ||
ABAP code using 7.40 inline data declarations to call FM FM_FG_GET_PARTNER_FROM_CMMTSTR
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