AGIS Inbound 'Transaction Status' changes to error on clicking Approve

Hi,
AGIS inbound 'transaction status' changes to error on clicking Approve or Apply button? how to find what is that error as I am not able to find any error message.
What are the causes for this error ?
I manage to generate the outbound transaction. When the recipient has received and approve, it shows an error under - Transaction Status and in the outbound side it shows Batch Status as Error.
Can some one help to to find out the way to fix it.
Thanks in Advance,
Thejas

Something might have gone wrong in the Workflow. Please check the metalink document 785167.1
Thanks,
John.

Similar Messages

Inbound delivery status change

Hi,
i have a situation where in the inbound ASN status changes from C to B,after a return delivery is done in MIGO (mvt type 122)against the goods receipts.
is there any way to prevent the inbound deliveries from opening up?
we are using ECC 6.0.
Any assistance will be highly appreciated

Hi Ram,
I have came accross this sitation as well.
Previously, MIGO won't update the deliveries statuses. That way
we did not have that tricky situation. However, in ECC6, it is possible to post
partial GR via MIGO and delivery is updated also. It cannot get
solved via customization, you may consider in case you really to check
the possibility via your own code implementation.
Best Regards,
Christian Rosa

Problem with Restricted Recruiter Requisition Status Change Approval Proces

Hello,
Our company is having a problem with Recruiters recieving any approval notifications for requisitions where the status change is performed by someone logged on as a Restricted Recruiter. The approval notification never appears in the Recruiters approval page. The Restricted Recruiter is able to submit the request without any problems.
I was hoping that someone could help point me in the right direction so that I may begin troubleshooting this.
Thanks for your assistance.
Ryan

I have been doing some digging on this matter on E-Recruiting workflow and have discovered transaction SWI2_FREQ (Work Items per Task), very useful. Upon running this utility I found 8 pending approval request tasks. I double clicked on the task to show the workflow status of each task.
I double clicked on one of the request for status change tasks for a requisition which took me to the approval request for status change of Req ########. Here I clicked on the activities tab selected the activities tab, selected the activity Approval request for status change of Requisition ######## then clicked on the execute icon.
Doing this opened up a new web browser and prompted me to login. Using the correct login credentials for this environment I click the login button and promptly recieve the error message...
Error in Web service execution
E:SWF_HTTP:050 TS51807979
At this point I am unsure of where to go...
Any help would be appreciated.
Ryan

While Changing the status system gives error

Dear Experts,
In Solution Manger, While changing the status from Tcode SE38 with Program CRM_SOCM_SERVICE_REPORT system gives error.
Document 8000002519 refused for technical reasons: ERROR_FREE
Message no. SOCM_ACTION_LOG203
Diagnosis
The status value cannot be changed.
The document may no longer be modifiable as a result of its status, or it may be being edited by another user.
System Response
This change transaction is skipped during report processing.
Procedure
Analyze the corresponding document during transaction processing and perform the status change manually if necessary.
Also if i select the status as in process, then it executes sucessfully. Please help me in this.
Ramesh Jaiswal
9867936636

Hi Ramesh,
Pls check your SP level because till SP17 this (CRM_SERV_REPORT) Tcode is not present
I just checked.
So it seems this is availabe only after SP18.... we can use the above report.
Kindly confirm once you solve your problem.
Dirk
Can you please tell us a document which wil tel us what technical things have been changed in this new SP18.for e.g the source for this information.
Regards
Prakhar

Error Inbound IDoc - Status 51

Hi,
i am new in working with SAP and I am trying to integrate an inbound IDoc type WPUBON via WE19 transaction, l solved all the issues related with ports and partner profiles(they were the first errors). But when I want to check if the process has been done well with the WE05 transaction I get two error messages, both of them with status 51:
The transactions for intermediate document 0000000000052247 could not be written
Message no. /POSDW/INPUT004
Document flow: Error reading model data of object relationship se
Message no. /POSDW/CORE028
Diagnosis
Error reading model data of object relationship se
System Response
The document links could not be updated.
Procedure
Contact your system administrator.
Procedure for System Administration
Check the format of the document links transferred to the POS Workbench.
Thank you very much in advance!!
Best regards,
Ander
Edited by: AAnder on Nov 3, 2010 11:46 AM

