Working with Profiles and Contacts > Enterprise Applications Integration Considerations > Differences for the Enterprise Edition
  
Differences for the Enterprise Edition
For the Enterprise Edition, the process is different; in this case not only is a customer created but also a business relation. The same template mechanism is employed for default data, but in this case requires both a business relation template and a customer template
When the customer is created in QAD Enterprise Applications, both the business relation and customer code values are auto-generated and returned to be stored against the profile.
Additionally, any contacts available against the profile in CRM will be created against the business relation in Enterprise Applications along with any addresses created in CRM that correspond to supported address types in Enterprise Applications.
A final consideration is that customers created in the Enterprise Edition require the update of fields in the Customer Data Maintenance function to enable them to be transacted. QAD CRM does not perform this final update when the Customer is created by sending it from Profile Maintenance.
Receiving Profiles and Updates from Enterprise Applications
Customers, suppliers, and end users can be received from Enterprise Applications as profiles in CRM. There are two mechanisms for this.
Initial Data Load
Typically, this function is run when the system is configured and ideally when all customer and supplier data has been loaded into Enterprise Applications.
Instant Update
This mode is active whenever a user is logged on to the system. Effectively, any updates to customers, suppliers, and end users that occur in Enterprise Applications will automatically create or update the relevant profile records in QAD CRM. The ERP Status field will reflect the QAD Enterprise Applications type of Profile—Customer, Supplier, or Enduser—and the Cust No field will reflect the customer or supplier number from QAD Enterprise Applications. In addition the Type field in CRM will also be updated to reflect Customer, Supplier, or End User.
The profile will be created in the business unit that corresponds to the domain in which the update occurs.
Differences for the Enterprise Edition
If a business relation in the Enterprise Edition has more than one linked supplier or customer, QAD CRM will create each linked supplier or customer as a profile sharing the same business relation code.
Example: Business relation Colossal Conglomerates has associated two customers, Colossal Spain and Colossal France, and also a supplier, Colossal Germany. In CRM there are three separate profiles created with ERP Status set to Customer or Supplier as required and all displaying the same business relation code on the Profile Detail tab.
Contact information—which for the Standard Edition is taken from the first contact in the Customer Data Maintenance function—will now be taken from the multiple contacts available for the business relation.