Re: trace table/view used - pls help, neil 2
Ah, now I see where your coming from. When I'm asked to do some development over an area I'm not familar with I'll sit down with the requestor and ask them to take me through the data as they see it on the screen, and if it's for a report, discuss how they want to see the output. If your lucky you'll be speaking to someone with a little experience who will know the bulk of the tables they are drawing the data from, if not you'll have to do some digging. Once the table has been identified I'd use the UTB to validate how to extract it. The other advantage of sitting with the requestor is that you'll start to appreciate what the data actually is, rather than just being records in a file. After a while the system will start to link up and make a lot more sense. With the P0411 you'll see payments to suppliers and employee expenses. I appreciate how you feel switching from a system you know well onto one that seems very 'foreign', but keep at it and you'll be upto speed soon enough.
A good number of JDE's applications will be primarily based on files named after the application (or fairly close) e.g. P0411 stores most of it's data in the F0411, though as you've seen from the x-ref it also uses the F0911. If this isn't the case I'd go into the application design, find the form(s) the requestor has shown, find the business view it's based on and this will then give you the primary tables. JDE, ok EnterpriseOne, like SAP, is a large and complicated system, so data can also to drawn from a number of other sources, and these won't necessarily show at the top level in the x-ref. To find all these sources I'd normally put debugging on, which is set within the JDE.INI file (this might be similar to SAP's trace, setting this on is very well documented though shout if you need a hand) and have a look at the SQL SELECT statements.
I think this should answer question 2. To see the contents of a table I find the UTB by far the best tool for just looking at the data. If I'm doing anything more than a simple view then I'd use SQL. You haven't said which database your on but if it's DB2/400 then just enter STRSQL or use the ops navigator, otherwise I'd use TOAD or SQLPlus, but there's loads of SQL tools out there. If you do use SQL then bear in mind that any changes to data (UPDATE, INSERT, DELETE) will have an immediate impact, so don't!
If you can get access to an experienced resource, user/consultant/developer etc, ask them to take you through the basic applications and their main tables e.g address books, AR, AP, GL, sales and purchasing are a good start. There's probably less than 30 main tables needed to maintain these and knowing a little about each will give you a real boost.
Regards
Neil.