Using Inter-Entity Trade
Once Inter-Entity Trade is set up, users do not manually enter transactions into Inter-Entity.
After configuring and testing Inter-Entity Trade, the related processes become automated. Inter-Entity Trade automatically initiates transactions based on the posting of the source transactions in Sage 300.
Orchid recommends that you review the Audit Inquiry Logs regularly to check transactions and identify transactions that failed to post successfully.
Errors can occur for a number of reasons, i.e. if there is no LanPak available at the time of posting the source transactions or if the user's credentials have changed. Details of the errors are recorded in the Inter-Entity Trade Audit Logs. Promptly correcting these errors is important, for example, before anyone manually creates the missing transactions, which could disrupt the chain established in Inter-Entity Trade.
After resolving the root cause of errors appearing in the Audit Log, the transactions in question should be re-processed using the appropriate Inter-Entity Trade Periodic Processing function.
Refer to troubleshooting tips in the articles below:
Tip: At the time of creating entries in the target entity, Inter-Entity will use an additional Sage 300 License. You can reserve a Sage 300 LanPak for the Sage 300 user configured in Trade Organizations. In older versions of Sage 300, it is recommend the "Use IAP" switch is turned off on all workstations and for all users in a Terminal Server setup.
