Create manufacturing lot
post
/ec-ors-svc/rest/v3.0/studies/{studyId}/{mode}/lots/manufacturing-lots
Creates a manufacturing lot. Rights: LotManagementPost.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training
-
studyId(required): string(uuid)
ID of the study
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest object for lot.
Show Source
-
doNotCount: number
(BigDecimal)
Minimum Value:
0Maximum Value:999Do not count(DNC) daysExample:10 -
doNotShip: number
(BigDecimal)
Minimum Value:
0Maximum Value:999Do not ship(DNS) daysExample:10 -
expirationDate(required): string
Pattern:
(\d){4}-(\d){2}-(\d){2}Expiration date -
kitTypeSrcId: string
(uuid)
kitType SrcId
-
lotNumber: string
Minimum Length:
0Maximum Length:50Lot number -
manufacturingLotNumber(required): string
Minimum Length:
0Maximum Length:50Manufacturing lot number -
materialId: string
(String)
Minimum Length:
0Maximum Length:255materialIdExample:1234 -
quantity: number
(BigDecimal)
Minimum Value:
1QuantityExample:10 -
updateKitTypeId: boolean
update KitTypeIdExample:
true -
updateMaterialId: boolean
update MaterialIdExample:
true
Response
Supported Media Types
- application/json
200 Response
Successful operation
400 Response
Invalid expiration date. OR Manufacturing Lot Number already exists or Lot short name (lotNumber) already exists.
Root Schema : ORSResponse
Type:
objectCommon response object.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult Object
403 Response
The study identifier does not match any study identifiers in Clinical One
Root Schema : ORSResponse
Type:
objectCommon response object.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult Object
500 Response
Internal server error
Root Schema : ORSResponse
Type:
objectCommon response object.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult Object