SAP SBUF_PARTIAL_WRITE_STAT Function Module for









SBUF_PARTIAL_WRITE_STAT is a standard sbuf partial write stat 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 sbuf partial write stat FM, simply by entering the name SBUF_PARTIAL_WRITE_STAT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBUF
Program Name: SAPLSBUF
Main Program: SAPLSBUF
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SBUF_PARTIAL_WRITE_STAT 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 'SBUF_PARTIAL_WRITE_STAT'"
EXPORTING
* BUFF_ID = 1 "

EXCEPTIONS
C_FUNC_ERROR = 1
.



IMPORTING Parameters details for SBUF_PARTIAL_WRITE_STAT

BUFF_ID -

Data type: RSDBSTAT-SEQ_SCAN
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

C_FUNC_ERROR - Return Code from the C Kernel Occurred

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

Copy and paste ABAP code example for SBUF_PARTIAL_WRITE_STAT 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_buff_id  TYPE RSDBSTAT-SEQ_SCAN, "   1
lv_c_func_error  TYPE RSDBSTAT. "   

  CALL FUNCTION 'SBUF_PARTIAL_WRITE_STAT'  "
    EXPORTING
         BUFF_ID = lv_buff_id
    EXCEPTIONS
        C_FUNC_ERROR = 1
. " SBUF_PARTIAL_WRITE_STAT




ABAP code using 7.40 inline data declarations to call FM SBUF_PARTIAL_WRITE_STAT

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 SEQ_SCAN FROM RSDBSTAT INTO @DATA(ld_buff_id).
DATA(ld_buff_id) = 1.
 
 


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!