1. Integrating Sales with JD Edwards EnterpriseOne
  2. Oracle CX Sales and JD Edwards EnterpriseOne Integration Component Architecture

Oracle CX Sales and JD Edwards EnterpriseOne Integration Component Architecture

The following lists the files required to implement the integration between Oracle CX Sales and JD Edwards EnterpriseOne.

Refer to the Related Topics section in this topic for a link to Integrating Oracle CX Sales with JD Edwards EnterpriseOne (Doc ID 1645923.1) on My Oracle Support. The files are located in the Attachments section of the article. The following figure shows the components of the integration between Oracle CX Sales and JD Edwards EnterpriseOne and their relationship with each other.

  • Oracle CX Sales standard objects. Standard objects are configured by adding fields, object functions, triggers, and validations, and by configuring UI pages.

  • Oracle CX Sales custom objects. Custom objects are created for the integration, and fields, pages, functions, and so on are added to the objects.

  • Groovy functions. Groovy scripts create functions, triggers, and validations that modify the action of Oracle CX Sales objects.

  • JD Edwards EnterpriseOne web services. Oracle CX Sales calls JD Edwards EnterpriseOne web services directly. For more information about web services, refer to the Integration Services topic.

  • JD Edwards EnterpriseOne Sales Order Entry Program. Opportunities in the Sales application in Oracle CX Sales are integrated with the Sales Order Entry Program in JD Edwards EnterpriseOne.

The figure shows the different components which make up the integration between Oracle CX Sales and JD Edward EnterpriseOne.