In this lesson, we will explore the various aspects of importing supplier data, including the import of supplier data, purchase organization supplier combination data, supplier location data, enhancement for goods receipt-based invoice verification, and remittance location data. Mastering the art of importing these crucial data sets is essential for businesses to efficiently manage their supplier relationships and streamline their procurement processes.
Importing Supplier Data
The Managed Gateway Add-On’s Master Data extract program downloads Supplier data from SAP ERP or SAP S/4HANA (on premise) in the SupplierConsolidated.csv for the following:
- Suppliers available in the LFA1 (Vendor Master Table).
- Suppliers that are not marked for deletion for a given Purchase Organization.
- Suppliers that do not have a centrally imposed purchasing block.
- Suppliers that are not blocked for any function.
Importing Purchase Organization – Supplier Combination Data
When you extract the Supplier data, the Managed Gateway Add-On’s Master Data extract program downloads the Purchase Organization – Supplier combination data from SAP ERP or SAP S/4HANA (on premise) in the PurchaseOrgSupplierCombo.csv for the following:
- Suppliers available in the LFM1 (Vendor Master Record Purchasing Organization Data).
- Suppliers that are not marked for deletion for a given Purchase Organization.
- Suppliers that do not have a centrally imposed purchasing block.
Supplier Location Data
Buyer users must maintain either the SL_VENDOR_ADDRESS parameter or SL_PARTNER_TYPE filter before downloading the Supplier Location data else the download would result in an error.
Hint
In Unit 2 (Configuring and Importing Master Data) of this course, we will go into more detail about how to maintain these parameters and filters.
Let’s look at some example of how SAP Ariba Procurement solutions integrated with SAP ERP or SAP S/4HANA (on premise) processes the supplier location.
The following table displays the values associated to the ABC Supplier:
| Supplier | Purchase Organization | Supplier Location 1 | Supplier Location 2 |
|---|---|---|---|
| ABC Supplier | 1000 | 1004 | 1005 |
| 3000 | 1006 | 1007 |
Scenario 1:
When you import the Supplier Location data, SAP Ariba Procurement solutions integrated with SAP System displays the Supplier Location for ABC supplier as 1004, 1005, 1006, and 1007 in the downloaded CSV file.
Scenario 2:
When ABC Supplier is blocked for Purchase Organization 1000, SAP Ariba Procurement solutions integrated with SAP System only displays the Supplier Location as 1006 and 1007 in the downloaded CSV file.
Enhancement for Goods Receipt-Based Invoice Verification
The vendor master data export program has been enhanced to export the GR-Based Invoice Verif flag from the buyer’s SAP ERP or SAP S/4HANA (on premise) to SAP Ariba Buying and Invoicing.
After you check the GR-Based Invoice Verif check box on the vendor purchasing view of SAP ERP or SAP S/4HANA (on premise) and export the data, the GR-Based Invoice Verif flag is exported as the GRBasedInvoicingPreferred flag in the SupplierLocationConsolidated file as part of Supplier Master Data. The determination of this flag is based on the purchasing data at the Purchase Organization level.
If you want to set the value of the GRBasedInvoicingPreferred flag in the SupplierLocationConsolidated file to True, you must set the flags to True in all Supplier Locations in Purchase Organizations.
If the GRBasedInvoicingPreferred flag is set to False for a particular vendor in any of the Purchase Organizations, the GRBasedInvoicingPreferred flag is set to False by default in the SupplierLocationConsolidated file.
Let’s look at some examples that explain how the GRBasedInvoicingPreferred flag is set in the SupplierLocationConsolidated file:
Scenario 1:
A supplier (1000) has two supplier locations (2000 and 3000) as partner functions. The suppliers 1000, 2000, and 3000 are associated with two purchase organizations (0001 and 0002). In this case, the supplier locations 1000 and 2000 are set to True in the purchase organizations 0001 and 0002. However, the supplier location 3000 was set to False in both purchase organizations.
| Purchase Organization 0001 | Purchase Organization 0002 |
|---|---|
| 1000 - True | 1000 - True |
| 2000 - True | 2000 - True |
| 3000 - False | 3000 - False |
When you check the GR-Based Inv. Verif check box in the vendor purchasing view, the GRBasedInvoicingPreferred flag in the SupplierLocationConsolidated file is set to True for 1000 and 2000. However, for 3000, the GRBasedInvoicingPreferred flag is set to False.
Scenario 2:
A supplier (1000) with a single, default Supplier Location as the partner function is associated with two Purchase Organizations (0001 and 0002). In this case, the Supplier Location 1000 is set to True in the Purchase Organizations 0001 and 0002.
| Purchase Organization 0001 | Purchase Organization 0002 |
|---|---|
| 1000 - True | 1000 - True |
When you check the GR-Based Inv. Verif check box in vendor purchasing view, the GRBasedInvoicingPreferred flag in the SupplierLocationConsolidated file is set to True for 1000.
Hint
For additional information on Goods Receipt-based Invoice Verification, refer to the following section of the SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network Overview Guide.
Transactions for SAP Ariba Procurement solutions > Inbound Transactions for SAP Ariba Procurement solutions > Invoice > Goods Receipt-Based Invoice Verification in SAP Ariba Buying and Invoicing.
Remittance Location Data
Remittance Location data is downloaded based on the filters and parameters you maintain. You can maintain the parameter RL_VENDOR_ADDRESS and the filter RL_PARTNER_TYPE. However, you must maintain at least one of these while downloading the remittance information.
Maintain the parameter RL_VENDOR_ADDRESS when you want to download the Supplier as the Remittance Location.
When you maintain only the parameter SL_VENDOR_ADDRESS for the Supplier Location Address and do not maintain the Supplier Location and Remittance Location for that Supplier, the Managed Gateway Add-On’s Master Data extract program considers the Supplier as the Supplier Location and Remittance Location.
- When you maintain the Supplier Location but do not maintain the Remittance Location, the Managed Gateway Add-On’s Master Data extract program considers the Supplier Location as the Remittance Location.
When you do not maintain the parameter RL_VENDOR_ADDRESS or the filter RL_PARTNER_TYPE, the Managed Gateway Add-On’s master Data extract program displays an error stating that you have not maintained the Remittance Location related parameter or filter.
Note
When you import the master data for suppliers, SAP Integration Suite, managed gateway for spend management and SAP Business Network does not send the Payment Method information to the SAP Ariba Procurement solutions. As a result, the RemittanceLocationConsolidated.csv does not contain information on the Payment Method.
Additional Information About Supplier Location and Remittance Location
When a supplier is either marked for Block or Delete and you run the master data for Suppliers, the Managed Gateway Add-On’s Master Data extract program does not extract the Supplier, Supplier Purchase Org, Supplier Location, or Remittance Location.
However, if the supplier is not marked for Block or Delete and active, but the Supplier Location or Remittance Location is either marked for Block or Delete, the Managed Gateway Add-On’s Master Data extract program processes the information as follows:
When you run the Full Load Master Data, the Managed Gateway Add-On’s Master Data extract program downloads the:
Supplier information
Supplier Purchase Org, Supplier Location, or Remittance Location in the SupplierLocationConsolidated.csv and RemittanceLocationConsolidated.csv files. This information is downloaded as the Supplier / Vendor is active and not marked for Block or Delete.
When you run the Incremental Master Data, the Managed Gateway Add-On’s Master Data extract program:
Downloads the information on the Supplier, Supplier Location, or Remittance Location that has been changed recently for the Supplier.
The changed information is only available in the first run of the incremental load in the SupplierLocationConsolidated__Delete.csv files and RemittanceLocationConsolidated__Delete.csv files.
Limitation for Supplier Delete Event Update for Different Purchase Organizations
When a supplier is marked for deletion in a Purchase Organization, a change document is generated in the ABRCIG_CHANGEDOC table to record the VENDORDELETED event. However, if the supplier is subsequently marked for deletion in other Purchase Organizations they belong to, no change document is created. This is because the Supplier Number is the only key used to update the change documents in the ABRCIG_CHANGEDOC table for any Create, Change, or Delete event.
During the export of Supplier Master Data from SAP ERP or SAP S/4HANA (on premise) to SAP Ariba Procurement solutions, only the information related to the deletion of the supplier for a single Purchase Organization is recorded. This is because the existing record in the ARBCIG_CHANGEDOC table for the VENDORDELETED event is overwritten when the same supplier is marked for deletion in the subsequent Purchase Organization.