1) The following code is used to display the current user Name .
display Name userName()
{
return XUserInfo::find(false, curuserid()).Name;
}
Friday, April 1, 2011
display the current user Name
1) The following code is used to display the current user Name .
display Name userName()
{
return XUserInfo::find(false, curuserid()).Name;
}
display Name userName()
{
return XUserInfo::find(false, curuserid()).Name;
}
line numbers in the form
1) In order to generate the line numbers in the form insert the following code in the table insert method:
void insert()
{
LedgerBalColumnsDim lbColumnsDim;
;
if (this.Column == 0)
{
select maxof(Column) from lbColumnsDim
where lbColumnsDim.BalanceSheet == this.BalanceSheet;
this.Column = lbColumnsDim.Column + 1;
}
super();
}
Take the same table instance that is used in the form datasource.
void insert()
{
LedgerBalColumnsDim lbColumnsDim;
;
if (this.Column == 0)
{
select maxof(Column) from lbColumnsDim
where lbColumnsDim.BalanceSheet == this.BalanceSheet;
this.Column = lbColumnsDim.Column + 1;
}
super();
}
Take the same table instance that is used in the form datasource.
What’s New in DYNAMICS AX 2012 OR AX 6.0 NEW COOL FEATURES?
As you all know this year (2011) Microsoft is planning to release Dynamics Ax 2012 or famously called as Ax 6.0. So what we can expect in this new version, have a look below
1. Shift away from AOD files to a SQL Server-based model store, model files (.axmodel), the perception of "parallel layers" using models, the command-line utility AXutil to manage manage models and model files as well as the graphical Model Management tool for managing models and model files.
2. Setting up security in Microsoft Dynamics AX using the new role-based security model. Wherein you will define the security artifacts in the AOT and creating security policies.
3. In Current version DAX 5.0 Configuration of Microsoft Dynamics AX2009 Role Centers and analysis cubes required a BI developer. In AX 6.0, setup and configuration of Analysis cubes can be done by a customer/partner with a wizard driven interface without having to go into BI development studio.
4. New eventing feature will be available in Microsoft Dynamics AX, it can be used to decouple publishers and subscribers, alleviating many upgrade issues.
5. Element IDs (such as table and class IDs) have been a problem since Microsoft Dynamics AX1 because they are limited to small ranges and often results in conflict between solutions. This, however, is changed in Microsoft Dynamics AX6.
6. A lot of Workflow enhancements has been done in Ax 6.0, wherein user will configure the workflow the way one creates flowchart in Visio.
7. Layout guidelines to support which language(X++ or .Net) or development environment (Visual studio or Morphx) to choose while doing customizations or developments. So guys/gals please make yourself updated with C# development.
8. Tool available to Convert Reports developed in X++ to SSRS Report!!! And also the way used to deploy the SSRS Reports has been changed.
9. New enhanced X++ editor with lots of colored indentation, intellisense features and code formatting!!
10. New Reporting programming model based on RDP which provides more control over data and UI design.
Prepare yourself to upgrade/development battle and enjoy new version once it reaches market!!!!
1. Shift away from AOD files to a SQL Server-based model store, model files (.axmodel), the perception of "parallel layers" using models, the command-line utility AXutil to manage manage models and model files as well as the graphical Model Management tool for managing models and model files.
2. Setting up security in Microsoft Dynamics AX using the new role-based security model. Wherein you will define the security artifacts in the AOT and creating security policies.
3. In Current version DAX 5.0 Configuration of Microsoft Dynamics AX2009 Role Centers and analysis cubes required a BI developer. In AX 6.0, setup and configuration of Analysis cubes can be done by a customer/partner with a wizard driven interface without having to go into BI development studio.
4. New eventing feature will be available in Microsoft Dynamics AX, it can be used to decouple publishers and subscribers, alleviating many upgrade issues.
5. Element IDs (such as table and class IDs) have been a problem since Microsoft Dynamics AX1 because they are limited to small ranges and often results in conflict between solutions. This, however, is changed in Microsoft Dynamics AX6.
6. A lot of Workflow enhancements has been done in Ax 6.0, wherein user will configure the workflow the way one creates flowchart in Visio.
7. Layout guidelines to support which language(X++ or .Net) or development environment (Visual studio or Morphx) to choose while doing customizations or developments. So guys/gals please make yourself updated with C# development.
8. Tool available to Convert Reports developed in X++ to SSRS Report!!! And also the way used to deploy the SSRS Reports has been changed.
9. New enhanced X++ editor with lots of colored indentation, intellisense features and code formatting!!
10. New Reporting programming model based on RDP which provides more control over data and UI design.
Prepare yourself to upgrade/development battle and enjoy new version once it reaches market!!!!
Tuesday, June 15, 2010
Small Code
static void DateUpdateJob(Args _args)
{
Table1 Table1;
date Condition_date;
Condition_date = Str2DateDMY("15/6/2010");
ttsbegin;
While select forupdate Table1 where Table1.DDate == Condition_date
{
Table1.DDate = Mkdate(13,03,2007);
Table1.update();
}
ttscommit;
}
{
Table1 Table1;
date Condition_date;
Condition_date = Str2DateDMY("15/6/2010");
ttsbegin;
While select forupdate Table1 where Table1.DDate == Condition_date
{
Table1.DDate = Mkdate(13,03,2007);
Table1.update();
}
ttscommit;
}
Friday, February 19, 2010
CRM and SRM
1.Customer Relationship Management
CRM is not a product, not even a suite of products,but a business philosophy that touches upon many independent parts of the organization
To speed customer acquisition, increase customer satisfaction and retention, and the company profit, it is necessary to develop a customer centric business model linking back and front office around the three pillars that are Sales, Marketing and Services.
CRM has mainly three goals:
i. Achieve higher revenues per customer by knowing and serving your customers better.
ii. Increase customer satisfaction and retention by integrating information from multiple channels stored in disparate systems.
iii. Lower costs to acquire and service customers by using technology to automate, manage, and analyze processes and data.
2. Supplier Relationhip Management
Definition of a SRM: “the practices needed to establish the business rules, and the understanding needed for interacting with suppliers of products and services of varied criticality to the profitability of the enterprise”....
SRM as the next generation of e-procurement or more specifically an integrated solution “that bridges product development,sourcing, supply planning, and procurement across the value chain”.
The same 3 pillars, adapted to a procurement perspective:
Marketing
Suppliers services
Purchase
In this case, marketing has to be understood as the mean to attract, filter suppliers, and
promote the company needs.
CRM, SRM needs to support the company-supplier relationship during its entire
lifecycle, meaning:
• Attract new suppliers: in a knowledge economy where goods can be produced anywhere around the world, finding the “best” supplier is becoming a complex task;
• Acquire new suppliers by doing business with them;
• Suppliers retention and development: retaining the best suppliers is the best warranty to
maintain a competitive edge;
• End of relationship by rejection or termination of contract: ending a contract with “bad”
suppliers is a necessary safeguard for the company and understanding why “good” suppliers are leaving is valuable information.
By opposition to CRM, SRM’s goal is to help the company to be a better purchaser by supporting and developing its understanding of suppliers. Some services can help the supplier directly or support its relationship with its own suppliers.
A SRM will therefore help the company gain the following competitive advantages:
1. Increase satisfaction of goods and services purchased and speed up product development by promoting a shared knowledge of suppliers and alternative technologies.
2. Increase supplier’s satisfaction to attract and retain the most competitive ones.
3. Lower prices for purchase and maintenance of goods and services by improving business processes across the supply chain.
Customer service and support:
CRM products are intended to support the company during its post-sale relation with its clients. Their goal is to help provide the best quality and most suited services at the lowest cost.
The SRM is pursuing the same objective, except that it is turned towards the inside (as developed in section 3) to collect and manage the information from all departments.
For example, when a problem is identified on a product - worker on a production line,customer, quality control…- the suppliers repository is updated by the call management unit and the incident is tracked.The procurement officer is automatically informed of the problem and contacts the supplier. The product line is adapted and the product design is perhaps modified to solve the problem. In the future, as the corporation has created a collective memory, this incident can have an impact on the adjudication when selecting a supplier.
Sales vs. Purchase:
The goal of this family of products is to automate the sales force or at least many of its tasks to improve their efficiency and reduce time and cost of sales.
Solutions to support the purchase of products or services are already common. Electronic catalogues, auctioning and electronic request for proposals (RFP) are only the last evolutions in a series of improvement since the 70’s. The SRM solution is the natural evolution of these as it integrates them with the rest of the procurement activities, especially product design and development.
Imagine a system,which could automatically adjudicate purchases for common goods, help prioritize needs and select the adequate purchase method: auction, catalogue, RFP.
Marketing (Marketing automation):
Marketing is at the center of any sales strategy. CRM support to marketing was therefore inevitable. In the contrary, the best warranty for a successful purchase is, for many purchase officers , the number of suppliers in competition. By promoting its needs using marketing techniques (single, multiplechannel campaigns) a company can attract as many suppliers as required. Company directories can also be used, but automated tools to search on the Internet for suppliers are now emerging.
In a CRM, they are primarily turn towards the outside of the company to respond to customer request. In a SRM, to collect information about your suppliers, you mainly search the information within the organization and not outside. SRM support tools are therefore
communicating internally although it can also provide communication channel with the outside to respond to specific suppliers requests concerning warranties,contract negotiation, delivery conditions and any other related question.
5. SRM inablers and inhibitors:
Implementing a SRM business philosophy in a company is not a simple matter especially as
“enterprises are not in the habit of looking to their internal procurement managers as the key to supporting customers”
CRM is not a product, not even a suite of products,but a business philosophy that touches upon many independent parts of the organization
To speed customer acquisition, increase customer satisfaction and retention, and the company profit, it is necessary to develop a customer centric business model linking back and front office around the three pillars that are Sales, Marketing and Services.
CRM has mainly three goals:
i. Achieve higher revenues per customer by knowing and serving your customers better.
ii. Increase customer satisfaction and retention by integrating information from multiple channels stored in disparate systems.
iii. Lower costs to acquire and service customers by using technology to automate, manage, and analyze processes and data.
2. Supplier Relationhip Management
Definition of a SRM: “the practices needed to establish the business rules, and the understanding needed for interacting with suppliers of products and services of varied criticality to the profitability of the enterprise”....
SRM as the next generation of e-procurement or more specifically an integrated solution “that bridges product development,sourcing, supply planning, and procurement across the value chain”.
The same 3 pillars, adapted to a procurement perspective:
Marketing
Suppliers services
Purchase
In this case, marketing has to be understood as the mean to attract, filter suppliers, and
promote the company needs.
CRM, SRM needs to support the company-supplier relationship during its entire
lifecycle, meaning:
• Attract new suppliers: in a knowledge economy where goods can be produced anywhere around the world, finding the “best” supplier is becoming a complex task;
• Acquire new suppliers by doing business with them;
• Suppliers retention and development: retaining the best suppliers is the best warranty to
maintain a competitive edge;
• End of relationship by rejection or termination of contract: ending a contract with “bad”
suppliers is a necessary safeguard for the company and understanding why “good” suppliers are leaving is valuable information.
By opposition to CRM, SRM’s goal is to help the company to be a better purchaser by supporting and developing its understanding of suppliers. Some services can help the supplier directly or support its relationship with its own suppliers.
A SRM will therefore help the company gain the following competitive advantages:
1. Increase satisfaction of goods and services purchased and speed up product development by promoting a shared knowledge of suppliers and alternative technologies.
2. Increase supplier’s satisfaction to attract and retain the most competitive ones.
3. Lower prices for purchase and maintenance of goods and services by improving business processes across the supply chain.
Customer service and support:
CRM products are intended to support the company during its post-sale relation with its clients. Their goal is to help provide the best quality and most suited services at the lowest cost.
The SRM is pursuing the same objective, except that it is turned towards the inside (as developed in section 3) to collect and manage the information from all departments.
For example, when a problem is identified on a product - worker on a production line,customer, quality control…- the suppliers repository is updated by the call management unit and the incident is tracked.The procurement officer is automatically informed of the problem and contacts the supplier. The product line is adapted and the product design is perhaps modified to solve the problem. In the future, as the corporation has created a collective memory, this incident can have an impact on the adjudication when selecting a supplier.
Sales vs. Purchase:
The goal of this family of products is to automate the sales force or at least many of its tasks to improve their efficiency and reduce time and cost of sales.
Solutions to support the purchase of products or services are already common. Electronic catalogues, auctioning and electronic request for proposals (RFP) are only the last evolutions in a series of improvement since the 70’s. The SRM solution is the natural evolution of these as it integrates them with the rest of the procurement activities, especially product design and development.
Imagine a system,which could automatically adjudicate purchases for common goods, help prioritize needs and select the adequate purchase method: auction, catalogue, RFP.
Marketing (Marketing automation):
Marketing is at the center of any sales strategy. CRM support to marketing was therefore inevitable. In the contrary, the best warranty for a successful purchase is, for many purchase officers , the number of suppliers in competition. By promoting its needs using marketing techniques (single, multiplechannel campaigns) a company can attract as many suppliers as required. Company directories can also be used, but automated tools to search on the Internet for suppliers are now emerging.
In a CRM, they are primarily turn towards the outside of the company to respond to customer request. In a SRM, to collect information about your suppliers, you mainly search the information within the organization and not outside. SRM support tools are therefore
communicating internally although it can also provide communication channel with the outside to respond to specific suppliers requests concerning warranties,contract negotiation, delivery conditions and any other related question.
5. SRM inablers and inhibitors:
Implementing a SRM business philosophy in a company is not a simple matter especially as
“enterprises are not in the habit of looking to their internal procurement managers as the key to supporting customers”
Wednesday, February 10, 2010
Project Management Life Cycle
Even this is not related to Axapta iam placing for knowledge sharing related to Project.....
Project Management Life Cycle
Project Management Life Cycle comprises four phases...
Initiation involves starting up the project, by documenting a business case, feasibility study, terms of reference, appointing the team and setting up a Project Office.
Planning involves setting out the roadmap for the project by creating the following plans: project plan, resource plan, financial plan, quality plan, acceptance plan and communications plan.
Execution involves building the deliverables and controlling the project delivery, scope, costs, quality, risks and issues.
Closure involves winding-down the project by releasing staff, handing over deliverables to the customer and completing a post implementation review.
Project Initiation
Project Initiation is the first phase in the Project Life Cycle and essentially involves starting up the project. You initiate a project by defining its purpose and scope, the justification for initiating it and the solution to be implemented. You will also need to recruit a suitably skilled project team, set up a Project Office and perform an end of Phase Review. The Project Initiation phase involves the following six key steps:
Project Planning
After defining the project and appointing the project team, you're ready to enter the detailed Project Planning phase. This involves creating a suite of planning documents to help guide the team throughout the project delivery. The Planning Phase involves completing the following 10 key steps:
Project Execution
With a clear definition of the project and a suite of detailed project plans, you are now ready to enter the Execution phase of the project.
This is the phase in which the deliverables are physically built and presented to the customer for acceptance.
While each deliverable is being constructed, a suite of management processes are undertaken to monitor and control the deliverables being output by the project.
These processes include managing time, cost, quality, change, risks, issues, suppliers, customers and communication.
Once all the deliverables have been produced and the customer has accepted the final solution, the project is ready for closure.
Project Closure
Project Closure involves releasing the final deliverables to the customer, handing over project documentation to the business, terminating supplier contracts, releasing project resources and communicating project closure to all stakeholders. The last remaining step is to undertake a Post Implementation Review to identify the level of project success and note any lessons learned for future projects.
Project Management Life Cycle
Project Management Life Cycle comprises four phases...
Initiation involves starting up the project, by documenting a business case, feasibility study, terms of reference, appointing the team and setting up a Project Office.
Planning involves setting out the roadmap for the project by creating the following plans: project plan, resource plan, financial plan, quality plan, acceptance plan and communications plan.
Execution involves building the deliverables and controlling the project delivery, scope, costs, quality, risks and issues.
Closure involves winding-down the project by releasing staff, handing over deliverables to the customer and completing a post implementation review.
Project Initiation
Project Initiation is the first phase in the Project Life Cycle and essentially involves starting up the project. You initiate a project by defining its purpose and scope, the justification for initiating it and the solution to be implemented. You will also need to recruit a suitably skilled project team, set up a Project Office and perform an end of Phase Review. The Project Initiation phase involves the following six key steps:
Project Planning
After defining the project and appointing the project team, you're ready to enter the detailed Project Planning phase. This involves creating a suite of planning documents to help guide the team throughout the project delivery. The Planning Phase involves completing the following 10 key steps:
Project Execution
With a clear definition of the project and a suite of detailed project plans, you are now ready to enter the Execution phase of the project.
This is the phase in which the deliverables are physically built and presented to the customer for acceptance.
While each deliverable is being constructed, a suite of management processes are undertaken to monitor and control the deliverables being output by the project.
These processes include managing time, cost, quality, change, risks, issues, suppliers, customers and communication.
Once all the deliverables have been produced and the customer has accepted the final solution, the project is ready for closure.
Project Closure
Project Closure involves releasing the final deliverables to the customer, handing over project documentation to the business, terminating supplier contracts, releasing project resources and communicating project closure to all stakeholders. The last remaining step is to undertake a Post Implementation Review to identify the level of project success and note any lessons learned for future projects.
Subscribe to:
Posts (Atom)
