Full Package Build Procedure

Forms(Interactive Applications)

Interactive Applications

•          After entering into OMW Window select the project to which you want to add the aqpplication and then click on ADD. Now select Interactive Application and select OK.
  
•          Fill all the fields like Object Name, Description, Product code and System Code. The namming Convension of Forms is Pxxxxyy. Click OK.
• 
  
•          Select the object and click on Design then go to Design Tools and select “Start Form Design Aid”.
•       After Entering into Form Design Aid Click on Form, Create and then Select the form which you want to Create.
  
• After adding the Form Click on Edit and attach a Business View

 The Form that is added first will be automatically selected as Entry Point   In this we have Grid Properties and Form Properties separately.   To add Columns to Grid Select the Grid then select the column to be added and click on Insert Column.

• We will have Grid Properties, Form Properties and Column Properties separately.
•          In this we have Grid Properties and Form Properties separately.
•          To add Columns to Grid Select the Grid then select the column to be added and click on Insert Column.
•          To change the Column Properties Right Click on the Columns Added and go to Properties.

•          By entering into Grid Properties we change the alignment of the added columns.
  
•          To Select Multiple Records at a time go to advanced and Select “Multiple Select” Option.
•  And also we have many other options in this Advanced Tab.
•   By clicking on Advanced or Options Tabs Change the properties based on the Requirement.  Fix Inspect Form will not have Grid. 
• Remaining all Forms will have Grid.

Reports

Reports: Reports are used for representing the data in a useful format.

Report Components: The report components are

• Report Introduction: A report exists as a set of specifications that are read by JDE batch engine for processing. We can create variations of a single report using versions.
• Report Objects: JDE is object based. Each report template is considered as batch application. When you add report object the system creates a header record in OL Manager Table(F9860).
• Report Sections: Report sections are basically components of a report. Selection types include:

1. Report header and Report Footer Section: Report Header section appears once at the beginning of the report. Report Footer appears once at the end of the report.
2. Page Header and Page Footer: Page Header section appears at the beginning of every page. Page Footer appears at the end of every page.
3. Detail Sections: These presents the information that the report is designed to convey. The types of sections are Columnar, Group and Tabular. The data for these sections is populated from a business view. In addition to Business View fields we can define and add data fields to detail report section such as data dictionary fields, constants and variables.Within this detail section we can 

• Attach a business view.
• Sequence data using business view fields.
• define level break using data sequencing fields.
• Filter data based on designated criteria.
• Present totals.
• Attach Event Rules.

The guide lines for the size of a report template is not the number of sections but the physical size. A report design should not exceed a size of 45 inches in length and width.

Table Conversion

Table Conversion: It is used for converting data from Table to Table, Table to Text File, Text File to Text File and Text File to Table.

Types of table conversions:

• Data Conversion: Data from records in the input is inserted into records in the output through mapping defined by you. Data Conversion is used to update records in a Table or Business view.

• Data Copy: It consists of one or more tables which are copied exactly from one environment or data source to another environment.

• Data copy with table input: It is similar to data copy except that is also allows information for the process to come from an input table.

• Batch Delete: It allows you to delete a range of records from input tables.

The Environments in Table Conversion are 3. They are

1. Logging Environment
2. Input Environment
3. Output Environment

Procedure for Table Conversion:

• After entering into OMW window Click on 'ADD' button and select Batch Applications and click OK.
• Fill all the fields like Object Name, Description, Product code, System code and select Table Conversion Check box then click OK. Now Table Conversion Object will be added to the project.
•  Click on Design Tools Tab and select Table Conversion Design Aid and click OK.
• In the Table Design Aid We have the Options like Data Conversion, Data Copy, Data Copy with Input and Batch Delete. From that select any one option and click 'Next'.
• If you want to add a Processing Option add it otherwise click Next.
• Select the Input and Output Environments and click Next.
• Select input i.e., Table, Business View,Text file and Foreign Table select any one and then click Next.
• If required add Data Sequencing, then click Next.
• If required define your Data Selection, then click Next.
• Select Output i.e., Table, Foreign Table and Text File Select any one option and click Next.
• Do mapping for the data items from input tables to Output Tables, then click Next.
• Create the version for that batch application save the created version and run the created version.
• We can check the output based on the output selected that is table or text file or foreign table.

