Requiring ERP Approval For Updates To Supplier Data in SLP
Requiring ERP Approval For Updates To Supplier Data in SLP
1.In SLP, registered supplier submits an update to one or more mapped fields in the registration
questionnaire
2. Example, the supplier might move and update its address in the registration questionnaire, and
those address fields are mapped to the vendor database address fields.
3. In SLP, updates for supplier-facing questionnaire are approved either automatically or manually.
4. SLP send a request for update to ERP that includes the new data.
5. ERP receives the update request & processes it through its approval flow.
6. An ERP vendor administrator either accepts the changes, accepts a modified form of the changes,
or rejects the changes.
7. The vendor record in ERP now reflects these actions by either including the changes from SLP or
remaining unchanged.
8.ERP sends the complete current vendor record back to SLP using DRF
->DRF : data replication framework (enables you to replicate data from a source system to
one or more target systems.)
9. SLP updates the vendor database to match the vendor record sent by ERP.
10.In either case, the SLP vendor record replicates the current, approved SAP ERP vendor record.
11.SLP sends an email notification to the supplier registration project owner, and supplier's primary
supplier manager indicating whether the update was approved or rejected in SAP ERP.
12.The notification includes the status of the update; if it was rejected, the notification also includes
the error message from SAP ERP, which the category or supplier manager can use to correct the
update & submit it again
Connecting ERP vendor fields to SLP questionnaires :
To map a question to a vendor database field, a template creator needs to add questions to a
supplier form, questionnaire, or internal survey in one of the supplier management project
templates
Add the vendor field to the Supplier Field Mapping field on the Add Question page.
There are several field mapping values that are used only internally in SLP projects, but the
majority of the values correspond directly to vendor field names in the ERP business partner model
(Customer & Vendor).
Configuration in SLP :
Configuration in CIG :