Resubmit in B2B

Hello All,
I added follwoing configuration in my tip.properties, but the resubmit doesn't happened as I expected. And I have not received any emails once resubmit failed.
#Resubmit
oracle.tip.adapter.b2b.data.ReSubmit.HostmailId = [email protected]
oracle.tip.adapter.b2b.data.ReSubmit.InboundResubmission = false
oracle.tip.adapter.b2b.data.ReSubmit.Mailport = 25
oracle.tip.adapter.b2b.data.ReSubmit.Mailserver = mymail.com.au
oracle.tip.adapter.b2b.data.ReSubmit.MsgTableSize = 500
oracle.tip.adapter.b2b.data.ReSubmit.ReSubmitCount = 3
oracle.tip.adapter.b2b.data.ReSubmit.ResubmitIntervals = 1,2,5
oracle.tip.adapter.b2b.data.ReSubmit.ResubmitWithInterval = false
Is there any thing wrong? Thanks.
Regards,
Kerr

Hi Anuj,
My email works fine, because our BPEL notification use a same outcoming configuration and works all the time.
Here is the log.
The message was rejected at 14:03:35. According to my configuration, resubmit should happen around 14:05, 14:06 then 14:08. But nothing happened during this time.
Regards,
Kerr
--------- Error -------------------------
2009.05.14 at 14:03:35:324: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
2009.05.14 at 14:03:35:324: Thread-11: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
2009.05.14 at 14:03:35:324: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 14:03:35:324: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.05.14 at 14:03:35:324: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 14:03:35:324: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendConnectionRefused] HTTP connection is refused.
A remote host refused an attempted connect operation.
2009.05.14 at 14:03:35:537: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:03:35:537: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.05.14 at 14:03:35:540: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.05.14 at 14:03:35:540: Thread-11: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2009.05.14 at 14:03:35:541: Thread-11: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
***** REQUEST MESSAGE *****
Exchange Protocol: AS2 Version 1.1
Transport Protocol: HTTP
Unique Message ID: <PO:511250:0:10000043@NSWHB2BDEV>
Trading Partner: PACCOMTEST
Message Signed: RSA
Payload encrypted: 3DES
Attachment: None
***** REQUEST MESSAGE *****
2009.05.14 at 14:03:35:541: Thread-11: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Exit
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 14:03:35:541: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
2009.05.14 at 14:03:39:505: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Active exclude design true
2009.05.14 at 14:03:39:505: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:03:39:506: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2009.05.14 at 14:03:39:507: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2009.05.14 at 14:03:39:507: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Quiescing exclude design true
2009.05.14 at 14:03:39:507: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:04:09:512: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Active exclude design true
2009.05.14 at 14:04:09:512: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:04:09:512: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2009.05.14 at 14:04:09:513: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2009.05.14 at 14:04:09:513: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Quiescing exclude design true
2009.05.14 at 14:08:39:576: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Active exclude design true
2009.05.14 at 14:08:39:576: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:08:39:576: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2009.05.14 at 14:08:39:577: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2009.05.14 at 14:08:39:578: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Quiescing exclude design true
2009.05.14 at 14:08:39:578: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.05.14 at 14:08:39:578: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2009.05.14 at 14:08:39:578: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2009.05.14 at 14:09:09:584: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Active exclude design true

Similar Messages

Error while resubmit the transaction in Oracle 10g B2B

Hi All,
I am facing the below error while resubmitting the transactions
bash-3.00$ java oracle.tip.adapter.b2b.data.ReSubmit
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/adapter/b2b/data/ReSubmit
bash-3.00$
Regards
sekhar

Hi Sekhar,
Make sure that you are setting the environment first by running Midtier_Home\ip\install\setenv.bat OR Midtier_Home\ip\install\setenv.sh (according to your OS). Run the resubmit command after executing this setenv file.
Regards,
Anuj

B2B-51507- Payload validation error - 11.1.1.7 Latest Version

