Thanks Charith. The API call is being done by the database server so is independent of the middleware server.As suspected, after adding the trusted root certificates to the wallet and restarting the server, Slack comms worked again (although I’m not sure if just a database restart would have worked just as well). The process looked something like this:Download DER root certificates and copy to E:\app\oracle\wallet\ Start Menu > “Oracle - OraDB12Home1” > Wallet Manager Wallet > Open Do you want to continue > Yes Select Directory E:\app\oracle\wallet\ Enter password Wallet > RMB on Trusted Certificates branch > Import Trusted Certificate Select a file that contains the certificate Browse to E:\app\oracle\wallet\ Choose certificate(s) > OK Wallet > Save Restart Oracle or Database Server
Because I am not the author or the document, just a contributor, so I am not free to distribute it openly.
All,I’ve been working on this issue (with IFS assistance) as the Coordinator Group fix didn’t work for us (but it would be useful to know how your Coordinator Groups are configured, i.e. assuming you have more than one, did you tick them all, etc?). Furthermore, our error message is slightly different…Yours is ORA-20112: CustomerOrder.EXIST2Ours is ORA-20112: ExtCustSched.FND_RECORD_EXIST: The Ext Cust Sched already exist...but I believe that it is a related issue, i.e. it is due to out of sync sequence numbers. The cause of our errors are as follows…Oracle sequence CUST_SCHED_MESSAGE_SEQ contains an auto indexing number that feeds the column Message ID in Incoming Customer Schedules. If you bring in an XML EDI message, which must have a MESSAGE_ID field, it fails with ORA-20112 if the incoming MESSAGE_ID is greater than the next value in CUST_SCHED_MESSAGE_SEQ. To test this, I run two queries...select cust_sched_message_seq.nextval from dual;select max(message_id) from ext_cust_sched_
I just looked back through our comms with IFS during our upgrade from 7 to 10, which included new WaDaCo capabilities. I had forgotten how complex it was! It seems that we eventually negotiated a deal where we effectively bought combined WaDaCo/IFS user licences, and the licences were issued as full but restricted to device use.
A scanner device would use a license but you can buy low level licences from as little as a couple of hundred pounds potentially. You don't need a “full” license.
@Clément B We’re doing the sane. CADLink simply displays the data from PLM and IFS side by side in a spreadsheet comparison style interface with colour coding. You can then choose what to copy and in which direction, so it is an interactive process rather than a behind-the-scenes synchronisation, with up versioning obviously @anbouk We installed Teamcenter client and the CADLink utility on a couple of vPCs and that’s about it. There is a bit of configuration and customisation involved but not much. Very straight forward.
Awesome, thanks. We upgraded from IFS 7 a couple of years ago and I’ve never noticed this!
Could you share what you found and where?Thanks.
The fact that we are talking about integrating PLM pretty much defines what needs to be integrated (synchronised between systems), eg part and BOM data as discussed.
Hi @Clément B,We use Siemens Teamcenter for PLM. I believe that it works in both directions and that it supports the creation of parts, PDM BOM and mBOM.
Hi @Adarsh,We use a third party application called CADLink to transfer Engineering and Inventory Parts and BOMs between PLM and IFS. This was much more cost effective than having the PLM vendor carry out the integration.
OK, that’s a shame.In the sample, you have <MESSAGE_ID>23186179:-</MESSAGE_ID> and then later on <PART_NO>23186183:-</PART_NO> so could the “:-” be causing an issue?In this view, what does the Error Text show?
Hi @svrmhuebner It looks like the spec (/ifsdoc/documentation/en/General/AboutEDIMessages.htm?StandAlone=true#ORDRSP) doesn’t seem to include the name, just the customer_no. The only way we found to include custom data was to build the XML file from scratch and use custom code to output it, involving hundreds of lines of code.Unless anyone else has any suggestions, I would strongly suggest that you avoid this unless it is absolutely critical.
No problem. IFS were very helpful to us when we had similar issues. Please let us know how you get on.
So it’s the conversion to the intermediate file that is causing the issue. Are you providing all mandatory lines in the Delsch file? And what version/update are you on? It might be a bug fixed in a later update so you will either have to update, or wait for IFS to fix.The only other option is to import your own intermediate file and bypass the Delsch format, but that depends on what is generating your inbound file.
I don’t have any testing data available as the servers have been reset but try going to Application Messages and open an inbound message, then right-click on the message line and then View Message Response.You should see a file called MESSAGE_RESPONSE.xml that looks something like this...<?xml version='1.0' encoding='UTF-8'?><IN_MESSAGE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:ifsworld-com:schemas:inbound_distribution_transactions_receive_customer_schedule_response"> <MESSAGE_ID xsi:nil="1"/> <RECEIVER xsi:nil="1"/> <SENDER xsi:nil="1"/> <SENDER_MESSAGE_ID xsi:nil="1"/> <RECEIVED_TIME xsi:nil="1"/> <VERSION xsi:nil="1"/> <CONNECTIVITY_VERSION xsi:nil="1"/> <SENDER_ID xsi:nil="1"/> <CLASS_ID>DELSCH</CLASS_ID> <OBJSTATE xsi:nil="1"/> <OBJEVENTS xsi:nil="1"/> <STATE xsi:nil="1"/> <LINES> <IN_MESSAGE_LINE> <MESSAGE_ID xsi:nil="1"/> <MESSAGE_LINE>1.0
Thanks, nothing obvious wrong with that.Have you checked IFS Connect > Application Messages? From memory, the DELSCH file gets converted to a RESPONSE file before being processed. We had issues with DELSCH and so also tried bringing in raw RESPONSE files instead and that worked for us (from a testing perspective as we still haven’t turned on that process yet). It might help to identify if the it’s the conversion to RESPONSE that is the issue or the processing of it.
Hi @NSRJMITCHELL I agree with you that this should be possible. Have you tried creating your incoming schedule as a dummy outgoing schedule first in order to check the structure? I can’t find any examples in our sample files of multiple article lines, however.Can you share a sample file?
This happens with our IFS10UPD4 installation only when we restart the middleware whilst people are still logged in. When the users try to use IFS again, they get that message and have to restart IFS.Sorry it isn’t a more useful contribution.
If only I’d know this a year ago! Thanks @dsj.
I have tried but couldn’t find a way to to it.
Excellent, thanks. Quick test...DOC_NUMBER_COUNTER_API.FETCH_NEXT_NUMBER('C1', '1')Works like a charm.
The answers above are good - Just a thought - rather than creating a Sequence using oracle script, there is a built-in sequence generator in the document management module. It’s called Number Counter in Document Basic. You can use it for anything, it doesn’t have to affect document management. This way you are using IFS functionality. There are many customers using Cloud, for whom running an oracle script to generate a sequence would be unacceptable or at least difficult, whereas using Number Counter is simply a case of setting up IFS Data. That sounds interesting. Can you give an example?
I wish. At least not that I am aware of.We have used Odex from Data Interchange for many years to rewrite EDI messages so we are using that to convert VDA to Edifact.You will probably have to create your own or pay a third party to do it. I would love to tackle this as a project for our data but don’t have the time or resources internally.
Hi @NSRJMITCHELL,This will be a good place to start:/ifsdoc/documentation/en/Supsch/dlgSuppSchedTransfer.htm/ifsdoc/f1doc/foundation1/040_administration/240_integration/310_connectivity/900_technical_details/default.htmYou will either need to convert the X12 message to the IFS EDIFACT format before you import it, or use custom code.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
