SAP FMFG_DERIVE_UNFILLED_ORDERS Function Module for Derivation: Sales Order Adjustment Program

Search SAP Function Modules

FMFG_DERIVE_UNFILLED_ORDERS is a standard fmfg derive unfilled orders SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Derivation: Sales Order Adjustment Program 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 fmfg derive unfilled orders FM, simply by entering the name FMFG_DERIVE_UNFILLED_ORDERS into the relevant SAP transaction such as SE37 or SE38.

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

Function FMFG_DERIVE_UNFILLED_ORDERS 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 'FMFG_DERIVE_UNFILLED_ORDERS'"Derivation: Sales Order Adjustment Program
  EXPORTING
*  I_ENVIRONMENT = 'SAP' "Environment for strategy
*  I_SUBCLASS = '01' "Subgroup by Application Class
   I_FMFG_UNFILLED_ORDERS_DERIVE =  "Source/target fields used by the SO Adjustment Program derivation
*  I_FLG_BUFFER = 'X' "Buffer derivation

 IMPORTING
   E_FMFG_UNFILLED_ORDERS_DERIVE =  "Source/Target Fields for the SO Adjustmnt Prog Derivation

EXCEPTIONS
   DERIVATION_FAILED = 1 

.

IMPORTING Parameters details for FMFG_DERIVE_UNFILLED_ORDERS

I_ENVIRONMENT - Environment for strategy

Data type: ABADRENV
Default: 'SAP'
Optional: Yes
Call by Reference: Yes

I_SUBCLASS - Subgroup by Application Class

Data type: ABADRSUBCLASS
Default: '01'
Optional: Yes
Call by Reference: Yes

I_FMFG_UNFILLED_ORDERS_DERIVE - Source/target fields used by the SO Adjustment Program derivation

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

I_FLG_BUFFER - Buffer derivation

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMFG_DERIVE_UNFILLED_ORDERS

E_FMFG_UNFILLED_ORDERS_DERIVE - Source/Target Fields for the SO Adjustmnt Prog Derivation

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

EXCEPTIONS details

DERIVATION_FAILED - Derivation failed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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