Type: New Feature
Component/s: Documents and business objects
Agreed at the conference calls on July 17 to add a repeatable Sub Status to the status:Agreed at the conference calls on July 17 to add a repeatable Sub Status to the status: <cac:Status> <cbc:StatusReasonCode listID= "RMStatusReason" > LEG </cbc:StatusReasonCode> <cbc:StatusReason> Legal issue </cbc:StatusReason> <cac:SubStatus> <cbc:StatusReasonCode listID= "RMStatusClarification" > VAT1 </cbc:StatusClarificationCode> <cbc:StatusReason> No VAT reference </cbc:Description> </cac:SubStatus> <cac:Condition> <cbc:AttributeID schemeID= "RMFieldValue" > BT-48 </cbc:AttributeID> <cbc:Description> EU123456789 </cbc:Description> </cac:Condition> </cac:Status> https://lists.oasis-open.org/archives/ubl/201907/msg00018.html
EESPA reports that it is sometimes necessary to provide additional information to clarify a Status Reason Code / Status Reason in an application response. For example:
Status reason: Legal issue
Status clarification: VAT reference is required
There may be several clarifications for a status reason, why simply providing more elaborate code lists for status reason codes is not sufficient. The Condition ASBIE is already being used to provide detailed information about required and/or missing elements and values, why the reporter doesn't find that it can fulfill their requirement.