Transaction Demarcation Error

Hi,
I have written entity bean and tried to verify it in J2EE 1.4 SDK in Deploytool.
It's giving me one error about findByPromaryKey() and findBySalary() methods in SalaryHome interface and description of error is something like "...Transaction Demarcation Error...".
Any idea when it comes and how to resolve it?
Any help is appreciated.
Thanks
Rajeev.

These methods should have container-transaction attributes defined for them in the ejb deployment descriptor, ejb.xml.
<container-transaction>
<method>
<ejb-name>TestBeanEJB</ejb-name>
<method-intf>Home</method-intf>
<method-name>findByPrimaryKey</method-name>
<method-params>
<method-param>java.lang.Integer</method-param>
</method-params>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>

Similar Messages

Entity Bean can only use container-managed transaction demarcation?

In <<Designing Enterprise Application with J2EE 2nd>>
Section 2.3.3.3 Enterprise Bean Transactions,it says:Entity beans can only use container-managed transaction demarcation.
That means,i can not get UserTransaction from EJBContext.
Is that true?

Yes this is the requirement of the specs. Your ejb code generator should give you the error if you use usertransaction.
--Ashwani

MDB container managed transaction demarcation not working in wls 6.1 beta

I have an MDB which sends the messages it receives onto another JMS
          destination within the onMessage method. These messages are not sent to
          the JMS destination unless I explicitly use a transacted session for the
          destination and subsequently commit the session. If I set the transacted
          parameter to Session as false the messages are sent. If I set the
          transacted parameter to true the messages will only be output if the
          session is committed. This is the standard behaviour for a JMS session
          but this is not the correct behaviour for an MDB running with
          container-managed transaction demarcation.
          For a start the transacted parameter to session should be ignored when
          run in the context of a container transaction and the commit method
          should thrown an exception as it is not allowed within the context of a
          container transaction.
          This is the MDB code and the deployment descriptor: -
          public class MessageBean implements MessageDrivenBean, MessageListener
          private String topicName = null;
          private TopicConnectionFactory topicConnectionFactory = null;
          private TopicConnection topicConnection = null;
          private TopicSession topicSession = null;
          private Topic topic = null;
          private TopicPublisher topicPublisher = null;
          private TextMessage textMessage=null;
          private transient MessageDrivenContext messageDrivenContext = null;
          private Context jndiContext;
          public final static String
          JMS_FACTORY="weblogic.examples.jms.TopicConnectionFactory";
          public final static String
          TOPIC="weblogic.examples.jms.exampleTopic";
          public MessageBean()
          public void setMessageDrivenContext(MessageDrivenContext
          messageDrivenContext)
          this.messageDrivenContext = messageDrivenContext;
          public void ejbCreate()
          public void onMessage(Message inMessage)
          try
          jndiContext = new InitialContext();
          topicConnectionFactory =
          (TopicConnectionFactory)jndiContext.lookup(JMS_FACTORY);
          topic = (Topic) jndiContext.lookup(TOPIC);
          topicConnection =
          topicConnectionFactory.createTopicConnection();
          topicConnection.start();
          // The transacted parameter should be ignored in the context of a
          container tx
          topicSession = topicConnection.createTopicSession(true,
          Session.AUTO_ACKNOWLEDGE);
          topicPublisher = topicSession.createPublisher(topic);
          textMessage = (TextMessage)inMessage;
          topicPublisher.publish(inMessage);
          // this is illegal in a container transaction
          topicSession.commit();
          topicConnection.close();
          catch (JMSException je)
          throw new EJBException(je);
          catch (NamingException ne)
          throw new EJBException(ne);
          public void ejbRemove()
          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <display-name>MessageBean</display-name>
          <ejb-name>MessageBean</ejb-name>
          <ejb-class>MessageBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          <security-identity>
          <description></description>
          <run-as>
          <description></description>
          <role-name></role-name>
          </run-as>
          </security-identity>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>MessageBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>


