Konard,
Just Checked the Seeburger Conversion log and it classifies this CONTORL 2 as an EDIFACT message.
but however will check on this on how to handle in B2B .
thanks again for your help
Br,
Manoj
Konard,
Just Checked the Seeburger Conversion log and it classifies this CONTORL 2 as an EDIFACT message.
but however will check on this on how to handle in B2B .
thanks again for your help
Br,
Manoj
Ok, then copy the CONTRL-3 to CONTRL-2 and cross check if this is working. CONTRL-3 and CONTRL-4 are pretty much the same.
Kind regards
Konrad
Hi Rahul,
The Java Mapping classes could be found at this location
D:\usr\sap\<SID>\J<inst num>\j2ee\cluster\apps
Regards,
Vikas
Hi Appala,
I tried creating the agreements again and without checking the Read from dynamic paramters it is working fine. When I am selecting read from dynamic header it is failing in the first scenario.
Also, I am mapping the document number using addDynamicHeader function but it is not reflecting in the monitoring(only the partners are reflecting). Is it due to read from dynamic header not working? But, in outbound it is working perfectly fine.
Please suggest how we can get document number for inbound scenarios.
Thanks,
Nidhi Srivastava
Hi Experts,
For User Defined Attributes Search Criteria(both inbound and outbound), if the search period is more than 24 hours, it shows "For searching with user-defined attributes, the performance is optimal when searching a short time period"
Is it a usual practice? or I am mistaking in some settings?
Please guide over this.
Thanks,
Nidhi Srivastava
It is just a warning. Consider it as a recommendation.
Searching through a lot of data can have an impact on performance and the query takes longer, obviously.
Kind regards,
Dimitri
Hi Dimitri,
It means warning is because of lot of data or there is some limit of 1 day?
If it is specific to 1 day then it's use is not that meaningful in our requirement, atleast it should be like one week so that if any missing orders/numbers are found we can search.
Thanks,
Nidhi Srivastava
Did you try it?
I guess data will be displayed, dispite the warning.
Ryan
thanks for your reply. we have used the same url path that you have provided.
But the partner was sending in non-encrypted MDN, while we have configured signed & encrypted MDN. So that's the reason MDN is always in "In Process". Once we chaged to non signed & encrypted config in PI, MDN started working alright.
Thanks
Ravindra
Hi Ruchir ,
I am facing same issue .
Message should get processed as EDIFACT . But Sender is not identified when UNH segment is carrying "EAN008" subversion . On removing EAN008 from UNH segmenet message gets processed successfully .
Any hint ?
Regards ,
SR .
Hi Raghu,
I am facing the same issue. We created a self signed certificate for our PO dev system and shared the same with the AS2 partner. I am signing with the public ssl like you have done. I get the same error too. Below are just errors from the message monitoring.
MDN with action-mode automatic-action, sending-mode MDN-sent-automatically and disposition-type processed received
MDN Disposition-modifier-extension is error: authentication-failed
Message could not be forwarded to the JCA adapter. Reason: javax.resource.ResourceException: MDN Disposition-modifier-extension is error: authentication-failed
MP: exception caught with cause javax.resource.ResourceException: javax.resource.ResourceException: MDN Disposition-modifier-extension is error: authentication-failed
Exception caught by adapter framework: javax.resource.ResourceException: MDN Disposition-modifier-extension is error: authentication-failed
Transmitting the message to endpoint <local> using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: javax.resource.ResourceException: MDN Disposition-modifier-extension is error: authentication-failed
Please help!!
thanks Thrinath