Difference between revisions of "ZUGSEIL P2P Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(30 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 manually imported from the Catalog Hub UI 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]"). The products which are part of the CIF-File can be manually imported from the Catalog Hub UI into a supplier digital or directly into the customer as articles of a "manual supplier"
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.


=== Automated Integration Scenarios ===
'''Example:''' Connection with a remote api or marketplace acting on behalf of a 3rd party.   


==== Commerce XML (cXML) ====
The [[Dev:P2P Hub Coreservice|P2P Hub Coreservice]] is covering these 4 basic integration paths and mixtures of them: 
cXML is published based on the input of many companies (and is controlled by SAP Ariba). cXML is '''a protocol that is published for free on the Internet along with its DTD.''' With the ZUGSEIL Catalog Hub product you can configure file exhange locations and rythm. Once this is done you can integrate with "manual suppliers" through these methods.  
 
* 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.
 
*
*
*
* '''Import cXML catalogs''' - the catalog hub will monitor a specific location for new catalog files and check then for differences (price changes, added articles, dropped articles and other changes). If they exist, it will download and import them into the specified supplier for review and acceptance in the catalog management ui.
* '''Export cXML orders -''' the catalog hub will monitor for Purchase Orders towards manual suppliers. If they exist, it will create a cXML order (per order or as bulk order) and upload these order files to the specified interface location. These orders can be tracked through the catalog management ui.
* '''Import cXML bills -''' the catalog hub will monitor a specific location for new bills and will import them into the ZUGSEIL, map them to the orders and display it in the Inbound Bills Clearance monitor.


== Customer onboarding functionality ==
== Components ==
It allows these functionality:
* [[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 ==


* Export cXML catalogs
* [[ZUGSEIL Catalog Hub]]
* Import cXML orders
__NOTOC__
* Export cXML bills

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