|Bookshelf Home | Contents | Index | PDF|
The common integration scenarios listed here apply to many of the integration requirements you face. Siebel eAI allows you to accomplish integrations within the scope of these scenarios, but is not limited to the scenarios described here.
In this scenario, you create a Siebel workflow process to create a unique file every time 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.
In this scenario, you want service requests entered from your Web site to be entered as service requests in Siebel Service. You also want to pull an automatically-generated service request number from Siebel Service, add it to the service request, and generate a file that is attached to a confirmation email message to the service requestor's email address.
In this scenario, whenever 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 the salespeople want to order from the remaining supply at the current price, they can respond to the message.
In this scenario, your salespeople want to be able to send an order from Siebel applications to your back-office ERP system that is using Japanese 932, while the code page used by the Siebel application is UTF-8. Your salespeople want to receive a confirmation with an order number generated by the ERP system.
In this scenario, whenever product information in your SAP R/3 system is updated, you want the system to send an updated IDOC to your Siebel system and have the product information updated in the Siebel Product business object.
|Overview: Siebel eBusiness Application Integration Volume l|