Cost accounting – Financial dimensions

This topic explains the various types of financial dimensions and how they are set up.

Use the Financial dimensions page to create financial dimensions that you can use as account segments for charts of accounts. There are two types of financial dimensions: custom dimensions and entity-backed dimensions. Custom dimensions are shared across legal entities, and the values are entered and maintained by users. For entity-backed dimensions, the values are defined somewhere else in the system, such as in Customers or Stores entities. Some entity-backed dimensions are shared across legal entities, whereas other entity-backed dimensions are company-specific.

After you’ve created the financial dimensions, use the Financial dimension values page to assign additional properties to each financial dimension.

You can use financial dimensions to represent legal entities. You don’t have to create the legal entities in Dynamics 365 Finance. However, financial dimensions aren’t designed to address the operational or business requirements of legal entities. The interunit accounting functionality in Finance is designed to address only the accounting entries that are created by each transaction.

Before you set up financial dimensions as legal entities, evaluate your business processes in the following areas to determine whether this setup will work for your organization:

  • Inventory
  • Sales and purchases between financial dimensions and legal entities
  • Sales tax calculation and reporting
  • Operational reporting

Here are some of the limitations:

  • You can use sales tax functionality only with legal entities, not with financial dimensions.
  • Some reports don’t include financial dimensions. Therefore, to report by financial dimension, you might have to modify the reports.

Custom dimensions

To create a user-defined financial dimension, in the Use values from field, select Custom dimension.

