SAP SO_ATTACHMENT_READ_API1 Function Module for SAPoffice: Read attachment using RFC

Search SAP Function Modules

SO_ATTACHMENT_READ_API1 is a standard so attachment read api1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPoffice: Read attachment using RFC 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 so attachment read api1 FM, simply by entering the name SO_ATTACHMENT_READ_API1 into the relevant SAP transaction such as SE37 or SE38.

Function Group: SOI1
Program Name: SAPLSOI1
Main Program: SAPLSOI1
Appliation area: S
Release date: 14-Apr-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SO_ATTACHMENT_READ_API1 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 'SO_ATTACHMENT_READ_API1'"SAPoffice: Read attachment using RFC
  EXPORTING
   ATTACHMENT_ID =  "ID of attachment to be viewed

 IMPORTING
   ATTACHMENT_DATA =  "Complete attributes of viewed attachment

TABLES
*  ATTACHMENT_HEADER =  "Header data for attachment (spec.header)
*  ATTACHMENT_CONTENT =  "Attachment contents
*  CONTENTS_HEX =  "Binary Content

EXCEPTIONS
   ATTACHMENT_NOT_EXIST = 1    OPERATION_NO_AUTHORIZATION = 2    PARAMETER_ERROR = 3    X_ERROR = 4    ENQUEUE_ERROR = 5 

.

IMPORTING Parameters details for SO_ATTACHMENT_READ_API1

ATTACHMENT_ID - ID of attachment to be viewed

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

EXPORTING Parameters details for SO_ATTACHMENT_READ_API1

ATTACHMENT_DATA - Complete attributes of viewed attachment

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

TABLES Parameters details for SO_ATTACHMENT_READ_API1

ATTACHMENT_HEADER - Header data for attachment (spec.header)

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

ATTACHMENT_CONTENT - Attachment contents

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

CONTENTS_HEX - Binary Content

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

EXCEPTIONS details

ATTACHMENT_NOT_EXIST - Specified attachment does not exist

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

OPERATION_NO_AUTHORIZATION - No authorization to view attachment

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

PARAMETER_ERROR - Invalid combination of parameter values

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

X_ERROR - Internal error or database inconsistency

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

ENQUEUE_ERROR - Required locks could not be set

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

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

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