Please see the response in the EJB newsgroup.
          Also, could you kindly only post to a single newsgroup?
          Thanks.
          "Jimmy Johns" <[email protected]> wrote in message
          news:[email protected]...
          > I have an MDB which sends the messages it receives onto another JMS
          > destination within the onMessage method. These messages are not sent to
          > the JMS destination unless I explicitly use a transacted session for the
          >
          > destination and subsequently commit the session. If I set the transacted
          >
          > parameter to Session as false the messages are sent. If I set the
          > transacted parameter to true the messages will only be output if the
          > session is committed. This is the standard behaviour for a JMS session
          > but this is not the correct behaviour for an MDB running with
          > container-managed transaction demarcation.
          >
          > For a start the transacted parameter to session should be ignored when
          > run in the context of a container transaction and the commit method
          > should thrown an exception as it is not allowed within the context of a
          > container transaction.
          >
          > This is the MDB code and the deployment descriptor: -
          >
          > public class MessageBean implements MessageDrivenBean, MessageListener
          > {
          > private String topicName = null;
          > private TopicConnectionFactory topicConnectionFactory = null;
          > private TopicConnection topicConnection = null;
          > private TopicSession topicSession = null;
          > private Topic topic = null;
          > private TopicPublisher topicPublisher = null;
          > private TextMessage textMessage=null;
          > private transient MessageDrivenContext messageDrivenContext = null;
          >
          > private Context jndiContext;
          >
          > public final static String
          > JMS_FACTORY="weblogic.examples.jms.TopicConnectionFactory";
          > public final static String
          > TOPIC="weblogic.examples.jms.exampleTopic";
          >
          > public MessageBean()
          > {
          > }
          >
          > public void setMessageDrivenContext(MessageDrivenContext
          > messageDrivenContext)
          > {
          > this.messageDrivenContext = messageDrivenContext;
          > }
          >
          > public void ejbCreate()
          > {
          > }
          >
          > public void onMessage(Message inMessage)
          > {
          > try
          > {
          > jndiContext = new InitialContext();
          > topicConnectionFactory =
          > (TopicConnectionFactory)jndiContext.lookup(JMS_FACTORY);
          > topic = (Topic) jndiContext.lookup(TOPIC);
          > topicConnection =
          > topicConnectionFactory.createTopicConnection();
          > topicConnection.start();
          > // The transacted parameter should be ignored in the context of a
          > container tx
          > topicSession = topicConnection.createTopicSession(true,
          > Session.AUTO_ACKNOWLEDGE);
          > topicPublisher = topicSession.createPublisher(topic);
          > textMessage = (TextMessage)inMessage;
          > topicPublisher.publish(inMessage);
          > // this is illegal in a container transaction
          > topicSession.commit();
          > topicConnection.close();
          > }
          > catch (JMSException je)
          > {
          > throw new EJBException(je);
          > }
          > catch (NamingException ne)
          > {
          > throw new EJBException(ne);
          > }
          > }
          >
          > public void ejbRemove()
          > {
          > }
          > }
          >
          >
          >
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          >
          > <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          > JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          >
          > <ejb-jar>
          > <enterprise-beans>
          > <message-driven>
          > <display-name>MessageBean</display-name>
          > <ejb-name>MessageBean</ejb-name>
          > <ejb-class>MessageBean</ejb-class>
          > <transaction-type>Container</transaction-type>
          > <message-driven-destination>
          > <destination-type>javax.jms.Queue</destination-type>
          > </message-driven-destination>
          > <security-identity>
          > <description></description>
          > <run-as>
          > <description></description>
          > <role-name></role-name>
          > </run-as>
          > </security-identity>
          > </message-driven>
          > </enterprise-beans>
          > <assembly-descriptor>
          > <container-transaction>
          > <method>
          > <ejb-name>MessageBean</ejb-name>
          > <method-name>*</method-name>
          > </method>
          > <trans-attribute>Required</trans-attribute>
          > </container-transaction>
          > </assembly-descriptor>
          > </ejb-jar>
          >
          >
          >
          >
          >
          >
          >
          >

