ITS transactions do not process!

Hello,
we are using SRM 4.00 with internal ITS (Web AS 640). The developement system is set up and works correct.
Now I'm setting up the integration system and noticed, that all ITS transactions apart from bbpstart do not work.
For example: when I go shopping (bbpsc02) the bbpstart-screen is copied and shown in the area, where normaly the shopping application (bbpsc02) is processed. All ITS transactions react like this.
When I test a service like bbpsc02 from SICF the screen is processed correct.
Has s.o. an idea?

Hello Yann,
TWPURLSVR was the right hint. Thank you very much!!!
Greetings
Dieter

Similar Messages

Receiving Transaction Processor not processing PENDING records

Good day,
I have pending records sitting in the RCV_HEADERS_INTERFACE, RCV_TRANSACTIONS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE. The PROCESSING_STATUS_CODE is set to "BATCH". But when I run the Receiving Transaction Processor nothing happens. The records are still in the interface tables as pending and the PO_INTERFACE_ERRORS table does not get populated with errors.
Kindly help by suggesting what I'm doing wrong. Why is the processor not picking up the records?
Thanking you in advance.

How are you trying to receive the items. Is it through iProcurement or Core Purchasing Forms?

MIRO - Transaction saved but not processed

Hello,
I have problem with MIRO :
Invoices are saved but after few minuts a message indicates that there are not processed.
What can be the reson please ?
Thanks

Do you get an FI document and can display it? If not, Check SM13 and see whether there are any entries for your user-Id and try to re-process through here.
Is there a short-dump - transaction code ST22?
Another option might be there is a block entry available (sm12) you might need to delete.
Pl revert and let us know how you go w investigation.
Regards
Hein

IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
    In data selection tab, I given date as from 2002 to 2003
    In Update tab, I selected update mode as Initialize Delta process-               without data transfer and Uncheck Update Data in master   system immediately
   In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.

Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier.

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

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.

Job getting cancelled for 'Chain not processed for date-2007031920070318' ?

Hi All,
We have 2 process chains running only on weekdays - one for sales and the other for billing. A cancelled job is created for one of the process chains with the job log message as 'Chain not processed for date-2007031920070318' for the not run days whereas the other does not have any issues though the same monitor job program runs for both. The difference is only in the variant but nothing much other than that its maintained for 2 different chains.
   We also debugged the monitor job program. It basically does nothing other than displaying messages depending on the status of the chain log.
Please let me know your suggestions as to why it happens.
Thanks,
krishna

it is also giving following error message:
Caution: Program has changed
Caution: At time of termination, Active source code no longer available and after above two statements its giving sign "?" before every statement in below manner:
024300 ?     lit_ekpo_dummy1[] = it_ekpo[].
024310 ?     DELETE lit_ekpo_dummy1 WHERE ebeln NE tab1-ebeln.
024320 ?     DESCRIBE TABLE lit_ekpo_dummy1 LINES count01.
024330 ?
024340 ?     REFRESH lit_ematn_dummy[].
024350 ?     lit_ematn_dummy[] = lit_ematn[].

Error: failed to prepare transaction (could not satisfy dependencies)

