Hierarchy
⤷ IS-OIL-PRA (Application Component) Production and Revenue Accounting
⤷ OIU (Package) PRA Production and Revenue Accounting (Upstream Business)
IMG Activity
ID | SIMG_PM_EXITS | Exit Routines for Master Entities (PRA/PM Integration) |
Transaction Code | S_P7I_60000040 | (empty) |
Created on | 20081209 | |
Customizing Attributes | SIMG_PM_EXITS | Exit Routines for Master Entities (E&P/PM Integration) |
Customizing Activity | SIMG_PM_EXITS | Exit Routines for Master Entities (E&P/PM Integration) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_EP_EXIT_ROUTNS |
Use
In order to make integration between PRA and Plant Maintenance flexible, fully configurable user routines are available to specify what data is passed between PRA and Plant Maintenance. These routines are utilized whenever a supported entity in PRA is maintained.
Requirements
Determine whether you can use the PRA routines delivered with the standard system.
Recommendation
Copy an existing routine and modify it as required.
Standard settings
Activities
1. At the Maintain screen, choose the appropriate item from the Master Entities menu.
The Maintain Master Entities <master entity name> screen appears.
2. Overwrite an existing routine or select a group number from the number range reserved for customer modifications (600 - 699) and then enter the corresponding description.
3. Program the routine in the editor.
4. Activate the routine.
5. Enter a long text that describes the meaning of the routine in more detail.
6. Enter the routine number in the appropriate customizing transaction.
Further Notes
Generally, the user routines extract data from each particular PRA entity maintenance trasnaction and fill standard structures use dby the Plant Maintenance data transfer utility. The structures are then passed to an appropriate function which creates the Plant Maintenance object and populates a cross reference table (OIU_PM_XREF).
Full documentation of this utility is available by using the transaction code IBIP and then choosing Information.
Example
Business Attributes
ASAP Roadmap ID | 899 | not to be assigned |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
O5U_PM_EXITS | T - Individual transaction object | O5U_PM_EXITS |
History
Last changed by/on | SAP | 20091126 |
SAP Release Created in |