Common Errors returned by Business Central, their meanings, and possible remedies
This article provides a list of the common errors that we've seen returned by Business Central when MV2 transactional data is written to Business Central. The article is broken up into sections based on the method used to update Business Central, with the details of each error message under that section.
Most, if not all errors, must be resolved by the customer in Business Central, and then MV2 must be updated to indicate that the processing of transactions should resume.
Failure in BC Posting Process
StatusCode: 400 - Bad Request
Message: Quantity (Base) available must not be less than X in Bin Content Location Code='XXX'...
Meaning: Not enough inventory to backflush Item No from Location/Bin Code.
Complete example message:
Response Body: {"error":{"code":"Internal_ServerError","message":"Quantity (Base) available must not be less than 8 in Bin Content Location Code='MKE', Bin Code='WC00120', Item No.='128717', Variant Code='', Unit of Measure Code='EA'. CorrelationId: 08f95230-b700-48b0-9964-c95a57eedd59."}}
StatusCode: 404 - Not Found
Message: The Bin Content does not exist. Identification fields and values...
Meaning:No inventory to backflush Item No from Location/Bin Code.
Complete example message:
Response Body: {"error":{"code":"Internal_RecordNotFound","message":"The Bin Content does not exist. Identification fields and values: Location Code='MKE', Bin Code='WC00145', Item No.='140153', Variant Code='', Unit of Measure Code='EA' CorrelationId: d68f9688-16b2-44f0-89a5-a1e2c00ac0f2."}}
StatusCode: 400 - Bad Request
Message: You cannot finish line 10000 on Production Order RPO-440248. It has consumption or capacity posted with no output
Meaning: Trying to convert Production Order to finished without reporting any Production Receipt.
Complete example message:
Response Body: {"error":{"code":"Application_DialogException","message":"You cannot finish line 10000 on Production Order RPO-440248. It has consumption or capacity posted with no output. CorrelationId: 992a653a-903d-4185-9b20-5e52f1efde00."}}
Failure in INSERT
Message: Exception: Stream was not readable. Exception type: System.ArgumentException.
Meaning: Typically a journal field validation error, commonly Production Order not found (as it has been Finished). This is the ONE error where no data will be in the BC Journal Batch.
Additional Errors
StatusCode: 400 - Bad Request
Message: The Released Production Order RPO-440855 cannot be found
Meaning: Failure to convert Production Order to finished, cannot be found in Released (as it has already been Finished).
Complete example message:
Response Body: {"error":{"code":"Application_DialogException","message":"The Released Production Order RPO-440855 cannot be found. CorrelationId: 549e3fff-c749-47b7-9f95-b0e69c712401."}}
StatusCode: 404 - Not Found
Message: The Prod. Order Routing Line does not exist. Identification fields...
Meaning: Cannot find Operation No. in BC for Order No.
Complete example message:
Response Body: {"error":{"code":"Internal_RecordNotFound","message":"The Prod. Order Routing Line does not exist. Identification fields and values: Status='Released', Prod. Order No.='RPO-440428', Routing Reference No.='10000', Routing No.='148575', Operation No.='10' CorrelationId: a98d2f17-f166-430c-bfa6-7dd29ef949d9."}}
StatusCode: 409 - Conflict
Message: The activity was deadlocked with another user who was modifying the G/L Entry table. Please retry the activity.
Meaning: Previous BC Posting has record lock, should be at attempt #4.
Complete example message:
Response Body: {"error":{"code":"Internal_ServerError","message":"The activity was deadlocked with another user who was modifying the G/L Entry table. Please retry the activity. CorrelationId: 1dab724c-48f8-4e2e-a26c-a0b6c0049ca5."}}
General Errors
Message: One or more errors occurred. A task was canceled.
Meaning: Not enough inventory to backflush for one Serialized Item No.