SAP EDI_VIEW_UPDATE Function Module for
EDI_VIEW_UPDATE is a standard edi view update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 edi view update FM, simply by entering the name EDI_VIEW_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDIM
Program Name: SAPLEDIM
Main Program: SAPLEDIM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDI_VIEW_UPDATE 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 'EDI_VIEW_UPDATE'".
EXPORTING
PI_VIEW = "View name
PI_ATTRIBUTES = "Attributes To Be Changed
IMPORTING
PE_ATTRIBUTES = "
CHANGING
* PC_ORDER = "Request
TABLES
PT_SYNTAX = "Syntax table for view
EXCEPTIONS
OBJECT_NOT_FOUND = 1 SYNTAX_ERROR = 2 TRANSPORT_ERROR = 3 DB_ERROR = 4 NO_AUTHORITY = 5 LOCK_ERROR = 6
IMPORTING Parameters details for EDI_VIEW_UPDATE
PI_VIEW - View name
Data type: EDVIEW-EDIVIEWOptional: No
Call by Reference: No ( called with pass by value option)
PI_ATTRIBUTES - Attributes To Be Changed
Data type: EDI_IAPI08Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EDI_VIEW_UPDATE
PE_ATTRIBUTES -
Data type: EDI_IAPI08Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EDI_VIEW_UPDATE
PC_ORDER - Request
Data type: EDI_IAPI07-TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EDI_VIEW_UPDATE
PT_SYNTAX - Syntax table for view
Data type: VIEWSYNOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYNTAX_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TRANSPORT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ERROR - Database Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOCK_ERROR - Locking Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EDI_VIEW_UPDATE 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_pi_view | TYPE EDVIEW-EDIVIEW, " | |||
| lv_pc_order | TYPE EDI_IAPI07-TRKORR, " | |||
| lt_pt_syntax | TYPE STANDARD TABLE OF VIEWSYN, " | |||
| lv_pe_attributes | TYPE EDI_IAPI08, " | |||
| lv_object_not_found | TYPE EDI_IAPI08, " | |||
| lv_syntax_error | TYPE EDI_IAPI08, " | |||
| lv_pi_attributes | TYPE EDI_IAPI08, " | |||
| lv_transport_error | TYPE EDI_IAPI08, " | |||
| lv_db_error | TYPE EDI_IAPI08, " | |||
| lv_no_authority | TYPE EDI_IAPI08, " | |||
| lv_lock_error | TYPE EDI_IAPI08. " |
|   CALL FUNCTION 'EDI_VIEW_UPDATE' " |
| EXPORTING | ||
| PI_VIEW | = lv_pi_view | |
| PI_ATTRIBUTES | = lv_pi_attributes | |
| IMPORTING | ||
| PE_ATTRIBUTES | = lv_pe_attributes | |
| CHANGING | ||
| PC_ORDER | = lv_pc_order | |
| TABLES | ||
| PT_SYNTAX | = lt_pt_syntax | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| SYNTAX_ERROR = 2 | ||
| TRANSPORT_ERROR = 3 | ||
| DB_ERROR = 4 | ||
| NO_AUTHORITY = 5 | ||
| LOCK_ERROR = 6 | ||
| . " EDI_VIEW_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM EDI_VIEW_UPDATE
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 EDIVIEW FROM EDVIEW INTO @DATA(ld_pi_view). | ||||
| "SELECT single TRKORR FROM EDI_IAPI07 INTO @DATA(ld_pc_order). | ||||
Search for further information about these or an SAP related objects