Oracle pdh publish schema

Read this section to learn concepts that are important to know before you configure and use the integration between Oracle Commerce and Oracle Product Hub Cloud.

This section describes concepts to know before you configure and use the integration between Commerce and Oracle Product Hub Cloud. It includes the following topics:

• Audience
• Overview
• Prerequisites
• Assumptions

This section is written for Commerce and Product Hub administrators who want to set up and configure the integration between these two systems. To use this documentation, you should have experience with Commerce , Oracle Integration Cloud (OIC), and Product Hub. This section does not provide any instructions for configuring any other aspects of these systems beyond those required for the integration. For information on other configurations, refer to each product’s documentation, available on the Oracle Help Center.

This integration provides the following features:

• Syncs products created in Product Hub to Commerce
• Associate collections created in Commerce to the products
• Optionally trigger a publish event in Commerce when import is complete
• Upload images from Product Hub to Commerce and associate them with products

• The item publication job can be scheduled in Product Hub with a required frequency, for example once per day or once every six hours. It exports new and updated items based on the defined filter criteria. The job runs as specified by the schedule, and on completion, it posts the exported files to Oracle Universal Content Management (UCM) and triggers the item-publication job event.
• The item publication job event triggers the OIC flow. It checks if a publish event is currently running in Commerce . If Commerce is publishing or if another import or export job is active, then it cannot accept new requests for import. In these cases, the integration execution stops and is moved to a queue to be retried at a later time. When publishing completes, the integration is resumed from the queue.
• The integration downloads the exported file from UCM. The archive file may contain multiple XML files, which are transformed into Commerce JSON format. The integration archives the JSON files and uploads them to Commerce . It then triggers the bulk product import process to load the data into the Commerce Admin server.

Publish imported items: After the import is successful, the integration flow checks if auto-publish is enabled in the OIC lookup. If enabled, it gets the total number of records pending publishing in Commerce for the user/application configured in the OIC Commerce connection. If it finds any such record and the number of such records is less than the threshold configured in OIC lookup, it publishes those records. Note that the publish operation includes all the records for the user, not only the ones imported as part of the current integration flow. If the threshold exceeds 10 MB, it sends an email notification to the administrator to inform that publish was not initiated automatically. A Commerce admin user can manually start a publish in this case.

Upload images: If Media Sync is enabled (that is, if CXCommerceMediaSyncEnabled is set to true in OIC lookups), then media items are also synced along with the items/products from Product Hub to Commerce . Supporting formats for images to be linked with products in Commerce are JPG, JPEG, PNG, and GIF. Separate ZIP file will be created with all the images of supported formats and then uploaded to Commerce . For more information about the rules Commerce enforces for images, see Manage Media for Your Store in Using Oracle Commerce .

Configuring and using this integration requires the following. If you require one or more of these, please contact an Oracle sales representative.

• A Commerce account and access to Commerce 20D or later.
• An Oracle Fusion Product Hub account and access to Product Hub Cloud 20B or later.
• An Oracle Integration Cloud account and access to Oracle Integration Cloud Service.

This integration makes the following functional assumptions. These assumptions require a functional understanding of both Commerce and Product Hub.

• Catalogs, collections, and product types are created in Commerce before the products are imported into Commerce by the integration.
• Products and SKUs data is always managed in Oracle Product Hub and is imported into Commerce . This means that Product Hub is the only source of products and SKUs for Commerce .
• By default, Commerce list prices are mapped to Product Hub's purchase list prices. It's recommended to create an Extensible Flexfield (EFF) attribute for sale list price and override the mapping.
• All changes are published on Commerce , once the products are imported.
• Configurable SKUs, add-on products, related SKUs, services and subscriptions are not supported by default in this integration. You will need to extend the integration if you wish to support these components.
• PDH Item Number is mapped to Commerce Product ID and SKU ID. While Item Number can include spaces and have a maximum length of 256 characters, Commerce IDs do not support spaces and can have a maximum length of 165 characters. Therefore, appropriate rules must be set in PDH to conform data to Commerce requirements. Also, the Item Number must not be modified in PDH.
• Translations to secondary locales are not supported by default in this integration. If your Commerce environment requires translations, this requires multiple exports to be triggered in PDH in different locales, and any extension to this integration must handle them accordingly in the integration flow.
• You can customize this integration to link Images to SKUs and to map an image’s path and name under SKUs. Before you can do this, make sure that the productType is mapped to a Commerce product type for which Allow product images at the variant property value level is enabled in the Variant properties.