存档

2013年2月 的存档

Navision 25th 25周年记 – 祝贺

2013年2月25日 没有评论

Navision从1984年诞生, 到2012年12月, 已经完美服役了25周年, 还将焕发更多活力. — Navision Asia Team祝贺.

下面内容摘自博客, 欢迎转载和翻译.

Microsoft Dynamics NAV celebrates its 25th anniversary. I joined the NAV world just two years after, in 1989. I urge you to comment on this article if you have additional fun or interesting facts to share. My main experience comes from servicing international customers with NAV, but I did have my 2 years at Navision Software and was a part of the Navision Financials/Windows 95 launch.

Here’s the full story in brief from the very beginning in the early 1980’s.

It began in 1984 with Pc Plus

In 1984 Jesper Balser, Peter Bang and Torben Wind were still students at Technical University of Denmark (known as DTU today) when they released PC Plus. PC Plus earned great success because of its simplicity and ease of use. Rumors say that they also were considering developing an ironing machine for shirts, but they decided for the IT-way, which was a clever choice.

Finance, warehouse, debit and credit: Everything a trader needs is in place in the first version. The program is however only a single-user solution. Despite its limitations, PC Plus is actually still used today in some small businesses. Quite amazing for a piece of computer software.

In 1987 NAV is born

In 1987, the three young IT engineers are ready to conquer the world. Together with IBM, they launch the first version of NAV (IBM-NAVIGATOR) – later also to be called:
• NAVIGATOR
• NAVISION
• A/Vista
• NAVISION ATTAIN
• NAVISION FINANCIALS
• Microsoft Business Solutions – Navision
• Microsoft Business Solutions – NAV
• Microsoft Dynamics NAV

(If any names are forgotten it’s not intentionally)

Think of it. Nowadays NAV is actually older than many of the people using it.

As the first ERP software in the world to utilize the client-server technology it was already from the beginning a state-of-the-art piece of software and the application was built on top of a genius native database. Us old-timers remember having explained “Optimistic Concurrency” about a million times.

NAV was sold in Denmark through IBM dealers with IBM as the exclusive distributor. I remember one of the first NAV campaigns run under the theme “The Beauty of Simplicity” picturing Einstein on public busses and in large newspaper ads in Copenhagen. The manual (handbook) had a brown leather cover that would fit into any retro English business club. You got the full software on 4 (later 2) floppy discs, which was quite convenient because to download over a 9.6 baud modem would’ve been a nightmare.

Several years later, Navision started distribution on its own, taking care of both development and sales. But NAV had already quickly become one of the leading financial systems in Denmark, yet competing head on with Concorde (which later became Microsoft Dynamics AX).

NAV was designed to manage financial, customer/vendor, product overviews and billing. The system simply made it possible to continuously keep track of whether your business earned money. Prior to that, businesses had to save and go through documents and invoices physically, to keep track of projects and business issues.

1990 The expansion of NAV

1990 was the year where we saw the release of the earliest iteration of how we know NAV today.

One of the major changes to the software was its ability to allow users to make major modifications to the software due to the introduction of an application language, or AL. This opportunity to make changes and new modules inside NAV is the foundation for the more than 1500 vertical and add/on solutions available today.

Iterations went from 1.X through 3.X by the late 1990′s. Version 2.X brought the ability to utilize SQL Servers as the RDBMS. Version 3.X was a critical release for North America as it initiated the process of combining the Navision Financial Management, Distribution, and Manufacturing Databases into one single Database. Other notable advances in Version 3.X were the combination of Canadian and U.S. databases into one, as well as the addition of unlimited dimensions building on a truly relational chart of accounts
NAV arrived in North America in 1994 as a DOS-based system called A/Vista.

Coming back to the design of the manuals, the brown leather was now replaced with artwork by the famous Danish designer Arnoldi: two blue colors representing the horizon between water and the sky .

NAV was also supported on a number of Unix platforms, IBM’s AIX platform actually worked really well with NAV. There was also an idea to run NAV on IBM’s AS/400 in an AIX emulator, but it was never pursued as a go to market offering.

1995: NAV is given a graphical user interface Windows 95 compliant

