Transaction RSA1 not work

Hello,
I installed "SAP NetWeaver ABAP Trial 7.02 Win 64-bit Version (SP7)" on Windows Server 2003 virtual machine.
System work's fine but when I will want start transaction RSA1, it fails:
Information on where terminated
Termination occurred in the ABAP program "SAPLRSAWB" - in "RSAWB_CHECKS_BEFORE_AWBSTART".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 17 of the (Include) program "LRSAWBU05".
>>>>> call function 'RSBATCH_CHECK_START_LOGWRITER'
Maybe anybody have any ideas of resolve this problem ?
best regards
Krys

It looks to be a problem related to Support pack.
Please search the market place for the SAP OSS note.
There are some OSS notes which needs to be implemented. Ask the BASIS ppl they will guide you in a proper way.
Same problem occurs for me last year, I have implemented few notes and problem get resolved.
I will try to find out the OSS note.
cheers

Similar Messages

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

Transaction launcher not working for custom business role

Hi Experts,
I am facing a very weird problem where the transaction laucher define for BOR transaction is working for one business role(Z business role Customized one) but its not working for other business role (Z business role).
to emphasize further we have the code:-
case ls_attributes-object_type.
    when lc_z23 or lc_z25.
      lv_logical_link = lc_ZITISU.
    when lc_BUS2000115.
      lv_logical_link = lc_ZITERP1.
    when others.
      lv_logical_link = lc_ZITERP2.
endcase.
l_if_navigation = cl_crm_ui_navigation_service=>get_instance( me ).
IF l_if_navigation IS BOUND .
Navigate to transaction launcher using link id
    l_if_navigation->navigate( iv_link_id = lv_logical_link ).
ENDIF.
in this the logical link is is lc_ZITISU whenever this BSP application is called from both the business roles but in one the window opens up for BOR transaction whereas when we login again using different business role the code is the same as given above. I mean the sam logical link id is used and navigated to but window is not opening for transaction launcher as it happens for the previous business role.
Request your help to resolve this issue.
Thanks,
Rajwin

Hi,
I tried by applying the PFCG role id of business role which was working to the business role id of the one for which it wasn't working and then try testing whether the transaction launcher is triggering. But the transaction launcher screen is still not opening even after doing this.
Probably there's something else too which is causing the problem. Request your inputs on this,
Thanks,
Rajwin

EJB Transaction does not work

Hi,
I have a servlet, a session bean, and an entity bean. A servlet doesn't have any transaction attribute, a session bean has Required, and an entity bean has Required. I have the code like the following:
Servlet:
EJBDelegate ed = new EJBDelegate();
TwoPhaseSB sb = ed.getTwoPhaseSB();
sb.testTransaction();Session Bean:
public void testTransaction() {
    try{
        TestInfoLocal testInfo;
        TestInfoLocalHome testInfoHome = TestInfoUtil.getLocalHome();
        testInfo = testInfoHome.create("525252", "353535", "transaction test insert", "etc");
        testInfo.setElement_id("111111");
        //There's no item which has its primary key as 7777, so there's exception error occurs
        testInfo = testInfoHome.findByPrimaryKey(new Integer(7777));
    }catch(Exception e){
         e.printStackTrace();
}Since the code in testTransaction is supposed to run in the same transaction, if there's exception occurrs, isn't it supposed to rollback? I mean, creation of item and update should be rollback. But, the data is inserted and created although there's exception. Could anyone can give me the idea why transaction doesn't work? FYI, I'm using Weblogic8.1.

Yes, you're right. I am using CMP. I added the following exceptions to my session bean but still the changes are updated:
     }catch(EJBException e){
          e.printStackTrace();
     }catch (NamingException e) {
          e.printStackTrace();
     }catch (CreateException e) {
          e.printStackTrace();
     }catch (FinderException e) {
          e.printStackTrace();
     } I tried to insert "TransactionRolledbackException", but it's not thrown in any statement since my beans are managed by container. Could you tell me what exception should I use? Or should I add some exception to my entity bean? Finder methods are throwing FinderException currently.
Thanks,

ABAP Query Execution via Custom Transaction Code - Not working

