Import Catalog Data

Thecatalog import cockpit facilitates importing data from OCI 5.0 compliant catalogs through HTTP(s) web service or JSON files, importing data from MDM catalog using MDM ABAP API or importing product master data from SRM.

You should have /SRMNXP/CONTENT_MGMT role assigned to import catalog data.

Catalog Data Import – File Upload

This section explains the procedure to importing the catalog data from JSON files.

SRM-MDM Catalog Data Import data into SRM Staging DB

1. Enter transaction /SRMNXP/CAT01

2. Add a catalog web service ID or select an existing catalog webservice id.

3. Select Import Action applicable - File 4. Provide the file path of Import file.

5. SelectImport Image checkbox, if you want to import images.

6. Provide the folder path for the folder containing images in Image Folder.

7. Click on Schedule Job button.

8. Define Job to start immediately or schedule to start at a specified date/time.

9. For Delta import, use “Reschedule Delta” or “Schedule Delta with CTI” indicators. The use of these indicators are explained in the table below:

Importing Type Values of Indicators Remarks Full Load or Initial

Load

Reschedule delta : OFF Schedule with CTI : OFF

Use when you are importing data into a catalog first time. All catalog items are added to tables.

Delta load Reschedule delta : ON Schedule with CTI : OFF

Use when you want to change some data or add additional items in already imported catalog

Delta Load – replace data completely

Reschedule delta : OFF Schedule with CTI : ON

Use when you want to erase the existing data in a catalog completely and replace with new data

Upon successful importing, the catalog data is stored in SRM UI Add-On 1.0 tables for indexing.

1 4

2 3

5

6

Catalog Data Import –Upload from Webservice

This section explains the process of importing the catalog data by connecting to a supplier provided HTTP(s) webservice.

1. Enter transaction /SRMNXP/CAT01

2. Add a catalog web service ID or select an existing catalog webservice id.

3. Select Import Action applicable - HTTP/HTTPS

4. Provide the URL, User name, password and page size. Give a requested page. If the catalog Webservice ID configuration has a user and password details, you need not enter here. If you enter user and password, system will access the URL using the given user id and password in this screen. You can also provide a transaction ID and requested page if you like to resume a stalled transaction from a desired page.

5. Click on Import Image checkbox, if you want to import images. Provide the folder path for the folder containing images in Image Folder. If you use proxy server, then you need to implement the BAdI SRM_CAT_GETPROXYINFO to provide proxy info (This BAdI is also available in SRM core .If you have already implemented this BAdI, then you do not need to implement again).

6. Click on Schedule Job button.

7. Define Job to start immediately or schedule to start a specified date/time.

8. For Delta import, use “Reschedule Delta” indicator. The use of these indicators are explained in the table below:

Importing Type Values of Indicators Remarks Full Load or Initial

Load

Reschedule delta : OFF

Use when you are importing data into a catalog first time. All catalog items are added to tables.

Delta load Reschedule delta : ON Use when you want to change some data or add additional items in already imported catalog

Upon successful importing, the catalog data is stored in SRM UI Add-On 1.0 tables for indexing.

SRM-MDM Catalog Data Import

This section explains importing the catalog data from internal catalogs, managed using SRM-MDM Catalog. The extraction from MDM Catalog is done using native MDM ABAP APIs.

Launch transaction code /SRMNXP/CAT01.

1. Enter the transaction /SRMNXP/CAT01.

2. Add a catalog web service ID or select an existing catalog web service id.

3. Select Import Action applicable - MDM 4. Click on Schedule Job button.

5. Define Job to start immediately or schedule to start a specified date/time.

6. For Delta import, use “Reschedule Delta” or “Schedule Delta with CTI” indicators. The use of these indicators are explained in the table below:

Importing Type Values of Indicators Remarks Full Load or Initial

Load

Reschedule delta : OFF Schedule with CTI : OFF

Use when you are importing data into a catalog first time. All catalog items are added to tables.

