SAP ADSPCM_STORE_S2KM Function Module for Store S2KM-data directly in tables (MM/SD) after IDOC_INPUT..
ADSPCM_STORE_S2KM is a standard adspcm store s2km SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Store S2KM-data directly in tables (MM/SD) after IDOC_INPUT.. 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 adspcm store s2km FM, simply by entering the name ADSPCM_STORE_S2KM into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADSPCM03
Program Name: SAPLADSPCM03
Main Program: SAPLADSPCM03
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADSPCM_STORE_S2KM 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 'ADSPCM_STORE_S2KM'"Store S2KM-data directly in tables (MM/SD) after IDOC_INPUT...
EXPORTING
TRG_EDIDC = "Control record (IDoc)
CHANGING
* I_BELNR = "
TABLES
TRG_EDIDD = "Data record (IDoc)
IMPORTING Parameters details for ADSPCM_STORE_S2KM
TRG_EDIDC - Control record (IDoc)
Data type: EDIDCOptional: No
Call by Reference: Yes
CHANGING Parameters details for ADSPCM_STORE_S2KM
I_BELNR -
Data type:Optional: Yes
Call by Reference: Yes
TABLES Parameters details for ADSPCM_STORE_S2KM
TRG_EDIDD - Data record (IDoc)
Data type: EDIDDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ADSPCM_STORE_S2KM 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_belnr | TYPE STRING, " | |||
| lv_trg_edidc | TYPE EDIDC, " | |||
| lt_trg_edidd | TYPE STANDARD TABLE OF EDIDD. " |
|   CALL FUNCTION 'ADSPCM_STORE_S2KM' "Store S2KM-data directly in tables (MM/SD) after IDOC_INPUT.. |
| EXPORTING | ||
| TRG_EDIDC | = lv_trg_edidc | |
| CHANGING | ||
| I_BELNR | = lv_i_belnr | |
| TABLES | ||
| TRG_EDIDD | = lt_trg_edidd | |
| . " ADSPCM_STORE_S2KM | ||
ABAP code using 7.40 inline data declarations to call FM ADSPCM_STORE_S2KM
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