1. Advanced Contract Billing Implementation Guide
  2. Additional Data Relationships Columns for JD Edwards EnterpriseOne Advanced Contract Billing

Additional Data Relationships Columns for JD Edwards EnterpriseOne Advanced Contract Billing

The Business Unit Master (F0006) and Contract Master (F5201) tables include additional columns for JD Edwards EnterpriseOne Advanced Contract Billing 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 advanced contract billing 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.