Boštjan Golob

When transporting different kinds of loose goods or liquids/gasses, there may be a difference between the loaded quantity on the truck and the delivered quantity, because of losses during transport (leakage/spillage, change in temperature, imprecise unloading if truck has several stops...).

In this case, you can try modelling the truck as a mobile warehouse only post packing slips when actual delivery quantities are known, but this can be cumbersome. I propose an additional document on the sales order, linked to a packing slip, called "proof of delivery" (POD). If POD invoicing were active for a sales line, only the quantities confirmed for receipt would be subject to invoicing, the difference between the picked/delivered quantity and total received/actually delivered quantity would need to be "sold" as a cost.

If you want to use a single warehouse for multiple companies, you need to be able to transfer all the inbound/outbound documents from these companies - it could just be intercompany within one Operations instance, or a company using a different ERP system altogether. For this purpose, sales and purchase orders may be overkill, since they are rather "heavy", and more importantly, have financial impact which is not needed in this case.

To address this use case, I propose a pair of inbound/outbound documents ("warehouse input"/"warehouse output"?) that would be enabled for all warehouse functions, but would not have any customer/vendor (maybe just a link to a global address book or even just an address directly) and no financial impact at posting or on the stock itself.

Currently, Country/Region context works only by fixing a comma separated list of countries in which a feature is enabled. In code, the same is true for the container of strings when checking if a legal entitiy is in a country/region.

I propose an extension of the simple list of countries to a "legislation". A "legislation" is a platform managed list of countries which can be added to a country/region property as. It could be managed as a metadata artifact and deployed, with an extension capability to add more countries in the future, or as a pure runtime feature. "Legislation" should have a unique string, longer than 2 characters not to collide with ISO country/region codes, or be prefixed with a non-alpha character, e.g. "+".

For example, features common to the European Union, such as VAT features, Intrastat reporting and so on, could be marked in metadata with a "legislation" +EU. Similarly, in code, checks could be rewritten from isLegalEntityInCountryRegion with a long list of countries to a short container of only "+EU". 

Given that functions that are enabled for more than one country generally fall into a couple of broad categories:

• are actually there because of some super-national legislation (EU, EEU, SEPA, NAFTA, Mercosur/Mercosul...)
• are not really localization features, just features developed by a localization team (used to be payment calendars, also configurable text descriptions, withholding tax per invoice line...)
• features that exists because several countries used to be one or had some other common historical influence

it would be beneficial to be able to add new countries to at least two of the above groups of features.