Delta load Reschedule delta : ON Schedule with CTI : OFF

Use when you want to change some data or add additional items in already

imported catalog. This picks the records from MDM catalog that have been created, modified or deleted since last successful extraction.

Delta Load – replace data completely

Reschedule delta : OFF Schedule with CTI : ON

DO NOT USE this combination as MDM ABAP API picks the changed records in Delta.

Upon successful importing, the catalog data is stored in SRM UI Add-On 1.0 tables for indexing.

Additional considerations while importing MDM Catalog data:

1. You can choose a language while scheduling so that data in the selected language only is

imported. This improves import performance. The list of languages is displayed directly from the MDM repository at run time. You can also schedule different jobs for different languages thus improving import performance. (This feature imade available with SAP Notes 1899986 and 1900543)

2. If the MDM catalog item has both contract price and normal price, contract price will be given preference (this feature is available with SAP Note 1896675). If you have multiple contract prices maintained for a single catalog item, the first price that is maintained will be chosen at the time of extraction. If you want to extract the other price maintained for a catalog item, use the BAdIs /SRMNXP/MDM_FIELD_MAPPING and /SRMNXP/CATALOG_TRANSFER_DATA for enriching the data. For more information, refer Catalog Data Enrichment during Import to SRM.

3. Images maintained in MDM repository cannot be imported to SRM. Only image URLs that are maintained as hyperlinks in the MDM repository for the catalog item and given as Type

“Rendered” will be treated as images during import. These links will show up as images in the search results. URLs maintained as hyperlinks in the MDM repository and Type “Links” will be treated as attachments in catalog results. You also need to ensure proper MIME types for the URLs given.

4. Named searches and masks maintained are not considered while importing. The import transfers all the data in the MDM repository to SRM. If you want to filter the data set available for a set of users, TREX authorization concept based on ABAP authorization objects can be used.

Import SRM Product Master Data

This section explains importing the SRM Product Master data. The extraction from SRM product master is done via ABAP report.

Launch transaction code /SRMNXP/CAT01.

1. Enter transaction /SRMNXP/CAT01 2. Select PRODUCT MASTER.

3. Click on Schedule Job button.

4. Define Job to start immediately or schedule to start a specified date/time.

5. For Delta import, use “Reschedule Delta” indicator. The use of these indicators are explained in the table below:

Importing Type Values of Indicators Remarks Full Load or Initial

Load

Reschedule delta : OFF

Use when you are importing data into a catalog first time. All catalog items are added to tables.

Delta load Reschedule delta : ON Use when you want to change some data or add additional items in already imported catalog

Upon successful importing, the catalog data is stored in SRM UI Add-On 1.0 tables for indexing.

Upon successful importing, the relevant product master data is stored in SRM UI Add-On 1.0 tables for indexing.

Catalog Data Enrichment during Import to SRM

BADIs have been provided to enrich data before importing into SRM tables. If you face any issue in importing catalog data or if the data is not imported due to errors, suggest you to verify the catalog data and determine the need for converting the data to suit your organizational requirements. Remember that catalog data is validated before importing and hence ensure that your catalog data is correct.

1. BAdI to enrich 3^rd party Catalog Data

You can use these BAdI to alter data according to your organizations’ requirements or to fill customer fields from OCI data.

Enhancement Spot: /SRMNXP/CATALOG_TRANSFER BAdI Definition: /SRMNXP/CATALOG_TRANSFER_DATA

The interface method ENRICH_ITEM_DATA provides access to catalog item data, search terms, attributes, price scales, images and customer fields. You can enrich any of this data by

implementing the BAdI.

2. BAdI to enrich MDM Catalog Data

BAdI /SRMNXP/MDM_FIELD_MAPPING is provided to do MDM field mapping during import from SRM-MDM Catalog and fill OCI data.

Note that BAdI /SRMNXP/CATALOG_TRANSFER_DATA implementation is also called after this before importing into SRM tables.