General process for a correct IDOC infrastructure is:
Create RFC destination --> SM59 (You can point to local machine for tests)
Create RFC port to process IDOC --> WE21 with the RFC create before
Create FILE port to process IDOC --> WE21
Create LOGICAL SYSTEM (BD54) --> IDOC2FILE
Define partner in WE20 with partner type "LS" --> WE20 ... add message
RECEIVER port ( created in WE21 )
FROM WE19 GENERAte IDOC with LOCAL SYSTEM as sender And FILE PORT as receiver
WE19 is FOR TEST...
tell me if you can understand, sorry for my english ....

SAP JIT Inbound - The external status change you requested is not planned

Hi All,
I am getting an error as "The external status change you requested is not planned" while creating JIT call in JIT inbound.
I have configured actions and external status.
What would be the problem??
Help me
Thanks,
Anbazhagan

Hi Lakshmipathi,
Thanks for your reply.
I missed out some configuration. Now the issue is solved.
Thanks,
Anbazhagan E

While trying to change a BOM with transaction CS02, a runtime error appears

While trying to change a BOM with transaction CS02, a runtime error appears.
In intial screen he entered material ,plant BOM usage and date valid from after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
Developer trace
ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
Error Code SAPSQL_ARRAY_INSERT_DUPREC.
Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
Function HandleRsqlErrors Line 775.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end RX_RFC
In sm21
Perform rollback
Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
     Short dump "090618 110101 donalda 11557 " generated
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
       Occurred on     18.06.2009 at   11:01:01
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RKE_WRITE_CE4__BPS1" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
The exception must either be prevented, caught within the procedure
"RKE_WRITE_CE4__BPS1"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
"RKE_WRITE_CE4__BPS1"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

Hi ,
you are getting beacuse u are trying to do mass update to database.
Please check that below note are applicable to your system.
Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
Note 869534 - AFS MRP doesn't work properly with all BOM item categories
Thanks Rishi Abrol

To create the follow up transaction automatically on status change in sap crm?

To create the follow up transaction automatically on status change in sap crm? If yes, how to make the setting for this?

Hi vishal,
As per the requirement transaction type is activity(ACTI) & sales order(TA). when the take order objective is complete system automaticaly craete a new activity of tele sales call or metting with wholesaler.
this is requirement of client.
now i am already create all type of transaction types of activity & sales order & create follow up transaction also. i have doam already create action profile also but when i am assign this action profile to transaction & try to create an sales order no follow up transaction could be create automatically. i think the condition is not right so please help me out in this. what should be the start & schedulec condition for this scenerio

Error "Status change from READY to COMMITTED is not allowed"

