## Understanding Data Relationships Setup for JD Edwards EnterpriseOne PGCA

The data relationships functionality is part of the base JD Edwards EnterpriseOne software. This chapter provides information that is specific to data relationships for JD Edwards EnterpriseOne Project and Government Contract Accounting (PGCA). It discusses:

- Data relationships and the Create/Edit Project and Government Contracts program.

- Additional data relationships columns for PGCA.

- Updating select columns for PGCA in the F5201 table.

See Also

Setting Up Data Relationships

Updating F0006 and F5201 Records with Data Relationships Rules

### Data Relationships and the Create/Edit Project and Government Contracts Program

The Data Relationships tool is a collection of programs that you can use to increase efficiency during data entry and manage the consistency and quality of data that is entered in the Contract Master table (F5201). You set up data relationships rules to define basis values and default destination values for government contracts. The default destination values appear when you enter a new record in the Create/Edit Project and Government Contracts program (P52G01M). You can also use this data entry program to manually update existing records with default destination values, or you can run a batch program to automatically update existing records.

See Understanding Data Relationships and the Create/Edit Project and Government Contracts Program.

The data relationships functionality for the P52G01M program is similar to the data relationships functionality in other data entry programs in the base software.

See Understanding Data Relationships.

### Additional Data Relationships Columns for JD Edwards EnterpriseOne PGCA

The Business Unit Master (F0006) and Contract Master (F5201) tables include additional columns for JD Edwards EnterpriseOne PGCA functionality.

You can review a list of the columns that support data relationships functionality in the Register Relationship Columns program (P00424). This program also displays the column type, which identifies whether the column can be used for both basis and destination values or for basis values only.

The program logic in the data relationships programs depends on the column type. Some of the columns can be set up only as basis columns.

The column type for AN8O in the F0006 and F5201 tables is hard-coded to be basis-only. The following columns in the F5201 table are used for PGCA and are also hard-coded to be basis-only:

- CASCO

- FDCL

- TINACO

- TOCC

- TOCS

- VTGR

These columns are basis only because they contain information that must remain the same throughout the contract, invoice, and funding levels. If you set up these columns as destination columns, you could cause field values to be inconsistent throughout the contract structure.

If you try to change any of these columns from basis only to basis and destination, the system issues a hard-error message and you are prevented from changing the column type. The system does not prevent you from changing basis and destination column types to basis only; however, you should do this during setup to prevent data integrity issues and not after you begin using the data relationships functionality. If you change a column type to basis only for a column that is not hard-coded and then change the column type back to basis and destination, the system does not issue an error message. To prevent users from changing column types from basis only back to basis and destination, you should add logic in the P00424 program or place security on column types.

Although the software enables you to add new columns to a table, that work should be performed by a software developer or a field consultant because program logic must also be added to accommodate the new columns. JD Edwards EnterpriseOne does not support changes made to column types after the initial setup nor does it support the addition of columns to a table.

#### Columns in the F0006 and F5201 Tables That Support Data Relationships

This section lists all of the supported data relationships columns in the F0006 and F5201 tables.

F0006 Table

This table lists the supported data relationships columns in the F0006 table and identifies whether the column can be used as both a basis and destination column or a basis column only:

Column (Data Item) | Description | Column Type
ADDS | State | Basis/Destination
ADJENT | Adjustment Entry | Basis/Destination
ANPA | Supervisor | Basis/Destination
AN8 | Address Number | Basis/Destination
AN8GCA1–AN8GCA5 | Address Number 1–5 | Basis/Destination
AN8O | Owner Address | Basis only
BUCA | Burden Category | Basis/Destination
CT | Contract Type | Basis/Destination
RP01–RP50 | Category Codes 1–50 | Basis/Destination
STYLE | BU Type | Basis/Destination

F5201 Table

This table lists the supported data relationships columns in the F5201 table and identifies whether the column can be used as both a basis and destination column or a basis column only:

Column (Data Item) | Description | Column Type
AI01–AI15 | Contract Category Code 1–15 | Basis/Destination
ANOB | Address Number–Owner Billing | Basis/Destination
AN8O | Job A/R | Basis only
AN8K | Address Number–Architect | Basis/Destination
* BILLLIM | Billing Limit | Basis/Destination
* BILLMET | Billing Method | Basis/Destination
* BILLST | Billing Status | Basis/Destination
* CAB1–CAB15 | Contract User Defined Address 1–15 | Basis/Destination
* CASCO | CAS Covered | Basis only
CT | Contract Type | Basis/Destination
DS | Contract Status | Basis/Destination
* EPOP | Enforce Period of Performance | Basis/Destination
* FDCL | Flow Down Clauses Apply | Basis only
INVF | Invoice Format Code | Basis/Destination
* KEYP | Key Personnel | Basis/Destination
* OWOR | Owning Organization | Basis/Destination
* QCOPR | Quick Close Out Provision | Basis/Destination
* REVLIM | Revenue Limit | Basis/Destination
* REVMET | Revenue Method | Basis/Destination
* REVST | Revenue Status | Basis/Destination
* TINACO | TINA Covered | Basis only
* TOCC | Type of Contract (Client Type) | Basis only
* TOCS | Type of Contract (Client/Sub) | Basis only
USA1–USA5 | User Address Number 1–5 | Basis/Destination
* VTGR | Vendor Type Goals Required | Basis only

The columns that are used in the Create/Edit Project and Government Contracts program (P52G01M) are identified with an * (asterisk).

### Updating Select Columns for JD Edwards EnterpriseOne PGCA in the F5201 Table

You can update records for JD Edwards EnterpriseOne PGCA in the F5201 table with data relationships rules using one of these methods:

- Manually update the records in the Create/Edit Project and Government Contracts program (P52G01M).

- Automatically update the records by running the Update Data Relationships program (R00422).

See Updating F0006 and F5201 Records with Data Relationships Rules.

Regardless of whether you update records manually or automatically, the system follows the same guidelines to update the data relationships rules in the F5201 table with one exception. The exception applies to these columns in the F5201 table, which are used specifically for JD Edwards EnterpriseOnePGCA:

- USA4

- USA5

- CAB9

- QCOPR

When you manually update records in the P52G01M program, the system applies the changes to related invoice (C2) and funding levels (C3) for the columns listed. For example, if you manually change the CAB9 column at the invoice level to a new value, the system updates the funding level with the same value. Typically, the values for these columns are the same at the invoice and funding levels (that is, the C2 and C3 values are the same).

When you run the R00422 batch program to automatically update F5201 records, the system does not update the funding level for the USA4, USA5, CAB9, and QCOPR columns (that is, the C2 and C3 values are not the same). Having different column values at the invoice and funding levels does not negatively affect the contract or any subsequent processes.