COMMIT BAPI Problems

hi we have implemented VC on Ep6.0 SP2 pacth 27.
when we try to create a model using BAPI_BANK_CREATE and BAPI_TRANSACTION_COMMIT with input forms for BANK_CTRY and BANK_KEY and also an input form for BANK ADDRESS the following is the problem we face.
after running the preview in runtime when we enter all the details in both forms and click submit only the BANK_CTRY and BANK_KEY is being written into R/3 i am getting no errors or messages after i click submit.
is there something wrong with the design or is it an issue with VC?
thanks

Hi Rahul,
When you use more than one input form to a BAPI, you should change the action name on the connecting line between the input forms and the BAPI to *submit.
You can also commit the work automatically by checking the "requires commit" property of BAPI_BANK_CREATE.
Regards,
Lisi

Similar Messages

Comm API problems RS232 SerialDemo

Hello,
before you ask: yes, i have read a lot of postings concerning this topic.
However, my problem is different than the common Comm API problems.
Win2000, JDK 1.5.2, Comm API 2.0.
The SerialDemo compiles (wow), shows the correct COM Ports (1) (this has been a major problem in a lot of postings), and works without exceptions. Great, but i dont get any serialEvent when i send something from my device on COM1 (a balance).
I know the RS232 parameters (1200,7 data bits, 1 stop bit, parity odd), and i connected this device without problems to a Delphi application.
Cable is the same and the correct one. The device sends with CRLF (ASCII 13 and 10) at the end of each string.
I tried SimpleRead.java too, but here the same: no serialEvent has been triggered when the device sends its data.
Any ideas?
Oliver

Hi
sorry, it does work now :)
It was the device itself which was causing the problem.
But i really wasnt expecting this, because the day before the device (a balance) worked without any problems. Its quite funny that the balance stopped working just the day i started with the Java communication :)
thanks
Oliver

Commit bapi

hi gurus,
the other day i had an interview question
what would happen if you do not commit a bapi.
i guessed somthing but i was not sure about it.
what could be the correct answer.

Hi,
see for suppose u have done some changes to the database table by using BAPI i mean to say u have inserted some data by using this data transfer tchniqnic i.e. BAPI if u dont commit bapi tht changes will not affeted in the database table in common words it is same like saving the data thts it
plzz reward if usefull...
if u have any further quiries my mail id [email protected]
plzzz reward if usefull.
right now i am avaliable on chat if u have any further quiries u can contact me
thanks and regards

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
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_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]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_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Regards
Prabhu

Bapi Problem

REPORT zbapi_create_po                         .
*DATA DECLARATION
CONSTANTS : c_x VALUE 'X'.
*Structures to hold PO header data
DATA : header LIKE bapimepoheader   ,
       headerx LIKE bapimepoheaderx .
*Internal Tables to hold PO ITEM DATA
DATA : item   LIKE bapimepoitem OCCURS 0 WITH HEADER LINE,
       itemx LIKE bapimepoitemx OCCURS 0 WITH HEADER LINE,
*Internal table to hold messages from BAPI call
       return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
DATA : w_header(40) VALUE 'PO Header'.
DATA : ws_langu LIKE sy-langu.
*text-001 = 'PO Header' - define as text element
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS : company LIKE header-comp_code DEFAULT '1000'      ,
             doctyp LIKE header-doc_type   DEFAULT 'NB'        ,
             cdate   LIKE header-creat_date DEFAULT sy-datum    ,
             vendor LIKE header-vendor     DEFAULT '1005',
             pur_org LIKE header-purch_org DEFAULT '1000'      ,
             pur_grp LIKE header-pur_group DEFAULT '026'       .
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
PARAMETERS : item_num LIKE item-po_item DEFAULT '00010',
             material LIKE item-material DEFAULT 'DPC1017'   ,
             plant    LIKE item-plant    DEFAULT '1200' ,
             quantity LIKE item-quantity DEFAULT 100.
SELECTION-SCREEN END OF BLOCK b2.
START-OF-SELECTION.
*DATA POPULATION
ws_langu = sy-langu.   "Language variable
*POPULATE HEADER DATA FOR PO
header-comp_code = company    .
header-doc_type   = doctyp     .
header-creat_date = cdate      .
header-vendor     = vendor     .
header-langu      = ws_langu   .
header-purch_org = pur_org    .
header-pur_group = pur_grp    .
*POPULATE HEADER FLAG.
headerx-comp_code = c_x.
headerx-doc_type   = c_x.
headerx-creat_date = c_x.
headerx-vendor     = c_x.
headerx-langu      = c_x.
headerx-purch_org = c_x.
headerx-pur_group = c_x.
headerx-doc_date   = c_x.
*POPULATE ITEM DATA.
item-po_item = item_num.
item-material = material.
item-plant    = plant.
item-quantity = quantity.
APPEND item.
*POPULATE ITEM FLAG TABLE
itemx-po_item    = item_num.
itemx-material   = c_x.
itemx-plant      = c_x .
itemx-stge_loc   = c_x .
itemx-quantity   = c_x .
itemx-tax_code   = c_x .
itemx-item_cat   = c_x .
itemx-acctasscat = c_x .
APPEND itemx.
*BAPI CALL
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = header
    poheaderx                    = headerx