We have created an ABAP Query in our DEV client and we then created a transaction code to run that query. We have done this because the customer does not want anyone to have access to SQ01, SQ02 in production. This works great in DEV but we can not get it to work in production.
The ABAP Query was exported to our Prod client successfully. I say exported because you do not do direct transports with queries.
We then transported the new transaction code to run the query to production and it was successful.
However, when we run the transaction is production we get a sys dump stating it can not find the query.
We believe the problem is the TRDIR table is missing an entry for the program in production (it has an entry in DEV).
I would have thought that the export on the query would have brought in this entry -but obviously not.
Any suggestions on how we can get this entry into the production client? Did we miss a step on the export that would do this? We want to only bring over this entry - not the entire TRDIR table for obvious reasons (size (1.5 million entries, programs not ready for production, etc.).
Please help!
Thanks.
Scott

Hi,
The above solution will work if you assign the transaction in one server, If you want this will not work in quality/production boxes when transported the query..the program name will not be the same in all the servers...
For this. Do the below:
In SE93, Create a Paramter Transaction
-> Transaction = Start_report
-> In default values, give the below details:
     D_SREPOVARI-REPORTTYPE = AQ
     D_SREPOVARI-EXTDREPORT = Name of the Query
     D_SREPOVARI-REPORT = User Group
Save the transaction..Now if the program is generated with different names in the quality/proudction, this will still work..
Regards
Vijay Hebbal

Java user-defined transaction management not working correctly???

Hi everyone,
I have encountered a problem when using Java user-defined transaction management in my session bean. It threw an exception but I could not work out what that means. Could anyone comment on this? Thanks.
This BrokerBean is a stateless session calling other entities bean to perform some simple operations. There are 2 Cloudscape databases in use. Invoices (EB) use InvoiceDB and all the other EBs use StockDB.
If I comment out the user-defined transaction management code, then everything works fine. Or if I comment out the Invoices EB code, it is fine as well. It seemed to me that there is something wrong in transaction management when dealing with distributed databases.
--------------- source code ----------------------
public void CreateInvoices(int sub_accno) {
try {
utx = context.getUserTransaction();
utx.begin();
SubAcc subAcc = subAccHome.findByPrimaryKey(new SubAccPK(sub_accno));
String sub_name = subAcc.getSubName();
String sub_address = subAcc.getSubAddress();
Collection c = stockTransHome.findBySubAccno(sub_accno);
Iterator i = c.iterator();
ArrayList a = new ArrayList();
while (i.hasNext()) {
StockTrans stockTrans = (StockTrans)i.next();
int trans_id = stockTrans.getTransID();
String tran_type = stockTrans.getTranType();
int stock_id = stockTrans.getStockID();
float price = stockTrans.getPrice();
Invoices invoices = invoicesHome.create(sub_accno, sub_name, sub_address, trans_id, stock_id, tran_type, price);
stockTrans = stockTransHome.findByPrimaryKey(new StockTransPK(trans_id));
stockTrans.remove();
utx.commit();
utx = null;
} catch (Exception e) {
if (utx != null) {
try {
utx.rollback();
utx = null;
catch (Exception ex) {}
// e.printStackTrace();
throw new EJBException("BrokerBean.CreateInvoices(): " + e.getMessage());
--------------- exception ----------------------
Initiating login ...
Enter Username:
Enter Password:
Binding name:`java:comp/env/ejb/BrokerSB`
EJB test succeed
Test BuyStock!
Test BuyStock!
Test BuyStock!
Test BuyStock!
Test SellStock!
Test SellStock!
Caught an exception.
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
java.rmi.RemoteException: BrokerBean.CreateInvoices(): CORBA TRANSACTION
_ROLLEDBACK 9998 Maybe; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x2000 minor code: 1806
completed: Maybe
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemExceptio
n(ShutdownUtilDelegate.java:64)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
at BrokerStub.CreateInvoices(Unknown Source)
at Client.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:22
9)
at com.sun.enterprise.appclient.Main.main(Main.java:155)
Caused by: java.rmi.RemoteException: BrokerBean.CreateInvoices(): CORBA TRANSACT
ION_ROLLEDBACK 9998 Maybe; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x2000 minor code: 1806
completed: Maybe
at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.ja
va:389)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:43
1)
at BrokerBean_EJBObjectImpl.CreateInvoices(BrokerBean_EJBObjectImpl.java
:265)
at BrokerBeanEJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(Ge
nericPOAServerSC.java:520)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(Gen
ericPOAServerSC.java:210)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAS
erverSC.java:112)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProces
sor.java:84)
at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadP
ool.java:99)

