Yes, I also came across with the same issue. This happened to me when there exist an export-controlled component under the parent part. But when I check the Export License tree it does not show such a requirement for the component. Still the Export License Status shows as Partially Connected.Please see the picture attached. EXP-02 is the manufactured parent part which require s an export license and it has been connected. The purchase component EXP-P1 also requires an export license, but it has shown here as “Not Needed”, but still it has made the status in the header Partially Connected. This is not correct and this scenario has created the error at picklist creation for me.
I raised this with IFS. It is core build. My solution was to add a record to the supplier for purchase part under the export control tab, marking it as not export controlled and activating the record. This will create a “connected” status on the customer order line. Unfortunately, it does require additional set up. Hi Jonny,Yes, that worked. Thank you very much. 😍
The reason for this error to appear seems nothing connected to CRO. But the key violation in part in stock record. What happens here is, by entering a different availability control ID, you are trying to insert a new record to the part in stock table with same keys. Therefore, the general error message of change W/D/R number displayed to the user. This is because W/D/R number is a key in that table and changing it can possibly create a new record with the new availability control ID.Having a new W/D/R number has no effects in the functional flows as long as you are ok to proceed with that value.Hope this clarifies the behavior.
You need to define your parts as export controlled with the value of the field Export controlled equals either <Yes> or <Denied Party Only>. Then it should work.Note: Defining denied parties is on High level and it will make a restriction on all export-controlled parts to those criteria.
Credit Card functionality is in 21R2, so has to be there in 22R1, at least for Customer Orders May you clarify on this? Has the terminology or bread trail for the customer credit card interface been changed in IFS Cloud? I don’t see anything credit card functionality (for customers not HR expenses) in the 23R1? If the functionality doesn’t exist anymore is there a reason why it remove between Apps10 vs Cloud? And if there’s any roadmap to re-introducing the functionality again in future version of Cloud? Thanks, Robert IFS has 2 Credit Card functionalities.1. Used in HCM - Developed by R&D2. CCI-Used in Customer order -Developed by IFS NASo, the CC in HCM has been in all later IFS releases including IFS Cloud. But Credit Card Interface-CCI, used in customer order has not been uplifted from APP 10 since it is not a core release. It doesn’t mean that it should not. But it hasn’t done yet. (It’s not there even in APP 10 Aurena client)
Hi Jude, Has this been updated for IFS Cloud? No, CCI has been implemented by IFS NA and has not been uplifted to IFS cloud yet.
Thank you Mithun,This document was created in 2015 and it does not contain the mapping with brain tree sandbox , because brain tree came lately. It does contain parameters for old systems. But those didn’t work for me. But, Thank you again.Best regards,Pushpa
Noted. Thank you very much @Richardson69
Hi, Yes, we had used this flag member of the EU in ISO country codes in some Tax reports for local Polish market. It can be used in some Invoicing processes , but here more important is the correct Tax Code. Best Regards, Pawel Thank you Pawel.
In case anyone else comes across this thread. The Credit Card Interface is available in IFS Cloud for Customer Orders. I’m in the process of implementing it now in 22R2. It is not apart of core and is treated as an Add On. Hi Faraz, Thank you for the great news. I hope it means that any customer who is on 22R2 or later version of IFS Cloud can request this from IFS NA. //Pushpa Kumara
Hi Amber,Mainly there are 2 main advantages by using DOP together with CTO.Dop facilitates parts with multi-level structure all the way from top to bottom with passing the configuration to each level. Dop can create the supplies for its components.If you want to produce a part along with subassemblies with passing the configuration upstream, then DOP is the only solution. Otherwise, it is not necessary to use DOP with CTO. you can use shop orders to produce your configured parts.
Hi, One more thing to look in addition to the above answers is, Uncheck the flag Stop MRP on error. Then see the results. if the result is consistent in this case, then it would be an issue with some parts, which made MRP to stop at a certain point earlier.
Already have an account? Login
No account yet? Create an account
Enter your 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.