Data Relationships and the Create/Edit Advanced Contracts Program
To set up advanced contract billing contracts, you use the P52G01M program. This program is enabled with the functionality that is provided by the Data Relationships tool. The Data Relationships tool is a collection of programs that you can use to manage the consistency and quality of data that users enter. When you implement data relationships for the P52G01M program, you can place tighter controls over your contract data and increase efficiency during data entry for contracts.
You use the tool to define relationships between columns (data items) in the F5201 table, which stores the contract master information, and then you define default destination values. The system populates the fields with the destination values that you want to appear when you enter a single basis value in the P52G01M program.
When setting up data relationships for the P52G01M program, consider the rules described in the following table:
|
Rule |
Description |
|---|---|
|
1 |
Some of the columns in the F5201 for which you can set up data relationships can be set up only as basis columns. These columns contain information that must remain the same throughout the contract, invoice, and funding levels:
Enabling these columns to be set up as destination columns could cause the field values to be inconsistent throughout the contract structure. |
|
2 |
When you create a new contract at the contract level, the data relationships that you have set up apply not only to the contract level but also to the invoice and funding level contracts. |
|
3 |
If you revise fields at the contract level for which data relationships exist, the system applies changes to the related invoice and funding levels only for the fields that must remain the same throughout the contract structure. |
|
4 |
If you set up a data relationship for one of the columns that does not have to remain the same throughout the contract structure and you select the Enforce Rule check box for the relationship, the system prevents you from being able to maintain consistency for the field value throughout the contract structure. In other words, if you change the field value at the contract level, then the system protects the same field from input at the invoice and funding levels because the Enforce Rules check box is selected. |
|
5 |
Check boxes function differently than fields, especially with regard to the setting for the Enforce Rule check box for the data relationship. When you add new contracts, the system updates check boxes with the value from the data relationship, regardless of the setting for the Enforce Rule check box for the data relationship. However, when you revise contracts, the system updates the check boxes only if the Enforce Rule check box for the relationship is selected. Most of the check boxes in the P52G01M program are basis-only columns, so they are not affected by this rule. These check boxes are affected by this rule:
|
|
6 |
You assign a sequential order to the column relationships. If the Enforce Rule check box is not selected for a column relationship, the system checks the subsequent relationships and, if the Enforce Rule check box is selected for the subsequent relationships, the system populates the destination values based on the rules that you set up. See Example 3. |
You can run a batch program to update multiple contracts at one time. You run the Update Data Relationships program (R00422) to update existing contracts. However, the R00422 program does not update the destination values at the funding level for these fields in the F5201 table:USA4, USA5, CAB9, and QCOPR.
See Updating Select Columns for JD Edwards EnterpriseOne Advanced Contract Billing in the F5201 Table.