1. If you want to convert the data from Text File to Text File then save the Text File in CSV format and upload the Text File in both Input and Out put also. In the user defined formats select the format type as Delimited and in that select 'Tab' option and add data items needed and finish it. In the output click User Defined Formats and select the format type as Delimited and in that select 'Tab' option and add data items needed and finish it. Then only complete data populates from one Text File to another.
2. If you want to convert the data from Table to Text File select the table as input. In the output also upload the Text File and in the User Defined Formats select the format type as Delimited and in that select 'Tab' option and add data items needed and finish it. Then only complete data populates from Table to Text File.
3. If you want to convert the data from Table to Table select the input and output tables. There is no need of changing user defined formats.
4.  If you want to convert the data from Text File to Table, upload the Text File saved in CSV Format and select the User Defined Format type as Delimited and in that select 'Coma' option and add data items needed and finish it. In the output select the Table.There is no need of changing user defined formats. Then complete data populates from Text File to Table.

Data Structures

Data Structures:

Data Structures is a list of parameters that passes data between applications and tables.

The types of data structures are:

1. System defined data structures
2. User defined data structures

System defined data structures: The system defined data structures are form data structure and report data structure.

     Form Data Structure: Each form with an attached business view has a default data structure.This is used to receive or send parameters to other forms.

     

    Report Data Structure: A report is a batch application. Batch application can receive parameters from or send parameters to data structures.

User defined data structures: The user defined data structures are 

1. Media Object Data Structure: It is used to add images or media files.

To create media object data structure:

• After entering into OMW window click on 'Add' button and select media object data structure and click 'OK' button.
• A window will pop up with the fields like object name, Description, Product code, System code. Fill all the fields and click OK button. Media object data structure will be created.

Naming Convention: GTXXXXYYA

GT is media object

XXXX is the file name

YY is next number

      2. Business function data structure: This business function uses source languages as C or NER.

To create a business function data structure:

After entering into OMW window click on 'Add' button and select  Business function data structure and click OK button.
• A window will pop up with the fields like object name, Description, Product code, System code and source language( C or NER ). Fill all the fields and click OK button. Business function data structure will be created.

The naming convention is DXXXXYYYY

      

       3. Data structure: 

To create a data structure:

• After entering into OMW window click on add button and select Data Structure and click OK button.
• A window will pop up with the fields like object name, Description, Product code, System code and type( Regular data structure or Processing option template). Fill all the fields and click OK button. Data structure will be created.

     Processing option Data structure: A parameter list is used to pass processing options to an application. 

Naming convention of processing option data structure is TXXXXYYYY.

Naming convention of Regular Data Structure is DXXXXYYYY

BusinessView

Business View: A business view is a selection of data items from one or more tables.

Table Joins: A table join combines data from individual rows of joined tables. Types of joins are:

1. Simple Join: This includes only rows that match both the primary and secondary tables.
2. Right Outer Join: This includes rows common to both the tables and unmatched rows from secondary table.
3. Left Outer Join: This includes rows common to both the tables and unmatched rows from primary table.
4. Sql 92 left outer join: This includes rows common to both the tables and unmatched rows form primary and null values in the secondary tables.

Adding a business view: 

1. On OMW click 'ADD'.
2. On Add One world object to project, choose business view option and then click OK.
3. On Add object complete all the fields like Object name, Description, Product code, System code, Object use and click OK.

Naming convention: the naming convention is VZZZZZZZZA.

V is business view name.

ZZZZZZZZ is character of primary table.

A is letter to generate view.

Working with business view: It has 4 windows

• Table Join: It defines the tables over which you create the business view.
• Available Tables: It locates tables for selecting and moving to the table joins view.
• Selects columns: It lists the data items from your tables that are included in your business view.
• Properties: we can get all the properties of the object.

To launch Business View Design Aid:

• After entering into OMW window click on existing business view and click the "Design" button in the center column.
• Click on design tool tab and then click start the "Business View Design Aid".

Choosing table and data items for a business view:

• Search the tables and add them to table joins view by drag and drop.
• If we add more than one table to a joins view then the first table is automatically indicated as primary table. If we want we can change it by double clicking on the title bar of desired table. A primary table denoted by a crown symbol in the upper left corner.
• To delete the table from a business view choose it and choose delete from table menu.
• Select the data items highlighted in the table joins window. As you select each item is added to the select column window.
• You cannot join unlike items.

Creating table join:

• Click and draw a line that links a column in the primary table to a column in the related table. You can create joins between the same data items only.
• To delete a join choose it and choose delete from the join menu.
• From the join menu choose types and choose one of the join types: Simple join, Left outer join, Right outer join.
• Click the selected columns view to sequence columns.

Table

Table: 

It is a combination of columns and Rows. Each column is a data item. Each row is a record.

Creating a table:

1. After entering into OMW window click on 'ADD' button and select table option.
2. Fill the fields like Object name, Description, Product code, System code and Column prefix. click ok button then table will be created.

Naming convention:

It's naming convention is FXXXXYYY.

F is Table name.

XX is System code.

