@Curious_User I was not, and it’s confirmed by support that this is not how it was designed.Looking for other customers where this is important to escalate the ticket for urgent development of this functionality.
@Chathuranga Samarakoon I don’t think it supports that currently.Provisioning Interval in Azure is 40 minutes, usually Ok enough.We currently run AD sync once per day.Our biggest issue is IFS’s SCIM implementation which does not allow to specify Person ID, nor works similar to Apps 10 when it comes to Address ID’s and its connected communication methods.best regardsDominik
IFS support informed be this function will come in 24R2 to control Person ID with Azure SCIM….
@osojans Hi Jan, we have done something similar extensively in Apps 10 using custom events.We are now in the process of upgrading to IFS Cloud and realize they don’t work, mostly due to the fact that the LU names have changed where the approvals are needed, as well as the key refs.Did you find a “better” or more modern approach?ThanksDominik
HelloAlso currently struggling with it. Person ID is created by HR on the employee file.I must be able to provide it during SCIM as parameter to just link it to an existing person ID.@techarisp did you find anything? Support is also taking it back with product development… ThanksDominik
@devin.amarasekaraI have managed to sync a group now and assign a permission set, so this appears to work finally in 23R2 ThanksDominik
Dear allI finally managed by deleting all default attribute mappings and sticking to just the bare minimum described here:Index - Technical Documentation For IFS Cloudwill gradually try to increase the amount of information, especially address and communication methods.ThanksDominik
Dear all23R2 SU02 applied but still same error. Ticket reopened. Anybody successfully implented SCIM from an existing Apps10 DB?ThanksDominik
Hi @Nemolk if you have already created the application that is used for SingleSignOn, you need to create yet another application in Azure just for the provisioning functionality. not really clever, but seems to be the only way.Dominik
Hi @knepiosko Planned versions of fixing this issue according to IFS support for my case CS0182667 is:22.1.23 - 22R1 SU2322.2.16 - 22R2 SU1623.1.9 - 23R1 SU923.2.2 - 23R2 SU224.1E.0 - 24R1 EAI have not managed a single user to sync. We sync address type ‘WORK’ as well as use field Initials containing the person ID to match the cycle from IFS employee file to AD → AAD → back to IFS. User Identity appears to be correct, we use firstname.lastnameI have not even yet tried with the AAD groups, but its also important for us that they manage the permission sets.
@linkri thank you for trying.I have an open case CS0182667 where IFS confirmed a bug. waiting for an update
Hi @subslk @Narmada same error, on 23R1, any solution that worked?ThanksDominik
@Martin Falkenau The last time I checked and had IFS Cloud demo access was 2 months ago and it was not yet possible. We are starting the upgrade project shortly and will bring it again to the attention of IFS that this is a basic requirement that could be quickly solved. Glad to hear we are not the only ones.Best regardsDominik
Issue finally found. In our case the sync application message number was 33 which is responsible to trigger a sync and it was in status finished, while it must be in status waiting continuously. Attached SQL statements can force it into status Waiting, and if there would be errors can clear the error text field.Checks the statusselect * from fndcn_application_message_tab where application_message_id = '33';Forces it in status Waiting:update fndcn_application_message_tab set state = 'Waiting' where application_message_id = '33';Clears the Error_textupdate fndcn_application_message_tab set ERROR_TEXT = '' where application_message_id = '33';
@Imal Thiunuwan Thank you so much for the code above It works for PDF_PARAM_1 but for some reason not for PARAM 5 and 6. send_pdf_info_ := Message_SYS.Construct('PDF'); Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_1','&VENDOR_MAIL_ADDRESS'); Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_5','&BUYER_MAIL_ADDRESS'); Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_6','&ORDER_NO'); best regards Dominik This above was not working at all, not just for PARAM_1 but all PARAMETERS. it did not pass on any values to the PDF_REPORT_CREATED event.
@Imal Thiunuwan Thank you so much for the code aboveIt works for PDF_PARAM_1 but for some reason not for PARAM 5 and 6.send_pdf_info_ := Message_SYS.Construct('PDF');Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_1','&VENDOR_MAIL_ADDRESS');Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_5','&BUYER_MAIL_ADDRESS');Message_SYS.Add_Attribute(send_pdf_info_, 'PDF_EVENT_PARAM_6','&ORDER_NO'); best regardsDominik
Hi @MitDenukN I face exactly the same problem with PDF Variables empty.They are populated when I manually print the PDF.They are empty when I programmatically print the PDF.Did you ever got a soluition for it, or is it indeed a bug in UPD12?
Hi @JONEDE with the knowledge we have after 2 years of IFS we would now also opt for just one matrix structure, and not the 6 we have in place. As you mention, it would be so much easier then to move.I rebuilt the structure now, and terminated the old one which seemed the quickest solution.ThanksDominik
Hi @JONEDE My issue is in a matrix structure, where it also does not seem to be allowed.ORG code cannot be reused, even if I terminate it on a date in the old structure.
Hi,Many thanks for the above instructions.We have successfully implemented the print purchase order event on Purchase Order Release.However, we also have a PDF_REPORT_CREATED event that is responsible in sending the mail once the purchase order has been printed.Individually these events work.Release PO will trigger the event to Print.RMD Print PO will trigger the event to email.But not in a fully automated sequence. Any idea as to why?ThanksDominik
We would also be very much interested in finding a solution to this.This is a huge gap from IFS to only write it for default customer/suppliersThanksDominik
@MR10 Thats what I was worried about. Yes we already know which role needs what screens/functions, but to click this all together again is crazy time consuming
@MR10 We will shortly start the transition as well.What do you mean with “not having to set it up from scratch … saves a lot of time”? We have roughly 100 permission sets what would need to be retranslated to Aurena, and we just don’t see this being done manually.Any conversion ideas are highly valued.ThanksDominik
Dear allwe have occasionally had the same issue using browser or desktop shortcuts that launch directly the ifs.Fnd.Explorer.application https://xxxx.xxxxx.xxx/client/runtime/Ifs.Fnd.Explorer.application. Going through the normal web interface to launch IFS Enterprise Explorer fixed it, and any subsequent attempts through the link started to work again. best regardsDominik
Hi PeshalaPlease see attached screenshot:manually run the jobs gives much better parameters to define the periodsWe’d expect similar parameters when we schedule, using current open period
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.
