Explanation of the destination options for the SOP Transaction using SQL Optimized Object adapter

TechKnowledge Content


In the options tab in the destination mapping for the Sales Transaction collection there are some new selections. I am wondering what they do and their effect on the integration?


These options can be set to optimize the performance of the SOP integration, typically by reducing the amount of validation performed for the integration. Because validation is reduced during the integration, it is imperative that the data is correct and consistent before the integration is run. If incorrect data is integrated, then all performance gains during then integration may be lost trying to fix the problems directly in eEnterprise. The following options are available:

Validate Record Keys
Setting this option to False prevents the key values for individual records from being checked, thus speeding up the integration. The posting routines in the accounting system will detect any documents that have invalid key values and prevent them from being posted. If documents are integrated with invalid key records, delete the batch they were integrated into and run check links on the sales work and sales distribution tables. Then fix the problem or turn the validation back on and rerun the integration. We recommend that this option to set to True.

Update Inventory Records
Setting this option to False prevents the Inventory Quantity Master table from being updated while the integration
is being run. After an integration, the inventory quantities would be incorrect, so the user should perform a reconcile operation in the accounting system to update them. It is advised to reconcile both SOP and Inventory. To reconcile SOP go to Utilities > Sales > Sales Doc Utilities and enter a range of documents to reconcile or mark to reconcile all documents. To reconcile Inventory go to Utilities > Inventory > Reconcile and enter a range of items or reconcile all items. Depending on how many documents and items are integrated, it may take longer to perform the reconcile in eEnterprise than it would to have the quantities updated as the integration proceeds. For this reason, we recommend setting this option to True.

Update Batch Header Record
Setting this option to False prevents the header record for a batch from being updated during an integration. The total number of transactions and the total transaction amount for the batch won’t be updated. A user can perform a check links operation on the Sales Work table to update the batch header records to reflect the transactions in the batch. Again, depending on how many documents are in the Sales Work table, check links may take as long or longer than the integration itself, so you would loose any performance gains. Note that it is not possible to run check links on one or a range of batches in eEnterprise and the sales work files contain all sales documents saved to batches, this includes quotes, orders, invoices, returns and backorders, not just the documents that were integrated. For these reasons, we recommend setting this option to True.

Update Customer Record
Setting this option to False prevents a customer’s available credit from being updated as the integration is performed. To update a customer’s credit limit information, a reconcile operation can be performed on the Current Customer Information. To perform this reconcile go to Utilities > Sales > Reconcile and mark the radio button next to Current Customer Information. You can insert a range of customers or reconcile all. As previously stated, depending on the number of customer records in your database, this procedure may take longer than having Integration Manager update the available credit during the integration.

Use Local Caching for Customer Information*
Setting this option to True causes customer information to be cached locally as the integration is run. This can potentially increase the speed of the integration.

Use Local Caching for Inventory Item Data*
Setting this option to True causes inventory item information to be cached locally as the integration is run. This can potentially increase the speed of the integration.

Track Master Numbers
Setting this option to False prevents master numbers from being assigned to documents as they are integrated. A master number is a single number assigned to a series of documents that is used to track related documents. For example, if you enter a quote directly in SOP and transfer that quote to an order, then subsequently transfer the order to an invoice, each document will be assigned the same master number thus linking them all together. If you have set up the accounting system to track master numbers (Setup > Sales > Sales Order Processing), you should leave this option set to True.

*Please refer to the Techknowledge entitled "Caching Customer and Inventory information during SOP SQL Optimized Integration on 6.0", KB document number 871760.

This article was TechKnowledge Document ID: 19286

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.