PTE Lecture Notes

Overview of BTE Implementation

• Continuing the topic of PTE (Process Transformation Engine).
• Steps covered:
  • Identified the BTE (Business Transaction Events).
  • Created and activated a function module.
  • Created and activated a product.

Purpose of Creating a Product

• To map the function module with the respective event (Event 1420).

Mapping Function Module with Event

• Transaction Code: FIBF is central to this topic.
• Process Interface: Used for mapping, not Publish and Subscribe Interface.
  • Publish and Subscribe Interface is used for specific requirements like sending emails to external systems.

Important Tables

• Table TB24: Stores product information; crucial for understanding flow.
• Table TPS34: Contains customer enhancement for Process BTE.
  • Distinction between Process BTE and Publish and Subscribe Interface:
    • Process BTE: Used when changing SAP standard processes.
    • Publish and Subscribe Interface: Used when not changing application data.

Creating a New Entry in TPS34

1. Access Table: Use transaction code SC11 to view TPS34.
2. Current Entries: Shows three existing entries related to Process BTE customer enhancements.
3. Create New Entry:
   • Event: Use process 1420 (Field modification to Life Item).
   • Function Module: Map the created function module (Z function module).
   • Product: Select the new product created earlier.
4. Country-Specific Implementation: Optional field for country code and application area; can be left blank if not applicable.
5. Save Changes: Use existing customizing request for saving.

Summary of Key Points

• Two Key Steps for Interviews:
  1. Creation of the product.
  2. Mapping of the function module with event 1420.
• Table Entries:
  • Entries for function modules and events go into TPS34.
  • Primary keys in TPS34: event/process, country, and application indicator.

Next Steps

• Future videos will cover the debugging process to understand how SAP picks and calls the function module's logic.