Sign in
< Back to Top

Configuring and Testing the Order flow

The FBM (MFN) orders from AMP are retrieved from CIC and the AMP order JSON is translated into NetSuite Sales Order XML, which is then posted to NetSuite.

This article explains the settings required to configure the integration between AMP Seller Central and NetSuite to retrieve the FBM (MFN) orders from AMP and create the corresponding Standard Sales Order on NetSuite. 

How to Configure - Global Variables and Schedulers

  1. Configure the following global variables in the com.cleo._customer_.booster.amp.AmpGV Global Variable object: 
    Global Variable Description
    PollingMinutes This is used to retrieve orders from Amazon for the latest "n" minutes.
    PollingHours This is used to retrieve orders from Amazon for the last “n” hours.

    Default value: 24  
    OrderStatus This is used to select orders with a current status that matches one of the status values that you specify. Multiple status can be configured by providing comma separated values ( Ex - Shipped, Pending).

    Default value: Unshipped
    MarketPlaceId

    This is used to select orders that were placed in the Marketplaces that you specify. To fetch the MarketPlaceId, refer the following link from Amazon documentation which provides a list of Amazon SP API MarketplaceId values.

    Default value: dummy
    MerchantIdentifier This is the identifier for the seller of record; assigned by Amazon when you opened your seller account. To fetch the MerchantIdentifier, please log into your Seller Central account.

    Default value: dummy
     AmpHttpErrorCodesToBeIgnoredForTicketCreation

    This is used to identify HTTP error codes that need to be flagged as ‘successful job flows’ in the cockpit. If not mentioned here, the error codes would be flagged as failed jobs in the cockpit. In case an AMP SP API request is throttled, the execution waits as per time period configured in the respective API restore rate global variable, and the API request is made again. Since we have a retry logic for throttled requests implemented in the accelerator, these jobs need not be marked as failures, and hence this global variable is configured with default value of throttling error code (429).

    Default value: 429
    CustomerNotificationEmail

    In case the order feed submission is rejected on Amazon, the ticket is created and the issue is visible on the Cockpit. An additional email notification is sent to the email that is configured in this global variable.

    Default value: name@customer.com
  2. Configure the Process Schedulers: 

    The scheduler - com.cleo._customer_.ampnetsuite.order.LaunchAmpFbmOrderPS is scheduled to run every 1 hour with start time set as 12:00:00 AM. See Creating and Defining Process Schedules – Cleo for more information about defining Schedulers.

How to Test the Order Flow

After you configure the Order Flow (described above), you can test the flow by running it manually or automatically.

  1. Make sure the following Projects have been deployed:
    • com.cleo.b2bcloud.core
    • com.cleo.b2biaas.clarify
    • com.cleo.cic.cockpit.core
    • com.cleo.cic.util
    • com.cleo.cic.connector.netsuite
    • com.cleo.cic.connector.amp
    • com.cleo._customer_.booster.netsuite
    • com.cleo._customer_.booster.amp
    • com.cleo._customer_.ampnetsuite

  2. Run the LaunchAmpFbmOrderBPS.
  3. Review the results of the flow as follows:
    • Review Auditor logs.
    • Verify the following in the CIC Cockpit: Message Tiles, Jobs, Dashboard > Charts.
    • If the processing fails, then a ticket will be generated; errors will be visible in the cockpit message tile and the job (examples shown below).

      (Cockpit Error)
      AppTip_CockpitError1.png

      (Cockpit error job)
      AppTip_CockpitError2.png

How to Customize the Order Flow

Two typical areas to customize the Order Flow are the schedule and mapping details.

Customizing the Schedule

The scheduler (com.cleo._customer_.customer_.ampnetsuite.order.LaunchAmpFbmOrderPS) is configured to retrieve orders every 1 hour by default. Change the schedule to run more frequently or less frequently. For details on defining a scheduler, see Creating and Defining Process Schedules.

Adding Mapping Details

The Sales order on NetSuite is currently created with the data required to process orders successfully. The values that are being mapped are documented in the Integration Design Specification template -
(com.cleo._customer_.ampnetsuite.docs.AMP-NetSuite-Accelerator-LMS.xlsx) - However, if you wish to add any additional fields, you must update the following Ruleset: com.cleo._customer_.ampnetsuite.order.AmpOrderToNetsuiteSalesOrderRS.

Related articles

Comments

0 comments

Please sign in to leave a comment.