- ERP System : Oracle, SAP
- MarkView Version: MarkView 9.0 and Below
- In certain scenarios when an invoice is created in the ERP System with a MarkView Attachment the data may not be immediately available in Advisor.
- Even though the sync between Markview and Advisor is realtime, sometimes it could take a minute or two to send a message from the ERP System using JMS queueing and for Advisor has to consume the message and populate the data. In addition, the report may not have been refreshed by the user to load the data.
If the invoice is still not appearing after several minutes and the report details have been refreshed please follow these steps in order to further troubleshoot the issue.
- The main data tables for invoices and workitems in the Advisor Schema are mvac_invoice and mvac_work_item, respectively. The first thing you can do is to check whether the invoice or workitem has made it into those message tables . If the data is in those tables, it could be that the invoice is there but does not have the correct payment status (if the payment message has not completed). This will cause invoices to appear in reports where they shouldn't, and knowing this will help pinpoint the ERP update that has not yet synchronized.ERP Specific Instructions
- If the invoice/workitems are not in the mvac_invoice and mvac_work_item tables the next thing to check is the mvam_event_message_sync table in the MarkView Schema (order the query by event_message_id). This table stores all of the message types sent from MarkView / your ERP System. Check the timestamp value in this table and it should be close to when you performed your actions. Some Message type examples would be InvoiceHeaderCreate , WorkItemTransition.
Note the event_message_id(s) that you think are relevant to your actions. Now using the event_message_id from request above, query the mvam_event_message_sync_detail table (MarkView Schema) to verify the detail contents of you messages. For InvoiceHeaderCreate message type some sample parameters should be like business-unit , invoice-id , user-id, etc
- Check the MarkView Advisor log files to see if the message was processed successfully. Please see the Logging section of for the location of the Advisor log files.
- If the Advisor log files show any invoice doesnt exist, workitem doesnt exist messages in the mvac- analytics-core log file for the invoice/workitem in question that means the invoice could have been deleted from the ERP System. If this is the case check to see if the invoice was deleted or cancelled in the ERP system.
- Customers Running SAP:
- Confirm that the MarkView Gateway is running. When the MarkView gateway is down the event messages are stored locally in SAP in tables /S170/MVAM_ETDTL and /S170/MVAM_ETVAL as name and value pair. Once the Gateway is up and the user tries to (complete a transaction) the data stored in tables /S170/MVAM_ETVAL and /S170/MVAM_ETDTL will be sent to MarkView which returns Y (successfully sent to MarkView) and N (unsuccessful). The entries in tables /S170/MVAM_ETVAL and /S170/MVAM_ETDTL are deleted if the return value is Y". Check if there are any records in those tables. If not, from an Advisor standpoint, you can likely rule out problems with the Gateway.
- Debugging the SAP Advisor Event Trigger using SE37 for the BKPF object in question may be necessary.
- Customers Running Oracle Applications:
- ?Ensure the MVAM* Triggers are enabled in the MarkView Schema
- If the above steps do not resolve the issue attempt to Restart your MarkView Middle Tier as well as the Advisor Queues. The Advisor Queues can be restarted with the following script (this applies to both Oracle and SAP):
set serveroutput on declare begin for rec in (select name from user_queues where queue_type = 'NORMAL_QUEUE') loop dbms_output.put_line ('Stopping queue ' || rec.name); dbms_aqadm.stop_queue( queue_name => rec.name ); dbms_output.put_line ('Starting queue ' || rec.name); dbms_aqadm.start_queue( queue_name => rec.name ); end loop; commit; end; /
Keywords: erp, invoice