Skip to main content

A2Z200 - A2Z P360 Order Synchronization Batch Job

Paige Freeman
  • Updated

Clients must submit a support request to enable the A2Z integration. Clients using the A2Z integration must submit a support ticket to have A2Z-related hotfixes deployed in their environment. The integration is only available for web client.

The A2Z200 process is a batch job within ThreeSixty that synchronizes order and payment data retrieved by the A2Z100 process. It validates and migrates this data into ThreeSixty, ensuring that orders and payments are accurately reflected in the system.

How It Works

  • Data Retrieval: The A2Z100 process collects order and payment information from A2Z Events and stores it in intermediate tables.
  • Data Validation: A2Z200 validates the retrieved data, checking for discrepancies such as unmapped products or constituents.
  • Data Migration: Upon validation, A2Z200 creates or updates orders and payments in ThreeSixty as needed.

First, run the A2Z100 process to retrieve order and payment information from A2Z and store it for further processing. Then, map the products as necessary and run A2Z200 to take the data collected by the A2Z100 process and create or update the orders/payments as needed in ThreeSixty.

Best Practices

  • Run A2Z100 First: Always execute the A2Z100 process before running A2Z200 to ensure that data is available for synchronization.
  • Map the Products: Ensure newly imported A2Z events and items are correctly mapped to ThreeSixty products.
  • Review Exception Reports: After running in EDIT mode, examine the exception reports for any issues that need to be addressed before migrating data.
  • Monitor Data Integrity: Regularly check for discrepancies between A2Z and ThreeSixty to maintain data accuracy.

The A2Z200 process currently supports orders for products within the MISC, MTG, and XBT subsystems.

The data updated by the A2Z200 process is stored in the A2Z200_PROCESS and A2Z200_PAYMENT_PROCESS tables.

Job Parameters

Parameter Description
Run Mode
  • When run in EDIT mode, the process generates the reports, including an exception report listing any A2Z orders that lack a mapped product or constituent in ThreeSixty, but does not update the data.
  • When run in PROD mode, the process validates the data and proceeds to create or update orders and payments in ThreeSixty as needed.
Event Id The Event Id from A2Z. This can be found within A2Z or within ThreeSixty on the Product Mapping page.
Receipt Type

The Receipt Type that should be used for the migrated transactions.

Regardless of the payment method used in A2Z, all transactions migrated to ThreeSixty will be linked to the receipt type selected during the A2Z200 TRS process.

Troubleshooting

Following are common validation messages displayed on the A2Z200 Exception Report and their recommended resolutions.

Validation Resolution
A2Z Item not mapped in P360 The A2Z Event is not mapped to a product in ThreeSixty. Map the product(s) on the A2Z Product Mapping page.
Constituent could not be identified The constituent in ThreeSixty is not correctly mapped to the constituent in A2Z. Check that the Company Number in A2Z matches the Master Customer ID in ThreeSixty. 
Mapped product is not validated The product that has been mapped to the A2Z Event is not validated in ThreeSixty. Validate the product in ThreeSixty and run the process again.
Product Details could not be fetched for Product Id The Available Through date for the product must be in the future. This can be set on the Product Setup page.
Product Account not defined for Product Id You need to define GL Accounts for the product.
Revenue Distribution is not defined for Product Id You need to define Revenue Accounts for the product.
Recognition Method must be INVOICE for Product Id The Recognition Method needs to be set to "On Invoice" for the product. This can be set on the Accounts Setup page.
Short pay method must be AR for Product ID The Short Pay Method needs to be set to "Create Receivable" for the product. This can be set on the Rates and Pricing page by selecting Structure Settings from the contextual menu in the grid.