SAP /SAPSLL/DATA_PROPOSAL_WRITE Function Module for

Search SAP Function Modules

/SAPSLL/DATA_PROPOSAL_WRITE is a standard /sapsll/data proposal write 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 /sapsll/data proposal write FM, simply by entering the name /SAPSLL/DATA_PROPOSAL_WRITE into the relevant SAP transaction such as SE37 or SE38.

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

Function /SAPSLL/DATA_PROPOSAL_WRITE 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 '/SAPSLL/DATA_PROPOSAL_WRITE'"
  EXPORTING
*  IV_DAT_FIELD =  "
*  IV_DATE =  "
*  IV_TIME =  "
*  IV_TIMEZONE =  "
*  IS_CONTROL =  "
*  IV_PAR_FIELD =  "
*  IV_GEN_FIELD =  "
*  IV_VALUE =  "
*  IV_GUID_CUHD =  "
*  IV_GUID_CUIT =  "
*  IV_ITVSY =  "
*  IV_LGREG =  "
*  IV_GUID_CORPAR =  "

 IMPORTING
   EV_UPDATE =  "
   EV_TEXT_UPD =  "

CHANGING
   CS_OBJ =  "

EXCEPTIONS
   INTERNAL_ERROR = 1    INVALID_FIELD_ELEMENT = 2    FIELD_ALREADY_EXISTS = 3    SEVERAL_ENTRIES_EXIST = 4    FOREIGN_KEY_ERROR = 5    PAFCT_NOT_ALLOWED = 6    TEXTID_NOT_ALLOWED = 7 

.

IMPORTING Parameters details for /SAPSLL/DATA_PROPOSAL_WRITE

IV_DAT_FIELD -

Data type: /SAPSLL/DPFDAT_S
Optional: Yes
Call by Reference: Yes

IV_DATE -

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

IV_TIME -

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

IV_TIMEZONE -

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

IS_CONTROL -

Data type: /SAPSLL/CUHD_LOAD_CONTROL_S
Optional: Yes
Call by Reference: Yes

IV_PAR_FIELD -

Data type: /SAPSLL/DPFPAR_S
Optional: Yes
Call by Reference: Yes

IV_GEN_FIELD -

Data type: /SAPSLL/DPFGEN
Optional: Yes
Call by Reference: Yes

IV_VALUE -

Data type: /SAPSLL/DPVAL
Optional: Yes
Call by Reference: Yes

IV_GUID_CUHD -

Data type: /SAPSLL/GUID_16
Optional: Yes
Call by Reference: Yes

IV_GUID_CUIT -

Data type: /SAPSLL/GUID_16
Optional: Yes
Call by Reference: Yes

IV_ITVSY -

Data type: /SAPSLL/ITVSY
Optional: Yes
Call by Reference: Yes

IV_LGREG -

Data type: /SAPSLL/LGREG
Optional: Yes
Call by Reference: Yes

IV_GUID_CORPAR -

Data type: /SAPSLL/GUID_16
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for /SAPSLL/DATA_PROPOSAL_WRITE

EV_UPDATE -

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

EV_TEXT_UPD -

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

CHANGING Parameters details for /SAPSLL/DATA_PROPOSAL_WRITE

CS_OBJ -

Data type: /SAPSLL/CUHD_OBJ_S
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INVALID_FIELD_ELEMENT -

Data type:
Optional: No
Call by Reference: Yes

FIELD_ALREADY_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

SEVERAL_ENTRIES_EXIST -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_KEY_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PAFCT_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

TEXTID_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /SAPSLL/DATA_PROPOSAL_WRITE 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 /SAPSLL/DATA_PROPOSAL_WRITE

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