POADDRVENDOR                 =
TESTRUN                      =
IMPORTING
EXPPURCHASEORDER             =
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
TABLES
   return                       = return
   poitem                       = item
   poitemx                      = itemx.
*Confirm the document creation by calling database COMMIT
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   wait          = 'X'
IMPORTING
RETURN        =
END-OF-SELECTION.
*Output the messages returned from BAPI call
LOOP AT return.
WRITE / return-message.
ENDLOOP.
I am getting this message, can u give me any ideas, where is the problem in code ?
<b>Creation of PO unsuccessful
PO Header data Still faulty
Purchase Order date is in the past
For the K4 fiscal year variant, no peroid is defined for 00.00.0000</b>
points for sure
Thanks in Advance
Vijaya

Try by passign doc_date.
header-pur_group = sy-datum.

PO BAPI Problem in condition types

Hi,
I am facing a strange problem in creation of PO through "BAPI_PO_CREATE1".
In the Item condition internal table, I am passing the condition types.
The PO is getting created successfully.
Eg. I pass conditions and their values as follows:
PB00 : 1000
ZB00 : 1000
FRB1 : 1000
The PO is created successfully and we can check the prices updated properly.
Now,
When I create a second PO with the same values, the prices are taken from the last PO and the prices from
my code(which are passed through BAPI) are added to the last value.
If I run the program with the same values as above, the PO is created with the values 2000.
Third time it is 3000 and so.
The value from the last PO is coming into the new PO.
Please advise me if anything missing.
My code is below::
================
*& Report ZTEST_PO
REPORT ZTEST_PO.
data : HEADER like BAPIMEPOHEADER .
data : HEADERX like BAPIMEPOHEADERX .
data : POITEM like BAPIMEPOITEM occurs 0 with header line.
data : POITEMX like BAPIMEPOITEMX occurs 0 with header line.
data : POSCHEDULE like BAPIMEPOSCHEDULE occurs 0 with header line.
data : POSCHEDULEX like BAPIMEPOSCHEDULX occurs 0 with header line.
DATA : RET LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA : ret1 like bapiret2.
Data PO like BAPIMEPOHEADER-PO_NUMBER.
data : pocond like BAPIMEPOCOND occurs 0 with header line.
data : pocondx like BAPIMEPOCONDX occurs 0 with header line.
*pocond-CONDITION_NO = '00000'.
pocond-itm_number = '000010'.
pocond-COND_ST_NO = '001'                                   .
*pocond-COND_COUNT = '1'.
pocond-COND_TYPE = 'PB00'.
pocond-COND_value = '500'.
pocond-CURRENCY = 'EUR'.
pocond-CURRENCY_ISO = 'EUR'.
pocond-CHANGE_ID = 'I'.
APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '10'                                   .
*pocond-COND_COUNT = '2'.
*pocond-COND_TYPE = 'PBXX'.
*pocond-COND_value = '555'.
*pocond-CURRENCY = 'EUR'.
*pocond-CURRENCY_ISO = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '20'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'ZB00'.
*pocond-COND_value = '666'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '30'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'FRB1'.
*pocond-COND_value = '777'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
*pocondx-CONDITION_NO = '00000'.
POCONDX-ITM_NUMBER = '000010'.
POCONDX-COND_ST_NO = '000'.
*POCONDX-CONDITION_NOX = 'X'.
*POCONDX-COND_ST_NOX = 'X'.
POCONDX-ITM_NUMBERX = 'X'.
*POCONDX-COND_COUNT = 'X'.
POCONDX-COND_TYPE = 'X'.
POCONDX-COND_value = 'X'.
pocondX-CURRENCY = 'X'.
*pocondX-CURRENCY_ISO = 'X'.
pocondX-CHANGE_ID = 'X'.
APPEND POCONDX.
HEADER-COMP_CODE = 'TF01'.
HEADER-DOC_TYPE = 'DMPO'.
HEADER-VENDOR = '0000000317'.
HEADER-LANGU = 'EN'.
HEADER-PURCH_ORG = '1001'.
HEADER-PUR_GROUP = '110'.
HEADER-CURRENCY = 'EUR'.
HEADER-DOC_DATE = '22.10.2007'.
HEADER-REF_1 = '999999999999'.
HEADERX-VENDOR = 'X'.
HEADERX-PURCH_ORG = 'X'.
HEADERX-PUR_GROUP = 'X'.
HEADERX-REF_1 = 'X'.
POITEM-PO_ITEM = '00010'.
POITEM-MATERIAL = '00042199730L'.
POITEM-PLANT = '1000'.
POITEM-STGE_LOC = '1030'.
POITEM-MATL_GROUP = '01'.
POITEM-QUANTITY = '10'.
POITEM-PRICE_UNIT = 500.
poitem-calctype = 'C'.
append POITEM.
POITEMX-PO_ITEM = '00010'.
POITEMX-MATERIAL = 'X'.
POITEMX-PLANT = 'X'.
POITEMX-QUANTITY = 'X'.
POITEMX-PRICE_UNIT = 'X'.
append POITEMX.
POSCHEDULE-PO_ITEM = '00010'.
POSCHEDULE-DELIVERY_DATE = '30.10.2007'.
append POSCHEDULE.
POSCHEDULEX-PO_ITEM = '00010'.
POSCHEDULEX-PO_ITEMX = 'X'.
POSCHEDULEX-DELIVERY_DATE = 'X'.
append POSCHEDULEX.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = HEADER
    POHEADERX                    = HEADERX
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
IMPORTING
   EXPPURCHASEORDER             = PO
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = RET
   POITEM                       = POITEM
   POITEMX                      = POITEMX
