Difference between revisions of "ZUGSEIL P2P Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
The more the inter-company processes are digitalized, the more value is generated for the customer and the supplier side as manual work process is vanishing. Since 2016 in an ideal world, all business participants have their own [https://www.b-op.com b-op digital] and are fully and digitally integrated at no cost.   
 
ZUGSEIL P2P Hub is a tool for connecting with 3rd party it systems along the procure-to-pay or return-to-refund process chains.   


But the Procure-To-Pay (P2P) process chain has been around way before 2020 and is since long being the target for digitalization. As a result of this a lot of standards and legacy software exists for this process chain. Around the globe there exist many suppliers or customers which are not yet part of the b-op network. Although the benefits of employing the b-op technology in this area of business, these parties must be able to integrate with the early adopters of the b-op technology with as least as possible effort. For exactly this purpose we have developed the '''ZUGSEIL P2P Hub'''.
== Intra digital connection ==
In this scenario the digital uses the P2P Hub to communicate with 3rd party systems within its IT landscape.  


The ZUGSEIL P2P Hub is a product which enables ZUGSEIL users to interact with not b-op based parties by leveraging legacy systems and technologies.
'''Example:''' Connection with an ERP, Warehousing Management of Finance systems  


== Functionality ==
== Cross digital connection ==
In this scenario the digital is receiving or sending information from a 3rd party system within another party. 


* [[Dev:ZUGSEIL Catalog Publishing Manager (CPM)|ZUGSEIL Catalog Publishing Manager (CPM)]] - The main tool to create and publish catalogs.
'''Example:''' Connection with a remote api or marketplace acting on behalf of a 3rd party.   
 
The [[Dev:P2P Hub Coreservice|P2P Hub Coreservice]] is covering these 4 basic integration paths and mixtures of them: 
 
* Supplier's b-op digital to customer's 3rd party product (Integration path SDC3) - see [[Dev:P2P Hub integration path SDC3|details here ...]]
* Supplier's b-op digital to supplier's 3rd party product (Integration path SDS3) - see [[Dev:P2P Hub integration path SDS3|details here ...]]
* Customer's b-op digital to supplier's 3rd party product (Integration path CDS3) - see [[Dev:P2P Hub integration path CDS3|details here ...]]
* Customer's b-op digital to customer's 3rd party product (Integration path CDC3) - see [[Dev:P2P Hub integration path CDC3|details here ...]]
These integrations are coming along with common plugins, which allow connectivity to stand-systems with very small effort of plugin-configuration. If any of the 3rd party solutions are not on our standard list, you can create customized plugins through our project partners.
 
*
*
 
== Components ==
* [[Dev:ZUGSEIL Supplier Catalog Monitor (SCM)|ZUGSEIL Supplier Catalog Monitor (SCM)]] - The main tool to see, analyze the impact and adopt catalog changes proposed by suppliers.
* [[Dev:ZUGSEIL Supplier Catalog Monitor (SCM)|ZUGSEIL Supplier Catalog Monitor (SCM)]] - The main tool to see, analyze the impact and adopt catalog changes proposed by suppliers.
* [[Dev:ZUGSEIL Product Classification Manager (PCM)|ZUGSEIL Product Classification Manager (PCM)]] - The main tool to map classification structures onto each other
* [[Dev:ZUGSEIL Product Classification Manager (PCM)|ZUGSEIL Product Classification Manager (PCM)]] - The main tool to map classification structures onto each other
* [[Dev:ZUGSEIL P2P Supplier Integration (P2P-SI)|ZUGSEIL P2P Supplier Integration (P2P-SI)]] - The tool to defines per supplier, how to integrate. It allows the configuration of the trust relations and in case of legacy integration allows which legacy interfaces/transport mechanisms to use.
* [[Dev:ZUGSEIL P2P Supplier Integration (P2P-SI)|ZUGSEIL P2P Supplier Integration (P2P-SI)]] - The tool to defines per supplier, how to integrate. It allows the configuration of the trust relations and in case of legacy integration allows which legacy interfaces/transport mechanisms to use.
* [[Dev:ZUGSEIL P2P Customer Integration (P2P-CI)|ZUGSEIL P2P Customer Integration (P2P-CI)]] - The tool to defines per customer, how to integrate. It allows the configuration of the trust relations and in case of legacy integration allows which legacy interfaces/transport mechanisms to use.
* [[Dev:ZUGSEIL P2P Customer Integration (P2P-CI)|ZUGSEIL P2P Customer Integration (P2P-CI)]] - The tool to defines per customer, how to integrate. It allows the configuration of the trust relations and in case of legacy integration allows which legacy interfaces/transport mechanisms to use.
*[[Dev:P2P Hub architecture]]
== Related articles ==
* [[ZUGSEIL Catalog Hub]]
__NOTOC__

Latest revision as of 17:44, 8 December 2023

ZUGSEIL P2P Hub is a tool for connecting with 3rd party it systems along the procure-to-pay or return-to-refund process chains.

Intra digital connection

In this scenario the digital uses the P2P Hub to communicate with 3rd party systems within its IT landscape.

Example: Connection with an ERP, Warehousing Management of Finance systems

Cross digital connection

In this scenario the digital is receiving or sending information from a 3rd party system within another party.

Example: Connection with a remote api or marketplace acting on behalf of a 3rd party.

The P2P Hub Coreservice is covering these 4 basic integration paths and mixtures of them:

  • Supplier's b-op digital to customer's 3rd party product (Integration path SDC3) - see details here ...
  • Supplier's b-op digital to supplier's 3rd party product (Integration path SDS3) - see details here ...
  • Customer's b-op digital to supplier's 3rd party product (Integration path CDS3) - see details here ...
  • Customer's b-op digital to customer's 3rd party product (Integration path CDC3) - see details here ...

These integrations are coming along with common plugins, which allow connectivity to stand-systems with very small effort of plugin-configuration. If any of the 3rd party solutions are not on our standard list, you can create customized plugins through our project partners.

Components

Related articles