ZUGSEIL P2P Hub

From ZUGSEIL Wiki
Jump to navigation Jump to search

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. The Procure-To-Pay (P2P) process chain is since long being the target for digitalization and as a result of this a lot of standards and legacy software exists for this area. ZUGSEIL delivers over b-op network full deep digital integration (not only P2P), but as each new technology there are many suppliers or customers which are not yet part of the b-op network.

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.

Functionality

  • ZUGSEIL Catalog Publishing Manager (CPM) - The main tool to create and publish catalogs.
  • ZUGSEIL Supplier Catalog Monitor (SCM) - The main tool to see, analyze the impact and adopt catalog changes proposed by suppliers.
  • ZUGSEIL P2P Supplier Integration (P2P-SI) - The tool to define 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.
  • ZUGSEIL P2P Customer Integration (P2P-CI) - The tool to define 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.

Customer onboarding functionality

Supplier working with ZUGSEIL should always try to onboard customers working with non b-op software to build up their own b-op digital.

STEP 1: Catalog export

To make products usable in 3rd party procurement systems, ZUGSEL P2P Hub allows you to publish certain catalogs in external formats:

  • Export CIF - this is a catalog format developed by SAP Ariba ("Catalog Interchange Format"). The catalog is published to a target location predefined by the customer side (SFTP, Email, Sharepoint, FTP, ...)
  • Export cXML - this is a public catalog format controlled by SAP Ariba. The catalog is published to a target location predefined by the customer side (SFTP, Email, Sharepoint, FTP, ...)
  • Import EDI Price/Sales Catalog (832) - this is a standard EDI catalog format. The catalog is published to a target location predefined by the customer side (SFTP, Email, Sharepoint, FTP, ...)

STEP 2: Order import

Once the customer has internally ordered products from the supplier, the order is transmitted to the supplier in these formats:

  • Import cXML orders - the catalog hub will monitor for inbound Purchase Orders and will import them automatically.
  • Import EDI Purchase Order (850) - the catalog hub will monitor for inbound Purchase Orders and will import them automatically.

STEP 3: Shipment notification export

To send shipment notifications towards the customer, the ZUGSEIL P2P Hub can:

  • Export EDI Advance Ship Notice/Manifest (856) - the catalog hub will monitor a shipments made to the customer and will create EDI message and publish it to a location predefined with the customer

STEP 4: Bill export

Once shipments were made, bills can be created towards the customer. To digitalize this process the ZUGSEIL P2P Hub can:

  • Export cXML bills - the catalog hub will monitor the digital for new bills being created towards the customer, export it and publish it to a location predefined with the customer
  • Export EDI Invoices (810) - the catalog hub will monitor the digital for new bills being created towards the customer, export it and publish it to a location predefined with the customer
Retrieved from "https://wiki.zugseil.com/en/index.php?title=ZUGSEIL_P2P_Hub&oldid=5543"