Balance in transaction currency error for AUC settlement

I was trying to perform AUC settlement and hit Balance in transaction currency error. When i open up the line items I found that there are 2 sets (duplicate) of data posted to the depreciation area. The second set is with value 0 except depreciation area 01 posted as 100000EUR.
so now i have 2 line with 100000EUR for depreciation area 01. I guess this is the main culprit of generating the error Balance in transaction currency.
I'd glad if someone can tell me why they are 2 sets of data generated in line items? I only post the vendor invoice against the AUC once.
Or perhaps am I heading to the right way in identifying the root cause of this issue?
This is part of the AC010 course part of asset accounting that teaching on AUC aasets.
Any positive reply is welcomed!
I attached the line item image. Please note that there are some lines hidden for dep area beyond 03. and all are with amount 0.
[Line Item Image|http://www.bnl.com.my/photos/aucsettle.jpg]
Edited by: Kam Weng Leong on Dec 13, 2009 5:00 AM

I was trying to perform AUC settlement and hit Balance in transaction currency error. When i open up the line items I found that there are 2 sets (duplicate) of data posted to the depreciation area. The second set is with value 0 except depreciation area 01 posted as 100000EUR.
so now i have 2 line with 100000EUR for depreciation area 01. I guess this is the main culprit of generating the error Balance in transaction currency.
I'd glad if someone can tell me why they are 2 sets of data generated in line items? I only post the vendor invoice against the AUC once.
Or perhaps am I heading to the right way in identifying the root cause of this issue?
This is part of the AC010 course part of asset accounting that teaching on AUC aasets.
Any positive reply is welcomed!
I attached the line item image. Please note that there are some lines hidden for dep area beyond 03. and all are with amount 0.
[Line Item Image|http://www.bnl.com.my/photos/aucsettle.jpg]
Edited by: Kam Weng Leong on Dec 13, 2009 5:00 AM

Container-managed / bean-managed transaction demarcation

I am trying to make sure I understand container-managed and bean-managed transaction demarcation and in particular where you have one bean calling another bean. What happens where one of the beans has container-managed transaction demarcation and the other bean-managed transaction demarcation. In fact the initial question to ask is, is this allowed?
Lets use an application scenario to illustrate the issue. The application has a payment transaction. Payments can be received in one of two ways:
1. As a payment at a branch where the individual payment is processed on a client application and resulting in the processing of a single payment transaction.
2. As a batch of payments received from a bank containing, potentially, thousands of payment transactions.
The proposed implementation for this uses two session beans. The first is a Payment session bean that implements the business logic as appropriate calling entity beans to persist the change. The second is a BatchPayment session bean. This processes the batch of payment transactions received from the bank. The BatchPayment reads through the batch of payments from a bank calling the Payment session bean for each payment transaction.
Lets look at the transactional properties of both session beans. In order to support the client application the Payment session bean can implicitly enforce transactional integrity and is therefore set to container-managed transaction demarcation. However the BatchPayment session bean will want to explicitly specify transaction demarcation for performance reasons. The transactional "commit" process is relatively expensive. When processing a large batch of transactions rather than performing a commit after every transaction is processed we want to perform the commit after a number of transactions have been processed. For example, we may decide that after every 100 transactions have been processed we commit. The processing will have a shorter elapsed time as we have not had to perform 99 commit processes. So the BatchPayment session bean will want to explicitly specify its transaction demarcation and will therefore be defined with bean-managed transaction demarcation.
How would this be implemented? A possible solution is:
Payment session bean implemented with container-managed transaction demarcation with transaction scope set to Required.
BatchPayment session bean implemented with bean-managed transaction demarcation with transaction scope set to Required.
When the client application is run it calls the Payment bean and the container-managed transaction demarcation ensures the transactional integrity of that transaction.
When a BatchPayment process is run it explicitly determines the transaction demarcation. Lets say that after every 100 Payment transactions (through 100 calls to the Payment session bean) have been processed the BatchPayment bean issues a commit. In this scenario however we have mixed container-managed and bean-managed transaction demarcation. Hence my original question. Can container-managed and bean-managed transaction demarcation be mixed? If not how is it possible to implement the requirements as described above?
Thanks for any thoughts.
Paul

BatchPayment session bean implemented with bean-managed transaction demarcation with transaction scope set to Required.Didn't quite understand this sentence.... if it's BMT it has no declarative transaction attributes such as "Required"....
Anyway, first of all I'll have to ask, Why at all would you want to commit in the middle of the business method? to get as much through as possible before a potential crash? :-)
Can container-managed and bean-managed transaction demarcation be mixed?Yes, of course. Just remember that the "direction" you are refering to ->
a BMT SB that propagates it's transaction to a method in a CMT SB that is demarcated with "Required" is the simplest case. If it were "reversed", or for that matter any BMT that might be called within an active transaction context must perform logic to manipulate the transaction state. For instance(and most common case), checking to see if a transaction is active and if so not to do anything(just use the one that is already active).
If not how is it possible to implement the requirements as described above?You could also implement this scenario with CMTs all the way through. your BatchPayment SB could consist of two methods, one (say, execute(Collection paymentsToExecute) ) with "Supports", and another(say executeBatchUnit(Collection paymentsToExecute, int beginIndex, int endIndex) ) with "RequiresNew".
then have the first just call the other with indexes denoting each time a group of payments.
Still, it does seem more suitable using BMT for these kind of things.....
Hope this helped....

ECC Transaction iView Error on Browser Resize

Hello.
I have created hundreds of SAP ECC Transaction iViews in the portal. After doing some testing, I realized that any time a browser window is modified when an ECC transaction iView is within display, the resize causes the transaction iView to refresh. Upon refreshing, the transaction throws error or works as if the user submitted the transaction on the backend, instead of just remaining in the same state.
For instance, if you have an SAP Transaction iView to an ECC system for tcode QM01 and it is accessible through the Detailed Navigation, this iView can be opened either in its own browser window, or within the desktop inner page. If configured to pop-up in a new browser window and you click or drag to resize the browser window, the transaction refreshes, and throws the error: "Fill in all required entry fields." This is the same error that is thrown in ECC when a user submits the transaction with no data. Similarly, if you have the iView configured to open within the portal framework and you click on the transaction it opens in the desktop inner page. If you maximize/restore down the browser window displaying the portal, the transaction refreshes within the desktop inner page and throws this same error, like it was submitted.
It happens with every ECC transaction iView that I have created, but does not happen with SRM IAC iViews, Web DynPro iViews, or SUS functionality iViews. This leads me to believe it is a problem in ITS. Does anyone know what is going wrong, or how to fix this?
Thanks for any help!
Alexa

Hi,
Super admin has permission for end user for all the iViews. So he will be able to view the iView. As mentioned, please check if the end user permission is given for the end user to access the iView. Also check if the permission is given for that particular system. To check permissions, go to System Administration -> Permissions -> Portal permissions -> Portal Content. Check for iView and system that you have created.
Regards,
Harinin S

Get error from SQL AGENT: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024

I am running SQL Agent that executes an SSIS process from sql server1. The SSIS process executes its SQL/tables/sp’s against another sql server2.
I get an error after adding data flow tasks with transaction supported within a sequence with transaction required. The error, “The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction
manager has disabled its support for remote/network transactions"
Prior to adding this sequence everything was working from sql agent, and there were other sequences with oledb destinations.
Everything works when running within SSIS Package.
I see this article on similar issue,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bfa2569-8849-4884-8f68-8edf98a9b4fe/problem-to-execute-a-package-and-tasks-with-a-certain-transactionoption-property-i-need-help?forum=sqlintegrationservices
“I had similar issue and solved by setting the following on both the machines. Allow Remote Clients, Allow Remote Administration,
Allow Inbound Clients, Allow Outbound Clients, and TIP are enabled in Component Services/My Computer/Properties/MSDTC/Security Configuration.”
I don’t want to remove transaction required for the “Remove Duplicates from Staging” sequence.
Anyone seen this?
Greg Hanson

DTC was running on remote computer. The problem was it was no longer accepting transactions from remote servers. This was in SSIS so I had to turn to "Transaction Supported" for all Data Flow Transactions.
Greg Hanson

Yum install Oracle-Validated Transaction Check Error:

Doing a yum install oracle-validated command with CentOS 5.3 and got these errors:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /etc/issue from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /etc/issue.net from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /etc/redhat-release from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /usr/share/eula/eula.en_US from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /usr/share/firstboot/modules/eula.py from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /usr/share/firstboot/modules/eula.pyc from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
file /usr/share/firstboot/modules/eula.pyo from install of enterprise-release-5-0.0.17.x86_64 conflicts with file from package centos-release-5-3.el5.centos.1.x86_64
Error Summary
Did the yum update work? Should I procede with the oracle install?
Thanks in advance

Hi Tom,
Could you please help me as im trying to install ORACLE OID 10.1.4.0.1 on OEL 5 n trying to use yum to load the default RMP
]# yum install oracle-validated
Loaded plugins: security
el5_oracle_addons | 951 B 00:00
primary.xml.gz | 1.6 kB 00:00
el5_oracle_addons 10/10
epel | 2.3 kB 00:00
primary.sqlite.bz2 | 2.0 MB 00:05
el5_ga_base | 1.1 kB 00:00
Setting up Install Process
Parsing package install arguments
No package oracle-validated available.
repo file :
[el5_ga_base]
name=Enterprise Linux $releasever GA - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/0/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1
[el5_u1_base]
name=Enterprise Linux $releasever U1 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/1/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u2_base]
name=Enterprise Linux $releasever U2 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/2/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u3_base]
name=Enterprise Linux $releasever U3 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/3/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_addons]
name=Enterprise Linux $releasever - $basearch - addons
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_oracle_addons]
name=Enterprise Linux $releasever - $basearch - oracle_addons
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/oracle_addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1
best regards,

J1IEX: Balance in Transaction Currency ERROR

All SAP Gurus,
While doing J1IEX: Balance in Transaction Currency ERROR occurs.
This happens only when figures are not even in case of capital goods credit.
Which SAP Note to be applied so that, system will accept odd figures too.
Regards,

Hi Rajan, Check the following threads :
Balance in transaction currency
Re: Balance in transaction currency Error

Balance in transaction currency error

Hi Friends,
In order to ressolve "Balance in transaction currency" error during J1IIN, we have applied oss notes 1018071 & 978186. However we are getting same promblem
Please help on this.

Hi shiv,
Kindly refer this threads,
Balance in transaction currency
Error : Balance in Transaction Currency
Error F5702 Balance in transaction currency VF01
Re: Balance in Transaction Currency
error in Balance in transaction currency
Balance in transaction currency
Thanks,
Swamy H P

Transaction Processor Error in View Pending Transactions

Dear All,
I am getting the Error: "Transaction Processor Error" in View Pending Transactions.
How can I identify due to what reason, this error had occured
because of this I am not able to close the inventory period for these transaction months..
and also I am having the following Error msg for another item in view Pending Transactions..,
How can I clear this ..?
Please update...
Many Thanks in advance....
Edited by: santark on Nov 10, 2009 6:46 PM

