Error Calling BAPI

We are getting below error while calling BAPI - Z_AW_READ_TEXT
(12.1) 04-22-10 06:04:47 (E) (4534318:6426) R3C-150412: |Dataflow DF_EXTRACT_STXL|Transform Query_Function8
R/3 CallReceive error <Function BAPI_TRANSACTION_COMMIT:User BOBAPI has no RFC authorization for function group BAPT.. User
BOBAPI has no RFC authorization for function group BAPT.>.
Any Ideas?
Thanks

Please ask the SAP basis team to set up a trace when you run this job.
I would probably expect there is some authorization group/role that needs to be added to your id.
Please let me know if that resolves the issue or has been already resolved

Similar Messages

How to add error message to return structure of calling BAPI from a BADI

i have a bapi where a badi is triggered.this badi method has just importing and changing parameters.is there any way with which i can add error message to the return structure of calling bapi.please reply at the earliest.High points can be expected.

thanks got it

Error in BAPI call using webdynpro

hi ,
am new to this webdynpro abap..so i was trying out sample tutorials from sdn..when i trigger a button click event in order to call bapi function..the error has be raisen..so give me a solution for this..kindly chk out this link..i was trying for this application..i did exactly as mentioned in this tutorial..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/00545e6d-0679-2910-acab-8073ce9a1659?rid=/webcontent/uuid/fed073e5-0901-0010-4eb4-c9882aac7b11 [original link is broken]
in this second tutorial..bapi usage
error :
The following error text was processed in the system NSP : RFC Exception COMMUNICATION_FAILURE with Message RFC destination bapi Fm does not exist. Occurred
The error occurred on the application server w2gzmbks01_NSP_00 and in the work process 0 .
The termination type was: RABAX_STATE

Hi Anuj,
I ve a similar kind of issue at my end. I am trying to call BAPI_DOCUMENT_CREATE2 from a Webdynpro application(A2C/000) and using commit work. A new doc_number is very much created, even commit work returns no error.
But surprisingly i dont see this new record in the same destination (A2C/000).
this BAPI is already remote enabled (SE37)

Calling Bapi through BADI gives data statement error

Dear Experts,
I am trying to call BAPI through BADI ME_PROCESS_REQ_CUST --> process_item.
I get an error stating that "The addition OCCURS no longer supported in OO objects"
If, I remove OCCURS statement I get an error stating that "Tables with headers are no longer supported in OO context" for the following data statement.
Appreciate, if you could provide possible solution to overcome the problem.
Regards
Kumar
BAPI code is as follows.
DATA: LV_TABIX LIKE SY-TABIX,
LT_WMDVSX LIKE BAPIWMDVS OCCURS 0 WITH HEADER LINE,
LT_WMDVEX LIKE BAPIWMDVE OCCURS 0 WITH HEADER LINE.
LV_TABIX = SY-TABIX.
CLEAR: LT_WMDVSX, LT_WMDVEX.
REFRESH: LT_WMDVSX, LT_WMDVEX.
Fill communication table
LT_WMDVSX-REQ_DATE = ET_PROCUREMENT_ITEM-DELIV_DATE.
LT_WMDVSX-REQ_QTY = ET_PROCUREMENT_ITEM-QUANTITY.
APPEND LT_WMDVSX.
Availability check with check rule '03'
CALL FUNCTION 'BAPI_MATERIAL_AVAILABILITY'
EXPORTING
PLANT = ET_PROCUREMENT_ITEM-PLANT
MATERIAL = ET_PROCUREMENT_ITEM-MATERIAL
UNIT = ET_PROCUREMENT_ITEM-UNIT
CHECK_RULE = '03'
TABLES
WMDVSX = LT_WMDVSX
WMDVEX = LT_WMDVEX
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC EQ 0.
READ TABLE LT_WMDVEX WITH KEY
COM_DATE = ET_PROCUREMENT_ITEM-DELIV_DATE.
IF SY-SUBRC EQ 0.
ET_PROCUREMENT_ITEM-AVAIL_QTY = LT_WMDVEX-COM_QTY.
ENDIF.
ENDIF.

Hi,
Occurs is no more supported by SAP ( is an obsolete statement )
Instead of following code
DATA: LV_TABIX LIKE SY-TABIX,
LT_WMDVSX LIKE BAPIWMDVS OCCURS 0 WITH HEADER LINE,
LT_WMDVEX LIKE BAPIWMDVE OCCURS 0 WITH HEADER LINE.
you can use
data: LT_WMDVSX type standard table of BAPIWMDVS,
 LT_WMDVEX type standrad table of BAPIWMDVE,
 LS_WMDVSX like line of LT_WMDVSX , "( work area )
 LS_WMDVEX like line of LT_WMDVEX. "(work area)
