Hi Timo, See below the descriptions from App10. Hope this helps.. Test Point ID:The test point on the object where you want to perform the action. This field is connected to the Testpoints/Parameters tab in Functional Object, Serial Object or Tool/Equipment windows and only permits test points for the objects entered there. Use List of Values to select a suitable value. Test Number:An identity for any external requirements, such as inspections required by authorities. The information in this field can be used as a query term. Alternate Designation:This field can be used as a free text field. One area of use is for company-specific query conditions that you want to store. Material:A reference to the contractor's repair manuals or any other documents that might be helpful. Regards, Thilanka
Hi Juan, As you have indicated that this is APP10, I assume you created and published your quick report in IEE.I created a similar quick report and a custom command and I can see my quick report working. See attached.As another option I created a navigator item to my quick report as well.I also added a internal link type of a navigator item to my quick report and it seems to be working as well. Hope this helps.Regards,Thilanka
Are you thinking of Fnd_Session_API.Get_Fnd_User ?
@Mayura Wasantha - I’m in middle of a scoping task for a customer project that will start later this year. For me 22R2 sounds good.
I happened to be trying a similar setup for a customer on 21 R2 and sees the same behavior as Jerry describes.
Hi Thilini, I can share the following based on my experience on the topic. Hope it helps There is no document size limitation built into the document replication solution. But due to the quality of actual networks used/available at replication customers, then there are limits to what is technically possible as a replication vendor.As a rule of thumb, when file size reach 10 MB or above, I would question the usefulness of such files on a satellite. This 10 MB number depend on available bandwidth, latency, packet loss etc.. as well. One of our customers has a solution to transfer lager files by breaking them into small parts as a modification. When one stores large volumes of files on the same HUB database, eventual rollout and disaster recovery can be challenging. This is normally avoided by planning and design. On the memory usage, on APP8 we knew each document may use as 4-5 times of that memory on application server. That is if you check-in 1 GB documents , App server will use 4 to
Hi Roshan, Please refer my answer in https://community.ifs.com/technology-all-about-the-nuts-and-bolts-that-make-it-work-50/replication-in-ifs-apps-10-message-bundling-1401 Regards, Thilanka
Hi ProSriniA, 1. NO. Unbundling is not part of Apps 10 implementation. Apps 10 uses a much faster and less resource intensive approach. 2. IFS do not use the separate services approach in Apps 10. We still have the queues but they run in the MWS cluster. Hope this information helps you. Best Regards, Thilanka
Hi Rajendra, Assuming that you have this issue in APP10 or App9, I would say that you should check the STOP_QUEUE parameter on the Application message queue. If you navigate to the queue that you have the issue in Solution Manager > Integration > IFS Connect> Setup IFS Connect, you can check the parameter. If the queue is an’ in order’ queue, messages on that queue will not process if there is one failed message. If a message seems to be stuck in a processing state, normally system recovers. If it does not in a reasonable time, then you need to get help from a technician to remove a stuck JMS message from the Middleware server. I like to note that, I have only seen this scenario when users have done something they should not. Regards, Thilanka Madugoda
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.