Call transaction in mode N fro transaction F-02

Hi,
The call transaction for F-02 work well in mode 'A' and it creates the FI posting. But when I execute it in mode 'N' it does not post.
Any ideas?
Thanks in advance.

Hi Abel Isaac Polo,
Welcome to SCN, as per your issue I do't thing that should happend... Can you paste wht all paramenters which you are passing to CALL Transaction statement.
Regards,
Suneel G

Similar Messages

ORA-22292: Cannot open a LOB in read-write mode without a transaction

Hi ,
somebody can help me, what is that problem.
I run the script by using the Oracle SQL developer to update the clob column.
error message is :
ORA-22292: Cannot open a LOB in read-write mode without a transaction.
Regards,
Message was edited by:
user533045

Without posting the code its difficult for anyone to figure out whats wrong with this
error.Please paste the code.
Khurram

Multiple insance of same transaction (asynchronous mode)

Hello
I created a structured service composed by:
- a master transaction executed every 10 minutes which runs several instances (30) of a slave transaction with Asynchronous mode
- a slave transaction with duration between 1 minute and 3 minutes.
I found that
- master transaction complete its task in 10 seconds and runs all 30 instances of slave transactions (asynchronous)
- 18 slave transactions start at once
- 12 slave transactions remain in pendig status till first group finishes
Have you ever found this behaviour?
Is this 18 a fixed limit or a MII parameter? Where could I change it?
Thanks a lot
Regards
Fabio
ps: MII 12.2, netweaver 7.3

Hello Fabio,
Transactions launched asynchronously are handled by MII via JMS and EJB.
You may be able to adapt the behavior in such execution, but it may affect directly the system performance.
I suggest you to check section 'Transactions stuck in PENDING state' of MII handbook.
http://wiki.scn.sap.com/wiki/download/attachments/15603/SAP+MII+Handbook.pdf
Please keep in mind that performance tests are necessary if you modify those values.
Hope it helps !
Please let us know the results.
Best regards,
Raphael

Oracle Inventory Transactions query mode

Hi,
we are working in oracle applications 11i (upgrade project is under process.)
I was wondering if there is a way the Transactions forms (miscellaneous and subinventory transfer ) can be in query mode ctrl+ F11
Any help....

No.
But you can use the Material Transactions screen to query past transactions.
Hope this helps,
Sandeep Gandhi

CALL SOLAR_EVAL report directly as a Transaction

Hi experts
we are using solar_eval reports to deliver different status for each support desk manager.
although , we need to call the reports and variants as transactions in se93.
do you know if this is possible?
regards
Julio Cesar Aquino

I've now viewed the HTML source in the 'customize' view of my report portlet and noted all the parameters used. I generated a URL based on all of these parameters, e.g.,
http://myserver.com/portal/page&_dad=portal&_schema=PORTAL&_type=portlet&_providerid=904735153&_portletid=204&_backurl=http://myserver.com/pls/portal/url/PAGE/TESTPAGES/JH_FORM_REP_INTEGRATION&_mode=2&_referencepath=403765_JH_SORT_REPORT2_904735153&p_arg_names=_orderby_col_1&p_arg_values=DATE_OF_PURCHASE&p_arg_names=_orderby_ord_1&p_arg_values=DESC
and loaded the URL.
I get the following weird behaviour. If I launch the URL then the report does not change its output on the first attempt.
However, clicking on the 'Customize' link shows that the orderbycol_1 and orderbtord_1 values have changed! Clicking on OK/Cancel takes me back to the page with the portlet on and the data is now updated! In fact, just hitting refresh on the main page forces the report to execute correctly.
Is this a caching issue? What is the workaround?
I have attempted to place all these hidden values into the report portlet (before page section) and using a custom layout, added a a javascript function that would submit the hidden form passing a value dependent on which hyperlink I clicked (the link relating to the column I am wishing to sort on and in what order). It suffers from the same issue.
I am so close to getting this to work!! Argh!

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

AIP-50143: Transaction Instance Not found for Transaction Id

