Importing Partner Source Files

This chapter provides an overview of the catalog source layouts and discusses how to:

• Define catalog source layouts.

• Define master catalog source layouts.

• Import source data.

Defining Catalog Source Layouts

To define the sources for catalog data use the Define Data Source (EOCM_REG_DATA_SRC) component.

This section provides an overview of data source types and discusses how to:

• Define the file format.

• Specify the file fields.

You can use sample files to assist you when defining the layout.

This step need only be performed once as long as the format of the partner's source files do not change. This step can be performed by either the partner or an enterprise catalog manager.

Note. Functionality to define shared master catalog sources and allow partners to define their own data sources exists.

Understanding Data Source Types

Catalog Management supports:

• Flat files

• xCBL

• CIF (Catalog Interchange Format) – Industry standard CSV file format from Ariba.

• CUP (Catalog Update Process) – Microsoft Access Database file from CommerceOne.

Catalog Interchange Format (CIF)

The field names on the Source Fields page of the catalog source will be defined based on the field names defined in the header section of the CIF file. If the field names have not been defined, Catalog Management will use the fields listed below:

Important! An error message will display when you attempt to upload a CIF file that does not have a .cif extension, CIF_I_V3.0 as the first row in the data file, or contains less than 12 columns of data.

Catalog Update Process (CUP)

The CUP format is only supported if eProcurement is installed. eProcurement users will be required to use the ePro visual basic executable to export the CommerceOne Microsoft Access Database file to a flat file. The fields exported are predefined and positioned in the same order as the list below.

Note. You must export the Microsoft Access Database Products file, which contains both product and price information.

The field names are automatically created on the Source Fields page of the catalog source, and are disabled to prevent users from making changes.

Pages Used to Define Catalog Source Layout

Defining the File Format

Access the Maintain Catalog Sources - Source Definition page (Catalog Management, Catalogs, Maintain Catalog Sources, Source Definition).

Partner ID and Catalog Source	These two values combined form a unique ID for the catalog source file.
Delimiter Type	Select the delimiter type used to separate each field value in this file. Choose from Comma, Semi Colon, Space, Tab, Fixed Length, Other. If Other is selected, a new field appears for you to enter the delimiter value, such as: % or $. If Fixed Length is selected, the Upload Sample File button is hidden, and the user must manually define the fields on the Maintain Catalog Sources - Source Fields page. Note. You can select a value for flat files only. The field is disabled with the value Comma preselected for CIF and CUP files. The field is not visible for xCBL files.
First Line	Specify if the first line of the file contains headings or data. If you select Headings, the values located in the first line of the uploaded sample file become the field names. If you select Data, the field names need to be added manually on the Maintain Catalog Sources - Source Fields page. Note. You can select a value for flat files only. The field is disabled with the value Headings preselected for CIF files and Data preselected for CUP files. The field is not visible for xCBL files.
Subsequent Lines	Specify if subsequent lines of the file contain data or nothing. Data is used for determining the field type and length from the sample file. Note. You can select a value for flat files only. The field is disabled with the value Data preselected for CIF and CUP files. The field is not visible for xCBL files.
Source Data Object	Enter a unique name, up to 30 characters. For example, use the partner ID and catalog source, such as 1001_OFFICESUPPLIES. This field creates a source data object for Data Transformer and is used as a source for the catalog map definition.
Flat File, xCBL, CIF, or CUP	Select the file type.
By	Displays the user ID of the person who created or updated this catalog source.
Created Date Time and Last Update DateTime	Displays the date and time that this catalog source was created and updated.
Upload Sample File	Click to upload a sample file. A page appears to enter the navigation path to the location of the sample file. Click Upload. The system reads the file and determines the format of the fields. When complete, the Maintain Catalog Sources - Source Fields page is displayed with the source field definitions. Alternatively, navigate to the Maintain Catalog Sources - Source Fields page and add rows to reflect the structure of the file.

Specifying File Fields

Access the Maintain Catalog Sources - Source Fields page (Catalog Management, Catalogs, Maintain Catalog Sources, Source Definition, Source Fields).

Note. Source field information is automatically completed when the sample source file is uploaded. However, the information can be changed or entered manually.

Attachments and Images

To utilize all the benefits of the attachments and images feature, you will need to define a catalog source layout with the addition of four new fields that must be mapped to these enterprise catalog fields:

• File Name.

• File Extension. (Image extensions can be BMP, RLE, GIF, JPEG, JPG, TIF, or PCX).

• File Path.

