Overview: Siebel Enterprise Application Integration > Scenarios for Using Siebel EAI > Overview of Architecture for Siebel EAI >

Scenarios for Common Integrations

The common integration scenarios described in this topic apply to many of the integration requirements you might encounter.

Outbound Message to a File

In this scenario, you define a Siebel workflow process that creates a unique file when a support representative closes a service request. The file is then sent to a central directory on a network server, where at midnight it is bundled automatically into an Adobe PDF file along with other closed service requests for that day.

Round Trip Message from a File to Siebel Applications

In this scenario, a service request that is entered from within your Web site must also be entered as a service request in Siebel Service. Also, you must pull, from Siebel Service, a service request number that is automatically generated, add it to the service request, generate a file that is attached to a confirmation email message, then send the email to the individual who requested service.

Round Trip Message from an External Application

In this scenario, when your back office Enterprise Resource Planning (ERP) system recognizes a reorder point on a popular inventory item, it sends a message to your Siebel application to notify salespeople that a popular item is about to be reordered. If a salesperson must order from the remaining supply at the current price, then the salesperson can respond to the message.

Round Trip Message to an External Application with a Different Code Page

In this scenario, a salesperson must send an order from a Siebel application to your back office ERP system which is using Japanese 932, while the code page used by the Siebel application is UTF-8. The salesperson must receive a confirmation that includes an order number which is generated by the ERP system.

Inbound Message from an External Application

In this scenario, when product information in your SAP R/3 system is updated, the SAP R/3 system must send an updated IDOC to your Siebel system, then the product information must be updated in the Product business object in Siebel.

Outbound Message to an External Application

In this scenario, account information must be updated in your SAP R/3 IDOC from Siebel Business Applications.