especially for 'BuyerTradeParty' and 'ShipToTradeParty' right now.
Since EN16931 allows only one ID entry for these entries, the ID assigned
by the buyer is prefered over the global ID for now if bot are defined in
the IZUGFeRDExportableTradeParty object.
and if necessary corresponding methods in the IZUGFeRDExportable... interface
objects of Transaction, Item and Product:
Properties with new methods:
- SubjectNote for 'ExchangedDocument.IncludedNote' (human readable
document subject)
- RebateAgreementExists for 'ExchangedDocument.IncludedNote'
(Note that there are rebate agreements)
- BasisQuantity (number of item units per price)
- SellerAssignedID (seller identification of product)
- BuyerAssignedID (buyer identification of product)
- TaxExemptionReason (explanatory statement why no tax gets applied)
enhancement to support other exemptions than "IC-supply"
Properties for existing methods that did not get written to the XML
up to now:
- SellerTradeParty.ID (buyer assigned ID of seller)
- SellerTradeParty.GlobalID of seller (e.g. DUNS)
- BuyerOrderReferencedDocumentID (order number of buyer)
The generated file is named "testout-ZF2new.pdf" not "testout-ZF2New.pdf"
which will make the test fail on case sensitive file systems as can be
found on many unix like systems.
so test for 'payment' being an instance of 'IZUGFeRDTradeSettlementDebit' as
'IZUGFeRDTradeSettlement' and 'IZUGFeRDTradeSettlementPayment' return 'null' for
'getPaymentXML()' which is not allowed to be written to the XML file.
or a NullPointerException might happen as 'hasDueDate==true' is not the result
of a test to ensure that 'trans' overwrites 'getDueDate()' at all, so the default
implementation from 'IZUGFeRDExportableTransaction' might get used which returns
the unusable result 'null'.