Hi,
This is not really and error. Oracle processes transaction in a batch. If one record will fail because of some error, other records/transaction in the batch fails with this error. For this error you really need to get the ERROR_EXPLANATION to find out the exact message as to why it is possibly failing. These can usually have their three flags reset and re-submitted as this error is usually attached to those records in a group where one of the records has been erred with one of the more severe errors.
I believe you can resubmit the transactions which are failed with the below script
Update mtl_material_transactions_temp
set      process_flag = ‘Y’,
     lock_flag = 'N',
     transaction_mode = 3,
error_code = NULL
Where organization_id = &org_id
Thanks,
Raghav

Transact RFC error

Hi Gurus,
I am getting one issue while loading the data thru infopackage.
While loading the data in 3.5 flow for some souce system it is taking long time
and givig me transact RFC error. I have checked the source system connectivity and it is fine.Although the status is yellow during the load but at the end of the load it turns to red and it gives me below mentioned error:
Missing data packages for No selection information arrived from the source s
Diagnosis
Data packets are missing from No selection information arrived from the source s. BI processing does not return any errors. The data transport from the source system to BI was probably incorrect.
Procedure
Check the tRFC overview in the source system.
You access this log using the wizard or following the menu path "Environment -> Transact. RFC -> Source System".
Error handling:
If the tRFC is incorrect, resolve the errors listed there.
Check that the source system is connected properly to BI. In particular, check the remote user authorizations in BI.
Kindly let me know your suggestion in this issue.
Thanks in advance.
Amit

Hi
This error would normally occur, if at the time of processing, the data packets get stuck
To check for stuck trfc follow the path
Environment -> Transact. RFC -> Source System
there, check if trfc recorded, then it means, it is stuck, slecect that particular record and press F6 to execute the LUW.
If this is not the case, check the job overview in the source system.
IF you find ARFCSTATE = loading/sysfail, it means the trfc is stuck ..
you can check the datapacket number from there, and try mannual update for those partiular data packets.
Or else, sometimes, the packet itself doesnt arrive in BW, because of connection problem during the processing of few packets, ands later when you check, it seems fine.
In such cases simply repeat the load
Hope this helps
Regards
Shilpa

Transaction Control Error

Hi,
i am getting "Transaction Control Error" in newly created Client while executing any tcode. can you please give the solution for this.
venkat

Hi,
i copied from 000 client to new client. it was successfully completed. After that if execute mm01 or mm02 transactions this type error i am getting. Can you please give the solution..
venkat

Transaction processor error in Misc. Transaction

Hi,
When i perform Misc transaction in Inventory module then system shows “Transaction processor error” at save Transaction.
can anyone guide about the error.
Regards,
Aman

HI Raghav,
Thanks for the note ids.
I have read all 3 metalink notes & solution written in note id: 412110.1 is applicable but that is for 11i and i am working in R12.0.4. It is some sort of bug.
i.e "the existing items can be fixed by unchecking and checking again the costing enabled flag and the inventory asset value flag."
But there is one problem with the solution that when i try to uncheck both flags system shows error:
"APP-INV-0557: You can't update this field when:
- On-hand quantities, pending & uncosted transactions exists"
Now there are onhand quantities exists for the item and i cannot uncheck or check the costing and asset value flag. Its working only for items with no onhand quantities as number of items are increasing and i can't clear on-hand quantities for every item.
Plz guide if i can avoid error and process misc. transactions without removing onhand quantities.
Regards,
Fahd

"Balance in transaction currency" Error in Depreciation Posting Run-AFAB

Hi,
We are having unit testing going on during ECC6.0 upgrade.I am getting following error while posting Asset Depreciation -AFAB.
Balance in transaction currency
Message no. F5702
Diagnosis
A balance has occurred in transaction currency 'AUD' with the following details:
Exchange rate '00', amount ' 467.00-' and currency key 'AUD'.
The data in the transaction currency were transferred from the calling application.
System Response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.
Please advise what can be the reason of this issue.
Thanks & Regards,
Prince Kochhar

Hi shiv,
Kindly refer this threads,
Balance in transaction currency
Error : Balance in Transaction Currency
Error F5702 Balance in transaction currency VF01
Re: Balance in Transaction Currency
error in Balance in transaction currency
Balance in transaction currency
Thanks,
Swamy H P

Transaction Demarcation Error

Similar Messages

Maybe you are looking for