SAP QALK_ISR_DOC_FLOW_POST Function Module for NOTRANSL: Fortschreiben des Belegfulßs für Meldung und Maßnahme
QALK_ISR_DOC_FLOW_POST is a standard qalk isr doc flow post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Fortschreiben des Belegfulßs für Meldung und Maßnahme 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 qalk isr doc flow post FM, simply by entering the name QALK_ISR_DOC_FLOW_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: QMEL_UC
Program Name: SAPLQMEL_UC
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QALK_ISR_DOC_FLOW_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 'QALK_ISR_DOC_FLOW_POST'"NOTRANSL: Fortschreiben des Belegfulßs für Meldung und Maßnahme.
EXPORTING
IS_BORIDENT = "Object Relationship Service: BOR Object Identifier
EXCEPTIONS
NOT_ALLOWED = 1
IMPORTING Parameters details for QALK_ISR_DOC_FLOW_POST
IS_BORIDENT - Object Relationship Service: BOR Object Identifier
Data type: BORIDENTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_ALLOWED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for QALK_ISR_DOC_FLOW_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: | ||||
| lv_is_borident | TYPE BORIDENT, " | |||
| lv_not_allowed | TYPE BORIDENT. " |
|   CALL FUNCTION 'QALK_ISR_DOC_FLOW_POST' "NOTRANSL: Fortschreiben des Belegfulßs für Meldung und Maßnahme |
| EXPORTING | ||
| IS_BORIDENT | = lv_is_borident | |
| EXCEPTIONS | ||
| NOT_ALLOWED = 1 | ||
| . " QALK_ISR_DOC_FLOW_POST | ||
ABAP code using 7.40 inline data declarations to call FM QALK_ISR_DOC_FLOW_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.Search for further information about these or an SAP related objects