Address and Contact information logic on AR side

Address on the customer record can be of many types. Like Invoice, Delivery, Business etc. These types of addresses are called ‘Purpose’ in AX. There can be separate address for different purpose. Like an address setup for address purpose = Invoice, will be used by default by the system when the invoice is generated. However there can be more than one address types of the same purpose. Hence there can be 2 invoice types of address setup for the customer. How will the system know which one to use?? For this AX provides the option of the setting default. The default address setup against the purpose will be selected.

The delivery address can be changed as system gives the option to change the delivery address. However the system does not give the option to change the invoice address on sales order, as system picks it directly from the setup. The only way to change the address for a customer during invoicing is to go back to the customer record and change the default address for address type invoice. However the invoicing address can be changed on the project contract.

There is another concept of ‘primary’ which becomes the primary address for that customer record. There can be many address per purpose but out of all the addresses defined for that customer, only one can be termed as ‘Primary’ address. This will be available for selection wherever address is editable. Other than that there is no significance of this address.

On the project invoice / customer invoice, the contact information that appears is always the contact information defined on the Legal entity form, Contact fast tab and that too the contact records should be marked as primary or else they will not appear.

Similarly on the sales order invoice / project invoice, the contact id is the one which is selected on the sale order from the contact records set on the customer record.

Thanks

Sarang

Fixed Asset creation and acquisition

Fixed asset creation (manual or automatic) and acquisition (manual or automatic) has a logic running in the background based on the selections made in the FA parameters and FA section on the PO record. These selections determines whether the FA creation and acquisition should be manual and automatic. This is simplified and presented in the manner which makes it more understandable and all the scenarios are presented at one go.

Thanks

Sarang

Period type, Periods, Worker Periods and Time sheet Periods

This topic has always confused me a hell lot. Hence trying to put down in writing my observations, so that i do not have to re-invent the wheel every time. The steps are as follows:

1. You create a Period type of 'Week' type. (Organisation administration > Common > Calendar > Period type)
2. After the period type is created, you generate the periods. While generating the periods, do not check the 'Update worker periods' and 'Update timesheet periods' checkbox, so that you can then understand the concept more correctly.
3. Now the periods are created for the period type. However there are no employees attached to the newly created period type.
4. Create a new employee and navigate to the 'Project management' tab in the ribbon. Click on the 'Project setup' icon. Project setup form would open up.
5. In this form, select the newly created 'Period type' from the 'Period code' drop down.
6. With the selection of 'Period code' in step 5 against the worker, you would assume that the periods that are created for the selected period code are assigned to the worker. However that is not the case.
7. To verify click on the 'Period status' icon and you would find out that the grid is empty. The reason for this is that though the period type is assigned to the worker, however the worker is not yet updated with the periods created for that period type.
8. To do this, there are two ways, either to do it by clicking the 'Update worker periods' button in the 'Period status' form (which would just update if for the said worker) OR to do it by clicking the 'Update worker periods' button from the 'Period type' form. If it is done from the 'Period type' form, then the worker periods are updated for all the employees associated with that period code.
9. This setup till now, still does not allow the user to submit the timesheet, as the timesheet periods are still not created for the newly created 'Period code'. Click on the 'Show timesheet periods' and verify it for yourself.
10. To do that, click the 'Update timesheet period' button and generate the timesheet periods.

Conclusion:

This means that creation of period type, generation of periods for the period type and association of that period type with an employee DOES NOT mean that the periods that are created for the period type are associated with the employee as worker periods. User will have to associate the created periods to the employee as worker periods by clicking update worker period button. Similarly the timesheet periods have to be updated for the created period type.

Thanks
Sarang