This special class of service request supports the ability for a user to request online access to multiple tax accounts and to perform various self-service operations.
One enrollment request is created per line of business.
This is a special kind of a service request that defines its own web service, TSEnrollmentServiceRequest. The web service requesting the enrollment is processed by the XAI Inbound Service, which invokes the service script C1-EnrSvcReq. The appropriate service task type to use must be passed in with the other information received from the self service system.
The integration has the following steps:
The self service application captures information about the taxpayer that is sufficient to identify tax accounts related to this taxpayer within the context of a specific line of business.
The integration layer generates two unique IDs: Confirmation ID, which will be later presented to the self-service user, and Enrollment ID, which will be used internally between SOA/BPEL layer and the revenue management system.
This information is sent to the system, which creates an Enrollment Request service task.
The task's lifecycle is designed to process the information immediately, with no deferred monitor process, so that the information can be returned to the self service application in real-time.
The base business object for the Enrollment Request Service Task includes an algorithm, C1-ENR-INIT, that reads enrollment service task type configurations and orchestrates the process. It invokes access type-specific logic to verify the taxpayer identity, determine what data this user should be able to access and manage, and populate the results on the response message. The response message contains the list of tax account identifiers (access type+access keys). Each entry also includes the enrollment status, revenue management system, and enrollment ID.
The response is sent back to the self-service application immediately.
Enrollment entries are processed by SOA Composite in the integration layer. They are captured in the user access store table.
The final response to the self-service application contains confirmation details.
Note that the implementation of the enrollment request creates a service task for the following reasons:
The creation of a service task with its business object architecture provides many plug-in spots to allow implementations to easily customize the initial enrollment logic.
The service task type provides a facility for the various configurations related to enrollment handling.
The enrollment request service task provides an audit tracking for the enrollment activities and is linked to the unique enrollment ID which is shared between the revenue management system(s) and the self service product. It also allows tracking of failed enrollments attempts.
The enrollment request service task captures the initial list of tax accounts and provides future reference for the implicit enrollment refresh.
Creating a service task enables the tax authority to provide the taxpayer with a confirmation ID for possible follow-up . If the taxpayer contacts the tax authority and provides the confirmation ID, the user can view the service task, verify the details, and more easily investigate the situation.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]