SAP ISAUTO_SICSR_CHECK_APO Function Module for Check planning in APO
ISAUTO_SICSR_CHECK_APO is a standard isauto sicsr check apo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check planning in APO 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 isauto sicsr check apo FM, simply by entering the name ISAUTO_SICSR_CHECK_APO into the relevant SAP transaction such as SE37 or SE38.
Function Group: ISAUTO_SICSR
Program Name: SAPLISAUTO_SICSR
Main Program: SAPLISAUTO_SICSR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISAUTO_SICSR_CHECK_APO 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 'ISAUTO_SICSR_CHECK_APO'"Check planning in APO.
EXPORTING
IF_EBELN = "Purchasing Document Number
IF_EBELP = "Item Number of Purchasing Document
EXCEPTIONS
PO_ITEM_NOT_FOUND = 1 APO_PLANNED = 2
IMPORTING Parameters details for ISAUTO_SICSR_CHECK_APO
IF_EBELN - Purchasing Document Number
Data type: BAPIEKKO-PO_NUMBEROptional: No
Call by Reference: Yes
IF_EBELP - Item Number of Purchasing Document
Data type: BAPIEKPO-PO_ITEMOptional: No
Call by Reference: Yes
EXCEPTIONS details
PO_ITEM_NOT_FOUND - Scheduling agreement item not existing
Data type:Optional: No
Call by Reference: Yes
APO_PLANNED - Purch. doc. planned in APO: Output in ERP not possible
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISAUTO_SICSR_CHECK_APO 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_if_ebeln | TYPE BAPIEKKO-PO_NUMBER, " | |||
| lv_po_item_not_found | TYPE BAPIEKKO, " | |||
| lv_if_ebelp | TYPE BAPIEKPO-PO_ITEM, " | |||
| lv_apo_planned | TYPE BAPIEKPO. " |
|   CALL FUNCTION 'ISAUTO_SICSR_CHECK_APO' "Check planning in APO |
| EXPORTING | ||
| IF_EBELN | = lv_if_ebeln | |
| IF_EBELP | = lv_if_ebelp | |
| EXCEPTIONS | ||
| PO_ITEM_NOT_FOUND = 1 | ||
| APO_PLANNED = 2 | ||
| . " ISAUTO_SICSR_CHECK_APO | ||
ABAP code using 7.40 inline data declarations to call FM ISAUTO_SICSR_CHECK_APO
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 PO_NUMBER FROM BAPIEKKO INTO @DATA(ld_if_ebeln). | ||||
| "SELECT single PO_ITEM FROM BAPIEKPO INTO @DATA(ld_if_ebelp). | ||||
Search for further information about these or an SAP related objects