Reason codes in Dynamics AX 2012 for Retail are very powerful possibly at the same time flexible way of collecting traveler during sales process at POS terminal. It can be used any sort of BI-related analysis requested, for example, by Marketing department.
To create a reason code, go to Retail->Setup->Reason codes.
Each reason code will need turn out to be assigned input type. There are several input types available:
I would encourage you to read online help using this form as it gives very good explanations for each brand.
I think the most powerful one is Sub code buttons type. For example, when one item is put in a transaction a popup message would show up asking a store associate if shipping charge item needs to become added. If the answer is Yes, then shipping item is automatically added to the sales transaction. If the reply is No, then no actions are played out. This can greatly simplify sales entering process for non-stocked products and eliminate human error when shipping was accidentally forgotten.
Now let's speak about different trigger actions for codes to pop up. Reason codes can be assigned to:
Let's consider several examples.
When you attach a reason code for item, it are displayed on POS screen when this item is enhanced a sales transaction. This could be useful for items have to have buyer's age thank you.
To attach a reason code to an item, go to Product information management->Common forms->Released products, Retail tab and go to reason codes button. From here you will be able to choose from one of the present codes and as appropriate modify default input parameters:
When you fasten a reason code in order to some customer, it tend to be displayed on POS screen when this customer is uploaded to a sales settlement. For example, reason code can remind store associate to verify shipping address or whether or not sales receipt must be emailed or just printed.
To attach a conclusion code to an item, go to AR->Common forms->All customers, double click of the customer you need to modify, select Retail tab and click Reason codes mouse.
When you attach reason code to payment method, daily schedules displayed on POS screen when this payment method is used to complete sales transaction. For example, the retail store may accept checks and they will be going to authorized using third part processing system that will return an authorization code at the end of successful consent. You may want to capture this code when check payment is accepted, the actual reconciliation process easier for head office employee. That is the reason why you may want to create a reason code with input type Text and attach it to store payment method. To try and do this, go to Retail->Common forms->Retail channels->Retail stores, Set up tab, Payment methods button and then click on Reason codes button:
And finally, area that it hurts that is used to attach reason codes to a big list of predefined trigger actions can be available on Functionality profile state. Functionality profiles are assigned to retail stores and among issues used for reason code assignments for one more trigger actions:
To open functionality profile form, pay a visit to Retail->Setup->POS->Profiles->Functionality profiles.
As you understand you can attach reason codes an extra shot transactions, price overrides and even originally and end of each transaction among more.
There are several key parameters that define the behavior any specific given reason code:
print either prompt, input or input name on sales receipts
specify the frequency with which reason code will pop under as well as weather input is reqired
max/min values allowed as inputs
Keep from heart that only prompt and not description of any reason code will show on POS screen.
Once precisely why code shows on POS and input is typed in, cause why code transaction is recorded in POS database. Then P-1001 is executed which transfers all POS transaction (including reason code ones) to AX database. That is when you can review them by likely to Retail->Inquiries->Transactions, click Transactions button and select Reason code transactions. Bear in mind that only transaction with type Sales and Customer order can have reason codes attached.
The table that holds these records in AX database has the name Retail Transaction Info code Trans.
That is all for as we speak. In my next post I for you to share my experience with setting up replenishment in AX. Some include creating replenishment rules and replenishment hierarchies as well as processing transfer orders made with buyer's push and cross-docking functions.