Blog directory

Using Complex Database Views on EnterpriseOne

Database View Diagram

A Database View is a subset of the database sorted and displayed in a particular way. For example, in an Invoice database, perhaps you only wish to display the Vendors stored in the database.
Database View Diagram
EnterpriseOne Views are similar in nature, where it sits on top on JD Edwards Tables, to retrieve data, or a subset of data.

With Business Views, we can join tables using Left outer, Right outer, Union, Intersect joins. One can usually join up to 5 tables in a Business View if using Simple joins. If one uses a Complex join, then number of tables is limited to 3.

What if you need to use more than 5 tables? What if you need to do some complex joins? And What if you need a column which would give you a Count of records for the group?
For e.g. if you have a need to display the number of items on Open orders and quantities shipped, with the order details, you may have to do the following SQL

SELECT sddoco, sdkcoo, sddcto, count(*), sum(sduopn)
FROM F0411
WHERE sdnxtr <=540
GROUP BY sddoco,sdkcoo,sddcto

To accomplish this in current JD Edwards EnterpriseOne Reporting, you will need to do a little more programming. Continue reading Using Complex Database Views on EnterpriseOne

Change Database values using MS Access (JDE E1 Oracle)

For people who have problems with SQL, there’s an easier way of changing backend database values. How about using MS Access where you can directly type in the values, and it gets updated or you can Insert, Update Delete & you can export, import…. and all. Following is the tutorial for setting up MS Access with Oracle Database Backend for JD Edwards EnterpriseOne. . . . → Read More: Change Database values using MS Access (JDE E1 Oracle)

Pop up Report/UBE after Processed

There are many instances where we do Report Interconnects from Interactive Applications, like print the Order from an order screen, or process something from an interactive application button. But, in all those cases, the report fires on the Server, and you need to go visit the Work Submitted Jobs to check the output. Every User asks for the same convenience, if they can get the output direct on the screen without going to the WSJ. Here is a crude way of popping up a UBE output onto the screen, without going to the Work Submitted Jobs. This makes life easy for the users. . . . → Read More: Pop up Report/UBE after Processed

Value of SV File_IO_Status in Table IO

On an Update or Delete, SV File_IO_Status will always return “CO SUCCESS” even if the update or delete is not successful because the record does not exist.The workaround is to issue a FetchSingle on the record to be updated/deleted and use the result of the SV File_IO_Status of the FetchSingle to issue the update or delete. . . . → Read More: Value of SV File_IO_Status in Table IO