Difference between revisions of "ZUGSEIL P2P Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(8 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! 
 
ZUGSEIL P2P Hub is a tool for connecting with 3rd party it systems along the procure-to-pay or return-to-refund process chains. 


Since 2016 in an ideal world, all business participants can have their own [https://www.b-op.com b-op digital] and are fully and digitally integrated at no cost. But the Procure-To-Pay (P2P) process chain has been around way before 2016 and has been target for digitalization for long time. As a result of this legacy software exists for this process chain, each with a lot of customers which can not just switch to a b-op based system at once, but must ways to at least partially use the benefits instead before a migration project can start. For exactly this purpose we have developed the '''ZUGSEIL P2P Hub'''. The ZUGSEIL P2P Hub enables users to interact with not b-op based parties by leveraging legacy systems and technologies.
== Intra digital connection ==
In this scenario the digital uses the P2P Hub to communicate with 3rd party systems within its IT landscape.  


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


=== Supplier side Integration ===
== Cross digital connection ==
ZUGSEIL offers through the P2P Hub a product allowing to integrate suppliers with minimal IT effort in two scenarios:
In this scenario the digital is receiving or sending information from a 3rd party system within another party. 


==== Scenario S1: Customer ERP to Supplier Digital Integration ====
'''Example:''' Connection with a remote api or marketplace acting on behalf of a 3rd party.    
This form of integration applies, if the <u>customer does not use b-op</u>, but the <u>supplier uses b-op</u>. In this case the customer and supplier may exchange P2P information through plugins hosted with the supplier's digital.


==== Scenario S2: Supplier ERP Integration ====
The [[Dev:P2P Hub Coreservice|P2P Hub Coreservice]] is covering these 4 basic integration paths and mixtures of them:
This form of integration applies, when <u>both the customer and the supplier use b-op, but the supplier also operates a 3rd party systems which are relevant to the P2P process</u>. The B-Op and the 3rd party system are exchanging information over these plugins:


* '''Catalog Adoption''' - This allows leading PIM/ERP systems to update catalogs fully or partially into the b-op digital through [[Dev:Supplier-CatalogUpdate-PlugIn|Supplier-CatalogUpdate-PlugIn]]. This plugin adopts a catalog format and transforms it to the [[Dev:P2P Hub catalog adoption format|P2P Hub catalog adoption format]], which is then interpreted by the [[Dev:P2P Hub Coreservice|P2P Hub Coreservice]] and used to create/update an catalog within the b-op digital..
* Supplier's b-op digital to customer's 3rd party product (Integration path SDC3) - see [[Dev:P2P Hub integration path SDC3|details here ...]]  
*'''New Customer Order Creation''' - This allows the supplier digital to push customer orders, which automatically arrived over the [https://www.b-op.com b-op network],  to its ERP through a [[Dev:Supplier-NewCustomerOrderTransmitter-Plugin|Supplier-NewCustomerOrderTransmitter-Plugin]]. Whenever a customer order arrives in the supplier digital, the plugin converts the customer order to a format which can be interpreted by the ERP system and transmits it to the desired connector of the ERP.
* Supplier's b-op digital to supplier's 3rd party product (Integration path SDS3) - see [[Dev:P2P Hub integration path SDS3|details here ...]]
* '''Customer Order Status Update'''- This allows the ERP to push customer order status notices over a [[Dev:Supplier-CustomerOrderStatusReceiver-Plugin|Supplier-CustomerOrderStatusReceiver-Plugin]]. Whenever the status of an customer order changes, e.g. to delivered, the ERP sends a message to the plugin, which transforms it into a standard format, which is is transported to the digital which communicates it to the customer digitals over the [https://www.b-op.com b-op network].
* Customer's b-op digital to supplier's 3rd party product (Integration path CDS3) - see [[Dev:P2P Hub integration path CDS3|details here ...]]
* '''Shipment Notice Integration''' - This allows the ERP to push shipment notices over a [[Dev:Supplier-ShipmentNoticeReceiver-Plugin|Supplier-ShipmentNoticeReceiver-Plugin]]. Whenever the ERP confirms a delivery, this information is transported to the digital which communicates it to the customer digitals over the [https://www.b-op.com b-op network].
* Customer's b-op digital to customer's 3rd party product (Integration path CDC3) - see [[Dev:P2P Hub integration path CDC3|details here ...]]
* '''Invoice Integration''' - This allows the ERP to push invoices over a Supplier-NewInvoiceReceiver-Plugin. Whenever the ERP creates an invoice, this information is transported to the digital which communicates it to the customer digitals over the [https://www.b-op.com b-op network].
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.


=== Customer side integration ===
*
*


==== Supplier Digital to Customer Digital Integration ====
This form of integration applies, when the supplier does not have its own digital and therefore the functionality of the [https://www.b-op.com b-op network] is not availble. In this case the customer digital can digitally communicate with the supplier over these standard integration methods:
* '''Purchase Order Creation Integration''' - Whenever a purchase order is finally approved, the digital can transmit it to the vendor's ERP through a Vendor-PurchaseOrder-TransmitterPlugIn.
*'''Customer Order Status Integation''' - Whenever a customer order status changes on the vendor's side, the vendor can transmit a status update to the customer's digital through a Vendor-PurchaseOrderStatus-ReceiverPlugin.
*
== Components ==
== Components ==
* [[Dev:ZUGSEIL Catalog Publishing Manager (CPM)|ZUGSEIL Catalog Publishing Manager (CPM)]] - The main tool to create and publish catalogs.
* [[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
Line 35: Line 29:
* [[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]]
*[[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

Retrieved from "https://wiki.zugseil.com/en/index.php?title=ZUGSEIL_P2P_Hub&oldid=19344"