Using the Excel to Component Interface Utility

This chapter provides an overview and discusses how to:

• Set up connection information.

• Create a template.

• Manage templates.

• Stage and submit data.

• Resubmit corrected data.

• Construct the SOAP/XML request.

• Send the SOAP/XML request and receive the SOAP/XML response.

Understanding the Excel to Component Interface Utility

Use the Excel to Component Interface utility and component interfaces to upload data from Microsoft Excel into your PeopleSoft database . Each source workbook contains both worksheets and Excel Visual Basic code modules that execute business logic for each transaction.

Use the Microsoft Excel workbooks as a template to create worksheets that are specific to the business logic that you need to use when you are uploading data to your PeopleSoft system. You can copy the data input sheet to other workbooks for distribution without copying the code modules.

The code formats spreadsheet data into a PeopleSoft readable Document Object Model (DOM) structure, and submits it to the PeopleSoft database. Next a PeopleCode program parses the DOM structure and uses the component interface to create entries in the PeopleSoft database, validating the data submitted against the business logic built into the PeopleSoft component. Because the component interface is a wrapper around the component, all logic applied during data entry is applied when loading data through this tool.

The component interface executes all the necessary PeopleCode events and the field-level edits. Based upon results from saving the component interface, another DOM is created in the PeopleCode that returns success, warnings, and/or errors to the Microsoft Excel document. Records in error can be corrected and resubmitted.

Microsoft Excel Column and Row Restrictions

A Microsoft Excel spreadsheet has a physical limitation of 252 columns and 65,000 rows. When you are creating a template and submitting data, you will need to keep these restrictions in mind.

When a template has more than 252 properties, you can work around this limitation by deselecting an appropriate number of columns to meet the restriction before submitting to the database. You can determine in advance which fields should be selected as input cells, which cells should be included for submission, and which cells need not be included at all.

To work around Microsoft Excel’s row limitations, you may need to stage your data in batches so that the number of rows on the Staging and Submission sheet will not exceed 65,000.

Note. You will find the optimal performance when using this utility with small to medium-complexity component interfaces. For large component interfaces, other methods of uploading may be more appropriate, including File Layout and Application Engine.

In addition, because of Microsoft Excel's high memory requirements, performance with more complex component interfaces will be inhibited. The number of cells containing values on any one sheet should be less than 1,000,000. Failure to ensure this can potentially result in serious performance issues with Microsoft Excel, including crashes.

Software Requirements

This utility is available only for Microsoft Office 2000 and specifically needs the Microsoft XML parser, msxml4.dll. Some applications have been known to overwrite previous versions of this file with another version, occasionally causing the utility not to function properly. You should use MSXML version 4, Service Pack 2, because it can coexist with older versions of the parser. You can download and reinstall MSXML from the Microsoft web site.

The Excel to Component Interface utility requires the Visual Basic 6.0 SP5: Run-Time Redistribution Pack and MSXML (Microsoft XML Parser) 4.0 Service Pack 2.

See the Microsoft downloads website for more information on these service packs.

Building a Component Interface for the Excel to Component Interface Utility

To use the Excel to Component Interface utility effectively, you must have a complete understanding of the component you are using and the component interface that is built around it. In addition, you should know what data needs to be entered and which fields on the component need to be exposed as component interface properties. Fields that are not relevant for data input should not be exposed on the component interface. This reduces processing time when loading data, as well as saving time when building the template because there will be no need to delete unnecessary properties on the template.

Some component interface structures will need to be modified before they can be used to load data through the utility. Components that have logic to insert multiple rows in child collections, and then require more values to be set on those collections, will need modification to the component to work with the Excel to Component Interface utility. Change the component so that the logic to insert and partially populate these rows does not happen by default through the component interface.

%CompIntfc and %CompIntfcName can be used so that this logic does not fire either from any component interface or from the component interface that you created for use with the Excel to Component Interface utility.

Additionally, components that have no keys at level 0, but rely on logic at level 0 to load the level 1 collection, cannot be loaded by using the Excel to Component Interface utility.

Component interfaces that rely on CommitWork to save the data cannot be used in the Excel to Component Interface utility.

Prompt and translate table values are validated when data is saved and submitted to the database through the Excel to Component Interface utility. This is different from the behavior on the page when prompts and translates are validated interactively. Some components may use prompts that are dynamically populated. For those situations, you must know what the valid values for the prompt will be.

Note. Remember that any changes made to the structure of a component interface will also need to be reflected in the template. Always ensure that the component interface and the template in the Excel to Component Interface utility are in sync. Structural changes made in only the component interface will cause an error in the Excel to Component Interface utility when data is submitted to the database.

Testing the Component Interface

Before using the Excel to Component Interface utility, you should run the component interface through the component interface tester in three-tier mode. Testing the component interface using the tester enables you to troubleshoot any problems before running the component interface through the utility. If the component interface does not work in the tester, it will not work in the Excel to Component Interface utility either. The component interface tester is located on the Tools menu in Application Designer.

See Testing the Component Interface.

Performance Expectations

The performance of a component interface depends entirely upon the underlying component. If the component has a complex user interface with many pages and scrolls, the component interface generally will have a slower processing time. The best performance times are found with small and medium-complexity component interfaces.

PeopleCode Behavior and Limitations

Certain PeopleCode functions and events that are specific to the user interface do not execute through the component interface. You will need to modify PeopleCode for the component, pages, and records when you build the component interface for the component.

PeopleCode events and functions that relate exclusively to the page interface and online processing cannot be used by component interfaces. These include:

• Search dialog processing.

• Menu PeopleCode and pop-up menus.

• Transfers between components, including modal transfers.

• Dynamic tree controls.

• ActiveX controls.

• DoSave and DoSaveNow.

• Functions that are ignored in a component interface call.

See Understanding PeopleCode Behavior and Limitations, Understanding Component Interface Class.

Automatic Defaulting of Properties

When you create a new component interface in Application Designer, the system can create default properties for all the fields exposed on the component interface that meet certain criteria.

When creating a new component interface, the following requirements must be met to qualify as a default property.

The fields should be of the following types:

• Character

• Long character

• Number

• Signed number

• Date

• Time

• Datetime

The field should be one of the following page control types and must be exposed on the page:

• Edit box

• Drop-down list box

• Check box

• Radio button

See Creating a New Component Interface.

Getting Started with the Excel to Component Interface Utility

To launch the Excel to Component Interface utility, locate the ExcelToCI.xls executable file in the PS_HOME\excel folder.

In addition, perform the following tasks:

• Grant access to the iScript WEBLIB_SOAPTOCI.

• Enable macros in Microsoft Excel.

Granting Access to WEBLIB_SOAPTOCI

To use the Excel to Component Interface utility, you must grant access to the iScript WEBLIB_SOAPTOCI in the permission list of the user who is building the template.

See Setting Up Permission Lists.

Enabling Macros in Excel

The Excel to Component Interface utility relies on macros; therefore, you must enable macros in Microsoft Excel for the utility to work. When a Microsoft Excel spreadsheet is opened, the system displays a dialog box asking you to select whether or not macros should be enabled on the spreadsheet. Always select Enable Macros so that the macros delivered with the Excel to Component Interface utility can function.

To ensure that the macros are available to run, you will need to set the security level in Microsoft Excel to allow macros to open.

To enable macros in Excel:

1. Open the Excel to Component Interface utility.

2. From the Excel menu, select Tools, Macros, Security.

3. Select either Medium or Low to enable the macros.

4. Select OK.

Viewing the Coversheet

The coversheet of the Excel to Component Interface utility workbook gives a brief overview of the process flow and functionality of the tool.

Access the Coversheet tab in ExcelToCI.xls:

Setting Up Connection Information

This section covers:

• Entering connection information.

• Connecting to the database.

Entering Connection Information

Access the Connect Information tab in ExcelToCI.xls:

The information on this page is required to create a new template or to submit data to the database. You will need to specify environment information as well as information about how data should be transmitted. The Action field will be filled in automatically based on your setup and the component interface that the template is associated with.

The initial connection settings will be the PeopleSoft default values. You will need to modify these values for your specific implementation of PeopleSoft. If you are unsure what to enter for these values, check with your system administrator.

The connection options are:

See Understanding PeopleSoft Pure Internet Architecture, Understanding PeopleSoft Security.

Multilingual Support

You can use the Excel to Component Interface utility to upload data from any installed language. For each delivered language, PeopleSoft delivers a translated version of the Excel to Component Interface worksheet . When you change the language code on the Connect Information, the field labels on the template and any error messages on the Staging and Submission sheet appear in the language that you specified. When data is submitted, the standard PeopleSoft related language architecture processing occurs. You will find the translated worksheets in the appropriate language directory found in the PS_HOME/EXCEL directory.

If you are using a language in which a different character set or numeric formatting is used, you need to set the locale of your client machine to match that language. To do so, open Control Panel, Regional settings, and select the correct language and input locale.

Error Thresholds and Chunking

A running error count is kept for each chunk of data that is being submitted to the database. When the total error count exceeds the error threshold that you specified on the Connection Information tab, submission to the database stops and the system displays an error message. Rows that errored out will have a status of Error on the data input page and should be corrected. The data submitted to the database before the error threshold was reached will remain in the target database. Rows not yet submitted will be submitted when the data is restaged and submitted.

Connecting to the Database to Create a Template and Submit Data

Your PeopleSoft login information is needed for both creating the template and submitting data to the database.

Access the Login dialog box by selecting the Template tab and then selecting the New Template button, or by selecting the Submit Data button on the Staging and Submission tab:

The system uses your user ID and password to ensure that you have the correct permissions to access the component interface that you are creating the template on. You must be granted permission to access the component interface that you are using.

See Viewing Log Files.

Creating a Template

The template page is a graphical representation of the component interface structure that you will be using to load data. The structure of the component interface is retrieved from the database when a new template is built. All of the fields that are exposed through the component interface appear on the template page. Fields that are read-only on the component interface will not appear on the template.

The new template macro builds the parent-child relationship within Microsoft Excel based upon the component interface scroll level definition. The system adds a new row for each scroll level and assigns a unique identifier to it.

Access the Template tab in ExcelToCI.xls to create your template:

Collection	The name of the component interface collection. A collection is a property that points to a scroll, rather than a field, in the underlying component for a component interface.
Property	The component interface property name. Typically, this is also the name of the field on the page.
Record Type	This number represents the parent/child relationship of the records. The level 0 scroll record is always represented by 000. Level 1 scroll records appear with numbers that start with 100 and always have 00 as the last two numbers. Level 2 scrolls are identified by numbers that start with the identifier of their level 1 parent and end with a 0. Level 3 scrolls are identified by the first number from the level 1 parent, the second number from its level 2 parent, and then the third number from its own position in the list. The numbers for each scroll level are incremented based on the number of records that exist at that level. For example, level 0 would be 000, level 1 would be 100, and level 2 would be 110, and so on. Note. Component interfaces that have more than 10 collections at a given level will be incremented with alphabetic identifiers. For example, 800, 900, A00, and so on.
Field Type	The standard PeopleSoft type for the field. For example, Date, Character, and so on.
Field Length	The length of the field as defined by PeopleSoft. For numeric fields and signed number fields, the length is broken down into integer and decimal positions. For example, a length of 15.3 indicates 15 integer positions and three decimal positions.
Key/Required	If the field is a key field, the system will display a Y to the left of the forward slash. When the field is not a key, it will be blank. If the field is a required field, the system will display an R to the right of the forward slash. When the field is not required, it will be blank. This information comes from the record definition itself. Note. Fields that are either keys or required must be set in order to submit data successfully.
Sequence	The sequence number represents the property order in the template.
Status	This field displays the load status on the Staging and Submission page.
Line No (number)	This corresponds to the line number on the Input Data and the Staging and Submission pages.

Understanding the Template Actions Toolbar

The template actions toolbar is made up of buttons that you use to create and modify a template, as well as create a data input sheet. You can resize the toolbar and move it to any location on the page or even drag it onto the existing standard Microsoft Excel toolbar. Once you have moved the toolbar to a location, it will remain there until you move it again. You do not need to move the toolbar each time you open the workbook.