Hey Guys,
We have configured a Custom Document Exchange over Generic protocol to transfer a file.
1. Internal delivery channel is 'SFTP' - Picks file
2. External delivery channel is 'SFTP' - Puts file
3. Exchange protocol - Custom document over generic
4. Translation enabled - False (Currently its turned off, but the file is xml so we may want to turn it on)
5. Validation enabled - False
We are encountering below error in B2B while processing. Can someone please help with this.
Thanks,
Phani
010.02.05 at 18:41:41:672: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setDocumentPlugin PickReqRev 1.0
2010.02.05 at 18:41:41:672: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setDocumentPlugin info : Cremul version D96A
2010.02.05 at 18:41:41:672: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setDocumentPlugin info : EDIPHARM version 1.0
2010.02.05 at 18:41:41:672: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setDocumentPlugin info : PickReqRev version 1.0
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setExchangePlugin Generic version 1.0
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:setExchangePlugin info : Genericversion 1.0
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage translated payload =
oracle.tip.adapter.b2b.message.MessageStorage@140fee
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage msg.isSignalMsg() = false
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Call Outgoing Response Processor
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Response:Response:outgoingResponse Enter
2010.02.05 at 18:41:41:673: Thread-26: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Response:Response:outgoingResponse Update the Request-Response Table Row for RefertoRequestMessageID with message state Processing Outgoing Response
2010.02.05 at 18:41:41:676: Thread-26: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2010.02.05 at 18:41:41:677: Thread-26: BusinessLogicLayer - (DEBUG) Push Stack: queryBusinessTransactionInstance
2010.02.05 at 18:41:41:693: Thread-26: BusinessLogicLayer - (DEBUG) Pop Stack: queryBusinessTransactionInstance
2010.02.05 at 18:41:41:694: Thread-26: B2B - (ERROR) Error -: AIP-50143: Transaction Instance Not found for Transaction Id "null"
 at oracle.tip.adapter.b2b.collaboration.B2BWFEventManager.handleException(B2BWFEventManager.java:478)
 at oracle.tip.adapter.b2b.collaboration.CollabCatalogAccessor.getTransactionInstance(CollabCatalogAccessor.java:364)
 at oracle.tip.adapter.b2b.collaboration.CollabCatalogAccessor.setTransactionState(CollabCatalogAccessor.java:283)
 at oracle.tip.adapter.b2b.collaboration.CollaborationManager.setTransactionState(CollaborationManager.java:871)
 at oracle.tip.adapter.b2b.msgproc.DbAccess.updateReqRespState(DbAccess.java:3249)
 at oracle.tip.adapter.b2b.msgproc.Response.outgoingResponse(Response.java:905)
 at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1170)
 at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
 at oracle.tip.transport.basic.sftp.SFTPProcessor.processMessage(SFTPProcessor.java:188)
 at oracle.tip.transport.basic.sftp.SFTPMonitor.processMessage(SFTPMonitor.java:351)
 at oracle.tip.transport.basic.sftp.SFTPMonitor.run(SFTPMonitor.java:304)
2010.02.05 at 18:41:42:001: Thread-26: B2B - (DEBUG) Engine:notifyApp Enter
2010.02.05 at 18:41:42:014: Thread-26: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0A140A0E126A1276F45000001AD6B570</b2bMessageId>
<errorCode>AIP-50014</errorCode>
<errorText>General Error</errorText>
<errorDescription>
<![CDATA[Machine Info: (fcgemappdev04)
Description: General Error
StackTrace:
Error -: AIP-50014: General Error: Error -: AIP-50025: Repository error : Error -: AIP-50025: Repository error : Error -: AIP-50143: Transaction Instance Not found for Transaction Id "null"
 at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1213)
 at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
 at oracle.tip.transport.basic.sftp.SFTPProcessor.processMessage(SFTPProcessor.java:188)
 at oracle.tip.transport.basic.sftp.SFTPMonitor.processMessage(SFTPMonitor.java:351)
 at oracle.tip.transport.basic.sftp.SFTPMonitor.run(SFTPMonitor.java:304)
Caused by: Error -: AIP-50025: Repository error : Error -: AIP-50025: Repository error : Error -: AIP-50143: Transaction Instance Not found for Transaction Id "null"
 at oracle.tip.adapter.b2b.msgproc.DbAccess.updateReqRespState(DbAccess.java:3252)
 at oracle.tip.adapter.b2b.msgproc.Response.outgoingResponse(Response.java:905)
 at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1170)
 ... 4 more
