ZUGSEIL P2P Hub

From ZUGSEIL Wiki
Revision as of 15:26, 9 February 2023 by Stefanseiler (talk | contribs)
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.

Supplier onboarding functionality

When a customer digital wants to rapidly onboard suppliers, which are not able to deliver deep digital integration through b-op, the ZUGSEIL P2P Hub supports with these digitalization tools along the P2P process chain:

STEP 1: Catalog import

Before a product can be used in 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 ("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.
  • Import 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

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

  • 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.
  • Export 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

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)
  • Import 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

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:

  • 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.
  • Import EDI Invoices (810) - 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

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=5542"