Hierarchy
⤷ IS-OIL-PRA-REP-ROY (Application Component) Royalty Reporting
⤷ OIU_REP (Package) Production, Tax & Royalty Reporting
IMG Activity
ID | SIMG_OIUREP_003 | MMS OGOR Additonal Settings |
Transaction Code | S_SO7_65001105 | Generated Text |
Created on | 20010724 | |
Customizing Attributes | SIMG_OIUREP_003 | MMS OGOR Additonal Settings |
Customizing Activity | SIMG_OIUREP_003 | MMS specific settings |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OIUREP_003 |
In this IMG activity, you define customizing settings specific to MMS Reporting.
In addition to maintaining the well status/reason code relationship in the Common Table, valid well status / reason code, and reason code / action code combinations can be maintained (action codes are codes that represent what action is to be taken to get a well completion 'up' - productive again, after is was 'down').
When you select the IMG activity, a dialog box is displayed, with the following options:
- Define Allowed Well Status - Reason Code Combinations - This defines which combinations of well status (code) and reason code are acceptable, and which are not acceptable. (The combinations themselves come from the MMS). To define allowed well status - reason code combinations, select well status / reason code combination, then, for each record, indicate whether it is 'acceptable' or 'unacceptable'. The MMS has specific rules - for instance - on which reason code and action code is valid for specific statuses. For example, for an oil well, you can have a reason code defining why it is 'down' or 'abandoned'.
- Define Allowed Reason Code - Action Code Combinations - Similar to the above, you define which combinations of reason code and action code are acceptable, and which are unacceptable. An action code is a one-digit code - out of five possibilities, of what is to happen to a well that is down (what action is required to get the well productive again). A 'reason code' is a code that defines the reason why a well is down. For each entry in the table, indicate whether it is 'acceptable' or 'unacceptable'.
- Cross Referencing MjPdCd, VT to MMS Codes (OGOR A) - Here, and in the two options below (OGOR B, OGOR C), you map (link) volume types to MMS codes. You customize volume-type data here, to reflect how your company does business. You also define where the volume types should print in the report columns.
- Cross Referencing MajPdCd, VT to MMS Codes (OGOR B) -
- Cross Referencing MajPdCd, VT to MMS Codes (OGOR C) -
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 899 | not to be assigned |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
SIMG_OIUREP_003 | US | USA |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_OIUREP_003 | 0 | I400001082 | Reporting |
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 |
OIUREP_MMS_REAS | S - Table (with text table) | SM30 | Define allowed Well Status - Reason Code combinations | |||
OIUREP_MMS_ACTN | S - Table (with text table) | SM30 | Define allowed Reason Code - Action Code combinations |
History
Last changed by/on | SAP | 20020328 |
SAP Release Created in | 46C |