Caused by: Error -: AIP-50025: Repository error : Error -: AIP-50143: Transaction Instance Not found for Transaction Id "null"
 at oracle.tip.adapter.b2b.collaboration.CollaborationManager.setTransactionState(CollaborationManager.java:874)
 at oracle.tip.adapter.b2b.msgproc.DbAccess.updateReqRespState(DbAccess.java:3249)
 ... 6 more
Caused by: Error -: AIP-50143: Transaction Instance Not found for Transaction Id "null"
 at oracle.tip.adapter.b2b.collaboration.B2BWFEventManager.handleException(B2BWFEventManager.java:478)
 at oracle.tip.adapter.b2b.collaboration.CollabCatalogAccessor.getTransactionInstance(CollabCatalogAccessor.java:364)
 at oracle.tip.adapter.b2b.collaboration.CollabCatalogAccessor.setTransactionState(CollabCatalogAccessor.java:283)
 at oracle.tip.adapter.b2b.collaboration.CollaborationManager.setTransactionState(CollaborationManager.java:871)
 ... 7 more
]]>

Hi Phani,
What is the naming convention you are using at IDC? If you are sending the response to your TP, then make sure to send ReplyToMsgId as part of file name. If it is not a response, then send MessageType as 1 as part of file name.
For file naming convention required, please refer -
http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_010_Transport_File_FTP_Internal.pdf
Regards,
Anuj

How to use Z transaction type while in the Transaction launcher Wizard?

In SPRO->CRM->Transactions->Basic Settings->Define transaction Types I can see a whole host of Z transaction types.
These define all sorts of business transaction defaults. Within the Transaction launcher Wizard there is a Transaction Type that can be entered, but I can only see three options, being 'BOR Transaction', 'URL Transaction' and ' M', for some reason. None of the transaction types shown in the above SPRO path are displayed.
Does anyone know how I can use my Z transation type. These are used by the config behind the Action Boxes for the Winclient IC, but I can not get the Transaction launcher wizard to see or use these. The SAP How-to Guide to tha Transaction Launcher says that only BOR and URL Transactions can be used (unless you have IS-U). If this is true then how does one provide all the information provided by the Transaction type. The whole idea of the transaction type is default this information in one area.
Anyone.
Jason

I think it is possible.
In CRMC_UI_NBLINKS if you look at the logical links you can see that SRV-ORD-DC has a Parameter of 'SRVO' with a certain Parameter Class.
If you were to check SPRO->CRM->Transactions_Basic Settings->Transaction Types you will see that SRVO exists as an entry. This logical ink is therefore using this Transaction type to extract characteristics etc.
Having said that, I need to call the sales order create with a certain transaction type, so I copied SLS-SLO-CR to a Z copy, added the Parameter of 'Z111' and also used the Parameter class of CL_CRM_UIU_BT_PARAM_CREATE.
This should now, in theory all work, and show the exact same transaction in the Webclient IC as it does in the Winclient IC as they are both using the same Transaction type. However, the Webclient transaction looks different in terms of fields etc., so I don't think it's working. after all.
Jason

Non transactional data source and ejb transaction

Inside an ejb method with trans-attribute = Required,
Do a bunch of things using a transactional data source and a bunch of things using
a non trasnactional data source.
Looks like the time spent doing the non-transactional data source related work
does not count for the transaction timeout defined for the ejb.
So, what happens here, the ejb transaction is suspended ( when I start using the
non transactional ds ) ?

Hi,
"siddiqut" <[email protected]> wrote in message news:3fa7c79d$[email protected]..
Inside an ejb method with trans-attribute = Required,
Do a bunch of things using a transactional data source and a bunch of things using
a non trasnactional data source.
Looks like the time spent doing the non-transactional data source related work
does not count for the transaction timeout defined for the ejb.
So, what happens here, the ejb transaction is suspended ( when I start using the
non transactional ds ) ?The transaction is not suspended when you call something
which is not non-transactional.
Regards,
Slava Imeshev

Weblogic Eclipselink Sequence Table Connection Pool Sequence Separate transaction while JTA on main transaction