In 1995 Navision Software and Microsoft joined forces around the release of Windows 95 and the first Windows based version of NAV. The first edition was called Financials – like Oracle’s competing ERP solution. NAV was the first piece of ERP software that was certified by Microsoft for Windows 95. Navision Financials 1.0 could also run under Windows 3.11. There were many jokes and circulating questioning on why bookkeeping with a graphical user interface and a mouse should be more effective than using the keyboard and short-keys.

The User Interface Designer and Project Manager Jakob Nielsen was responsible for making NAV compliant with the Windows 95 GUI standards. Jakob was very thorough and at the launch of the Windows based NAV version he handed over a monster thick report to Microsoft detailing where Microsoft did not meet their own standards. And what is Jakob Nielsen doing today¬? He is Principle User Experience Manager at Microsoft Cooperation – and by the way he is always volunteering at Microsoft Convergence and WPC for community work, but that’s another story.

In parallel with the ongoing updates of the product, resellers started making their own solutions based on NAV. It was also around this time that the cooperation with IBM ended and Navision Software established their own distribution company in Denmark, and distributors were added in several countries (they were called Navision NTR’s).

In 1999, the newest version of NAV presented the option to use Microsoft SQL database as an alternative to the Native database. A few years later, this turned out to be a really good idea!

Throughout the rest of the decade, newer versions of NAV were released, continuing to improve upon its simplicity and performance.

The product could also handle production management, making it attractive for larger customers – also outside Denmark. “Dimensions” were introduced to the product, allowing customers to analyze their business across departments or job functions. Also the core of the program – the database – was continuously optimized to run even faster. Partners now started implementing solutions for up to 100 or more users and in many more geographies, which was added continuously.

New millennium

The next year, Navision Software merged with Damgaard, a Danish competing company whose system Axapta was born and built on SQL database (and Oracle). NavisionDamgaard was merged to bring together Damgaard’s high-end Axapta capabilities with Navision’s strong international channel and beauty of simplicity.

The 2001 release of NAV, marketed under the name Attain included a CRM function, so users could now manage the entire customer side including sales and service. In addition, the program could also support production management. With these evolutions, the solution reached out to more and more customers on the international markets. For the first time, NAV could officially be referred to as an ERP system.

The international business with NAV was growing fast and Partner Power was founded in 2001 as the first and is still the only Microsoft Dynamics partner with a dedicated focus on international Dynamics implementations in more than 50 countries.

Microsoft era
In 2002, Microsoft acquired NavisionDamgaard. In the autumn of the same year Microsoft Business Solutions – Navision 3.70 was released.

Microsoft Dynamics
Microsoft Business Solutions – Navision 4.0 was then released with a menu structure looking very much like the Outlook menu.

In 2007, Navision 5.0 is now known as the NAV part of Microsoft’s ERP portfolio – with a strong Danish participation in the form of XAL, C5 (DK only), NAV and the former Damgaard Axapta product, under the name AX is aimed towards enterprise customers.

The other products in the Microsoft Dynamics family are Great Plains (GP) and Solomon (SL), which are mainly targeting the US and English speaking markets – and Dynamics CRM.

Development environments are now focused in the direction of Microsoft SQL database, and each of the products are framed by a Product Roadmap that is bringing an overall long term MS planning to each of the products.

NAV 2009 – the Role Tailored client

Microsoft Dynamics NAV 2009 release was promoted big time for the new role based client, where each user desktop is adapted to the function they have in the company. At the same time, there is increasingly better integration between NAV and programs in the Office suite.

Partners and users have however been reluctant to take advantage of the Role Tailored client holding on to the classic client. But those days are over with the NAV 2013 release where only the RTC user interface is available in the full client version.

Where the original database was tailored to find data – and therefore lightning fast – the native database came short in the long run because it was less suitable for integration with the Microsoft stack.

But NAV has provided 25 years of dedicated service from the good old DOS days to a fully integrated web application soon to move into the cloud on Azure we all believe.

The future

Microsoft has geared up to deliver a major release every year. They are re-activating partners in many of the countries to deliver localizations under the PLLP framework. And NAV will for sure soon be available in the cloud.

As an NAV professional that has been on board almost from the start, I can only say that the many years with NAV has given me a life full of joy and an opportunity to work with some of the brightest people in IT and Business Management.

Thank you all NAV old-timers; Users who have NAV as their daily work tool, the certified professionals that sometimes work really long hours to get the system ready for the planned go-live, and to Microsoft for continuing to invest in Microsoft Dynamics NAV.

