SAP SIPT_READ_SIPT_TABLE_WS Function Module for To update change/delete status
SIPT_READ_SIPT_TABLE_WS is a standard sipt read sipt table ws SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for To update change/delete status 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 sipt read sipt table ws FM, simply by entering the name SIPT_READ_SIPT_TABLE_WS into the relevant SAP transaction such as SE37 or SE38.
Function Group: MSPT_OIG
Program Name: SAPLMSPT_OIG
Main Program: SAPLMSPT_OIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SIPT_READ_SIPT_TABLE_WS 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 'SIPT_READ_SIPT_TABLE_WS'"To update change/delete status.
EXPORTING
* I_STATUS = "TD Shipment Status (Functional)
I_OIGS = "Internal Table for Shipment
EXCEPTIONS
DOCUMENT_ALREADY_SIGNED = 1
IMPORTING Parameters details for SIPT_READ_SIPT_TABLE_WS
I_STATUS - TD Shipment Status (Functional)
Data type: OIG_SSTSFOptional: Yes
Call by Reference: Yes
I_OIGS - Internal Table for Shipment
Data type: ROIGSOptional: No
Call by Reference: Yes
EXCEPTIONS details
DOCUMENT_ALREADY_SIGNED - Document Already signed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SIPT_READ_SIPT_TABLE_WS 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_i_status | TYPE OIG_SSTSF, " | |||
| lv_document_already_signed | TYPE OIG_SSTSF, " | |||
| lv_i_oigs | TYPE ROIGS. " |
|   CALL FUNCTION 'SIPT_READ_SIPT_TABLE_WS' "To update change/delete status |
| EXPORTING | ||
| I_STATUS | = lv_i_status | |
| I_OIGS | = lv_i_oigs | |
| EXCEPTIONS | ||
| DOCUMENT_ALREADY_SIGNED = 1 | ||
| . " SIPT_READ_SIPT_TABLE_WS | ||
ABAP code using 7.40 inline data declarations to call FM SIPT_READ_SIPT_TABLE_WS
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