Contract Management Exchange User’s Guide - … Management Exchange User’s Guide ... and we disclaim liability for any damages caused by such use of the ... Contract Management

CCoonnttrraacctt MMaannaaggeemmeenntt EExxcchhaannggee UUsseerr’’ss GGuuiiddee VVeerrssiioonn 11..00

2

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle and Primavera are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

To view the Contract Management 13.0 Commercial Notices and Disclosures for Documentation, go to the Documentation folder of the Contract Management physical media or download.

3

CONTENTS

OVERVIEW ......................................................................................................................................... 5 Introduction ....................................................................................................................................... 5 Where to Get Support ....................................................................................................................... 6 Contract Management Business Objects ........................................................................................ 7

INSTALLING AND CONFIGURING CONTRACT MANAGEMENT EXCHANGE......................................... 9 Installing Contract Management Exchange ..................................................................................... 9 Setting Up Your Environment ......................................................................................................... 10

USING CONTRACT MANAGEMENT EXCHANGE ............................................................................... 13 Connecting to the Contract Management Application Server ...................................................... 13 Using SSL With Contract Management Exchange ......................................................................... 14 Importing Project, Cost Codes, and Contracts ............................................................................... 15

Importing data into the Contract Management Module .......................................................... 15 Importing Projects ...................................................................................................................... 17 Importing Cost Codes ................................................................................................................. 18 Importing Contracts ................................................................................................................... 19

Importing and Exporting Requisitions and Change Orders........................................................... 21 Importing Requisitions ............................................................................................................... 21 Exporting Payment Requisitions................................................................................................ 21 Importing Change Orders ........................................................................................................... 25 Exporting Change Orders ........................................................................................................... 26

TROUBLESHOOTING ....................................................................................................................... 29 Interpreting Log Messages ............................................................................................................. 30

5

IN THIS CHAPTER

Introduction .............................................................................................................. 5 Where to Get Support .......................................................................................... 6 Contract Management Business Objects ........................................................... 7

INTRODUCTION

Primavera Contract Management is a multiuser, multiproject application that provides a centralized way to store, organize, and track project information so you can keep your contracts on time and within budget. When you use the Contract Management module to manage your projects, you access the module from a client Browser to enter, view, or print project information.

Using Contract Management Exchange, you can share and synchronize Contract Management information with JD Edwards EnterpriseOne and other applications using XML files as an intermediary exchange mechanism.

The XML data files can be placed and retrieved to and from either a local mapped drive or an FTP site located on a remote or local server.

About this Guide

This guide provides information on installing and using Contract Management Exchange to import and export XML files in and out of Contract Management.

See Also

Detailed information about Contract Management is available in the Contract Management User’s Guide, available from the Contract Management release media or download.

Detailed information about using Contract Management Exchange to integrate with JD Edwards EnterpriseOne is available in the JD Edwards EnterpriseOne 9.0 Integration with Primavera Contract Management Implementation Guide. This document is available at https://support.oracle.com/CSP/ui/flash.html.

Chapter 1 OVERVIEW

6

Contract Management Exchange User’s Guide

WHERE TO GET SUPPORT

If you have a question about using Oracle Primavera products that you or your network administrator cannot resolve with information in the documentation or Help, go to:

http://www.oracle.com/primavera/support.html

This page provides the latest information on contacting Oracle Global Customer Support and the support renewals process.

7

Chapter 1 Overview

CONTRACT MANAGEMENT BUSINESS OBJECTS

The XML files that Contract Management Exchange uses to import data into Contract Management must adhere to the cmexchange.xsd schema file located in the CM Exchange Home/schemas directory, where CM Exchange Home is the location in which you installed the Contract Management Exchange application. The cmexchange.xsd schema file defines which business objects may exist in the XML files that are used with Contract Management Exchange.

The following table presents a summary of the Contract Management business objects that you can import into and export out of Contract Management using Contract Management Exchange.

Note: The table below lists the Contract Management objects that you can import and export using Contract Management Exchange. Refer to the Contract Management XML API documentation for information on importing or exporting additional Contract Management business objects.

CM Business Object Import into CM Export out of CM

In Contract Management, a Project consists of modules, logs and documents.

Yes. Projects imported into Contract Management must contain the following elements: Name Title CompanyCode EngineerOfRecordCompanyCode SubmittalCoordinatorCompanyCode

No

Cost Codes are used to break down costs in the Cost Worksheet into categories

Yes. CostCodes that are imported into CM must contain the following elements: ProjectName CostCode Title