I am half way through my working life with NAV and I hope that I can retire in 23 years from now and rest assured that NAV is not getting older, only better. “Like” this article to say “Congratulations NAV”.

None of Navision’s founders are working in Microsoft anymore.

博文作者介绍:

Henning

Henning is Vice President and Senior Executive Advisor at Partner Power International. Having worked with Microsoft Dynamics since 1989 Henning is a seasoned professional with international experience from more than 200 Microsoft Dynamics projects completed all over the world. He is a methodology expert and recognized as one of the leading innovators by consistently improving how Microsoft Dynamics can be utilized in international organizations. Henning has an impressive track record from various management positions within the MS partner organization and is now working at Partner Power International heading the global customer engagement organization.

原博文地址:
http://www.partnerpowerinternational.com/blog/nav-turned-25-years-congratulations

分类: NAV2013 标签:

NAV 2009 – Course 80258 – Trade – 课程3

2013年2月22日 没有评论

培训时间: 2013年02月21日 晚20:00 – 21:30
培训地点: YY频道 40215226
培训内容: NAV 2009 – Course 80258 – Navision Trade III

视频:

课堂大纲 Trade III

Item Charge — 收费物料

不以数量形式去体现的物料附加成本/费用功能. 虚拟

附加到物料交易(采购收货/销售发货)上去. (Value Entries)

销售业务发生的运费. 1月1次结算.

采购业务发生的关税.

Financial management Inventory Setup Item Charges

数量 x 单价 = 金额
1) 数量为总金额, 单价为1
2) 单价为总金额, 数量为1

1. 创建Item Charges, 指定过账组
2. 创建采购发票, 选择Item Charges, 分配收费物料 – 分配方式
3. 过账

分配收费物料 – 分配方式 以及特殊应用
数量为1, 单价为总金额. (这是不建议的方式)
数量为总金额, 单价为1. (手动填写需要分配的金额或自动分配)

特殊应用,修复错误使用
采购订单 VAT17, 应该是VAT 6. –>收货 –>发票

1. 做Credit Memo, 选择Item Charge. Item Charge 和物料一致的产品过账组/VAT过账组=VAT17. 数量=订单总金额. 单价为1. 分配时使用按金额自动分配, 到对应的采购收货行.
2. 做Invoice, 选择Item Charge. 选择VAT过账组=VAT6. 数量=订单总金额. 单价为1. 分配到对应的采购收货.

特殊应用2:

将Item Charge进行开发,实现 生产上的制造费用分摊到对应的产出分录上.

Order Promising 订单计划. 订单预期

交货周期
采购交货周期. 采购订单 (订单日期 Order Date + Lead Time (取供应商卡片或物料卡片上的最大日期) = Planned Receipt Date.
Planned Receipt Date + Safety Lead Time (默认来自 生产设置, 可以在物料卡片上单独设置) + Inbound Warehouse Handling Time (来自Inventory Setup) = Expected Receipt Date)

Expected Receipt Date 是 MRP 自动计算后的预期收货日期. 也是对现有采购订单作为供应需求的计算依据

Document Date: Document Date + Payment Terms = Due Date (将带入发票的到期日期)

Posting Date, 过账日期 (收到G/L Setup上的允许过账期间管理, 或者User Setup上允许过账期间)