use workarea to get the data and then append the records from workarea to Internal tables
Reward points if usefull
Regards,
Mohan

Performance issue calling bapi po create in test mode to get error messages

Hi,
We have a report which displays in alv the purchase orders that got created in SAP, but either got blocked due to not meeting PO Release Strategy tolerances or have failed output messages .We are displaying the failed messages too.
We are looping the internal table of eban(purchase requisition) and calling bapi po create in test mode to get failed messages.
Now we are facing performance issue in production.What can be the other effecient way to get the error messages without effecting performance.
Regards,
Suvarna

Hi Suvarna,
so you need to reduce the number of PO-simulations.
- Likely you checked already, that all EBAN-entries should already be converted into POs. If there would be a large number of "new" EBAN-entries, they don't need to be simulated.
- If it's a temporary problem: give aid to correct the problems (maintain prices or whatever the error-reasons are) Then the amount of not-converted purchase requisitions (PR) should drop, too
- If it's likely, that your volume of open PR will stay high: create a Z-Table with key of EBAN and a counter, simulate (once a day) PO conversions and store the results in the Z-table. In your report you can use the results... if they are "new enough". From time to time new simulations should be done, missing master data might be available.
Maybe users should be allowed to start this 2nd report manually (in background), too -> then they can update the messages after some data corrections themself, without waiting for the result (just check later in online report and do something different in between).
And you might need to explain, PO simulation takes as long as PO creation... there is no easy or fast way around this.
Best regards,
Christian

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
 MATNR LIKE MARA-MATNR,
 MBRSH LIKE MARA-MBRSH, "Industry Sector
 MTART LIKE MARA-MTART, "Matl Type
 WERKS LIKE MARD-WERKS, "Plant
 LGORT LIKE MARD-LGORT, "Storage location
 VKORG LIKE MVKE-VKORG,
 VTWEG LIKE MVKE-VTWEG,
 MAKTX LIKE MAKT-MAKTX, "Matl Desc.
 MEINS LIKE MARA-MEINS, "Base UOM
 MATKL LIKE MARA-MATKL, "Matl.Grp
* BISMT LIKE MARA-BISMT,
 SPART LIKE MARA-SPART, "Division
* BRGEW LIKE MARA-BRGEW, "Gross weight
 GROES LIKE MARA-GROES,
 FERTH LIKE MARA-FERTH,
 ZEINR LIKE MARA-ZEINR,
 TAXKM1 LIKE MLAN-TAXM1,
 TAXKM2 LIKE MLAN-TAXM2,
 TAXKM3 LIKE MLAN-TAXM3,
 TAXKM4 LIKE MLAN-TAXM4,
 KTGRM LIKE MVKE-KTGRM,
* GEWEI LIKE MARA-GEWEI, "Weight unit
* NTGEW LIKE MARA-NTGEW, "Net weight
* KLART LIKE RMCLF-KLART,
 MTVFP LIKE MARC-MTVFP, "Availibility Check
* XGCHP LIKE MARA-XGCHP,
 XCHPF LIKE MARA-XCHPF, "Batch Management
 TRAGR LIKE MARA-TRAGR,
 LADGR TYPE MARC-LADGR,
 VPRSV LIKE MBEW-VPRSV, "Price Control
 VERPR LIKE MBEW-VERPR,
* SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
* $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
* $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
 IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
* $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
 MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
* DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = 'P_FILE'
 IMPORTING
 FILE_NAME = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*& Form data_fetch_to_xls
