Quote's and Sales orders (Source Type 143) are ignored when transaction consolidation in on

Quote's and Sales orders (Source Type 143) are ignored when transaction consolidation in on

*********************  For Internal use for Citixsys  ***********************

Version

6.5 and not the version-specific

Issue

Quote's and Sales orders (Source Type 143) are ignored by the iVend API (GetQueueWithoutStatusUpdate()) when transaction consolidation is turned on.

Resolution

Transaction Rollup (consolidation) is configured in this case. While taking into consideration Sales Order for eg “SOCON0011845” (Transaction Key – 4000000000045255), if you check table named ConTrxTransactionMapping and run SQL query “Select * from ConTrxTransactionMapping where TransactionKey = 4000000000045255” this will return the record and will show IsConsolidated flag = 0 that clearly specifies transaction is not part of any consolidation but it will be integrated with ERP not with TransactionKey=4000000000045255 but with ConsolidatedTransactionKey=900000000000000016

Below are the screenshots for the same:

Select * from ConTrxTransactionMapping where TransactionKey = 4000000000045255


If we check the database we could see ConsolidatedTransactionKey has already been integrated into your ERP:

SQL Query –
Select * from RepIntegrationLog where SourceKey = 900000000000000016


So when searching for this transaction in ERP then look for the "900000000000000016" not for the 4000000000045255.

Means Consolidation Key = 900000000000000016 will be used as TransactonKey in ERP, not the actual transaction key 4000000000045255 (which is in iVend).

Note: This is true in the case of Consolidation only, if Consolidation is not enabled then transaction key 4000000000045255 itself will be used.



    • Related Articles

    • How to break consolidation into inidividual transaction.

      Environment: iVend Version 6.6 with SAPB1 9.2 Problem Statement: How to break consolidation into individual transaction. Symptoms: Not Applicable Resolution/Work Around: Before performing Break Consolidation, please ensure the following points are ...

    • iVend Retail- Transaction Roll-up

      iVend Retail – Transaction Rollup The Transaction Rollup feature is used to reduce the volume of transactions integrated into an ERP. It is recommended to use this feature when transaction volumes are large. Note: In this article we will use SAP ...

    • Query to verify Sales Transaction by Store report (Refund included)

      ************************************Internal to Citixsys**************************************** Problem Statement SQL Query to verify results of default iVend report "Sales Transaction by Store report (Refund included) " Solution Below query can be ...

    • Transaction Rollup/Consolidation "Could not save the business Object"

      Environment: iVend Version 6.6 7747 with SAPB1 9.2 Problem Statement: While enabling transaction Roll-up in the iVend Enterprise. It displays the error message on screen “Could not save the business Object”. iVend Enterprise MC Log file displayed the ...

    • Query used to found Sales Difference between iVend & SAP in Consolidation

      *******Internal to CXS Support*********** Environment : iVend 6.6 integrated With SAPB1 Problem Statement : Sales Difference between iVend & SAP against particular date transacation.Customer is using Transaction consolidation. Symptoms: NA ...