Need IMAN to create an on-hold order when customer is on hold (5 replies and 2 comments)
I think this depends on the Sage300 user you have set in the System Connector. If it has the ability to override the on hold status (like ADMIN does) then you can place the order. If it does not then an error occurs.
Have you tested this successfully? I changed the Sage 300 user to ADMIN and I'm getting the same results. I suspect the problem has to do with IMAN not being able to acknowledge the Warning message that pops up. In addition, if I sign in to Sage as the former integration user, I can still enter a Sage 300 order after I acknowledge the warning message.
Arline, this is working as expected per our response.
The customer is on hold, we go to create an order and the order is placed on hold.
If you have changed the user to ADMIN it should work.
If you either set a field to the SYS.ERROR field OR set Action on Transform Error to Abort can you see why the order is failing (there may be a different reason....like credit limit)?
Thanks
Here are my results. They still do not make sense to me.
I set Action on Transform Error to Abort, and that threw this error:
"1140 - Item number 062Xx3 does not exist."
This error does not make sense to me.
The value we feed to Sage is the Customer Item number.
While testing, I took the customer OFF hold, and the order was successfully created using the Customer Item Number.
I can also reproduce this in the UI, whether the customer is on hold or not, I can create an order by entering the customer item number in the Sage 300 item number field. Sage then translates that to the Sage 300 item value.
However, if with IMAN, I INSTEAD feed in the Sage 300 item number (rather than the customer item number), then I can successfully create an on-hold order, which is what I want.
But this automation ONLY uses the customer item number, so this is not a sustainable solution, I don't think.
I should also mention that IMAN has already processed hundreds of other orders with this integration, using the customer item number, for customers that are not on hold.
Can you help me understand why these two things are linked??
Following up - any thoughts on this?
Arline, after testing I can see the issue.
When a customer is on hold AND you use Customer Items when you enter the customer item number you get another error/message 'Customer is on hold'.
This is a consequence of the steps the Sage Views performs to translate the customer item number to the actual I/C Item.
The problem is that when a customer is placed on hold, the automatic translation of the customer item number performed in the view fails! When the customer is not on hold the translation works.
This is one of those rare cases where the logic in the Sage300 views probably needs a bit of refinement.
What Sage300 does is to manually convert the customer item code to the actual item code in the event of an error i.e. when the customer is on hold.
We could try to replicate this behaviour in the connector, but my recommendation would be to implement a workaround.
In a map transform prior to the Sage connector, do a lookup against the ICITMC to perform the translation and map the translated value to the Item field in Sage.
Hope this helps.
Gotcha- thank you.
Hi there,
I'm trying to get IMAN to do what I can already do in the Sage UI: acknowledge a Warning message that the Customer is on hold, then create an order in Sage 300.
Instead, IMAN processes the Sage 300 transaction, logs the ORDNUMBER value as '' and then logs that "Job has completed successfully." So, essentially it fails silently. We caught this because we then log the Sage 300 ORDNUMBER value and write it back to a staging table.
How can I use the Sage 300 connector to acknowledge/close the Warning message, and create the on-hold order?