Hi,
I was going to install a winff package (a GUI front end to ffmpeg for converting between video formats), but when I ran yaourt -S winff and tried to install it refused because it isn't for the x86_64 architecture. So I decided to edit the PKGBUILD and perhaps try to force it anyway, but then I saw that the PKGBUILD is actually getting the precompiled RPM package and as I checked, while there was no precompiled 64bit version of the RPM there was one for a deb version that is offered on winff site.
Since deb's are just archives I ended up, after a few tries, with this PKGBUILD which uses ar and tar commands to get to the binaries inside of the amd64 deb:
# Contributor: yugrotavele <[email protected]>
# Modified by libervisco for x86_64
pkgname=winff-amd64
pkgver=0.42
pkgrel=1
pkgdesc="GUI for ffmpeg"
url="http://www.winff.org"
license=('GPL')
depends=('ffmpeg gtk gdk-pixbuf')
makedepends=('')
source=('http://winff.googlecode.com/files/winff-0.42-amd64.deb')
arch=('x86_64')
md5sums=('1febf5fd19fa76bdc1da06d3e6c4d3b8')
build() {
ar vx winff-0.42-amd64.deb
tar xvzf data.tar.gz
install -Dm755 $startdir/src/usr/bin/winff $startdir/pkg/usr/bin/winff
install -Dm755 $startdir/src/usr/share/winff/presets.xml $startdir/pkg/usr/share/winff/presets.xml
install -Dm755 $startdir/src/usr/share/winff/winff.png $startdir/pkg/usr/share/winff/winff.png
So what I basically do is run yaourt -S winff and when it asks whether I want to edit it, I edit it and replace the original PKGBUILD content with above.
It successfully runs the build() commands, finds and installs the dependencies, but when it's time to install the actual new winff package is throws up this:
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
I don't get it. It installed all the dependencies (and I even checked whether winff works in one of the earlier tries when I manually installed gdk-pixbuf when the binary asked for it). What does it want now?
Here is the whole process:
[daniel@memeport ~]$ yaourt -S winff
==> Downloading winff PKGBUILD from AUR...
Comment by: yugrotavele on 20080518 [04:36:56]
A nice GUI frontend for ffmpeg.
First Submitted: Sun, 18 May 2008 04:28:31 +0000
Last Updated: Mon, 30 Jun 2008 04:23:08 +0000
winff 0.42-1 (Unsupported): GUI for ffmpeg
==> winff dependencies:
- ffmpeg (already installed)
- rpmextract (already installed)
==> Edit the PKGBUILD (recommended) ? [Y/n] ("A" to abort)
==> ----------------------------------------------
==>y
Please add $EDITOR to your environment variables
for example:
==> Edit PKGBUILD with: (replace gvim with your favorite editor)
==> Edit ./PKGBUILD with: gedit
==> winff dependencies:
- ffmpeg (already installed)
- gtk (already installed)
- gdk-pixbuf (package found)
==> Continue the building of 'winff'? [Y/n]
==> ----------------------------------------------
==>y
==> Building and installing package
==> Making package: winff 0.42-1 (Tue Jul 1 21:34:12 CEST 2008)
==> Checking Runtime Dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...
Targets: gdk-pixbuf-0.22.0-4
Total Download Size: 0.00 MB
Total Installed Size: 0.70 MB
Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [############################################################] 100%
(1/1) installing gdk-pixbuf [############################################################] 100%
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading winff-0.42-amd64.deb...
--2008-07-01 21:34:13-- http://winff.googlecode.com/files/winff-0.42-amd64.deb
Resolving winff.googlecode.com... 64.233.187.82
Connecting to winff.googlecode.com|64.233.187.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1383594 (1.3M) [application/x-archive application/x-debian-package]
Saving to: `winff-0.42-amd64.deb'
100%[=============================================================================>] 1,383,594 191K/s in 7.4s
2008-07-01 21:34:21 (183 KB/s) - `winff-0.42-amd64.deb' saved [1383594/1383594]
==> Validating source files with md5sums...
winff-0.42-amd64.deb ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
x - debian-binary
x - control.tar.gz
x - data.tar.gz
./usr/
./usr/bin/
./usr/bin/winff
./usr/share/
./usr/share/doc/
./usr/share/doc/winff/
./usr/share/doc/winff/copyright
./usr/share/doc/winff/winff.pdf
./usr/share/doc/winff/README.txt
./usr/share/doc/winff/README-Icons.txt
./usr/share/doc/winff/README-Presets.txt
./usr/share/doc/winff/changelog
./usr/share/applications/
./usr/share/applications/winff.desktop
./usr/share/winff/
./usr/share/winff/winff.png
./usr/share/winff/presets.xml
./usr/share/winff/languages/
./usr/share/winff/languages/winff.es.po
./usr/share/winff/languages/winff.nl.po
./usr/share/winff/languages/winff.fr.po
./usr/share/winff/languages/winff.pb.po
./usr/share/winff/languages/winff.tr.po
./usr/share/winff/languages/winff.de.po
./usr/share/winff/languages/winff.zh.po
./usr/share/winff/languages/winff.it.po
./usr/share/winff/languages/winff.pt.po
./usr/share/winff/languages/winff.pl.po
./usr/share/winff/languages/winff.bg.po
./usr/share/winff/languages/winff.po
==> Tidying install...
-> Removing info/doc files...
-> Compressing man pages...
-> Stripping debugging symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: winff (Tue Jul 1 21:34:22 CEST 2008)
==> Continue installing 'winff'? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>y
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
==> WARNING: Your package is saved in /tmp/winff-0.42-1-x86_64.pkg.tar.gz
I tried doing it without changing the package name to winff-amd64, but same thing happens. What's going on?

Ahh man, and that's it! It works.
I'm just wondering now how can I contribute this PKGBUILD to AUR, but I can read that in the wiki too.
Thanks!

Getting "JTA transaction is not present" error while updating db table.

Hi All,
In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
OPMN logs:
<2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Thanks in advance.

I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
Is this happening for all BPEL instances or some of them get thru succesfully ?
Are you EVER updating that particular row of your table ( before/after) ?
-Shishir

Regarding Rough FISCAL YEAR VARIANT NOT PROCESSED

Hi Experts,
I am loading data from 2lis_03_um to 0IC_C03,While executing DTP i am getting error as Rogh FISCAL YEAR VARIANT NOT PROCESSED.
Can anyone please suggest me how to resolve the issue.
Thanks
Laxman

Hi,
Use the settings here:
transaction code SPRO
SAP Netweaver
Business Intelligence
Settings for BI content
Trande Industries
Retailing
=> set fiscal year variant
regards,
pascal

[Urgent] Error: The transaction is not active

Our process encounters some errors when the execution time takes longer than normal, e.g. 5mins. Any help is much appreciated.
Process Flow:
The flow consists of 3 process, 1 long-lived process and 2 short-lived processes, let say process A, B and C
Long-lived process A call short-lived process B,
and then, short-lived process B call another short-lived process C.
There is a loop inside process B, so that process C would be called several times.
* Both invocation policy have been tested, including "Do not wait for response" and "Wait for response".
Problem:
Everything work fine when the whole process is within a short-period of time. e.g. 1-2 minutes
However, when the process takes longer, e.g. > 5mins, we got some error message in the sever log.
Server log:
2011-08-18 18:43:11,625 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNe w(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.Transa ctionCallback) throws com.adobe.idp.dsc.DSCException, causedBy:
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImp le.java:223)
at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:411)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doRequiresNew(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:188)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEUtil.invokeAction(PEUtil.java:886)
at com.adobe.workflow.engine.SynchronousBranch.handleInvokeAction(SynchronousBranch.java:510 )
at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:888)
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2792)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:697)
at sun.reflect.GeneratedMethodAccessor1076.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 73)
at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy200.asyncInvokeProcessCommand(Unknown Source)
at com.adobe.idp.workflow.dsc.service.ProcessCommandExecutorService.invokeProcess(ProcessCom mandExecutorService.java:55)
at sun.reflect.GeneratedMethodAccessor3010.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
at com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker.invoke(WorkflowDSCInvoker.java:154)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassi vationInterceptor.java:53)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:227)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:378)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doSupports(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:165)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEInvokeProcessCommand.execute(PEInvokeProcessCommand.java:126)
at com.adobe.workflow.workadapter.WorkflowCommandExecutionUnit.execute(WorkflowCommandExecut ionUnit.java:22)
at com.adobe.idp.dsc.workmanager.adapter.ManagedAsynchronousWorkAdapter.run(ManagedAsynchron ousWorkAdapter.java:70)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Unknown Source)

