Hierarchy
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-PRA-REP-ROY (Application Component) Royalty Reporting⤷
OIU_REP (Package) Production, Tax & Royalty Reporting
IMG Activity
| ID | OIUREP_2014_CONFIG | Reporting Process Variations |
| Transaction Code | S_SOG_81000026 | IMG activity: OIUREP_2014_CONFIG |
| Created on | 20020204 | |
| Customizing Attributes | OIUREP_2014_CONFIG | Reporting Process Variations |
| Customizing Activity | OIUREP_2014_CONFIG | Reporting Process Variations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OIUREP_2014_CONFIG |
In this IMG activity, you can activate specific processing directions that will then be used for carrying out the MMS-2014 reporting process. The table defines which specific actions will be carried out during the process that produces the MMS-2014 report.
To activate a specific processing option, set the indicator for that item (the items you can chosse from are contained in the drop-down list for each field in the table).
Include Statistical Accounting Entries (TIK) -
Set this option if your company will report Take-In-Kind ( MMS 2014 Payment Method = 04, Royalty-in-kind ) accounting entires stored on the Statistical Subledger, STSL. Setting this option will extract MMS 2014 reportable entries to be placed on the MMS 2014 report. However, the MMS 2014 master data must either reflect a payment method of 04 or set the Royalty In Kind indicator on the SalesType level master data.
Enable Report Line Level Locking During PRTM -
During pending royalty transaction maintenance, the default is that all entries for a particular company code, sales year, and sales month are locked. However, if your business requires that a more detailed level of locking is needed (for example, your company requires multiple people to work on the same month's pending royalty transaction entries at the same time), setting this indicator will lock at a company code, sales year, sales month, and report line number level. That way, multiple people can work on different entries.
Note: If all the entries are displayed and the user switches to change mode, all entries are locked (since all entries have been selected). This option is only useful if the user restricts the entries via some other criteria (for example, venture/DOI, etc.).
Warning: Setting this indicator will place a heavier load on the enqueue/dequeue work process because instead of submitting one request to lock, the program will request multiple locks (bundled together). This will impact the process itself which may have an effect on other areas of SAP since the enqueue/dequeue process is shared among all SAP processes.
Report All Quantity Changes, When Royalty Is Zero -
Set this indicator if your company wants to report all quantity (volume) changes during report generation, even if the resulting MMS transaction generates a zero royalty less allowances amount. Normally, within MMS regulations, they do not wish to receive transactions with a royalty value less allowances equal to zero. However, under certain conditions, your company may wish to report adjustments to quantity or volume data regardless of the resulting royalty value less allowances.
If this indicator is not set, then all generating MMS pending royalty transactions with a royalty value less allowances equal to zero will not be stored (OIUREP_MRT_PEND). If these entries do not exist on the MMS pending royalty transaction table, during finalization, they will also not be dedicated to historic MMS royalty transactions (OIUREP_MRT_HIST).
Suspend All Affected JE Offset Key Trans via AutoSuspend -
AutoSuspend allows for the automatic suspension of records retrieved via the selection options designated when accessing the Pending Royalty Transactions Maintenance screen directly (Production and Revenue Accounting > Production, Tax and Royalty Reporting > Royalty Reporting > MMS > MMS-2014 Workplace; Monthly Processing tab > Pending Royalty Transactions Maintenance tab). Select this option to allow the system to also find any matching records, not originally retrieved, that could affect the offsetting journal entries upon finalization. Transactions are matched by the key fields of venture, division of interest (DOI) number, well number, well completion, owner, owner sequence, interest type, interest sequence, sales date, contract and material.
This option will assist to ensure all matching records that make up a single summarized journal entry (JE) offsetting entry are not incomplete, due to a portion of suspended transactions. When a portion of a summarized JE offsetting entry is suspended, the JE purge will not remove the original payable entries. These remaining entries can remain on the ledger, and incorrectly be allocated during the following month's MMS 2014 extraction process. The selection of this option helps to prevent an incorrect allocation.
Suspend All Affected Indian Recoup Trans via AutoSuspend -
Since the Indian recoupable transactions (MMS transaction codes 50 and 51) are generated during the MMS 2014 extraction process, using the AutoSuspend feature can impact the transactions initially used to calculate recoupable transactions. This is because when AutoSuspend is in effect, the system retrieves all suspended royalty transactions. If you want to maintain Indian recoupable transactions separately from other royalty transactions that were suspended, select this option.
By selecting this option, the system will find all matching MMS leases involved in an Indian recoupable transaction when the MMS lease is contained in an automatically suspended transaction via AutoSuspend. If you do not maintain Indian recoupable transactions, when other involved royalty transactions are suspended, the resulting MMS 2014 report may reflect inaccurate recoupable transactions.
Generate Report Doc ID at Lease Level (usually used with BAdI) -
There may be situations where the MMS agency may want the customer to submit a report with specific document IDs for specific leases. The normal document ID is generated uniquely by the reporting engine for each payor, fed/Indian type, and Indian tribe number. By enabling this option, it will also generate a new reporting ID for each lease. However, in most cases, the customer would not want to have a unique document ID for all change of leases. Therefore, the usage of the provided BAdI will usually have to accompany this option in order to provide the correct solution.
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 |
|---|---|---|
| OIUREP_2014_CONFIG | US | USA |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OIUREP_2014_CONFIG | 0 | I400001074 | Royalty 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 |
| V_OIUREP_2014_CF | V - View | SM30 |
History
| Last changed by/on | SAP | 20020204 |
| SAP Release Created in | 46C |
