How to Use a Connector Business Process - 2 Examples

Two examples are provided to show how a Connector Business Process can be used with the AMP Connector.

Example 1: Below is an example showing how Connector Business Processes can be used.  In this example, ListOrders.bps (from the Connector Project) is used to retrieve the existing orders from the Amazon Seller Central application. This is followed by a step (Ruleset) that then transforms the received data.

Steps to create the Connector Project and Integration:

Step 1: Create a Connector Project.

Step 2: Create an Integration Project (CIC Project).

Step 3: Set the Connector Project as a dependency in the Integration Project.

Step 4: To perform an operation using the Connector BP and Schemas, follow the below steps:

Step 4a: Create a BP in the Integration Project.

Step 4b: Create a task in the above BP to include the BP from the Connector Project, i.e. ListOrders.bps (ListOrders.bps is equivalent to ListOrders API).

For ListOrders.bps, pass these parameters:

• MarketplaceID

• Either CreatedAfter or LastUpdatedAfter is a required parameter. Both cannot be used together. Accepted date format is (YYYY-MM-DDT00:00:00.000Z)
  
  

Step 4c: Create another task in the Business Process - a Ruleset. This Ruleset maps from JSON to any Clarify supported schema. All Connector Schemas (request and response) will be JSON format. Map any required fields in this Ruleset (e.g. AmazonOrderId, Price, Quantity, etc.)

Example 2: This example shows how to use the SubmitFeed Business Process. This BP is used to upload a feed for processing by Amazon. In this example, it is used to update the price of a given item.

Steps to perform the SubmitFeed operation using the SubmitFeed BP and Schemas:

Step 1: Create a Business Process in the Integration Project.

Step 2: Create a task to fetch the data that needs to be sent for processing. Any object that reads data can be used.

Step 3: Create a new task in the Business Process - a Ruleset. This Ruleset will map from any supported schema to an XML schema. The XML schema to be used is AmazonEnvelopeOBJ.xml.objSchema.

The following header mappings are required for every SubmitFeed operation regardless of the feed type.

DocumentVersion -- 1.01

MerchantIdentifier  -- SellerID or Merchant ID

MessageType  -- Price or Inventory or ProductImage (this depends on the feed type)

MessageID -- ID of the payload sent

Depending on the feed type, the content of the feed that has to be submitted will change. This example is specific to Price so the mapping will be with respect to the Price feed type.

For more information on feedType please refer to the link: https://docs.developer.amazonservices.com/en_US/feeds/Feeds_FeedType.html

Step 4: Create a new task in the above BP to include the BP from the connector project i.e. SubmitFeed.bps 

For SubmitFeed.bps, the below parameters are required:

• feedContent   
  
  (the output of the Ruleset created in the above step)

• feedType         
  
  (the keyword specific for each feedType.  For Price the feedType is                     _POST_PRODUCT_PRICING_DATA_)