Understanding Log Information

Log information is supplemental to the information contained in an order. It includes details such as submittals and transmittals. A submittal is information that you need to receive from a subcontractor or supplier, for example, proof of insurance and licensing. A transmittal is information that you need to send to a subcontractor or supplier, such as permission to proceed. Logs can also include information relevant to the order such as meeting dates, notes, and so forth.

Checks and balances are put in place during the progress payment function to enforce compliance with the logs. You can assign dates to log information so that the system issues an outstanding submittal warning when you try to make payments before you receive all of the submittals. For example, if you require a subcontractor or supplier to submit insurance information to you before you make a payment against the order, you can specify for outstanding submittal warnings. The system then warns you if you try to make a payment before you receive the information. Thus, a hold code is placed on the payment until the requirement is satisfied.

You can enter new log information into a contract, or you can copy log information into an order from a model log. A model log is a set of standard log information that you can copy into the contracts and then modify for each contract. The copy feature saves you time when you have log information that is duplicated across many orders.

Log information is typically specific to the vendor and not on a contract-by-contract basis. However, bonding can be at a job or contract level. Logs can be entered and modified at multiple hierarchical levels. Log details can be added at an individual contract level or at global levels, such as company, subcontractor, project, or job. These individual levels can then be activated or deactivated based on the business process.

You can enter logs from contract entry at any time during the project. The logs and hierarchies are maintained in the Log Master table (F4305).

You can view log details through multiple online views and reports. You can search and view all levels of a hierarchical log with the Logs Entry program (P4305) by setting the processing options to specify the contract type and log view options. You can use the Log Hierarchy Constants program (P4304) to review outstanding logs.

The F4305 Logs Report program (R43050) prints logs at different hierarchies for you to review. The Logs (F4305) Report/Update program (R43540) allows you to specify whether you want to print and review associated text and contract management reports when running the report. You can also specify whether the system changes the log status code. You can also use the Order Detail Print report (R4401P) to print contract details for the logs at either all hierarchical levels or at just the contract level.

See "JD Edwards EnterpriseOne Subcontract Management Reports" in the JD Edwards EnterpriseOne Applications Subcontract Management Implementation Guide.

If you are currently using the Log Master Revisions program (P4303) for single-level logs at the contract level, data is stored in the Log Master table (F4303). You can run conversion programs and use the hierarchal logs feature.

Note: You can use either the Log Master Revisions program (P4303) or the Logs Entry program (P4305) to create and maintain log information. You cannot use both log programs in the system. Purchase Order Entry and Voucher Match read UDC 40/VF and call the Log Master Revisions or Logs Entry program based on the setting in the UDC.