Dear experts,
once again SAPs workflow environment drives me crazy with mysterious error messages.
Some time ago I posted a question here concerning the problem that I cannot put back a workitem by using function module SAP_WAPI_PUT_BACK_WORKITEM due to a lock on this workitem which has been set right after it has been double clicked in the business workplace workflow inbox:
[How can I put back a workitem before I'm back in the business workplace?;
Since I do not want to dequeue the lock for the workitem in my application (where the user finds the appropriate detail information along with the function buttons for approval, rejection and F3/BACK) I tried it with calling a POPUP_TO_CONFIRM ("Do you want to put back the workitem?") directly from within the BO-method, right after returning from the FM that called my application. From here (the popup then shows in front of the business workplace instead of the application) the locking doesn't seem to be a problem any more! But whatever I do after the users decision to put the WI back - calling the FM SAP_WAPI_PUT_BACK_WORKITEM or trying to leave the method with macro EXIT_CANCELLED - leads to the error message "Status change from READY to COMMITTED is not allowed" and the workitem changes to status ERROR, too. This message seems to be bull***t, since the status of the item is supposed to go back to READY.
Does anybody have experience to help me on that ?
Thanks in advance
regards
Andreas

Hello Andreas,
Ah, sorry, there was so much talk about user decisions that I assumed you were using a standard decision task.
Still, I would be extra careful of changing the way workflow usually works because you have an unknown target audience that are based on the standard.
The standard SAP philosophy is quite simple: cancel/F3 or do nothing and it stays reserved. If you do not want it reserved, you need to perform an action. This is based on a majority of processes: in most cases when you execute a work item you will also be the one who is going to completed it. Replacing it is the lesser used of the two alternatives, therefore it is the only one that requires an action on the part of the user.
Again, this is intended as constructive input. Strange quirks and unusual behaviour tend to add a black mark to software if they do not make things easier to use. In many environments users are not even aware of the reserve/replace business, so there you would be adding an additional layer of complexity.
Personally I would find an exit popup annoying as a regular workflow user - regular decisions can be approved with one click, or I can back out with a single click if I need to make a phone call or look up some info before approving - but with this new-fangled thing I've got an extra button to click and an extra thing to think about. This is especially the case in a payment approval scenario where you may have users in some departments who may approve hundreds of payments each week.
My suggestion would be to leave it like that. By all means put an option into the user decision to put it back or to 'un-reserve' it (and loop round if the user chooses it). That way you are adding value and not clicks.
Cheers,
Mike

Inbound idoc ( shipment) - Status change

Hi Experts,
I will be getting an inbound idoc containing tracking number of the shipment from an external agent.
I have to update this tracking number in the shipment and change the status of 'shipment Start' and 'Shipment End' to be completed.
1. Is this status change feasible ?
2. If so can you please guide me both to update tracking number & status .
Thanks
Seema

Hi Martin,
Thanks for the response.
Can you tell me which basic type will suit for this among SHPMNT01 to 05. I need to get the tracking number from any of the segments.
thanks
Seema

Process chain failed with Error-Status Change of Process ABAP ZL321NIMIMUUT

Hi,
process chain got failed with Error --**Status Change of Process ABAP ZL321NIMIMUUT
Save Status and Trigger Events if Appropriate**

Hi Neha,
When we do the repeat after right click then we are getting this messege"--**Status Change of Process ABAP ZL321NIMIMUUT
Save Status and Trigger Events if Appropriate**"
I have come to know that there is one ABAP programe when we go to manage varient.
ABAP Programme"ZBWR_ZMYYNNINOH_CSV_CHANGE"

BDOCs in status E01 - Technical Error

We are using CRM 7.0 with service order.
We have BDOCs that created automatically after creation of service order or changing in BP details and got stuck in the system and were not processed (SMW03) .
The BDOCs types:
BUPA_MAIN
BUS_TRANS_MSG
These BDOCs entered into queues in SMQ2 in status ready.
In order these BDOCs will be read automatically, we registered the queues which started with CSA* in SMQR.
Unfortunately, the BDOCs still not processed and now in status E01 u2013 Technical Error (incomplete).
The messages are for each type (BUPA_MAIN and BUS_TRANS_MSG respectively) are:
u201CCould not determine module name: BUPA_MAIN GENKEY: REP_GET_RECIPIENTu201D
u201CService that caused the error: SMOH_REPLICATION_WRAPPER_MSGu201D
Could not determine module name: BUS_TRANSACTION_MESSAGE GENKEY: REP_GET_RECIPIENTu201D
u201CService that caused the error: SMOH_REPLICATION_ERAPPER_MSGu201D
It is important to mention that these BDOCs were not deleted in order not damage data that suppose to be uploaded to the BI.
Due to security issues, we cannot provide connection to the system.
Please advice
Best regards,
Hanoch Aharoni

Hi Hanosh
Please see bleow, this is an extract from very helpful document attached to note 768503 for the E01 bdocs status:
Description
Technical error. If any of the flow services fail a technical error is raised. Possible reasons
for that error are:
- Data inconsistencies (e.g. between CRM and CDB)
- Implementation and programming errors
- Missing functionality (implementation problems)
Inbound
s-flow
(SI1)
Detection:
Select BDoc message, click button u2018Errorsu2019 and u2018Classical Datau2019
Possibly the inbound s-flow definition (transaction SMO8FD) is not correct
(services do not exist or have syntax error) or the rejection handling in case
of validation errors is not correct.
Solution:
- If no validation errors and no receiver errors exist, retry to process the
message. Otherwise (if no retry possible) correct the error, send the changes
from the sender site (usually Mobile Client) again if possible or request the
data from the leading system to the different receivers and mark the original
failed BDoc message to u201Cdeletedu201D.
Inbound
m-flow
(MI0)
Detection:
Select BDoc message, click button u2018Errorsu2019:
- No validation function defined for BDoc type
- Technical error occurred: Service (usually validation service), BDoc type <>,
BDoc <>
Solution:
Check in table SMW3BDOCIF if the validation module is entered for the
BDoc type. If no retry is possible correct the error, request the message from
the sender system and set the original failed BDoc to u201Cdeletedu201D.
If the error occurs during the call of the validation module, start the
debugging mode, restart the BDoc processing and put a breakpoint at the
validation module. This requires knowledge in the implementation of the
validation module (and application logic). Look for notes related to that
function module, if this is a SAP standard function.
E01
Outbound
m-flow
(MO1)
Detection:
Select BDoc message, click button u2018Errorsu2019:
- Technical error occurred: Service <>, BDoc type <>, Message <>
- Service that caused the error: <>
Solution:
Find a solution to the errors that occurred, for example through SAPNet Note
search or opening a SAPNet problem message on the corresponding
application component. The right application component can be found in the
corresponding properties of the package where the service is implemented
(use transaction SE37 to display the attributes of that function module).
Possibly there is something wrong inside the Mobile Bridge or in the following
services of the s-flow (like CDB update).
Re-process the message (this is allowed for testing purposes; be careful in
the case of a production system, especially if the data in the BDoc message
is not current) or request the data from the sender or from the original system
(this is usually possible for master data but not always for transactional data).
==================================================================
Best regards
Christophe

Solman 7.1 - CRM WebClient UI - custom field mandatory on status change

Hi
I've got a question and I'm not sure if it's possible.
Basically i have created a custom field in CRM WebClient UI and I have added this field to my Z configuration. This works fine.
Now, I'm wanting to make an error to appear if this field is blank (hasn't been filled in) when the status of the transaction type changes to a specific status.
i.e. if "custom field" is BLANK when SMTM changes to Closed, then error appears
I know the field can be made mandatory, but this particular custom field won't be filled out straight away. Therefore I want the check to occur when the document is closed. Can this be done via PPF Conditions? Or is ABAP/enhancement the only way?
Thanks
Shaun

