Can you put the altered layout on the First Page and use the Repeating page for the full layout?
I think you have two options.Through Apps 10 IEE, create an IAL. The IAL file can be saved locally and deployed to other instances. But be aware that IALs are being phased out in future versions of IFS.ORUsing IFS Developer Studio, create a new project, add a Utility Model with your custom views definitions. Connect to your desired database and deploy the views.
For what you’re calling dynamic enumeration, I did that a different way. This activates the ellipsis (like you get for date parameters) instead of the down arrow list of values. parameter CompanyNo Text(100) O---L { default ":User_Finance_API.Get_Default_Company"; lov "PERSON_COMPANY"; } parameter Site Text(50) O---- { lov "USER_SITE_COMPANY"; }About the .rdf vs .report development, I’m not a strong pl/sql developer, so working in the .report file and then generating the .rdf was the only way to go for me. It is challenging to do this way because you’re kind of on your own. I looked at the seeded report files that IFS provides for their operational reports and they are done a very different way, with the .report file being a shell for the structure and the logic being in the .rdf file. This makes it difficult if you want to emulate the functionality of a particular operational re
Docs say you need separate sales part 9001012ATU IFS Data Migration Excel Add in ATU
Joe - I’ve only created a couple of operational reports from scratch, so my knowledge is limited. That being said, I did need to create a custom enumeration for a report parameter. The way I did it was to add an Enumeration Model in IFS Developer Studio. The syntax in the .enumeration file is pretty simple: enumerationname CMyCustomList;component <IFS component>;values { value MyValue1; value MyValue2; value MyValue3;} Then in the .report file, the enumeration is referenced as such: parameter ReportSection Enumeration<CMyCustomList> M---L { default "%"; } I deployed the enumeration then generated the .rdf and deployed the .rdf.Best way to do this? I don’t know, but it worked for me.
Yes, for IFS Apps 9, when using the “Select” Implementation Type for a Read Only custom field, you can use any valid SQL statement, as long as it’s correctly bound.Did you run into some issue when trying this out to see if it would work?I believe Pawel is outlining your options when creating a persistent custom field that references a single view to determine what shows up on the list of values when the user chooses a value to populate the field.
Mino - Thanks for your post and F1 docs link. We had a customer getting an Error 502 - Bad Gateway System Exception Error when attempting to use RMB/Export to Excel instead of the Output Channels. It was happening on all of the Quick Reports where we used the “with” functionality. Wrapping the code in a “select” fixed the issue.
I got this to work by using enumerate instead of the lov. parameter ServiceType Text(100) M---L { default "%"; enumerate "SERVICE_TYPE_CFP.ENUMERATE"; }Is there a better resource to explain report modeling features and properties other than the Tech Doc which can be sparse in sections and skips over some subjects? I have read through what is available in the v10 Tech Doc and have reviewed some of the .report and .rdf files belonging to IFS standard operational reports. The issue is that I’m putting all of my code in the .report file and autogenerating the .rdf file. I see that the standard IFS reports don’t do this - the .report file is just a shell for the structure and all of the logic is written in the .rdf files. So it’s hard to use the standard reports as samples.I have reviewed this: Foundation1/Development Guide/Operational Reporting/Report Modeling/Model Syntax/Model Syntax for Reports
What’s the “A.” for? You have “t” as the view alias.
Nick - I found a particular part that is a good test. I have receipts for the part before and after the date where the RNYI sourcing appears to change. Inventory Valuation Method is currently “Standard Cost”Inventory Value/Unit Cost is currently $0.50Part Cost/Total Cost is currently $0.00 for all cost setsThere are 7 received not yet invoiced receipts on the reportThe RNYI report uses the $0.50 for the first receipts, after that it uses the various buy unit prices on the POs.In the Inventory Transaction History/Accounting tab, there are PRICEDIFF- (Price Difference - Lower Price) and PRICEDIFF+ (Price Difference - Higher Price) for each receipt where the PO buy unit price differs from the Inventory Value/Unit Cost. Posting Types for those are M10 (Receipt with Purchase Order) and M20 (Price diff Purch, Lower[or Higher] Price).For the record, I was able to get over my immediate need by incorporating the above accounting transactions into my report code - didn’t mention it, but tha
Thanks Ruchira. We’ll try that if we can’t get the process to complete.
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.