Difference between revisions of "ZUGSEIL P2P Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(32 intermediate revisions by the same user not shown)
Line 1: Line 1:
Our Catalog Hub is a product which helps to onboard suppliers or customers which are not participating in [https://www.b-op.com b-op concept] or are using products of competitors like SAP Ariba.
 
ZUGSEIL P2P Hub is a tool for connecting with 3rd party it systems along the procure-to-pay or return-to-refund process chains.


== Supplier onboarding functionality ==
== Intra digital connection ==
It allows these functionality
In this scenario the digital uses the P2P Hub to communicate with 3rd party systems within its IT landscape. 


=== Simple Integration ===
'''Example:''' Connection with an ERP, Warehousing Management of Finance systems   
For suppliers which are not digital and are not willing to go digital


* '''Standard ZUGSEIL catalog Import''' - this is a standard catalog format offered by ZUGSEIL allowing to import products manually. The products can be imported into a supplier digital or directly into the customer as articles of a "manual supplier"
== Cross digital connection ==
* '''Import CIF catalogs -''' this is a catalog format developed by SAP Ariba ("[https://help.sap.com/docs/ARIBA_NETWORK/5a46328f2c754661b46a4a05974fe025/dd8d3c2df018101482eddb270f0237ad.html Catalog Interchange Format]")
In this scenario the digital is receiving or sending information from a 3rd party system within another party.
* '''Email orders''' - if orders are placed with products of a "manual supplier", the supplier shall recieve an order email.


'''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: 
* Import cXML catalogs
* Import cXML orders
* Import cXML bills


=== Customer onboarding functionality ===
* Supplier's b-op digital to customer's 3rd party product (Integration path SDC3) - see [[Dev:P2P Hub integration path SDC3|details here ...]]
It allows these functionality:
* 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.


* Export cXML catalogs
*
* Import cXML orders
*
* Export cXML bills
 
== 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 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 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

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