Hi Paul,
Thank you for your advice.
It seems that it is not a bug of Adobe Livecycle, but some kind of configuration problems. Since the problem does not occurs when the process implementation time is short, such as 1-3 minutes.

Certificate issues Active Directory Certificate Services could not process request 3699 due to an error: The revocation function was unable to check revocation because the revocation server was offline. 0x80092013

Hi,
We have some problems with our Root CA. I can se a lot of failed requests. with the event id 22: in the logs. The description is: Active Directory Certificate Services could not process request 3686 due to an error: The revocation function was unable to
check revocation because the revocation server was offline. 0x80092013 (-2146885613). The request was for CN=xxxxx.ourdomain.com. Additional information: Error Verifying Request Signature or Signing Certificate
A couple of months ago we decomissioned one of our old 2003 DCs and it looks like this server might have had something to do with the CA structure but I am not sure whether this was in use or not since I could find the role but I wasn't able to see any existing
configuration.
Let's say that this server was previously responsible for the certificates and was the server that should have revoked the old certs, what can I do know to try and correct the problem?
Thank you for your help
//Cris

hello,
let me recap first:
you see these errors on a ROOT CA. so it seems like the ROOT CA is also operating as an ISSUING CA. Some clients try to issue a new certificate from the ROOT CA and this fails with your error mentioned.
do you say that you had a PREVIOUS CA which you decomissioned, and you now have a brand NEW CA, that was built as a clean install? When you decommissioned the PREVIOUS CA, that was your design decision to don't bother with the current certificates that it
issued and which are still valid, right?
The error says, that the REQUEST signature cannot be validated. REQUESTs are signed either by itself (self-signed) or if they are renewal requests, they would be signed with the previous certificate which the client tries to renew. The self-signed REQUESTs
do not contain CRL paths at all.
So this implies to me as these requests that are failing are renewal requests. Renewal requests would contain CRL paths of the previous certificates that are nearing their expiration.
As there are many such REQUEST and failures, it probably means that the clients use AUTOENROLLMENT, which tries to renew their current, but shortly expiring, certificates during (by default) their last 6 weeks of lifetime.
As you decommissioned your PREVIOUS CA, it does not issue CRL anymore and the current certificates cannot be checked for validity.
Thus, if the renewal tries to renew them by using the NEW CA, your NEW CA cannot validate CRL of the PREVIOUS CA and will not issue new certificates.
But it would not issue new certificates anyway even if it was able to verify the PREVIOUS CA's CRL, as it seems your NEW CA is completely brand new, without being restored from the PREVIOUS CA's database. Right?
So simply don't bother :-) As long as it was your design to decommission the PREVIOUS CA without bothering with its already issued certificates.
The current certificates which autoenrollment tries to renew cannot be checked for validity. They will also slowly expire over the next 6 weeks or so. After that, autoenrollment will ask your NEW CA to issue a brand new certificate without trying to renew.
Just a clean self-signed REQUEST.
That will succeed.
You can also verify this by trying to issue a certificate on an affected machine manually from Certificates MMC.
ondrej.

