Summary:
Vendor Program Creation and Configuration in GDE involves establishing the program hierarchy (Country > Master Vendor > Vendor Program), setting up the Master Vendor with required identifiers, and creating Vendor Programs with key details such as program information, vendor codes, and financial settings. It also includes configuring critical options that control program behavior and downstream processes, as well as performing validation checks to ensure the setup is complete and ready for onboarding.
Table of Contents
What is included in Vendor Program Creation and Configuration in GDE?
What means the error “SKU NOT FOUND” and how to resolve?
Question #1: What is included in Vendor Program Creation and Configuration in GDE?
Answer: Vendor Program Creation and Configuration in GDE includes:
Vendor program hierarchy and structure in GDE: Country > Master Vendor > Vendor Program, and how this structure is used to organize onboarding and bid processing.
Master Vendor creation: creating the Master Vendor record and capturing the required vendor identifiers and basic setup.
Vendor Program creation under a Master Vendor: completing the required program fields such as program identity, vendor codes, source, company code, currency, bid type, and discount configuration.
Key program configuration settings that enable downstream functionality, including multi-reseller settings and the key flags used for program behavior (for example, Auto code and related controls, visibility settings, and rule engine enablement where applicable).
Validation checks to confirm the Vendor Program is correctly saved and ready for the next onboarding steps.
Question #2: What means the error “SKU NOT FOUND” and how to resolve?
Answer: The error SKU NOT FOUND indicates that the Vendors GDS has a Deal ID that has expired. To resolve this error the validity period needs to be updated with purchases for the order to be processed.