Anuj/Nitesh (B2B Gurus)
I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B. Once the message is posted to B2b It is throwing the following Error.
But I am passing all the mandatory and Optional Parameters.
Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
How to map Internal-Properties in XSLT.
Oracle B2B Payload Validation exception
Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
Disabled the Validate flag in the Partner Agreement for the B2B Document.
Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
Scenario - 2 (Error )
Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
Error
Id
C064016C14103689486000005559CD14
Message Id
C064016C14103688C7F000005559CD0F
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
ABC
Receiver Type
Name
Receiver Value
TEST123
Sender
ABC
Receiver
TEST123
Agreement Id
EDI_850_tpa_Lt7763342564515893374
Agreement
XXX_EDI_X12_4010_850_Outbound
Document Type
850
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
9/9/2013 10:48
Receive Time Stamp
9/9/2013 10:48
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
5471
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
Collaboration Id
C064016C14103688E1A000005559CD13
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
Error Brief :^M
Error reporting limit exceeded.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
Error :^M
Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
Thanks
Rao.

Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi.

B2B PositionalFlatFile Inbound Operation

B2B Experts,
I am working on a scenario with B2B in which i would be receiving the file through B2B (inbound operation).
The file is positional flat file, i have created the document guidelines (ecs) using the spec generator in oracle b2b editor
and generated the xsd from the ecs...now i have created the document definition in b2b console by selecting the PositionalFlatFile
document protocol and after selecting the protocol,version,type. for the document definition; i have given the xsd and ecs files
and in the identification tab;i have given the identification value as HDR, start position 1 and end position 3. In the listening channel
i have created a new listening channel and selected the Generic-file 1.0 as the message exchange protocol and gave the path in the folder name location.
And in the partners, i have created a new partner, created the agreement and deployed the same. Now when i drop the file name like NewPartner_12345.te, the file is getting picked up.
But the BPEL instance is not getting triggered.If i go to the report status, the state is MSG_COMPLETE.If i go to wire message, the state is COMPLETE. If i go to application message, it is showing the time details and all,
but the domain name, composite name, composite version, reference name, service name and resubmit count; these fields are empty. If the BPEL instance would have been triggered, these values would have been there. Why is my BPEL
instance not getting triggered ? Did i do anything wrong?
Please help me...
Thanks,
Naresh

sorry for the multiple threads...
please help me at this thread...
B2B Customer Protocol Inbound Operation
Thanks,
Naresh

Resubmit and notification in case of error

Hi,
In Oracle B2B if there is error while sending outbound or Inbound message, how can we resubmit the messages automatically.
Also is there any way to send the notification in case of error while sending the messages.
Thanks,
Arun Jadhav

Hi Arun,
As far as Resubmittting is concerned, there are two ways by which you may resubmit a message in 11g -
1. Through UI (http://blogs.oracle.com/oracleb2bgurus/2009/09/what_do_i_like_most_in_11g_-_r.html)
2. Through Resubmit command line utility (http://blogs.oracle.com/oracleb2bgurus/2009/09/b2b_commandline_utilities.html)
Notification is not an in built mechanism in Oracle b2b. You may like to implement the same using BPEL. As Nitesh mentioned, by default exception/error message is enqueued to IP_IN_QUEUE and has the recipient name b2berroruser. You may develope a BPEL process listening for error messages (recipient name=b2berroruser), and perform required notification processing (EMail, SMS, Fax etc.) in that.
Regards,
Anuj

Tracking documents in B2B

Hi,
There are a couple of questions pertaining to B2B that I have
1) Is it possible in B2B to keep track of documents based on the Interchange Control Number (ISA13 segment). Say if a TP was to send documents control number 1000,1001,1002 and misses to send the one with 1003, is it possible for B2B to identify that a raise an error or warning?
2) Can we use a resubmit facility to resubmit a document if a 997 is not received within a specified time. In our case we have 810 documents going out and if we dont get a response within a specified time, resend the document.
Please let me know.
Thanks,
Emil.

Answers are in line.
Hi,
There are a couple of questions pertaining to B2B that I have
1) Is it possible in B2B to keep track of documents based on the Interchange Control Number (ISA13 segment). Say if a TP was to send documents control number 1000,1001,1002 and misses to send the one with 1003, is it possible for B2B to identify that a raise an error or warning?
You should do that as a custom solution based on the InstanceMessageUtil or DB tables.
2) Can we use a resubmit facility to resubmit a document if a 997 is not received within a specified time. In our case we have 810 documents going out and if we dont get a response within a specified time, resend the document.
This is a custom solution using resubmission feature in maual mode. You can do the timeout as a custom feature. Let me know we can work with you to build this.
Please let me know.
Thanks,
Emil.