No

Contracts are created in the Primavera Contract Management system. Contracts are written agreements in which one party agrees to perform specialized work for another party for a certain price. CM Exchange enables you to import two types of Contracts: Budgeted contracts represent

the amount of resources allocated to complete the

Yes. Contracts that are imported into CM must contain the following elements: ProjectName DocumentNumber ToCompanyCode FromCompanyCode An optional element, DistributedTo, determines whether the contract is imported as a budgeted or committed

No

8


CM Business Object Import into CM Export out of CM

project. Committed contracts are

agreements between parties to perform a portion of the work.

contract. If the DistributedTo element is omitted, the Contract is imported as a committed contract.

Requisitions are formal requests for payment and are usually issued by general contractors (GCs) to the owner on a monthly basis as portions of work on a project are completed.

Yes. Requistions that are imported into CM must contain an ApplicationNumber element.

Yes, if the requisition has been certified.

Change orders specify a redirection of plans or introduce new items to the schedule. Change orders also show any approved increases or decreases in costs and contract item allowances.

Yes. A ChangeOrder must contain the following elements: ToCompanyCode FromCompanyCode ChangeNumber

Yes, if the change order has been approved.

9

IN THIS CHAPTER

Installing Contract Management Exchange........................................................ 9 Setting Up Your Environment ........................................................................... 10

INSTALLING CONTRACT MANAGEMENT EXCHANGE

Java Runtime Environment Requirements

Java Runtime Environment (JRE), version 1.6.x, also known as J2SE 6.0, or Java Development Kit (JDK), version 1.6.x, also known as J2SE 6.0, is required to run CM Exchange. While CM Exchange is compatible with any 1.6 version, we recommend using Update 15 or later.

You can download the JRE or Java JDK from http://java.sun.com/products/archive/. Please ensure that it is installed before running the setup.exe file.

To Install Contract Management Exchange 1) From the Contract Management Exchange folder of the physical media or download location,

navigate to the Disk1\install directory and then double-click on the setup.exe file. 2) On the Welcome screen, click Next. 3) On the Specify Home Details dialog box:

a. Enter an appropriate name for Contract Management Exchange in the Name field. b. Specify the installation location for the Contract Management Exchange files in the Path field. c. Note: Contract Management Exchange does not have to be installed on the same server as

Contract Management. d. Click Next.

4) On the Java Home Directory dialog box: a. Type or browse to the location where Java is installed. The setup wizard automatically detects

the JDK/JRE on your local machine. To specify a different location, enter the path, or click Browse to select it.

b. Click Next. 5) On the Summary dialog box, click Install. 6) On the End of Installation dialog box, click Exit. 7) The following shortcuts are added to the Oracle - Primavera Contract Management |

Contract Management Exchange entry in your Start menu:

Chapter 2 INSTALLING AND CONFIGURING CONTRACT MANAGEMENT EXCHANGE

10


Contract Management Exchange Contract Management Exchange User Guide Readme

SETTING UP YOUR ENVIRONMENT

Before you can use Contract Management Exchange to synchronize Contract Management data with other applications, you need to prepare the Contract Management environment. This involves the following steps:

1) Ensure all patches and updates have been installed. For a list of the required releases and patches, see the Readme that accompanies Contract Management Exchange.

2) After you install all required items, you must then import EXP_CMPROJ_EXCHANGE.jar, a file that contains an empty project, into the Contract Management system. This project includes the following custom fields that are required for Contract Management Exchange: Amount Paid Tax Amount Paid Date Exported Date Imported To import this project and add the custom fields to the Contract Management module, follow the Importing the Empty Project steps below.

3) Determine how you will be exchanging the XML import\export files. You can set up Contract Management Exchange to use a local or remote FTP site to exchange the XML files. Alternatively, you can use a mapped drive to exchange the files. If you are using an FTP site to exchange the XML files, ensure that the following information is available: URL to the FTP site, including the path to the transfer directory FTP User name and Password

11

Chapter 2 Installing and Configuring Contract Management Exchange

Importing the CMExchange Setup Project 1) Navigate to your <CM Exchange Home>\ directory and locate the EXP_CMPROJ_EXCHANGE.JAR

file 2) In Contract Management, use the Single Project Restore function to import the file. Restoring the

project in the EXP_CMPROJ_EXCHANGE.jar file loads the custom definitions into the Contract Management module.

13

IN THIS CHAPTER