Hi,
And thanks in advance for your support.
In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
QUICK REFERENCE:
http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
The concept:
While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
Namely, pumping messages to JMS queues, persisting entities etc.
Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
Under glassfish, for example, tagging a persistence.xml with :
<persistence-unit name="MY_PU" transaction-type="JTA">
 <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
 <jta-data-source>jdbc/DERBY_DS</jta-data-source>
 <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>
 <properties>
 <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
 </properties>
</peristence-unit>
does miracles, when entities are using TABLE sequencing.
Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
at org.eclipse.persi
While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
For example:

 
This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
Is this a known issue?
Is there something I am missing in the configuration?
It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
Error Code: 30000
Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
Many thanks for your help.

Are you calling the cmp bean code and your new Sql code under a same transactional context?
The following setting
"rollbackLocalTxUponConnClose=true"
will make the connectionpool to call the rollback method on the connection object before keeping it back in the pool. In your sql code if you are calling connection.close() , then your entire transaction will be rolled back.
CMP bean requires a transactional connection while communicating with the database.
What is the sequence of code execution?
I think you must be calling sql code first and then cmp bean code later.
You may avoid this problem in this way. This is my guess based on my understanding on your code execution.
1. set rollbackLocalTxUponConnClose=false
Execute the sql code and cmp code in a single transaction (in a single session bean method with cmt or bmt transaction ). Specify tx.rollback if it is bmt. or call tx.setRollbackOnly() if it is a cmt. In this way you will have control to roll back the transactions.
Hope this helps you.
bmt-> bean managed transaction
cmt-> container managed transaction.
Regards,
Seshi.

Transaction aborted (possibly due to transaction time out) - Question

