Hello, We are currently facing an issue where the MPL voucher has a balance in Parallel currency and as a result it is impossible to update the MPL voucher to the GL. IFS Version – APP10 UPD11 PO created in currency EUR for an inventory part. Accounting currency of the company is USD & Parallel currency is NGN (Nigerian Naira). Parallel currency base for the company = Transaction Currency. GR done & inventory transaction has been transferred to Finance. MPL voucher stuck in Voucher Entry screen with Not Approved state. When you try to Approve you get the error “Voucher with status approved must be in balance”. As highlighted below there is a balance remaining in Parallel currency. Appreciate if anyone could advise what is the best way to fix this issue. Hi roshanF, We have the same issue. How did you solve it? Thank you very much!Balazs
Hello, Consolidation of opening balances is needed for initialization of currency adjustments functionality (used in case accounting currency of child company is different than mother one), it does not create C voucher in GL of mother company. Period 0 balances in GL Analysis window are created only by GL Year end process (Preliminary or final). Is the period 0 of 2024 the first one you ever consolidate the COMP1 to parent GROUP? If you did consolidation in 2023, balances are there already in Group GL and all you need is to close 2023, you do not need to create GL voucher from consolidation for period 0, it would double the GL figures in mother. Thank you very much Adam! Yes, this was the issue. Business didn’t perform the preliminary year end step. (But then we face an other issue, but I found the answer here: https://community.ifs.com/ifs-applications-239/what-causes-the-error-the-accounting-balance-object-already-exists-when-executing-preliminary-year-end-9478) Thank you again!Re
@bapehu can you use IP whitelisting to restrict traffice to /admin only when originating from the jumphost or localhost? Some guidance on this is documented here: https://docs.ifs.com/techdocs/Foundation1/010_overview/210_security/090_exposing_to_internet/default.htm Best regards, Rukmal Hi Rukmal, Thank you very much for the link and the advise! I will ask my network colleagues to check this! Kind regards, Balazs
Hi @bapehu . I can confirm that what @jaw has said should work. Actually using “=%” should also work. For future reference: The conditions for the “=” option are actually evaluated by database method “Report_SYS.Parse_Parameter” which supports all the usual search syntaxes that are also available in the client. This includes wildcards “A%”, lists “B;C;D”, ranges “E..G”, or a combination of it “A%;B;C;D;E..G”. Hi Jonas, Thank you so much the explanation and the examples! Very helpful to understand if we have more possibilities! Kind Regards, Balazs
Hi, We faced the same issue. LIKE % will be true for any value other than NULL and not fire the action. Good luck! Alexander Thank you very much Alexander, I tried and works!
Hi Balazs, It seems like you are having some certificate issue with the atom. Please follow the community post to import the SSL certificate into your atom and remember to restart the atom before proceeding. I hope this will fix the error. Thanks. Hi Denam, Thank you so much for your answer. Our team reviewed the certificates on Boomi side and you were right! Issue was with the certificates.Briefly: With our previous test environment, we used self-signed certificates, when the IFS app server issued the certificate. But with the new test App server we have a different method to issue the certificates. We reviewed our certificates in Boomi, then re-imported the certificate which fits for the new App server and the issue is gone. Thank you very much again for the help!Kind regards, Balazs
Hi hhy38, Thank you very much for your comments. We switched on the compatibility mode: If I understood correctly: we can reach the /main/ only with OAuth authentication we can reach the /int/ with basic authentication if we switch on the Compatibility mode as I know from our Boomi developer, Boomi can call only /main/ layer. But if Boomi can use only Basic authentication - and can’t use OAuth authentication - as it is written in that Boomi page - which is not available in /main/ layer, how this can work at all? :) An interesting fact is this whole structure worked in a different test environment and we don’t know why it is not working now. Thank you very much any thoughts! Regards, Balazs Hi, The IFS REST Partner Connector is capable of calling /int layer APIs. You can find that when importing the API, where it will appear as “integration” for the projection category input. Please refer to the below screenshot. Thanks. Hi Denam, I discussed wi
Hi hhy38, Thank you very much for your comments. We switched on the compatibility mode: If I understood correctly: we can reach the /main/ only with OAuth authentication we can reach the /int/ with basic authentication if we switch on the Compatibility mode as I know from our Boomi developer, Boomi can call only /main/ layer. But if Boomi can use only Basic authentication - and can’t use OAuth authentication - as it is written in that Boomi page - which is not available in /main/ layer, how this can work at all? :) An interesting fact is this whole structure worked in a different test environment and we don’t know why it is not working now. Thank you very much any thoughts! Regards, Balazs Hi, The IFS REST Partner Connector is capable of calling /int layer APIs. You can find that when importing the API, where it will appear as “integration” for the projection category input. Please refer to the below screenshot. Thanks. Thank you very much Dena
@bapehu You are welcome. Actually, I don't know the Boomi parts. But, this is how it works. I am just trying to show what I know :) Thank you very much hhy38 all of your effort! Really appreciate and it help a lot to understand the logic! Thank you again! Kind regards, Balazs
Hi hhy38, Thank you very much for your comments. We switched on the compatibility mode: If I understood correctly: we can reach the /main/ only with OAuth authentication we can reach the /int/ with basic authentication if we switch on the Compatibility modeas I know from our Boomi developer, Boomi can call only /main/ layer. But if Boomi can use only Basic authentication - and can’t use OAuth authentication - as it is written in that Boomi page - which is not available in /main/ layer, how this can work at all? :) An interesting fact is this whole structure worked in a different test environment and we don’t know why it is not working now. Thank you very much any thoughts!Regards, Balazs
Hi @bapehu, The difference between “Main” and “Int” is the authentication method. While “Main” uses AUTH2 authorization and “Int” uses BASIC authorization. Which method are you using while requesting the “main” layer? Hi hhy38, Thank you very much for your quick answer! We tried to use basic authentication, because we read this: here: Article: Getting Started with the IFS Applications 10 REST Connector - Boomi Community Kind regards, Balazs
@bapehu I highly recommend you blur the URL and Port information of your IFS server in screenshots. Thank you very much for the advise!
Hi @Mathias Dahl ,Document repository settings is exactly the same, we use database repository. We investigated a lot and it looks like this message pops up when we attach documents also. So not just when we would like to open an attached doc. We saw somehow our Live environment is not able to write and read records to edm_file_storage_tab. We receive the error above when we have record in edm_file_tab but somehow the connected record is missing from edm_file_storage_tab.Currently we don’t know how is this possible. Probably this is not permission issue, because IFSAPP user also not able to add record. Thank you very much for your thoughts!Best regards, Balazs
Hi @Mathias Dahl , Thank you very much for the suggestion. Unfortunately It didn’t help. I tried to: delete whole 2.0 folder, then reinstall IFS instances (test and prod) delete prod Ifs.Fnd.Explorer.exe and copy there the test .exe delete windows registry keys regarding IFSNeither above steps helped. Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> System.NullReferenceException: Object reference not set to an instance of an object. at Ifs.Application.Docman.cEdmRepository.___DownloadDocument(String sourceFileName, String destinationFileName, String sDocClass, String sDocNo, String sDocSheet, String sDocRev, String sDocType, String sTicket) at Ifs.Application.Docman.cEdmRepository._GetCopyOfCheckedOutFileFromRepo(SalString sDocClass, SalString sDocNo, SalString sDocSheet, SalString sDocRev, SalString sDocType, SalString sTicket) at Ifs.Application.Docman.cEdm.ViewCopyExecute() at Ifs.Application.DocumentConnectionsAttachmentPlugin.DocumentConn
Hi @Alexander, Thank you very much for the suggestion, but yes, we checked. We don’t exactly why but this error has gone. But I would have an other question: We tried to use: PurchaseOrderSet projection and LineNopartArray function. We sent this information: {"BuyQtyDue": 1,"BuyUnitMeas": "EA","Contract": "2","CurrencyCode": "EUR","FbuyUnitPrice": 21,"LineNo": "1","OrderNo": "A0152939","PlannedReceiptDate": "2021-12-01T01:01:01Z","PurchaseOrder_OrderNo": "A0152939"}But we got back this error: {"error": {"code": "DATABASE_ERROR","message": "Database error occurred. Contact administrator.","details": [{"code": 20124,"message": "ORA-20124: Error.NULLVALUE: Field [CurrencyRate] is mandatory for Purchase Order Line Nopart and requires a value."}]}} Then We added CurrencyRate field to the message and it is worked. {"BuyQtyDue": 1,"BuyUnitMeas": "EA","Contract": "2","CurrencyCode": "EUR","CurrencyRate": 1,"FbuyUnitPrice": 21,"LineNo": "1","OrderNo": "A0152939","PlannedReceiptDate": "2021-12-
Dear @Dumeesha Wanigarathna We have a great progress in create PO via API. But currently we stuck at the line level. If we try to create PO lines (part lines or no part lines) we always got the following error:{"error": {"code":"DATABASE_ERROR","message":"Database error occurred. Contact administrator.","details": [{"code":20111,"message":"ORA-20111: UserAllowedSite.RECNOTEXIST: Site is not allowed for User IFSAPP"}]}} We tried - I think - everything. IFSAPP has rights for everything. We just tried a very simple input for order line: { "BuyQtyDue" : 1, "PartNo" : "P00002", "PurchaseOrder_OrderNo" : "A0152939", "PurchaseSite" : "SBX"} Do you know idea about what could be the issue?Do you have a working example request for PO header and Line, to see how a working one looks like? Thank you very much in advance for your help!Kind regards, Balazs
Hi @Peter Sketch Boomi Thank you very much for the explanation! This certainly explain why restarting the server solve the issue. Thank you very much for your contact details, if we have other issue, we will definitely contact you. Thank you!Kind regards, Balazs
Hi @Dumeesha Wanigarathna , hi @Sameera Perera , Thank you so much for all of the above information!These are very useful! Now I will be able to find the correct projections and methods! Thank you again!Kind regards, Balazs
Hi @Dumeesha Wanigarathna , hi @Alexander , Thank you very much for the information! I found it! Thank you again!Best regards, Balazs
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.
