Sage 100

The client just upgraded this weekend from 2016 Advanced to 2018 Premium using web services (before and after). While testing, web orders with a credit card will not import into Sage order entry. It will create the customer but times out before it can get the order in and they have it set to 10 minutes and still times out. All other type orders including order with a deposit (deposit field on totals tab) will go in fine. They can manually create a sales order with a CC pre-auth. They say Paya is installed. They checked the payment types to make sure it did not disappear on migration, they are now double-checking all the setup for web services between 2016 to 2018 installs. They even rebooted everything. I don't know anything about web services and racked my brain on possible problems. Does anyone have any ideas?

------------------------------
Kelly Sappington
DeRosa Mangold Consulting - Sr. Implementation Specialist
Kat Six, LLC
Elkhart IN
254-265-6736
------------------------------

By Web Services do you mean Sage's eBusiness Web Services (which has nothing to do with eBusiness Mgr) OR a custom one created by a developer (like CIMCloud, ROI, Certipro, xkzero, etc)? There seems to be 2 approaches. I don't know which one they use but hopefully either the attached PDF with the CC eBiz Web Service example or KB article link will help the developer.

1. Add the CC GUIDs to AR_CustomerCreditCard and SO_SalesOrderPayment separately (2 objects, 2 tables):
   
   
   • Paya pre-authorize the CC before it hits Sage.
   • Add the CC GUID info to AR_CustomerCreditCard table. Here is KB article 82352 on how to V/I import into there but same principle if your developer uses AR_CustomerCreditCard_bus object - How to import customer credit card GUIDs that exist in the Sage Exchange Vault
   • Create and save the Sales Order without adding payment info.
   • Update same Sales Order and connect to the SO Payments child object then to set and add the payment info including same CC GUID and other reqd Paya/SED Vault pymt fields. 
     
     
2. Set payment info directly from SO Payments object while adding the CC number/GUID (1 object, 2 tables)

1. • Create and save the Sales Order without adding payment info.
   • Update the same Sales Order and connect to the SO Payments child object, add the raw CC number to the Vault (unless it was Paya preauthorized already), set the CC GUID, update the rest of the reqd Paya/SED Vault pymt fields. Also for adding CC GUID to AR_CustomerCreditCard, set SaveCreditCard = Y and run the Add() method.
   • To this end, attached is a Sage doc called Sage100ERPCreditCardProcessing.pdf. The last 6 pages so are for eBiz Web Services and includes an example of creating / updating a Sales Order with CC pymt info.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------

Thanks, @Alnoor Cassim for the information. It is Sage's EBusiness Web Services without E-Business Manager.​ Worked perfectly fine in v2016. The steps you mention are they changes that need to be made between the versions? Not sure if it matters but they had E Biz Manager installed in v2016 and tested prior to upgrade that this was not used anymore anywhere and they were simply using web services so it was uninstalled prior to migration. I know it was not available in Premium.

------------------------------
Kelly Sappington
DeRosa Mangold Consulting - Sr. Implementation Specialist
Kat Six, LLC
Elkhart IN
254-265-6736
------------------------------

Original Message:
Sent: 08-18-2019 02:05
From: Alnoor Cassim
Subject: Prem 2018 and Web Services

By Web Services do you mean Sage's eBusiness Web Services (which has nothing to do with eBusiness Mgr) OR a custom one created by a developer (like CIMCloud, ROI, Certipro, xkzero, etc)? There seems to be 2 approaches. I don't know which one they use but hopefully either the attached PDF with the CC eBiz Web Service example or KB article link will help the developer.

1. Add the CC GUIDs to AR_CustomerCreditCard and SO_SalesOrderPayment separately (2 objects, 2 tables):
   
   
   • Paya pre-authorize the CC before it hits Sage.
   • Add the CC GUID info to AR_CustomerCreditCard table. Here is KB article 82352 on how to V/I import into there but same principle if your developer uses AR_CustomerCreditCard_bus object - How to import customer credit card GUIDs that exist in the Sage Exchange Vault
   • Create and save the Sales Order without adding payment info.
   • Update same Sales Order and connect to the SO Payments child object then to set and add the payment info including same CC GUID and other reqd Paya/SED Vault pymt fields.
     
     
2. Set payment info directly from SO Payments object while adding the CC number/GUID (1 object, 2 tables)

1. • Create and save the Sales Order without adding payment info.
   • Update the same Sales Order and connect to the SO Payments child object, add the raw CC number to the Vault (unless it was Paya preauthorized already), set the CC GUID, update the rest of the reqd Paya/SED Vault pymt fields. Also for adding CC GUID to AR_CustomerCreditCard, set SaveCreditCard = Y and run the Add() method.
   • To this end, attached is a Sage doc called Sage100ERPCreditCardProcessing.pdf. The last 6 pages so are for eBiz Web Services and includes an example of creating / updating a Sales Order with CC pymt info.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------