Three things:
first, maybe you should think of putting ut.begin() just before the invoicesHome.create() method and ut.commit() just after the stockTrans.remove() method.It wont solve the current problem but will help in performance once the problem is solved.
second, your utx.commit() is outside the try block. how come the code is compiling then??
third, try doing a SOP call before and after invoicesHome.create() method and see where the problem actually lies.
let us know...
Hi SteveW2,
Thanks for being so helpful. Here are my replies:
Can I just ask why you're not using containermanaged
transactions?The reason why I didn't use container managed
transactions is because I don't really know how to do
that. I am more familiar with this user-defined
transaction handling.
I have attempted to implement the same method in an
entity bean and just let the container manage the
rollback itself. The same exception was thrown when
running the client.
Also, the transaction behaviour is likely to relateto
the app server youre using - which is it?What do you mean by the app server? I am using J2EE
1.3.1 if that is what you meant.
Finally, if your code has a problem rolling back,and
throws an exception, you discard your exception
thereby losing useful information.I have tried to print the exception stack as well, but
it is the same as just printing the general
exception.
This problem is very strange cause if I comment out
the transaction management thing, then everything
works fine. Or if I am only working with 1 single
database, with this user-defined transaction handling,
everything works fine as well.
Here is the error log from J2EE server if you are
interested.
------------ error log ---------------
javax.ejb.TransactionRolledbackLocalException:
Exception thrown from bean; nested exception is:
javax.ejb.EJBException: ejbCreate: Connection
previously closed, open another Connection
javax.ejb.EJBException: ejbCreate: Connection
previously closed, open another Connection
     at InvoicesBean.ejbCreate(Unknown Source)
at
InvoicesBean_RemoteHomeImpl.create(InvoicesBean_Remote
omeImpl.java:31)
     at InvoicesHomeStub.create(Unknown Source)
     at BrokerBean.CreateInvoices(Unknown Source)
at
BrokerBean_EJBObjectImpl.CreateInvoices(BrokerBean_EJB
bjectImpl.java:261)
at BrokerBeanEJBObjectImpl_Tie._invoke(Unknown
Source)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispa
chToServant(GenericPOAServerSC.java:520)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.inter
alDispatch(GenericPOAServerSC.java:210)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispa
ch(GenericPOAServerSC.java:112)
at
com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:25
at
com.sun.corba.ee.internal.iiop.RequestProcessor.proces
(RequestProcessor.java:84)
at
com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThr
ad.run(ThreadPool.java:99)
javax.ejb.TransactionRolledbackLocalException:
Exception thrown from bean; nested exception is:
javax.ejb.EJBException: ejbCreate: Connection
previously closed, open another Connection
at
com.sun.ejb.containers.BaseContainer.checkExceptionCli
ntTx(BaseContainer.java:1434)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(Base
ontainer.java:1294)
at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseCo
tainer.java:403)
at
InvoicesBean_RemoteHomeImpl.create(InvoicesBean_Remote
omeImpl.java:37)
     at InvoicesHomeStub.create(Unknown Source)
     at BrokerBean.CreateInvoices(Unknown Source)
at
BrokerBean_EJBObjectImpl.CreateInvoices(BrokerBean_EJB
bjectImpl.java:261)
at BrokerBeanEJBObjectImpl_Tie._invoke(Unknown
Source)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispa
chToServant(GenericPOAServerSC.java:520)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.inter
alDispatch(GenericPOAServerSC.java:210)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispa
ch(GenericPOAServerSC.java:112)
at
com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:25
at
com.sun.corba.ee.internal.iiop.RequestProcessor.proces
(RequestProcessor.java:84)
at
com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThr
ad.run(ThreadPool.java:99)
What is "connection previously closed, open another
connection"? This might be the cause of the
exception.
I'll keep trying till I solve the problem.
Thanks,
Sasuke

Explicit Transaction Management not working

Hi,
I have written a StatelessSession Bean. There is a method in this bean which
calls methods of Other BMP Beans.All these methods have to be part of one Transaction.Below
I have shown in Pseudocode ,how I am handling it.
//This is the SessionBean Method
public void processDocument()
UserTransaction Utrx = SessionContext.getUserTransaction();
try
Utrx.begin();
Bean1.method1();//this method inserts a row in the database
Bean2.method2();// this method inserts a row in another table
Bean3.method3();//deletes a row
// couple of other method calls
Utrx.commit();
catch()
//catch Exceptions and rollback.

