PRIMAVERA Connector

As a popular, packaged ERP for enterprises today, PRIMAVERA has no equal. It is also a fact that effective business decision-making requires a holistic view of enterprise information. Strategic business decisions require timely intelligence from various sources and there is a clear need for historical and operational data to be invoked from disparate (PRIMAVERA and non-PRIMAVERA) environments.

As middleware components, PRIMAVERA connector can provide quick and simple integration between PRIMAVERA logistic modules and external business processes without having to write any custom code or modify existing PRIMAVERA landscape.

Skelta BPM.NET PRIMAVERA Connector

To connect business insights with business process, Skelta's BPM.NET incorporates a customer centric approach in the form of a proprietary PRIMAVERA connector that integrates external applications with PRIMAVERA modules. Skelta's PRIMAVERA Connector makes provision for data access in and out of PRIMAVERA without the need to write code or create a host footprint.

Skelta’s proprietary PRIMAVERA Connector and advanced workflow platform scales PRIMAVERA’s limited approval and escalation processes by spanning across legacy systems and handling escalation scenarios via PRIMAVERA.

• Requires no code integration with PRIMAVERA for business processes
• Integrates transactional and analytical data with logistics (asles and purchases) using PRIMAVERA object model API.
• Built on top of Microsoft .NET Framework 

• Eliminates IT dependencies by removing the need for writing code
• Ensures scalability for even complex approval processes
• Information flow is bi-directional – can be retrieved from as well as submitted to PRIMAVERA
• Focus to configuration instead of developing custom applications for seamless data flow.

Business Scenario

Company 'X' is using PRIMAVERA system for purchase management, wherein the purchase details are stored in PRIMAVERA for accounting purposes. The PRIMAVERA system has limited capability in terms of advanced approval and escalation processes. The organization does not want to develop the process using Visual Basic for Applications as it is an expensive option and requires a lot of time and effort. The need is felt for an advanced human workflow, which can span across legacy systems and handle complex approval and escalation scenarios via PRIMAVERA.

The gap can be bridged with Skelta’s proprietary PRIMAVERA Connector and advanced human workflow features.

Now, before the purchase order is posted in PRIMAVERA, Skelta’s BPM.NET platform is called to have a proper approval process in place.

An employee enters the purchase details by making use of Skelta’s form. Once the employee submits the purchase order request, it triggers the workflow for approval in Skelta through PRIMAVERA Connector. The Skelta Workflow then forwards it to the relevant managers for approval. The Skelta workflow can also be configured for escalation if the approval does not happen within a specified time period. For example, if the manager does not respond within a certain within a certain timeframe (say 3 days), the request is escalated to the next higher level - to the next manager in the hierarchy. There will be some cases in which the purchase order may require approval from a group of people. In that case, the Skelta workflow can be configured to get the approval from the group (which can be set at minimum number of approvals or approval by all). Skelta's advanced workflow engine acts on the approval process, and the workflow will send the approved purchase order to the purchases management system, at PRIMAVERA, at the same time updating the purchase status status in PRIMAVERA. Following this, another employee is alerted to send the purchase order to the vendor.

Upon receive of the goods and Vendor Invoice, Skelta Workflow will cross vendors invoice against the purchase order, making sure the products references and prices at the vendor invoice were the same as those present at purchase order. Also delivery rules can be verifies automaticaly. This before the vendor invoice be automatically acepeted (if no discrepency is found) and automatically added to PRIMAVERA ERP or send to an employee for decision, if some discrepancies were found between the purchase order and the client invoice.