SAP BAPI_AR_WS_EXP_REJ_RESP_2758 Function Module for NOTRANSL: AR: BAPI For Rejection Response(Web services Export 2758)









BAPI_AR_WS_EXP_REJ_RESP_2758 is a standard bapi ar ws exp rej resp 2758 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: AR: BAPI For Rejection Response(Web services Export 2758) 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 bapi ar ws exp rej resp 2758 FM, simply by entering the name BAPI_AR_WS_EXP_REJ_RESP_2758 into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_AR_WS_EXP_REJ_RESP_2758 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 'BAPI_AR_WS_EXP_REJ_RESP_2758'"NOTRANSL: AR: BAPI For Rejection Response(Web services Export 2758)
  EXPORTING
   CUIT_COMP_CODE =  "Character Length 11
   CBTE_TIPO =  "Two digit number
   PUNTO_VTA =  "Branch
*  CBTE_NRO =  "Character field, 8 characters long
*  MONITOR_FLAG =  "Single-Character Indicator

 IMPORTING
   W_RESULT =  "AR:WS 2758 - compconsultarResult
   XML_DATA =  "Predefined Type

EXCEPTIONS
   SYSTEM_FAILURE = 1    COMMUNICATION_FAILURE = 2    RESOURCE_FAILURE = 3
.



IMPORTING Parameters details for BAPI_AR_WS_EXP_REJ_RESP_2758

CUIT_COMP_CODE - Character Length 11

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

CBTE_TIPO - Two digit number

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

PUNTO_VTA - Branch

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

CBTE_NRO - Character field, 8 characters long

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

MONITOR_FLAG - Single-Character Indicator

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

EXPORTING Parameters details for BAPI_AR_WS_EXP_REJ_RESP_2758

W_RESULT - AR:WS 2758 - compconsultarResult

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

XML_DATA - Predefined Type

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

EXCEPTIONS details

SYSTEM_FAILURE - System failure

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILURE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

RESOURCE_FAILURE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_AR_WS_EXP_REJ_RESP_2758 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_w_result  TYPE J_1A_WS_RESULTGET_2758, "   
lv_cuit_comp_code  TYPE CHAR11, "   
lv_system_failure  TYPE CHAR11, "   
lv_xml_data  TYPE STRING, "   
lv_cbte_tipo  TYPE NUMC2, "   
lv_communication_failure  TYPE NUMC2, "   
lv_punto_vta  TYPE J_1ABRNCH, "   
lv_resource_failure  TYPE J_1ABRNCH, "   
lv_cbte_nro  TYPE CHAR8, "   
lv_monitor_flag  TYPE CHAR1. "   

  CALL FUNCTION 'BAPI_AR_WS_EXP_REJ_RESP_2758'  "NOTRANSL: AR: BAPI For Rejection Response(Web services Export 2758)
    EXPORTING
         CUIT_COMP_CODE = lv_cuit_comp_code
         CBTE_TIPO = lv_cbte_tipo
         PUNTO_VTA = lv_punto_vta
         CBTE_NRO = lv_cbte_nro
         MONITOR_FLAG = lv_monitor_flag
    IMPORTING
         W_RESULT = lv_w_result
         XML_DATA = lv_xml_data
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        COMMUNICATION_FAILURE = 2
        RESOURCE_FAILURE = 3
. " BAPI_AR_WS_EXP_REJ_RESP_2758




ABAP code using 7.40 inline data declarations to call FM BAPI_AR_WS_EXP_REJ_RESP_2758

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!