You can also specify an account mask to limit the amount and type of information that can be entered for dimension values. You can enter characters that remain the same for each dimension value, such as letters or a hyphen (-). You can also enter number signs (#) and ampersands (&) as placeholders for characters that will change every time that a dimension value is created. Use a number sign (#) as a placeholder for a number and an ampersand (&) as a placeholder for a letter. The field for the format mask is available only when you select Custom dimension in the Use values from field.

Example

To limit the dimension value to the letters “CC” and three numbers, enter CC-### as the format mask.

Entity-backed dimensions

To create an entity-backed financial dimension, in the Use values from field, select a system-defined entity to base the financial dimension on. Financial dimension values are then created from that entity. For example, to create dimension values for projects, select Projects. A dimension value is then created for each project name. The Financial dimension values page shows the values for the entity. If those values are company-specific, the page also shows the company.

Activating dimensions

When you activate a financial dimension, the table is updated so that it includes the name of the financial dimension. Deleted dimensions are removed. You can enter dimension values before you activate a financial dimension. However, a financial dimension can’t be consumed anywhere until it’s activated. For example, you can’t add a financial dimension to an account structure until the financial dimension has been activated. When you select Activate, all dimensions are updated and show status changes.

Translations

On the Text translation page, you can enter text for the selected financial dimension in various languages. On the Main account translation page, you can enter text for the main account in various languages.

Not all dimensions are valid for all legal entities. Additionally, some dimensions might be relevant only for a specific period. In these cases, you can use the Legal entity overrides section to specify the companies that the dimension should be suspended for, the owner, and the period when the dimension is active.

Deleting financial dimensions

To help maintain referential integrity of the data, financial dimensions can rarely be deleted. If you try to delete a financial dimension, the following criteria are evaluated:

  • Has the financial dimension been used on any posted or unposted transactions, or in any type of dimension value combination?
  • Is the financial dimension used in any active account structure, advanced rule structure, or financial dimension set?
  • Is the financial dimension part of a default financial dimension integration format?
  • Has the financial dimension been set up as a default dimension?

If any of the criteria are met, you can’t delete the financial dimension.

Default dimension values

You can use values from master records, such as customer and vendor, as default values in new dimensions. When the new dimensions are created, the master record ID is entered in the dimension values for those master records. For example, when you create a new customer, the customer ID is entered in the customer dimension. When you create sales orders, invoices, or other documents that require a customer ID, the existing defaulting rules are used, and the customer ID is added to the document.

This feature is controlled by a setting in the dimension. This setting is named Copy values to this dimension on each new DimensionName created, where DimensionName is the name of the dimension. By default, the feature is turned off. However, it can be turned on at any time.

If records already exist for the dimension, the master records are updated when you turn the feature on. However, existing documents and transactions aren’t updated.

If you are using a template to create a master record, make sure that the template value for the master dimension is blank. For example, if you’re creating customers from a template, make sure that the customer dimension in the template is blank. The customer dimension value will default from the new customer number when you create the new customer.

Derived dimensions

You can configure a dimension so that information for other dimensions is automatically entered when you enter that dimension in a document. For example, if you enter cost center 10, a value of 20 can be automatically entered in the department dimension.

You can set up derived values on the dimensions page.

  1. Select a dimension and then select Derived dimensions. The Derived dimensions page includes a grid. The selected dimension segment is the first column in this grid.
  2. Add the segments that should be derived. Each segment appears as a column.

Enter the dimension combinations that should be derived from the dimension in the first column. For example, to use the cost center as the dimension that the department and location are derived from, enter cost center 10, department 20, and location 30. Then, when you enter cost center 10 in a master record or on a transaction page, department 20 and location 30 are entered by default.

Overriding existing values with derived dimensions

By default, the derived dimension process doesn’t override existing values for derived dimensions. For example, if you enter cost center 10, and no other dimension is entered, department 20 and location 30 are entered by default. However, if you change the cost center, the values that have already been established aren’t changed. Therefore, you can establish default dimensions on master records, and those dimensions won’t be changed by derived dimensions.

You can change the behavior of derived dimensions to override existing values by selecting the Replace existing dimension values with derived values check box on the Derived dimensions page. If this field is selected, you can enter a dimension with derived dimension values and those derived dimension values will override any values that already exist. Using the previous example, if you enter cost center 10, and no other dimension is entered, department 20 and location 30 are entered by default. However, if the values were already department 50 and location 60, the values will now be changed to department 20 and location 30.

Derived dimensions with this setting do not automatically replace the existing default dimensions values when dimension values are defaulted. Dimension values will only be overridden when you enter a new dimension value on a page and there are existing derived values for that dimension on the page.

Preventing changes with derived dimensions

When you use Add segment” on the Derived dimensions page to add a segment as a derived dimension, an option is provided at the bottom of the Add segment page that allows you to prevent changes to that dimension when it is derived on a page. The default setting is off so it does not prevent the derived dimension values from being changed. Change the setting to Yes if you want prevent the dimension from being changed after it has been derived. For example, if the value for the Department dimension is derived from the value of the Cost center dimension, the Department value cannot be changed if the Prevent changes setting is Yes.

The setting does not prevent changes if the dimension value is valid but it is not listed in the derived dimensions list. For example, if Department 20 is derived from Cost center 10 and you enter Cost center 10, then you will not be able to edit Department 20. However, if you enter Cost center 20 and it is not in the list of derived dimensions for Cost center, then you can edit the Department value.

In all cases, the account value and all dimensions values will still be validated against the account structures after the derived dimensions values have been applied. If you use derived dimensions and they fail validation when used on a page, you must change the derived dimensions values on the derived dimensions page before you can use them in transactions.

When you change dimensions on the Financials dimensions FastTab, the dimension that is marked to prevent changes will not be editable. If you are entering an account and dimensions into the segmented entry control on a page, the dimensions are editable. However, when you move the highlight off the segmented entry control and move to another field or take an action, the account and dimensions will be validated against the derived dimensions list and the account structures to ensure that you have entered the appropriate values.

Derived dimensions and entities

You can set up the derived dimensions segments and values by using entities.

  • The Derived dimensions entity sets up the driving dimensions and the segments that are used for those dimensions.
  • The Derived dimensions value entity lets you import the values that should be derived for each driving dimension.

When you use an entity to import data, if that entity imports dimensions, the derived dimension rules are applied during the import unless the entity specifically overrides those dimensions.

The original article can be found here

Set up vendor invoice policies

This topic explains how to set up vendor invoice policies. Vendor invoice policies are run when you post a vendor invoice by using the Vendor invoice page and when you open the vendor invoice Policy violations page. You can also configure the vendor invoice workflow to run vendor invoice policies every time that you submit an invoice to workflow.

  • Vendor invoice policies do not apply to invoices that were created in the invoice register or invoice journal.
  • Invoice matching validation does not use vendor invoice policies, but is instead set up in the Accounts payable parameters page.
  • This recording uses the USMF demo company. The accounts payable manager or accounting manager role would perform these steps. Before you begin, make sure that the Invoice matching configuration key is selected.

Prepare to create vendor invoice policies

  1. Go to Navigation pane > Modules > Accounts payable > Setup > Accounts payable parameters.
  2. Select the Invoice validation tab.
  3. Select or clear the Automatically update invoice header status check box.
  4. Select OK.
  5. In the Post invoice with discrepancies field, select an option.
  6. Close the page.
  7. Go to Navigation pane > Modules > Accounts payable > Policy setup > Vendor invoice policies.
  8. Select Parameters.
  9. Select Add.
  10. Close the page to return to the home page.

Create policy rule types for vendor invoices

  1. Go to Navigation pane > Modules > Accounts payable > Policy setup > Vendor invoice policy rule types.
  2. Select New.
  3. In the Rule name and Description fields, type values.
  4. In the Query name field, select the drop-down button to open the lookup, then select the desired record.
  5. Select Save.
  6. Close the page to return to the home page.

Define a vendor invoice policy

  1. Go to Navigation pane > Modules > Accounts payable > Policy setup > Vendor invoice policies.
  2. Select New.
  3. In the Name and Description fields, type values.
  4. Expand or collapse the Policy organizations section.
  5. In the tree, select Contoso Entertainment System USA.
  6. Select Add.
  7. Expand or collapse the Policy rules section.
  8. Select Create policy rule.
  9. In the Policy rule description field, type a value.
  10. Select Filter.
  11. Select Add. Select the desired record.
  12. In the Table, Derived table, and Field fields, select or enter options from the drop-down menus.
  13. Close the page.
  14. In the Criteria field, type a value.
  15. Select OK.
  16. Select OK.
  17. Close the pages to return to the home page.

The original article can be find here

Cost accounting – Fiscal calendars, fiscal years, and periods

This article discusses fiscal calendars, fiscal years and periods and how to utilize them for legal entities, fixed assets and budgeting.

Fiscal calendars provide a framework for the financial activity of an organization. Each fiscal calendar contains one or more fiscal years, and each fiscal year contains multiple periods. Fiscal calendars can be based on a January 1 to December 31 calendar year, or on any dates that you select. For example, some organizations select a fiscal calendar that starts on July 1 of one year and ends on June 30 of the following year.

There is no limit to the number of fiscal calendars that you can create, and no limit to the number of fiscal years that can be created for a fiscal calendar. Each fiscal calendar is independent of your organization, and can be used by multiple legal entities in the organization. For example, an organization has eight departments and each department is a separate legal entity. Five of them share the same fiscal calendar and three use different fiscal calendars. You can create one fiscal calendar for the five legal entities that share the same fiscal calendar, and then create separate fiscal calendars for the other legal entities.

Create fiscal calendars, fiscal years, and periods

You can create and delete fiscal calendars, fiscal years, and periods on the Fiscal calendars page. You can also divide existing periods and create closing periods that can be used to close a fiscal year.

A closing period is used to separate general ledger transactions that are generated when a fiscal year is closed. When the closing transactions are in one fiscal period, it is easier to create financial statements that either include or exclude different types of closing entries. If a fiscal year is divided into 12 fiscal periods, the closing period is usually the 13th period. However, a closing period can be created from any period that has a status of Open.

When you create a closing period, select a period that has a status of Open and that has the dates that you want to use. The new closing period will copy the starting and ending dates from the existing period. The original period will continue to exist. For example, you select Period 12, which is the last period in the fiscal year, and that has dates of August 1 through August 31. You enter a name for the closing period, such as Close. After you create the new closing period, you now have the original period and the closing period. Both have dates that start on August 1 and end on August 31.

Select fiscal calendars for ledgers, fixed assets, and budget cycles

Fiscal calendars are used with fixed asset depreciation, financial transactions, and budget cycles. When you create a fiscal calendar, you can use it for multiple purposes. You can select a fiscal calendar for a fixed asset book to make it a fixed asset calendar. You can select a fiscal calendar for a ledger to make it a ledger calendar. And you can select a fiscal calendar for a budget cycle to make it a budget calendar. You can use the same fiscal calendar for all of these.

Select the fiscal calendar that you want to use for the ledger for your legal entity in the Ledger form. A fiscal calendar must be selected on the Ledger page for every legal entity. After a fiscal calendar is selected, you can set up period statuses and permissions on the Ledger calendar page for any of the periods that are part of a fiscal year.

Select a fiscal calendar for fixed assets

You can select a fiscal calendar for a fixed asset book, and that fiscal calendar will be used by the fixed assets that use the selected book. You can select from any fiscal calendar that is defined on the Fiscal calendars page.

Define budget cycle time spans

Budget cycles are the length of time during which a budget is used. Budget cycles can include part of a fiscal year or multiple fiscal years, such as a biennial budget cycle of two years or a triennial budget cycle of three years. The budget cycle time span defines the number of periods that are included in the budget cycle. To specify the budget cycle time span, use the Budget cycle time spans page.

Maintain periods for your organization

You can use the Ledger calendar page to view the details of the fiscal calendar, fiscal years, and periods used by your organization. You can also change the status of the periods and select which users can post accounting transactions to periods. For example, at the start of a new period, you might want a group of users to finish posting financial transactions in the previous period, while other groups work only in the new period.

You can find original article here

Accounts Payable – Invoice matching and intercompany purchase orders

The purchasing legal entity that is involved in an intercompany trade transaction might be set up to use accounts payable invoice matching. When the Post invoice with discrepancies field in the Accounts payable parameters form is set to Require approval, invoice matching validation will be performed. In this case, the posting requirements for both intercompany trade and accounts payable invoice matching must be met before intercompany vendor invoices can be posted.

The examples in this topic use the following setup for intercompany trade:

  • Fabrikam Purchase is the purchasing legal entity.
  • Fabrikam Sales is the selling legal entity.
  • Customer 4020 exists in Fabrikam Sales.
  • Vendor 3024 exists in Fabrikam Purchase.
  • In Fabrikam Purchase, intercompany information is specified for vendor 3024. Fabrikam Sales is specified as the customer company, and customer 4020 is specified as the customer account that corresponds to the Fabrikam Purchase legal entity.
  • In Fabrikam Sales, intercompany information is specified for customer 4020. Fabrikam Purchase is specified as the vendor company, and vendor 3024 is specified as the vendor account that corresponds to the Fabrikam Sales legal entity.

The examples use the following setup for accounts payable invoice matching for Fabrikam Purchase:

  • On the Accounts payable parameters page, the Enable invoice matching validation option is selected.
  • On the Accounts payable parameters page, the Post invoice with discrepancies field is set to Require approval.
  • The price tolerance percentage for the legal entity is 2 percent.

Example: Price matching and intercompany trade

The net amounts for the intercompany vendor invoice and the intercompany customer invoice must be equal. This requirement overrides any invoice matching approvals or price tolerance percentages that apply. For example, you follow these steps.

  1. In Fabrikam Purchase, create sales order SO888 for customer 4020. Intercompany purchase order ICPO222 is automatically created for vendor 3024 in Fabrikam Purchase, and sales order ICSO888 is automatically created in Fabrikam Sales.
  2. In Fabrikam Sales, register that the items have been received, and post a packing slip. The status of ICSO888 changes to Delivered. The status of ICPO222 changes to Received.
  3. In Fabrikam Sales, perform an invoice update for ICSO888. The unit price is 0.45, and 100 items are updated.
  4. In Fabrikam Purchase, create an invoice for ICPO222. You accidentally change the net price from 45.00 to 54.00. An icon is displayed to indicate that the price exceeds the allowable price tolerance of 2 percent.
  5. On the Invoice matching details page, select the option to approve posting with matching discrepancies. On the Vendor invoice page, click OK. If the vendor invoice was not an intercompany vendor invoice, posting would be successful. However, because you are working with an intercompany vendor invoice, posting is unsuccessful. For intercompany trade, the invoice totals on the intercompany sales order must equal the invoice totals on the corresponding intercompany purchase order. To resolve this issue, you must correct the net price on the invoice by changing the net price back to the default amount, 45.00.

Example: Quantity matching with intercompany trade

The quantities on the intercompany purchase order and the intercompany sales order must be equal. This requirement overrides any invoice matching approvals that apply. This example uses the following additional setup for intercompany trade:

  • In Fabrikam Purchase, the purchase order action policy for vendor 3024 is set up to automatically post both the original customer invoice and the intercompany vendor invoice.

This example uses the following additional setup for accounts payable invoice matching for Fabrikam Purchase:

  • On the Item model groups page for the model group that is used by item B-R14, the Receiving requirements option is selected.
  • The on-hand quantity for item B-R14 is 0 (zero).

For example, you follow these steps.

  1. In Fabrikam Purchase, create sales order SO999 for customer 4020. The order contains one line item: 100 batteries (item B-R14) at a unit price of 1.00 each. Intercompany purchase order ICPO333 is automatically created for vendor 3024 in Fabrikam Purchase, and sales order ICSO999 is automatically created in Fabrikam Sales.
  2. In Fabrikam Sales, perform an invoice update for ICSO999. Posting is unsuccessful, because the item is out of stock and has not yet been received. Therefore, the financial information cannot be updated.
  3. In Fabrikam Sales, register that the items have been received, and post a packing slip for ICSO999. A product receipt for ICPO333 is automatically posted in Fabrikam Purchase. In Fabrikam Purchase, the received quantity for item B-R14 changes to 100.
  4. In Fabrikam Sales, perform an invoice update for ICSO999. Posting is successful in both legal entities. In Fabrikam Purchase, the quantity that is purchased for item B-R14 changes to 100.

You can find original article here

Asset Management – Functional location lifecycle states

This topic describes how to set up functional location lifecycle states and lifecycle models in Asset Management. Functional location lifecycle states define the states that a functional location can go through, for example, created, active, and ended. You are able to view all functional locations, regardless of their lifecycle state, in the All functional locations list page. You can change the state of a functional location by selecting it in the All functional locations list page and selecting Update functional location state.

Set up functional location lifecycle states

  1. Select Asset management > Setup > Functional locations > Lifecycle states.
  2. Select New to create a new functional location state.
  3. Insert the state ID in the Lifecycle state field and a name for the functional location state in the Name field. In the Lifecycle models field, you can see the number of functional location lifecycle models that uses the functional location state.
  4. On the General FastTab, select “Yes” on the Active toggle button if the functional location should be active at this state.
  5. Select “Yes” on the Create assets toggle button if it should be possible to automatically create an asset with the same name as the functional location and install it on the functional location at this state.

Note

This toggle button relates to the Asset type field on the General FastTab in the Functional location types form (Asset management > Setup > Functional locations > Functional location types). 6. Select “Yes” on the Rename location toggle button if it should be possible to change the name of the functional location at this state. 7. Select “Yes” on the New sub locations toggle button if it should be possible to add new sub locations to the functional location at this state. 8. Select “Yes” on the Install assets toggle button if it should be possible to install assets on the functional location at this state. 9. Select “Yes” on the Delete functional location toggle button if it should be possible to delete the functional location at this state. 10. Select an asset state in the Lifecycle state field if you want the asset lifecycle state for all assets installed on the functional location to be automatically updated at this state. Example: If you close down a functional location, and set the functional location lifecycle state to “Ended”, you may want to automatically change the lifecycle state of the assets installed on that functional location to “Not in use”.

Note

Functional location lifecycle states, lifecycle models, and types are related and used in the same way as work order lifecycle states, work order lifecycle models, and work order types.

Set up functional location lifecycle models

When you have created the lifecycle states required for your functional locations, they can be divided into groups. This is done to create the lifecycle model flow that may be used for different types of functional locations. As a minimum, one standard functional location lifecycle model should be created.

  1. Select Asset management > Setup > Functional locations > Lifecycle models.
  2. Select New to create a new lifecycle model.
  3. Insert the lifecycle model ID in the Lifecycle model field and a name for the lifecycle model in the Name field. In the Functional location types and Lifecycle states fields, you can see the number of functional location types that uses the lifecycle model and the number of states selected in the lifecycle model.
  4. On the Lifecycle states FastTab, select the states that should be included in the model. This is done by clicking on a state in the Lifecycle states remaining section and clicking the forward arrow button.
  5. If you want to select all the available states for a model, click the select all available stages button. All states are transferred to the Lifecycle states selected section.
  6. If you want to remove a selected state from the model, select the state in the Lifecycle states selected section and then select the back arrow button.
  7. Select Lifecycle state updates to define which lifecycle states can follow a selected state.

You can find original article here

Use Accounts receivable to track customer invoices and incoming payments

You can create customer invoices that are based on sales orders or packing slips. You can also enter free text invoices that are not related to sales orders. You can receive payments by using several different payment types. These include bills of exchange, cash, checks, credit cards, and electronic payments. If your organization includes multiple legal entities, you can use centralized payments to record payments in a single legal entity on behalf of the other legal entities.

Business processes

Business process

Set up Accounts receivable

Use Accounts receivable to track customer invoices and payments that you receive from customers. You can set up customer groups, customers, posting profiles, interest notes, collection letters, commissions, and parameters regarding customers, charges, deliveries and destinations, bills of exchange, and other types of Accounts receivable information.

Set up credit and collections

Accounts receivable collections information is managed in one central view, the Collections page. Credit and collections managers can use this central view to manage collections. Collections agents can begin the collections process from customer lists that are generated by using predefined collection criteria, or from the Customers page.

Credit and collections in Accounts receivable

Configure Accounts receivables and Credit and collections

Set up Credit and collections

Set up payments and settlements

Accept different types of payments from customers, such as bills of exchange, cash, checks, credit cards, and electronic payments.

You can find original article here

Asset management overview

Asset Management is an advanced module for managing assets and maintenance jobs in Dynamics 365 Supply Chain Management. Asset Management integrates seamlessly with several modules in Finance and Operations apps.

The image below is an illustration of the interfaces to other modules in Finance and Operations.

Overview of how Asset Management integrates

Asset Management enables you to efficiently manage and carry out tasks related to managing and servicing many types of equipment in your company, for example, machines, production equipment, and vehicles. Asset Management supports solutions across numerous industries.

You can find original article here

Configure Accounts payable overview

Prerequisites for Accounts payable setup

Before you can set up Accounts payable, you must complete the following setup:

  • In General ledger:
    • If you plan to use payment journals, set up payment journals.
    • If you plan to run exchange rate adjustments, set up currency codes on the Currencies page, set up exchange rate types on the Exchange rate types page, and set up currency exchange rates on the Currency exchange rates page.
  • In Cash and bank management, set up bank accounts to use with methods of payment.

Setup pages for Accounts payable

Use the following pages to set up the basic functionality of Accounts payable for each legal entity. The pages are listed in the recommended order of setup. To make the setup process easier, you can create templates from the first records that you create. In a template, values are typically entered in many fields to reflect the features that the organization wants to implement for a particular type of vendor.

  1. On the Terms of payment page, define the terms of payment that you assign to sales orders, purchase orders, customers, and vendors, and that determine invoice due dates. For more information, see Define vendor payment fees.
  2. On the Methods of payment – vendors page, create and maintain information about how the organization pays its vendors.
  3. On the Vendor groups page, create and maintain groups of vendors that share important parameters for posting, settlement and payment, reporting, and forecasting.
  4. On the Vendor posting profiles page, define how vendor transactions are posted to the general ledger.
  5. On the Accounts payable parameters page, set up default settings that are applied if a more specific setting isn’t specified, parameters for various kinds of functionality, and the various number sequences for Accounts payable.
  6. On the Form setup page, define the format of various documents that are related to vendors, and that the organization uses to keep track of receipts from vendors and enter reasons for the flow of payments to vendors.
  7. On the Vendors page, create and maintain vendor accounts, and also the tax authorities that your organization reports sales taxes to.

Optional setup pages for Accounts payable

In addition to the basic functionality, Accounts payable has other functionality that you can set up.

The additional setup pages are organized by functionality.

Policies

  • On the Vendor invoice policy page, set up vendor invoice policies.

Invoice matching

  • On the Invoice totals tolerances page, set up tolerances for invoice totals.
  • On the Matching policy page, set up two-way and three-way matching policies.
  • On the Price tolerances page, set up tolerances for unit prices.
  • On the Item price tolerance groups page, set up tolerance groups for item prices.
  • On the Vendor price tolerance groups page, set up tolerance groups for vendor prices.
  • On the Charges tolerances page, set up tolerances for charges.

Workflow

  • On the Accounts payable workflows page, set up workflow configurations for journal approvals and purchase requisitions.

Reasons

  • On the Vendor reasons page, set up reason codes.

Charges

  • On the Charges code page, set up codes for the charges that are used in purchase orders.
  • On the Vendor charges group page, create and maintain charges groups for vendors.
  • On the Item charge groups page, create and maintain charges groups for items.
  • On the Auto charges page, define the charges that are automatically assigned to orders.

Supplementary items

  • On the Supplementary item groups – Vendor page, create and maintain supplementary item groups for vendors.
  • On the Supplementary item groups – Inventory page, create and maintain supplementary item groups for items.

Distribution

  • On the Terms of delivery page, create and maintain the conditions for an item’s transfer from seller to buyer.
  • On the Modes of delivery page, create and maintain the methods of transport that are used when an order is delivered from the seller to the buyer.
  • On the Destination codes page, create and maintain identifiers and descriptions for delivery destinations.

Forms

  • On the Form notes page, create the standard text that appears on various pages.
  • On the Form sorting parameters page, set up the sorting order for requisitions, receipt lists, packing slips, and invoices.
  • On the Print management setup page, set up print management information for originals and copies of pages.

Payments

  • On the Cash discounts page, set up and manage the terms for obtaining cash discounts. The cash discount codes are linked to vendors and are applied to purchase orders.
  • On the Payment schedules page, set up the payment schedules that are used to manage installment payments to vendors.
  • On the Payment days page, define the payment days that are used to calculate due dates, and specify payment days for a specific day of the week or month.
  • On the Payment fee page, create and maintain the payment fees that are associated with vendors.
  • On the Payment instruction page, create and maintain payment instructions.

Statistics

  • On the Aging period definitions page, set up user-defined intervals that are used to analyze the maturity distribution of vendor accounts.
  • On the Line of business page, create the line of business (LOB) codes that are assigned to vendors.

Tax 1099

  • On the 1099 fields page, verify and update the minimum amounts that must be reported to the Internal Revenue Service (IRS), based on the latest IRS requirements.

Optional setup for other modules

Organization administration

  • On the Number sequences page, set up number sequence groups for invoice numbers.
  • On the following pages, set up address information:
    • Address setup
    • NAF codes
    • Import ZIP/postal codes

General ledger

  • On the Financial dimensions page, set up financial dimensions.
  • On the following pages, set up tax information:
    • Sales tax codes
    • Sales tax groups
    • Item sales tax groups
    • Account group
    • Sales tax exempt codes
    • Sales tax jurisdictions
    • Sales tax authorities
    • Sales tax settlement periods

You can find the original article here

Today I will show you how to initiate a manual failover and how to perform a fallback on your IOT-hub

By default, the IoT Hub service provides intra-region High Availability by implementing redundancies in almost all layers of the service. The SLA published by the IoT Hub service is achieved by making use of these redundancies. No additional work is required by the developers of an IoT solution to take advantage of these High Availability features.

Although IoT Hub offers a reasonably high uptime guarantee, transient failures can still be expected as with any distributed computing platform. If you’re just getting started with migrating your solutions to the cloud from an on-premise solution, your focus needs to shift from optimizing “mean time between failures” to “mean time to recover”. In other words, transient failures are to be considered normal while operating with the cloud in the mix. Appropriate retry policies must be built into the components interacting with a cloud application to deal with transient failures.

Manual failover is a feature of the IoT Hub service that allows customers to failover their hub’s operations from a primary region to the corresponding Azure geo-paired region. Manual failover can be done in the event of a regional disaster or an extended service outage. You can also perform a planned failover to test your disaster recovery capabilities, although it is recommended that a test IoT hub is used rather than one running in production as the solution is unavailable during the failover process.

Azure IoT Hub Manual Failover You should note that there is a limit of two failovers and two failbacks per day for an IoT Hub.

Complete the following steps:
1. In your Web browser, to open your Azure portal, navigate to the portal.azure.com. When you log into Azure you will arrive at the Azure portal home page for your Azure account.

2. In the top-left corner of your Azure portal, under Favorites click Resource groups.
3. In the Resource groups blade, select the resource group name you are using.
4. In the Resource group blade, in the list of resources, click the Storage account you have created.
5. Under Resiliency on the IoT Hub blade, click Manual failover (preview).
6. On the Manual Failover pane, read and note the warning: Use this feature to failover your IoT hub to the secondary location. This action will cause down time and telemetry loss to your solution.

This is a long running operation and could take several minutes to finish. Please exercise with caution when using it.

7. On the Manual failover pane, you see the IoT Hub Primary Location and the IoT Hub Secondary Location.

The primary location is initially set to the location you specified when you created the IoT hub, and always indicates the location in which the hub is currently active. The secondary location is the standard Azure geo-paired region that is paired to the primary location. You cannot change the location values.

8. At the top of the Manual failover pane, click Initiate failover.

9. On the Confirm manual failover pane note the warning: Warning! This action can’t be canceled. Your IoT hub will be activated in the secondary location.

In order to move your IoT hub back to the original location, you will have to trigger the failover again after the current operation succeeds.

10. Under Iot hub name, enter the name of your IoT hub and click OK. This confirms your desire to failover.

Note that you can use the mouse to select and copy the IoT hub name from another area of the web page. The amount of time it takes to perform the manual failover is proportional to the number of devices that are registered for your hub. For example, if you have 100,000 devices, it might take 15 minutes, but if you have five million devices, it might take an hour or longer.

While the manual failover process is running, there is a banner on the Manual Failover pane that tells you a manual failover is in progress. After a processing period, you will get a notification that your IoT Hub failover has been completed successfully. After it’s finished, the primary and secondary regions on the Manual Failover page are flipped and the hub is active again. Azure IoT Hub Failback After you have performed a manual failover, you can switch the hub’s operations back to the original primary region – this is called a failback. If you have just performed a failover, you must wait about an hour before you can request a failback. If you try to perform the failback in a shorter amount of time, an error message is displayed.

A failback is performed just like a manual failover.

These are the steps:
1. To perform a failback, return to the Iot Hub pane for your Iot hub.
2. Under Resiliency on the IoT Hub pane, click Manual failover.
3. At the top of the Manual failover pane, click Initiate failover. You see the Confirm manual failover pane.
4. In the Confirm manual failover pane, under Iot hub name, enter the name of your IoT hub and click OK.

As before, the amount of time it takes to perform the manual failover is proportional to the number of devices that are registered for your hub. For example, if you have 100,000 devices, it might take 15 minutes, but if you have five million devices, it might take an hour or longer. While the manual failover process is running, there is a banner on the Manual Failover pane that tells you a manual failover is in progress. After a processing period, you will get a notification that your IoT Hub failover has been completed successfully. After it’s finished, the primary and secondary regions on the Manual Failover page are flipped and the hub is active again.

Verify Device-to-Cloud Communication

Now you will verify that device-to-cloud communication is taking place by using the Serial Monitor in Visual Studio Code and checking your Azure Portal.

  1. Ensure that you have your GetStarted project opened in Visual Studio Code and that your device is connected to you PC.
  2. In Visual Studio Code, examine the status bar that runs along the bottom of the window.
  3. Hover your mouse pointer over each of the buttons on the status bar. You should see label appear that identifies the purpose associated with the buttons.
  4. Use the button labels to locate the following buttons:
    • Show Board Config
    • Open Serial Monitor
    • Select Serial Port
    The Open Serial Monitor button is the button displaying the icon that looks like a power plug.
  1. In Visual Studio Code, on the bottom status bar, click the Select Serial Port button.
  2. At the top of the Visual Studio Code window, notice the prompt asking you to “Select a serial port”.
  3. At the prompt, select the COM port labeled STMicroelectronics You may recall seeing the STMicroelectronics name pop up when you were configuring your MXChip device. The STMicroelectronics driver is used to communicate with the MXChip AZ3166 device.
  4. On the bottom status bar, click the Baud Rate button, and then click 115200 If your application is running successfully, you see something similar to the following:
  1. Open a browser window and navigate to your Azure portal: portal.azure.com You should see your dashboard and the Resources tile. If you don’t, verify that you are logged in with the Azure account and subscription that you are using.
  2. Open your IoT Hub, and review the information displayed on the Overview blade.
  3. Notice that the IoT Hub Usage tile shows you that messages are arriving at your IoT Hub.