Scenario 48 - Sales Lead

48.0 Overview

Scenario #48 describes the integration for partner sales systems with a supplier sales system concerning sales leads.

The purpose of this scenario is to enable the visualization of the participants in the process and the dialogs between them for this specific integration. This scenario is not meant to be the only model for integrating general ledger applications to a budget applications. This is simply one model that may be used to guide one’s own integration efforts.

48.1 Scenario Diagram

The scenario below contains the participants involved in the interaction, the dialog flows or conversation between them, certain assumptions about the sequence of events, and assumptions about the technical approach, for example, publish and subscribe.

This is a model to be used as a design recommendation, not a required approach.

48.2 Assumptions

This scenario assumes a loosely coupled, asynchronous approach with transaction management required but not explicitly defined.

It is assumed that the supplier party is the organization that is interested in providing goods or services.

The environment for this first part of this integration is typically within an enterprise and within a division.

The environment for this second portion of this integration is typically between two enterprises.

This scenario also assume that one application will maintain the master data for integration.

48.3 Participant Definitions

This scenario contains two participants or roles: a partner sales system which is intended to provide sales leads to a supplier party, and the supplier parties system.

48.4 Business Workflow (Sequence)

The business workflow is graphically represented by starting at the Scenario top and reading from top down and from left to right.

This scenario contains the following events in the workflow sequence:

  1. A sales lead is sent to a supplier party for processing including possible credit and relationship establishment which is acknowledged by the supplier parties system including any adjustments.
  2. An exchange of a possible sales lead relationship initiated by the supplier party
  3. The change and adjustment of a sales lead and its associated information initiated by the partners system.

48.5 Exception Handling

Exception handling is highly localized as the result of an implementation’s infrastructure, management and business rules. As such, this section of the Scenario documentation is planned to be used as a guide to help understand the additional intent of these Scenarios. If no exceptions are noted here, then it can be assumed that the Scenario designers agreed that the Scenario is straight forward and has no additional needs:

  • Note that the Confirm BOD is not shown in the scenario and that it is the most obvious method for providing an application level exception and feedback mechanism between business software components. Full Confirm BOD use is described in other OAGIS documentation in detail, but it should be noted that the specific use of the Confirm BOD may vary significantly from scenario to scenario and from integration to integration.

  • The Confirm BOD is typically intended to be used by the original receiving application to communicate to the sending application that the information it sent in the message BOD (business object document) was received and understood and can be processed.

  • If the information was not received or nor understood, or contained errors of any type, it is accepted practice for the OAGIS users to presume that the data was not acted on and in the absence of a Confirm BOD within a partnership previously agreed to time limit to resend the original message again.

  • As errors and assumptions are the bane of any implementation, it is strongly recommended that the Confirm BOD be used to prevent any potential problem although it is not a requirement by OAGIS use.

Feedback

OAGi and its members welcome your feedback.