Email/print in status "Not processed" when RFQ is published

Hello,
We are running SRM 5.0.
We have set up the event schema for BUS2200 (RFQ) to react on events: PUBLISHED, PUBLISHED_AGAIN etc. And assigned the event schema to RFQ's transaction types, eg BID.
However, when an RFQ is published, the email is not sent to vendor (whose default medium is MAI) or printed on vendor's default printer (if the medium is set to PRN). The output log under bidder/bids tab shows something like :
Status: Not processed
Medium: Print
When I clicked on the action button "Output pushbutton", the status would be changed to "Successful" and the email would be sent or the print job would be printed then.
I have checked the PPTTRIGG table and all the entries in there are of DISPATCH = 1 or 4. Not 3, which seems to indicate an "immediate processing".
My question is how I would configure the system so that the email/print when the RFQ is published could be processed immediately.
Thanks.

Hello Masa,
I realized it as well. I was then a little puzzled why SRM didn't allow "immediate processing" for the "processing time" parameter in the action definition. Do you know if there is a particular reason for that?
Thanks,

In F-51 transaction was not posted,& due date field for advance payment VEN

1. In F-51 transaction was not posted.
In the above T-code I want to tranfer Invoice amount (RE) to special GL debit retention money payable the following error was throwing,
Balancing Field "Profit Center" in the line item 001 not filled.
2. For advance payments for vendors due date field is not appearing in document entry screen. How can I see due date field in document entry screen.
In OB41 I changed the field status for posting key 29 in payment transations I made due date field required, but it is not appearing due date field in document entry screen, while posting transaction.
Please advise on this.
Regards

Hi thru f-51 u cannot post the transaction here u can enter first line item and select process open item and post it and the base line date is already entered in invoice document based on that one the advance amount is adjusted u con't enter that base line date at the time of advance payment and also the payment terms are maintained in vendor master based on that on also due date is calculated i hope it will be helpful.

Idoc in 53 status but not processed completely. Missing authorisation error

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
Thanks
Deepthi.

done.

ITS transactions do not process!

Similar Messages

Maybe you are looking for