SAP APO_BAPI_SBC_ATP Function Module for Generates ATP Request and Waits for Return Document When in Sync. Mode









APO_BAPI_SBC_ATP is a standard apo bapi sbc atp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generates ATP Request and Waits for Return Document When in Sync. Mode 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 atp FM, simply by entering the name APO_BAPI_SBC_ATP 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_ATP 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_ATP'"Generates ATP Request and Waits for Return Document When in Sync. Mode
  EXPORTING
   DOCTYPE =  "xCBL document type of request document
   DOCSTRING =  "xCBL request document in UTF-8 encoding
*  SENDERDOMAIN =  "domain of the sender id
*  RECEIVERDOMAIN =  "domain of the receiver id
   REQUESTMODE =  "Characterfeld der Länge 10
*  CORRELATIONID =  "xCBL-Correlation ID

 IMPORTING
   RETDOCTYPE =  "xCBL document type of response document
   RETDOCSTRING =  "xCBL response document in UTF-8 encoding
.



IMPORTING Parameters details for APO_BAPI_SBC_ATP

DOCTYPE - xCBL document type of request document

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

DOCSTRING - xCBL request document in UTF-8 encoding

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

SENDERDOMAIN - domain of the sender id

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

RECEIVERDOMAIN - domain of the receiver id

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

REQUESTMODE - Characterfeld der Länge 10

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

CORRELATIONID - xCBL-Correlation ID

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

EXPORTING Parameters details for APO_BAPI_SBC_ATP

RETDOCTYPE - xCBL document type of response document

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

RETDOCSTRING - xCBL response document in UTF-8 encoding

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

Copy and paste ABAP code example for APO_BAPI_SBC_ATP 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_doctype  TYPE CHAR255, "   
lv_retdoctype  TYPE CHAR255, "   
lv_docstring  TYPE XSTRING, "   
lv_retdocstring  TYPE XSTRING, "   
lv_senderdomain  TYPE CHAR255, "   
lv_receiverdomain  TYPE CHAR255, "   
lv_requestmode  TYPE CHAR10, "   
lv_correlationid  TYPE BAPIAPO_SBC_CORRELATIONID. "   

  CALL FUNCTION 'APO_BAPI_SBC_ATP'  "Generates ATP Request and Waits for Return Document When in Sync. Mode
    EXPORTING
         DOCTYPE = lv_doctype
         DOCSTRING = lv_docstring
         SENDERDOMAIN = lv_senderdomain
         RECEIVERDOMAIN = lv_receiverdomain
         REQUESTMODE = lv_requestmode
         CORRELATIONID = lv_correlationid
    IMPORTING
         RETDOCTYPE = lv_retdoctype
         RETDOCSTRING = lv_retdocstring
. " APO_BAPI_SBC_ATP




ABAP code using 7.40 inline data declarations to call FM APO_BAPI_SBC_ATP

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



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!