# Create or Update Batch GroupPlanYear

Create or Update multiple GroupPlanYear at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /groups/{groupID}/divisions/{divisionID}/plan-years-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Path parameters:

  - `groupID` (string, required)
    Group ID

  - `divisionID` (string, required)
    Division ID

## Request fields (application/json):

  - `group_ID` (string, required)
    References GroupDivision.Group_ID value on the parent record.

  - `division_ID` (string, required)
    References GroupDivision.Division_ID value on the parent record.

  - `plan_Year` (string, required)
    User defined Plan Year value for this accumulator period. Should denote the values in From_Date and Thru_Date. Example: Plan Year "CY2009" would be 1/1/2009 - 12/31/2009.

  - `entry_Date` (string)
    Date when the record was first added to the system.

  - `entry_User` (string,null)
    User that first added the record to the system.

  - `ex_Code` (string,null)
    If an Ex_Code should be applied when a claim is identified for carry over, place that here.

  - `from_Date` (string,null)
    The date range for this Plan Year.

  - `plan_Type` (string,null)
    If this Plan Year is specific to a Plan Type, you would denote that here. Normally no value is set for standard accumulation.

  - `qtr4_Accum` (boolean, required)
    Indicates if this Plan Year has 4th quarter carry-over. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `qtr4_Benefit_Code` (string,null)
    When accumulators are carried over they are bucketed into a single Benefit Code (typically a shell Benefit Code to catch the carry-over dollars).

  - `qtr4_Deductible` (boolean, required)
    Indicates if carry-over applies to Deductible. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `qtr4_From_Date` (string,null)
    If this Plan Year has 4th quarter carrry-over, this would indiate the dates, inside From_Date and Thru_Date, that signify the 4th quarter carry-over period.

  - `qtr4_Member` (boolean, required)
    Indicates if the carry-over applies to Member level accumulators. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `qtr4_Out_Of_Pocket` (boolean, required)
    Indicates if carry-over applies to Out of Pocket. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `qtr4_Out_Of_Pocket_Type` (string,null)
    If Out of Pocket carry-over is flagged, this identifies what constitutes Out of Pocket (Deductible, Co-Ins, Co-Pay).

  - `qtr4_PlanYear` (string,null)
    Indicates which Plan Year these carry-over accumulators will carry over to (typically a plan year on the other side of the carry-over period).

  - `qtr4_Subscriber` (boolean, required)
    Indicates if the carry-over applies to the entire Family for accumulators. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `qtr4_Thru_Date` (string,null)
    If this Plan Year has 4th quarter carrry-over, this would indiate the dates, inside From_Date and Thru_Date, that signify the 4th quarter carry-over period.

  - `thru_Date` (string,null)
    The date range for this Plan Year.

  - `update_Date` (string)
    Date when the record was last updated in the system.

  - `update_User` (string,null)
    User that last updated the record in the system.

## Response 207 fields (text/plain):

  - `data` (array,null)

  - `data.id` (array, required)
    List of key/value pairs that represent the unique id for the entity operation.

  - `data.id.key` (string,null)

  - `data.id.value` (any,null)

  - `data.status` (integer, required)
    http status of the operation (eg, 200, 201, 500)

  - `data.body` (string, required)
    operation message (eg, Updated, Created, Error message)

  - `error` (object)

  - `error.detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string,null)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string,null)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)


## Response 401 fields