search
Twitter Rss Feeds
MicrosoftArticlesForumsGroups
C# .NET
VB.NET
Visual Studio .NET
ADO.NET
Xml/Xslt
VB 6.0
.NET CF
GDI+
LINQ
Deployment
Security
FoxPro
Silverlight / WPF
Entity Framework
RIA Services

Web ProgrammingArticlesForumsGroups
JavaScript
ASP
ASP.NET
Web Services

Non-MicrosoftArticlesForumsGroups
NHibernate
Perl
PHP
Ruby
Java
Linux / Unix
Apple
Open Source

DatabasesArticlesForumsGroups
SQL Server
Access
Oracle
MySQL
Other Databases

OfficeArticlesForumsGroups
Microsoft Excel
Microsoft Word
Microsoft Powerpoint
Publisher
Money

Operating SystemsArticlesForumsGroups
Windows 7
Windows Server
Windows Vista
Windows XP
Windows Update
MAC
Linux / UNIX

Server PlatformsArticlesForumsGroups
Share Point
BizTalk
Site Server
Exhange Server
IIS
Transaction Server

Graphic DesignArticlesForumsGroups
Macromedia Flash
Adobe PhotoShop
Microsoft Expression

OtherArticlesForumsGroups
Subversion / CVS
Ask Dr. Dotnetsky
Active Directory
Networking
Uninstall Virus
Job Openings
Reviews
Search Engines
Resumes

 

Previous Thread:   9084.1 Axapta calendar

9/17/2005 7:01:19 PM    10634.1 Item Dimension
I am newbie for Axapta 3.0v.  
  
Now we have a customer. They want to make four item attributes(dimension)  
  
color-size-treatment-packaging for a unique itemID.  
  
So that means itemID won't be able to create manually, I would coding on  
  
form\inventTable\datasource\inventTable\method\create, to stop 'Edit' and  
  
give customer a CREATE ITEM WIZARD.  
  
Because Axapta3.0v has standard item dimension(configuration-color-size).  
  
Can I take the advantange of this standard funcation, just create new  
  
field treatment and packaging, and Group this two field into Item  
  
Dimension??  
  
Customer finally wants to have bike(10)-red(02)-size 1(15)-treatment  
  
TT1(80)-Packaging UBM(25) as itemName, together hence ItemID would be  
  
1002158025 which created by my new Wizard.  
  
Project manager said I should create Item Attribute, not dimenstion for  
  
customer. Because each itemId would point to Price/Cost.  
  
In Stand Axapta 3.0v, itemId (Bike10) with different color/size would be  
  
the same price. (Or my project manager understanding wrong?), the  
  
itemId(Bike10) with special color/size should have different price. That  
  
is Attribute my project manger means............  
  
Big Problem for me. Because by my experience, I really can't handle this.  
  
Now I already create whole new system for project manager. four new table  
  
with all new extend data type, then four new tables  
  
colorgroup-sizegroup-treatmentgroup-packaginggroup which can let customer  
  
enter value. And also put Item Attribute in Inventory Management Set up.  
  
From there, you also can find Item Dimension and combination. Then I  
  
create a form for that Wizard to create new and unique ItemId.  
  
Then, obviously, other module like OLAP and CRM would not work on my Item  
  
Attribute.  
  
This item attribute would just work for Inventory Management and AR/AP....  
  
Terrible implementation by my understanding, But that is customer wants...  
  
Any guys here has good experience to handle this unique ItemId, and each  
  
dimension should attribute to price/cost???  
  
Thanks in advance for help.  
  
Posted on technet.navision.com on: Friday, August 13, 2004


Pete's Blog   |    Pete's Resume   |    Robbe's Blog   |    Robbe's Resume   |    Archive #2   |    Archive #3   |    Dotnetslackers   |    XmlPitStop   |    Advertise   |   Contact Us   |   Privacy   |   Copyright (c) 2000 - 2009 eggheadcafe.com  All rights reserved.