Source-to-Pay Operations Integrations release notes
Summarize
Summary of Source-to-Pay Operations Integrations Release Notes
The ServiceNow® Source-to-Pay Operations integrates with various third-party applications to enhance procurement and financial processes. The Australia release introduces new integrations with SAP, Oracle EBS, Coupa, SAP Ariba, and Oracle Financial Cloud, enabling users to manage sales orders and procurement tasks directly from their ServiceNow instance.
Show less
Key Features
- Oracle Financial Cloud Integration: Enables actions for invoices, cost centers, payment terms, and more, facilitating seamless data exchange.
- Enhanced Purchase Requisition Line (PRL): Improvements to the outbound staging table enhance data consistency.
- Performance Optimizations: Upgrades to the Purchase Order (PO) transform map improve processing efficiency for high-volume data.
- Updated Security Features: Read-only security directives have been added to enhance data protection in SAP integrations.
- Standardization Improvements: Entity naming conventions updated from Department to Buyer Groups for better consistency.
Important Upgrade Information
For customers upgrading to the Australia release, a modified sourcing fix script will require manual execution by administrators post-upgrade, as it will not run automatically during the upgrade process. This should be performed outside of business hours to ensure minimal disruption.
Key Outcomes
By integrating with third-party applications, customers can streamline their Source-to-Pay operations, enhance data accuracy, and improve compliance across their procurement processes. The enhancements and new integrations are designed to drive efficiency and provide a more cohesive operational experience within ServiceNow.
he ServiceNow® Source-to-Pay Operations extends its capabilities by integrating with third-party applications. The Source-to-Pay Operations integration with SAP, Oracle EBS, Coupa, SAP Ariba, and Oracle Financial Cloud are new applications in the Australia release.
Source-to-Pay Operations Integrations highlights for the Australia release
- Handle sales orders, procurement, finance, and so on, in Oracle Financial Cloud from your ServiceNow instance using the Source-to-Pay integration with Oracle Financial Cloud.
- Added enhancements to the Purchase Requisition Line (PRL) outbound staging table.
- Performance optimizations applied to the Purchase Order (PO) transform map.
See Source-to-Pay integration with third-party applications for more information.
Important information for upgrading Source-to-Pay Operations Integration with third-party apps to Australia
New in the Australia release
- Source-to-Pay integration with Oracle Financial Cloud
-
- You can use this integration to perform Integration Hub actions for invoices, cost centers, product models, payment terms, purchasing organizations, departments, GL accounts, currencies, FX rates, invoice payment details, suppliers, plant addresses, and legal entities.
- You can also fetch currencies, GL accounts, legal entities, and payment terms information from Oracle Financial Cloud.
Changed in this release
- Source-to-Pay integration with SAP
-
- Enhanced integration to support data retrieval from SAP ECC, SAP OData, and SAP HANA RFC using the updated Buyer Group staging process.
- Enhanced integration to support Read-Only security directives to strengthen data protection, applying required field-level changes in alignment with the Read-only field remediation guidelines to ensure compliance and consistency across integrations.
- Updated entity naming convention from Department to Buyer Groups for improved standardization.
- Source-to-Pay integration with SAP Ariba
-
- Enhanced integration to support fetch shipment details from SAP Ariba.
- Updated entity naming convention from Department to Buyer Groups for improved standardization.
- Source-to-Pay integration framework
-
- Enhanced the Purchase Requisition Line (PRL) outbound staging table to improve data completeness and consistency for outbound Purchase Requisition integrations.
- Performance optimizations have been applied to the Purchase Order (PO) transform map to improve efficiency and scalability when processing high‑volume PO data.