Mapping, Transforming, and Loading Partner Source Data

This chapter discusses how to:

• Define catalog maps.

• Transform and load data.

• Remove partner versions.

Note. These activities, except defining master map information, can be performed by the partner if the partner has been granted privileges.

See Also

Assigning Partners and Granting Privileges

Defining Catalog Maps

To define catalog maps, use the Define Catalog Maps (EOCM_MAP_DFN) component.

This section provides an overview of the mapping process and master maps, and discusses how to:

• Define map information.

• Define map field detail.

• Perform map edits.

• Preview map results.

Note. This step need only be performed once as long as the format of the partner's source files or the enterprise target layout do not change.

Understanding the Mapping Process

Catalog mapping translates values from the catalog source data to the format of the enterprise catalog using default target values, transformations, translation sets, and map rules to facilitate the process. Although the majority of the data transformation setup and maintenance process is automated you may need to perform such tasks in Data Transformer before performing the tasks documented here for the Define Catalog Map component:

• Set up target field default values.

• Set up translation sets.

• Create transformations.

• Set up map rules.

Setting Up Target Field Defaults

The AutoMapper feature populates the map field details with the field value based on the target field. If Allow Map Override is not selected, you cannot override the field value at the map level. A default with no value is initialized to a blank, zero, or the appropriate PeopleSoft null value.

When setting the default values, consider the target field data type format. Character fields are used for names, codes, and letter values. Uppercase converts the field value to uppercase and signifies that no other formatting options apply to this field. Mixed case stores uppercase and lowercase characters as entered. Number fields and signed number fields are fixed in field length and allow the entry of positive numbers. Only signed numbers allow the entry of negative numbers. Date fields contain calendar dates. A date field has a field length of 10 and is maintained by the system. The default format of a date field is defined by the database and can be overridden by the browser settings.

Setting Up Translation Sets

You use translation sets to define equivalent values or a code set for data conversion, for example: EA = Each, GAL = Gallon, IN = Inch. The translation to and from values can be applied as a required rule to the map rule definition; the value is used by the AutoMapper feature based on a source input and target field in the map definition. If the value is not a required rule, you can select Translation Set when completing the map field details. Enter translation set values for map definition details, used as equivalent values for data transformation.

Creating Transformations

When data is copied from the source to the target, the data can be transformed using edits, lookups, or PeopleCode. Transformations allow you to change a column's value.

Note. Use the Data Transformer transformation wizard to guide you through the process of creating transformations.

Setting Up Map Rules

You can create rules to be used by the AutoMapper feature in the map field detail definition. You use rules to assign correct default values to target fields when creating maps. Using map rules, you can assign a literal default, transformation, source field, or a translation set to the target field. If the map rule is required, you cannot override the rule on the Define Catalog Map - Map Field Detail page.

Note. To access the Data Transformer Map Rules page, you need to update permissions for the delivered roles or assign additional roles.

See Also

Enterprise PeopleTools 8.50 PeopleBook: Security Administration.

Understanding Master Maps

Unlike defining map information for a single partner, defining master map information is performed at the enterprise catalog level. The pages used to enter the information are the same.

To associate the map to a master catalog source, the lookup you use to select a source data object on the Map Information page, is restricted to only source data objects created for master catalog source definitions. When the source data object is selected, the map is associated to a master catalog source as well as the partners identified to share the selected source.

Pages Used to Define Catalog Maps

Defining Map Information

Access the Define Catalog Map - Map Information page (Catalog Management, Catalog Management Home, Define Catalog Map, Map Information).

Source	Select the source file for this map. The source selected should be the name specified as the source data object when the catalog source layout was defined.
Target	Automatically populated based on the enterprise catalog selected when navigating to this page. The value cannot be overridden. This value controls the target fields available on the Define Catalog Map - Map Field Details page.
Error Handling	Select from: No error handling needed. Data validation is not performed and all rows are inserted into the target table. Identify error row: Currently not available. Correct data error & reprocess: Data validation is performed. Valid rows are inserted into the target table and invalid rows are inserted into a user-defined error table. Note. The user-defined error table must be created by the system administrator in Application Designer before attempting to load the defined map.

See Also

Defining Catalog Source Layouts

Defining Map Field Details

Access the Define Catalog Map - Map Field Detail page (Catalog Management, Catalog Management Home, Define Catalog Map, Map Field Detail).

To define map field details, click the Apply AutoMapper button.

AutoMapper automatically attempts to match the source to target field list. It also applies any required map rules, including target field defaults, translation set values, and transformations. AutoMapper then maps remaining target fields with constant values from the PSRECFIELD.DBFIELDNAME.SQL assembler, and coordinate the transformation steps.

If modifications to the mapping defined by AutoMapper is required, make changes to these options:

Performing Map Edits

Access the Map Edit page (Catalog Management, Catalog Management Home, Define Catalog Map, Map Edit).

Select a new source input value to replace or add to the current source. Click the Detail link to access the Transformation Definition page and edit transformation definition information. Click the Add link to access the Transformation Definition page and add a new transformation.

Previewing Map Results

Access the Preview Map Results page (Catalog Management, Catalog Management Home, Define Catalog Map, Preview Map Results).

Click the Preview button to view a subset of mapped data based on the map definitions.

