BACKGROUND OF THE INVENTION

Product manufacturers and service providers, known as â€œbrand owners,â€ work with many independently operating external business partners, known as â€œchannel partners,â€ who market, sell, and/or service the brand owners' products. To have successful relationships with channel partners, a brand owner must be able to share information about the owner's products with its channel partners so that the partners may operate effectively on behalf of the brand owner.

For example, brand owners consider it very important to convey the current information about the brand owners' products to their channel partners. This includes campaign-related information about the brand owner's products, such as details about a soon-to-be released new product, upgrades of existing products, on-sale products, special promotions, etc. The campaign information may also include a description of the consumer group to whom the brand owner wants to target the campaign and the duration of the campaign. Having such campaign information helps the channel partner effectively direct its activities on behalf of the brand owner to the target consumer group.

Because brand owners consider campaign information to be highly sensitive, ensuring its security is important. Brand owners provide campaign information to only those channel partners eligible for such campaigns or for whom the information would be most relevant, while not providing the information to all other partners. Brand owners typically conduct several campaigns at once. As such, ensuring that the correct campaign information is provided to the correct channel partner is a nontrivial task.

Customer relationship management (CRM) solutions (such as mySAP CRM) are computer applications that allow brand owners to manage their channel partners by providing access to data and processes on the brand owner's CRM system, so that the channel partners may readily access product information. For those channel partners, a â€œpartner portalâ€ provides a user interface through which channel partners access the brand owner's CRM system from an external computer network.

However, in CRM systems, it has not been possible to designate certain partners to have access to certain campaign information. Because of this, brand owners have not been able to (a) model groups of authorized channel partners and (b) securely set up and maintain the authorizations.

There is a need in the art for a system and method for authorizing business information access.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a system diagram in accordance with an embodiment of the present invention.

FIG. 1B is a block diagram that depicts software components resident on a management server in accordance with an embodiment of the present invention.

FIGS. 2A through 2C are block diagrams that depict data structures associated with partner authorization groups in accordance with an embodiment of the present invention.

FIG. 3 is a flowchart of a method for creating partner authorization groups in accordance with an embodiment of the present invention.

FIG. 4 is a screenshot that depicts a segment builder screen as viewed by a brand owner from which the brand owner may create partner authorization groups made up of channel partners in accordance with an embodiment of the present invention.

FIG. 5 is a screenshot that depicts a marketing planner screen as viewed by a brand owner from which the brand owner may create a campaign and designate it as accessible to partner authorization groups in accordance with an embodiment of the present invention.

FIG. 6 is a screenshot that depicts a marketing planner screen as viewed by a brand owner from which the brand owner may link partner authorization groups to a campaign in accordance with an embodiment of the present invention.

FIG. 7 is a flowchart of a method for authorizing access to a campaign for channel partners belonging to the designated partner authorization group in accordance with an embodiment of the present invention.

FIG. 9 is a block diagram that depicts a computing device in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention increases the capabilities of customer relationship management applications by authorizing access by channel partners to relevant campaigns and associated information of a brand owner. The present invention does this by adding access functionality to an existing CRM application and applying this functionality to channel partner data.

In a CRM application, each business object such as an activity, a lead, an opportunity, etc., is assigned to a particular channel partner, thereby granting that partner access to the information associated with these objects. For example, channel partner A is assigned to handle lead X. Hence, channel partner A (but no other channel partners) is granted access to information regarding lead X by virtue of being assigned thereto. In an example of a CRM system, a tool called â€œsales partnerâ€ assigns a channel partner to a business object. A rule generator, e.g., an access control engine (ACE), then generates an access rule, which is executed when the partner logs into the CRM system to authorize access by the channel partner named by the â€œsales partnerâ€ tool to the business object information. The rule generator further allows access by one or more employee of the assigned channel partner.

In the case of campaigns, each campaign is typically assigned to multiple channel partners, rather than to a single one. While the above assignment idea is extendible to campaigns as business objects, the above-described tool would assign channel partners to campaigns, one partner at a time. This would be a time-consuming, laborious process for the brand owner. Therefore, a further extension of this idea to allow multiple channel partners to be assigned to a campaign, all at once, has been implemented in the present invention, which will be described below.

In a CRM system, campaign information has generally been set up for distribution to end customers, i.e., the purchasers of the brand owner's product, but not to channel partners. The end customers, however, receive campaign information from the brand owner, but can not access the brand owner's system for the information. In an example of a CRM system, a brand owner uses a tool called â€œmarketing plannerâ€ to create a campaign, which includes information about the new campaign to be launched. A brand owner uses a tool called â€œsegment builderâ€ to set up a â€œmarket segmentâ€ , which defines the type of customer to whom a campaign should be targeted. The brand owner inputs descriptive criteria about the target customer into the segment builder, which builds the market segment containing the criteria. The builder tool then generates the target group of end customers that meets those criteria to receive the campaign information. The marketing planner tool then links the target group with the campaign. The system sends all or portions of the campaign information to the end customers, in a broadcast email, for example. This operation of the CRM system is known.

