Internal Item Requisition In Ax 2009

-
Problem : Design a Internal Inventory Requisition

Solution : We design a solution to cater the need of Inventory Internal Requisition from the Store to a department with self designed Workflow.

Steps We follow.

1. Create Inventory Movement Journal to hold Requisition Information with Date and Creator ID.
2. Send Intimation to Approver to approve the Requisition Information after submit status of the creator.
3. When Approver approves then send it to Store/Dispatcher to take action and record the delivered qty to creator.
4. Now Creator will get the items and confirm the receiving.
5. ........

Please contact : 0923328244088 for full details.

Arif 

Comments

Post a Comment

Popular posts from this blog

How to import data in Ax2009 from a CSV file

-
In Microsoft Dynamics AX 2009, importing data from a CSV file can be done through the Data Import Export Framework (DIXF) , AIF (Application Integration Framework) , or by using X++ code to handle custom imports. Here's a step-by-step guide to importing data from a CSV file: Method 1: Using AIF (Application Integration Framework) AIF is commonly used for integrating external data in AX 2009. Here's how you can use it to import data from a CSV file. Step 1: Create an AIF Service Define an inbound port for the data import: Navigate to Basic > Application Integration Framework > Channels . Create a new channel for importing the CSV file, specifying the necessary details. Create a Data Service : Go to Basic > Application Integration Framework > Services . Add a new service or choose an existing one that handles the type of data you want to import (e.g., purchase orders, vendors). Setup File Adapter : Go to Basic > Application Integration Framework > Adapters . U...
For More Details »

July 2017 update: Form Adaptors Replaced by Type Providers

-
The July 2017 update of Microsoft Dynamics 365 for Finance and Operations, Enterprise edition includes many new features and changes. One of our new features is  type providers . Type providers are a new way to interface with forms in unit tests without a form adapter model. Previously, when a developer built or changed a form they would also have to add the adapter for the form to the same solution and rebuild the model to see the new form changes in test code. Type providers provide instant design time support, so that tests can access forms. With type providers, we have removed the need to maintain a form adapter model and the need for extra compile time to generate and compile the form adapter model. We removed the form adapter models in the July 2017 update because they are expensive to run and maintain. In general, the type provider framework requires less processing time, and is more flexible to use than the form adapter models.
For More Details »

X++ to C# Comparisons

-
Differences The following table lists X++ features that are different in C#. Feature X++ C# Comments Declarations All declarations must be at the start of the method, before any X++ statements. Declarations can occur anywhere in the method. Both languages permit multiple variables of the same type to be listed together in one declaration. Both languages allow you to assign an initial value in the declaration statement. if  and  else conditional statements The  if  statement accepts any type of expression that it can automatically convert to a Boolean. Common examples include an  int  for which 0 means false, or an object for which null means false. The  if  statement requires a Boolean expression. The syntax structure regarding curly braces and parentheses is exactly the same between X++ and C#. Literal string A literal string can be delimited by either of the following: A pair of double quotation mark (") characters. A pair of singl...
For More Details »