-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BT-14 in CII -> BT-13 in UBL check #23
Comments
I went deeper into this matter and could narrow down the "bug" to class OrderReferenceType of ph-ubl21-9.0.1. It seems, that @XmlElement(name = "ID", namespace = "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2", required = true)
private IDType id; Then I looked into the scheme and the syntax binding and Maybe filling it with a placeholder can be a workaround, but it would change the invoice a little bit. |
I've implemented the workaround in // OrderReference
{
final OrderReferenceType aUBLOrderRef = _createUBLOrderRef (aHeaderAgreement.getBuyerOrderReferencedDocument (),
aHeaderAgreement.getSellerOrderReferencedDocument ());
/* Set BT-13 with a hyhen if it is empty */
if(aUBLOrderRef != null)
{
if(aUBLOrderRef.getIDValue().equals(""))
{
aUBLOrderRef.setID("-");
}
}
aUBLInvoice.setOrderReference (aUBLOrderRef);
} |
@lkumai I checked the existing code, and that branch is already contained. |
The problem is not just, that it is required, but also that it must not be empty.
|
Is part of the upcoming v2.2.2 release |
It seems, that if there exists BT-14 in CII, BT-13 will be generated, even if it not exists
The text was updated successfully, but these errors were encountered: