Creation and processing of AIP events

The AIP Connector automates data synchronization between Business Central (BC) and the Aptean Integration Platform (AIP) using inbound and outbound events to ensure consistent and accurate master data across both systems.

Outbound events automate the export of master data and operational records from Business Central to external systems, while inbound events import and update master data into Business Central covering entities like customers, vendors, addresses, locations, sales orders, and transport requests.

The AIP Events page provides a centralized location for tracking and managing events within the AIP connector. It allows users to monitor the status of both outbound and inbound events. 

• Select the Search icon , enter AIP Events, and then choose the related link.
  Alternatively, you can open the AIP Events page from the AIP Connection Setup page by selecting the Events action or from the source document (customer/vendor/sales order/transport request) page (Related > AIP Connector > Events).- The AIP Events page opens.
  You can view all the events that are created between AIP and Business Central as follows:

  Field	Description
  Entry No.	Specifies the entry number of the event.
  Source System Id	Specifies the system ID generated for the event.
  Source Type	Specifies the source type of the event.
  Source Product	Specifies the ID of the source product.
  Event Type	Specifies the type from which the event is created.
  Status	Specifies the status of the event. The available options are: Open: Event is currently active and to be processed. Ready: Event is prepared for export or processing. Review: Event is under review to be processed. Complete: Event has been successfully processed or sent. Ignored: Event is excluded from processing due to errors or mismatches. Failed: All schedules in the payload have failed. Partially Failed: One or more schedules in the payload have failed. Note that the Failed and Partially Failed options are applicable only to inbound events.
  Error	Specifies if an error has occurred during the process of the event. If an error occurs during event processing, the event will be marked as Errored. Note that if an event is marked as Errored, it requires review and troubleshooting to identify the root cause of the error. After resolving the issue, the event can be reprocessed, and its status will update accordingly.
  Message	Specifies the description of the error associated with the event.
  Direction Type	Specifies the direction of the event. It may be either Inbound or Outbound.
  Configuration	Specifies the configuration of the selected event.

To process the AIP events, follow these steps:

1. Navigate to the desired event.
2. On the action bar, select Process. The AIP Process Event dialog opens.
   The available operations for outbound events are:
   • Build: Creates the payload for the event, preparing it for transfer to the external system.
   • Build & Send: Creates the payload and sends the event to the external system.
   • Ignore: Prevents the event to be imported or sent that are created by mistake.
   
   The available operations for inbound events are:
   • Import: Processes all downloaded inbound events.
   • Ignore: Prevents the event from being processed.

The Build and Build & Send options are available for outbound events, and Ignore option is available for outbound and inbound events.

To handle errors, follow these steps:

1. Navigate to the event which has error while processing it.

2. On the action bar, select Actions > Event Errors.
   The AIP Event Errors page opens.

To recreate the failed event, follow these steps:

You are allowed to recreate the failed events due to errors as follows.

1. Select the failed event.

2. On the action bar, select Process.
   The system displays a confirmation message.

3. Select Yes.
   The AIP Process Event dialog opens.

You can select the available options and recreate it.

You cannot create duplicate events with the Status field set to Open.