The present invention extends this CRM application to meet the needs of channel management to define groups of channel partners to which campaign information should be distributed and adds functionality to authorize the channel partners to access the brand owner's CRM system to get the campaign information. In an example of a CRM system, the segment builder may be modified to define channel partner groups called partner authorization groups (PAGs). As with target groups of end customers, the brand owner may define a PAG of channel partners by inputting descriptive criteria about channel partners to whom the campaign information should be directed. Examples of descriptive criteria may include, but are not limited to, a partner type, a partner program, a partner status, duration of partner's relationship with brand owner, etc. For example, a partner type may be an â€œauthorized dealer,â€ a partner program may refer to a â€œplatinum partner,â€ a partner's status may be â€œactive,â€ and duration of partner's relationship with brand owner may be â€œsince 2003.â€

Suppose a brand owner wishes to send campaign information about the latest widgets to all channel partners who are active, authorized dealers of the brand owner's widgets. As such, the brand owner inputs â€œactiveâ€ and â€œauthorized dealer of widgetsâ€ as desired criteria of channel partners forming a PAG for this campaign. The segment builder then generates a PAG containing the channel partners who meet the criteria. The marketing planner designates a new campaign as accessible to PAGs, links the campaign to particular PAGs, and triggers the access control engine to generate access rules. The access control engine then generates access rules that authorize the PAG partners to access the campaign information on the brand owner's CRM system. It is possible to assign one or more PAGs to a campaign.

Alternatively, the brand owner may select particular channel partners to make up a PAG. The segment builder generates the PAG containing the selected channel partners. The marketing planner links the PAG to a campaign and triggers the access control engine. The access control engine then generates the access rules that authorize the PAG partners to access the campaign information.

This extended functionality allows the brand owner to assign multiple channel partners to a campaign all at once, thereby saving time and effort. Moreover, the brand owner may assign the channel partners to campaigns in the same way as the brand owner has assigned end customers to campaigns. Hence, the brand owner need not learn new tools. Additionally, the use of existing applications minimizes the developer's time and effort in adding this functionality.

When a channel partner logs onto the brand owner's CRM system, the access control engine executes the access rules that authorize the logged-in partner to access campaign information. The channel partner can access the designated campaign information, but not other campaign information. If a channel partner is not in a PAG associated with certain campaign information, the channel partner can not access the information at all.

Authorizing a channel partner to access campaign information on the brand owner's CRM system advantageously provides the channel partner with real-time information about the featured product, additional information that is not accessible in broadcast emails, individual channel partner information regarding the campaign, the partner's role in the campaign, e.g., individual sales targets, etc.

FIG. 1A is a diagram of a system for authorizing business information access in accordance with an embodiment of the present invention. In this embodiment, a channel partner may utilize partner client 100-1 or 100-2 to access campaign information on partner management server 110, which is operated by a brand owner. The brand owner may utilize owner client 120 to set up PAGs on partner management server 110. Server 110 may execute the applications to generate the PAGs from the brand owner's input, generate the access rules from the PAGs, and then authorize access by PAG partners to particular campaign information based on the access rules. Partner clients 100-1 and 100-2, owner client 120, and partner management server 110 may be connected via communication network 105.

It is to be understood that the system is not limited to that illustrated in FIG. 1A, but may include any client devices, server devices, and transmission media capable of providing embodiments of the present invention.

FIG. 1B is a block diagram that depicts software components that may reside on a management server in accordance with an embodiment of the present invention. Server 110 may include segment builder 112, which may receive descriptive criteria from the brand owner about the type of channel partner that should be authorized to access particular campaign information. Segment builder 112 may then search the channel partner information to find partners who match the criteria. Alternatively, segment builder 112 may receive a list of channel partners authorized to access the campaign information. Segment builder 112 may then generate partner authorization groups 220, including the determined channel partners.

Server 110 may also include marketing planner 113, which may receive campaign information from the brand owner and store campaign information 230 on server 110. Marketing planner 113 may link partner authorization groups 220 with corresponding campaign information 230. Linking provides access to all campaign information associated with the linked campaign, including subordinate campaign elements. Alternatively, marketing planner 113 may link partner authorization groups to particular campaign elements. Marketing planner 113 may also send some campaign information 230 out to partner authorization groups 220 via broadcast emails, for example.

Server 110 may also include access control engine 114, which may be triggered by marketing planner 113 to generate access rules 116. Access control engine 114 may then generate access rules 116 based on the linked campaign information 230 and partner authorization groups 220. Access control engine 114 may then store access rules 116 on server 110.

