Hierarchy
EA-FIN (Software Component) EA-FIN⤷
CA-JVA (Application Component) Joint Venture und Production Sharing Accounting⤷
GJV2 (Package) Joint Venture Development
IMG Activity
| ID | SIMG_MAS_0021 | Class |
| Transaction Code | S_KK4_66000115 | IMG-Aktivität: SIMG_MAS_0021 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_MAS_0021 | Class |
| Customizing Activity | SIMG_MAS_0021 | Class |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_MAS_0021 |
In this step of defining JIB/JIBE service codes for the operating statement transaction set (819), you should define the highest level component: class.
The JIB/JIBE class represents a logical grouping of expenses of a similar type that will receive the same accounting treatment. Line item detail (JIL segment) is presented on the 819 by JIB/JIBE class.
Example
The following is a typical set of JIB/JIBE classes for a US region company:
Class BCode Capital Text
A Operating Expense
B Repair & Maintenance
C Miscellaneous Revenue
D Recompletion/Recondition
US region companies do not use the BCode and Capital fields.
The following is a typical set of JIB/JIBE classes for a Canadian region company:
Class BCode Capital Text
C10 10 X Geological & Geophysical
C20 20 X Well Drilling Costs
C30 30 X Well Completion Costs
O25 25 Well Costs & Unit Costs
O45 45 Battery Facilities
O50 50 Gas Plant & Facilities
Requirements
Standard settings
Canadian region companies use the BCode for billing code and Capital fields.
The BCode or billing code is the JIB/JIBE code associated with the expense on the JVA billing extract, which is the source for the billing data processed by EDI. Expenses in the billing extract with the billing code specified in the BCode field will be mapped to the JIB/JIBE class being defined. The billing code should always be defined; it will not default to the second and third character of the class.
The expenses connected to the JIB/JIBE class being defined can be either capital or non-capital. If the indicator General Capital der. fr. JIBE (capital derived from JIBE) is selected on the JVA billing structure for your company, then this capital indicator on the JIB/JIBE class determines whether expenses associated with the JIB/JIBE class are capital.
If the indicator on the billing structure is not selected, then the cost object to which the expenses associated with the JIB/JIBE class were originally booked is used to determine whether those expenses are capital. Specifically, if the Control Capital indicator on the JVA cost object type (See the JVA Cost Object Types section of this IMG) for the cost object is selected (only available for WBSs and orders), then the expenses associated with the JIB/JIBE class are capital.
Recommendation
Activities
To define a JIB/JIBE class for JVA EDI, enter the following information:
In the Class field, enter the code for the JIB/JIBE class being defined.
For Canadian region companies, in the BCode field, enter the code for JIB/JIBE in the JVA billing extract to which the class being defined is to be mapped.
For Canadian region companies, select the Capital indicator if the expenses associated with the JIB/JIBE class being defined are capital.
In the Text field, enter a description of the JIB/JIBE class being defined.
Further notes
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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 |
| V_T8J6A | V - View | GJ57 | MAS_0021 | JIB/JIBE classes |
History
| Last changed by/on | SAP | 20010306 |
| SAP Release Created in |