Getting "IPEnqueueError end" while using ReSubmit utility

Hi Gurus,
When I tried to to resubmit the failed message using resubmit utility, I am getting "IPEnqueueError end" as output. I have pasted the output of this test. I am using file system. Please suggest.
D:\OracleB2B-Installation\OraHome_Cache\ip\install>java oracle.tip.adapter.b2b.data.ReSubmit AC18E5411208A6D52790000013154280
Resubmision started for message IDAC18E5411208A6D52790000013154280
Message Id to resubmit : AC18E5411208A6D52790000013154280
getWireMessageID AC18E5411208A6D53B200000131542F0
Agreement Name : Test_Agree_Multiple_Duns
refToMsgId !!!!!!!!!null
ACTION:rqRequestIncidentReport;SERVICE:bcRequestIncidentReportv1
Sender :PG receiver :BTGS actionName :ACTION:rqRequestIncidentReport;SERVICE:bcRequestIncidentReportv1 docType :rqRequestIncidentReport_DT docRevision :1.0 direction :Outbound ConversationId :null
Enqueue the Message
IPEnqueueError start...
conversationId : null
replyToMsgID :
C:\DOCUME~1\V05E4~1.003\LOCALS~1\Temp\ReSubmit_AC18E5411208A6D527900000131542807
030.xml
IPEnqueueError end.