Access control engine 114 may act as a gatekeeper when a channel partner logs into the brand owner's CRM system. Upon notification of a partner's login, access control engine 114 may execute access rules 116 in which the logged-in partner is a member of a PAG. Access control engine 114 may then allow access to campaign information 230, as defined in the executed access rule.

Server 110 may also include a partner interface 118 through which a channel partner may log onto the brand owner's system and view campaign information 230.

In addition to campaign information 230, server 110 may also handle other types of marketing related information, e.g., trade promotions and deals, according to embodiments of the present invention.

FIGS. 2A-2C depict data structures that may be utilized in the implementation of partner authorization groups in accordance with an embodiment of the present invention. FIG. 2A illustrates a partner data structure (data structure 210), which may include partner information (data structure 215) that identifies the channel partner, e.g., the company name, address, telephone number, email address, employees, etc.

FIG. 2B illustrates a partner authorization group data structure (data structure 220), which may include partner data structures (210) of those channel partners to be assigned to one or more campaigns.

FIG. 2C illustrates a campaign data structure (data structure 225), which may include campaign information (data structure 230) that includes the name of the campaign, the target product, the time period of the campaign, etc. The campaign data structure (225) may also include PAG data structures (220), which identify the partners who are authorized to access campaign information represented by campaign data structure (225).

It is to be understood that the representation of the data is not limited to the data structures described herein, but may include any representation capable of storing and retrieving data.

A brand owner may input partner information (215) to server 110, which may store the partner information (215) into a database in partner (210). The brand owner may also input campaign information (230), which may be stored in the database in campaign (225). When the brand owner inputs partner descriptive criteria to server 110, the segment builder 112 may take the descriptive criteria and search partner information (215) for channel partners meeting the criteria. The segment builder 112 may then generate partner authorization group (220) with pointers to the group's partners (210). Marketing planner 113 may include pointers in campaign (225) to the generated partner authorization groups (220).

FIG. 3 is a flowchart of a method for creating partner authorization groups in accordance with an embodiment of the present invention. In this embodiment, server 110 may receive (305) a command to build a partner authorization group (PAG) from owner client 120. Server 110 may inquire (315) whether the channel partners to make up the PAG are chosen by description or by selection.

If the PAG is formed by description, server 110 may receive (320) descriptive criteria about the type of channel partner who should receive campaign information from owner client 120. Server 110 may determine (325) the channel partners who meet the criteria and then group the determined partners into a PAG.

If the PAG is formed by selection, server 110 may display (330) a list of all the brand owner's channel partners in the database on owner client 120. Server 110 may receive (335) the brand owner's selections on the list from owner client 120 and then group the selected partners into a PAG.

Server 110 may save (340) the PAG in the database. Server 110 may link (345) the PAG to one or more campaign stored in the database.

Server 110 may then execute a rule generator, e.g., the access control engine, and generate (350) access rules to indicate that the PAG partners are authorized to access campaign information. For example, partners X, Y, and Z form a PAG that has been authorized by a brand owner to access campaign A. Server 110 may generate the following access rule: Access to â€œCampaign Aâ€ if â€œPartner Xâ€ or â€œPartner Yâ€ or â€œPartner Z.â€

Server 110 may also authorize access to one or more employees of the channel partners that form the PAG. For example, any employee of partners X, Y, and Z that form a PAG has been authorized by a brand owner to access campaign A. Server 110 may generate the following access rule: Access to â€œCampaign Aâ€ if â€œemployee of Partner Xâ€ or â€œemployee of Partner Yâ€ or â€œemployee of Partner Z.â€ The partner information stored in the database would include an employee list of each partner to be read by the access rule upon authorizing access to the campaign information.

Server 110 may store (360) the generated access rules in its database for later use to authorize channel partner access.

Because the present invention extends an existing application to provide PAG functionality, the existing functions may also be used with the new PAGs. For example, the PAGs may be used as target groups for the brand owner to broadcast emails informing the PAG partners of a new campaign.

Similarly, the PAG functionality may be applied to other marketing related information, e.g., trade promotions and deals.

FIG. 4 is a screenshot that depicts a segment builder screen as viewed by a brand owner from which the brand owner may create PAGs made up of channel partners in accordance with an embodiment of the present invention. The brand owner may create a PAG using the segment builder tool. In this screen, the brand owner creates the PAG by selecting particular channel partners to form the PAG. The brand owner selects the â€œTarget Groupsâ€ tab to create a PAG. The brand owner then selects the â€œMembersâ€ tab to include channel partners in the PAG. To add partners to the PAG, the brand owner selects â€œAdd Entry.â€ To remove partners from the PAG, the brand owner selects â€œDelete Entry.â€

