So here's the scenario: We have PeopleSoft and want to send messages back and forth from salesforce. Unfortunately PeopleSoft doesn't have a tool like wsimport which consumes a wsdl and generates classes for you. There is something that consumes wsdl's, but all it does it generate stub message objects. A developer would still have to write the code to manually generate the xml message string.

I obviously don't want to do all of that. So I know that java can be called from within PeopleSoft. I also know I could send messages just using the generated classes, but I would like to use the message monitoring features built in to PeopleSoft.

So a possible solution that I am thinking of will:

1. call the webservice method in java (without sending out the message)
2. Grab the xml
3. send the xml via peoplesoft mechanisms
4. grab the response xml
5. pass the response xml back into the response java class
6. Use java classes to grab values within the xml

Am I crazy or is this possible?

p.s. i am a newbie java developer

I've encountered an issue while monitoring some failed message in my integration broker. When I look at details and click on error messages I've got only 50 lines ... So I'm not able to check what's really going on in there during process. (PeopleTools -> Integration Broker -> Service Operations Monitor -> Monitoring -> Asynchronous Details)

I've tried to retrieve the log directly form PSIBERRP , but as you could expect , there's also only 50 lines for one transaction ID in it.

I'm on Tools 8.50.06, I checked in books and some request on google, asked around me , and no one have any idea about how unlock this limit.

Does anyone know about some settings to remove this limit ?

In part one we identified some of the main reasons large PeopleSoft projects fail.  Now let’s discuss how we mitigate these risks and implement for our clients successfully.

Risk: The solution is not tied to the business objectives.

• As outlined in previous blogs, one of the first activities we conduct is the BluePrint Workshop. The workshop identifies all of the project objectives, classifies them as strategic or tactical, prioritizes all of the objectives, identifies how we are able to measure each objective (after all, if you can’t measure it, it is challenging to determine if it was met).  Finally we attach project success criteria to the objectives.  These objectives are a part of the project charter which is expected to be signed off by the executive sponsor.

Risk: Scope is not managed.

• Every project has a well defined scope change management plan with appropriate escalations and approvals.  Preferable is the approach that any change to scope once the fit/gap is completed requires a change order whether it is the smallest seemingly insignificant change or a very large change.  All changes have must be approved by project management and executive sponsorship to be fully approved for the project.

Risk: Organization is not prepared for change.

•  A full time organizational change management lead who is experienced with preparing organizations for change associated with PeopleSoft engagements should be deployed on the project.  Organizational change preparedness is so much more than simply communication in that is requires its own discipline, expertise and dedicated skillsets.

Risk: Project team skills are not appropriate and unavailable.

• During the BluePrint Workshop we identify the required resources required from both the client and MIPRO.  For each client resource we identify the very specific role and responsibilities along with the percentage of time they are required for the project.  This information again becomes part of the project charter.  Additionally, as outlined in the charter, these are the resources required to achieve the objectives of the project and be on time and on budget.  We conduct a sanity check of resources against project objectives.  We expect the executive sponsor to support the project and ensure the identified resources are available for the anticipated timeframe.

Risk: Executive Sponsorship is not strong and not visible.

• The role of the executive sponsor begins immediately with the BluePrint Workshop where the executive sponsor outlines why the project is important to the organization and identified corporate level objectives (that we then tie to the project objectives).  The executive sponsor signs off on the project charter along with his/her expected role.  We put the executive sponsor into the change process, issue escalation process and organizational change process.

Risk: The system is not sustainable by the client.

• Knowledge transfer is the cornerstone of our SD3 implementation methodology.  Not only do we staff with the best and brightest, but we align resources directly to the appropriate client counterparts.  Our design allows for the MIPRO team to understand the client business and for the client to understand PeopleSoft.  By the end of the project we expect our clients to know as much as we do about PeopleSoft so they can sustain the system.  Additionally we ensure shortcuts are not taken on testing and training.  This is achieved if we plan appropriately upfront and execute well.

Risk: End users are not trained

• There are multiple factors used to ensure end user training.  The first is a training strategy developed up front, early in the project.  We also recommend a training lead to develop and lead the training efforts. UPK is a very valuable tool to help ensure end users are trained.  We time end user training to coincide as close to go live as possible.  As noted prior, with the proper planning we do not find ourselves in situations where the timeline is crunched and the project is looking for ways to cut corners (which usually results in training being reduced).  Having the right staffing, dedication to training and planning allows us to ensure end users are trained appropriately.

1. Is ARIS the perfect tool for Process modeling?
2. The future of customizations within Oracle Apps
3. OpenWorld 2007: Day 2

Visit PSChrome Homepage

PSChrome is a Chrome extension to help improve the user experience associated with everyday tasks in PeopleSoft. End users, developers and administrators will find this tool enhances their user experience.

Current Features:

• Remember login information
• Process Monitor: quick links, automated actions and auto-refresh
• Integration Brokers: auto-refresh and 1-click domain restart
• Random User Profile password generation
• 1-click CTRL-J information
• PIA visualization and Favorites enhancements

by melban

My employer is considering migrating our e1 reporting from crystal reports 10 to another solution.

I want to use jasper server and I was wondering if there is a standard migration path or standard report package that we could use to make the task easier/faster. Also, any experience shared about creating the user objects for jasper business intelligence portal would be appreciated.

1. PeopleTools 8.52, starting to look like Fusion Applications
2. Setting up predelivered Related Content services
3. PeopleSoft & Oracle Secure Enterprise Search (SES)

Just a quick post to let you know the website move is complete.  I’m sorry about any down time you may have experienced.  Hopefully, I can get active again and start blogging again.

If you are interested in the details check out:

• My lessons learned
• Website speeds

1. Installing Oracle Fusion Applications: Where to start
2. Oracle Fusion Applications: Installing Oracle Enterprise Linux (64bit) to host Oracle Identity Management
3. Fusion Applications Final(ly) no more Beta version!

Overview

Oracle/PeopleSoft is happy to announce the first feature pack release of the PeopleSoft Applications Portal. This is the first release in the new continuous release model, which we believe will enable us to make new functionality and features available to customers faster. We also expect that the new features will be easier to uptake in more fine-grained packages. The release continues Oracle’s commitment to protecting and extending the value of PeopleSoft applications. It provides valuable enhancements that improve the productivity of end users, as well as improvements to help reduce the total cost of ownership. While the feature pack contains many enhancements, in this post we'll highlight the major enhancements, including the following:

• Unified and seamless navigation
• Content management
• Collaboration
• User Experience/PeopleTools uptake

In addition, there are some collaborative capabilities that are provided by the Applications Portal that will also be enhanced. These enhancements will extend beyond the use of the portal.

The English and Multi-Language CD recuts for the PeopleSoft Portal Solutions 9.1 Feature Pack 1 enhancements are now available on the Oracle Software Delivery Cloud (OSDC).  Physical CD shipments will be ready by January 30, 2012. Documentation updates are also complete and available on OSDC and My Oracle Support.

The recertified upgrade scripts are posted to My Oracle Support here:

PeopleSoft Portal Solutions 8.9 to 9.1 Feature Pack 1 Upgrade

PeopleSoft Portal Solutions 9.0 to 9.1 Feature Pack 1 Upgrade

The Feature Pack recut CD is intended for organizations that are implementing PeopleSoft Portal Solutions 9.1 newly, or are upgrading from an earlier release.  Feature pack enhancements and maintenance through PeopleSoft Portal Solutions 9.1 Maintenance Pack 1, and PeopleSoft Portal Solutions Bundle #6 are included in these recuts.

New Release Model

Instead of large Portal releases that occur every two or three years, Oracle-PeopleSoft is moving the Applications Portal to a new release model based on Feature Packs. Feature Packs are a new delivery mechanism supplementing the existing delivery mechanisms of bundles and maintenance packs.

Feature Packs will consist of a roll-up of new features and updates, and in addition, at the delivery of Feature Packs, Oracle will include the roll-up of capabilities and updates previously delivered in bundles and maintenance packs as well as re-certify upgrades and integrations.

Unified Navigation

Setting up the PeopleSoft Applications Portal for use with other PeopleSoft applications has been a manual process prior to Feature Pack 1 (FP1). For example, using Applications Portal to access PeopleSoft HCM and other application pages, an administrator sets up the node and registry entries for each CREF and assigns the security information manually. To automate this process in Applications Portal, we are providing a Workcenter specifically supporting Unified Navigation. The Workcenter will guide administrators through the process, and bring all the necessary pages together to streamline the process.  The Unified Navigation framework federates all PeopleSoft application nodes in one place so everything can be managed from Applications Portal. Unified Navigation supports systems using PeopleTools 8.50 and above.

Content Management

Content management is an important part of Applications Portal, and the following new features make it more useful and powerful:

• Configurable WorkCenter for delivering and managing content
• Securable portal content by business data
• Update Content usage tracking

The content management WorkCenter offers the ability to more easily manage and consume content, and it also provides the ability to capture and display (in related content) additional contextual information such as ratings, tags, and discussions associated with any piece of content. This enriches the user experience by providing users with additional valuable collaborative information about the content they are viewing. The WorkCenter also makes it easier to navigate among published content items.

Collaboration

A few new features are included to facilitate collaboration and other Enterprise 2.0 activities. This includes improvements to Related Attachments and the calendar.

Related Attachments is a new feature provided by Portal’s Related Links service. This service can be used by any application using the Related Content Framework, enabling users to attach files to virtually any PeopleSoft page or component. The Related Links service is context-sensitive, so related attachments can be keyed to specific data on a page.

Calendars in Portal and Collaborative Workspaces will now support aggregating user tasks, worklist tasks, and action items. This brings all relevant time/date dependent events into a user’s calendar, making them easier to manage and act upon. This consolidated calendar streamlines user event management by enabling users to refer to a single calendar to manage their work.

User Experience--PeopleTools Uptake

Some of the enhancements that are extending the value of the PeopleSoft applications to customers include the following:

• Authorization as a Service
• Guidance on branding and creating a rich self-service user experience
• Global Search

Additional and detailed information is available in my.oracle.support:

Configuring a Contemporary User Experience in PeopleSoft Applications Portal Red Paper (Doc ID 1399586.1)

