Before you Begin
In this business scenario, the Prototype company utilizes the Data Intake feature to reconcile bills of enrolled clients in a group policy. The OIPA application is hosted on a TomEE server, and the necessary parameters are input into Apache JMeter. Apache JMeter is utilized to execute a task of inserting records into a Payment Prototype profile in OIPA. The records are inserted into the data intake profile based on an XML schema. These records correspond to the bill reconciliation of enrolled clients who were added as members to a child class based on the membership rules.
Note:
This use case may differ from your actual requirements. This is written to help understand the steps to implement a group customer in OIPA. To follow steps in this use case, it is recommended that the default Prototype company is available in your environment.Scenario
In this business scenario, we are using the Prototype company and we are using the Prototype company default configuration.
Prerequisites
- You must have the required clients enrolled in a group policy. To enroll clients, please refer to the Group Customer – Enrollment tutorial.
- XML schema to add records in Apache JMeter.
- Apache JMeter should be up and running.
Step 1: Activate the Group Policy
To activate the group policy, follow these steps:
- On the Policy screen, in the Left Navigation list, click Activities. The Activate activity appears in Pending state.
- Click the
Process icon. The activity is processed, and the policy status is changed to Active.
Group Policy
Step 2: Process GenerateBillDetail Activity
To process the GenerateBillDetail activity, follow these steps:
- On the Activities screen, click +. The Add Activity page appears.
- Select GenerateBillDetail in the Select Activity drop-down.
- Enter the required details and then, click OK. The GenerateBillDetail activity page is added in the Pending state.
- Click the
Process icon. The activity is processed.
Group Policy
Step 3: Process the GenerateBill Activity
To process the GenerateBill activity, follow these steps:
- On the Group Customer screen, in the Left Navigation list, click Activities. The Activities screen appears.
- Click +. The Add Activity page appears.
- Select GenerateBill activity in the Select Activity drop-down.
- Enter the required details and then, click OK. The activity is added on the Activities page.
- Click the
Process icon. The activity is processed.
- Go to the Activity details page, and then click the Billing tab.
- Note the Bill Reference ID.
Bill Reference ID in GenerateBill Activity Details
Step 4: Create the Data Intake Profile
To add an intake profile, follow these steps:
- On the Group Customer screen, in Left Navigation list, click Data Intake, the Data Intake screen appears.
- In the Add Intake Profiles drop-down, select Payment Prototype and click the Create icon. The Payment Prototype window appears.
- Enter TaxId in the Record Member ID Field.
- Select Client Field in the Record Member ID Field Type drop-down box.
- Click Save. The Data Intake profile is created.
Before you run the Data Intake job from Apache JMeter, please activate the data intake profile.
To activate a data intake profile, follow these steps:
- On the Data Intake screen, click the (hyperlink) for the required data intake profile. The profile detail appears.
- Click the Activate button. The profile is updated to the Active status.
Data Intake - Payment Profile
Step 5: Configure User Parameters in Apache JMeter
To configure user parameters, follow these steps:
- Double-click ApacheJMeter.jar file. The Apache JMeter opens.
- Navigate to File > Open, select the required .jmx file and then click Open.
- In the left pane, expand the nodes and click User Parameters. The User Parameters page appears.
- On the User Parameters page, enter the parameters. The following table describes the parameters.
Parameters Description myuuid Specifies the universally unique identifier. It is generated by the system. Please enter ${__UUID} for this parameter. GroupCustomer Specifies the Group Customer Number. For example, GC2003. expectedRecordCount Specifies the number of records to be entered in the Data Intake profile. For example, 1. Maxprocessorder Enter any integer which is atleast one less than expectedRecordCount. For example, 0. ProviderURL Specifies the URL of the machine where the application is hosted. For example, tcp://fsgbu-mum-748.snbomprshared1.gbucdsint02bom.oraclevcn.com:61616 ChildClassGroup Specifies the child class name. For example, Orphans. ProfileName Specifies the data intake profile name. For example, DataIntakeCorp. TaxID Specifies the Tax ID of the first record. For example, 294851898. EntityType Specifies the entity type for the bill reconciliation. For example, Policy. PolicyNumber Specifies the policy number of the group policy. For example, 20068943. CoverageName Specifies the Plan Segment name. For example, BaseCoverageBasic. Amount Specifies the amount to be reconciled. For example, 999. ReferenceNo Specifies the Bill Reference ID. For example 4429. - In the Left Pane, under the Loop Controller node, click Counter-taxid. The Counter screen appears.
- Enter the Starting Value. Ensure that this value is same as TaxID above.
User Parameters Counter Tax ID
Step 6: Enter the required XML under addRecord

Step 7: Run the Job
To run the job, on the Apache JMeter, click .

Observations
Records are added in the Data Intake Profile
To view records under the data intake profile, follow these steps:
- On the Group Customer screen, in the Left Navigation list, click the Data Intake. By default, the Profiles tab appears.
- Click the Files tab. The Intake File Search Criteria appears.
- Select the required filters and click Find. The Intake File Search Results appear.
- Hover over the Ellipsis icon under the Action column of the required row.
- Click Show Records. The records added under the data profile are displayed.
Records
The Reconciliation activity is added in the group policy

Click the Process icon, the activity is processed. On the successful processing, the bill is reconciled.

Group Customer - Payment
F89508-01
November 2023
Copyright © 2021, 2023, Oracle and/or its affiliates.
How to reconcile bills for group policy members using data intake.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.