The supply chain package for the HQUS legal entity is split into packages that are named 300-Supply chain 1 of 2-HQUS.zip and 300-Supply chain 2 of 2-HQUS.zip. For example, the Supply chain data package for the PICH legal entity is named 300-Supply chain-PICH.zip. These names of these data packages consist of 300-Supply chain followed by the legal entity that the packages are intended for. However, you can load these packages as two separate projects.
You must load both packages to complete the supply chain scenarios. Because of the large number of entities, the Supply chain packages for some companies have been split into two packages. The Supply chain data packages contain data for inventory management, product information, procurement and sourcing, sales and marketing, quality management, warehouse management, transportation management, production control, process manufacturing, costing, and master planning for a single company. For example, the Project management and accounting data package for the HQUS legal entity is named 250-Project management and accounting-HQUS.zip. The names of these data packages consist of 250-Project management and accounting followed by the legal entity that the packages are intended for. The Project management and accounting data packages contain data for project accounting and expense management. For example, the Expense management data package for the HQUS legal entity is named 225-Expense management HQUS.zip. The names of these data packages consist of 225-Expense followed by the legal entity that the packages are intended for. The expense management data packages contain data for expense management and aren't specific to project management. More complete products will be added when you import the Supply chain data packages. However, you no longer have to set up products when you want to demonstrate only Financials functionality. These items use a minimum of inventory and product functionality to support those processes. The Financials data packages also have five inventory products to support the creation of invoices that can move through the accounts receivable and accounts payable processes. The CONS legal entity is required if you want to do consolidations. To facilitate cross-company tasks, all customers and vendors have been added to each legal entity. For example, the Financials data package for the HQUS legal entity is named 200-Financials-HQUS.zip.Īt least two financial companies are required for cross-company tasks such as centralized payments. The names of these data packages consist of 200-Financials followed by the legal entity that the packages are intended for. The Financials data packages contain data for the general ledger, bank, accounts payable, tax, accounts receivable, fixed assets, and budgeting for a single company. It includes setup information that is intended for non-US companies.Ī process industries company that is focused on chemicals.Ī process industries company that is focused on food and beverages.
This company is based on the original DEMF data, but it has been changed to remove the manufacturing focus in the name. The non-US-based headquarters for your demo company. It includes setup information that is intended for US companies. This company is based on the original USMF data, but it has been changed to remove the manufacturing focus in the name. The US-based headquarters for your demo company. The package is named 100-System and Shared.zip.Īfter the System and Shared package is loaded, you will see one or more of the following legal entities. It must be loaded first to support all the remaining packages. This package creates legal entities, loads the global address book, and adds other shared information.
The base package, System and Shared, is the foundation for all other packages. In this case, a separate global information package will be created, and only packages that are related to that global information can be layered on top of the package.įor example, there is currently a commercial system and shared package as well as a separate public sector system and shared package that can't be used together. For example, the dimensions for one scenario will interfere with the dimensions for another scenario. However, the global information for one demo scenario might have completely different requirements than the global information for another demo scenario. The demo data packages are designed to be layered on top of each other, as shown in the following illustration.
#DATA GENERATOR FULL#
The demo data packages aren't yet a full replacement for the demo database that is currently provided.
0 kommentar(er)
