TechKnowledge Content
SUMMARY
This articles discusses how to determine the number of source queries to use and how to link them when using Integration Manager.
MORE INFORMATION
To determine the number of source queries to use and the query relationships, open the Integration and look at the destination mapping. A Subfolder icon indicates that there is a one to many relationship between the Folder and the mapping above it. This type of relationship requires an additional query. A Collection icon indicates that there is a one to one relationship between this mapping and the mapping above it. This type of relationship does not require an additional query.
For example, if you have a SOP integration that brings in items and payment information, three source queries are required. To verify the number of queries and review the mappings, open the SOP integration mapping and look at the relationship between the mapped fields. In this example, you must map fields to the main Sales Transaction mapping, the Items mapping, and the Payments mapping. One query is required for the main mapping – Sales Transactions. Items mapping and the Payments mapping are subfolders of the main mapping and will require additional queries.
The source query linking will be the same as the destination mapping. Because the Items subfolder is linked directly to the Sales Transaction mapping and the Payments mapping is also linked directly to the Sales Transaction mapping, the Query Relationships information will show that the SOP Number field in Items Query is linked to the SOP Number field in the Sales Transaction query (Header Query), and that the SOP Number field in the Payment Query is linked to the SOP Number field in the Sales Transaction query (Header Query).
In a different example, you may have a SOP integration that brings in items, item detail, and intrastat information. This integration will also require three source queries. To verify the number of queries and review the mappings, open the SOP integration mapping and look at the relationship between the mapped fields. In this example, you must map fields to the main Sales Transaction mapping, the Items mappings, the Intrastat mapping, and the Item Detail mapping. Because the Item Detail mapping has a one to one relationship with the Items mapping above it (note the Collection icon), no additional query is needed for this mapping. The fields that are mapped to the Item Detail mapping will be pulled from the Items query.
The source query linking will be the same as the destination mapping. Because the Items subfolder is linked directly to the Sales Transaction mappings and the Intrastat subfolder is linked directly to the Items mapping, the Query Relationships information will show that the SOP Number field in the Item Query is linked to the SOP Number field in the Sales Transaction query (Header Query), and that the Item Number field in the Intrastat Query is linked to the Item Number field in the Item Query. Note that there is not an Item Detail query because those fields will be mapped from the Item Query.
This article was TechKnowledge Document ID: 29102
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.
THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