销售交货周期. 销售订单 (Shipment Date, 是MRP计算需求的依据.
Shipment Date(发货日期) + Outbound Warehouse Handling Time (来自库存设置) = Planned Shipment Date (计划的发货日期)
Planned Shipment + Shipping Time = Planned Delivery Date (预计交货日期)

物料可用性状态查询

GrossRequirement := 毛需求量
Item.”Qty. on Sales Order” +
Item.”Qty. on Service Order” +
Item.”Scheduled Need (Qty.)” +
Item.”Trans. Ord. Shipment (Qty.)” +
Item.”Planning Issues (Qty.)” +
Item.CalcPurchReturn;

PlannedOrderReceipt := 订单计划收货
Item.”Planned Order Receipt (Qty.)” +
Item.”Purch. Req. Receipt (Qty.)”;

ScheduledReceipt := 计划入库
Item.”FP Order Receipt (Qty.)” +
Item.”Rel. Order Receipt (Qty.)” +
Item.”Qty. on Purch. Order” +
Item.”Qty. in Transit” +
Item.”Trans. Ord. Receipt (Qty.)” +
Item.CalcSalesReturn;

PlannedOrderReleases := 订单已发放
Item.”Planned Order Release (Qty.)” +
Item.”Purch. Req. Release (Qty.)”;

分类: Training 标签:

Navision多语言标志

2013年2月15日 没有评论

Navision在多语言处理方面, 非常不错. 下面为大家整理了多语言标签翻译时的相关参考.

 

标签ID 标签名称 标签说明 是否存在相关参考
P8629 CaptionML 标题翻译 Y  P2818
P8630 PageNamesML 页名称翻译 Y  P2818
P8631 ToolTipML 辅助提示翻译 Y  P2818
P8632 OptionCaptionML 选项标题翻译 Y  P10340
P18490 Report’s   LableCaptionML 报表节中的标签标题翻译 Y  P2818
P26171 ConstValueML 文本常量翻译 Y  P2818

欢迎各位评论.

分类: C/AL, Installation 标签:

Navision C/AL程序开发学习License及视频

2013年2月9日 没有评论

首先恭祝大家蛇年快乐, 为大家特别献上新年礼物. Navision C/AL程序开发学习教程.

另, 在开发学习过程中, 需要具有开发权限的License, 请到群共享中下载微软公司提供的基于BRL AM授权的可开发License.

软件License版权归微软公司所有. License信息如下:

License number : 0034
Licensed to : Cronus
1 Lone Tree Rd

Fargo
ND
58103
United States

Product Line : Microsoft Dynamics NAV Business Ready
Product Edition : Unspecified
Country : United States
Language : English (US)
Created Date : 2/16/2011 12:36:11 PM (-08:00)
Expires : 2/13/2021
Configuration : Demo_W1_AM
****************************************************************************
Name Amount
—————————————————————– ———-
1010 Foundation Layer 1
1150 Subsidiary / each 1
1200 NFR Sessions 2
1295 Microsoft Dynamics ERP Payment Service 1
1400 User IDs & Passwords 1
1410 Permissions 1
1421 Application Server Counter (hidden) 1
1520 Server – Windows NT (Intel) 1
1700 C/ODBC 1
1750 C/OCX 1
1800 C/FRONT 1
2000 Client Monitor 1
2010 Server – Microsoft SQL Server Option 1
2020 Per Database license 1
2110 Navision Version 3.xx 1
2120 Navision Version 4.0 1
2130 Navision Version 5.0 1
2140 Dynamics NAV 2009 1
3010 General Ledger – Basic General Ledger 1
3020 General Ledger – Allocations 1
3030 General Ledger – Budgets 1
3040 General Ledger – Account Schedules 1
3050 General Ledger – Consolidation 1
3070 General Ledger – Basic XBRL 1
3080 General Ledger – Change Log 1
3090 General Ledger – Intercompany Postings 1
3260 Sales & Receivables – Basic Receivables 1
3270 Sales & Receivables – Sales Invoicing 1
3280 Sales & Receivables – Sales Order Management 1
3290 Sales & Receivables – Sales Invoice Discounts 1
3310 Sales & Receivables – Alternative Ship-to’s 1
3320 Sales & Receivables – Order Promising 1
3340 Sales & Receivables – Shipping Agents 1
3350 Sales & Receivables – Sales Return Order Mgt. 1
3360 Sales & Receivables – Calendars 1
3370 Sales & Receivables – Sales Line Discount 1
3380 Sales & Receivables – Sales Line Pricing 1
3390 Sales & Receivables – Campaign pricing 1
3410 Sales Tax 1
3510 Purchases & Payables – Basic Payables 1
3520 Purchases & Payables – Purchase Invoicing 1
3530 Purchases & Payables – Purchase Order Management 1
3540 Purchases & Payables – Purchase Invoice Disc. 1
3550 Purchases & Payables – Requisition Management 1
3560 Purchases & Payables – Alt. Order Addresses 1
3570 Purchases & Payables – Purchase Return Order Mgt 1
3580 Purchases & Payables – Purchase Line Discount 1
3590 Purchases & Payables – Purchase Line Pricing 1
3760 Application Wide – Multiple Currencies 1
3770 Purchases & Payables – Drop Shipments 1
3780 Application Wide – Salespeople/Purchasers 1
3790 Application Wide – Intrastat 1
3800 Application Wide – Extended Text 1
3810 Job Queue 1
4010 Inventory – Basic Inventory 1
4020 Application Wide – Multiple Document Languages 1
4040 Inventory – Multiple Locations 1
4045 Inventory – Stockkeeping Units 1
4050 Inventory – Alternative Vendors 1
4060 Inventory – Bills of Materials 1
4100 Inventory – Location Transfers 1
4110 Inventory – Item Substitutions 1
4120 Inventory – Item Cross References 1
4130 Inventory – Nonstock Items 1
4140 Inventory – Item Tracking 1
4150 Inventory – Item Charge 1
4160 Inventory – Cycle Counting 1
4170 Inventory – Bin 1
4220 Inventory – Standard Cost Worksheet 1
4230 Inventory – Analysis Reports 1
4240 Inventory – Item Budgets 1
4260 Resources – Basic Resources 1
4270 Resources – Capacity Management 1
4290 Resources – Multiple Cost 1
4510 Jobs 1
4540 Jobs Suite 1
4760 Application Wide – Basic Dimensions 1
4770 Application Wide – Reason Codes 1
4780 Advanced Dimensions 1
5010 Cash Manager – Bank Account Management 1
5020 Cash Manager – Check Writing 1
5030 Cash Manager – Bank Reconciliation 1
5110 CRM – Contact Management 1
5120 Relationship Mgt. – Contact Classification 1
5130 Relationship Mgt. – Campaign Management 1
5140 Relationship Mgt. – Opportunity Management 1
5150 CRM – Task Management 1
5160 CRM – Interaction/Document Mgt. 1
5170 Relationship Mgt. – Contact Search 1
5180 E-mail logging for MS Exchange 1
5195 Outlook Client Integration 1
5260 Fixed Assets – Basic 1
5290 Fixed Assets – Allocation 1
5300 Fixed Assets – Reclassification 1
5410 Basic Manufacturing – Production Orders 1
5420 Production Bill of Materials 1
547 AM Demonstration Granule 1
5980 Connector for Microsoft Dynamics 1
6010 Capacity Planning – Basic 1
6040 Capacity Planning – Production Schedule 1

7110 Report & Dataport Designer 1
7120 Form and Page Designer (includes 100 Pages & Forms) 1
7130 Table Designer 1
7140 XML Designer 1

9000 Role Centers-(DUP)2 1
9100 Dynamics NAV Server 1
99004710 Euro Conversion Tool 1
Company 100,000,000
Country Code: W1 1

分类: C/AL, Development, Training 标签:

NAV 2009 – Course 80258 – Trade – 课程2

2013年2月1日 没有评论

培训时间: 2013年01月31日 晚20:00 – 21:30
培训地点: YY频道 40215226
培训内容: NAV 2009 – Course 80258 – Navision Trade II

视频:

课堂大纲

Trade – II

Purchase Order

基础设置和配置

Setup
常规
设置各种选项(包括选项和开关)

编号号码规则

Master Data
供应商

物料

采购价格

采购模块的设置

业务:

PO
1. 新增订单, 选择供应商
2. 输入订单行 (选择物料, 仓库, 数量, 核实价格)
3. 确定PO(Confirm) –> Released (如果需要,可以启用审批流程)
4. 收货–>开发票

Quote

Blanket Purchase Orders

Drop Shipment & Special Order的介绍
3方贸易( A贸易公司, C, 客户, V, 供应商)
V –> C (货物流转) V –> A –> C (单据流转)

Special Order
关联关系的记录. 与货物的流转/单据流转无任何直接关系.

查询:
供应商的查询(余额, 未入库订单, 未到发票订单)
单据的查询 ( 采购历史记录)
余额追踪(Navigate)

采购申请
申请部门填写.
采购部具有(Report 493的权限), 就可以完成采购申请转采购订单的动作.

采购的解决方案
供应商库存查询.
员工-供应商解决方案. (Reqlogic – Web 采购申请/费用入帐申请. NAS –> 对应员工的供应商明细账. 应付账款)
Sugest Payment –> eBank Interface –> Bank interface import
Posting and email

分类: Training 标签: