PeopleSoft PeopleCode — Lesson 3: SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs

Learning Objectives

• Translate a realistic requirement into an executable approach for SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs.
• Use application-class implementation and integration test evidence to verify completeness, access, and process behaviour.
• Explain how to recover safely when dynamic SQL accepting an unsafe value or returning an unexpected row shape occurs.

Detailed Topics

• SQLExec
• CreateSQL
• File handling
• Application packages
• Classes
• Exceptions
• Integration Broker interaction
• And reusable APIs
• Decision ownership, prerequisites, and acceptance evidence for SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs, narrating each decision and showing how it contributes to maintainable PeopleCode that respects the Component Processor, manipulates PeopleSoft data safely, integrates services, and can be debugged without destabilizing delivered behaviour. The demonstration records application-class implementation and integration test evidence so learners can compare configuration intent with observable behaviour.

Hands-On Exercise

Configure and test SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs with representative records. Use “dynamic SQL accepting an unsafe value or returning an unexpected row shape” as the troubleshooting challenge, compare competing hypotheses, retest only the affected path, and complete application-class implementation and integration test evidence for peer review.

1. Define the requirement and identify dependencies before changing the environment.
2. Create a baseline result that can be compared with later changes.
3. Reproduce the exception and test one hypothesis at a time.
4. Complete the evidence record and obtain peer or instructor review.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how application-class implementation and integration test evidence should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid editing multiple settings at once when troubleshooting SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs. Preserve the failing example, review application-class implementation and integration test evidence, and verify whether “dynamic SQL accepting an unsafe value or returning an unexpected row shape” is the root cause. After remediation, repeat the transaction, confirm downstream effects, and record any monitoring action.

Validation Checklist

• The scope of SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs is clear, including what is deliberately excluded from the test.
• Evidence in application-class implementation and integration test evidence supports each material decision and outcome.
• A negative test demonstrates that controls reject or flag an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply SQLExec, CreateSQL, file handling, application packages, classes, exceptions, Integration Broker interaction, and reusable APIs, explain the decisions made, and defend the result with application-class implementation and integration test evidence.