* text
* --> p1 text
* <-- p2 text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = 1
 I_BEGIN_ROW = 2
 I_END_COL = 25
 I_END_ROW = 2
 TABLES
 INTERN = IT_EXCEL
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
 /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
 IF NOT IT_EXCEL[] IS INITIAL.
 CLEAR LEGACY_DATA.
 REFRESH LEGACY_DATA[].
 LOOP AT IT_EXCEL.
 IT_EXCEL_DUMMY = IT_EXCEL.
 AT NEW COL.
 CASE IT_EXCEL_DUMMY-COL.
 WHEN 1.
 LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 2.
 LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 3.
 LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 4.
 LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 5.
 LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 6.
 LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 7.
 LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 8.
 LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
 WHEN 9.
 LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
 WHEN 10.
 LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
 WHEN 11.
 LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 12.
 LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
 WHEN 13.
 LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 14.
 LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
 WHEN 15.
 LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 16.
 LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 17.
 LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 18.
 LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 19.
 LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 20.
 LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 21.
 LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 22.
 LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 23.
 LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 24.
 LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 25.
 LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
 APPEND LEGACY_DATA.
 CLEAR LEGACY_DATA.
 ENDCASE.
 ENDAT.
 AT END OF ROW.
 ENDAT.
 ENDLOOP.
 ENDIF.
ENDIF.
ENDFORM. " data_fetch_to_xls
*& Form insertion
* text
* --> p1 text
* <-- p2 text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM. " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

HTTP to RFC (Calling BAPI)

Hi,
I am working on creating a Purchase Order in SAP system by calling BAPI's from XI using RFC adapter.
I defined the following in IR:
1. Created data types for mapping with BAPI request and response.
2. Created messsage types and assigned corresponding data types to the message types.
3. Created one Message Interface (Outbound/Synchronous), Output message - request message type, Input message - response message type.
4. Create request and response message mapping and one Inteface mapping (with request tab and response tab) properly assigned.
Defined the following in ID:
1. Created HTTP business system (no communication channel)
2. Created communication channel for receiving system (SAP).
3. Created receiving determination and interface determination, receiver agreement, no sender agreement.
I sent XML message (required data to create purchase order) from HTTP client but I am getting the response as Unable to determine name of mapping program, my Interface Determination has proper Inbound Interface (ZBAPI_PO_CREATE) and Mapping program (PO_I_MAP). But Why am I getting the reposnse as I said above in my HTTP client?
Appreciate your help,
Thanks and Regards,
Jagadish.

Hi Jagadish,
The error lies in Message Mapping .So please check it once again .You have mentioned your steps it seem there is problem in Message mapping..
Please look at the following Steps..
IR:
1.Import Corresponding RFC(BAPI). No need to create Interface Objects( Data type, Message type,Message Interface ) for SAP( RFC ) system..
2.Create Interface Objects For HTTP System.As you told it is synchronous.
3.Perform Two Message Mappings
(A).HTTP Request <--> RFC Req
(B).RFC Response<-->HTTP Res
4.Perform one Interface Mapping which includes Request and Response Mappings ..
5.Activate all objects..
ID : what you have done is ok..
URL: http://<hostname:port>/<path>?<query-string> Make sure your URL is correct or not for( sender HTTP )..
I think it will hepl you , if it is solved please assign points . If you have any doubt you can call me...
Thanks
N.Prasad Babu
iGATE Global Solutions Hyderabad : 98490 65377

How to create an Accounting Document by calling BAPI

Hai friends ,
please tell me how to call this BAPI and fulfill all the parameters .. Please help me , I dont know the head and tail of it ...
create an Accounting Document by calling BAPI BAPI_ACC_DOCUMENT_POST
Below is the step to fill the parameters for BAPI:
Enter company code, invoice no, invoice date, document type, header text into DOCUMENTHEADER
Enter customer, item text, company code, payment term into ACCOUNTRECEIVABLE
Enter offset account, company code, document type, item text into ACCOUNTGL
Enter currency type u201800u2019, currency, exchange rate, amount into CURRENCYAMOUNT. Please note there will be two rows in this table, one positive amount and one negative amount
Call the BAPI to create the AR document. If p_check is checked, call the BAPI only without COMMIT and then do the message processing
If p_check is initial, COMMIT the data to the database tables.
Check the RETURN table after each BAPI, if no u2018Eu2019 message type found, output the document no. Otherwise, output the error messge to the screen with the message type u2018Eu2019.
thanks in advance ...

Hi,
Check the link
http://www.sapbrainsonline.com/sapinfo/tutorial.php?artid=617
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bapi_acc_document_post-error-1973720
http://delaynomore.spaces.live.com/blog/cns!D2BFFB84EDFE4189!528.entry
http://sap4.com/wiki/index.php?title=BAPI_ACC_DOCUMENT_POST
http://www.sapfans.com
Anurodh

How can we find error in BAPI Creation?

Can any one help out in How to findout Errors in BAPI Creation and Usage?

