<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Maria Jerome Prasanna George on Medium]]></title>
        <description><![CDATA[Stories by Maria Jerome Prasanna George on Medium]]></description>
        <link>https://medium.com/@mariajeromeprasanna?source=rss-e1f032ab1a59------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Y-ciRsIzIJHmKU89</url>
            <title>Stories by Maria Jerome Prasanna George on Medium</title>
            <link>https://medium.com/@mariajeromeprasanna?source=rss-e1f032ab1a59------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:24:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mariajeromeprasanna/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[SAP Ariba — PeopleSoft ChartField Validation Integration]]></title>
            <link>https://medium.com/@mariajeromeprasanna/modernizing-accounting-validation-using-peoplesoft-and-sap-ariba-with-integration-e855453e74f7?source=rss-e1f032ab1a59------2</link>
            <guid isPermaLink="false">https://medium.com/p/e855453e74f7</guid>
            <dc:creator><![CDATA[Maria Jerome Prasanna George]]></dc:creator>
            <pubDate>Mon, 18 May 2026 19:44:55 GMT</pubDate>
            <atom:updated>2026-05-19T21:17:58.937Z</atom:updated>
            <content:encoded><![CDATA[<p>The business requirement was to validate accounting ChartField values entered by users in the SAP Ariba requisition screen against the validation rules maintained in PeopleSoft System.</p><p>Users entered ChartField combinations, such as Business Unit, Department, Account, Fund, Program, and Project, when creating requisitions in SAP Ariba. An online real-time integration interface was developed between SAP Ariba and PeopleSoft to validate these ChartField entries.</p><p>When the user submitted or updated the requisition in Ariba:</p><ol><li>The ChartField data was sent through an online interface to PeopleSoft.</li><li>PeopleSoft received the request through Integration Broker services.</li><li>Validation logic in PeopleSoft verified:</li></ol><ul><li>Valid ChartField values</li><li>Combination edit rules</li><li>Active/inactive status</li><li>Department and Account relationships</li><li>Business Unit restrictions</li></ul><p>Detailed flow</p><ol><li>The ChartField data was sent through an online interface to PeopleSoft.</li><li>Based on the validation outcome, PeopleSoft generated a success or error response.</li><li>The response was sent back to SAP Ariba in real time.</li><li>Invalid ChartField combinations were displayed to the end user in Ariba with appropriate error messaging.</li><li>The response was sent back to SAP Ariba in real time.</li><li>Invalid ChartField combinations were displayed to the end user in Ariba with appropriate error messaging.</li></ol><p>The integration helped ensure that only valid accounting distributions were used during procurement processing, thereby reducing downstream invoice and GL posting errors.</p><h3>Architecture / Design Description</h3><h3>Integration Flow</h3><p>→ SAP Ariba Requisition Screen<br> → Online Interface Call<br> → PeopleSoft Integration Broker<br> → ChartField Validation Logic<br> → Combination Edit Validation<br> → Response Generation<br> → Validation Status Returned to SAP Ariba</p><p>End-user perspective</p><p>“Users entered accounting ChartFields in SAP Ariba requisitions. We built a real-time interface where Ariba sent the ChartField values to PeopleSoft for validation. PeopleSoft applied the ChartField and combination edit rules and returned success or error messages back to Ariba instantly. This ensured procurement transactions used valid accounting combinations before processing.”</p><h4><strong>Challenges</strong></h4><p>The integration between PeopleSoft and SAP Ariba was disrupted due to firewall restrictions blocking direct system communication. To resolve the issue, the integration architecture was redesigned to route transactions through a middleware layer, enabling secure and controlled data exchange between the two platforms.</p><p><strong>Resolution steps</strong></p><p>The middleware solution acted as an intermediary orchestration layer that:</p><ul><li>Bypassed firewall constraints through approved secure channels and API gateways.</li><li>Managed message transformation and protocol compatibility between PeopleSoft and SAP Ariba.</li><li>Implemented retry, logging, and monitoring mechanisms to prevent transaction loss.</li><li>Improved security compliance by centralizing authentication, encryption, and traffic control.</li><li>Restored end-to-end procurement and supplier synchronization processes with minimal business disruption.</li></ul><h3>Error Handling in SAP Ariba — PeopleSoft Chart Field Validation Integration</h3><p>A robust error-handling framework was implemented as part of the online integration between SAP Ariba and PeopleSoft to ensure accurate ChartField validation and user-friendly error reporting.</p><p>When SAP Ariba sent ChartField data to PeopleSoft for validation, the integration performed multiple levels of validation and exception handling.</p><h3>Error Handling Process</h3><ol><li><strong>Request Validation</strong></li></ol><ul><li>Validated mandatory fields such as Business Unit, Department, Account, Fund, Program, and Project IDs.</li><li>Checked request format, null values, invalid characters, and data structure integrity.</li></ul><p><strong>2. Business Rule Validation</strong></p><ul><li>Verified whether ChartField values existed in PeopleSoft.</li><li>Checked the active/inactive status of ChartFields.</li><li>Applied Combination Edit rules and accounting validation logic.</li><li>Validated dependencies between Department, Account, Project, and Business Unit.</li></ul><p><strong>3. Integration-Level Error Handling</strong></p><ul><li>Handled interface failures such as timeout issues, malformed requests, authentication failures, and service unavailability.</li><li>Captured Integration Broker errors and service operation exceptions.</li></ul><p><strong>4. Response Management</strong></p><ul><li>Validation failures were returned to SAP Ariba in real time with meaningful error messages.</li><li>Error responses included details about the invalid ChartField or failed combination.</li><li>Successful validations returned confirmation status for requisition processing.</li></ul><p><strong>5. Logging and Audit</strong></p><ul><li>All request and response payloads were logged for audit and troubleshooting purposes.</li><li>Error transactions were captured in interface tables/logs for reprocessing and support analysis.</li><li>Monitoring mechanisms were implemented to track failed integration messages.</li></ul><p><strong>6. User Experience</strong></p><ul><li>Users received immediate feedback in the SAP Ariba requisition screen.</li><li>Invalid accounting combinations were prevented from progressing further in the procurement lifecycle.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e855453e74f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Redesigned PeopleSoft Fluid Time Entry for Better User Experience]]></title>
            <link>https://medium.com/@mariajeromeprasanna/recently-i-worked-on-a-peoplesoft-fluid-time-entry-customization-project-focused-on-improving-2ba37bf61844?source=rss-e1f032ab1a59------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ba37bf61844</guid>
            <dc:creator><![CDATA[Maria Jerome Prasanna George]]></dc:creator>
            <pubDate>Mon, 18 May 2026 14:34:24 GMT</pubDate>
            <atom:updated>2026-05-18T18:42:25.952Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transforming a Classic Time Entry Process into a Modern Fluid Experience</h3><p>Organizations using legacy enterprise applications often struggle with outdated user experiences, especially when employees need to perform routine tasks like time entry.</p><p>Recently, I worked on a challenging and rewarding project where we redesigned and customized the PeopleSoft Time Entry experience by transforming classic pages into a modern Fluid UI approach.</p><p>The goal was simple:</p><blockquote><em>Make time entry faster, easier, mobile-friendly, and more intuitive for employees and managers.</em></blockquote><h3>Project Background</h3><p>The existing time entry process had several usability and performance challenges that affected employee productivity and overall experience.</p><h3>Key Problems Identified</h3><ul><li>Multiple navigation steps required to submit time</li><li>Poor mobile responsiveness</li><li>Limited or no mobile accessibility</li><li>Slow page performance</li><li>Validation errors appearing only after submission</li><li>Complex approval experience for managers</li><li>Inconsistent user interface across devices</li></ul><p>Employees found the process time-consuming, while managers struggled with approvals and visibility.</p><h3>Understanding the Existing Process</h3><p>Before starting the redesign, I conducted:</p><ul><li>Multiple stakeholder discussions</li><li>User walkthrough sessions</li><li>Teams-based design reviews</li><li>Process analysis workshops</li></ul><p>The objective was to understand:</p><ul><li>Real user pain points</li><li>Existing workflow limitations</li><li>Business expectations</li><li>Mobile usability requirements</li><li>Weekly and monthly submission behavior</li></ul><p>This collaborative approach helped ensure the redesigned solution aligned with both business needs and user expectations.</p><h3>Proposed Modernization Strategy</h3><p>Instead of directly implementing Oracle’s delivered Fluid Time Entry pages, we evaluated the organization’s unique business process and identified gaps between:</p><ul><li>Oracle delivered functionality</li><li>Client-specific operational workflow</li><li>Existing employee behavior patterns</li></ul><p>After detailed analysis, I documented:</p><ul><li>Why the delivered solution would not fully support the client’s process</li><li>Areas requiring customization</li><li>Recommended UI improvements</li><li>Simplified navigation approach</li></ul><h3>Solution Architecture</h3><p>The solution involved converting Classic Time Entry components into fully responsive Fluid interfaces.</p><h3>Technologies Used</h3><ul><li>PeopleSoft Fluid UI</li><li>PeopleCode</li><li>Fluid Containers</li><li>Activity Guides</li><li>Tile-Based Navigation</li><li>Responsive Design Components</li></ul><h3>What We Improved</h3><h3>1. Simplified Navigation</h3><p>The old process required users to move across multiple pages and menus.</p><p>The redesigned Fluid interface introduced:</p><ul><li>Single-entry workflow</li><li>Faster access through tiles</li><li>Reduced clicks</li><li>Guided navigation</li></ul><h3>Suggested Graphic</h3><p><strong>Flow Diagram:</strong><br> Classic Navigation vs Fluid Navigation</p><pre>Classic:<br>Home → Self Service → Time → Enter Time → Submit</pre><pre>Fluid:<br>Homepage Tile → Time Entry → Submit</pre><h3>2. Mobile-First Experience</h3><p>One of the biggest improvements was enabling seamless access from:</p><ul><li>Mobile phones</li><li>Tablets</li><li>Laptops</li></ul><p>The new Fluid pages automatically adapted to different screen sizes.</p><blockquote><em>Responsive Fluid Time Entry across devices</em>:</blockquote><ul><li>Desktop view</li><li>Tablet view</li><li>iPhone/mobile view</li></ul><h3>3. Real-Time Validation</h3><p>Previously, users only discovered errors after submission.</p><p>We redesigned validations to provide:</p><ul><li>Immediate feedback</li><li>Inline error handling</li><li>Better user guidance</li><li>Reduced submission failures</li></ul><h3>4. Improved Manager Experience</h3><p>Managers needed a faster and cleaner approval interface.</p><p>Enhancements included:</p><ul><li>Simplified approval views</li><li>Better visibility of pending entries</li><li>Faster approval actions</li><li>Improved responsiveness</li></ul><h3>Design Collaboration Process</h3><p>Before finalizing the implementation, we conducted several collaborative review sessions using Microsoft Teams.</p><p>These discussions helped us:</p><ul><li>Validate design expectations</li><li>Review usability scenarios</li><li>Align with business workflows</li><li>Ensure employee adoption readiness</li></ul><p>This phase was critical because successful enterprise UI modernization is not only about technology — it’s also about user acceptance.</p><h3>Final Outcome</h3><p>The redesigned PeopleSoft Fluid Time Entry solution successfully modernized the employee experience by delivering:</p><p>✅ Responsive mobile-enabled interface<br> ✅ Simplified navigation<br> ✅ Faster time submission process<br> ✅ Improved accessibility<br> ✅ Better usability for employees and managers<br> ✅ Reduced manual effort<br> ✅ Enhanced user satisfaction</p><h3>Key Takeaways</h3><p>Modernizing enterprise applications is not just a technical upgrade.</p><p>It requires:</p><ul><li>Understanding user behavior</li><li>Simplifying workflows</li><li>Improving accessibility</li><li>Designing for mobile-first experiences</li><li>Aligning technology with business operations</li></ul><p>This project demonstrated how thoughtful PeopleSoft Fluid customization can significantly improve productivity and user engagement. Same converted time entry page shown below for reference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*s2fwtPmIlSRy_tiHuDB4ew.png" /></figure><p>Double tap of the mobile device (Zoom out / Zoom In) appears as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/327/1*Jw-rN4JGeqiaaTnFTw7zEA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ba37bf61844" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>