Each button on the toolbar has help text that describes the purpose and use of each of the buttons when you place the cursor over the button. .

Note. When you create a new template or a new data input sheet, the system clears the existing worksheet of all existing information. If you have a template or data input sheet that you need to save from previous uploads, save a copy of the worksheet before you create a new template or data input sheet.

Entering Data into the Template

When determining which properties to include as input cells and which properties to include for submission, remember that the component interface uses the same business logic and executes the same PeopleCode as if the record were entered online using the page in your PeopleSoft application. To provide the minimal data necessary, these fields must either be provided with default (hard-coded) values or values that you provide using the data input sheet.

Note. You should unit test the template that you created with a few sample entries, and then verify your results before using the interface for mass input. For example, if you forgot to select a property, you will need to build a new data input sheet. If the results of the submission are satisfactory, continue entering data.

Adding a New Child Record

By default, each collection is represented once on the template. To insert copies of a given collection, select that collection and click the Insert New Child button to create a copy of the selected row. The collection that you selected is copied so that you can have two rows under the same parent.

Note. On the data input sheet (when the hierarchy is flattened) you will see duplicate columns where multiple children exist.

Adding Default Values

Some fields have default values associated with them, either in the record definition or at runtime when the record is created on the database. Additionally, many components trigger PeopleCode, which populates default values, as well. To accept the database default, include the property for submission and the system default will be used.

There may be some fields for which you want to create your own default. For example, if you want to set the value of a field named Status as of Effective Date to A for every row that you submit, enter that value for the field in the template. Then, include the cell for submission on the template. The field will not appear on the data input page, but the value will appear in the field on the Submit to Database page. This is useful for effective dates, status fields, set IDs for simple imports, and so on.

When providing values for translate fields or prompt tables, provide the field value rather than the short or long description for the translate value. If you are unsure of the field values, check in the record or field definition in Application Designer.

Template Wrapping

If you are creating a template that has more than 252 properties, the Excel to Component Interface utility will wrap the additional columns and display them at the bottom of the spreadsheet so that they are still visible and can still be selected and deselected for submission.

Note. Because of Microsoft Excel column limitations, no more than 252 columns may be submitted to the database at one time. When a template has more than 252 properties, you can work around this limitation in Microsoft Excel by deselecting an appropriate number of columns to meet the restriction before submitting to the database. You can determine in advance which fields should be selected as input cells, which cells should be included for submission, and which cells need not be included at all.

Entering Data on the Data Input Sheet

The data input sheet enables you to enter data into the Excel to Component Interface utility so that it can be loaded to the database by using the component interface that you've selected. You can enter data manually or you can cut and paste it from another spreadsheet or third-party application.

Using the Data Input Sheet

Access the data input tab to enter data:

The field labels that appear on the data input sheet are those properties that you selected as input cells on the template. Each scroll level is identified by color. The record type from the template is also displayed for each property.

The system creates default date, datetime, and number formats when it creates the template. You can modify this format by using Microsoft Excel's default cell formatting when entering data, with the exception of the d/m/yy format for dates and datetimes. Instead, always use a d/m/yyyy format for dates and datetimes. To access the formatting feature select Format, Cells from the Excel menu.

The data input sheet is also used to correct data that failed to submit to the database. Errors that are flagged on the Submit to Database page are posted to the data input page, and when you have corrected them, the items marked in error can be staged again to the Staging and Submission sheet.

Data Input Actions

The data input Actions toolbar contains the Stage Data for Submission button, which takes the data that you entered on the data input sheet and stages it for submission to the database. Once the data is staged, it appears on the Staging and Submission sheet in the hierarchical template structure. At this point, you should check that all fields are populated as expected. When the data is staged, it displays both the data on the data input sheet and the data that you specified as default values.

Viewing the Staged Data

Access the Staging and Submission tab:

Note. Microsoft Excel has a physical limitation of 252 columns and 65K rows. Depending on the complexity of the record structure and the number of scroll-level records that are included in the template, you can use multiple rows on the Staging and Submission sheet to reflect one row of data from the data input sheet. To work around Microsoft Excel’s limitations, you may need to stage your data in batches so that the number of rows on the Staging and Submission sheet will not exceed 65K.