HI,
you can findout error by declaring BAPI RETURN type structure .
for ex:"
DATA : return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
      EXPORTING
        sales_header_in     = header
        sales_header_inx    = headerx
      IMPORTING
        salesdocument_ex    = v_vbeln
      TABLES
        return              = return
        sales_items_in      = item
        sales_items_inx     = itemx
        sales_partners      = partner
        sales_conditions_in = i_conditions.
    LOOP AT return WHERE type = 'E' OR type = 'A'.
      EXIT.
    ENDLOOP.
if helpful reward points.

Can i call BAPIs with explict commit uisng xi

I have a RFC which has 3 BAPI's inside it . Each Bapi is using an explict commit. Can i call this RFC from XI .

Hi,
You have 2 options..
In the RFC Receiver Communication channel set the Advanced Property - "Commit Control for Individual BAPI Calls"
the description in help is as follows -
Commit Control for Individual BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/frameset.htm
or
you can include the commit in the RFC(if it is a custom one...)
Thanks,
Renjith

Calling BAPI from java screen

Hi All
I want to develop Order entry form in PDK, in that i need to call BAPI...namely "BAPI_SALESORDER_CREATEFROMDAT2".
Can anybody send me the sample code...
[email protected]
Thanks for ur help
Pradeep

In PDK you can import RFC modules. For that you have to create a jco connection. The code for calling an simple rfc ....
package com.satyam.callrfc;
import com.sap.mw.jco.JCO;
import com.sapportals.portal.prt.component.*;
public class rfc extends AbstractPortalComponent
     private JCO.Client jcoClient;
// proxy for rfc you already assigned...
     Insert_pgm_PortType insFunc=new Insert_pgm_PortType();
     Zinsert_Pgm_Input ip=new Zinsert_Pgm_Input();
     Zinsert_Pgm_Output op=new Zinsert_Pgm_Output();
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
    this.connect();
     insFunc.messageSpecifier.setJcoClient(jcoClient);
//setting input params
     ip.setAssociate_Id1("44");
     ip.setCourse_Objt1(2);
     ip.setQlty_Content1(5);
     ip.setSeq_Content1(2);
     ip.setTraining_Id1("22");
     try{
//calling rfc
     op=insFunc.zinsert_Pgm(ip);
     }catch(Exception e){}
