Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Triage Article: Requisitions created through Integration Flows - BPA Autosourcing Issues

edited May 16, 2020 8:47AM in Self Service Procurement 9 comments

Summary

Why is my requisition creation failing from integration sources such as Min Max or other SCO Flows with these specific error messages?

Content

Customers / Support

I wanted to highlight what I believe is one of the most often and commonly seen occurrences of errors during integration flows to create requisitions. Typically seen in any SCO (Supply Chain Orchestration) flows including Min Max Planning, the requisition fails creation with the following very common messages:

a) You must enter the Price attribute

b) You must enter the Charge Account attribute.

Now this tends to confuse the triage specialists because these are derivative errors. The system needs a price and a charge account to create a requisition. But often these are not directly populated in these kind of orchestration flows. The most common use root cause is the failure to autosource a BPA in the flow.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!