Connecting to the Contract Management Application Server ................. 13 Using SSL With Contract Management Exchange ........................................ 14 Importing Project, Cost Codes, and Contracts ............................................ 15 Importing and Exporting Requisitions and Change Orders ....................... 21

CONNECTING TO THE CONTRACT MANAGEMENT APPLICATION SERVER

To connect to the Contract Management Application Server: 1) From the Oracle - Primavera Contract Management | Contract Management Exchange

entry in your Start menu, click Contract Management Exchange. 2) On the Contract Management Exchange dialog box, complete the following fields in the Enter

the Contract Management server information area and then click Next: Server Host: Enter the name of the server that is hosting the Contract Management service. CM Server Port: Enter the port number corresponding to the Contract Management service. Service Type: Select Standard if the Contract Management service is set up to use the HTTP

protocol. Select SSL if it is set up to use the HTTPS protocol.

Note: If you are using SSL, follow the steps in Using SSL with Contract Management Exchange (on page 14).

3) In the Enter your Contract Management login information area, enter a valid user name and password for the Contract Management system and then click Next. Note: The user that you log in as must have access and permission to insert data into the Contract Management database. If the user credentials you enter do not have sufficient access, the system will produce an error, and you will not be able to continue.

Chapter 3 USING CONTRACT MANAGEMENT EXCHANGE

14


USING SSL WITH CONTRACT MANAGEMENT EXCHANGE

If you are using SSL to connect to the application server, follow these steps to generate and use a keystore for use with Contract Management Exchange.

1) Obtain the .cer file from the server that is hosting Contract Management. a. Access Contract Management using your browser via HTTPS. For example, connect to

http://myserver b. Accept the certificate c. Export the .cer file. The precise instructions for doing this will vary with the browser. For

example, in Internet Explorer: From the Tools, Internet Options menu, select the Content tab. Click Certificates. Then choose the appropriate certificate and click Export.

2) Use the JDK keytool command to generate a keystore from the certificate you exported in the previous step. Access a command line and type the following command: keytool -import -trustcacerts -keystore mykeystore -storepass mypassword -noprompt -file mycert.cer Where mykeystore is the name of the keystore you are generating, mypassword is the password for the keystore, and mycert.cer is the certificate you exported in the previous step.

3. Navigate to your <CM Exchange Home>\ directory and open the .cmd file in a text file. 4. Open the certificate file that you created in step 2 and use it to change the following line in the

cmexchange.cmd from this

"%JAVA_HOME%\bin\java" -classpath "%LIB_DIR%/cmexchange.jar;%LIB_DIR%/jdom.jar;%LIB_DIR%/xml.jar;%LIB_DIR%/xmlparserv2.jar;%LIB_DIR%/commons-net-2.0.jar" com.primavera.cmexchange.client.intg.CMExchangeApp to follow this example:

"%JAVA_HOME%\bin\java" -Djavax.net.ssl.trustStore=<path to mykeystore> -Djavax.net.ssl.trustStorePassword=<password> -classpath "%LIB_DIR%/cmexchange.jar;%LIB_DIR%/jdom.jar;%LIB_DIR%/xml.jar;%LIB_DIR%/xmlparserv2.jar;%LIB_DIR%/commons-net-2.0.jar" com.primavera.cmexchange.client.intg.CMExchangeApp

15

IMPORTING PROJECT, COST CODES, AND CONTRACTS

IN THIS CHAPTER

Importing data into the Contract Management Module ............................. 15 Importing Projects ............................................................................................... 17 Importing Cost Codes ........................................................................................ 18 Importing Contracts ............................................................................................ 19

IMPORTING DATA INTO THE CONTRACT MANAGEMENT MODULE

Note: Before using this procedure, you must first use EnterpriseOne to create an XML file that can be validated against the cmexchange.xsd schema file.

1) Follow the procedure in Connecting to the Contract Management Application Server (on page 13).

2) Select the Contract Management database you want to import data into and then click Next.

Chapter 4

16


3) Under Select the action to perform, select Import data and click Next

4) Specify the location of the XML file to import. Either browse to a file on a mapped drive or specify

the address of the file on an FTP site. Specify a folder for the log files and then click Next.

5) Click Finish to confirm your selections.

The system imports the selected data and produces a log file for review.

17

Chapter 4 Using Contract Management Exchange

IMPORTING PROJECTS

In Contract Management, a Project consists of a collection of modules, logs and documents. When you use Contract Management Exchange with EnterpriseOne, business units along with an extended job master are the equivalent of a Contract Management project.

Constraints: Projects that you share between EnterpriseOne and Contract Management must first be created in EnterpriseOne. The XML file that you use to import the projects into Contract Management must contain the following elements: Name Title CompanyCode EngineerOfRecordCompanyCode SubmittalCoordinatorCompanyCode

Optional Elements

Projects that you import into Contract Management may optionally contain the following elements:

CompanyName EngineerOfRecordCompanyName SubmittalCoordinatorCompanyName SubmittalCoordinatorContactCode SubmittalCoordinatorContactName ProjectSettings

See the cmexchange.xsd schema file located in the <CM Exchange Home>\schemas directory for additional information about the Project elements.

Usage Guidelines

To import project data into the Contract Management Module, first use EnterpriseOne to create an XML file that can be validated against the cmexchange.xsd schema file. Then follow the instructions in Importing data into Contract Management (see "Importing data into the Contract Management Module" on page 15). When you import the XML file into Contract Management, Contract Management Exchange creates the project(s) that are specified in the XML file, creates any associated company and contact records, and populates the Date Imported field. Once the projects have been imported into Contract Management, you can use Contract Management to add additional project settings to the projects.

If you import a project that already exists it is treated as an update.

When Contract Management Exchange imports a project:

It determines whether the company names already exist. If the company names do not exist, Contract Management Exchange adds the company names as project companies.

18


For the CompanyCode, Contract Management Exchange creates the company with the value in the CompanyName field.

It treats EngineerOfRecordCompanyCode in the same manner. It also creates a contact record for each of these if there is not already a default contact defined. For those fields that do not have a default contact defined, Contract Management Exchange creates

the contact with the initials of “TBD” and the Name of “To be determined." It also treats the SubmittalCoordinator fields the same with the exception that it uses the values in

the Contact fields if they exist.

See the Specifying Project Settings section in the Contract Management User’s Guide and the Synchronizing Project Data chapter in the JD Edwards EnterpriseOne 9.0 Integration with Primavera Contract Management Implementation Guide for additional information.

IMPORTING COST CODES

Cost Codes are used to break down costs in the Cost Worksheet into categories. The account structure in EnterpriseOne is the equivalent of cost codes in Contract Management.

Constraints:

Cost Codes must be created in Contract Management. Additionally, cost codes that you import into Contract Management must contain the following elements:

ProjectName CostCode Title

Usage Guidelines

To import cost code data into the Contract Management Module, first use EnterpriseOne to create an XML file that can be validated against the cmexchange.xsd schema file, and then follow the instructions in Importing data into Contract Management (see "Importing data into the Contract Management Module" on page 15). You import cost code data into Contract Management so that you can use those cost codes in the cost code worksheet. For additional information about cost codes see the Setting Up Cost Codes and Modifying Cost Worksheet section of the Contract Management User’s Guide.

19


IMPORTING CONTRACTS

Contracts are created in the Primavera Contract Management system, and are written agreements in which one party agrees to perform specialized work for another party for a certain price.

CM Exchange enables you to import two types of Contracts:

Budgeted contracts represent the amount of resources allocated to complete the project. Committed contracts are agreements between parties to perform a portion of the work.

Contracts can contain contract line items along with cost details. Contract line items and their associated cost details enable you to enter itemized costs for the contract.

A purchase order in EnterpriseOne is the equivalent of a committed contract in Contract Management. A project budget is the equivalent of a budgeted contract in Contract Management.

Constraints:

Contracts can only be imported into Contract Management once. If you import a contract that already exists, Contract Management Exchange skips the contract but processes any change orders, requisitions, or line items that are related to the contract, updating any line items that it encounters.

When you use Contract Management Exchange to import contracts, the contracts must originate in EnterpriseOne; you cannot use Contract Management to create contracts that are shared with EnterpriseOne.

Additionally, contracts that you import into Contract Management must contain the following elements:

ProjectName DocumentNumber ToCompanyCode FromCompanyCode

Optional Elements

An optional element, DistributedTo, determines whether the contract is imported as budgeted or committed contract.

Other optional Contract elements include the following elements:

ToCompanyName ToContactCode ToContactName FromCompanyName FromContactCode FromContactName DocumentDate Title DistributedTo CalculateRetainageUsingSummaryPercentages

20


UsePercentOfCompletedWorkForRetainage UsePercentOfStoredMaterialForRetainage EnterRetainageOnRequisitionLineItems RetainagePercentForNewLineItems ContractLineItem Requisition ChangeOrder

Usage Guidelines

The first step in working with contracts is to import the project budget from EnterpriseOne as a budgeted contract into Contract Management. The original budget amounts in EnterpriseOne create a single budgeted contract in Contract Management.

To import contract data into the Contract Management Module, first use EnterpriseOne to create an XML file that can be validated against the cmexchange.xsd schema file, and then follow the instructions in Importing data into Contract Management (see "Importing data into the Contract Management Module" on page 15).

For both budgeted or committed contracts, once contracts are imported into Contract Management and approved in Contract Management, they can only be modified via change orders.

21

IMPORTING AND EXPORTING REQUISITIONS AND CHANGE ORDERS

IMPORTING REQUISITIONS

Payment requisitions are formal requests for payment and are usually issued by general contractors (GCs) to the owner on a monthly basis as portions of work on a project are completed.

Constraints:

Requisitions that you import into Contract Management must contain an ApplicationNumber element.

Optional Elements

Requisitions that you import into Contract Management should contain the following elements:

PeriodToDate CheckNumber PaymentDate CustomFields

Usage Guidelines

Once the requisition has been paid, you can import it back into Contract Management. See the Recording Progress section of the Contract Management User’s Guide for additional information. To import requisition data into the Contract Management Module, first use EnterpriseOne to create an XML file that can be validated against the cmexchange.xsd schema file, and then follow the instructions in Importing data into Contract Management (see "Importing data into the Contract Management Module" on page 15).

EXPORTING PAYMENT REQUISITIONS

Requisitions in Contract Management are sent to EnterpriseOne to initiate the creation of payment vouchers.

Constraints The payment requisition must contain the appropriate custom fields before it can be

exported. When you generate the payment requisition in Contract Management, we recommend clearing the Copy Custom Fields from the original checkbox to ensure that the payment requisition that is generated does not contain the custom fields values from the prior requisition.

The requisition must be certified before it can be exported.

To Export Payment Requisitions 1) Follow the procedure in Connecting to the Contract Management Application Server (on page

13).

22


2) Select the Contract Management database you want to export data out of and then click Next.

3) Under Select the action to perform, select Export Payment Requisitions and click Next.

23


4) Select the project that contains the payment requisition and click Next.

5) Specify the export folder location and click Next. Either browse to a folder on a mapped drive or

specify the address of an FTP site. Specify a folder for the log files and then click Next.

6) Click Finish.

The system exports the selected data and produces a log file for review.

24


Usage Guidelines

Once a the requisition is certified you can export the requisition to EnterpriseOne to be paid. See the Preparing Requisitions for Payment chapter of the Contract Management User’s Guide.

Note: If you export a requisition and need to export the change order again, you will need to blank out the Date Exported field in Contract Management. To blank out the Date Exported field, access the requisition in Contract Management and navigate to the Custom Fields tab for the requisition. If required, click the Edit Document button to enter Edit mode. Then blank out the Date Exported field.

25


IMPORTING CHANGE ORDERS

Change orders specify a redirection of plans or introduce new items to the schedule. Change Orders result from changes in the scope of work, site conditions, or schedule delays. Change orders also show any approved increases or decreases in costs. A change request in EnterpriseOne is the equivalent of a change order in Contract Management.

Constraints:

Constraints: Once a change order is created in Contract Management, its number cannot be altered. Additionally, change orders that you import into Contract Management must contain the following elements:

ToCompanyCode FromCompanyCode ChangeNumber

Optional Elements

Change orders that you import into Contract Management may optionally contain the following elements:

ToCompanyName ToContactCode ToContactName FromCompanyName FromContactCode FromContactName ChangeDate Title ChangeOrderLineItem

Usage Guidelines

An example is a scenario whereby a change order was created in EnterpriseOne that affects data that is already in Contract Management. In this scenario you can synchronize the data in Contract Management with EnterpriseOne by exporting the change order out of EnterpriseOne and importing it into Contract Management Exchange. To import change order data into the Contract Management Module, first use the EnterpriseOne application to create an XML file that can be validated against the cmexchange.xsd schema file, and then follow the instructions in Importing data into Contract Management (see "Importing data into the Contract Management Module" on page 15).

26


EXPORTING CHANGE ORDERS

Change orders specify a redirection of plans or introduce new items to the schedule. Change orders result from changes in the scope of work, site conditions, or schedule delays. Change orders also show any approved increases or decreases in costs.

Constraints

The change order must be approved before it can be exported.

To Export Change Orders 1) Follow the procedure in Connecting to the Contract Management Application Server (on page

13). 2) Select the Contract Management database you want to export data out of and then click Next.

