SAP IDOC_INPUT_ASSET_POSTCAP_POST Function Module for
IDOC_INPUT_ASSET_POSTCAP_POST is a standard idoc input asset postcap post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 idoc input asset postcap post FM, simply by entering the name IDOC_INPUT_ASSET_POSTCAP_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: AMFA
Program Name: SAPLAMFA
Main Program: SAPLAMFA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function IDOC_INPUT_ASSET_POSTCAP_POST 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 'IDOC_INPUT_ASSET_POSTCAP_POST'".
EXPORTING
INPUT_METHOD = "
MASS_PROCESSING = "
IMPORTING
WORKFLOW_RESULT = "
APPLICATION_VARIABLE = "
IN_UPDATE_TASK = "
CALL_TRANSACTION_DONE = "
TABLES
IDOC_CONTRL = "
IDOC_DATA = "
IDOC_STATUS = "
RETURN_VARIABLES = "
SERIALIZATION_INFO = "
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
IMPORTING Parameters details for IDOC_INPUT_ASSET_POSTCAP_POST
INPUT_METHOD -
Data type: BDWFAP_PAR-INPUTMETHDOptional: No
Call by Reference: No ( called with pass by value option)
MASS_PROCESSING -
Data type: BDWFAP_PAR-MASS_PROCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IDOC_INPUT_ASSET_POSTCAP_POST
WORKFLOW_RESULT -
Data type: BDWF_PARAM-RESULTOptional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_VARIABLE -
Data type: BDWF_PARAM-APPL_VAROptional: No
Call by Reference: No ( called with pass by value option)
IN_UPDATE_TASK -
Data type: BDWFAP_PAR-UPDATETASKOptional: No
Call by Reference: No ( called with pass by value option)
CALL_TRANSACTION_DONE -
Data type: BDWFAP_PAR-CALLTRANSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_INPUT_ASSET_POSTCAP_POST
IDOC_CONTRL -
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_DATA -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_STATUS -
Data type: BDIDOCSTATOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_VARIABLES -
Data type: BDWFRETVAROptional: No
Call by Reference: No ( called with pass by value option)
SERIALIZATION_INFO -
Data type: BDI_SEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_FUNCTION_CALLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_INPUT_ASSET_POSTCAP_POST 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: | ||||
lt_idoc_contrl | TYPE STANDARD TABLE OF EDIDC, " | |||
lv_input_method | TYPE BDWFAP_PAR-INPUTMETHD, " | |||
lv_workflow_result | TYPE BDWF_PARAM-RESULT, " | |||
lv_wrong_function_called | TYPE BDWF_PARAM, " | |||
lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
lv_mass_processing | TYPE BDWFAP_PAR-MASS_PROC, " | |||
lv_application_variable | TYPE BDWF_PARAM-APPL_VAR, " | |||
lt_idoc_status | TYPE STANDARD TABLE OF BDIDOCSTAT, " | |||
lv_in_update_task | TYPE BDWFAP_PAR-UPDATETASK, " | |||
lt_return_variables | TYPE STANDARD TABLE OF BDWFRETVAR, " | |||
lv_call_transaction_done | TYPE BDWFAP_PAR-CALLTRANS, " | |||
lt_serialization_info | TYPE STANDARD TABLE OF BDI_SER. " |
  CALL FUNCTION 'IDOC_INPUT_ASSET_POSTCAP_POST' " |
EXPORTING | ||
INPUT_METHOD | = lv_input_method | |
MASS_PROCESSING | = lv_mass_processing | |
IMPORTING | ||
WORKFLOW_RESULT | = lv_workflow_result | |
APPLICATION_VARIABLE | = lv_application_variable | |
IN_UPDATE_TASK | = lv_in_update_task | |
CALL_TRANSACTION_DONE | = lv_call_transaction_done | |
TABLES | ||
IDOC_CONTRL | = lt_idoc_contrl | |
IDOC_DATA | = lt_idoc_data | |
IDOC_STATUS | = lt_idoc_status | |
RETURN_VARIABLES | = lt_return_variables | |
SERIALIZATION_INFO | = lt_serialization_info | |
EXCEPTIONS | ||
WRONG_FUNCTION_CALLED = 1 | ||
. " IDOC_INPUT_ASSET_POSTCAP_POST |
ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_ASSET_POSTCAP_POST
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."SELECT single INPUTMETHD FROM BDWFAP_PAR INTO @DATA(ld_input_method). | ||||
"SELECT single RESULT FROM BDWF_PARAM INTO @DATA(ld_workflow_result). | ||||
"SELECT single MASS_PROC FROM BDWFAP_PAR INTO @DATA(ld_mass_processing). | ||||
"SELECT single APPL_VAR FROM BDWF_PARAM INTO @DATA(ld_application_variable). | ||||
"SELECT single UPDATETASK FROM BDWFAP_PAR INTO @DATA(ld_in_update_task). | ||||
"SELECT single CALLTRANS FROM BDWFAP_PAR INTO @DATA(ld_call_transaction_done). | ||||
Search for further information about these or an SAP related objects