3 Business Operational View

3.1 Business Process Definition

Maintenance of account information includes such activities as updating ship-to and bill-to locations as well as updating relationships between ship-to and bill-to address. This Partner Interface Process (PIP) supports both customer and vendor account types. For an explanation of these account types, please refer to PIP1A1, "Request Account Setup."

Example

Assume that "ABC Distributor" purchases product from "Acme Manufacturer." If ABC Distributor decides to open a new warehouse, they would initiate this PIP to report the new warehouse location to Acme Manufacturer. Acme would update the customer account in their system with the new location and provide an acknowledgment back to ABC. Conversely, Acme may add a new address to which purchase orders should be sent. As a result, Acme would use this PIP to advise ABC of this new address. ABC would add the purchase order address to the vendor account and acknowledge the addition(s) back to Acme.

This PIP was also designed with the understanding that the Account Provider determines what, if any, of the updated account information is accepted and reflected in their system. Thus, referencing the example, ABC might report the new warehouse location and a new bill-to location to Acme. However, Acme must review the updates and decide which information to change in their system. If Acme finds that ABC's new bill-to location already exists in their system, then Acme would reject that portion of the request and notify ABC of the rejection. This PIP was designed to allow an Account Provider to accept part of a request and reject part of a request, so that the recipient could reject the bill-to, but accept the warehouse location within the same PIP.

3.2 PIP Purpose

The purpose of this PIP is to support a process whereby trading partner account information can be maintained.

3.3 PIP Business Process Flow Diagram

Figure 3.1. Maintain Account

3.4 PIP Start State

The start state is comprised of the following conditions.

• The account type is defined to be a Customer or a Vendor.

• The account has been setup.

3.5 PIP End States

End states are comprised of one or more conditions.

END

• Account Change Response received.

• One or more of the change requests applied.

• If any change was denied; a reason code for that denial is supplied.

FAILED

• The number of attempts has exceeded the retry count maximum.

• PIP0A1, "Notification of Failure," has been executed. (This is a RosettaNet convention.)

• Change requests not applied.

3.6 Partner Role Descriptions

Table 3.1 describes the partner roles in this PIP.

Table 3.1. Partner Role Descriptions

Role Name	Role Description	Role Type
Account User	Any trading partner that requires an account to buy or sell products/services.	Functional
Account Supplier	Any trading partner that buys or sells products/services from customer and/or vendors.	Organizational

3.7 Business Process Activity Controls

Table 3.2 describes the interaction contract between roles performing business activities in this PIP.

Table 3.2. Business Activity Descriptions

Role Name	Activity Name	Activity Description	Pre-Conditions	Post-Conditions
Account User	Request Account Change	This activity involves systematically reviewing the updated account information for completeness and validity and systemically updating the account information in an account provider's system. The activity then informs an account requester which account information was updated and which was invalid.	The account type to be changed is defined as a Customer or a Vendor.	Success or failure of the account change is received. If any change was denied; a reason code for that denial is supplied.

Table 3.3 details the security, audit and process controls relating to activities performed in the PIP.

Table 3.3. Business Activity Performance Controls

Role Name	Activity Name	Acknowledgment of Receipt			Time to Perform	Retry Count	Is Authorization Required?	Non-Repudiation of Origin and Content?
		Non-Repudiation Required?	Time to Acknowledge	Time to Acknowledge Acceptance
Buyer	Request Account Change	Y	2 hrs	N/A	24 hrs	3	Y	Y

3.8 PIP Blueprint Data

3.8.1 PIP Business Documents

Business Documents listed in Table 3.4 are exchanged by roles performing activities in this PIP. The Business Documents can be downloaded from the RosettaNet Business Document Repository using the Uniform Resource Locator (URL) specified Section 1.6, "Related Documents."

Table 3.4. PIP Business Documents

Business Document	Description
Account Change Request	Specifies change(s) for a particular account
Account Change Response	Contains the result of the requested change(s). A reason code is provided if a change is denied.

3.8.2 Business Data Entities

The business data entities, fundamental business data entities, and global identifying properties can be found in the RosettaNet Business Dictionary using the URL specified in Section "Related Documents."

Business Data Entity Security

There are no security controls specified for this PIP.