To receive notifications if any error occurs in processing Non-EDI data, you need to configure the following properties:
...
Notifications sent during Non-EDI processing can be classified into following categories:
- 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.
- 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:
...
- On the Adeptia Suite homepage, click the Administer tab. The Application Settings screen is displayed.
- Click the link Update System Properties. The Update System Properties screen is displayed.
Expand Solution Properties and then further expand EDI Solution Parameters (see Figure 55).
...
...
Figure 55: EDI Solution Properties
- Enter the required email address in the above properties.
- Click Save button. A screen is displayed confirming that System Properties have been saved.
Info |
---|
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. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
9
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
- Click the Create New link. The Create Database Event screen is displayed (see Figure 57).
...
| To know how to create Database Info activity, refer to the section Creating Database Info in Administrator Guide. |
...
| For EDI Outbound Processing you can only use SQL Query option. |
...
select * from PurchaseOrder where processingStatus='Ready'
...
...
| 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. |
...
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. |
- 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. |
| Once processing of the records is completed, the status (value of processingStatus) will be updated to Processed. |
...
| Recommended minimum Polling Frequency is 30 seconds. |
...
- InboundFileSource
- OutboundFileSource
- InboundFTPSource
- OutBoundFTPSource
...
| Password of EDISolutionUser is ediuser123. |
...
- Click on the Delete File on Success checkbox.
- Save the activity.
- Repeat the above steps for the other following activities:
- OutboundFileSource
- InboundFTPSource
- OutBoundFTPSource
11