POADDRDELIVERY               =
   POSCHEDULE                   = POSCHEDULE
   POSCHEDULEX                  = POSCHEDULEX
POACCOUNT                    =
POACCOUNTPROFITSEGMENT       =
POACCOUNTX                   =
   POCONDHEADER                 = POCOND
   POCONDHEADERX                = POCONDX
    POCOND                       = POCOND
    POCONDX                      = POCONDX
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
POCOMPONENTS                 =
POCOMPONENTSX                =
POSHIPPING                   =
POSHIPPINGX                  =
POSHIPPINGEXP                =
NFMETALLITMS                 =
if RET-type NE 'E'.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          WAIT   = 'X'
        IMPORTING
          RETURN = ret1.
write : ' PO Created : ', PO   .
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
        IMPORTING
          RETURN = ret1.
    ENDIF.
================

Any input??

RFC & BAPI problem in SUP 2.0

Hi,
I have been using the Standard BAPI's & RFCs for my app. However i am getting the errors for all of them while actually using in workflow app.
1] Invalid Templet for BAPI.
2] java.io.Exception:JASON:character not standard date time type
3] ____BAPI Return is not a standard DateTime type
But i can see the preview of all successfully. Do we need some kind of special requirement fo BAPI & RFC's to work in SUP ?
I am using MBS & simple workflow app concept to design. I have also searched the SDN for any SUP 2.0 & SAP BAPI example. I found My Flights but that was too old in previous 1.5.2 i think so which is of no use.
Your help highly appreciated
BR
Yogesh

Hi,
That's the first thing i checked the version, I have the latest JCO & JAR files being used. So there is no version conflict in Backend EIS & the front UI.
I am on digging out the infinitesimal log entries in the server to fetch the exact reason behind the problem.
I would like to know if you have ever imported the BAPI or RFC would you normally get conflicts with SAP returning the NULL or NaN values from backend.
Because I know Sybase Messaging Client can not handle the NaN & NULL values thats an offcial confirmation from Sybase for RESTful WS i got.
So may be its same but i am not sure I must or someone who has encounter these errors should confirm this.
Best Regards
Yogesh

File to BAPI problem

Hi,
We are sending a file using sender file adapter through PI into SAP system BAPI with receiver RFC adapter.
The input file is received in XI and we don't see any mapping done, but message mapping displaying as succefully delivered to SAP system.
We are using asynch call, no BPM involved. Its just File to RFC.
Any help appreciated.
Thanks.

Hi,
Do you make a commit after BAPI call.
There is a parameter in adapter which has to be set.
From documentation:
<i>"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."</i>
Regards,
Wojciech
Message was edited by: Wojciech Gasiorowski

COMM API problem

