Today on, we are going to start series of Interview questions on JD Edwards Technical for all. Many questions may be simple or of basic level, as we would like to include questions asked to the person with 1 year experience too. We will be having questions regarding technical scenarios and competencies too.
- What is an Object in JDE? Define Some…
Traditionally a OneWorld Object was defined as any object created in Object Librarian.
Ex: Applications, Business Functions,Business Views, UBEs, Data Structures, Tables, Media Objects
- How do JDE Stores Objects?
Provides a central location for managing all OneWorld objects. Only used for Development & Software deployment.
Never used at runtime.
- What are Replicated Objects?
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
- What are Control Objects?
Control objects are like buttons on the Form as Control obj. Fields on the Form are also control objects.
We set control errors on the form design so that it stops the processing of error is set on the control.
- What are tokens?
A Token has a One-to-One relationship with the following objects:
Applications, Business Functions, Business Views, UBEs, Data Structures, Tables, Media Objects and Batch Versions
The Token is used to minimize the possibility of one user overriding another user’s changes to an object.
When an object is checked out and is not already checked out by another user The project receives a Token.
A Token can be released, switched or inherited.
The Token is released by the project when the project reaches the status designated by the administrator for release.
A Token is not released by the project when the object is checked back in.
- What is OMW?
As a OneWorld developer I sometimes long for the simple days before XE. I could check out objects from any environment and check them back into any environment. I could more easily view if an object was checked out and to who and which environment. I could easily see what objects I personally still had checked out locally. I could also transfer objects from one environment to another with a few mouse clicks.
The OMW was designed to replace the old tools we were used to using such as the Object Librarian, Promotion Manager, and Object Transfer. I believe that the OMW is a great tool when it comes to developing for new projects. I like the fact that I can group up all of the objects I am working on into a project so I never forget the objects I created or modified for the new module I am creating. In the old days you would have to keep track of objects in a separate file to give to the CNC guy once it was ready to deploy. Using the old method, how many times do you remember leaving off 1 or 2 objects because you forgot to write them down?
- Promotion Manager
- Object Transfer
- Object Librarian
- Object Librarian Check-in Log
- To Hide Object Management Tasks
- To Provide Better Control of OneWorld Objects
- To Unify all Development into One Interface
- To Automate Change Management Process
- To Provide Detail Logging of Objects
- What is Check In & Check Out?
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
- What is the difference between GET & Check Out?
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.
- What are the Object Librarian and Non-Object Librarian Objects?
Only Object Librarian objects have tokens and Non Object Librarian Objects do not have token.
non-Object Librarian objects are based on data source rather than path code.
One World objects include the following non-Object Librarian objects:
- Data dictionary items
- User defined code items
- Workflow items
- What are the required fields when adding an Object?
Object Name, Description, Product Code, System Code, Object Use
More Questions & Answers coming on the way!