Introduction
While working with Oracle Fusion Cloud Contracts, I came across an interesting configuration option related to Ship-To Account and Ship-To Site validations.
In a typical order fulfillment process, ship-to information is important because goods are delivered to a specific customer location. However, the same requirement may not apply when an organization provides consulting, implementation, or other professional services.
For example, consider a consulting company billing its customer for implementation services. The customer is being invoiced for the work performed, rather than for goods delivered to a physical location.
In such cases, maintaining Ship-To Account and Ship-To Site information on every contract line may not add much value, particularly when those details are not required for sales tax determination.
Oracle Fusion Cloud Contracts provides configurable validations that allow privileged users to make these fields optional.
In this article, I will explain how the configuration works and what happens to the ship-to information when the contract is invoiced through Oracle Fusion Receivables.
1. Understanding the Business Requirement
Let's consider a company providing Oracle Cloud implementation services to its customers.
The company creates customer contracts in Oracle Fusion Cloud Contracts and uses the contract billing functionality to generate invoices.
For this example, assume the following:
| Contract Details | Value |
|---|---|
| Contract Type | Customer Contract |
| Contract Line | Implementation Services |
| Billing Type | Professional Services |
| Ship-To Account | Not Required |
| Ship-To Site | Not Required |
The business does not want users to enter ship-to information when it is not relevant to the services being billed.
However, the existing contract validation requires the fields to be populated.
The requirement is to allow the contract to proceed without mandatory Ship-To Account and Ship-To Site information.
Instead of entering unnecessary information just to satisfy the validation, we can review the configurable contract validations available in Oracle Fusion.
2. How Contract Line Validations Work
Oracle Fusion Cloud Contracts performs validations to check whether the required contract information has been entered.
Some of these validations are configurable.
For Ship-To Account and Ship-To Site, privileged users can modify the applicable validation behavior through the Manage Contract Validations setup page.
There are two ways to make these details optional:
Option 1: Change the validation severity from Error to Warning
The system will continue to notify users when ship-to information is missing, but the validation will no longer prevent contract processing solely because of that missing information.
Option 2: Disable the corresponding validation
The system will no longer execute the disabled validation for the missing ship-to information.
Both options can address the requirement, but they provide different levels of control.
Personally, I would consider using a Warning when the business wants to retain visibility of missing ship-to details without making them mandatory.
If the information is not relevant to the organization's contract billing process, disabling the validation may also be appropriate.
The decision should be based on the organization's billing and tax requirements.
3. Review the Existing Contract Validations
The first step is to review the existing validation setup in Oracle Fusion Cloud Contracts.
Navigate to the Manage Contract Validations task in Setup and Maintenance.
On this page, identify the validations related to Ship-To Account and Ship-To Site.
Review their current severity and enabled status.
If the applicable validations are configured with an Error severity, missing ship-to information can prevent the contract from proceeding through the relevant validation process.
Before making any changes, it is worth checking whether these fields are used by other business processes, particularly tax determination.
4. Make Ship-To Account and Ship-To Site Optional
For this example, I will use the first approach and change the applicable validation severity from Error to Warning.
The configuration change is straightforward:
- Open the Manage Contract Validations setup page.
- Identify the validations for Ship-To Account and Ship-To Site.
- Change the severity of the applicable validations from Error to Warning.
- Save the changes.
With this setup, users can receive a warning when ship-to information is missing, rather than being blocked by those validations.
Alternatively, the corresponding validations can be disabled if the business does not want them to run.
One point worth mentioning is that these changes should be reviewed carefully before being introduced into a production environment.
A validation that is unnecessary for professional services contracts may still be relevant to other contract scenarios.
5. Create a Customer Contract Without Ship-To Information
Once the validation setup has been updated, the next step is to test the behavior on a customer contract.
Create a customer contract in Oracle Fusion Cloud Contracts.
For this example, consider a contract line for implementation services.
Enter the required contract information, but leave the following fields blank:
- Ship-To Account
- Ship-To Site
Run the applicable contract validation.
Since the corresponding validations have been changed from Error to Warning, the missing ship-to information should no longer block the contract solely because of those fields.
Other contract validations will continue to apply as configured.
This allows the organization to process contracts without requiring ship-to details that are not relevant to the business transaction.
6. What Happens During Receiving Invoicing?
This is an important part of the functionality to understand.
Making the ship-to fields optional on the billing invoice line also affects the information available during downstream invoicing.
When the Billing invoice line does not contain Ship-To Account and Ship-To Site details, the invoice lines generated from that contract line will not have those details populated.
For example:
| Attribute | Contract Line | Receivables Invoice Line |
|---|---|---|
| Ship-To Account | Blank | Blank |
| Ship-To Site | Blank | Blank |
Oracle Fusion Receivables also supports optional ship-to information on invoices.
Therefore, the absence of ship-to information on the contract line does not, by itself, mean that the corresponding Receivables invoice cannot be generated.
However, this behavior should be evaluated against the organization's tax requirements.
If ship-to information is used as a sales tax determinant, making it optional may not be appropriate.
7. Updating Ship-To Information on a Draft Invoice
Now consider a slightly different situation.
The contract was created without Ship-To Account and Ship-To Site information because those details were not required at the time.
However, after the Receivables invoice is generated, the business decides that ship-to information needs to be entered.
Oracle provides the flexibility to update the Ship-To Account and Ship-To Site on the invoice lines while the invoice is in Draft status.
This is useful because the ship-to details do not necessarily have to be maintained on the original contract line when they are optional.
For example:
| Attribute | Initial Value | Updated Value |
|---|---|---|
| Ship-To Account | Blank | Customer Ship-To Account |
| Ship-To Site | Blank | Customer Ship-To Site |
| Invoice Status | Draft | Draft |
The user can update the required information before the invoice progresses beyond the draft stage.
8. When Would I Recommend This Configuration?
I see this functionality being particularly relevant in the following situations.
Professional Services Contracts
Organizations providing consulting, advisory, or implementation services may not have a physical delivery location associated with every contract line.
In such cases, mandatory ship-to information can create unnecessary data entry.
Project-Based Billing
For project-based contracts, billing may be based on milestones, time and materials, or other agreed billing arrangements.
Where ship-to information is not relevant to the transaction or tax calculation, making the fields optional can simplify contract maintenance.
Contracts Without Ship-To-Based Tax Determination
This is probably the most important consideration.
If the organization does not use Ship-To Account or Ship-To Site as a determinant for sales tax, there may be a valid reason to make these fields optional.
However, I would always recommend confirming the tax requirements before changing the validation configuration.
9. Configuration and Testing Considerations
Before implementing this change, I would validate the following scenarios.
| Test Scenario | Expected Behavior |
|---|---|
| Ship-To Account and Site are populated | Contract validation proceeds normally |
| Ship-To details are blank and validation severity is Error | Applicable validation blocks processing |
| Ship-To details are blank and severity is Warning | Warning is displayed without blocking solely for those fields |
| Applicable validations are disabled | Disabled validations do not execute |
| Contract line has no ship-to information | Generated invoice line does not inherit ship-to details |
| Receivables invoice is in Draft status | User can update the ship-to information |
These tests help confirm that the configuration behaves as expected and that downstream invoicing is not affected unexpectedly.
I would also recommend testing at least one contract where ship-to information is required for tax purposes, to confirm that the configuration does not create issues for other business scenarios.
10. Key Takeaways
The main points from this configuration are:
- Ship-To Account and Ship-To Site can be made optional on contract lines through configurable contract validations.
- Privileged users can change the validation severity from Error to Warning or disable the corresponding validations.
- Changing the severity to Warning retains visibility of missing information without blocking contract processing solely for those fields.
- If ship-to information is not entered on the contract line, it will not be populated on the corresponding generated Receivables invoice lines.
- Ship-To Account and Ship-To Site can be updated on invoice lines while the Receivables invoice is in Draft status.
- The impact on sales tax determination should be reviewed before making these fields optional.
Final Thoughts
This is a relatively small configuration change, but it can be useful for organizations managing professional services and project-based contracts in Oracle Fusion Cloud.
Rather than requiring users to enter ship-to information that may not be relevant to the transaction, the validation can be adjusted to match the actual business requirement.
What I find particularly useful is that Oracle provides the option to retain the validation as a Warning instead of disabling it completely.
This gives organizations some flexibility in how they want to manage missing ship-to information.
The main consideration is to understand the impact on downstream Receivables invoicing and tax determination before implementing the change.
Have you come across similar contract validation requirements in Oracle Fusion Cloud Contracts? Feel free to share your experience or connect with me to discuss other configuration options.
Top comments (0)