Differences

This shows you the differences between two versions of the page.

--- versago:payment_configuration_and_reports [2019/09/19 14:39]
runger [To Begin]
+++ versago:payment_configuration_and_reports [2020/11/04 11:19] (current)
dlee
@@ Line 26: / Line 26: @@
   * Click on the “Payment Setup” link in the Admin console to begin.
-{{:versago/payments1.png?576x208}}
+{{  :versago/payments1.png?576x208  }}
   - Select the appropriate **Payment Gateway** from the drop-down list.
@@ Line 33: / Line 33: @@
   - Enter the **Merchant Login** provided by your gateway.
   - Enter the **Merchant Password** provided by your gateway.
-  - Select the payment method(s) you wish to accept.  \\ \\ <WRAP center round important 50%>
+  - Select the payment method(s) you wish to accept.  \\ \\ <WRAP center round important 100%>
 Be sure the checkbox is cleared if you do not want to accept a payment method. In the illustration above, American Express is not accepted and will not be presented as an option for the user.
 </WRAP>
   - Click the Demo option during testing only. This option must be cleared for production operations.
-====== Mapping SAP Business One Values ======
-For the payment information in Versago to be processed into SAP Business One, some specific values must be defined. This is done using the “Versago Payment Info Mapping” form.
-{{:versago/payments2.png?576x298}}
-  - Click the look-up (funnel) icon in each credit card field to see a list of credit cards defined in your SAP Business One system.
-    - Select the card that matches the label on the field.
-    - The internal SAP code is displayed in the right-hand column.
-    - If you do not accept a particular type of card (Discover in this example), leave the field blank.
-  - Click the look-up icon in the “eCheck GL Account” field to select the appropriate GL account where bank transfers will be posted.
-    - The internal SAP code is displayed in the right-hand column.
-  - Enter the URL to your Bizweaver instance that will process the payments into SAP Business One.
-    - Be sure to include HTTP:%%//%% or HTTPS:%%//%% as appropriate.
-  - Enter the port used by your Bizweaver instance.
-  - Enter the Bizweaver workflow ID that will process the payments into SAP Business One.
-**Notes**
-  * Credit cards must be defined in your SAP Business One system before item 1 can be defined.
-  * The internal SAP codes are displayed for support purposes only. The user does not need to be concerned with them during the configuration process.
-  * Your system administrator should be able to provide you with the information needed for items 3 and 4.
-  * The workflow to process payments from Versago will need to be imported (or created) in Bizweaver before item 5 can be set. This value will be different for each installation.
-Once any of the codes have been defined and saved, the associated report, “Versago Payment Info Mapping” must be used to review and update values. The maintenance form will not allow more than one record to be created.
 ====== Payment Selection Report Setup ======
@@ Line 88: / Line 63: @@
 The “Record Submission” page is used to configure the report for record selection. When the “Enable Record Submission” checkbox is selected, additional configuration items are displayed.
-{{:versago/recordsub2.png?384x109}}
+{{  :versago/recordsub2.png?384x109  }}
 Also select the “Process Payments” option checkbox if this report will be used for accepting and processing credit card and eCheck payments.
@@ Line 94: / Line 69: @@
 Configuration of Record Submission reports for payments is described in the documents //Versago – Payments Setup//.
-See the [[record_submission_configuration|Record Submission Configuration]] page for detailed information on configuring the record submission information.
+See the //**[[record_submission_configuration|Record Submission Configuration]]**// page for detailed information on configuring the record submission information.
 ===== Calendar tab =====
@@ Line 112: / Line 87: @@
 Charts should not be used with Record Selection reports.
-====== Back End Processing ======
+====== Back-End Processing ======
 In a Versago environment, back-end processing is typically done using Bizweaver. The information here refers to Bizweaver but other process flow tools might be used as well.
@@ Line 118: / Line 93: @@
 Most record submission reports will have an associated Bizweaver workflow to handle additional processing. For payments this might be creating SAP Business One Incoming Payment transactions. Or it might be updating the status on a group of orders.
-There are two ways to initiate this processing. One is to have the Bizweaver workflow set on a schedule so that it executes periodically during the day. Second is to initiate the workflow when the submission is saved to the database. For the second option a database trigger is used.
+There are two ways to initiate this processing. The most basic approach is to have the Bizweaver workflow set on a schedule so that it executes periodically during the day.
-The SQL database needs to be initialized to allow triggered (immediate) processing to occur.  The initialization process is described **//[[bw:call_bizweaver_web_service_from_sql_server|here]]//**.
+The more sophisticated approach is to initiate the workflow when the submission is saved to the database. For the second option a database trigger is used.
-The following discussion assumes that you have some knowledge about database triggers and have access to the SQL Server tools needed to install them.
-===== Payments Processing =====
-A basic database trigger to initiate Bizweaver processing for payments will look like this.
-<code sql payments_trigger_sql.txt>
-CREATE TRIGGER [dbo].[twbs_tr_VersagoPayments]
-ON [dbo].[Versago_Payments]
-AFTER INSERT
-AS
-BEGIN
--- SET NOCOUNT ON added to prevent extra result sets from
--- interfering with SELECT statements.
-SET NOCOUNT ON;
---
-DECLARE
-@vgo_BatchID INT,
-@object INT,
-@url VARCHAR(5000),
-@bw_url nvarchar(100),
-@bw_WorkflowID int,
-@bw_port int,
-@pArgVariableName nvarchar(50)
---
-/* It may be necessary to change all instances of "vgoCommon" to a different name if you have used a different name */
-select
-t0.BW_URL, t0.BW_Port, t0.BW_WorkflowID
-from vgoCommon..twbs_vgo_payment_InfoMapping t0
---
-set @pArgVariableName = 'vgo_BatchID'
-select @vgo_batchid = (select vgo_batchid from inserted)
-select @bw_url = (select t0.bw_url from vgoCommon..twbs_vgo_payment_InfoMapping t0)
-select @bw_port = (select t0.bw_port from vgoCommon..twbs_vgo_payment_InfoMapping t0)
-select @bw_Workflowid = (select t0.BW_WorkflowID from vgoCommon..twbs_vgo_payment_InfoMapping t0)
---
-SELECT @url = @bw_url + '/BWService/api/workflow/InvokeWorkFlow?pTaskID=' + cast(@bw_WorkflowID as varchar) + '&pStartAfter=0&pArguments={' + @pArgVariableName + ':' + CAST(@vgo_BatchID AS VARCHAR) + '}'
-EXEC sp_OACreate 'MSXML2.XMLHTTP', @object OUT;
-EXEC sp_oamethod @object, 'open', NULL, 'get', @url
-EXEC sp_oamethod @object, 'send'SELECT @url
---select @responsetext as [Response]
--- select @url
-EXEC sp_oadestroy @object
-END
-</code>
-The following video illustrates this process.
-{{ :versago:versago_db_trigger_demo.mp4?800 |DB Trigger Demo}}.
-====== Reports Overview ======
-Two main reports are provided for users to review payment transactions and resolve issues. These reports are Versago Payments Recap and Payments Transaction Log. The standard location for these reports is in the ‘Payments Admin” menu category.
-====== Versago Payments Recap Report ======
-Detailed information about successful payment transactions can be viewed using the “Versago Payments Recap” report. This report displays details about each transaction, including invoices paid, information sent to the processing gateway, and the response from the gateway.
 <WRAP center round important 60%>
-This report utilizes a SQL View as the data source.  The View must be created manually in the database.  Code to create the View is provided below.
+The following discussions assumes that you have some knowledge about database triggers and have access to the SQL Server tools needed to install them.
 </WRAP>
-Create the view in the **VersagoData** database (or whatever database name you may be using to capture Versago form data).
+The SQL database needs to be initialized to allow triggered (immediate) processing to occur.  The initialization process is described **//[[bw:call_bizweaver_web_service_from_sql_server|here]]//**.  Examples of the trigger used to initiate Bizweaver processing are then found in the lower section of the page.
-<code sql>
-CREATE view [dbo].[vgo_vw_PaymentTransactions] as
-select distinct
-t0.vgo_transid,
-(select sum(x0.BalDue) from Versago_Payments x0 where x0.vgo_transid = t0.vgo_transid group by x0.vgo_transid) as [TtlAmtPaid],
-CASE t0.vgo_paymenttype
-when 1 then 'Credit Card'
-when 2 then 'eCheck'
-END as [TransType],
-cast(t0.vgo_paymentdate as date) as [vgo_PaymentDate],
-(select count(*) from Versago_Payments x0 where x0.vgo_transid = t0.vgo_transid) as [DocCount],
-t0.vgo_PostingStatus, t0.vgo_PostingDate, t0.vgo_PostingId
-from Versago_Payments t0
-</code>
-Use the [[#payments-transaction-log-report|Payments Transaction Log]] report for information about unsuccessful transactions.
-===== Versago Payments Recap – Main Report =====
-{{:versago/payments3.png?700}}
-  - Expand the row to see a list of invoices paid.
-  - The “SAP Posting Status” indicates if the transaction has been posted into SAP Business One.
-    - “0” indicates that the transaction has not been processed.
-    - “1” indicates that the transaction has been posted successfully.
-    - “9’ indicates that the transaction posting failed.
-      - Click on a “9” to see the reason the SAP posting failed.
-{{:versago/payments4.png?700}}
-  * Click the __Transaction ID__ link to view details of the transaction.
-===== Payments Log Sub-report =====
-{{:versago/payments5.png?700}}
-  - Click on the __CC Request__ or __eCheck Request__ link as appropriate to view the information that was sent to the gateway for processing.
-===== Payments Log Request (CC and eCheck) Sub-report =====
-{{:versago/payments6.png?700}}
-{{:versago/payments7.png?700}}
-===== Payments Response (CC and eCheck) Sub-report =====
-{{:versago/payments8.png?700}}
-{{:versago/payments9.png?700}}
-  * Click on the __Response__ link to view the information that was sent to back from the gateway.
-====== Payments Transaction Log Report ======
-The Payments Transaction Log report is like the Payments Processing Recap report, except that it shows both successful and unsuccessful transactions.
-Note that the “Transaction ID” for unsuccessful transactions begins with “E” followed by the log record ID, and the date & time of the transaction.
-{{:versago/payments10.png?700}}
-  - Click on the “CC Request” or “eCheck Request” link as appropriate to view the information that was sent to the gateway for processing.
-  - Click on the “Response” link to view the information that was sent to back from the gateway.
-In general, the “Response” information will be the most helpful for troubleshooting unsuccessful transactions since it shows the reason a transaction was rejected.

Wiki

User Tools

Site Tools

Differences

Page Tools