Alternatively, in FIG. 4, the brand owner may create the PAG by inputting descriptive criteria of the type of channel partner to receive the campaign information. To do so, the brand owner selects the â€œProfilesâ€ tab and inputs the criteria. The segment builder then models the PAG containing channel partners who meet the criteria.

FIG. 5 is a screenshot that depicts a marketing planner screen as viewed by a brand owner from which the brand owner may create a campaign and designate it as accessible to PAGs in accordance with an embodiment of the present invention. The screen shows a listing of the current campaigns in the brand owner's system. To create a new campaign, the brand owner selects the â€œCreate Subnodeâ€ button and inputs the required information regarding the campaign. Conversely, to delete a campaign, the brand owner selects the â€œDeleteâ€ button. The screen shows that campaign â€œ/-20040702-115803â€ has been created by the brand owner. The brand owner selects the â€œBasic Dataâ€ tab to enter and review the campaign information associated with this campaign. To permit access to the campaign by channel partners, the brand owner checks the box â€œOpen to Partners.â€

FIG. 6 is a screenshot that depicts a marketing planner screen as viewed by a brand owner in which the brand owner may link PAGs to a campaign in accordance with an embodiment of the present invention. The screen shows that campaign â€œ/20040702-115803â€ has been selected by the brand owner. To link PAGs to this campaign, the brand owner selects the â€œAuthorized Partnersâ€ tab and either enters the name of the PAG or selects the PAG from a search list using a function â€œvalue help.â€ The brand owner checks the â€œPublishedâ€ box associated with the PAG, thereby triggering the creation of access rules by the access control engine.

FIG. 7 is a flowchart of a method for authorizing access to a campaign for channel partners belonging to the designated PAG in accordance with an embodiment of the present invention. As a channel partner logs onto server 110 via partner client 100, server 110 may receive (705) a login notification. Server 110 may retrieve (710) the campaign access rules from its database. Server 110 may check (720) the name of the logged-in channel partner against the partners listed in the PAGs in the access rules.

If a match is found (725), server 110 may execute the matched access rule and grant (730) the logged-in partner access to the campaigns specified by the matched access rule. The channel partner may then review campaign information on the brand owner's CRM system. Server 110 may also check an employee list of a channel partner if the channel partner is listed in a PAG to determine whether the logged-in employee is listed as being authorized to access a campaign.

If a match is not found (725), server 110 may not allow the logged-in partner access to any campaign information, though the partner may view other business objects to which the partner has been assigned.

FIG. 8 is a screenshot that depicts a campaign screen as viewed by a channel partner that shows the campaign that the channel partner is authorized to access in accordance with an embodiment of the present invention. After logging onto the brand owner's system, the channel partner selects â€œCampaignsâ€ to view the campaigns the channel partner is authorized to see. The partner then selects â€œBasic Dataâ€ to view the campaign information.

FIG. 9 illustrates the components of a basic computing device in accordance with an embodiment of the present invention, which may include partner client 100, partner management server 110, and owner client 120. The computing device may be a personal computer, workstation, handheld personal digital assistant (â€œPDAâ€ ), or any other type of microprocessor-based device. The computing device may include one or more of processor 910, input device 920, output device 930, storage 940, and communication device 960.

Input device 920 may include a keyboard, mouse, pen-operated touch screen or monitor, voice-recognition device, or any other device that provides input. Output device 930 may include a monitor, printer, disk drive, speakers, or any other device that provides output.

Storage 940 may include volatile and nonvolatile data storage, including one or more electrical, magnetic or optical memories such as a RAM, cache, hard drive, CD-ROM drive, tape drive or removable storage disk. Communication device 960 may include a modem, network interface card, or any other device capable of transmitting and receiving signals over a network. The components of the computing device may be connected via an electrical bus or wirelessly.

Software 950, which may be stored in storage 940 and executed by processor 910, may include, for example, the application programming that embodies the functionality of the present invention (e.g., as embodied in mySAP CRM 5.0). Software 950 may include a combination of enterprise servers such as an application server and a database server.

Communication network 105 may include any type of interconnected communication system, which may implement any communications protocol, which may be secured by any security protocol. The corresponding network links may include telephone lines, DSL, cable networks, T1 or T3 lines, wireless network connections, or any other arrangement that implements the transmission and reception of network signals.

The computing device may implement any operating system, such as Windows or UNIX. Software 950 may be written in any programming language, such as ABAP, C, C++, lava or Visual Basic. In various embodiments, application software embodying the functionality of the present invention may be deployed on a standalone machine, in a client/server arrangement or through a Web browser as a Web-based application or Web service, for example.

Several embodiments of the invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention. For example, the data structures that implement the present invention can take many different forms yet still provide the same functionality.