Staging and Submission Actions Toolbar

Error When Submitting Existing Keys

If you receive the error Row already exists with the specified keys and you are in CREATE mode, this indicates that the key already exists at level 0 or is part of the search record.

To verify that the key exists:

1. Open the component interface in Application Designer.

2. Launch the component interface tester by selecting Tools, Test Component Interface.

   The Component Interface Tester search dialog box appears. This dialog box displays the keys (in the left-hand columns) for getting, creating, or finding an instance of the component interface.

3. Enter the value for the key you are testing.

4. Click Get Existing for the key that you are about to add, using the Excel to Component Interface utility.

   If the Get Keys command returns the key, the key already exists and you must add data by using UPDATE mode.

   If you receive a message that no row exists for the key, then the key does not exist at level 0 and the data should be added by using CREATE mode.

See Testing the Component Interface.

Correcting and Resubmitting Data

After you submit the data to the database, results of the process appear on the Staging and Submission sheet. If a submission had an error, the errored status appears on the Staging and Submission sheet. Use the data input page to correct the data and then resubmit it to the database. Continue this process of correcting errors and resubmitting until there are no errored records on the data input page.

Note. Data that was not submitted because the error threshold was reached will have no status. When the data that created the error is corrected on the data input sheet, the data that was not submitted will be staged to the database.

Submission Statuses

Errors received for that record appear in a comment field by moving the cursor over the error flag. The records marked OK in green cannot be restaged for submission and can be kept as a record of work completed.

There are three statuses that can appear when you have submitted you data to the database.

Creating a SOAP/XML Request

You can construct a SOAP/XML (Simple Object Access Protocol/Extensible Markup Language) request to create, update, or get component interface rows. The request and response contain component interface data in a SOAP/XML format.

Request Format

The following example shows the request format:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <Action__CompIntfc__CIName>
      Tags and Data
    </Action__CompIntfc__CIName>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Valid actions are Create, Get, Update, and Updatedata.

CIname is the name of the component interface.

Tags and Data contains the tags and data for the component interface row or rows.

Sample Create Request

The followings is a sample Create request:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Body>
  <CREATE__CompIntfc__SUPPORT_DOC_TBL>
    <SUPPORT_DOC_ID>POLICE</SUPPORT_DOC_ID>
    <SUPPORT_DOC>
      <DESCR>Police Report</DESCR>
      <DESCRSHORT>Police</DESCRSHORT>
    </SUPPORT_DOC>
  </CREATE__CompIntfc__SUPPORT_DOC_TBL>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Sample Get Request

The following is a sample Get request:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Body>
  <Get__CompIntfc__SDK_BUS_EXP>
    <SDK_EMPLID>8052</SDK_EMPLID>
  </Get__CompIntfc__SDK_BUS_EXP>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Sample Update Request

The following is a sample Update request:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Body>
  <UPDATE__CompIntfc__SDK_BUS_EXP>
    <SDK_EMPLID>8001</SDK_EMPLID>
    <SDK_BUS_EXP_PER>
      <SDK_EXP_PER_DT>08/14/2002</SDK_EXP_PER_DT>
        <SDK_BUS_EXP_DTL>
          <SDK_CHARGE_DT>08/14/2002</SDK_CHARGE_DT>
          <SDK_EXPENSE_CD>01</SDK_EXPENSE_CD>
          <SDK_EXPENSE_AMT>1234.56</SDK_EXPENSE_AMT>
          <SDK_CURRENCY_CD>USD</SDK_CURRENCY_CD>
          <SDK_BUS_PURPOSE>Client Visit</SDK_BUS_PURPOSE>
          <SDK_DEPTID>10100</SDK_DEPTID>
        </SDK_BUS_EXP_DTL>
    </SDK_BUS_EXP_PER>
  </UPDATE__CompIntfc__SDK_BUS_EXP>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Sample Updatedata Request