XX is Group type.

YYY is Object version.

Working with Table Design:

• After adding a table to the project select the table and click on the design button and click design tool tab and select Table Design Aid.
• In TDA we have four windows like Column, Data Dictionary Browser, Indices and properties.
• We should search for the data items in the DDB and add it to Column.
• Add any one data item as primary key  in the indices window. Then close the TDA and generate Table, Indices.

Defining Indices: We use indices to find specific records and to sort records faster. Each index is comprised of one or more keys which are individual data items.

Working with Tables:

1. GENERATING TABLES: After you have selected data items and assigned indices for your tables, you are ready to configure the table for a specific data source. Table generation also creates .h files.

• To generate table on the table design click the table operation tab, and then click generate table.
• On generate table, complete all the fields and then click OK.  

      2. Generating Indices: To generate indices on table design click the table operations and then click generate indices.

      3. Generating header file: On table design click the design tools tab and then click generate header file.

      4. Copying Table: On the table design click the table operations tab and then click copy table. Complete all the fields and click OK.

      5. Removing tables from database: On table design click table operation tab and then click remove table from database.

Data Dictionary Items

Data Dictionary: It is just as word definition, the JDE data dictionary is a central repository that contains data item definitions and attributes.

Data dictionary is composed of 

• Understanding the data dictionary
• Using the data dictionary
• Defining data item

Understanding the data dictionary:  

• How the data dictionary is used at run time
• Naming data items
• Storing the data dictionary and data dictionary items
• Glossary items
• Error messages
• Understanding default triggers

Using the data dictionary: We can create new data dictionary items and view existing one's with OMW.

Defining a data item: We can define data item specifications when we add, modify or copy a database data item.

