SAP 2002_NETWORK_MAINTAIN Function Module for NOTRANSL: implementation of BAPI_NETWORK_MAINTAIN
2002_NETWORK_MAINTAIN is a standard 2002 network maintain 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: implementation of BAPI_NETWORK_MAINTAIN 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 2002 network maintain FM, simply by entering the name 2002_NETWORK_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2002
Program Name: SAPL2002
Main Program: SAPL2002
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function 2002_NETWORK_MAINTAIN 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 '2002_NETWORK_MAINTAIN'"NOTRANSL: implementation of BAPI_NETWORK_MAINTAIN.
IMPORTING
RETURN = "Return Parameter
TABLES
I_METHOD_PROJECT = "BAPI structure: Processing methods
* I_RELATION = "BAPI structure for network relationships
* I_RELATION_UPDATE = "Update structure: Network relations
* E_MESSAGE_TABLE = "Message table for BAPIs (Project System)
* I_NETWORK = "Network BAPI structure
* I_NETWORK_UPDATE = "Network header BAPI structure update
* I_ACTIVITY = "BAPI structure for network activities
* I_ACTIVITY_UPDATE = "Update structure: Network activity
* I_ACTIVITY_ELEMENT = "BAPI Structure for Activity Elements
* I_ACTIVITY_ELEMENT_UPDATE = "Update Structure: ActivityElement
* I_ACTIVITY_MILESTONE = "BAPI Structure for Milestones under Network Activity
* I_ACTIVITY_MILESTONE_UPDATE = "BAPI Structure Milestones under Activity (Update Fields)
EXPORTING Parameters details for 2002_NETWORK_MAINTAIN
RETURN - Return Parameter
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for 2002_NETWORK_MAINTAIN
I_METHOD_PROJECT - BAPI structure: Processing methods
Data type: BAPI_METHOD_PROJECTOptional: No
Call by Reference: No ( called with pass by value option)
I_RELATION - BAPI structure for network relationships
Data type: BAPI_NETWORK_RELATIONOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RELATION_UPDATE - Update structure: Network relations
Data type: BAPI_NETWORK_RELATION_UPOptional: Yes
Call by Reference: No ( called with pass by value option)
E_MESSAGE_TABLE - Message table for BAPIs (Project System)
Data type: BAPI_METH_MESSAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NETWORK - Network BAPI structure
Data type: BAPI_NETWORKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NETWORK_UPDATE - Network header BAPI structure update
Data type: BAPI_NETWORK_UPDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY - BAPI structure for network activities
Data type: BAPI_NETWORK_ACTIVITYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY_UPDATE - Update structure: Network activity
Data type: BAPI_NETWORK_ACTIVITY_UPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY_ELEMENT - BAPI Structure for Activity Elements
Data type: BAPI_ACT_ELEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY_ELEMENT_UPDATE - Update Structure: ActivityElement
Data type: BAPI_ACT_ELEMENT_UPDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY_MILESTONE - BAPI Structure for Milestones under Network Activity
Data type: BAPI_ACT_MILESTONEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY_MILESTONE_UPDATE - BAPI Structure Milestones under Activity (Update Fields)
Data type: BAPI_ACT_MILESTONE_UPDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for 2002_NETWORK_MAINTAIN 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_return | TYPE BAPIRETURN1, " | |||
| lt_i_method_project | TYPE STANDARD TABLE OF BAPI_METHOD_PROJECT, " | |||
| lt_i_relation | TYPE STANDARD TABLE OF BAPI_NETWORK_RELATION, " | |||
| lt_i_relation_update | TYPE STANDARD TABLE OF BAPI_NETWORK_RELATION_UP, " | |||
| lt_e_message_table | TYPE STANDARD TABLE OF BAPI_METH_MESSAGE, " | |||
| lt_i_network | TYPE STANDARD TABLE OF BAPI_NETWORK, " | |||
| lt_i_network_update | TYPE STANDARD TABLE OF BAPI_NETWORK_UPDATE, " | |||
| lt_i_activity | TYPE STANDARD TABLE OF BAPI_NETWORK_ACTIVITY, " | |||
| lt_i_activity_update | TYPE STANDARD TABLE OF BAPI_NETWORK_ACTIVITY_UP, " | |||
| lt_i_activity_element | TYPE STANDARD TABLE OF BAPI_ACT_ELEMENT, " | |||
| lt_i_activity_element_update | TYPE STANDARD TABLE OF BAPI_ACT_ELEMENT_UPD, " | |||
| lt_i_activity_milestone | TYPE STANDARD TABLE OF BAPI_ACT_MILESTONE, " | |||
| lt_i_activity_milestone_update | TYPE STANDARD TABLE OF BAPI_ACT_MILESTONE_UPD. " |
|   CALL FUNCTION '2002_NETWORK_MAINTAIN' "NOTRANSL: implementation of BAPI_NETWORK_MAINTAIN |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| I_METHOD_PROJECT | = lt_i_method_project | |
| I_RELATION | = lt_i_relation | |
| I_RELATION_UPDATE | = lt_i_relation_update | |
| E_MESSAGE_TABLE | = lt_e_message_table | |
| I_NETWORK | = lt_i_network | |
| I_NETWORK_UPDATE | = lt_i_network_update | |
| I_ACTIVITY | = lt_i_activity | |
| I_ACTIVITY_UPDATE | = lt_i_activity_update | |
| I_ACTIVITY_ELEMENT | = lt_i_activity_element | |
| I_ACTIVITY_ELEMENT_UPDATE | = lt_i_activity_element_update | |
| I_ACTIVITY_MILESTONE | = lt_i_activity_milestone | |
| I_ACTIVITY_MILESTONE_UPDATE | = lt_i_activity_milestone_update | |
| . " 2002_NETWORK_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM 2002_NETWORK_MAINTAIN
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