3) Under Select the action to perform, select Export Change Orders and click Next.

27


4) Select the project that contains the change order and click Next.

5) Specify the export folder location and click Next. Either browse to a folder on a mapped drive or

specify the address of an FTP site. Specify a folder for the log files and then click Next.

6) Click Finish.

The system exports the selected data and produces a log file for review.

28


Usage Guidelines

An example is a scenario whereby you need to make an increase to a committed contract. In this example, you would use the change management features in Contract Management to modify the committed contract and then export the change order so that you could send it to EnterpriseOne for further processing. For additional information, see the Using Change Management chapter or the Entering Change Orders and Proposals without Using Change Management chapter in the Contract Management User’s Guide.

Note: If you export a change order and need to export the change order again, you will need to blank out the Date Exported field in Contract Management. To blank out the Date Exported field, access the change order in Contract Management and navigate to the Custom Fields tab for the change order. If required, click the Edit Document button to enter Edit mode. Then blank out the Date Exported field.

29

IN THIS CHAPTER

Interpreting Log Messages ................................................................................. 30

Chapter 5 TROUBLESHOOTING

30


INTERPRETING LOG MESSAGES

The log contains status and error message that are generated from the following sources:

From the Contract Management: Refer to the Contract Management User’s Guide, for additional information.

Validation error messages. From Contract Management Exchange: Refer to the table below for additional information.

MESSAGE SIMILAR TO THE FOLLOWING INDICATIONS AND ACTIONS

A Change already exists for the information provided.

Indication: You are importing a change order that already exists. User Action: Determine whether you should be importing this change order and if so, delete the existing change document in CM and re-import.

A ChangeOrder Line Item already exists for the information provided.

Indication: You are importing change order line item that already exists. User Action: Check the XML data for a duplicate line item number.

A Requisition was not found for the information provided.

User Action: Ensure that you are importing the correct requisition data into Contract Management.

A Value must be supplied for <element> Indication: You are importing an element that exists in the XML but it does not have any content. User Action: Ensure that the element contains a valid content.

Company row not found using CompanyObjectId or CompanyAbbreviation.

Indication: When adding a contact, Contract Management Exchange could not find the associated company in Contract Management.

< ProjectName> was not found. Indication: You are attempting to update a project that does not exist or to which you do not have rights.

ProjectSetting <ProjectName> was not found. Indication: You are attempting to update a project setting that does not exist or to which you do not have rights.

The CostCode <costCode> does not exist. Indication: You are attempting to

31

Chapter 5 Troubleshooting


import a cost detail to a cost code that does not exist in CM. User Action: Ensure that the cost code you are using exists in Contract Management.

The element ProjectName must exist and have a value.

Indication: The ProjectName element does not have any content. User Action: Ensure that the element contains a valid Contract Management project name.

The From Company <companyCode> does not exist.

Indication: When importing a change order, the from company must already exist in Contract Management. User Action: Ensure the from company has the correct companyCode.

The To Company <companyCode> does not exist.

Indication: When importing a change order, the to company must already exist in Contract Management. User Action: Ensure the to company has the correct companyCode.

There are no approved Changes to export. Indication: One or more of the following conditions have not been met: 1. The change order must be approved. 2. The date imported must be blank. 3. The date exported must be blank. User Actions: 1. Approve any change orders that you are exporting. 2. Review the change orders that you are expecting to export. 3. Ensure that you have selected the correct project. 4. Determine whether you want to export the change again. If so, blank out the date exported.

There are no certified Requisitions to export. Indication: At least one of the following conditions have not been met:

32



1. The requisition must be certified. 2. The date exported must be blank. User Actions: 1. Certify any requisitions that you are exporting. 2. Ensure that you have selected the correct project. 3. Ensure whether you want to export the requisition again. If so, blank out the date exported.

Values must be supplied for <element(s)> Indication: You are importing an element that exists in the XML but the element does not have any content. User Action: Ensure element contains valid elements.

You do not have the proper rights to the projectName project.

Indication: At least one of the following conditions have not been met: 1. You do not have rights to the project. 2. The project does not exist in Contract Management. User Actions: 1. Contact the Contract Management Administrator to obtain rights to the project. 2. Check the spelling of the project name and ensure that the project has been created in Contract Management.

Documents

Contract Management Exchange User’s Guide - … Management Exchange User’s Guide ... and we disclaim liability for any damages caused by such use of the ... Contract Management