Using MS Excel for Component Interface utility

A Component Interface (CI) helps expose a PeopleSoft component -defined as a set of pages grouped together for a business purpose -for synchronous access from another application such as PeopleCode, Java, C/C++, COM, or XML. One can think of CI’s as black boxes that capture and compress PeopleSoft data and business processes, while hiding the details of the underlying page and data.

CI's can be used for integrating one application with either another application or with external systems. In executing the business logic built into the component; CI's carry a higher level of data validation than a simple SQL insert.

A CI can map to only one PeopleSoft component. However, multiple component interfaces can be created for the same component using PeopleSoft Application Designer.

Teaching about using MS Excel for CI's

Compliance4All, a leading provider of professional trainings for all the areas of regulatory compliance, will show how to use MS Excel for Component Interface utility and CI's to upload data from Microsoft Excel into PeopleSoft databases.

Nitika will demonstrate the actual way by which one can use MS Excel for Component Interface utility and CI's to upload data from Microsoft Excel into PeopleSoft databases. This is how it is done: Each source workbook contains both worksheets and Excel Visual Basic code modules that execute business logic for each transaction. Nitika will show how to use the Microsoft Excel workbooks as a template to create worksheets that are specific to the business logic that need to be used when uploading data to the PeopleSoft system. The data input sheet can be copied to other workbooks for distribution without copying the code modules.

The code formats spreadsheet data into a PeopleSoft readable Document Object Model (DOM) structure, and submits it to the PeopleSoft database. Next, a PeopleCode program parses the DOM structure and uses the component interface to create entries in the PeopleSoft database, validating the data submitted against the business logic that is built into the PeopleSoft component. Because the component interface is a wrapper around the component, all logic applied during data entry is applied when data is loaded through this tool.

The CI executes all the necessary PeopleCode events and the field-level edits. Based upon results from saving the component interface, another DOM is created in the PeopleCode that returns success, warnings, errors, or a combination of the three to the Microsoft Excel document. It allows for correction and resubmission of erroneous records.

Nitika will cover the following topics at this webinar:

To educate the community on Excel-to-CI: What it is? Creating a new Excel-to-CI? How to create and modify new/existing templates? How to identify errors and create solutions?

To present a live demo of building Excel-to-CI, which will try to close the gap between the slides and actual hands on process

To educate the community on Architecture of Component Interface and how to debug it

This session will be of benefit to professionals such as Business Analyst, PeopleSoft Developer, Functional Manager, Project Manager, Testing Team on the project, Project Coordinator, HR Analyst and Students.

Forum

In order to understand the goals of MapReduce, it is important to realize for which scenarios MapReduce is optimized. The MapReduce programming model is created for processing data which requires…Continue

I have a question regarding the difference between TensorFlow Serving versus TensorFlow service. (Sorry that I'm not familiar with this at all.)I found TensorFlow serving's definition, which is "…Continue