The following is a sample Updatedata request:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
        <UPDATEDATA__CompIntfc__USER_PROFILE>
            <UserID>VP1</UserID>
            <UserDescription>updated description</UserDescription>
            <EmailAddresses>
                <EmailType>BUS</EmailType>
                <EmailAddress>[email protected]</EmailAddress>
            </EmailAddresses>
        </UPDATEDATA__CompIntfc__USER_PROFILE>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Sending the Request

To send the request, post the XML code to the URL of the PeopleSoft Pure Internet Architecture server with the appropriate path to the iScript on the server.

Note. The PeopleSoft user ID and password must be sent in the SOAP request header with the identifiers of userid and pwd. You should send the request on a secure site.

Use this format:

Protocol(http or https)>://<WebServerMachineName>:<HTTPPort>/psc/ps/<Portal>/<Node>/s/
WEBLIB_SOAPTOCI.SOAPTOCI.FieldFormula.IScript_SOAPToCI?&disconnect=y&postDataBin=y

For example,

http://MyWebServer:80/psc/ps/EMPLOYEE/PT_LOCAL/s/WEBLIB_SOAPTOCI.SOAPTOCI.FieldFormula.IScript_SOAPToCI?disconnect=y&postDataBin=y

Receiving a Response

This section provides examples of response types.

Viewing a Response if a Row Already Exists

This is one example of the error response. The messages vary depending on the type of error.

<?xml version="1.0" encoding="UTF-8" ?> 
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> 
  <SOAP-ENV:Body> 
    <USER_PROFILE> 
      <Error-Warning> 
        <Message> 
          <Type>Error</Type> 
          <MessageSetNumber>91</MessageSetNumber> 
          <MessageNumber>49</MessageNumber> 
          <MessageText>Row already exists with the specified keys.   
             {USER_PROFILE} (91,49)</MessageText> 
          <ExplainText>A rows already exists in the database with the 
            specifiedkeys. 
             </ExplainText> 
        </Message> 
      </Error-Warning> 
      <Key_information> 
        <UserID>PTDMO10</UserID> 
      </Key_information> 
    </USER_PROFILE> 
</SOAP-ENV:Body> 
</SOAP-ENV:Envelope>

Viewing a Sample Get Request and Response

The following XML code gets an SDK_BUS_EXP component interface row for an employee with an employee ID of 8052:

<?xml version="1.0"?>
<SDK_BUS_EXP action="GET">
         <SDK_EMPLID key="Y">8052</SDK_EMPLID>
      </SDK_BUS_EXP>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The XML response for this employee is:

<?xml version="1.0" encoding="UTF-8" ?> 
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
    <SDK_BUS_EXP> 
      <SDK_BUS_EXP_PER> 
        <SDK_EMPLID>8052</SDK_EMPLID> 
        <SDK_EXP_PER_DT>2000-11-09</SDK_EXP_PER_DT> 
        <SDK_BUS_EXP_DTL> 
          <SDK_EMPLID>8052</SDK_EMPLID> 
          <SDK_EXP_PER_DT>2000-11-09</SDK_EXP_PER_DT> 
          <SDK_CHARGE_DT /> 
          <SDK_EXPENSE_CD /> 
          <SDK_EXPENSE_AMT>0</SDK_EXPENSE_AMT> 
          <SDK_CURRENCY_CD>USD</SDK_CURRENCY_CD> 
          <SDK_BUS_PURPOSE /> 
          <SDK_DEPTID /> 
        </SDK_BUS_EXP_DTL> 
      </SDK_BUS_EXP_PER> 
    </SDK_BUS_EXP> 
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Diagnosing and Resolving Errors

This section discusses how to:

• View the log files.

• Resolve error messages.

Viewing Log Files

If you select the check box to create log files when building a template or submitting to the database, two log files are created—one that logs the activity of ExcelToCI.xls and the other that logs the SOAPTOCI Web Library.

The log for ExcelToCI.xls is created in the temp directory on the workstation running the Excel spreadsheet.

The log for the Web Library is created on the application server in the <PS_HOME>\appserv\<DOMAIN>\files directory. This file contains both the SOAP request and the SOAP response.

Log files are written for each chunk of data that is sent to the database.

Resolving Error Messages for Client Environments