Security Table

 Top  Previous  Next

Security Table

 

To enable Branch/Plant, Search Type or Dream Writer Security, you will need to create a file in the Host Control Library (UES_20) called SECURITY.

 

Field

Description

Attribute

Default *

Default **

SECUI

User Id or Group Id

10 Alpha

None, NULL Invalid,

*PUBLIC for All

None, NULL invalid

*Public for ALL

SECBP

Apply Branch Plant Security

1 Alpha

0 - NO

1 - YES

SECST

Apply Search Type Security

1 Alpha

0 - NO

1 - YES

SECDW

Apply Dream Writer Security

1 Alpha

0 - NO

1 - YES

SECVL

Expose Logicals to Schema

1 Alpha

1 - YES

1 - YES

SECVB

Expose Business Views to Schema

1 Alpha

1 - YES

1 - YES

SECVP

Expose Physical Tables to Schema

1 Alpha

1 - YES

1 - YES

SECV3

Expose 3rd Party Tables

1 Alpha

1 - YES

1 - YES

 

 

Once the SECURITY file has been created, using either SQL, DFU or UPDDTA, enter records into this file by either JD Edwards User Id, Group Id or *PUBLIC, setting each of the 7 flags to either 1 for YES and 0 for NO.

 

Default *

Default values used in the absence of the host control library or the SECURITY file.

 

Default **

Default values used in the absence of the user or group profile record where the SECURITY file exists in the host control library.

 

Please refer to the following additional guides to understand how World Security is set up and configured in JD Edwards:

 

World Business Unit Security  (54k)

World Technical Foundation  (2.6meg)

 

 

SECBP - Branch Plant Security

Set this flag to 1 where you require the Business Unit Security as defined in the F0001 file to be applied.

 

SECST - Search Type Security

Search Type Security records are not stored in a dedicated file.  Instead they are stored in UDC records in the F0005 UDC detail table under system code 94.  Note that this type of security can

only be set up at the user level.  Security by Group or *PUBLIC is not allowed.

 

The possible values for Search Type security are stored in UDC 94 in the F0004.  Set this SECST flag to 1 where you require the Search Type Security as defined in the F0004 and F004 files to

be applied.

 

Please note that where security is set up in F0005 UDC 94, a corresponding entry must be made for that specified Search Type value in F0004 UDC 94 .  Data results may become unpredictable

without this entry.

 

SECDW - Dream Writer Security

Dream Writer security will switch fields off from the users view. Set this flag to 1 where you require the Dream Writer Security as configured in the F9401 file to be applied.

 

Please note that secured out fields should not be included in Business Views as this will cause the business view to fail.

 

SECVL - Expose Logicals

Set this flag to 0 where you DO NOT want logical files to be exposed to the file schema.

 

SECVB - Expose Business Views

Set this flag to 0 where you DO NOT want Business Views to be exposed to the file schema.

 

A business view is a pre-defined view over your data. This could be a join over the Sales Header and Detail, or a view over the Item Master but excluding a range of Item Codes.  The jdeDirect

implementation of Business Views is very flexible giving you total control to decide on which files and fields are exposed to the user.

 

Business Views are defined in a file called VIEWDEF. The jdeDirect ODBC driver will load this file from the Control Library.  You will need to create a file in the Host Control Library called

VIEWDEF.

 

Field

Description

Attribute

VDNAME

Name/Description of the View

50 Alpha

VDSQL

SQL Statement of View

1024 Alpha

 

 

A simple example of a Business View would be:

 

VDNAME Sales_Headers_at_SO_and_Address_Book_Link

VDSQL SELECT F4201.*, F0101.* FROM F4201 INNER JOIN F0101 ON F0101.ABAN8 = F4201.SHAN8 WHERE ((F4201.SHDCTO = 'SO'))

 

The SQL statement needs to be in simple iSeries (AS/400) SQL format.  Ensure that it executes without error on the AS/400 prior to configuring the Business View.

 

Note:

•Business Views should not include fields that have been secured out from the user using Dream Writer Security as this will cause the business view to fail.

 

•By setting the Expose Business Views to 1 (ON) you will automatically cause the Physical and Logical files to be exposed as the view SQL will make reference to these files.

 

•If you intend to use your Business Views with Crystal Reports, ensure you do NOT use any spaces when naming your Business View (VDNAME)

 

 

SECVP - Expose Physicals

Set this flag to 0 where you DO NOT want physical files to be exposed to the file schema.

 

 

SECV3 - Expose Third Party Files

Set this flag to 0 where you DO NOT want 3rd Party Files to be exposed to the file schema.

 

A 3rd party file can be any file that is not already defined in Software Version Repository (SVR) as part of the World system. To enable this feature, you need to create a file called FILES3PT in the Host Control Library with the following definition.

 

 

Field

Description

Attribute

 

 

F3FIL

Name of the 3rd Part File

10 Alpha

 

 

F3LIB

Library *LIBL Allowed

10 Alpha

 

 

F3ENV

Name of JDE World Environment

10 Alpha

 

 

F3MBR

Multi-Member 1=Yes, 0=No **

1 Alpha

 

 

 

 

 

 

 

3rd party files are only exposed when the user logs into the driver into the specified environment, use AS/400 DFU or UPDDTA to update and maintain this file, entering the names and library names of the 3rd Party files you want to expose along with the equivalent JDE World Environment name.

 

NOTE:

Do not enter the names of existing JDE files, these are not considered 3rd party and will cause the driver to return erroneous results.

Duplicates will be ignored.

 

** Multi-member files are not currently supported, only the *FIRST member will be exposed at the moment, this feature may be supported in the future.

 

 

 

 

 



Page URL: http://www.unitysolutions.com/Helps/Unity_ODBCv2/HTML/index.html?world_host_config_security_table.htm