• URL. (Required if you are creating a link to the partner's website).

The following figure shows the fields in the partner source data file that contains the name of the attachment files, their extension names, and the path to their location.

To avoid duplicate entries, the system assigns the Vendor Item ID and UOM fields as pseudo key fields. To allow for the association of multiple attachments to a single offering, the system also assigns the field File Name as a pseudo key field.

When the catalog source layout is defined, import the partner source data file. No changes have been made to the import process. Once imported, the data is available to be transformed and loaded into the enterprise catalog.

Defining Master Catalog Source Layouts

This section provides an overview of master data source and map concepts, and discusses how to define master catalog sources.

Understanding Master Catalog Source and Map Concepts

Using one master catalog source layout and one related master catalog map for multiple partners allows customers to standardize the format that partners must use to transmit catalog offerings. In turn, a standardized format prevents customers from having to create and maintain several sources and map definitions, which can be very time-consuming and costly.

A master catalog source and related master map will provide the ability to:

• Share a master catalog source definition among multiple partners across catalogs.

• Share a master source data object with multiple partners.

• Share a master map definition.

• Use a unique catalog source and master map, for one or multiple partners.

Note. Functionality to allow partners to define their own catalog sources and map definitions also exists.

Pages Used to Define Master Catalog Sources

Defining Master Catalog Sources

Access the Source Partners page (Catalog Management, Catalogs, Maintain Catalog Sources, Define Master Catalog Source, Source Partners) for defining partners.

The source definition page used to define a master catalog source, is similar to the source definition page used to define a catalog source for a single partner. The only difference is the way partners are associated to the source format. When defining a catalog source for a single partner the key fields are setID, partner ID, and Catalog Source. Values for these fields are entered on the Search page. When defining a master catalog source the key fields are setID and Catalog Source. Partners who will share this source format are identified on the Source Partners page.

To identify partners:

1. Go to the Source Partners page.

2. Add the partners that will share this source layout.

   Click the Insert All Partners button to automatically add all partners registered in Catalog Management. Click Delete All Partners to remove all partners from the list.

3. Click Save to capture changes.

Importing Source Data

This section provides an overview of the source data import process and discusses how to:

• Import partner source data into Catalog Management.

• Import partner source data using a master catalog source.

• View and correct import errors.

Note. This activity can be performed by the partner if the partner has been granted privileges.

See Also

Assigning Partners and Granting Privileges

Understanding the Source Data Import Process

When a partner changes a source file, such as adding new offerings, deleting offerings, or updating prices, the catalog management business process flow cycle begins, starting with the process of importing the updated source file into a temporary table in Catalog Management. Once imported, the data is available to be transformed and loaded into the enterprise catalog.

Managing Errors

The system allows the import process to run to completion even if errors are encountered. The system captures the error information and presents the user with this set of options:

• Delete the error rows for a specified file.

• Delete all the imported data for a specific file.

• Export error rows to an external .txt file, correct the errors in this file, and then re-import the file by appending it to the previously imported data.

Pages Used to Import Source Data

Importing Partner Source Data Into PeopleSoft Catalog Management

Access the Import Catalog Sources page (Catalog Management, Catalogs, Import Catalog Sources).

This page shows the import history for the selected partner ID and catalog source. From this page you can view or delete previously imported data files, or add a new file to be imported.

Note. The import process leverages PeopleTools file attachments, which can be configured to use either the FTP or HTTP transfer protocol. File attachments are supported by using PeopleCode built-ins that implement the transfer of a file to or from a browser using the application server.

Import Status Details

Access the Import Status Details page (click the Status link on the Import Catalog Sources page).

Use the Import Status Details page to view more detailed import process information for the selected file.

See Also

Defining Catalog Source Layouts

Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Developer's Guide.

Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler.

Importing Partner Source Data Using a Master Catalog Source

The process of a master catalog source definition is similar to the process you use for importing partner-offering data using a catalog source definition for a single partner. The only difference is when you select the catalog source you want to import. In the master catalog source situation, the same catalog source may be listed multiple times in the search results.

To select a master catalog source to import:

1. Access the Import Catalog Sources page.

2. Click the Import Master Catalog Source link.

   The Import Master Catalog Source search page appears.

3. Select the desired master catalog source file by setID, partner ID, and catalog source.

   If multiple partners have been identified to share a specific master catalog source, that source file will be listed multiple times in the search results.

Viewing and Correcting Import Errors

Access the Data Source Import Error Details page (click the View Errors button on the Import Catalog Sources page).

See Also

Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Language Reference.

Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Developer's Guide.