OK, now I'm catching up. Do you see that exception thrown in your calling
code, i.e. does your code as posted catch that exception?
If so, you most probably are not using the proper connection pool -- you
should be using the JTS pool not just a WL pool -- and so the connection is
not participating in the transaction.
Peace,
Cameron Purdy
Tangosol Inc.
Tangosol Coherence: Clustered Coherent Cache for J2EE
Information at http://www.tangosol.com/
"Sunil Naik" <[email protected]> wrote in message
news:3c26a505$[email protected]..
>
"Cameron Purdy" <[email protected]> wrote:
Why do you say it is not working? Do you get a compile error? An
exception?
A partial commit? Deadlock? Horse head in your bed? Out of memory?
Peace,
Hi Cameron,
Actually , while testing the method ,I am deliberately making the3 rd
method call throw an Exception and exit.In that case what I expect is thatthe
work done in the first two method calls should be rolled back. i.e.Therows should
not be inserted in the database.This is not happening.The inserts made inthe
earlier two methods are being commited.
Hope it is clear now.
Thanx,
sunil
Cameron Purdy
Tangosol Inc.
Tangosol Coherence: Clustered Coherent Cache for J2EE
Information at http://www.tangosol.com/
"Sunil Naik" <[email protected]> wrote in message
news:3c230f17$[email protected]..
Hi,
I have written a StatelessSession Bean. There is a method in thisbean
which
calls methods of Other BMP Beans.All these methods have to be partof one
Transaction.Below
I have shown in Pseudocode ,how I am handling it.
//This is the SessionBean Method
public void processDocument()
UserTransaction Utrx = SessionContext.getUserTransaction();
try
Utrx.begin();
Bean1.method1();//this method inserts a row in the database
Bean2.method2();// this method inserts a row in another table
Bean3.method3();//deletes a row
// couple of other method calls
Utrx.commit();
catch()
//catch Exceptions and rollback.

Copied Transaction ZCS02 not working...

Hi,
I want to create a copy of transaction CS02. But this is a function Group (CSDI).. After all, i copy the Function Group with all Function Modules. Also create a t.code ZCS02 through SE93 (copy program SAPMC29S also).
But, when i m executing the ZCS02 transaction, it's not working..means not responding.
Please tell me what would be the problem..
Regards,

Thanks for ur reply,
We have some issues with the users, so don;t want to give the CS02 transaction to them...so i want to create a new Z transaction for user.
But after copy the function group from SE80, it is not working properly...
Please suggest..
regards......
Edited by: Prince Kumar on Jun 4, 2009 3:20 PM

Session Bean Transaction Rollback not working for RuntimeException

Hi,
I am calling a number of JDBC create/update statements within a method in a container managed transaction stateless session bean with transaction attribute set to required. I am running the bean within the embedded OC4J supplied with JDeveloper 10g (10.1.2). For each JDBC call, i connect to a datasource via JNDI containg a pool of connections pointing to an Oracle 10g database (standard J2EE)
If i throw a runtime exception within the method the transaction is NOT rolled back as it should be according to the EJB spec. However, if i setRollbackOnly() on the session bean SessionContext the transaction does roll back.
Has anybody experienced this before?
Is this an OC4J bug?
Thanks
Dave

Generally, for urgent issues it's best to open a SR with Oracle Support rather than posting to the forums.
enlist=dynamic didnt exist in 10.2.0.2.20, but does now. I can't recall what specific version it was introduced though.
enlist=false prevents enlistment in MSDTC transactions, so thats why it's not rolling back in that case.
"transaction branch length 90 is illegal" was a known issue on Vista, is that the OS you're using? It takes a two part fix, and It is resolved by
1) getting up to 10204 ODP (apply the 10204 rdbms patch to your client install)
2) applying SP1 for Vista
Hope it helps,
Greg

RSA1 not working

Hi All,
I am facing an issue in switching client in BI 7.0 System.
The scenario is that we have a BW system which is built from another BW system by bachup restore method.
Intially we had client 200 in which the connection to ECC and CRM system was done.
Now we have created another client 500 with SAP_ALL copy of client 200 and deleted client 200. Also in table RSADMINA we have changed BWMANDT field from 200 to 500 but when I login to client 500 and run transaction RSA1 it gives me the message "Logical system name has been changed for this system".
Kindly help in fixing the issue. Let me know if any more details required.
Looking forward for you reply.
Regards,
Soumya

