Issue processing B2B message id from AQ in BPEL 11g
Hi,
IN 10g we used header variable to get the b2b message id for a message from AQ for inbound messages.
But when we migrated the BPEL to 11g, we are not able to retrive the B2B mesage id from header as the header variable is coming as null.
Let me know if we have a special way to handle this in 11g
Thanks,
Naveen Kumar T.
Did u chk with the properities tab in the receive activity? There is a property called b2b.messageId. you can try setting a pre-defined variable to this property.
Similar Messages
-
How to handle more than one message coming from an async BPEL in a sync BPEL process?
Here is the scenario,
Sync process A is calling an Async process B and Async process B is developed in such a way that it is returning more than one message to sync process A, how you will handle those messages in sync process A?As durga said, its a wrong design, you will have issues in real time. You wont get the response back most of the time. It can be otherway around, async is waiting for sync process.
Change your design or provide what is your use case below, we can think of which design suits you.
Thanks,
Vijay -
Issue in configuring Standby Database from Active database in 11g by RMAN
POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PMHello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg -
Mail message sent from PI comes with weird characters at Subject
Hi folks,
I've a Scenario where I must send a e-mail with some process data. To do that, I'm using emial Package to build the email Message.
The email Package XML Looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<ns:email xmlns:ns="http://sap.com/xi/XI/emial/30">
<Subject>HEY THIS IS JUST A LONG PLACEHOLDER SUBJECT TO HELP ME TO FIND OUT THE ISSUE OF MY MESSAGE</Subject>
<From>sender</From>
<To>rcpt</To>
<Content_Type>multipart/mixed; boundary="--JrSnBoUnDaRy"</Content_Type><Content>----JrSnBoUnDaRy
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Lorem Ipsum Dolor Sit ...
</Content></ns:email>
When the message arrives at my emialbox, the SUBJECT looks like this:
"HEY THIS IS JUST A LONG PLACEHOLDER SUBJECT TO HELP ME TO FIND OUT THE I SSUE OF MY emial MESSAGE"
Instead of:
"HEY THIS IS JUST A LONG PLACEHOLDER SUBJECT TO HELP ME TO FIND OUT THE ISSUE OF MY emial MESSAGE"
As you can see, there`s a "space" between the I and SSUE word. Looking closer at a Hex Editor I can see that I'm dealing with two special characters, first one LF (0xA) and later a TAB(0x9).
Doing some test I've found out that it just happens at the 72th position of the Subject string.
Is there any limitation for email fields while using email Package or Receiver email Adapter?
Thanks in advance,
José Nunes
Edited by: Jose Nunes on Mar 11, 2010 1:39 AMHi José,
SMTP has a line length limit and any long header line needs to be split in multiple lines, where each subsequent line must start with a single TAB.
It is strange that your mail client couldn't decode these multiple lines back to the original single line.
It might be that the mail adapter did not split the original line into valid multiple lines.
TCPGateway attached in the SOAP adapter note can capture the SMTP traffic and save it into a binary file.
You can check if the mail adapter correctly did the splitting.
This is not directly related to your issue. But you should avoid using the mail package if you have some format sensitive content. XML parsing inevitably changes the original physical representation (refer to whitespace handling in the XML specification). The issue can be avoided if the base64 encoding option is used within the content encoding. But you should switch to the adapter specific message attributes (ASMA) approach if you are configuring a new scenario.
Best regards, Yza -
Steps in processing of message b/w IS and AAE
Hi,
Kindly guide the steps involved in processing a message sent from Integration Server to Advanced Adapter Engine.
Thanks...Hi,
refer below link for betetr understanding how internal communictaion works
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
coming IS and AAE , AAE has all capabilties to process the message without IE(ABAP stack help).
Regards,
Raj -
B2B Arch - How the Messages move from the Servlet to IP_IN_QUEUE
Hi all,
I am having one basic architectural question.
We have defined the Host Trading partner with the Delivery channel having the URI for the transport as b2b/transportServlet. While creating the agreement between this host trading partner with the other remote trading partner, we are using the standard Internal delivery channel as B2B Inbound, as we are doing the inbound interface. So, whatever the Inbound messages is coming from the remote trading partner it will enqueued into IP_IN_QUEUE.
I referred some of the documents, to know the architectural details how the message come into the IP_IN_QUEUE. Those document says that b2b/transportServlet is the entry point for all the Inbound messages. Please correct me if I am wrong. I am more interested to know what are all the intermediate steps involved in the movement fo the message from the b2b/transportServlet to IP_IN_QUEUE. Basically how the message move from b2b/transportServlet to the IP_IN_QUEUE.Hi,
The transportServlet hand over the b2b message via RMI to the B2B Server. The B2B Server then process this message and delivers it to the IP_IN_QUEUE.
Eng -
Issue in Posting Messages from XI to MDM Console
Helloo Experts,
I am trying to Post the Message from XI to SAP MDM Console. When I am trying to post a test message it appears success in XI and it is not visible in SAP MDM.
But, the logs of MDM shows the Namespace and Interface were not registered.
Can any one tell me how I can register my Namespaces in the SAP MDM console?
From some of the previous topics I can understand that to register any interface I need to have the below details
Namespace :
Interface :
Bean :
Method :
I can provide the Namespace and Interface which I am using to post the messages to SAP MDM console.
Can any one tell me where do I can find the Bean and Method of the particular Inbound interface?
Cheers!
RamHello,
I think I clearly didn't explain my problem.
My Scenario is to post the message from SAP XI to one more External SAP system using HTTP cc (RFC destination)
Unfortunately that External System has been built on SAP MDM.
As per XI it is picking the message from the Source and successfully sending to the Receiver.
But at Receiver side we donu2019t see any message. But we can see certain Logs stating that
Error in processing the Inbound Message Exception:-Unable to Process the Message with Message ID u201C*********u201D with u201CNameSpace#Inbound InterfaceNameu201D is not Registered.
I want to know how to register the namespace and the Interface name of XI system ( my own system ) in External SAP System.
Cheers!
Ram -
I'm not able to message everyone from my iPad has anyone had this issue
I'm unable to message everyone from my iPad. Has anyone had this issue?
Unable to message everyone meaning that you cannot use messages at all? Certain contacts? Some details would really help.
iOS: Troubleshooting Messages - Support - Apple
iOS: Troubleshooting FaceTime and iMessage activation -
Error in inbound processing: EDI message - XML Gateway
Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda -
Unable to process inbound EDI docs from TP-multiple Host ID's,1 transaction
Issue:
Unable to process inbound EDI documents from trading partners
(Same doctype and revision, but diff receiver ID’s for host)
Host: ISA ID’s are HOSTA, HOSTB
Transaction: X12, 210, 5010
Trading Partner A: sends EDI document with these values
Interchange Sender ID: TPA
Application Sender's Code: TPA
Interchange Receiver ID: HOSTA
Application Receiver's Code: HOSTA
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner A : Process_210_Initiator It has
Interchange Sender ID as TPA
Interchange Receiver ID as TPA
Application Sender's Code: TPA
Application Receiver's Code: TPA
This creates a Process_210_Responder for HOST
It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code: HOSTA
Application Receiver's Code: HOSTA
Validated Agreement and deployed, Result is success and everything works fine until here
Note: B2B validates taking everything from Process_210_Initiator except the Interchange Receiver ID that it gets from the Process_210_Responder
New Trading Partner B also sends us an X12, 210, 5010 but he uses Receiver ID as HOSTB
Trading Partner B: sends EDI document with these values
Interchange Sender ID: TPB
Application Sender's Code: TPB
Interchange Receiver ID : HOSTB
Application Receiver's Code: HOSTB
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner B : Process_210_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code: TPB
Application Receiver's Code: TPB
This doesn’t create a new Process_210_Responder for HOST It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code : HOSTA
Application Receiver's Code : HOSTA
Validated Agreement and deployed, Result the document fails with error
Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid
Upon looking at the log file it fails, as the Interchange Receiver ID in data is HOSTB where as in Process_210_Responder it is setup as HOSTA
Work Around that we tried, but could not succeed
Create a new business action called Process_210_HOSTB, created a new Document Protocol Revision X12_5010_HOSTB,Created a doc type 210 version 5010 under that
Used this new Business action for Trading Partner B so the new setups look like this
Business action : Process_210_HOSTB
Operational Capability for Trading Partner B : Process_210_HOSTB_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code : TPB
Application Receiver's Code : TPB
This creates a new Process_210_HOSTB_Responder for HOST It has
Interchange Sender ID as HOSTB
Interchange Receiver ID as HOSTB
Application Sender's Code : HOSTB
Application Receiver's Code : HOSTB
Validated Agreement, but could not deploy as I was getting AIP-11016 SQL error , may be integrity constraint issue
Note: I was able to deploy this agreement if I change the Document Type from 210 to something else like 210_new, but since the document is EDI I can’t have the Document Type as anything except 210Ramesh,
Sorry for the delay , but this was the first thing I tried and it didn't work, I tried again just to be sure, it didn't work I am getting this error
When group Receiver ID didn't match
"Validation of Group parameters failed. Please verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in B2B"
In addition, when Interchange Receiver ID did not match
"Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid"
Here is the log file extract
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@12d8ecd
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1fa5e5e
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@497062
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 60DD87849FFE4147BFCEB66842A33298-26-1-4
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsOptFileBlob
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsFileBlob
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber sName = Interchange, controlNumber = 210011217
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber return = true
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {156BEDFC-931E-4923-840D-3AC0BAB670F2} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1b5c22f
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupReceiverID, val = [STMSLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupSenderID, val = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [GroupReceiverID] value = [STMSLCY] param = [SLCY] Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {6EE88EFC-B084-4FA8-8EE8-8C7BD397E9F1} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:073: Thread-10: B2B - (DEBUG) iAudit report :
Error Brief :
5082: XEngine error - Guideline look-up failed. -
Hi All,
I have done a BADI implementation for ME_PROCESS_PO_CUST and when I try to convert a PR to PO using ME59N in ECC u2013 AFS System I am getting below error message.
Data from Business Add-In ME_PROCESS_PO_CUST not transferred.
I am trying to populate certain PO fields ( ekko and ekpo ) from PR fields. But the above error occurs when I update the Ex Factory Date manual that is EKPO-J_3AEXFCM.
I am updating this in the method PROCESS_ITEM and what I found while debugging is in the class CL_PO_HEADER_HANDLE_MM, in the implementation of IF_FLUSH_TRANSPORT_MM~START, the contents of field u2018my_iteration_countu2019 keeps increasing and becomes 10 and raises this error.
I read few of the related questions raised by others in this forum and understood that this can happen if I try to change the field that is disabled ( greyed) in ME22N. But this field that I am talking about is enabled.
I also tried to move my code of populating the field EKPO-J_3AEXFCM from the PROCESS_ITEM to the enhancement point just above the user exit EXIT_SAPMMO6E_018 but still it doesnu2019t resolve the error.
(We donu2019t want to use User Exit and hence we are trying with BADIs or enhancement point.)
Can anyone please help me with this. I also found an OSS note 1334046 but not sure if that can resolve my issue.
Thanks in advance.
Ameesha.Hi Ameesha,
i think u need to implement the BADI ME_PROCESS_PO_CUST in SPRO settings.
SPRO>Purchasing>Business Add-in Purchasing-->BAdI: Enhance Processing of Enjoy Purchase Order
try this once.
All check this link.
[Error Message: Data from Business Add-In ME_PROCESS_PO_CUST not transferred;
Hope it helps.
Regards,
Raj -
How to get current suspended message ID from context
Hi all,
I'm trying to get the Suspended Message Id from my orchestration.
I don't want to get the this inside the orchestration, because that I already know how to do it.
I've search inside this forum and get a solution, but actually does not work.
Using this: Microsoft.XLANGs.Core.Service.RootService.InstanceId
(http://social.msdn.microsoft.com/Forums/en-US/95d2c9d9-5cbe-4bca-9cef-da7aba984d3c/how-do-i-access-instance-id-of-a-message-from-orchestration?forum=biztalkgeneral)
Also, I have searched in "all" properties of Microsoft.XLANGs.Core.Service.RootService and didn't had any luck
My goal?
I have a service that logs, to SQL, all errors in my biztalk applications. Right now is not saving the message id, and I do need. (I can easily change the method to receive the message id, but I'm trying to avoid that because I have 30 applications
using the same method/application).
Also, I have another service that is listening to all suspended messages.. In here I have the message Id (and other data) using WMI...
Now, I need to correlate both info..
Any help would be appreciated
Ricardo BessaHi,
Thanks for the reply. My answers inline.
I already understood the logic that you said and I'm working on it. However, if you have more good inputs to give, please do!
Thanks
Hi Ricardo,
Let us be clear with your requirement.
“I
have another service that is listening to all suspended messages.. In here I have the message Id (and other data) using WMI... ”
- What this “service” is? Is this some service external to BizTalk from where you want to access the detail of the suspended message? If so then you go to use some way similar to my earlier reply. When you want to access the suspended message details,
you got to access it from management db. The code which I have given in my earlier reply would do that. No other option in this case.
Yes, I am already doing that. I'm using a Windows service that is listening for all suspended messages in BizTalk. In this
windows service I can access to everything that I want (message Id; service type id; instance id; and many other properties...). My issue is not in here.
“Actually
when i call Microsoft.XLANGs.Core.Service.RootService.InstanceId I'm getting the property SendingOrchestrationID.”
- Are you try to access the message Instance ID from another child orchestration?
SendingOrchestrationID is the orchestration instance
ID where the message originated and you would get it when another orchestration (subprocess) which has been triggered by another orchestration (parent orch whose ID is
SendingOrchestrationID). Detail us about where and how
to you get this SendingOrchestrationID.
Because when you want to access “Suspended” Orchestration’s message instance ID, you can’t achieve it by calling it from sub-processes.
I'm using a external (custom) class library.
I have a custom log which tracks everything that goes in our BizTalk applications. When errors / warning I write that to a database table.
This is made in different times, so when I log the error to the database I need "something" that exists in my other service (MEssageID; service type
id; instance id; or other 'unique' property). Also, I don't want to change the log method, because (if I do that, I would need to change 30 applications).
That's why I'm looking for a 'global' property that I can use, without changing (a lot) my code.
When an Orchestration is suspended, it will be marked as “Suspended” in db and to get the messages associated with it, access the suspended Orchestration instance
ID from the db and use this ID from db to get its related contents/messages IDs.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.
Ricardo Bessa -
Error while processing audit message
hi
I'm running a reconciliation, and throws me the following error .
please help me
ERROR,28 Aug 2009 03:50:32,492,[XELLERATE.AUDITOR],Error while processing audit message
java.lang.NullPointerException
at com.thortech.xl.audit.engine.AuditEngine.processSingleAudJmsEntry(Unknown Source)
at com.thortech.xl.audit.engine.AuditEngine.processOfflineNew(Unknown Source)
at com.thortech.xl.audit.engine.jms.XLAuditMessageHandler.execute(Unknown Source)
at com.thortech.xl.schedule.jms.messagehandler.MessageProcessUtil.processMessage(Unknown Source)
at com.thortech.xl.schedule.jms.messagehandler.AuditMessageHandlerMDB.onMessage(Unknown Source)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.RunAsInterceptor.invoke(RunAsInterceptor.java:31)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.MessageDrivenConsumer.onMessage(MessageDrivenConsumer.java:347)
at com.evermind.server.ejb.MessageDrivenConsumer.processMessages(MessageDrivenConsumer.java:233)
at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:169)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)Seems like Article ID: 864906.1
Cause
The cause of this problem is, the entries in aud_jms table which were not processed
after run "Issue Audit Messages Task" schedule task are not complete audit entries.
Solution
1. Run the following query.
select IDENTIFIER from aud_jms where aud_class='UserProfileAuditor'
IDENTIFIER is the usr_key.
Save the output of above query into text file. lets say a.txt, the a.txt will looks like........
a.txt
122896 122896 122997 122999 122999
122986
122997
2. Delete the all entries (rows ) from aud_jms table
3. Run the GenerateSnapshot.sh/GenerateSnapshot.bat using following parameter.
GenerateSnapshot.bat -inputFile E:\OIM9101\XLServer\xellerate\bin\a.txt -missingSnapshots -username xelsysadm -password xelsysadm -numOfThreads 2
Where E:\OIM9101\XLServer\xellerate\bin\a.txt is the location of text file which is created in Step1.
4. Run the "Issue Audit Messages Task" schedule task -
Regarding Goods Reversal & Goods Issue Process for PO
Hi Experts,
Could you any one tel me what is Goods Reversal and Goods Issue process for PO...
How to create the FM & detailed Procedure Pls?....
Please any one tel me.......
Thanks & Reagards
HBHi Hans,
SOURCE : HELP.SAP
Purpose
Inventory Management uses this process in such a way that the goods issue posting is divided into two parts that run in separate systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The physical goods receipt takes place as usual.
Prerequisites
When using batch processing, the following prerequisites must be fulfilled:
Both the original and target systems have the same batch definition level.
The batch definition level is either the material or the client.
An ALE scenario exists for materials and classes (characteristics).
Unique batch numbers exist cross-system.
Batches can only be changed in their original system when they are not decoupled. From an organizational point of view, this must also lead to the batch status being changeable in a local SAP R/3 system. For example, this is impossible when transfer posting to a new batch and results in further actions, for example, relabeling containers, palettes and so on.
Characteristics
As for the purchase order in a one-system situation, the system should automatically post the material into the stock in transit at the receiving profit center and the corresponding Profit Center Accounting using intra-CC transfer prices at goods issue for the purchase order and the unchecked delivery. This requirement is valid for one-system situations as well as for two-system situations where there is an ALE interface. No internal billing document should be created.
In a two-system case, the receiving profit center should be derived at goods issue from the unchecked delivery. Profit Center Accounting then takes place with
Stock change transfer price to stock
Internal expense to internal sales
Internal clearing account to stock change transfer price.
Account determination in a purchase order for an intra-company-code transaction must be different from account determination in external transactions. Automatic GR/IR account clearing is required in both one-system and two-system situations.
The stock in transit must be visible in the receiving profit center.
The system must send a shipping notification at goods issue in one-system and two-system situations.
You need to create an invoice document for the internal and external trading statistics for cross-boundary deliveries as well as for customs purposes.
GR/GI slips are created.
Process Flow
Goods Issue Posting for Stock Transfers
The delivery triggers the goods issue in the issuing system.
The call contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.
The transaction (quantity and value updates) is selected using the movement type:
Movement Type
Function
641
Goods issue with UB logic (Creation of stock in transit at recipient, immediate value posting).
647
As 641, however the goods receipt line (movement type 101) is added automatically, so that the goods receipt is posted at the same time as the goods issue (one-step procedure).
You determine the movement type according to the schedule line category in Sales and Distribution. The goods issue for a cross-system stock transfer must be different from the integrated transaction. This is achieved by adding a new movement type.
You post quantities and values at goods issue in the same way as a goods issue for a sales order. That is to say, the quantity is posted in the supplying plant and the value is adjusted to that of the stock account. The offsetting posting is made to a clearing account. The known data from the delivery is copied to Accounting to balance the account where necessary.
The system creates a message to the appropriate receiving system for all items with reference to a cross-system purchase order. The system does not perform any validity checks on the recipients data before posting begins. Incorrect Customizing results in the update being terminated.
If a goods issue has receiving plants in different logical systems, an IDoc is sent for each system.
In order that the goods receipt is able to use the values on the receiver side, you must add the values used to post the goods movement, in particular the transfer prices, to the IDoc.
The logic for recognizing the profit center switch functions as follows: At goods issue, the system recognizes that the profit center of the issuing plant is different from the profit center of the receiving plant. The system derives the profit center node from the relevant profit center.
Data Transfer
The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.
Background Posting in the Receiving System
The goods receipt is posted in the receiving system using the IDoc. The interface receives the data from the goods issue in the supplying plant. The following processes now run at the recipient:
The system finds the update control for the GR part of the posting.
The goods movement is posted with the new movement type.
During valuation of the goods receipt, the system might, where necessary (UB logic), refer to the values (legal value and the value from the parallel valuation type, if you are using the transfer price function) from the IDoc.
The PO history is updated. The PO history is updated with the material document number from the second part of the GI posting. The GI document number is not stored in the supplying plant, because there is no way to display this document.
In two-step procedures the goods receipt is posted to the stock in transit.
Reversal
You can only reverse this goods issue for the PO using the cancellation transaction in SD. You cannot reverse the GI in Inventory Management.
The material document that is automatically created in the receiving system cannot be canceled. This reversal is triggered by the sending system (the actual reversal of the GI document takes place there) and transmits the data, including the reversal movement type, to the receiving system. No actual reversal is posted in the receiving system, because the material document number of the original document does not exist in this system. This scenario is applicable for cases where you use the two-step procedure (with stock in transit).
Distribution of Batch Master Data and Characteristics
The batch information is transported using the message category BATMAS.
When you create a cross-system goods issue, the system creates the corresponding IDoc using the message category BATMAS.
When the delivery arrives in the target system, the batch and all the information is already present in the system.
Changes to the batch data are also distributed using the message category BATMAS.
The batch can be decoupled in the receiving SAP R/3 system. This means that the batch can have a different status in the receiving system than in the original system. By setting an indicator at material level, you decide whether the batch can be decoupled or whether the batch and all its attributes are copied from the original system. "Decoupled" i.e. "locally independent" batches are no longer distributed from its own system.
The batch data does not need to be available before the physical goods receipt takes place. The goods receipt into the stock in transit does not usually refer to the batch unless you are working with batches with assigned active ingredient values.
If the GI cannot be posted for organizational reasons, for example because the goods cannot be loaded onto a truck until 10pm, then you can post the goods into the GR blocked stock. This stock is also non-batch-specific.
In cases where the GI IDoc arrives before the batch IDoc, then the GI IDoc can be subsequently posted by a periodically scheduled report (transaction BD87). A program like this exists in the SAP standard system. In Customizing for MM Inventory Management (activity Copy, Change Movement Types), you should make settings to define that manual creation of batches at goods receipt is not allowed.
Shipping Notification
The shipping notification is required in the receiving system due to its relevance for MRP. In this way, for example, a change in delivery date determined at goods issue is sent to the receiving system using the shipping notification. The shipping notification can also be used when posting the GR batches.
Reward if found helpfull,
Cheers,
Chaitanya. -
Queue processing of messages (files / idocs)
Hi,
We have 4 communication channels:
INT A
1 filesender (file)
1 filereceiver (idoc)
INT B
1 filesender (file)
1 filereceiver (idoc)
So, the issue is we need to process the messages in order. First, 2 files from INT A, next 1 file from INT B. The correlationship is the key.
Is any configuration possible for queue processing with no using of BPM?
Regards,hi,
yes you can set queue (EOIO) processing in both filesenders
and if you hava ERP (IDOC) on WAS 6.40 it can be processed
in this one queue
how to (IDOC queue processing part) described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
Maybe you are looking for
-
Why does the creative cloud application not load?
I am trying to upgrade lightroom 4 to 5, and i can't access it through the creative cloud app because it won't load. I even bought lightroom and photoshop creative cloud again, but it has to download through the cc app.
-
Hi- I'm working with some HDV media in a ProRes 422 HQ sequence and while the picture looks great on my computer but when spitting it out via my Canopus box to a TV I'm getting a horrible looking picture (my final output will be DVD). Looks like inte
-
I am connected to wifi, but 3G is still on the top??
We have two iPhone4's, my wifes and mine. I have wifi running on my phone, but my wifes doesn't want to connect to the same at home wifi we have. why? 3G costs me $$, where as wifi does not. Thanks, Blaine
-
Address book restore in Lion 10.7.2
For some reason iCloud just accidentally deleted all my address book items. I was then trying to restore them from a time machine backup. Before in Snow Leopard you were able to restore single addresses by opening time machine when the address book w
-
IPlanet/Sun ONE Directory Server 5.1 configuration help needed.
Hi from Finland. We have a SunFire 420 running Solaris 8. It has 2 network adaptors each configured to have separate IP addresses. Eventually these cards will be on quite separate networks... one for intranet users and one for the rest. What I am wan