SAP APO_BAPI_SBC_TS_REQUEST_RECEIV Function Module for Receive Time Series Request









APO_BAPI_SBC_TS_REQUEST_RECEIV is a standard apo bapi sbc ts request receiv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Receive Time Series Request 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 apo bapi sbc ts request receiv FM, simply by entering the name APO_BAPI_SBC_TS_REQUEST_RECEIV into the relevant SAP transaction such as SE37 or SE38.

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



Function APO_BAPI_SBC_TS_REQUEST_RECEIV 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 'APO_BAPI_SBC_TS_REQUEST_RECEIV'"Receive Time Series Request
EXPORTING
SENDER = "char255
RECEIVER = "char255
* DOCTYPE = 'TimeSeriesRequest' "char255
DOCSTRING = "
* REQUESTMODE = 'peer-peer' "Characterfeld der Länge 10
CORRELATIONID = "xCBL-Correlation ID

EXCEPTIONS
ROLL_BACK = 1
.



IMPORTING Parameters details for APO_BAPI_SBC_TS_REQUEST_RECEIV

SENDER - char255

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

RECEIVER - char255

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

DOCTYPE - char255

Data type: CHAR255
Default: 'TimeSeriesRequest'
Optional: No
Call by Reference: No ( called with pass by value option)

DOCSTRING -

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

REQUESTMODE - Characterfeld der Länge 10

Data type: CHAR10
Default: 'peer-peer'
Optional: No
Call by Reference: No ( called with pass by value option)

CORRELATIONID - xCBL-Correlation ID

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

EXCEPTIONS details

ROLL_BACK - Fehler desshalb zurückrollen

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for APO_BAPI_SBC_TS_REQUEST_RECEIV 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_sender  TYPE CHAR255, "   
lv_roll_back  TYPE CHAR255, "   
lv_receiver  TYPE CHAR255, "   
lv_doctype  TYPE CHAR255, "   'TimeSeriesRequest'
lv_docstring  TYPE XSTRING, "   
lv_requestmode  TYPE CHAR10, "   'peer-peer'
lv_correlationid  TYPE BAPIAPO_SBC_CORRELATIONID. "   

  CALL FUNCTION 'APO_BAPI_SBC_TS_REQUEST_RECEIV'  "Receive Time Series Request
    EXPORTING
         SENDER = lv_sender
         RECEIVER = lv_receiver
         DOCTYPE = lv_doctype
         DOCSTRING = lv_docstring
         REQUESTMODE = lv_requestmode
         CORRELATIONID = lv_correlationid
    EXCEPTIONS
        ROLL_BACK = 1
. " APO_BAPI_SBC_TS_REQUEST_RECEIV




ABAP code using 7.40 inline data declarations to call FM APO_BAPI_SBC_TS_REQUEST_RECEIV

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.

 
 
 
DATA(ld_doctype) = 'TimeSeriesRequest'.
 
 
DATA(ld_requestmode) = 'peer-peer'.
 
 


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!