Derive supplier site from invoice account numbers

You can now derive the pay site for GHX inbound invoices using the B2B Account Number setup in Collaboration Messaging.

This feature automatically derives the appropriate pay site for GHX inbound invoices, thereby ensuring invoices are routed to the correct payable supplier site.

Steps to enable and configure

To use this functionality:

1. Enable either the Simplify Configuration and Processing for B2B Messaging feature or the Use Collaboration Messaging in Redwood Experience with Classic Flows feature.
2. Enable the Assign B2B Account Numbers to Your Ship-to Locations feature.
3. Create the CMK_DERIVE_PAYSITE_FROM_ACCOUNT_NUMBER profile option.

Create the profile option

Complete these steps to create the CMK_DERIVE_PAYSITE_FROM_ACCOUNT_NUMBER profile option:

1. In the Setup and Maintenance work area, search for and select the Manage Profile Options task.
2. Select New and enter the following information:

Create profile option

3. Select Save and Close.
4. In the Profile Option Levels section, select both the Enabled and Updatable checkboxes at the Site level.

Profile option levels

5. Select Save and Close.
6. In the Setup and Maintenance work area, search for and select the Manage Administrator Profile Values task.
7. On the Manage Administrator Profile Values page, search for and select the CMK_DERIVE_PAYSITE_FROM_ACCOUNT_NUMBER profile option code.
8. In the Profile Values section, set the Site level to Y. 

• Y = enables the feature
• N = disables the feature

9. Click Save and Close. Changes in the profile value will affect users the next time they sign in.

Manage administrator profile values

Configure pay site retrieval in simplify configuration and processing for B2B messaging

Complete these steps to configure pay site retrieval for the Simplify Configuration and Processing for B2B Messaging feature:

Non-PO invoices

1. 1. Create supplier messaging properties. This is required to identify the Partner ID and Partner ID Type. Configuring the Site is optional for this feature.

Supplier properties

2. Create messaging account numbers records.

Messaging account numbers

3. Activate the GHX Invoice Inbound connection.

GHX invoice inbound connection

4. Process a non-PO invoice message.
   • Include an Account Number in this location: /Invoice/InvoiceHeader/ShipToParty/Location/ID

Account number location in payload

• • The B2B Account Number setup resolves to a pay site. So, the message is processed successfully and completes with a Success status on the History page.
  • The Message Details page displays the pay site derived from the account number provided in the inbound invoice payload.

Message details – history page

• • The transformed payload shows the VendorSiteId for the pay site derived from the B2B Account Number setup.

VendorSiteId – transformed payload

PO invoices

1. Create supplier messaging properties. This is required to identify the Partner ID and Partner ID Type. Configuring the Site is optional for this feature.

Supplier properties

2. Create Messaging Account Numbers records.

Messaging account numbers

3. Activate the GHX Invoice Inbound connection.
4. Process an inbound invoice message.
   • The payload includes a PO number in this location: /Invoice/InvoiceLine/PurchaseOrderReference/ID

The payload doesn't include an account number.

Purchase order location in payload

• • The purchase order contains the same Supplier, Supplier Site, and Ship-To Location configured for the B2B Account Number shown below:

B2B account number supplier, site, and ship-to location

      The application derives the Account Number from the purchase order and uses it to determine the pay site. The Message Details page displays the derived pay site.

Message details – history page

• • The transformed payload shows the VendorSiteId for the pay site derived from the B2B Account Number setup.

VendorSiteId – transformed payload

Configure pay site retrieval in Redwood experience with classic flows

Complete these steps to configure pay site retrieval for the Use Collaboration Messaging in Redwood Experience with Classic Flows feature:

Non-PO invoices

1. Ensure that the GHX Invoice Inbound connection is active.

GHX invoice inbound connection

2. Create a trading partner using the GHX service provider.

GHX trading partner

3. Navigate to the Supplier B2B Configuration page. Under the Trading Partner Assignment tab, associate the GHX trading partner with a supplier site.

Supplier site trading partner assignment

4. Under the Document Setup tab, add the documents that you want to exchange with the trading partner.

Document setup for the GHX trading partner

5. Create Messaging Account Numbers records.

Messaging account numbers

6. Process a non-PO invoice message.
   • The payload includes an Account Number in this location: /Invoice/InvoiceHeader/ShipToParty/Location/ID

Account number location in payload

• • The B2B Account Number setup resolves to a pay site. So, the message is processed successfully and completes with a Success status on the History page.
  • The Message Details page displays the pay site derived from the account number provided in the inbound invoice payload.

Message details – history page

• • The transformed payload shows the VendorSiteId for the pay site derived from the B2B Account Number setup.

VendorSiteId – transformed payload

PO invoices

1. Ensure that the GHX Invoice Inbound connection is active.
2. Create a trading partner using the GHX service provider.

GHX trading partner

3. Navigate to the Supplier B2B Configuration page. Under the Trading Partner Assignment tab, associate the GHX trading partner with a supplier site.

Supplier site trading partner assignment

4. Under the Document Setup tab, add the documents that you want to exchange with the trading partner.

Document setup for the GHX trading partner

5. Create Messaging Account Numbers records.

Messaging account numbers

6. Process an inbound invoice message.
   • The payload includes a PO number in this location: /Invoice/InvoiceLine/PurchaseOrderReference/ID

The payload doesn't include an account number.

Purchase order location in payload

• • The purchase order contains the same Supplier, Supplier Site, and Ship-To Location configured for the B2B Account Number shown below:

B2B Account number supplier, site, and ship-to location

The application derives the Account Number from the purchase order and uses it to determine the pay site. The Message Details page displays the derived pay site.

Message details – history page

• • The transformed payload shows the VendorSiteId for the pay site derived from the B2B Account Number setup.

VendorSiteId – transformed payload

Tips and considerations

• This feature applies to GHX inbound invoices only.
• Configure a Primary pay site for suppliers that have multiple pay sites to ensure that a single payable site can be resolved during fallback processing.
• The CMK_DERIVE_PAYSITE_FROM_ACCOUNT_NUMBER profile option must be set to Yes to enable pay site derivation from the B2B Account Number setup. If this profile option isn't enabled, pay site retrieval from Account Numbers isn't performed, even if the Assign B2B Account Numbers to Your Ship-to Locations feature is enabled.
• If both an Account Number and a PO are included in the inbound invoice, the application uses the Account Number to derive the pay site. The PO is used only when an Account Number isn't provided in the payload.
• If a valid payable site can't be determined, invoice processing fails and an appropriate error is returned.
• For Non-PO invoices, the application first attempts to resolve the pay site from the B2B Account Number setup. If no payable site is found, the application derives the supplier's Primary pay site or the only pay site, if one exists. If a valid payable site can't be resolved, the application returns an appropriate error.
• For PO invoices, the application derives the Account Number using the PO information. If the B2B Account Number setup resolves to a pay site, it's used. Otherwise, the application falls back to the PO Site. If the PO Site isn't a pay site, the application derives the supplier's Primary pay site or the only pay site, if one exists. If a valid payable site can't be resolved, the application returns an appropriate error.

Access requirements

If you're using custom job roles, then you need to add privileges identified as new in this update as well as validate that you have the previously delivered privileges listed.

Privilege status	Privilege name and code
Previously delivered	Manage Account Numbers by web service CMK_MANAGE_B2B_ACCOUNT_NUMBERS_WEB_SERVICE_PRIV