JD Edwards Integration
Oracle's scalable JD Edwards EnterpriseOne construction suite enables you to integrate virtually all of the information you have about your properties, allowing you to streamline your
financial and operations processes over the real estate lifecycle.
|
JD Edwards Data Validation
 Data validation is a critical component of the JD Edwards EnterpriseOne integration with Content Manager. Data validation ensures that the document management system is operated on correct, clean and up-to-date JD Edwards EnterpriseOne data. Often this process is carried out for the purpose of making EnterpriseOne data available to end-users without giving them access to the EnterpriseOne software. It also ensures data consistency between the two programs and eliminates manual entry. Popular data validation includes Data Lookup and Commitment Pull.
Data Lookup
Lookups, like in JD Edwards EnterpriseOne, provide an easy way to ensure users input valid information into the appropriate fields. Lookups can be as simple as showing a list of vendors, or as complicated as providing the user with a list of valid cost types for the company, job and phase that they have entered for a particular invoice detail line. Lookup fields are typically configured to mirror EnterpriseOne but may be customized to customer requirements if necessary.
Commitment Pull
Content Manager's standard detail grid provides a great way to code invoices; however, for those invoices that have the coding lines already setup in JD Edwards EnterpriseOne, implementing the Commitment Pull feature is a great advantage. The Commitment Pull provides real-time access to EnterpriseOne's Job Cost data from Content Manager. Users are presented with a grid showing all lines in EnterpriseOne for that particular commitment. Users then select lines that apply to that invoice and enter the current amount for the line item being approved.
Advanced Validation
JD Edwards EnterpriseOne clients that have advanced validation needs, a solution feature provided allows for customer-created Stored Procedures to be executed when a user attempts to approve a document. The Stored Procedure will have access to any field value from the document and when completed will return a warning or error message stating the reason the document failed validation. If the information validated successfully, the user sees nothing and the document is approved. Stored procedures can include verifying that the subcontract has been signed, insurance is up to date and a lien release is present.
Return to Content Manager JD Edwards Integration
|
