Access JD Edwards EnterpriseOne 9.0 Standalone Webclient from anywhere.

BY DEEPESH M DIVAKARAN, ON SEPTEMBER 28TH, 2009

DEMO/Standalone clients are supposed to be used for a Single system, and not available for Multi-User environments. But now with the advent of Web Interfaces, you can access the E9 Standalone Local Webclient from any other computer in your network. There are couple of small steps you need to follow to accomplish that. *All steps mentioned below needs Administrator Credentials, and needs to be checked with your IT policies before opening any port or so.

1. Start your E1 Demo, and go to the Web client

2. Note your Port number from the address of the page. Say your web page address
says http://localhost:8888/jde/E1Menu.maf; then your Port number is 8888 3. Now we need to open the port on the machine you are in. For Windows XP Machines, go to Control Panel Windows Firewall and take the Exceptions Tab.

Enter E9Local in the Name, and port number to 8888. Click OK and Save the Firewall settings. 4. For Windows Vista users, Open Windows Firewall by clicking the Start button Picture of the Start button, clicking Control Panel, clicking Security, and then clicking Windows Firewall. Follow the same options as shown above. To change scope for the port, click Change scope, and then click the option that you want to use. (Scope refers to the set of computers that can use this port opening.)

5. Find the Computer name by going to Control Panel -> System, and check the Computer Name tab. The Full computer name would be given there. Note the name; for e.g. MyE9Local.Atlanta.myCompany.com Here MyE9Local is the computer name and Atlanta.myCompany.com is the Domain. 6. Now you are ready to access your E9 Web client from other computers by simply replacing the localhost with the computer name as shown. http://MyE9Local:8888/jde/E1Menu.maf , if you are accessing the Demo within same network or http://MyE9Local.Atlanta.myCompany.com:8888/jde/E1Menu.maf , if you are accessing the Demo outside of the network. 7. You can create as many users and give specific roles to them for login.

The Client over here was trying for an upgrade, so we were trying to list out versions with overrides for estimation purposes. Then we started off with F983051, just to find out that theres not a single field which would let us know that it has a version override. Finally on web search, and from Oracle Metalink Documents we found that the RDASPEC information is updated locally in the TAM spec when the version override is created, and then in Central Objects when the version is checked-in. Whenever a new version is created, if no overrides are performed, only one RDASPEC record is created with a Record Type of 1. If additional overrides are performed on the version, then additional RDASPEC records are created. For example, if the user performs data selection overrides, then records are created in the RDASPEC for that report/version with record type 7 with the selection overrides for the version. If section layout overrides are performed, multiple records with record type 3 are created in the RDASPECS. If data sequencing changes are made, then record type 6 records are created in TAM spec and if event rule overrides are performed, record type 16 records are created. This same information can be seen in the Central Objects when the version has been checked in. If no overrides exist for the version, there will be only one record in the F98761 RDASPEC central object table with the report name in RSOBNM, the version name in RSVERS and a record type RSRCRDTP of 1. However, for additional overrides, additional records are written to the central object table with the corresponding record type for the type of override. At runtime the system looks at the RDASPEC for the version and, depending on the records that exist for the version, it knows what overrides have occurred on the version and pulls the appropriate override information. Any record types that do not exist at the version level are then pulled from the report template RDASPEC information. There is not a standard report or simple inquiry that can be performed to see all versions with overrides. The easiest way to determine this information would be to look at the F98761 table in the central objects data source and find all records with a specific version name that have record types other then just 1. This would indicate some type of override was performed on the object. Depending on the value in the record type field (RSRCRDTP)

you can determine what type of override exists for the version. You can also use the Universal Table Browser (UTB) and add the setting of TAMMENUS=Show in the [INTERACTIVE RUNTIME] section of the jde.ini to be able to view local TAM spec information and central object information from UTB. Based on testing and review of the RDASPEC records, the record types are the following: 1 = Base Record 2 = Sections (will have one type 2 record for each section of a report) 3 = Report objects (one record for each report variable and constant on the report) 4 = Column calculation defined on tabular sections 5 = Subsection join (defines join information between sections) 6 = Data Sequencing (will have one record for each data item included in data sequencing) 7 = Data Selection (will have one record for each data item included in data selection) 8 = Database output (one record indicating destination for output -filename) 9 = Database output (one record for each mapping in database output) 10 = Row on tabular section (one record for each row) 11 = Cell on tabular section (one record for each cell) 13 = Row calculation defined on tabular section 16 = Event rule overrides performed at version level 17 = Row on tabular section (record for defined row criteria 18 = Cell on tabular section (record for defined cell criteria) 19 = Column data selection on tabular section 20 = Column and row overrides (tabular section only) Source: Oracle Documentation/Knowledge Garden

Convert UTC time Format to Local Date and Time format The field JSSCHSTTIME in F91320 stores the Scheduled Start Time in UTC format e.g. value 18698955. This is a Local Date and Time format of 2005-07-21 17:15:00 JSSCHSTTIME stores the UTC time. UTC stands for Universal Time Coordinate and is a long integer containing the elapsed minutes since Midnight on January 1, 1970 in Greenwich, England. Now lets write some code which would help converting timezones, from and to. Similarly use UTC time zone and its format effectively for Multi-Location Projects/softwares. But before hand make sure daylight saving rules (DST) are set up correctly in P00085 application. This is applicable only for countries observing DST. The Event rules (ER) along with the screen shot of the app done is given below.

1 Listing of ER for Application : Test for UTC Timezones (P550003) 2 ================================== 3 FORM: Fix/Inspect [FIX INSPECT] (W550003A) 4 ================================== 5 CONTROL: FORM 6 EVENT: Post Dialog is Initialized 7 ----------------------------------------8 // Retrieve the Current UTC Time into a Long Integer Variable 9 Get Current UTC Time 10 VA frm_SchStartTime_SCHTTIME <- BF mnCurrentUTCTime 11 // Display UTC Time 12 FC UTCTime_UTIME = utc_get_cur_time() 13 14----------------------------------------------------------------------CONTROL: BUTTON Convert EVENT: Button Clicked 15 16----------------------------------------------------------------------// Get the Local Time from UTC TimeZone 17 Get Time and Date From UTC 18 VA frm_SchStartTime_SCHTTIME -> BF mnUTCTime 19 FC Time Last Updated <- BF mnTime 20 FC Date Updated <- BF jdDate 21 "2" -> BF cUTC_Local 22 "14" -> BF szTimeZone 23 // 24 // 25 // Format the Time into hh:mm:ss 26 Format MathNumeric to Time String 27 FC Time Last Updated -> BF mnTime 28 FC FormattedTime <- BF szTime 29 "Zero"-> BF cFormatMode 30 Call Business Function Get Time and Date From UTC B9800009 This function can be used to return the date and time for a UTC time in Local Date and Time format. Get Time and Date From UTC 18698955 -> mnUTCTime VA frm_SchedulerStartTime_SCHSTTIME <- mnTime

2 -> cUTC_Local 14 -> szTimeZone

FC Scheduled Start Date <- jdDate /* 2 stands for Local Time. 1 stands for UTC time */ /* Check UDC H91/TZ for your country time zone. 14 is Indian Standard Time Zone */ c