Sage 100

Upgrading SAGE 100 STD from version 4.40 to v2017. Client uses credit card processing. In v2017, in the AR_CustomerCreditCard file there is a new field called ""CreditCardID"" (I think in AR Customer maintenance it's called ""Payment ID"") its 10 characters. What does the conversion program populate this new field with? Or does it leave it blank?

Why do you ask?

I did a test upgrade from v4.40 to v2017. I stripped out all the customer credit card records in v4.40 to make the test conversion not have to deal with uploading to the SAGE Vault, etc. Now I'm ready to perform the migration and conversion of the live data. The client has 1,260 customer credit card records in v4.40. During testing the client asked what 10 character codes should be used for the Payment ID/CreditCard ID when they set up a new customer credit card record in the file AR_CustomerCreditCard file. I told them they could develop their own coding scheme using 10 characters. I'm just trying in advance to know what the SAGE conversion program is going to do with that field.

It's been this way since v2013. I'm 68% certain Conversion does NOT populate CreditCardID (which is also in many other related tables as well) but that's not being 100% sure. Notice the CreditCardID is never part of a primary key in AR_CustomerCreditCard, SO_SalesOrderPayment, SO_SalesOrderHistoryPayment, and other tables using CreditCardID. FWIW having dealt with a customer who by themselves created their own coding scheme of using only the Last 4 digits of card, I recommend you do the finger wag and get more specific with them so you don't have to change it later in the future. In my case the Last4 turned out to be not granular enough as it caused a problem with an integrated application that was creating SPS payment authorizations. Long story short, I gave them attached Sage CC Processing PDF and pointed out Sage's example of using PaymentType + space + Last4 as the suggested CreditCardID. They agreed to that.

@AlnoorCassim This pdf document is exactly what I was looking for. Thanks for your weekend help!

Anyone know if a more recent version exists of that CCP doc @AlnoorCassim posted? It's from Nov '13 and I know Sage has made some CCP-related changes since then.

I'll continue to look for an update. What I found so far is Sage 2013 related but that is also when the vault and exchange came into use so they may not have updated the doc since.

UPDATE: Performed the final data migration and conversion from SAGE 100 STD v4.40 to v2017. The 1,260 credit card records that were stored in v4.40 were migrated into v2017 AND the SAGE conversion program assigned a ""PaymentID/CreditCardID"" of MC + Asterisk + Last4 for MasterCard cards and AMEX + Asterisk + Last4 for American Express, DISC + Asterisk + Last4 for Discover, VISA + Asterisk + Last4 for VISA cards and CC + Asterisk + Last4 if the payment type was ""Credit Card"". Nice work SAGE Software, this makes perfect sense.

Hmm I wonder if that changed in v2017 to populate CreditCardID on conversion. But it used PaymentType + Asterisk + Last4. Different from the example in their doc which used the space instead of asterisk. I don't like inconsistency.

@AlnoorCassim ... I changed my comment above to match what you said. SAGE did change from inserting a space to the "" * "".