Hi,
For customizing crm web ui, you must need AET or EEWB tools. Best Practices for SAP CRM Web UI Customization - CRM - SCN Wiki
but try by using the standard sap note 1772650 - ST710:You can save a message even though mandatory fields are not filled in. which can set certain warning message for custom fields or not and the other relevant 1931783 - Incident can be saved without filling mandatory fields
Please check.
Thanks
Jansi

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3

Hi,
I have query how to have the JTA transaction in SEI(Service endpoint interface) generated by WSDL.
I have a MDMListener (using MDM API) which looks for a recordchange in MDM repository which needs to be send to PI7.1 via soap request.
1) I had imported the WSDL from ESR(PI) and generated outside-in proxy.
2) Created ejb3.0 stateless session bean using NWDS
3) Created web service client application by generating the WSDL again (by Generate client)
4)Added a method callPI()with Service and i set the context with endpointaddress property as the soap location of the sender agreement configured in PI7.1.
The damean thread listener(EventDispatcher) looks for MDM record change and it calls the method callPI() from ejbsession bean by lookup to transfer the record to PI7.1 system via webservices(web method). I hit the below error.
Exception com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Status of ( SAP J2EE Engine JTA Transaction : 06223ffffffa20048fffffffe ) should be active, but it is STATUS_COMMITTED = 3.
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronizationWithoutStatusChecks(TransactionImpl.java:672)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronization(TransactionImpl.java:641)
at com.sap.engine.services.ts.transaction.TxLevelSynchronizations.addSynchronization(TxLevelSynchronizations.java:118)
at com.sap.engine.services.ts.transaction.TxManagerImpl.registerSynchronization(TxManagerImpl.java:829)
at com.sap.transaction.TxManager.registerSynchronization(TxManager.java:303)
at com.sap.engine.messaging.runtime.j2ee.sapengine.SAPTransactionManager.registerSynchronization(SAPTransactionManager.java:126)
at com.sap.engine.messaging.impl.util.tx.TxController.<init>(TxController.java:83)
//Method in the ejb stateless session bean
@WebServiceRef (name="DistributeMasterDataService") DistributeMasterDataService service;
@RelMessagingNW05DTOperation(enableWSRM=true)
public void callPi(DistributeMasterDataRequestType req) {
port.distributeMasterDataOutA(req);// the distributeMasterDataOutA is the method available in SEI..Here is the issue on JTA
For the first time the message(req object)transmits to the PI successfully,but for the second call i hit this JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3.
I tried chanding the transactionmanagement from container to bean.
@TransactionManagement(value=TransactionManagementType.BEAN)
@TransactionAttribute(value=TransactionAttributeType.REQUIRES_NEW)
I wanted to know how can i have the JTA transaction status in SEI(service enpoint interface)java method distributeMasterDataOutA.Since it is an interface i dont know what annotation can be used.
If its possible i can try this UserTransaction,
http://help.sap.com/saphelp_nw04/helpdata/de/f6/7a8df922db4ab79342b46c48dac7d0/content.htm
ut.begin() & ut.commit(),so that everytime this method is called it will treat as a new transaction..
Let me know if you need more details??,Any idea provided would be great.
Thanks
Sabarinathan
Edited by: Sabarinathan Selvaraj on May 7, 2009 12:31 PM
Edited by: Sabarinathan Selvaraj on May 7, 2009 12:32 PM

Hi,
May be i have not mention the issue clearly.Let me know mention the issue with details.
I have a MDMListener (using MDMPI) which looks for a recordchange in MDM repository which needs to be send to PI7.1 via soap request.
1) I had imported the WSDL from ESR(PI) and generated outside-in proxy.
2) Created ejb3.0 stateless session bean using NWDS
3) Created web service client application by generating the WSDL again (by Generate client)
4)Added a method callPI()with Service and i set the context with endpointaddress property as the soap location of the sender agreement configured in PI7.1.
@WebServiceRef (name="DistributeMasterDataService") DistributeMasterDataService service;
     @RelMessagingNW05DTOperation(enableWSRM=true)
     public void callPi(DistributeMasterDataRequestType req) {
port.distributeMasterDataOutA(req);// the distributeMasterDataOutA is a method available in SEI
For the first time the message(req object)transmits to the PI successfully,but for the second call i hit this JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3.
I tried chanding the transactionmanagement from container to bean.
@TransactionManagement(value=TransactionManagementType.BEAN)
@TransactionAttribute(value=TransactionAttributeType.REQUIRES_NEW)
I wanted to know how can i have the JTA transaction status in SEI(service enpoint interface)java method distributeMasterDataOutA.Since it is an interface i dont know what annotation can be used.
If its possible i can try this UserTransaction, ut.begin() &   ut.commit(),so that everytime this method is called it will treat as a new transaction..
Let me know if you need more details??,Any idea provided would be great.
Thanks
Sabarinathan

AGIS Inbound 'Transaction Status' changes to error on clicking Approve

Similar Messages

Maybe you are looking for