SAP DDIF_VIEW_PUT Function Module for DD: Interface for writing a view in the ABAP Dictionary

Search SAP Function Modules

DDIF_VIEW_PUT is a standard ddif view put SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Interface for writing a view in the ABAP Dictionary 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 ddif view put FM, simply by entering the name DDIF_VIEW_PUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDIF
Program Name: SAPLSDIF
Main Program: SAPLSDIF
Appliation area: S
Release date: 18-May-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DDIF_VIEW_PUT 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 'DDIF_VIEW_PUT'"DD: Interface for writing a view in the ABAP Dictionary
  EXPORTING
   NAME =  "Name of the view to be written
*  DD25V_WA = ' ' "View header
*  DD09L_WA = ' ' "Technical settings of the view

TABLES
*  DD26V_TAB =  "Basis tables of the view
*  DD27P_TAB =  "View fields
*  DD28J_TAB =  "Join conditions of the view
*  DD28V_TAB =  "Selection conditions of the view

EXCEPTIONS
   VIEW_NOT_FOUND = 1    NAME_INCONSISTENT = 2    VIEW_INCONSISTENT = 3    PUT_FAILURE = 4    PUT_REFUSED = 5 

.

IMPORTING Parameters details for DDIF_VIEW_PUT

NAME - Name of the view to be written

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

DD25V_WA - View header

Data type: DD25V
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

DD09L_WA - Technical settings of the view

Data type: DD09V
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DDIF_VIEW_PUT

DD26V_TAB - Basis tables of the view

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

DD27P_TAB - View fields

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

DD28J_TAB - Join conditions of the view

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

DD28V_TAB - Selection conditions of the view

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

EXCEPTIONS details

VIEW_NOT_FOUND - Header of the view could not be found

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

NAME_INCONSISTENT - Name in Sources Inconsistent with NAME

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

VIEW_INCONSISTENT - Inconsistent Sources

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

PUT_FAILURE - Write Error (ROLLBACK Recommended)

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

PUT_REFUSED - Write not Allowed

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

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

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