Note. Map results are only available to preview after the partner source file has been imported.

Transforming and Loading Data

This section provides an overview of the transformation and loading process and discusses how to transform and load offering data.

Understanding the Transformation and Loading Process

After a partner's offering data has been successfully imported into Catalog Management, it can be transformed into the enterprise catalog format and then loaded into the enterprise catalog.

The transformation of data is based on the catalog map that you defined for the partner's source file.

You can use three different methods to load offering data into the enterprise catalog:

• Incremental update.

  The system updates the most recently loaded data. Required changes are made to existing data, such as price changes, and new offering data is added.

• Full load.

  The system replaces the current data with the new data.

• Error recycle only.

  If errors occurred during a previous attempt, this is the only option available. The system uses the data in the corrected error table as the source data.

The following diagram illustrates the transformation and loading process of source data to the target enterprise catalog.

Transformation and loading of source data

Note. The process of transferring and loading data from a shared catalog source to the enterprise catalog format, using a master data map is similar to transferring and loading data for a single partner. The only difference is when you select the catalog map object. The selection is restricted to master catalog maps associated to the selected partner.

See Also

Defining Catalog Maps

Pages Used to Transform and Load Data

Transforming and Loading Offering Data

Access the Load Catalog Map page (Catalog Management, Catalog Management Home, Load Catalog Map).

Set ID and Catalog ID	Values are based on the enterprise catalog selected on the Catalog Management Home page. The name of the enterprise catalog is displayed to the right of the catalog ID.
Partner ID	The value is based on the partner catalog selected on the Enterprise Catalog Console page. The name of the partner source is displayed to the right of the partner ID.
Map Name	Select the catalog map defined for this partner source file.
Target Load Option	Select from: Attachment Only. Error Recycle Only. Full Load. Incremental Update. Price Only Note. The Error Recycle Only option is available only if errors exist.
Run Map	Click to transform and load the offering data.

Note. A new version of the partner offering data is created once the transformation and load process has completed.

Using Attachment Only Target Load Option

An Attachments Only load give users the opportunity to add attachments to offerings that already exist in a staged or production version of the catalog without having to import, load, and categorize the offerings again. Attachments can also be associated to offerings using Maintain Partner Offerings.

If you have a different file format for updating attachments, you will need to create a new source definition and define a second catalog map to use when performing an Attachments Only load. At a minimum, this map definition must contain mapping information for the attachment and key fields. For example:

• Vendor Item ID.

• File Name.

• File Extension.

• File Path.

Note. An Attachments Only load can be performed only when the most recent version has a status of Staged or Production.

If you performed an Attachments Only load, the system will make a copy of the most recent partner version and increment the version by 1. For example, if the most recent version is version 5, the system copies that version to version 6. The system will then update offerings with the new attachments using the key fields to match offerings. The system will ignore offerings that have no match. The new version is automatically staged.

Using Price Only Target Load Option

A Price Only source data load give users the opportunity to update price fields for offerings that already exist in a staged or production version of the catalog without having to import, load, and categorize the offerings again.

If you have a different file format for updating prices, you must create a new source definition and define a second catalog map to use when performing a Price Only load. At a minimum, this map definition must contain mapping information for the prices and the key fields. For example:

• Vendor Item ID.

• Unit of Measure.

• Vendor Price.

Note. A Price Only load can be performed only when the most recent version has a status of staged or production. If the most recent version does not have a status of staged or production, the only available target load options will be Full Load or Incremental Update.

When you perform a Price Only load, the system will make a copy of the most recent partner version and increment the version by 1. For example, if the most recent version is version 5, the system copies that version to version 6. The system will then update offerings with the new prices using the key fields to match offerings. The system will ignore offerings that have no match. The new version is automatically staged.

See Also

Creating Versioning

Removing Partner Versions

This section provides an overview of the removal process and discusses how to remove unused partner versions.

Understanding the Removal Process

Catalog Management allows catalog managers and partners to load and maintain several different versions of a partner's data. Once a version is selected for production, all other versions are stored but not used again. The remove Unused Versions feature provides a way for the catalog manager to remove these unused partner versions.

Important! Remove means deleting all the partner data. Once removed, the partner version cannot be retrieved.

Page Used to Remove Unused Partner Versions

Removing Unused Partner Versions

Access the Remove Versions page (Catalog Management, Catalog Management Home, Remove Unused Versions, Remove Versions).

SetID and Catalog ID	Values are based on the enterprise catalog selected on the Catalog Management Home page
Partner ID	Value is based on the partner catalog selected on the Enterprise Console.
All Versions or Unused Versions	Select All Versions to list all versions of partner data for this partner. Select Unused Versions to list only those versions that are no longer used (Default).
Versions	Displays a list of partner versions based on the previous selection, including these options: Partner Version. Load State. For example, Loaded, Categorized, Staged, Production. Catalog Version. Last Update Date/Time. Last Update User ID.
Select	Select the associated check boxes to select the partner versions you want to remove. The check box will be disabled for: Version that has been moved to production. Currently staged version. Latest version.
Remove Versions	Click to run the application engine EOCM_REM_VER process. The process is submitted. Click the Process Monitor link to monitor the status of the request. Note. Once removed, the partner version cannot be retrieved.