Customer Registration

Until now, you were able to create person and account from the different screens. Now, ORMB provides the ability to create a person and multiple accounts for the person from the same user interface. A new object named Customer Registration is introduced in this release. Through a customer registration object, you can create person, accounts and contracts at the same time from the same interface. Before creating a customer registration object, you need to create the following:

• Customer Registration Template - A customer registration template encapsulates the following information:

• List of pages that should appear when you create a person or account using the respective customer registration template

• List of sections that should appear in each page

• Field or characteristic attributes, such as:

  • Default value for a field or characteristic type

  • Default value for a person or account identifier type or phone type

  • Primary identifier type for a person or account

  • Mandatory field in each section

  • Enable or disable the field value, identifier type, identifier value, characteristic type, characteristic value, phone type, or phone number

You can create multiple customer registration templates for person and account. Depending on whether you are creating a customer registration template for person or account, you can include the following pages and define field or characteristic attributes for the following sections:

• Customer Registration Type - A customer registration type encapsulates the following information:

  • Users with a particular access group can only create a customer registration object using the customer registration type.

  • Whether the customer registration type can be used to create a customer registration object from the user interface, through the inbound message, or through the File Upload Interface utility.

  • Whether the approval is required when you create, edit, or delete a customer registration object.

  • The business objects using which the person, account, and address should be created when a customer registration object is created using the customer registration type.

  • A customer registration template which indicates the pages and sections that should appear when you are creating a customer registration object using the customer registration type. You can specify one customer registration template for person and one or more customer registration templates for account.

• Information, such as person names, person identifiers, person phones, person characteristics, person addresses, person hierarchy, accounts, account identifiers, account characteristics, account auto pay information, account persons, account bill routing information, or credit rating history, which should be copied when you create a copy of a customer registration object which is created using the customer registration type.

While creating a customer registration object, you need to specify the following:

• A customer registration type using which the customer registration object should be created

• A source system from the customer information is received

• A type of person that you want to create through the customer registration object

Once you specify the above details, the Customer Registration screen appears with a set of pages and sections which are added in the respective person template. The default values for the fields, characteristic types, identifier types, and phone types are shown as specified in the person template. In addition, the field values, characteristic types, characteristic values, identifier types, identifier values, phone types, and phone numbers are disabled as specified in the person template. On the Accounts page, you can view one row for each account template which is added in the customer registration type. You can then edit the row and thereby create an account for the person. You can create multiple accounts for the person using the same or different template.

Note: The system creates effective dated address using the address business object which is specified in the customer registration type. By default, the account override address is effective from the date when the customer registration object is created in the system.

On clicking the View/Edit icon or the Add New Account button, the Customer Registration - Add Account screen appears with a set of pages and sections which are added in the respective account template. The default values for the fields, characteristic types, and identifier types are shown as specified in the account template. In addition, the field values, characteristic types, characteristic values, identifier types, and identifier values are disabled as specified in the account template.

You can save the person and account details as and when you are entering the data by clicking the Save as Draft button. On clicking the Save as Draft button, the system creates a customer registration object in the Draft status. Once all person and account details are specified, you can click the Validate and Save button. The system then validates the information. You can edit, delete, or submit a customer registration object when it is in the Draft status. On submitting a customer registration object, the person and accounts are created in the system. If an algorithm created using the C1-CRECONT algorithm type is attached to the Post-Processing system event of the account business object (which is specified in the customer registration type), the system creates the contracts for each account. Finally, the status of the customer registration object is changed to Complete.

You can optionally configure the approval process for the customer registration. If the Approval Required option is selected in the customer registration type, the status of the customer registration object is changed to Approval In Progress on submitting it. A To Do using the approval To Do type is created and assigned to the users with the approval To Do role. The approver can then review the customer registration object and accordingly approve, reject, or request the submitter to resubmit the customer registration object for approval. On approving a customer registration object, the person, accounts, and contracts (if the required algorithm is attached) are created in the system. Finally, the status of the customer registration object is changed to Complete.

If the approver rejects a customer registration object due to some reason, the status of the customer registration object is changed to Rejected. However, if the approver requests the submitter to resubmit a customer registration object for approval after making the required changes, the status of the customer registration object is changed to Draft. The submitter can then make the required changes and resubmit the customer registration object for approval.

Note: The system enables you to create maximum 10 accounts for a person through a customer registration object from the user interface.

You can also create a customer registration object using the File Upload Interface utility. On creating a customer registration object using the File Upload Interface utility, the status of the customer registration object is set to Draft. You can then submit the customer registration object manually from the user interface. Note that, at present, only the XML format is supported for creating a customer registration object using the File Upload Interface utility.

To implement the Customer Registration feature, the following new screens are introduced in this release:

• Customer Registration Template

• Customer Registration Type

• Customer Registration

Related Topics

Parent Topic: Oracle Revenue Management and Billing Financial Services Business Processes