Hi Ramesh,
Thanks for your prompt reply,
Have changed the tip.property ReSubmit.InboundResubmission as FALSE.
Also since i'm trying to re-submitt more than one messages i'm using the command
java oracle.tip.adapter.b2b.data.ReSubmit "2009/04/24 06:06" "2009/04/24 06:24" TPName
But the above command is giving the error mentioned below.
Rsubmission with 3 argument > startdate, enddate and TPName
total number of Messages : 10
0 : individualMsgId : AC18FC3D120D6849E05000001CE64F90-1
Message Id to resubmit : AC18FC3D120D6849E05000001CE64F90-1
getWireMessageID AC18FC3D120D684998A000001CE64F60
Agreement Name : BT_Supplier_Agreement
SendMessage
Sender :E537Gateway receiver :PABSStest actionName :SendMessage
docType :SendMessage_BTWholesaleE537XML docRevision :1.0 directi
on :Inbound ConversationId :null
Resubmit feature for inbound is disabled. Please enable in tip.properties
IPEnqueue Event start...
Updated 0
oracle.jms.AQjmsException: JMS-204: An error occurred in the AQ JNI layer
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:308)
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1190)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1291)
at oracle.tip.adapter.b2b.data.ReSubmit.sendEvtMessage(ReSubmit.java:646
at oracle.tip.adapter.b2b.data.ReSubmit.beginResubmission(ReSubmit.java:
743)
at oracle.tip.adapter.b2b.data.ReSubmit.getMessagesForTimeRange(ReSubmit
.java:147)
at oracle.tip.adapter.b2b.data.ReSubmit.main(ReSubmit.java:123)
[Linked-exception]
oracle.jms.AQjmsException: JMS-104: Message Payload must be specified
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:285)
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:864)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1291)
at oracle.tip.adapter.b2b.data.ReSubmit.sendEvtMessage(ReSubmit.java:646
at oracle.tip.adapter.b2b.data.ReSubmit.beginResubmission(ReSubmit.java:
743)
at oracle.tip.adapter.b2b.data.ReSubmit.getMessagesForTimeRange(ReSubmit
.java:147)
at oracle.tip.adapter.b2b.data.ReSubmit.main(ReSubmit.java:123)
1 : individualMsgId : AC18FC3D120D684A0CE000001CE64FA0
Message Id to resubmit : AC18FC3D120D684A0CE000001CE64FA0
Error -: AIP-13004: A context has already been started
at oracle.tip.buslogic.common.ExecutionContextManager.startContext(Execu
tionContextManager.java:194)
at oracle.tip.buslogic.common.ExecutionContextManager.startContext(Execu
tionContextManager.java:566)
at oracle.tip.adapter.b2b.utility.InstanceMessageUtil.getInstanceMessage
s(InstanceMessageUtil.java:199)
at oracle.tip.adapter.b2b.data.ReSubmit.getMessageDetails(ReSubmit.java:
332)
at oracle.tip.adapter.b2b.data.ReSubmit.beginResubmission(ReSubmit.java:
731)
at oracle.tip.adapter.b2b.data.ReSubmit.getMessagesForTimeRange(ReSubmit
.java:147)
at oracle.tip.adapter.b2b.data.ReSubmit.main(ReSubmit.java:123)
Exception while getting the messages using InstanceMessageUtility: java.lang.Nul
lPointerException
Should we add property in tip.properties or is there anything i'm missing out.
Regards,
Cema

Oracle 11g B2B resubmission commanline utility

Hi,
Do we have the commandline resubmission option available with Oracle 11g b2b server to resubmit a application message or a wire message?
Regards,
Bp

Hello Bp,
In 11g, Resubmission is UI based and is a manual operation. Please refer section "16.1.3 - Resubmitting Messages from Oracle B2B" at below link-
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10229/bb_reports.htm#CHDCDDIE
Also refer-
http://blogs.oracle.com/oracleb2bgurus/2009/09/what_do_i_like_most_in_11g_-_r.html
Regards,
Anuj

DPS Enterprise License for Apple's B2B Store

Hey everyone,
we developed an app and successfully tested it on our iPads via DPS. We aim to distribute the app via the B2B store from Apple and the tutorial PDF from Adobe tells me that we need an "Enterprise license" for DPS.
Our company uses Adobe Creative Cloud and I am wondering now whether this already means that we have an "Enterprise license" for DPS, as well?
Cheers,
Alex

No. It does not.

Error while importing a new CERT in oracle 10G B2B

Hi All,
I am trying to upload a new certificate in 10 G B2B server, its not updating a certificate, I am facing the below error while importing
Error
An error occurred when updating the certificate.
Error -: AIP-16001: The model validation engine failed due to an internal system error.
Error -: AIP-11052: Writing following objects: Certificate failed due to following constraint violation: CERTIFICATE. CAN NOT UPDATE UNVERSIONABLE OBJECT IN A VALIDATED CONFIGURATION.
Note: Please help me in resolving this ASAP.
Regards
Sai

Hi Sai,
It seems you are updating certificate in a delivery channel which is being used in a validated (or may be deployed) agreement. Please retire/purge any deployed configuration which is using that delivery channel and also make sure no such agreement is in valid state(which is using this delivery channel).
Regards,
Anuj

Custom File Name Format in B2B Console

Hi,
Please let me know if we can have a customized File Name Format in the B2B Console for the X12 EDI/XML Files.
I have read the Oracle doc and only the following formats are mentioned:
%FROM_PARTY%
%TO_PARTY%
%DOCTYPE_NAME%
%DOCTYPE_REVISION%
%MSG_ID%
%TIMESTAMP%
Is there a way to have a PO# (From the Trading Partner Payload) in the filename format?
You help is appreciated.
Thanks
Priyanka G

no. It has the format which helps B2B in identifying the agreement

Dynamic filename in receiver AS2 adapter in B2B Add-on

Hello Experts,
Can you please let me know how we can put dynamic filename in the receiver AS2 adapter for B2B Addon on SAP 7.4.
Thanks
Saurabh

Hi Ryan / Experts,
Let me explain you in more detail.
In the receiver AS2 Communication channel, if I keep the Filename field as blank as shown below, then in the Mendelson inbox folder, a file is generated with the name "ASJAVA_DX5" which is my business component name.
If I fill the filname field for example with "CONTRL", then in the Mendelson inbox folder, a file is generated with the name "CONTRL".
This is my requirement because, suppose i trigger this interface "first time", a file with static name (ASJAVA_DX5/CONTRL ) would be generated in the inbox folder. If I trigger this interface "second time", since the file already exists with same name, it is not overwritten and I cannot check the output of 2nd trigger . Contents are not overwritten.
To solve this problem + as a general requirement, I wish to have this name to be dynamic, atleast with date+timestamp.
Can you please help.

Erro B2B de entrada

Olá Pessoal,
Não sou PI, e não tenho um aqui disponível no momento... por isso preciso da ajuda de um...rsrs
Estou com um erro no recebimento de NF-e via e-mail, meu B2B está configurado para receber e-mails com vários anexos, porém ele lê o PRIMEIRO XML válido e descarta o restante dos arquivos.
Está configurado para se comportar desta forma...
Porém, tenho um e-mail com três arquivos:
41110178956968002712550050000071344110034264-nfeProc.xml
41110178956968002712550050000071344110034264.xml
41110178956968002712550050000071344110034264.pdf
O que meu sistema deveria fazer era ler o primeiro XML válido e descartar o restante dos arquivos, porém ele não lê nenhum e na SXI_MONITOR ele dá um log de erro, porém como não so PI não consigo interpretá-lo:

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>Unable to find an inbound interface</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Na SXI_MONITOR:
Na coluna "Error Category" está a seguinte informação: IF_DETERMINATION
Na coluna "Error ID" está a seguinte informação: NO_IIF_CASE_ASYNC
Alguém poderia me ajudar por favor?
Muitíssimo obrigado,
Mateus.
Edited by: MATEUS PARREIRA GUIMARÃES on Feb 7, 2011 7:05 PM
Edited by: MATEUS PARREIRA GUIMARÃES on Feb 7, 2011 7:05 PM

Então Henrique,
Não sei, achei estranho por isso, não tem nada indicando...
Para ver se consigo ajudar a identificar vou lhe falar as pastas que tenho:
Interface Determination (Bandeirinha vermelha com erro: Sistem Error - Manual Restart Possible)
      SOAP Header
            Main
            ReliableMessaging
            Error
            HopList
            RunTime
            PerformanceHeader
            Diagnostic
            Trace
      SOAP Body
            Manifest
      Payloads
            MailMessage ( multipart/alternative;boundary="----=_NextPart_001_0004_01CBC
            MailAttachment-1 ( text/xml;name="41110178956968002712550050000071344110034
            MailAttachment-2 ( application/pdf;name="4111017895696800271255005000007134
            MailAttachment-3 ( text/xml;name="41110178956968002712550050000071344110034
Qual conteúdo você quer que eu envie?
Abs.
Mateus.

Processo B2B aguardando processamento em background - NFE 3.10

Boa noite,
após implementarmos a versão 3.10 da NFe todos os nossos e-mails de XML para nossos parceiros no GRC ficam aguardando que alguém clique no botão "Continuar processo B2B", só então eles são enviados.
Verificando o status do B2B constatei que ele apresenta o status "Esperando por processamento em background".
Alguém saberia por favor me dizer qual configuração esta faltando para que o envio fique automático?
Agradeço antecipadamente.
Helio Camargo

Helio,
Você pode agendá-lo de 1 em 1 minuto ou 5 em 5 minutos, vai de acordo com a disponibilidade de recursos (Background Working Process) que seu servidor possui.
http://help.sap.com/saphelp_nw70/helpdata/EN/4a/2d513897110872e10000009b38f889/content.htm
Em vários clientes onde passei, 5 minutos de intervalo entre as execuções já era suficiente.
Ele vai processar apenas os processos que estão com status inicial.
[]'s

Licença de SAP Netweaver Portal para Processo de B2B

Pessoal, boa tarde!
Alguém sabe me dizer se para utilizar o SAP Netweaver Portal para os processos de B2B é necessário comprar licença SAP ou está incluso no pacote onde a empresa compra o GRC e o PI?
Essa licença do PI que a empresa tem direito nessa compra, é somente para o processo de NF-e ou ela pode utilizar para integração com outros processos e sistemas?
No aguardo, obrigado.
Danilo

Danilo,
a licenca do NFE inclui:
- Netweaver runtime: licença Web AS (ABAP e Java) para rodar os componentes SLL-NFE e SLL-NFE-JWS.
- PI runtime: exclusivamente para utilizacao das interfaces do XI Content de NFE (SWCV SAP SLL-NFE 1.0).
Se vc precisa do PI para outras interfaces e/ou precisa do Portal para disponibilizacao de telas para clientes/fornecedores, essas licencas realmente estao fora da licenca do SAP NFE 1.0.
Att,
Henrique.

Resubmit in B2B

Similar Messages

Maybe you are looking for