1 / 5

1. Check email

1. Check email. 2. Login to Adeptia. Logon to Adeptia: - go to Optimize > Process Flow Logs and in the Process Flow Name drop-down, select the particular transaction name and click on Details

eliasm
Download Presentation

1. Check email

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1. Check email

  2. 2. Login to Adeptia • Logon to Adeptia: • - go to Optimize > Process Flow Logs and in the Process Flow Name drop-down, select the particular transaction name and click on Details • the result is a list of all the transaction instances that have ran with its Status, Start and End Time • Click on Details of the Aborted transaction

  3. 3. Go to logs and see the details Details will open up in another window. Go to the section where the “Level” column contains Error. Here the Message column Will contain the actual error description. In this instance the Country field is set as United States. However the rule is that is must be _unitedstates. In order to find out which record?, in the Logs result screen, there is a “Repository” link, click on that and a new window will appear (refer to next slide).

  4. 4. Go to Repository and see the source data In the Repository window, click on the highlighted XML file, and then in the XML Request File look for this value and see which Field contains this value (here it is in billCountry field). Now go to the database and make the correction for this record. Since the flow is on “AddList” this means that Adeptia was adding (not updating) the records and thus the ModifyBywill be “AddedByWeb” for this record in the database.

  5. 5. Identify which record (s) is causing the problem Another way to find the record that has bad data is to click on the highlighted XML file and look at the NetSuiteInternalID And then correct the data and manually execute this transaction by going to Manage > Process Flow page. If you prefer the automatic trigger will pull this record again next time it runs the Addlist transaction for Sales Order. Note: If the error message in the logs say “not found in ReferenceList” that means that the value is not found in a drop-down.

More Related