Hi Soumya,
Check in Tx SCC4 whether logical system name has been changed, and try to restore it to the original name.
or
Contact your Basis team and they can use Tx: BDLS to change the Logical system through out the client.
Please also check this thread incase none of the above oprion is helpful:Logical system name has been changed for this system
Thanks,
RP

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

Transaction launcher not working for custom business role in WEB UI

Hi Experts,
we have maintained a link for activity reports in web Ui which triggers a program Z_CRM_TIME_REPORT . we have maintained the logical links and assigned them to the custom business role. when we run the program in SE38 in GUI its working fine but we are facing the problem when we click the link in WEB UI we get a different screen related to BP and not the activity report.Kindly suggest what are the configuration need to be tested.
Thanking you,
Deepa

My guess would be that the parameter stated in the logical link (navigation bar customizing) that you use is incorrect. This should be the name of the transaction launcher definition you have maintained.
Otherwise, check the transaction launcher wizard to see that the report is maintained correctly.
Hope this helps.
Regards,
Pieter Rijlaarsdam

JTA Transaction does not work

Hi,
I am currently porting an application from Websphere 3.5 to Weblogic 6.1.
I have an Oracle 8.1.7 database.
I have a problem when rollbacking JTA transaction.
I have a session bean manipulating Entity beans (CMP & BMP) within a single
method.
This method creates beans and then update them.
The issue is that during the update, the application generates an exception
(system or applicative). The method rollbacks the transaction, but if I look
in the database, the insert requests are not rollbacked !
I have tried two different approach:
1) container manage transaction: I catch the exception and then call
setRollbackOnly()
2) bean manage transaction: I retrieve the user transaction, and apply the
rollback on exception.
What's wrong with that ? This actually works fine on Websphere.
Regards
Jacques Desmazieres

Make sure that you are using a TxDataSource and not a plain DataSource.
(This is configured in the console.)
-- Rob
Jacques Desmazieres wrote:
Hi,
I am currently porting an application from Websphere 3.5 to Weblogic 6.1.
I have an Oracle 8.1.7 database.
I have a problem when rollbacking JTA transaction.
I have a session bean manipulating Entity beans (CMP & BMP) within a single
method.
This method creates beans and then update them.
The issue is that during the update, the application generates an exception
(system or applicative). The method rollbacks the transaction, but if I look
in the database, the insert requests are not rollbacked !
I have tried two different approach:
1) container manage transaction: I catch the exception and then call
setRollbackOnly()
2) bean manage transaction: I retrieve the user transaction, and apply the
rollback on exception.
What's wrong with that ? This actually works fine on Websphere.
Regards
Jacques Desmazieres

Scheduled background job for FBV0 transaction is not working.

Hi All,
We have impleted OSS note 971193. This is program which deletes parked documents in the system and it behaves good when we run in the foreground and doesn't work when it is scheduled in background. I debugged background job which is scheduled and program fails after call transaction. I get this following error "Error in Document Deletion. Runtime error RAISE_EXCEPTION has occurred".
Can anyone please help me if you have any info on this or if you see similar kind of problem.
Thanks in Advance.
Regards,
M

any idea ?

Call transaction is not working sometimes - Update mode as 'P'

Hello Team,
Whenever contact(ME31K) gets created the contract number should be updated in ME47(one custom fields).
I have written BDC in the BADI IF_EX_ME_PURCHDOC_POSTED~POSTED.
      call transaction 'ME47' using it_bdcdata
                       mode vmode
                       update vupdate
                       messages into it_msgtab.
        vupdate type char1 value 'S',
        vmode type char1 value 'P'.
Is the problem could be in mode 'P' but its working sometimes.
And no further sessions on ME47 with same document number.
What could be the reason.
Regards,
Vadamalai A

Hi Vadamalai,
mode 'P' is no proper vmode for a production system. No normal user should found himself stoppping at a break-point in debugger in any transaction. Please check, if the issue remains after changing the vmode to n.
Is there really a break-point (maybe in a userexit or badi) that can be reached on DEV system? If not, there is no reasen to use vmode 'P'. If yes, please remove the break-point after finishing your test.
Regards,
Klaus

Transaction RSA1 not work

Similar Messages

Maybe you are looking for