OrganicAX

If you are setting up items for a legal entity you might have a lot of items to release. So you might want to consider releasing them in batch. This way the server can do the work and you can get on and do other things. However if something goes wrong you might want to review the error message. This is where the open product releases form comes in to play. I will give you items that error if they can’t be released and you can review the infolog to see what the message might have been. Here...

When working with suppliers sometimes you might want to value a relationship over price if the quality or the delivery performance is good. When setting up an RFQ you might want to setup a evaluation criteria that can allow you to capture some data beyond just the price. You can setup your own criteria with the scoring method. Then you can use this to update the bid entries with your internal data. Here is a quick overview AX2012 R3 CU11 Cheers Lachlan Filed under: Procurement and...

The following code changes are made in the merged objects. It’s probably more efficient to add these manually without going through the trouble of trying to merge into you environment and there are only four objects to modify with some minor changes. VendTable. There changes to the VendTable are minimal with the addition of a new field. First modify the VendTable. There is a new field here called cXMLOrderEnable which is based on the EDT cXMLOrderEnable which is included in the CXMLPurchaseRequest...

Working with a number of customers using both punchOut and having a need to send purchase orders I’m sharing some sample code that you can leverage to add automation to your AX2012 environment for sending purchase orders to suppliers. I’ve released a follow-up to the cXML PunchOut Protocol Handler for AX2012 R3 with the addition of a purchase order sending capability. You can find the sample code here https://ax2012r3cxml.codeplex.com/releases/view/630625 If you are working in procurement...

There are times where data might not be formatted correctly or wrong data provided that will cause a purchase to be returned from the supplier. The supplier will often return an message that will give you an indication of what data is incorrect. This could be a missing part number, wrong contact information, missing address information for example. The purchase request form will allow you to see the errors. You can see and filter on the orders that have been return with an error and then address...

There is a purge function provided on the purchase request form that will allow you to remove the history. As the send status is a record of what you have communicated to a supplier you probably don’t want to just delete it. But you will need to clean up the amount of records you are storing live in the database to avoid growing the database unnecessarily with old data. You will need to provide a path and file name in the cXML parameters form. When you use the purge button it will take the...

When you are setting up the purchase send functionality you might want to test the generation of the XML documents before sending them to the suppliers. There is a function provided on the purchase request form that you can use to generate the cXML which will allow you to review. This is handy if you have turned off the live send in the cXML parameters and don’t have the batch job running and just want to generate the output for one purchase order. Here is a quick overview AX2012 R3 ...

The pre-requisite to the cXML Purchase Request send capability is the cXML PurchOut Protocol Handler that you can find details here . You can find the code here https://ax2012r3cxml.codeplex.com/releases/view/630625 For the purchase request send there are two projects. One is a project with just new objects and the second is a project with objects that you will have to merge as they touch existing AX objects. The assumption is you know how to create a model file, label file and import XPO...

When using the purchase send functionality there maybe times where an order is confirmed and you might want to stop it from being sent to the supplier. Or an order was return with an error message and you want to re-submit it. There are two functions provided on the purchase request form that you can use to control this. Here is a quick overview AX2012 R3 Refer to this post for an overview of the cXML Purchase Order Send. https://organicax.com/2017/02/08/cxml-purchase-order-request...

The purchase order send makes use of a batch job so the user isn’t waiting when they confirmation the purchase order. The batch job will update the status in the purchase request form so you can review this for sending status and if there are errors returned from the supplier. Here is a quick overview. AX2012 R3 Refer to this post for an overview of the cXML Purchase Order Send. https://organicax.com/2017/02/08/cxml-purchase-order-request-send-ax2012-r3-v1/ Cheers Lachlan...

If you are looking to use the cXML Purchase Order send then you will need to enable a parameter on the vendor which will default to the purchase order for it to be picked up. This parameter is assessed when the purchase order is confirmed. Here is a quick overview AX2012 R3 Refer to this post for an overview of the cXML Purchase Order Send. https://organicax.com/2017/02/08/cxml-purchase-order-request-send-ax2012-r3-v1/ Cheers Lachlan Filed under: Procurement and sourcing ...read...

There are a few parameters that you can leverage to enable functionality for sending and archive of the purchase order request. Here is a quick overview of the existing parameters. AX2012 R3 Refer to this post for an overview of the cXML Purchase Order Send. https://organicax.com/2017/02/08/cxml-purchase-order-request-send-ax2012-r3-v1/ Cheers Lachlan Filed under: Procurement and sourcing ...read more

I posted a small update to the AX2012 R3 cXML protocol handler for punchOuts. This update you can find up on codeplex here http://AX2012R3cxml.codeplex.com This updates includes some extra error handling for the punchOut setup request response from suppliers. Please refer to my original post with setup details on how to use the cXML protocol handler sample code. While working with customers implementing cXML based punchOuts with AX2012 the following suppliers were used in the US. If you are working...

In a previous post we had a look at changes on sales return disposition codes. I had a question the other day about how to setup a tiered set of charges based on original sales date to set a restocking fee. Unfortunately there isn’t a date trigger on the disposition code or charge codes in standard AX. If for example you have a 20% re-stock fee after 30 days and a 40% stock fee after 60 days then you could setup two charge codes and two disposition codes and then the operator could pick the...

If you are working with planning and sourcing materials then you might on occasion have the need to use an RFQ to see if a product can be sourced differently from multiple suppliers. There is an option to change a planned purchase into a request for quote when reviewing the planned orders. This will then follow the RFQ and when a vendor is selected then a purchase order would be created from the RFQ. Here is a quick overview. AX2012 R3 CU11 Cheers Lachlan Filed under: Procurement and...