This one is driving me insane!
Bellow you will find the code, the descriptor stuff and the exception. The code belongs to a CMP EJB using CMT (transactions). This gets called from a session bean. Please help.
Here is the code:
public Object ejbCreate( String id )
 throws CreateException {
 s_logger.debug( "ejbCreate()" ); // this prits
 //setId( id );
 return null;
public void ejbPostCreate( String id )
 throws CreateException {
 s_logger.debug( "ejbPostCreate()" ); // this also prints
here is descriptor stuff:
<container-transaction>
<method>
<ejb-name>AgentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
here is the !@#$ exception (sorry been tracing this one for hours):
RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
javax.transaction.RollbackException: Transaction marked for rollback
<<no stack trace available>>

It usually means that you're doing something which creates a loop in your locking. Something like setting a value in each instance from an update method of one of the instances. Your posted code doesn't seem to be the trouble, but I could be missing something.
Success,
S.

Jabber for Windows Video calling in Deskphone mode

Hi
Does Jabber for windows support video calling in deskphone mode? I have 7942 IP Phone, VT advantage camera on Laptop and Jabber clinet insatlled on laptop. Can i make video callng with Jabber in Deskphone mode?
It is not working please help.
Regards,
Andy

Hi Andy,
Yes, Jabber for Windows supports video calling in deskphone mode.
You'll need to install the Cisco Media Service Interface specific to your version of Jabber and correctly configure Jabber for Deskphone Video.
Please follow these instructions to configure Deskphone Video:
For Jabber for Windows 9.1
For Jabber for Windows 9.2
Once completed, if you run Jabber you should see the following when you open the Connection Status window (Help > Show connection status):
Regards,
Matt

Transaction only as follow up transaction

Hi all,
I hope you can help me. We would like to make a certain transaction only available as follow up transaction as not as initial transaction. I know that this is possible by means of authorization but I would like to know whether this can be done in the customizing.
For example it should only be possible to create an opportunity after the creation of a lead. One should never be able to start with an opportunity.
I hope you can help!
Kind regards Mireille

Actually at a previous customer of mine they had implemented such a functionality.
I remember that wether or not a certain business transaction type was only USABLE for Follow-up purposes was determined customizing:
spro>Customer relationship management>Transactions> Basic Settings>Define Transaction types
In Standard SAP solution;in Define Transaction types (View CRMV_PROC_TYPE) for the Column ''INACTIVE'' which corresponds with field
PROCESS_BLOCKED (data element CRMT_PROCESS_BLOCKED) you have two possible entries:
X (inactive)
Y (Blocked for online Maintenance)
These values are stored in the domain CRMT_PROCESS_BLOCKED as a value Range.
Ofcourse, I can not verify this anymore since I am currently working at another customer, but I assume they made another 'customer' entry , e.g. FOLLOWUP and adjusted the coding to check on the customizing settings for a certain Transaction type.
Next I think they might have used the BADI CRM_ORDER_AUTH_CHECK in method CRM_ORDER_ADD_AUTH_CHECK to do a check based on the IV_PROCESS_TYPE and verify in TableView CRMV_PROC_TYPE what the entry is for field 'PROCESS_BLOCKED'. If the field has value 'FOLLOWUP' I think a message was raised 'this transaction type is only used as follow-up'.
Since I am not a developer I can not provide you with any coding...and I am not sure this approach will work...but it might be a good starting point
If helpfull, please award with points.
cheers
davy

Transaction code for creation of transaction keys in obyc

Dear Experts,
Can u tell me what is the transaction code for creation of transaction keys in obyc asap.
Thanks & Regards,
Radhika.

Hi
There is no TCode and the path is
SPRO-Material Management-Purchasing-Conditions-Price Determination....
Cheers
Srinivas

[Solved] if(Transaction specified for a non-transactional database) then

I am getting started with BDBXML 2.4.14 transactions and XQuery update functionality and I am having some difficulty with 'node insert ...' and transactions failing with 'Transaction specified for a non-transactional database'
Thanks for helping out.
Setup:
I have coded up a singleton manager for the XmlManger with a ThreadLocal holding the transaction and a query method to execute XQueries. The setup goes like this:
environmentConfig = new EnvironmentConfig();
environmentConfig.setRunRecovery(true); environmentConfig.setTransactional(true); environmentConfig.setAllowCreate(true); environmentConfig.setRunRecovery(true); environmentConfig.setInitializeCache(true); environmentConfig.setTxnMaxActive(0); environmentConfig.setInitializeLocking(true); environmentConfig.setInitializeLogging(true); environmentConfig.setErrorStream(System.err);
environmentConfig.setLockDetectMode(LockDetectMode.MINWRITE); environmentConfig.setJoinEnvironment(true); environmentConfig.setThreaded(true);
xmlManagerConfig = new XmlManagerConfig(); xmlManagerConfig.setAdoptEnvironment(true); xmlManagerConfig.setAllowAutoOpen(true); xmlManagerConfig.setAllowExternalAccess(true);
xmlContainerConfig = new XmlContainerConfig(); xmlContainerConfig.setAllowValidation(false); xmlContainerConfig.setIndexNodes(true); xmlContainerConfig.setNodeContainer(true);
// initialize
instance.xmlManager = new XmlManager(instance.getEnvironment(), instance.getXmlManagerConfig());
instance.xmlContainer = instance.xmlManager.openContainer( containerName, instance.getXmlContainerConfig());
private ThreadLocal<XmlTransaction> transaction = new ThreadLocal<XmlTransaction>();
public XmlTransaction getTransaction() throws Exception {
 if (transaction.get() == null) {
 XmlTransaction t = xmlManager.createTransaction();
 log.info("Transaction created, id: " + t.getTransaction().getId());
 transaction.set(t);
 } else if (log.isDebugEnabled()) {
 log.debug("Reusing transaction, id: "
 + transaction.get().getTransaction().getId());
 return transaction.get();
 private XmlQueryContext createQueryContext(String docName) throws Exception {
 XmlQueryContext context = xmlManager.createQueryContext(
 XmlQueryContext.LiveValues, XmlQueryContext.Lazy);
 List<NamespacePrefix> namespacePrefixs = documentPrefixes.get(docName);
 // declare ddi namespaces
 for (NamespacePrefix namespacePrefix : namespacePrefixs) {
 context.setNamespace(namespacePrefix.getPrefix(), namespacePrefix
 .getNamespace());
 return context;
 public XmlResults xQuery(String query) throws Exception {
 XmlQueryExpression xmlQueryExpression = null;
 XmlQueryContext xmlQueryContext = getQueryContext(docName);
 try {
 xmlQueryExpression = xmlManager.prepare(getTransaction(), query,
 xmlQueryContext);
 log.info(query.toString());
 } catch (Exception e) {
 if (xmlQueryContext != null) {
 xmlQueryContext.delete();
 throw new DDIFtpException("Error prepare query: " + query, e);
 XmlResults rs = null;
 try {
 rs = xmlQueryExpression.execute(getTransaction(), xmlQueryContext);
 // catch deadlock and implement retry
 catch (Exception e) {
 throw new DDIFtpException("Error on query execute of: " + query, e);
 } finally {
 if (xmlQueryContext != null) {
 xmlQueryContext.delete();
 xmlQueryExpression.delete();
 return rs;
<?xml version="1.0" encoding="UTF-8"?>
<Test version="0.1">
<Project id="test-project" agency="dda">
<File id="large-doc.xml" type="ddi"/>
<File id="complex-doc.xml" type="ddi"/>
</Project>
<Project id="2nd-project" agency="test.org"/>
</Test>
Problem:
All the queries are run through the xQuery method and I do delete the XmlResults afterwards. How do I get around the 'Transaction specified for a non-transactional database' what is the transactions doing? How do I get state information out of a transaction? What am I doing wrong here?
1 First I insert a node:
Transaction created, id: -2147483647
Adding document: large-doc.xml to xml container
Reusing transaction, id: -2147483647
Working doc: ddieditor.xml
Root element: Test
Reusing transaction, id: -2147483647
insert nodes <Project id="JUnitTest" agency="test.org"></Project> into doc("dbxml:/ddieditor.dbxml/ddieditor.xml")/Test
Reusing transaction, id: -2147483647
2 Then do a query:
Reusing transaction, id: -2147483647
doc("dbxml:/ddieditor.dbxml/ddieditor.xml")/Test/Project/@id
Reusing transaction, id: -2147483647
3 The same query again:
Reusing transaction, id: -2147483647
doc("dbxml:/ddieditor.dbxml/ddieditor.xml")/Test/Project/@id
Reusing transaction, id: -2147483647
4 Delete a node:
Reusing transaction, id: -2147483647
delete node for $x in doc("dbxml:/ddieditor.dbxml/ddieditor.xml")/Test/Project where $x/@id = '2nd-project' return $x
Reusing transaction, id: -2147483647
5 Then an error on query:
Reusing transaction, id: -2147483647
doc("dbxml:/ddieditor.dbxml/ddieditor.xml")/Test/Project/@id
Reusing transaction, id: -2147483647
Transaction specified for a non-transactional database
com.sleepycat.dbxml.XmlException: Error: Invalid argument, errcode = DATABASE_ERROR
 at com.sleepycat.dbxml.dbxml_javaJNI.XmlResults_hasNext(Native Method)
 at com.sleepycat.dbxml.XmlResults.hasNext(XmlResults.java:136)
Message was edited by:
jannikj

Ok got it solved by increasing the locks lockers and mutex's I allso increased the the log buffer size:
environmentConfig = new EnvironmentConfig();
 // general environment
 environmentConfig.setAllowCreate(true);
 environmentConfig.setRunRecovery(true); // light recovery on startup
 //environmentConfig.setRunFatalRecovery(true); // heavy recovery on startup
 environmentConfig.setJoinEnvironment(true); // reuse of environment: ok
 environmentConfig.setThreaded(true);
 // log subsystem
 environmentConfig.setInitializeLogging(true);
 environmentConfig.setLogAutoRemove(true);
 environmentConfig.setLogBufferSize(128 * 1024); // default 32KB
 environmentConfig.setInitializeCache(true); // shared memory region
 environmentConfig.setCacheSize(2500 * 1024 * 1024); // 250MB cache
 // transaction
 environmentConfig.setTransactional(true);
 environmentConfig.setTxnMaxActive(0); // live forever, no timeout
 // locking subsystem
 environmentConfig.setInitializeLocking(true);
environmentConfig.setMutexIncrement(22);
environmentConfig.setMaxMutexes(200000);
environmentConfig.setMaxLockers(200000);
environmentConfig.setMaxLockObjects(200000); // default 1000
environmentConfig.setMaxLocks(200000);
// deadlock detection
 environmentConfig.setLockDetectMode(LockDetectMode.MINWRITE);
In the docs by Oracle it is limited information given regarding the impact of these settings and their options. Can you guys point in a direction where I can find some written answers or it hands on?

Call transaction in mode N fro transaction F-02

Similar Messages

Maybe you are looking for