//display output
          response.write(op.getMessage());
          this.disconnect();
     private void connect() {
               try {
                    jcoClient =
                         JCO.createClient("client","userid","password","EN","application_system","system_no");
                         jcoClient.connect();
               } catch (Exception e) {
                    System.out.println("Error connecting to SAP ::" + e.getMessage());
                    e.printStackTrace();
     private void disconnect() {
               try {
                    jcoClient.disconnect();
               } catch (Exception e) {
                    System.out.println(
                         "Error dis-connecting to SAP ::" + e.getMessage());
                    e.printStackTrace();
Hope this helps
gEorgE

Calling Bapi from Dot Net

Hi All,
We are Trying to upload Bapi's From Dot Net.
When we are uploading Sales Order upload i will get this error ""ERROR: Sales document type DG-1 is not defined"" ,But If i Call Again It is not giving the any error and simply its updating the SAP data base.Not only Sales Order upload but Customer Master upload also First time iam getting :"" Invalid form of address text"" This Error...After Second Exectuion I am getting Sucess Message.
Why My Bapi Call is Not Sucess for First Call and why it is Getting sucess in Second Exection When i am calling bapi from .Net
how can i solve my Problem?
Thank you,
Madhu
Edited by: madhubabu rao on Oct 24, 2008 8:20 AM

Hello,
Refer to the below Thread & Link respectively.
Re: Call BAPI WS from .NET
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/12f6d390-0201-0010-e18d-cdb4554a9e75
Thought it might give you some inputs.
Thanks and Regards,
Venkat Phani Prasad Konduri

Call bapi bapi_po_create1 will get dump message SYNTAX_ERROR

hi
when i call bapi will get SYNTAX_ERROR dump!
i have check in bapi_po_create1 report i found have add support node ( get new function:ZBAPI_PO_CHANGE--> this note will active in other function) and in this function i will found one perform process_po parameter not eq the definition FORM, so will get SYNTAX_ERROR!
in call function report BAPI_PO_CREATE1 set command :
SET EXTENDED CHECK OFF!
BUT the dump will happend again!
how to inactive SYNTAX check !
thank you very much!

Hi thomas,
Thanks.
The info you wanted is as follows:
Short text
    Exception condition "FAILURE" raised.
What happened:
   The current ABAP/4 program encountered an unexpected
situation.
Error analysis :
A RAISE statement in the program "CL_HANDLE_MANAGER_MM==========CP" raised the
exception
condition "FAILURE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Trigger Location of Runtime Error:
    Program Name                            CL_HANDLE_MANAGER_MM==========CP
    Include                                 CL_HANDLE_MANAGER_MM==========CM005
    Row                                     13
    Module type                             (METHOD)
    Module Name                             GET
Line SourceCde
    1
    2 METHOD get.
    3
    4   IF my_manager is initial.
    5     CALL METHOD get_manager.
    6   ENDIF.
    7
    8   CALL METHOD my_manager->search EXPORTING im_id = im_id
    9                                  IMPORTING ex_handle = ex_handle
   10                                  EXCEPTIONS failure = 01.
   11
   12   IF sy-subrc ne 0.
>>>>>     RAISE failure.
   14   ENDIF.
   15
   16 ENDMETHOD.

Call BAPI to Create Invoice During PGI(VL01N) via BADI

Hi,
Requirement: During PGI (VL01N), we have implemented a BADI (IF_EX_DELIVERY_PUBLISH) in method (PUBLISH_AFTER_SAVE) to call BAPI (BAPI_BILLINGDOC_CREATEMULTIPLE) to create invoice simultaneously with the PGI. In DEV box, the call BAPI is working fine (invoice is created). However in QA box there is a update termination occuring in the call BAPI, thus no invoice is being created. The thing is, how do I locate why the BAPI is terminating in QA but not in DEV? Is the BADI used correct? I have searched SAP Notes related to this termination when doing PGI in VL01N. Up to now we still do not know why in DEV is okay in QA it is not.
SAP Notes:
782447 Runtime error SAPSQL_ARRAY_INSERT_DUPREC when posting GIs
777409 Foreign trade: Update termination EXPIMP_POSTING
ST22 dump analysis:
In the source code you have the termination point in line 51
of the (Include) program "LV50EU05".
The program "SAPLV50E" was started in the update system.
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "EXPIMP_POSTING" "(FUNCTION)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLV50E "; its source code begins in line
1 of the (Include program "LV50EU05 ".
Source code:
DESCRIBE TABLE XEIKP LINES LIN.
IF LIN GT 0.
INSERT EIKP FROM TABLE XEIKP. <<< the dump is happening in this standard logic
REFRESH XEIKP.
ENDIF.
Edited by: Mawi C. Ng on Sep 2, 2009 2:24 PM

Hi,
Based on the DUMP i can say that in the below statement :
INSERT EIKP FROM TABLE XEIKP. <<< the dump is happening in this standard logic
The program is trying to insert lines which have duplicate key values check the btable XEIKP at this point and see if the records that are there do they have key fields values that already exist. You can put a break-point at that statement and check.
Regards,
Himanshu

Handling errors in BAPI

Hi frnds i m unable to know the answer for the q?
How do u handle errors in BAPI.
i.e i m using standard BAPI po creation if some errors occurs then how to handle those errors
how can we know the errors.
plz reply me back frnds...
thnks...

Hi Sanjay,
   Call BAPI like this :
data: it_retrun typa table of bapireturn.
CALL FUNCTION 'BAPI_PO_CREATE'
EXPORTING
    po_header                        =
PO_HEADER_ADD_DATA               =
HEADER_ADD_DATA_RELEVANT         =
PO_ADDRESS                       =
SKIP_ITEMS_WITH_ERROR            = 'X'
ITEM_ADD_DATA_RELEVANT           =
HEADER_TECH_FIELDS               =
IMPORTING
PURCHASEORDER                    =
tables
    po_items                         =
PO_ITEM_ADD_DATA                 =
    po_item_schedules                =
PO_ITEM_ACCOUNT_ASSIGNMENT       =
PO_ITEM_TEXT                     =
   RETURN                           = it_return
PO_LIMITS                        =
PO_CONTRACT_LIMITS               =
PO_SERVICES                      =
PO_SRV_ACCASS_VALUES             =
PO_SERVICES_TEXT                 =
PO_BUSINESS_PARTNER              =
EXTENSIONIN                      =
POADDRDELIVERY                   =
IT_RETURN will contains all message returned from BAPI. For error message you can read IT_RETURN table where type = 'E'.
Thanks
Swagatika

Error Calling BAPI

Similar Messages

Maybe you are looking for