JD Edward's Interview Questions

Handel is data base related tool in JDE1 that provide the following facility, • We can use handles to open multiple instances/times, of a single table or business view. • We can use handles to open a table or business view in an environment other than the environment  you are logged into. • We can pass handles into a form, named event rule or business function so that you do not need to  open a table or business view more than once.

Replicated Objects are stored in a directory on every workstation and logic server that will run OneWorld Built from Central Objects, Deployed via packages (‘point-in-time’ snapshot of selected objects) Stored in runtime (TAM vs. RDB) format

No, but you can add totals to a columnar section by creating a level break footer section.

Only one section can be created initially when using the Report Design Director but additional sections can be added later.

Columnar, group, tabular, financial (application specific)

The director guides you through all the steps of creating a report section.

A business view, this links the report section with the data in a table.

Data sequencing allows you to list your data in the order that best fits your needs.

Data selection allows you to filter your data to provide you with only the records that are of interest to you.

A tabular section as it provides a columnar layout with automatic column totaling.

A columnar section would provide you with rows of data beneath a heading.

A group section as it allows you to place fields in a free-form manner.

Only one report header per report and it prints only once at the beginning of the report

Layout of section, content, headers/footers, page breaks, section breaks, and group breaks.

BDA Business View Design Aid BSFN Business Function BSVW Business View CSV Comma Separated Values DD Data Dictionary DS or DSTR Data Structure ER Event Rules FDA Form Design Aid H4A HTML for Applications NER Named Event Rule OCM Object Configuration Manager OL Object Librarian OMC Object Management Configuration OMW Object Management Workbench OSA Output Stream Access PO Processing Option QBE Query by Example RDA Report Design Aid SAR Software Action Request TAM Table Access Management TBLE Table TC Table...

Custom Sections allow you to control, through event rules, the information that prints on a report. We can use Custom Sections to print additional information depending on certain criteria.

Smart fields are the fields, which provide the ability to add complex and reusable calculations to the financial report. Smart fields are grouped by smart field template, which is based on a particular business view. Its glossary, type is K

Text Variables are used to store strings, which can be attached to the reports using Event Rules. They are used as alternative to hard coding text strings in assignments.

There are following events available in Header Detail Form: Dialog is Initilized Clear Screen Before Add Post Dialog is Initilized Grid Record is Fetched Write Grid Line-Before Last Grid record has been read Add Record to DB - Before Add Record to DB - After Update Record to DB - Before Update Record to DB - After End Dialog Write Grid Line-After Clear Screen After Add Call is Alerting Director Back Button is Clicked Director Next Button is Clicked Director Cancel Button is Clicked Post Comit XAPI Subscribe Event

There are following events available in Headerless Detail Form: Dialog is Initilized Clear Screen Before Add Post Dialog is Initilized Grid Record is Fetched Write Grid Line-Before Last Grid record has been read End Dialog Write Grid Line-After Clear Screen After Add Call is Alerting Director Back Button is Clicked Director Next Button is Clicked Director Cancel Button is Clicked Post Comit XAPI Subscribe Event

There are following events available in Fix/Inspect Form: Dialog is Initialized Clear Screen Before Add Post Dialog is Initialized Add Record to DB - Before Add Record to DB - After Update Record to DB - Before Update Record to DB - After End Dialog Clear Screen After Add Call is Alerting Director Back Button is Clicked Director Next Button is Clicked Director Cancel Button is Clicked Post Comit XAPI Subscribe Event

There are following events available in Find/Browse form. Dialog is Initilized Post Dialog is Initilized Grid Record is Fetched Write Grid Line-Before Last Grid record has been read End Dialog Write Grid Line-After Call is Alerting Director Back Button is Clicked Director Next Button is Clicked Director Cancel Button is Clicked XAPI Subscribe Event

There are several Project status pre-defined in JD Edward's. They are as follows: 01 - Complete 11 - New Project Pending Review 21 - Programming 25 - Rework-Same Issue 26 - QA Test/Review 28 - QA Test/Review Complete 38 - In Production 40 - Production Development 41 - Transfer Production to Prototype 42 - Transfer Prototype to Development 45 - Pristine Get 91 - Canceled-Entered in Error

Tokens are used to identify when a developer is modifying a specific object and minimize the chances of modifications being overwritten by another developer.

1. Interactive Applications 2. Business Functions 3. Tables 4. Business Views 5. Batch Versions 6. Batch Applications 7. Media Objects 8. Data Structures

Table I/O is a business function we can create the instruction that perform the table I/O .so there is no need  to create any manually business function in a C language ,and we can use table I/O call the table through event rule and validate table ,retrive record ,delete and add record.

Checking out an object allows you to modify the object and check it back in to Central Objects. Performing a Get copies the latest specifications to your workstation but does not allow you to check in. This is similar to erasing a check out for those familiar with previous releases of OneWorld.

Simple or Inner Join:  Fetch the record only matched rows from  primary table and secondary table. Right Outer Join:  Fetch the record  matched rows from primary table and secondary table and unmatched rows from the secondary table. Left Outer Join: Fetch the record  matched rows from both table primary and secondary table and unmatched rows from primary table.   

The Header Detail form allows you to work with data from two separate tables. You can use this form to add or update a single header record. You can also add, update, or delete multiple detail records from the same form. The Header Detail form includes an input-capable grid so you can add or update detail records. Click OK to perform updates or adds to both tables on the form. When you click Cancel, any changes are lost and no database changes are made. Because the Header Detail form allows you to update or add records from two different tables, you can attach two business views to a Header Detail form. Attach one business view to the grid and the other to the form, updating both tables from a single form. You can use the Header Detail form for one to many relationships.

A subsection join is used in specific circumstances to present data from two different business views in the same report using two sections (a parent and a child) each with a different business view attached. You must join your parent and child sections on common key fields

A data structure is a list of parameters that is used to pass data between applications and tables or forms. There are 2 types of Data Structure. 1. Systems generated Data Structures : Form and Report Data Structures. 2. Users defined Data Structures : Media Object Data Structures, Processing Option Data Structures and Business Function Data Structures.

The layout of a columnar section consists of column headings with the associated column values listed under the headings. Each data field is a column, and each record is a row. The column heading is linked to its column data, and the two cannot be disconnected in the report. If one is deleted, the other is deleted also. Because you cannot change the column format, the columnar section is the least flexible detail section.

Check In - We send the updated specs to the server. It will replace the specs on the server with the specs which we are doing check in. User will not lose the Token. Check Out - It will override the local specs of the object which we are trying to check out. We will get the latest specs from the server. User will get the token.