Difference between revisions of "ZUGSEIL P2P Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
m (Stefanseiler moved page ZUGSEIL Catalog Hub to ZUGSEL P2P Hub without leaving a redirect)
 
(26 intermediate revisions by the same user not shown)
Line 1: Line 1:
The more the Procure-To-Pay process is digitalized, the more value is generated for the customer and the supplier side as manual work process is vanishing. ZUGSEIL delivers over [https://www.zugseil.com b-op network] full deep digital integration, but as each new technology there are many suppliers or customers which are not yet part of the b-op network. The ZUGSEIL Catalog Hub is a product which enables ZUGSEIL customers to interact with not b-op based parties by leveraging legacy systems and technologies, which provide sufficient solutions for most of the basic P2P processes.  
 
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 ==
When a customer digital wants to rapidly onboard suppliers, which are not able to deliver deep digital integration through b-op, the ZUGSEIL Catalog supports with these digitalization tools along the P2P process chain:
In this scenario the digital uses the P2P Hub to communicate with 3rd party systems within its IT landscape. 


=== STEP 1: Catalog import ===
'''Example:''' Connection with an ERP, Warehousing Management of Finance systems   
Before a product can be used in [[ZUGSEIL Shop|ZUGSEIL BEST Shop]], the article has to be entered and assigned to internal catalogs. This can be a quite cumbersome process, where some standard import functionality can help a lot. The suppliers can deliver catalogs in these formats:
* '''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"
* '''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"
*'''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.
*'''EDI Price/Sales Catalog (832) -''' 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.


=== STEP 2: Order export ===
== Cross digital connection ==
Once an internal order has been placed, the supplier must be notified on the order being placed. The default tool for non-digitalized integration are
In this scenario the digital is receiving or sending information from a 3rd party system within another party.
*'''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.
*'''EDI Purchase Order (850) -''' the catalog hub will monitor for Purchase Orders towards manual suppliers. If they exist, it will create a EDI 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.
*'''Email orders''' - if orders are placed with products of a "manual supplier", the supplier shall receive an order email.


=== STEP 3: Shipment notifications ===
'''Example:''' Connection with a remote api or marketplace acting on behalf of a 3rd party.    
Once an order has been placed, the customer expected deliveries. These can be either


* '''Auto-Generated -''' in the catalog hub UI, the user can per product classification group)
The [[Dev:P2P Hub Coreservice|P2P Hub Coreservice]] is covering these 4 basic integration paths and mixtures of them: 
* '''EDI Advance Ship Notice/Manifest (856)''' - the catalog hub will monitor a specific location for new shipment notice files and will adopt them into the digital.


=== STEP 4: Receive Bills/Clear Bills ===
* Supplier's b-op digital to customer's 3rd party product (Integration path SDC3) - see [[Dev:P2P Hub integration path SDC3|details here ...]]
Once shipments have been made bills may arrive at any time and are cleared automatically only if shipment of the billed goods were confirmed. This process can either be:
* 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 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 ==
Supplier working with ZUGSEIL should always try to onboard customers working with non b-op software to build up their own b-op digital.
* [[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.
=== STEP 1: Catalog export ===
* [[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.
To make products usable in 3rd party procurement systems, ZUGSEL P2P Hub
*[[Dev:P2P Hub architecture]]
 
=== STEP 2: Order import ===


=== STEP 3: Shipment notification export ===
== Related articles ==


=== STEP 4: Bill export ===
* [[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"