![]() This change would have a series of ripple effects, since the core definition of what functions was allowed performed with the previous service item has been changed. If for some reason whatsoever a service item was to be promoted to become a standard item to be purchased, the system offered the option to change the item type from service to item. During the inventory closing run, the service items will be settled according to the special “service item settlement” principle, which will close service item transactions without making any adjustments, therefore will be no additional posting created. Therefore the service items transactions will be excluded during the inventory recalculation process. This will ensure that, in the example of purchasing the car service, an expense account will be used for receipt transactions.įrom an inventory costing perspective, the system does expect service item transactions to be adjusted. Furthermore, all ledger integration options, particularly the Post financial inventory must be left blank. In the inventory model group, negative physical and financial inventory must be allowed for service items. In order to support the scenario in Microsoft Dynamics AX 2009 the reference data for such a service item would have to be defined specially for these items. The financial value of the service would be posted directly to expense accounts rather than inventory accounts. A business has certain services (items of type service) in their inventory, which they would like to, in the above scenario, purchase. The example illustrates the normal practice for service items. The employee will take the company car and “purchase” (consumes) the service at the car shop. ![]() Once a year, the company car must undergo service inspection at a local car shop (producer). The Contoso Company (consumer) has a fleet of company cars. Services are by definition consumed at the moment they are produced and can therefore not be stocked nor “owned” unlike items. Whereas the item types Item and BOM share to a very high degree the same characteristics, the item type service is different. – Coverage plan settings can be defined as purchase, transfer or production – BOMs can be produced and transferred when running master planning BOMs can be semi-finished items or finished items – Cannot configure items using the Product Configurator – Coverage plan settings can only be defined as purchase – Master planning cannot produce or transfer service – No inventory balances are stored, which means these items cannot be reserved nor picked ![]() – Inventory transactions are created for source documents, allowing the user to receive/issue inventory for service items – Coverage plan settings can be defined as purchase – Planned purchase orders and transfer orders can be created when running master planning ![]() – Inventory balances are stored, which means these items can be reserved and picked Represent finished items and raw materials. The table below illustrates these options: Microsoft Dynamics AX 2009 offered the options to define different types of items. Item definitions in Microsoft Dynamics AX 2009 and earlier The purpose of this post is to describe the difference between stocked and non-stocked products of type service and to provide general recommendation about this subject. With Microsoft Dynamics AX 2012 new capabilities of selling and procuring products, decoupled from inventory control, have been introduced.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |