SAP CALL_TRANSACTION_APO Function Module for NOTRANSL: Aufruf APO Transaktionen von MD04

Search SAP Function Modules

CALL_TRANSACTION_APO is a standard call transaction 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 NOTRANSL: Aufruf APO Transaktionen von MD04 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 call transaction apo FM, simply by entering the name CALL_TRANSACTION_APO into the relevant SAP transaction such as SE37 or SE38.

Function Group: M61R
Program Name: SAPLM61R
Main Program: SAPLM61R
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CALL_TRANSACTION_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 'CALL_TRANSACTION_APO'"NOTRANSL: Aufruf APO Transaktionen von MD04
  EXPORTING
   IV_MATNR =  "Material Number
   IV_WERKS =  "Plant
   IV_LGORT =  "Storage Location
   IV_TCODE =  "Transaction Code
*  IV_NMODE =  "Transaction Call in New Session
*  IV_ANFBD =  "Transaction Call with Initial Screen

TABLES
*  IT_PARAMS =  "SPA/GPA structure for RFC

EXCEPTIONS
   MAT_NOT_RELEVANT = 1    NO_PLUGIN = 2    NO_IMOD = 3    NO_RFCDEST = 4    OWN_LOGSYS_UNKNOWN = 5    UNSUPPORTED_RELEASE = 6    RFC_ERROR = 7 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLM61R_001 User Exit for Evaluation PP-MRP Material Requirements Planning

IMPORTING Parameters details for CALL_TRANSACTION_APO

IV_MATNR - Material Number

Data type: MATNR
Optional: No
Call by Reference: Yes

IV_WERKS - Plant

Data type: WERKS_D
Optional: No
Call by Reference: Yes

IV_LGORT - Storage Location

Data type: LGORT_D
Optional: No
Call by Reference: Yes

IV_TCODE - Transaction Code

Data type: TCODE
Optional: No
Call by Reference: Yes

IV_NMODE - Transaction Call in New Session

Data type: ANMOD
Optional: Yes
Call by Reference: Yes

IV_ANFBD - Transaction Call with Initial Screen

Data type: ANFBD
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for CALL_TRANSACTION_APO

IT_PARAMS - SPA/GPA structure for RFC

Data type: RFC_SPAGPA
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

MAT_NOT_RELEVANT -

Data type:
Optional: No
Call by Reference: Yes

NO_PLUGIN -

Data type:
Optional: No
Call by Reference: Yes

NO_IMOD -

Data type:
Optional: No
Call by Reference: Yes

NO_RFCDEST -

Data type:
Optional: No
Call by Reference: Yes

OWN_LOGSYS_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

UNSUPPORTED_RELEASE -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR - Error During RFC Call

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CALL_TRANSACTION_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.

ABAP code using 7.40 inline data declarations to call FM CALL_TRANSACTION_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.

Search for further information about these or an SAP related objects