Default Requestor and Ship-to Location in Contract Fulfillment from Negotiation backed Requisition — Cloud Customer Connect
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

Default Requestor and Ship-to Location in Contract Fulfillment from Negotiation backed Requisition

in Sourcing 1 comment

Summary:

Hi Experts,

We create contracts in Fusion via cycle Requisition → Negotiation → Award → Contract. Each contract may have approx 80–120 lines from requisitions.

Content (please ensure you mask any confidential information):

Requirement:
Requestor and Ship-to location should auto-populate on Contract Fulfillment based on backed negotiation<requisition.
Challenges:
OOB features do not support to default these information.
REST API for contract fulfillment is not available.

1.Are there any workarounds, SOAP Web Services or other integration approaches to address this use case?
2.What are the best practices or recommended methods to default these fields?
3.Can SOAP Web Services or Oracle Integration Cloud (OIC) be leveraged for automation?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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