# Create or Update Batch EDICodeMap

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

Endpoint: PUT /edi-code-mapping-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

  - `ediCodeMap_Key` (integer, required)
    Key value that identifies the EDI code map Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `destination_Value` (string, required)
    Value that is assigned at the destination when the source value is encountered

  - `direction` (string, required)
    Specifies the direction of the EDI transfer - import or export

  - `effective_Date` (string,null)
    Optional date when the EDI code map condition becomes effective

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

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

  - `map_Type` (string, required)
    Type of map that is being used for the EDI transfer

  - `map_Variable1` (string,null)
    Variable associated with the EDI code map

  - `map_Variable2` (string,null)
    Variable associated with the EDI code map

  - `map_Variable3` (string,null)
    Variable associated with the EDI code map

  - `map_Variable4` (string,null)
    Variable associated with the EDI code map

  - `map_Variable5` (string,null)
    Variable associated with the EDI code map

  - `source_Value` (string, required)
    Value specified by the source that needs to be mapped

  - `term_Date` (string,null)
    Optional date when the EDI code map condition terminates

  - `trading_Partner_Key` (integer,null)
    Kev value that identifies the EDI trading partner or vendor

  - `update_Date` (string)
    Date 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` (string,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