SAP ROS_TRANSFER_STAGING_DATA Function Module for
ROS_TRANSFER_STAGING_DATA is a standard ros transfer staging data 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 ros transfer staging data FM, simply by entering the name ROS_TRANSFER_STAGING_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ROS_BUPA
Program Name: SAPLROS_BUPA
Main Program: SAPLROS_BUPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ROS_TRANSFER_STAGING_DATA 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 'ROS_TRANSFER_STAGING_DATA'".
EXPORTING
IV_PARTNER_ID = "
IMPORTING
ES_ADDRESS = "
ET_FAX = "
ET_TEL = "
ET_MAIL = "
ET_TAX = "
ES_COMPANY_ORGAN = "
ET_BANK = "
EV_CURRENCY = "
IMPORTING Parameters details for ROS_TRANSFER_STAGING_DATA
IV_PARTNER_ID -
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ROS_TRANSFER_STAGING_DATA
ES_ADDRESS -
Data type: ROS_COMPANY_SE_ADDRESS_STAGINGOptional: No
Call by Reference: Yes
ET_FAX -
Data type: BAPIADFAX_TOptional: No
Call by Reference: Yes
ET_TEL -
Data type: BAPIADTEL_TOptional: No
Call by Reference: Yes
ET_MAIL -
Data type: BAPIADSMTP_TOptional: No
Call by Reference: Yes
ET_TAX -
Data type: ROS_T_COMPANY_SE_TAX_STAGINGOptional: No
Call by Reference: Yes
ES_COMPANY_ORGAN -
Data type: ROS_S_COMPANY_SE_COMP_STAGINGOptional: No
Call by Reference: Yes
ET_BANK -
Data type: ROS_T_COMPANY_SE_BANK_STAGINGOptional: No
Call by Reference: Yes
EV_CURRENCY -
Data type: BBP_BSTWAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ROS_TRANSFER_STAGING_DATA 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_es_address | TYPE ROS_COMPANY_SE_ADDRESS_STAGING, " | |||
lv_iv_partner_id | TYPE BU_PARTNER, " | |||
lv_et_fax | TYPE BAPIADFAX_T, " | |||
lv_et_tel | TYPE BAPIADTEL_T, " | |||
lv_et_mail | TYPE BAPIADSMTP_T, " | |||
lv_et_tax | TYPE ROS_T_COMPANY_SE_TAX_STAGING, " | |||
lv_es_company_organ | TYPE ROS_S_COMPANY_SE_COMP_STAGING, " | |||
lv_et_bank | TYPE ROS_T_COMPANY_SE_BANK_STAGING, " | |||
lv_ev_currency | TYPE BBP_BSTWA. " |
  CALL FUNCTION 'ROS_TRANSFER_STAGING_DATA' " |
EXPORTING | ||
IV_PARTNER_ID | = lv_iv_partner_id | |
IMPORTING | ||
ES_ADDRESS | = lv_es_address | |
ET_FAX | = lv_et_fax | |
ET_TEL | = lv_et_tel | |
ET_MAIL | = lv_et_mail | |
ET_TAX | = lv_et_tax | |
ES_COMPANY_ORGAN | = lv_es_company_organ | |
ET_BANK | = lv_et_bank | |
EV_CURRENCY | = lv_ev_currency | |
. " ROS_TRANSFER_STAGING_DATA |
ABAP code using 7.40 inline data declarations to call FM ROS_TRANSFER_STAGING_DATA
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