Portal Solutions Cumulative Feature Overview Tool [ID 793160.1

PeopleSoft Applications Portal Solutions 9.1 Documentation Homepage (Doc ID 887960.1)

We’re putting the finishing touches to the agenda for the 1 day UK & EMEA PeopleSoft Conference in London on 23rd February.

There’s some interesting content in all of the streams, however just highlighting some of the Tech stream:

• Jeff Robbins is over from the US to talk us through PeopleTools 8.52 and the PeopleTools roadmap,
• Chris Heller from Grey Sparling is also coming over – he’ll be giving a session on the Test Framework, however come and find him around the Succeed stand if you want to talk to him about their Mobile Framework.
• Steve Smith from Cambridge Uni is going to talk about security/auditing, and having seen first hand some of the work they’ve done there to customise PeopleSoft I’m looking forward to an interesting session (no pressure Steve!)
• We’ll also have a round-table session, so if you’ve got anything that’s challenging you technically bring it along and see if the awesome combined PeopleTools brainpower we’ve assembled can help out.

You can see the full agenda here.

Starts here

Connected Query enables you to create a single XML file based on a set of queries with parent-child relationships.

A connected query is a hierarchical object built with existing PeopleSoft queries. A parent query can nest n levels of child queries and any child query can have m sibling queries within a hierarchy. No artificial limits exist for n and m, but typical use involves a single parent-child relationship or a few levels of nesting. Fields in a child query are mapped to related fields in the immediate parent query.

A connected query returns a hierarchical data set in which data returned by child queries is filtered by the results of its immediate parent query.

Connected queries are used to analyze data, supply to other systems with PeopleSoft data using Web Services, and create XML Publisher reports that use connected query as a Data Source.

Connected queries are significantly useful:

• To simplify task for a business user.

• User create a set of linked simple queries to collect data from multiple tables instead of creating a complicated query with multiple equal, outer joins, and grouping conditions.

• When two or more SQL statements are linked with left outer join to the same query.

• Connected Query enables you to collect data similar to query performing left outer joins. In contrast to query, Connected Query enables you to link multiple queries to a single parent query.

• As a tool in the process of replacing Crystal reports (that use subreports) with XML Publisher reports.

Crystal reports can include the main reports and a set of subreports that could be combined in the same template. Using Connected Query, you can replace a Crystal reports having main reports and sub-reports with XML Publisher reports.

• When outputs need to be in structured XML.

A simple query (including a query with multiple joins) creates a tabular plain layout. To have a hierarchical output, you need to use multiple grouping conditions that involve complicated logic and is not always straight forward. Connected Query processing creates a hierarchical output where a single row of data from parent query results in a set of rows in a child query. This data is processed row by row and produces structured data. It has similarity with SQR and Application Engine nested loops processing.

Instead of using Application Engine or SQR to collect data for file processing by XML Publisher, use Connected Query as the data collection tool because no conditional logic involves in this process. However, use SQR for processes with high volume of data or when high performance is required. You can quickly create a single parent-child relationship using the Connected Query Quick Start component (CQ_WIZARD), and create complex connected queries using the Connected Query Manager (PSCONQRS).

OVERVIEW

PeopleSoft Forms and Approval Builder is part of Common Components 9.1, therefore available for use throughout all of the PeopleSoft HCM and FMS modules.  It allows a business analyst or other non-developer PeopleSoft application expert to create simple forms and establish an approval for the content.

HOW-TO

Begin with creating the form using the Design Form Wizard.

Navigation:  Main Menu > Enterprise Components > Forms > Design a Form

1. Basic Information – enter information about the form, including effective date and a description.
2. Instructions – enter instructions that will be available for users accessing the form.
3. Form Fields – enter the fields that will be available for users accessing the form.  Fields of a variety of data types are displayed in one or two columns.  You can enter a short and long label, indicate if a field is required, designate a prompt record, and define a prompt control for the field against an existing field and record.
4. Attachments – indicate if any attachments should be made available to users accessing the form, for example a policy or template document.
5. Publish to a Menu – designate where the form should be accessed on the PeopleSoft menu.
6. Approval Process – designate the chain of approval the form should go through, if needed, and if the fields on the form should be locked down after submission, approval, or not at all.

After creating the form, it can be previewed in design mode, prior to activation onto the PeopleSoft menu.  Activate the form to make it available to users on the menu as designated.

When a user accesses a form, three tabs are available.

1. Form
2. Instructions – displays the instructions entered during form creation.
3. Attachments – provides access to any attachments assigned during form creation and allows the user to upload a form as well.

As an added bonus, you can connect data collected on a form to one or more component interfaces in an effort to eliminate redundant data entry.  (Example:  new vendor request form can feed into adding a vendor.)

Note, this feature intended only for the creation of new records through a simple single page front end, not maintaining them.

I hope you have found this introduction to Forms Builder helpful.  I believe this is a powerful, yet simple feature you can leverage to either remove custom pages or automate currently manual processes to stretch your PeopleSoft investment even further. If you have any questions, don’t hesitate to contact me. I’m always happy to chat.

###

More links:

MIPRO Consulting main website.

MIPRO on Twitter and Facebook.

About this blog.

There are a number of tools you could use to achieve this, be it data mover, raw SQL or even an SQR or App Engine. All of these would need to be custom written. An alternative solution is to use the Manage Configuration Set functionality. It’s a delivered component (at least on more recent versions of the Application) that lets you choose the modules you wish to export config for, and it builds the DMS files (Data Mover Scripts) for you.

1. Oracle Benelux User Group – Connect 2009
2. Extending PSQuery productivity with Drilling Url
3. Using UPK for an evolving system