Naming convention: the naming convention is YSSS(28D's).The data item name is 32 character alphabetical field that identifies and defines a data item.

                  Y denotes an external data dictionary item.

                   SSS denotes System code number.

                   28D's denotes name of the data item.

Procedure:

1. After entering into OMW window click on "ADD" button then a window will be opened from that window select "Data Item" and click on OK button.
2. Then a message window will be opened asking whether we want to add a glossary data item or a normal data item, click YES if you want to add a glossary item or click NO if you want to add a normal data item.
3. Click on No button.
4. Now a window having the fields like Data item,Alias,Glossary group,Description,Product code,Data type,Size. Fill all the fields and click OK button.
5. If we want we can add Default value,Visual assists,Next number. 
6. DD item is added to the project.  
7. If we want to add a glossary data item in the message window click on YES button.
8. Now a window having the fields like Item specification,Alias,Glossary group,Product code,Product code reporting,Description and Error level. Fill all these fields and click OK button
9. Then the glossary item is added to the project.

Glossary Items:

Glossary Items are items that cannot be attributes in table. Some of the glossary items are C,D,S,K.

C = Data item class

D = Primary Data elements

S = Secondary Data Elements

K = Smart field

Error Messages:

Error messages used in one world are stored as data items.

Understanding of default Triggers:

Default triggers are reusable objects and automatically associated with each application that uses the data item.

We use triggers to 

• Establish field default values.
• Link data items to a user defined code.

Attaching Default Trigger:

We use triggers to initiate display and edit routines associated with data items at application run time. There are several specific type of triggers we can attach including:

• Default value trigger
• Visual assist trigger
• Edit rule trigger
• Display rule trigger
• Next number trigger
• Smart field trigger

Working with Project,Object,Token,Users and Attachments

Working with Project:

•   Viewing the project in the Project window:

After entering in to OMW window fill all the fields and click on “Find” button we can view all the projects.

• Creating a project: After entering in to OMW window click on add button. And select OMW Project then we will get a window.

   

Fill all the fields and click on “OK” button. Then the project will be added to the project window.

•  Advancing the Project: After all the modifications are completed on the project then it is advanced to next level by operating the “Advance Project” button.
•   Adding existing Project to a Project: Search for the Project which we would like to add to our project and click on that project and select our project and click on the arrow button. Then that project will be added to our project.

•            Deleting the Project: we can delete the project only if we have the user role as administrator. Administrator has all rights on the project.

Working with Object:

• Searching for objects: We can search for objects in properties window. After filling all the fields click on “Advanced SEARCH” button. Then we can see all the objects in the Properties window.
  

·         Creating Object:  Click on ADD button and select the object which you would like to create and click OK. Then fill all the fields and click OK. Then the object is created.

·         Adding Object to Project: Search for objects in the properties window. Select the object which you would like to add and also select the project to which the object is to be added. Then click on arrow buttons the object will be added to the project.

·        Moving Object: We can simply drag and drop the objects from one project to other project.

·        Removing Objects: Select the object which you want to remove and click on left arrow button it will be removed from the Project.

·         Deleting the object: After creating the object we have to check in the object once and after that only we can delete the object.

·        Getting object Specifications: If we select the object and see in the properties window we can get its properties like whether it has token or not, it is in check in or check out status......etc

·         Checking objects in and out: If we have token then only we can check in the object. If we are not having the token with us if we check out the object then we will be in the token queue. We will check out the object for getting the token.

·         Changing Objects: On Object Management Workbench, choose an object in the project window. Click the Design button in the centre column. An appropriate design form for the object appears. The current properties of the object appear on the form. Make the necessary changes to the object, and then click OK.

·        Maintaining Objects in Multiple Software Releases: Same-named objects in different software releases can be modified in OMW in the same project. After adding the objects to the project, you can maintain them independently or you can update one to match the other. When working on objects from separate releases, OMW handles save and check-in file paths for you, based on the Object Management Configuration.

Working with tokens:

·       Understanding Token queue: when two or more projects holds the same object only one user holds the token and remaining all users had checked out the object and all are waiting for the token.

·         Inheriting token: when two or more projects holds the same object and all user has token with them then it is known as inheriting token. In this multiple users can work on single object at a time.

After checking out the object it asks us whether we want to be in token queue or to inherit the token select any one option based on the requirement and click select button.

·         Switch Token: This is used to switch a token from on project to another. This might have done if the project owner is not available.

·        Release Token: After the work on the object is completed then the user releases the token so that it will be used by other user to do the modifications on the object.

Working with Users:

Searching for users: In the properties window fill the fields as Owners, User ID and click on search button then we will get all the users in this window.

          Adding user to the project: Select the user you want to add and select the project to which you want to add the user and click on the right arrow button. It asks the role of the user select one of the roles and click ok button. User is added to the project.

       Removing user from the project: Select the user that you want to remove and click the left arrow button. User will be removed.

      After selecting the users by using the arrow buttons we can either add or delete the users from the project.

·        Changing user properties:

 1. On Object Management Workbench, choose a user (owner) in the project window, and then click Select.

2. On Project User Details, complete the following fields, and then click OK:

• User Role

• Project Lead

• Estimated Hours

Working with Attachments:

·        Viewing attachments in design view:

Select the Project and click on design button. A window will be opened in that go to attachments. In this way we can view attachments in design view.

Viewing attachments in the OMW: To get attachments in OMW go to “ROW” and then select “Attachments”.

Advanced Get: Advanced Get will allow you to get the specs from a different path code.

Naming Convention of Project and it's Life Cycle

Naming Convention:

The naming convention of the project is YYYZZZZZ.

YYY = Company-specific code

ZZ = User Reserved Code

ZZ= Module Number

Z= Unique Number

Project Life cycle:

Colour Concept

      COLOUR CONCEPT: 

         

•  Gray Object Icon with Check Mark: Another project holds the token for this object.
•  Coloured Object Icon (not gray): The project that contains the object holds the token for this object.
• Coloured Object Icon with Check Mark (not gray): The project that contains the object holds the token for the object, and the object is checked out.
• Gray Object Icon: This object is not checked out and no project currently holds the object for the token.           
  

OMW Interface

OMW Interface: It has 3 windows:

1. Project Window
2. Action Buttons Window
3. Information Window or Properties Window

1. Project Window: we get all the project details in this window. We have to fill all the fields like user, role and status and click on “Find” button shows all the projects in the Project window. We are having different roles as Originator, Developer, Manager, Quality Assurance, Product Support, PVC Administrator, Training, Documentation and supervisor.

2. Action Buttons Window:

Advance Project: This button is used to advance the project to next level. That is for example from development to testing....etc  

Switch Token: This is used to switch a token from on project to another. This might have done if the project owner is not available.

                                               

Release Token: After the work on the object is completed then the user releases the token so that it will be used by other user to do the modifications on the object.

                                                     

Erase Check Out: This will erase the check out of any object generally you would use this button for any object that you have checked out in error.

      

Check In: (Work station to Server)

 Check in an object when you want to upload its specifications to server and make it publically available.

     

Check Out: (Server to Work station)

This action button is used to check out the object so that we can do modifications on the object.

      

GET: This action button is used to get the latest option specifications.

        

Design: This action button is used to modify an object. The object type will determine which one world tool you will access after processing the design button.

Save: This action button is used to save the medications that are done on an object.

                                                           

Restore: This action button is used to restore any object we have saved. So we can start working on them.

                                                           

Arrow Buttons: This action buttons are used to move the object in and out of the project.                     

3. Properties Window: All the properties of the project like Project name, Description, Project status, Project type.....etc