No update in transaction vl33n.

Hey All,
I am working with an ASN inbound IDOC. When I test my IDOC using we19, it says IDOC passed to the application. But when I see vl33n I see no update. Please tell me what would be the possible reason.
Thanks
Disha.

Hello,
You can find the idoc number in WE02 which you generated through the WE19. From the bttom in idoc, there is status record, there you can find the inbound delivery number which is created through the inbound idoc. Then go to VL33N and check.

Similar Messages

Error while posting the Idoc 'Update error, transaction VA01'

Hi Gurus,
When an inbound Idoc for sales order is trying to post we are getting the error 'Update error, transaction VA01'.
Aslo following are the details of the error:
Update error, transaction VA01
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
Update information
Return code: 009
Text : Error during insert table FPLTC (RC= 1, Key= )
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.
Can somebody let me know what would be the cause.
Also the we are trying to post the Idoc with a Id which is having maximum Authorization.

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Call transaction 'VL33N' on click of Inbound delivery number in ALV List.

Hi,
My ALV output is having Inbound delivery number.
If user clicks on one of the Inbound delivery it has to call transaction VL33N and display the user selected document.
Code:
WHEN '&IC1'.
IF rs_selfield-fieldname = 'VBELN'.
        READ TABLE gt_final INTO wa_final INDEX rs_selfield-tabindex.
        if wa_final-vbeln is not initial.
          FREE MEMORY ID 'VL'.
          SET PARAMETER ID 'VL' FIELD WA_FINAL-VBELN.
          CALL TRANSACTION 'VL33N' AND SKIP FIRST SCREEN.
        ENDIF.
      ENDIF.
I am setting the parameter id 'VL' by passing Inbound Delivery number.After that it is calling VL33N Screen but the Inbound delivery number is blank.In debugging i can see the SAP memory for 'VL' as the selected document number.
Why VL value is not transferred to Inbound Delivery number field in VL33 Eventhough Parameter id having value.
VL (10) <0180000057>
Thanks
Bhuvana
Edited by: Pulibhuvana on Nov 22, 2010 8:20 AM

Hi,
Removed Free statement.
      IF rs_selfield-fieldname = 'VBELN'.
        READ TABLE gt_final INTO wa_final INDEX rs_selfield-tabindex.
        if wa_final-vbeln is not initial.
          SET PARAMETER ID 'VL' FIELD rs_selfield-value.
          CALL TRANSACTION 'VL33N' AND SKIP FIRST SCREEN.
        ENDIF.
      ENDIF.
In background VL is passing to VL03N Transaction instead of VL33N.
Outbound delivery and Inbound Delivery both are assigned to same paramer id.
Don't undestand if i'm calling VL33N Why the paramer value is passed to Outbound delivery transaction VL03N.
Please suggest me.
Thanks
Bhuvana

E377 Update error, transaction CO01

Hello PP Gurus,
This error appears when we create production order using the bdc "E377 Update error, transaction CO01".
What does this error mean?
and how do we solve it?
Thank you very much!

Nanz,
Can you please try manually creating an order with CO01 transaction and let us know whether it was successful?
Regards,
Prasobh

Auto Update MB1* transactions

Hi All,
I would like to Update transactions MB1A,MB1B,MB1C through Flat file.
I appreciate if any one let me know the relevent IDOc/RFC ( I got WMMBID02 Idoc from SDN )
and configurations in R3 to Update transaction.
I have configured connection between XI and R3.
regards,
Ramesh.

Hi Ramesh,
Usually we dont update the transactions directly from PI. We usually send to SAP using RFC or IDOC and from there we post it and while posting if we need to use any user exits we will use them and post it.
For your transactions you can use the idoc WMMBID02 or you can also use RFC BAPI_GOODSMVT_CREATE. You need to check all the fields required which are used to post. If you dont have all the fields then you can also create a zrfc or extend the idoc to support your requirement. or Call the RFC INBOUND_IDOC_PROCESS with IDOC_CONTROL and IDOC_DATA. The structure in the field sdata in the IDOC_DATA are e1mbxyh and e1mbxyi. So in PI it will be like File - PI - IDOC or File - PI - RFC scenario. To find any user exits are there for this transaction you can do the steps mentioned in this thread:
Userexit for extended idoc for std. idoc WMMBID02 for T.Code MB1A & MB1B
> and configurations in R3 to Update transaction.
The corresponding functional consultant will help you in detail for your client requirements. Some configuration you can see here:
http://sap.rfgen.com/docs/PR/PR%20Component%20Scrap.pdf
http://www.sapstudymaterials.com/2007/12/accounting-fico-journal-of-mm-goods_09.html
Regards,
---Satish

Update error, transaction VA21

Hi all,
when i want to save transaction Va21, i got this error update error, when i click where used list , i dunno which one program to set breakpoint. lots of list.
then i click the error message it display like this...when i go to SM13 the error details shows TD 423: CONTROL_FORM.
where and how i should solve this.. i'm really stuck.. donno how and why. Please xperts... help me...
Update error, transaction VA21
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA21.
Update information
Return code:        009
Text       :        CONTROL_FORM is invalid, OPEN_FORM is missing
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.

You can delete the output from VA21 Transaction by EXTRAS-OUTPUT-HEADER-EDIT and then try to SAVE.May it will aloow you to save.
one more suggestion Check with Table TNAPR where KSCHL = ZN00 and NACHA = ? (Check in VA21) then you can get the Program and Name of routine Just Put a break point over there and find what is the issue.
Kanagaraja L

Function modules to update ME01 transaction

Hi,
Can I get the list of Function modules to update ME01 transaction..
Thnx in advance,
Shivaa

Hi shiva,
Try this funtion module ,
ME_UPDATE_SOURCES_OF_SUPPLY Update source list
ME_UPDATE_SOURCES_OF_SUPPLY_BA Update source list records in background during generation
I hope,it will help you
<=<< Sharing Knowledge is a way to Innovative >>=>
By,
Yoga

BDC to update CAT2 transaction.one issue while updating CAT2 transaction

Good Day Friends,
i have one issue while updating CAT2 transaction,
i have enhnced 3 custom fields in CAT2 tx-code. while updating through manually the data is getting stored in CATSDB tx-code for this i have done validation in enhamcement spots ECC 6.0.
but when i am running bdc this custom field data is not updating in CATSDB table.
my dout is will BDC work for enhancement spots or not , also please suggest if you have any idea ?

Hi,
Usually I am trying to avoid BDC. So I would try to use BAPIs BAPI_CATIMESHEETMGR_INSERT and BAPI_CATIMESHEETMGR_CHANGE. Similar to other BAPIs, you can pass values for your extended fields using table EXTENSIONIN. It's described in BAPI's documentation or look for EXTENSIONIN on SDN. The principle is same for all BAPIs.
Regards

Error: (00 377) Update error, transaction FB01 in EBS

Hi,
I have uploaded electronic bank statement through jobs but some documented was posted but some document was not posted and received error message like >>>>>>>>>> Error: (00 377) Update error, transaction FB01 .
Is it possible to re upload same bank statement? or without rectify is it possible to upload next statement ?
In FEBA I could not find any error log . How to rectify the above
Your valuable input in this regards highly appreciated with high points.
Thanks in advance.
With regards,
v.k
Edited by: KRISHNAM MOORTHY on Aug 7, 2010 6:54 PM

You dont have to re-import the Bank statement. Try posting in foreground in FEBA which might show you what error you have. You might probably have mandatory fields whose values are not filled from the Bank statement.
Ravi.

Demo for updating a transaction

hi all,
can anyone plz send me the demo for how to updata a transaction ,
not standard transaction like mm01,va01,me21 some what other transaction.why iam asking for some what other transaction when ever i was attending for interview they expecting some different transaction
plz help me ,so that i will be thankful to you.some differnt transaction with steps plzzzzzzzzzzz.
thank u all.

Hi,
create a new program and copy the below code.
Note:- create a flat file (with comma seperated) with the below structure.
Flat file Example:-
Material number,oldmaterial number (don't put this header in your flat file)
13571228,oldmaterial
13571229,oldmaterial1
save this file into your local path, make sure that the path should be given in the function module "GUI_UPLOAD" example:- "D:\MM02.TXT".
test this it will work.
copy from here.
DATA : BEGIN OF it_data OCCURS 0,
data(255),
END OF it_data .
DATA : BEGIN OF it_mat OCCURS 0,
matnr LIKE rmmg1-matnr,
bismt LIKE mara-bismt,
END OF it_mat.
DATA : BEGIN OF it_error OCCURS 0,
matnr LIKE mara-matnr,
mess(255),
END OF it_error.
DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE,
v_text(200).
PERFORM upload.
LOOP AT it_data.
PERFORM pop_mat.
ENDLOOP.
LOOP AT it_mat.
PERFORM pop_bdcdata.
REFRESH it_bdcmsgcoll.
CLEAR it_bdcmsgcoll.
CALL TRANSACTION 'MM02' USING it_bdcdata
UPDATE 'S'
MODE 'A'
MESSAGES INTO it_bdcmsgcoll.
IF sy-subrc NE 0.
LOOP AT it_bdcmsgcoll WHERE msgtyp = 'E' OR
msgtyp = 'A' OR
msgtyp = 'S'.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
id = it_bdcmsgcoll-msgid
lang = sy-langu
no = it_bdcmsgcoll-msgnr
v1 = it_bdcmsgcoll-msgv1
v2 = it_bdcmsgcoll-msgv2
v3 = it_bdcmsgcoll-msgv3
v4 = it_bdcmsgcoll-msgv4
IMPORTING
msg = v_text
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2
IF sy-subrc NE 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CONCATENATE it_error-mess v_text INTO it_error-mess.
ENDLOOP.
it_error-matnr = it_mat-matnr.
APPEND it_error.
CLEAR it_error.
ENDIF.
ENDLOOP.
LOOP AT it_error.
WRITE : it_error-matnr, it_error-mess.
ENDLOOP.
FORM upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = 'D:\sreeram\MM02.TXT'
filetype = 'ASC'
TABLES
data_tab = it_data .
IF sy-subrc NE 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " UPLOAD
FORM pop_mat .
SPLIT it_data AT ',' INTO it_mat-matnr
it_mat-bismt.
APPEND it_mat.
CLEAR it_mat.
ENDFORM. " POP_BDCDATA
FORM pop_bdcdata .
REFRESH it_bdcdata.
CLEAR it_bdcdata.
PERFORM fill_screen USING 'SAPLMGMM' '0060' 'X'.
PERFORM fill_valus USING 'BDC_CURSOR'
'RMMG1-MATNR'.
PERFORM fill_valus USING 'RMMG1-MATNR'
it_mat-matnr.
PERFORM fill_valus USING 'BDC_OKCODE'
'=AUSW'.
PERFORM fill_screen USING 'SAPLMGMM' '0070' 'X'.
PERFORM fill_valus USING 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(01)'.
PERFORM fill_valus USING 'MSICHTAUSW-KZSEL(01)'
'X'.
PERFORM fill_valus USING 'BDC_OKCODE'
'=ENTR'.
PERFORM fill_screen USING 'SAPLMGMM' '4004' 'X'.
PERFORM fill_valus USING 'BDC_CURSOR'
'MARA-BISMT'.
PERFORM fill_valus USING 'MARA-BISMT'
it_mat-bismt.
PERFORM fill_valus USING 'BDC_OKCODE'
'=BU'.
ENDFORM. " POP_BDCDATA
FORM fill_screen USING p_prog
p_dynpro
p_dynbegin.
it_bdcdata-program = p_prog.
it_bdcdata-dynpro = p_dynpro.
it_bdcdata-dynbegin = p_dynbegin.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM. " FILL_SCREEN
FORM fill_valus USING p_fnam
p_fval.
it_bdcdata-fnam = p_fnam.
it_bdcdata-fval = p_fval.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM. " FILL_VALUS
End of copy
Also see this :
Here iam giving just recorded sample code.here material number is ASNFINAL.
Old material number changed is :'OLD_BSIMT'.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
'RMMG1-MATNR'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'RMMG1-MATNR'
'ASNFINAL'.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
'X'.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
'=BU'.
perform bdc_field using 'MAKT-MAKTX'
'ASN FINAL TEST MATERIAL'.
perform bdc_field using 'BDC_CURSOR'
'MARA-BISMT'.
perform bdc_field using 'MARA-MEINS'
'EA'.
perform bdc_field using 'MARA-MATKL'
'AS02'.
perform bdc_field using 'MARA-BISMT'
'OLD_BSIMT'.
perform bdc_field using 'MARA-SPART'
'10'.
perform bdc_field using 'MARA-PRDHA'
'RC2120'.
perform bdc_field using 'MARA-GEWEI'
'KG'.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Inbound idoc status 53 but nothing is updated in transaction level

Hi All
I am using we19 test tool to process routing idoc LOIROU02 (inbound processing)with some test values. After executing using standard inbound function module in R/3 4.7, I am getting a status 53 ( application document posted). This idoc is used for changing routings in PP module to allocate operations for BOM components in a master BOM material and Group. After processing, I went to routing transaction and checked but nothing is updated for operations. Do anyone knows why then the application document is successfully posted and giving status 53.
Any response is appreciated
Thanks

Hi All,
I am using inbound process code ED00 ( Display using workitem) , Identification TS30200088, with/o Ale service, Processing by task. I get the idoc in my business work place when I execute it through we19. From the business work place inbox, I got to edit idoc and End process for gettign the status 53. I am not sure why it is not updating the DB?
Thanks
Ricky

How to update Asset transactions

Hi FI Experts,
I've been updating a asset by providing values for ANLC table during asset creation. The asset summary is getting updated properly for the fiscal year. I can see them under Planned Value tab..
But Transactions is not updated.
Could anybody help, which table contains the entry for asset transactions. Can it be updated during asset creation?
Thanks & Regards,
Ravi

Hi Eli,
I don't find the BAPI FIXEDASSET_CREATEINCLVALUES in the system. Could you please provide me the correct BAPI and if possible an example on how to create a reference asset.
As I mentioned, I'm using Z Object, which is a copy of LAFA_ASSET_CREATE. I'm providing the values for ANLC using the FM AMSP_ADD_ENTRIES_TO_GLOBAL_TBS (available in LAFA_ASSET_CREATE). So the values for the asset is properly updated. I can not pass values for tables ANEK and ANEP using the same FM i.e. AMSP_ADD_ENTRIES_TO_GLOBAL_TBS so I'm using FM AMBU_APPEND_LINES_OF_ITAB_AC to update values of ANEP and ANEK. But the values for ANEP and ANEL are not getting updated. If you can suggest something here, it would be great help.
Regards,
Ravi

Dependent characteristics updation in transaction QP02

HI Friends,
Could you please help me regarding updation of dependent characteristics in the transaction QP02.
My requirement is i will give the plant and group in the first screen and i select the first entry and i will click inspection characteristics in the appl tool bar and then i will select master inspection characteristics and i have to press dependent characteristics update to update
diameter,unit of measurment.... based on material assignment. CAn i use any BAPI for this?
Please help me i will give the points.
Thanks a lot in advance.

Hi,
I think your problem is solved .
I am also working on same requirement .Please can you tell the bapi or procedure how to solve that problem .
regards
Nandan.N

Update operation transaction timing out

Hello,
I have a large data structure that needs to be updated atomically (i.e. within a transaction). I am calling the logical service via a web service map, so I presume the transaction starts when the logical service is invoked. It is receiving a transaction timeout on the server, which I suspect is set to 30 seconds at the WebLogic level by our middleware team. (See stack trace below).
The update operation SDO XML is at least 2MB.
1. Is there any way to override this transaction timeout at the service or data space level?
2. Is there any more efficient way to do this update? Sending a big wad of xml is inefficient, and I am not aware of another format supported by ODSI web services. I cannot use mediator API straight from my client to ODSI.
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
Any advice would be much appreciated.
Thanks,
Jeff
weblogic.xml.query.exceptions.XQuerySystemException: {bea-err}SYS003: Unexpected exception
     at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:96)
     at weblogic.xml.query.transaction.TransactionManager.teardownOnSuccess(TransactionManager.java:178)
     at com.bea.ld.EJBRequestHandler.handleProcessingComplete(EJBRequestHandler.java:1020)
     at com.bea.ld.EJBRequestHandler.handlePusher(EJBRequestHandler.java:979)
     at com.bea.ld.EJBRequestHandler.invokeOperation(EJBRequestHandler.java:323)
     at com.bea.ld.ServerWrapperBean.invoke(ServerWrapperBean.java:153)
     at com.bea.ld.ServerWrapperBean.invokeOperation(ServerWrapperBean.java:80)
     at com.bea.ld.ServerWrapper_s9smk0_ELOImpl.invokeOperation(ServerWrapper_s9smk0_ELOImpl.java:141)
     at com.bea.dsp.ws.RoutingHandler$PriviledgedRunner.run(RoutingHandler.java:96)
     at com.bea.dsp.ws.RoutingHandler.handleResponse(RoutingHandler.java:217)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:176)
     at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
     at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
     at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
     at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
     at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.transaction.RollbackException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
     at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1708)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:255)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
     at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:94)
     ... 30 more
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1734)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1607)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1879)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
     at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     ... 2 more

1. Is there any way to override this transaction timeout at the service or data space level?
You can set trans-timeout-seconds in the weblogic-ejb-jar.xml for your dataspace. You'll find it in <dataspaceName>dspejb.jar in <domain>/dsp/dataSpaces/<dataspaceName>request_handlers.ear. I've include a complete weblogic-ejb-jar.xml (at the end of the post) so you can see where to add it. Just copy-paste the <transaction-descriptor>...</>
the request handlers ear is created when the dataspace is deployed the first time and during a full-deploy (i.e. you don't have to go back and edit it after incremental deploys)
2a. Is there any more efficient way to do this update?
If you described it in painful detail, we might be able to think of something. You might find mutators helpful - http://download.oracle.com/docs/cd/E13167_01/aldsp/docs32/dsp32wiki/Mutators%20for%20Updates.html
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
You could write/host your own webservice on the ODSI server which would call ODSI via the java api. Your ws would expose operations to the following calls from your client
contextId = myWsStartUserTransaction()
while( moreChunks)
myWsUpdate(contextId, chunk)
myWSEndUserTransaction(contextId)
Just a heads-up, WLS has an anti-denial-of-service attack setting that rejects input messages over a certain size. I believe the default is 10MB. You can set it in the WLS console.
- Mike
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Server</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.server</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserver</local-jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>ServerTxRequired</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.serverTxRequired</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserverTxRequired</local-
jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Metadata</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.metadata</jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

[ADF BC | ADF Faces] Updating a table with values updated in transaction

Summary: A table is based on a view with a bind variable. Based on some action, I update rows in the view so that they no longer satisfy the query. How do I update the table to reflect this?
I have an ADF Faces page with a multi-select table component on it, mapped to an ADF Business Components view object. The view object has a bind variable (:Status), which is used in the query to only retrieve rows with a specific status.
The user selects rows in the table that should have their status changed, and then hits a button to perform the action. In the backing bean for the page, the button click is processed and the selected rows are updated to a different status. At this point the transaction is not committed.
Changing the status of these rows now means that they no longer match the where clause of the view object, yet they still appear in the table.
My question is, how can I update the table so that rows which don't match the where clause are removed?
This is a simplified version of the problem I am working on - this needs to work when rows that aren't in the table are being updated so that they now MATCH the where clause and rows may also be added or completely removed.

Quite an interesting little problem....
I have created a simple test case to illustrate your scenario - perhaps Steve M could comment...
My scenario:
1). create an EO based on the HR.EMPLOYEES table
2). create an updatable VO based upon the aforementioned EO. Add "COMMISSION_PCT IS NULL" to the where clause.
3). Add the VO to an app module as usual.
4). Create an ADF Faces page by dropping the VO from the data control as an ADF table. Show only first name, last name, and commission pct.
5). Add a command button to the page so I can call various code from the backing bean.
Now, when I update the commision for the first record to ".1" and press the submit button (the one in the table actions facet), the update "takes" - I assume that it's just in the EO cache at this point. The record still shows on the screen, even though it no longer meets the where clause criteria.
When I add some code to the command button (#5) to perform a commit - the record STILL shows on the screen after committing to the DB. I can make the record disappear by either (in the same backing-bean method that does the commit)
a). Re-execute the iterator after the commit
b). Call "clearVOCaches" on the application module (forces the iterator to re-execute)
I even tried programmatically adding the where clause back in (via addWhereClause) and re-executing the iterator - no go. I suspect that the only way to do this would be to post the changes to the DB (without committing them) and then re-execute the query. This, however, would be a killer from a scalability perspective.
John

No update in transaction vl33n.

Similar Messages

Maybe you are looking for