How do I ensure a successful SAP Ariba import into AWARD®?

A successful import from SAP Ariba into AWARD® depends on three things: the SAP Ariba system is configured and active, you have the right project and user access in SAP Ariba, and you know what AWARD® can import. This article covers each, with tips to avoid the common problems.


Make sure the SAP Ariba system is active

Imports can only use a SAP Ariba system once its credentials have been validated. When an Account Administrator saves a system, AWARD® tests the connection: if it passes, the system is Active; if it fails, the system is saved Inactive and cannot be imported from until it is corrected. If imports are not working at all, ask your Account Administrator to check that the system shows as Active under Administration → Account → Ariba System Settings. See How do I configure a SAP Ariba integration? for the setup detail.


Make sure you have the right access in SAP Ariba

  • Your user must be matched in SAP Ariba. Your External User ID in AWARD® must match your user (email/username) in SAP Ariba. If it does not, the import returns a "no matching user" message — ask your AWARD® Administrator to check your External User ID for the eSourcing system.
  • Your account must have access to the project in SAP Ariba. The import runs against the SAP Ariba project using your linked account. If that account lacks access to the project, the import returns "The eSourcing account being used does not have access to the requested Project in Ariba." Access has to be granted within SAP Ariba.


Identify the project correctly

AWARD® locates the SAP Ariba project from the reference/code you provide. Check it carefully — an incorrectly formatted or unknown code returns "Invalid RFX format provided…" or "No project found with the RFX code provided…". There is no SAP Ariba project "state" you need to set before importing — if no responses come back, it usually means none are available yet for that project and configuration, not that a status needs changing.


Know what maps across from SAP Ariba

  • Sections in SAP Ariba map to Sections in AWARD®.
  • Requirements in SAP Ariba map to Evidence Items in AWARD®.
  • Supplier Responses map to Evidence Items in AWARD®.

Reviewing how your SAP Ariba content is structured into sections and requirements before you import makes the resulting AWARD® structure easier to work with.


Unsupported fields are skipped, not fatal

If the SAP Ariba template contains a field type that AWARD® does not support (for example certain Master Data / Material Group columns), AWARD® skips that field and continues the import, rather than failing the whole import. After importing, check the content and add anything that was skipped manually if you need it.


If the import is rate-limited

If SAP Ariba receives too many requests at once, the import may pause with a message such as "…has received too many requests; please retry after {n} seconds." Wait the stated time and try again.


Related articles:

K
Kenny is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.