Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

To receive notifications if any error occurs in processing Non-EDI data, you need to configure the following properties:

  • abpm.solution.edi.notification.translationError.hostEmailID
  • abpm.solution.edi.notification.systemError.hostEmailID


Notifications sent during Non-EDI processing can be classified into following categories:

  1. Translation Error:
  • Translation Error at source end of inbound processing.
  • Translation Error at target end of inbound Processing.
  • Translation Error at source end of Outbound Processing
  • Translation Error at target end of Outbound Processing.

Translation Error, which occurs at source end of inbound processing, is sent to the email ID configured in the Contact Information field of the trading Partner.
All other translation errors are sent to the email ID configured in the abpm.solution.edi.notification.translationError.hostEmailID property.

  1. System Error

All system errors are sent to the email ID configured in the abpm.solution.edi.notification.systemError.hostEmailID property.
Steps to configure the EDI Solution Properties:

  1. On the Adeptia Suite homepage, click the Administer tab. The Application Settings screen is displayed.
  2. Click the link Update System Properties. The Update System Properties screen is displayed.
  3. Expand Solution Properties and then further expand EDI Solution Parameters (see Figure 55).


Figure 55: EDI Solution Properties

  1. Enter the required email address in the above properties.
  2. Click Save button. A screen is displayed confirming that System Properties have been saved.

    Changes made in the System Properties do not come into effect until you reload the configuration. To reload the configuration, click Reload Configuration in the Application Settings screen.

    For detailed information about the properties and their possible values, refer to Properties of B2BI section.

    9
    Configuring Database Event for Outbound Processing
    In case you are using Database as a source for outbound processing, you need to use Database Event.
    Steps to create a Database Event
  3. On the Adeptia Suite homepage, click the Develop tab.
  4. Go to Services ? Events and then click Database. The Manage Database Event screen is displayed (see Figure 56).


Figure 56: Manage Database Event

  1. Click the Create New link. The Create Database Event screen is displayed (see Figure 57).


Figure 57: Create Database Event

  1. Enter the name and description of the new Database Event activity in the Name and Description fields respectively.
  2. Select the Database Info Id activity from the Database Info Id drop-down list.

    To know how to create Database Info activity, refer to the section Creating Database Info in Administrator Guide.

  3. You can create the database event definition by entering an SQL Query or a database trigger command. By default, SQL Query option is selected.

    For EDI Outbound Processing you can only use SQL Query option.

  4. Enter the query in the SQL Query field. For example:

select * from PurchaseOrder where processingStatus='Ready'

Here:
processingStatus is a field in the source database table, which stores the status of the records. For example, If any record is already processed or not. This is important to make sure that same record should not be processed repeatedly.
You can use any existing field for this purpose or you can add an additional field.

In the above example, only those records, whose processingStatus is Ready, are picked for processing.


  1. Select the Condition checkbox should not be enabled in case of EDI Outbound Processing.

    In case Trigger for All Record checkbox is checked, then for all the records, only one process flow is trigger and it processes all the records.

  2. Enable the Execute Update Query option and enter the update query in the Update Query field. For example:

update PurchaseOrder set processingStatus='%%Pass%%'

The update query is executed for each record picked up based on select query in previous step. Database Event executed update immediately after picking up the record to update the column storing the status of the record. This ensures the records are not picked up again. For example, in the query given above, the processingStatus will be updated to Pass.


  1. Enter the where condition. For example:

where id='%%id%%'

Where condition is used with Update Query in previous step to update only those records that satisfies this where condition.
It can be any column or set of columns that make the record unique.
In the above example id is a column in the database which uniquely identifies the records and %%id%% is value of this column in the selected record.


Once processing of the records is completed, the status (value of processingStatus) will be updated to Processed.
Even if any record encounters any error while processing, their status will be changed to Processed. You have to refer EDI log to check if any record has not been processed.


  1. Enter the date from which Database event will start triggering; in the Event Start Date field. The date must be in mm/dd/yyyy format. Click the Calendar icon and select the required date from the calendar.
  2. Enter the start time from the Time drop-down list.
  3. Enter the date on which Database event will stop triggering, in the Event Expiry Date field. The date must be in mm/dd/yyyy format. Click the Calendar icon and select the required date from the calendar.
  4. Enter the expiry time from the Time drop-down list.
  5. Enter the time interval, the database event checks the database Server in the Polling Frequency field. Enter the digit in the Frequency field and select the unit of time i.e. seconds, minutes or hours etc. from the Duration drop-down list.

    Recommended minimum Polling Frequency is 30 seconds.
    To learn about Advanced Properties refer to Changing Advanced Properties section.

  6. Click Save button. This displays a screen confirming that the database event has been created successfully. 10
    Enabling Delete on Success Option for EDI Processing
    When an EDI process flow is executed successfully without any error records then, you may want to reclaim the allocated memory space by deleting the now processed files. You can achieve this by configuring Enable Delete On Success option in the various EDI activities. To enable this option, you need to modify the following activities:
  • InboundFileSource
  • OutboundFileSource
  • InboundFTPSource
  • OutBoundFTPSource


Steps to enable Delete on Success option:

        1. Login with EDISolutionUser.

          Password of EDISolutionUser is ediuser123.

        2. From the workspace menu expand *Design ? Services ? Source{*}.
        3. Click on the File link. This action will show you the Manage File Source screen.
        4. Edit the InboundFileSource activity (see Error! Reference source not found.).


Figure 58: InboundFileSource Activity Edit Screen

        1. Click on the Delete File on Success checkbox.
        2. Save the activity.
        3. Repeat the above steps for the other following activities:
  • OutboundFileSource
  • InboundFTPSource
  • OutBoundFTPSource

11

  • No labels