SAP UPSCP_SEND Function Module for

Search SAP Function Modules

UPSCP_SEND is a standard upscp send 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 upscp send FM, simply by entering the name UPSCP_SEND into the relevant SAP transaction such as SE37 or SE38.

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

Function UPSCP_SEND 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 'UPSCP_SEND'"
  EXPORTING
   IM_INSTID =  "ALE Distribution Packet: ID for Instantiation
*  FLG_APPL_LOG = KUPS_FALSE "Write application log
*  FLG_MSG_COLLECT = KUPS_FALSE "Collect accumulated messages
*  IM_HANDLE =  "Application Log: Log Handle
*  IT_UPSITMS_DEL =  "

 IMPORTING
   EX_DOCS_CREATED =  "Number of communication IDocs created

TABLES
*  EX_MESSAGES =  "Table Type of BAPIRET2

EXCEPTIONS
   FAILING_INSTANCE = 1    NO_AUTHORITY = 10    NO_DATA_AVAILABLE = 2    PREDEC_NOT_SENT = 3    NOTHING_TO_DO = 4    SENT_BEFORE = 5    NO_MODEL_FOUND = 6    LOG_ERROR = 7    UPSSTS_ERROR = 8    NO_CHANGE = 9 

.

IMPORTING Parameters details for UPSCP_SEND

IM_INSTID - ALE Distribution Packet: ID for Instantiation

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

FLG_APPL_LOG - Write application log

Data type: XFELD
Default: KUPS_FALSE
Optional: Yes
Call by Reference: Yes

FLG_MSG_COLLECT - Collect accumulated messages

Data type: XFELD
Default: KUPS_FALSE
Optional: Yes
Call by Reference: Yes

IM_HANDLE - Application Log: Log Handle

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

IT_UPSITMS_DEL -

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

EXPORTING Parameters details for UPSCP_SEND

EX_DOCS_CREATED - Number of communication IDocs created

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

TABLES Parameters details for UPSCP_SEND

EX_MESSAGES - Table Type of BAPIRET2

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

EXCEPTIONS details

FAILING_INSTANCE -

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

NO_AUTHORITY - No Authorization

Data type:
Optional: No
Call by Reference: Yes

NO_DATA_AVAILABLE - No packet data available

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

PREDEC_NOT_SENT - Predecessor packet not yet distributed

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

NOTHING_TO_DO - Nothing to do

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

SENT_BEFORE - Packet has already been distributed

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

NO_MODEL_FOUND - No Entry Found in Distribution Model

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

LOG_ERROR - Unspecified error in application log

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

UPSSTS_ERROR - Packet status is not allowed

Data type:
Optional: No
Call by Reference: Yes

NO_CHANGE - Packet has been opened for display only

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

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

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