Large number of steps to set up each supplier as per 42K scope item

[mdonovan]

Hi,

As per the config guide in scope item 42K there are a large number of config steps required each time a new supplier needs to be set up for transactions to/from Airba Network with S/4HANA Cloud. Some of which are also required for each Company Code of each supplier.

Is there a streamlined best practice process which avoids so many steps needing to be completed for each supplier/company code?

[mdonovan]

One activity I'm specifially talkining about is the "Assign company codes" config. This in an area of S/4HANA which would not ordinarily be maintained by business users/master data owners. However based on our testing it mandates that Supplier (Invoicing Party) is required which makes the supplier set up process awkward.

In addition, it is not clear what function this config performs. We are only allowing PO Invoices, therefore the invoice will always be matched to a PO and the PO will have the correct company code. Why is it required to make a mapping of supplier to company code when that information is already held elsewhere in PO.

Please can you confirm if there is a way to avoiding having to maintain this config in S/4HANA Cloud at supplier level or whether there is a roadmap item to remove the need for it?

[matic]

Hi Matt

Correct, the setup guide p.66 is very high level. Please note you can still use the usual enablement channels for standard or enterprise account setup. Either enablement via Standard PO or Vendor Upload File for enterprise account.

Reach out to our team if you'd like to discuss details.

[mdonovan]

One activity I'm specifially talkining about is the "Assign company codes" config. This in an area of S/4HANA which would not ordinarily be maintained by business users/master data owners. However based on our testing it mandates that Supplier (Invoicing Party) is required which makes the supplier set up process awkward.

In addition, it is not clear what function this config performs. We are only allowing PO Invoices, therefore the invoice will always be matched to a PO and the PO will have the correct company code. Why is it required to make a mapping of supplier to company code when that information is already held elsewhere in PO.

Please can you confirm if there is a way to avoiding having to maintain this config in S/4HANA Cloud at supplier level or whether there is a roadmap item to remove the need for it?

[mdonovan]

Having looked at this a bit more, the help guide suggest that it is required to derive the Company Code from "Address Name" in the invoice. I can understand this to some extent because invoice does not contain the actual company code ID. But it still makes no sense why Invoicing Party (supplier) is mandatory....why can we not just specify a list of Company Names assigned to Company Codes that would apply to ALL suppliers? Or is this possible?

------help guide text--------

"In a first step, the system checks whether the address name (AddressName parameter) is identical to an entry in the Company Code Name field that is assigned to a specific company code."

For example, your SAP S/4HANA Cloud system contains two relevant company codes (1000 and 1010) that can both be used to procure goods from an external company.

• First step (system checks address name):

-

AddressName = SAP SE; this is the buyer address that must be entered in the Company Code Name field. SAP SE is assigned to company code 1000.

-

AddressName = SAP LAB; SAP LAB is assigned to company code 1010.