SAP IBAPI_T_ROUTING_EXPLODE Function Module for NOTRANSL: Anleitung per BAPI in Auftrag einbinden









IBAPI_T_ROUTING_EXPLODE is a standard ibapi t routing explode 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: Anleitung per BAPI in Auftrag einbinden 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 ibapi t routing explode FM, simply by entering the name IBAPI_T_ROUTING_EXPLODE into the relevant SAP transaction such as SE37 or SE38.

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



Function IBAPI_T_ROUTING_EXPLODE 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 'IBAPI_T_ROUTING_EXPLODE'"NOTRANSL: Anleitung per BAPI in Auftrag einbinden
  EXPORTING
   IV_AUFNR =  "Order Number
*  IV_WORKCENTER_FROM_HEADER =  "Selection Indicator
*  IV_REFERENCE_EQUIPMENT =  "Equipment Number
   IV_PLNTY =  "TL Type
   IV_PLNNR =  "Key for Task List Group
   IV_PLNAL =  "Group Counter
*  IV_REPLACE_OPERATIONS =  "Selection Indicator
*  IV_WORKCENTER_ID_SELECT =  "Main work center for maintenance tasks
*  IV_WORKCENTER_PLANT_SELECT =  "Plant
*  IV_WORKCENTER_ID_USE =  "Main work center for maintenance tasks
*  IV_WORKCENTER_PLANT_USE =  "Plant

EXCEPTIONS
   ERROR_OCCURED = 1
.



IMPORTING Parameters details for IBAPI_T_ROUTING_EXPLODE

IV_AUFNR - Order Number

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

IV_WORKCENTER_FROM_HEADER - Selection Indicator

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

IV_REFERENCE_EQUIPMENT - Equipment Number

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

IV_PLNTY - TL Type

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

IV_PLNNR - Key for Task List Group

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

IV_PLNAL - Group Counter

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

IV_REPLACE_OPERATIONS - Selection Indicator

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

IV_WORKCENTER_ID_SELECT - Main work center for maintenance tasks

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

IV_WORKCENTER_PLANT_SELECT - Plant

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

IV_WORKCENTER_ID_USE - Main work center for maintenance tasks

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

IV_WORKCENTER_PLANT_USE - Plant

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

EXCEPTIONS details

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IBAPI_T_ROUTING_EXPLODE 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_iv_aufnr  TYPE AUFNR, "   
lv_error_occured  TYPE AUFNR, "   
lv_iv_workcenter_from_header  TYPE FLG_SEL, "   
lv_iv_reference_equipment  TYPE EQUNR, "   
lv_iv_plnty  TYPE PLNTY, "   
lv_iv_plnnr  TYPE PLNNR, "   
lv_iv_plnal  TYPE PLNAL, "   
lv_iv_replace_operations  TYPE FLG_SEL, "   
lv_iv_workcenter_id_select  TYPE GEWRK, "   
lv_iv_workcenter_plant_select  TYPE WERKS_D, "   
lv_iv_workcenter_id_use  TYPE GEWRK, "   
lv_iv_workcenter_plant_use  TYPE WERKS_D. "   

  CALL FUNCTION 'IBAPI_T_ROUTING_EXPLODE'  "NOTRANSL: Anleitung per BAPI in Auftrag einbinden
    EXPORTING
         IV_AUFNR = lv_iv_aufnr
         IV_WORKCENTER_FROM_HEADER = lv_iv_workcenter_from_header
         IV_REFERENCE_EQUIPMENT = lv_iv_reference_equipment
         IV_PLNTY = lv_iv_plnty
         IV_PLNNR = lv_iv_plnnr
         IV_PLNAL = lv_iv_plnal
         IV_REPLACE_OPERATIONS = lv_iv_replace_operations
         IV_WORKCENTER_ID_SELECT = lv_iv_workcenter_id_select
         IV_WORKCENTER_PLANT_SELECT = lv_iv_workcenter_plant_select
         IV_WORKCENTER_ID_USE = lv_iv_workcenter_id_use
         IV_WORKCENTER_PLANT_USE = lv_iv_workcenter_plant_use
    EXCEPTIONS
        ERROR_OCCURED = 1
. " IBAPI_T_ROUTING_EXPLODE




ABAP code using 7.40 inline data declarations to call FM IBAPI_T_ROUTING_EXPLODE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!