Проблема разделения данных по компаниям в MSDax 2012

[EVGL]

Еще как имели практику.
Проекты в AX2012 разделены по компаниям, но могут просматриваться вместе.
Intercompany projects можно использовать в табелях (западных), командировочных (западных) и счетах на покупку: https://blogs.msdn.microsoft.com/bwe...012-r3-part-1/

Их нельзя использовать в заказах на продажу и покупку: покупка всегда формируется в компании, в которой сидит проект.

Виртуальные компании - это тупик: в AX7 их больше нет.

Финансовая аналитика, интегрированная с проектами, видна только в компании проекта. Поэтому сделали отдельную custom аналитику:

Цитата:

For every new project create a new unique dimension ProjectID and automatically assign it to the project.
* Every time a project record is created a new value must be generated for the dimension “Project ID”, Dimension value = Project id (as is), Description = Project name (as is). The description is not updated on project name changes, i.e. it is a one-time action. At that moment, this value should also be written back to the project record (ProjTable) and merged with the other existing dimensions.

 
There is no need to update this field in the Create project form while the user is typing in the project code, it only happens after clicking OK.
The Project ID should also be assigned in any scenario in AX where a project record is created, either manually (the “Create project” form) or automatically (from a project quotation in the wizard, for example). I.e. it must be triggered upon ProjTable.insert().
Should the assumption “5 Project IDs never intersect across companies” be broken for some reason (i.e. somebody is creating a project with a number already existing in another legal entity), this may not lead to an error in project creation. A new dimension record is not inserted, the value of the existing dimension is written into the project master record.
 
The dimension values are not deleted if the user decides to delete the project record, but they may be re-used as the system may re-use the project IDs. 
Project numbers / ID's are NOT deleted but will be "terminated" by the project end date. Every project ID that is no longer active (closed) should be "hidden" or no longer be usable for end-user input in time-sheets, expense reports, purchase orders or new invoices. However historical transactions in accounting still might use the project reference, e.g. Fixed Asset's amortizations, reversals from manual GL entries, etc.

Should accounting be in the need of a manual correction, they may manually temporarily remove the checkbox.

Цитата:

Существуют ли какие-либо баги в использовании Cross Company применимо к
Query, Selects

- Да. "Западные" табели (Project timesheets) не работают, если начать "виртуализировать" проекты. Если в коде встречается cross company, то в комбинации с виртуальными компаниями это перестает работать.