Hello there
I am hoping you can help me with following. I am trying to transfer files from one computer
to another using a serial port and hence I am using the communications api. I have gotten so
many errors on the problem. I have followed the information for installing the api but I
still get errors. It will let me compile a file but when I try to run it it give me the
following error
NoClassDeffounder found
What my lecturer did was opened up the jar file and put them into a separate folder. We then
put them into the bin directory in the jdk.
Everywhere in the code where it was calling a class,constant belong to the api we did the
following
comm.CommPortIdentifier.getPortIdentifiers();
In the above line comm is the folder with the class files
When we try to tun it now it executes.But it still cannot find any ports whatsoever
Please can anyone at all help. I am stuck on this problem for over a month and is slowing me down
Thanks

No the code has not come from my tutor
I've had 2 experts trying to help me and they dont
know what the problem is
I have tried the SerialDemo
I still get the same result
Any other ideasIf you have followed these instructions to the letter, which I doubt, then you probably need to re-install Windows.
If they haven't fixed this relatively simple problem they are not experts. Consultants perhaps, but not experts.

Bapi problem - again

Sorry to all of you with probably the same problem but i can't find solution.
Anyway i'm trying to write simple WD which will make in target system user.
I'm using BAPI_CREATE_USER FM.
I did everything like in ohter examples of consuming transaction FM (BAPi).
Anyway will post some code so maybe you will finde some bugs.
I made model with my bapi and bapi_transaction_commit of course.
in wdDoInit of custom controler i wrote:
    Bapi_User_Create_Input input = new Bapi_User_Create_Input();
     wdContext.nodeBAPI_USER_CREATE_INPUT().bind(input);
     input.setPassword(new Bapipwd());
     input.setAddress(new Bapiaddr3());
     input.setUsername("");
        Bapi_Transaction_Commit_Input inputTrans = new Bapi_Transaction_Commit_Input();
        wdContext.nodeBAPI_TRANSACTION_COMMIT().bind(inputTrans);
     inputTrans.setWait(true);
i wrote 2 methods for both bapi
1st.
    try{
         wdContext.currentBAPI_USER_CREATE_INPUTElement().modelObject().execute();
          wdContext.nodeOutput().invalidate();
    catch (Exception ex){
          ex.printStackTrace();
2nd
     try {
          wdContext.currentBAPI_TRANSACTION_COMMITElement().modelObject().execute();
          wdContext.nodeOutput().invalidate();
     } catch (Exception ex){
          ex.printStackTrace();
View contains 4 input fields for user name, name, last name and password.
All of them are binded to the context.
Button create user triger code:
    try{
          wdThis.wdGetUserCreateCustController().executeBAPI_USER_CREATE_INPUT();
    catch(Exception ex){
          wdComponentAPI.getMessageManager().reportWarning(ex.toString());
    wdThis.wdGetUserCreateCustController().executeBAPI_COMMIT();
What i'm doing wrong?
It dosent efect target system.
It dosen't even start fm because i try to debug it.
PS. I'm new to WD so sorry for some stupid things.

Hi,
1.first check whether the BAPi is working correctly with same values which u have set it in ur web dynpro application.
2. Check whether any exception is thrown: after executing the model use message manager to report exception.
wdComponentAPI.getmessageManager().reportException(ex);
or u can find the error logs in the NWA . login to NWA --> Problem management --> logs and Tracess --> log Viewer.
Thanks and Regards

Web Service Commit (BAPI inside out)

Hi all,
I want to use update BAPI through web service which made by Web Service Wizard.
I know we usually have to use BAPI_TRANSACTION_COMMIT to commit.
Can I call single web service with commit?
I found optional configrations in Service Definision (TR- SE80).
"Configration" Tab=>"Operation Profile".
commit hundling
tranaction hudling
It seems we can commit without BAPI_TRANSACTION_COMMIT.
I tried several options but it didn't work.
And I could find any document in help.sap.com and SDN like
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
Requirement
1) We want to use BAPI without rapping.
2) We want to use Web Service Wizard for BAPI/RFC web service generation.
Environment
ERP6.0 NW7.0(SP18)
Regards,
Teru

Teru,
When the web service is made for the BAPI to update, through the wizard,
1) the endpoint should be selected as BAPI after giving the service name and short text
2) Next scree, choose the application and the BAPI you need for update
3) On the next screen, you have the option to add BAPI commit function to the existing list of methods. There is a pushbutoon which appears at the bottom of the table - BAPI Commit/Rollback
So, the we service will have the BAPI commit included along with the update BAPI. So you need to invoke only one webservice from your end.
Hope this helps!!
Regards
Deepthi

SAVE / COMMIT further problems

I am using JDeveloper 3.1 to create JSP applications using the wizard for business components for JSP application.
I want to amend the generated application in the following ways :
1) On pressing the SAVE button, a COMMIT is automatically performed. Or the Save and Commit to occur together.
2) Once the data is committed I want to stay on the record I have commited.
To resolve the issues above I found the solution of setting the Module properties file parameter to IsStateLessRuntime=true from IsStateLessRuntime=false.
This did save and commit together but caused the following problems.
a) On inserting a record, I still did not get back to the inserted record on Save (On Editing a record it was fine).
b) The application was much slower
c) When I tried to insert a child record, on Save, I got the error message :
JBO-27021 : Failed to load CustomDayum value at index 1 with java object of type oracle.jbo.domain.Number due to java.sql.SQLException. Exhausted ResultSet
Anyone have any ideas ?
Many Thanks,
Ketan
null

In the Oracle Portal Version: 3.0.9.8.0 it's solved.
Greet

Maintainence order bapi problem - to get time of MO creation

Hi ,
I am using
BAPI_ALM_ORDERHEAD_GET_LIST to get maintainence orders from ECC
It is giving me details like who created the order and when.
I also need to find out at what time the order was created.
But the return has 9 output time data and i am not able to understand which of these denote which time field returns the MO order creation time
I also tried
BAPI_ALM_ORDER_GET which gives back the details of any MO but
again i face d the same problem.
Can anyone help me to find the field which stores
the time at which MO is created.?
Also if possible can one please explain -
what do all the various time fields denote?
Thanks and Regards
Points assured for help.

I think it is ACTUAL_START_TIME field.
But anyways after executing the BAPI, You will have all the Order details in the return parameter.
Go to AUFK table give one order number to AUFNR. And check the entry date and map the value to the return parameters in the BAPI

COMM Api problems to send a CR (13 or ^M) character.

I am trying to get familiar with the COMM API, I use the examples in the package like "BlackBox", or "SerialDemo".
They work fine, but I realized there is no way to send an "enter" to my router I am trying for testing the COM.
With any other term program on my COM1 I have no problems, both with standard ASCII characters, and with any control character (0-32), thus including "enter" (CR, 13, ^M are equivalents as far as I know).

When trying to send ASCII characters, make sure that you don't send a String, as Java strings are Unicode characters consisting of two bytes. Standard ASCII uses the bottom 7-bits of a byte. The send an Enter or Return chararcter, use the primative type: char
char myEnterChar = '\r';Cheers,
- David

BAPI Problems accessing tables

Dear Experts,
I'm trying to make a SAP Java Connector. My problem is that, when they are called by Java, BAPI functions don't run in the same manner as in SAP testing mode .
I tested two BAPI functions called through my connector and I saw with the debbuger that BAPI functions don't execute the select and loop at with a WHERE clause when they are called by Java, therefore they throw errors. But in the SAP testing mode functions work just fine.
I'm new to SAP and I don't know why this happens. Would you like to explain to me how to fix this problem?
Thank you very much.

Hi,
You do not need super_admin rights.
Ask your security admin to assign you SAP_JAVA_NWADMIN_LOCAL_READONLY, and if your server is on a cluster SAP_JAVA_NWADMIN_CENTRAL_READONLY roles in the portal.
This will alow you to inspect the logs.
Be aware that not all ABAP types are not supported from JAVA so your input parameters may need to be type cast and handled internally in ABAP. Also consider handling of codesets (unicode/non-unicode ie. US/NUS system types also raise compatibility issues).
Here is some useful info concerning BAPI's that may benefit you:
waht is bapi and how to creating the bapi
difference between a BAPI and function module
Have you set an external breakpoint to see what is being triggered remotely for your BAPI? In SE37 --> Utilities --> External Breakpoints --> Set Breakpoints. This will allow you to run and debug from the system invoking the call remotely.
You can also turn tracing on for the iView or use httptrace to track issues.
See below excerpt from SAP Doco relating to US/NUS:
The Remote Function Call (RFC) interface has also changed as part of the conversion to Unicode. The following remarks give a very brief outline of the general guidelines.
So that the RFC works in both USs and NUSs, an additional attribute has been added to the destination. This attribute specifies whether the RFC is to run in a US or a NUS. If an ABAP program uses function modules that change the RFC destination, this new attribute must be filled using another required parameter.
When text data is transferred in an RFC, the following new exceptions may occur:
A text cannot be converted from the source code page to the target code page because the corresponding character in the target code page is not available.
The field in the target system is shorter than the field in the source system. This may occur if data from a US is transferred to a multibyte system.
In principle, you can assume that text data has a different length in the sending system than in the receiving system. For this reason, we recommend that you use strings wherever possible. That is, you should try to avoid specifying the length of text data. You can, however, send binary data whose length is specified, without any problems.

COMMIT BAPI Problems

Similar Messages

Maybe you are looking for