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_NOP_0002 | JV Non-Operated Billing Form Line Item Details |
| Transaction Code | S_KK4_66000043 | IMG-Aktivität: SIMG_NOP_0002 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_NOP_0002 | JV Non-Operated Billing Form Line Item Details |
| Customizing Activity | SIMG_NOP_0002 | JV Non-Operated Billing Form Line Item Details |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_NOP_0002 |
When you have defined the name for a manual non-operated billing form, you can define line items for the form.
Example
The following is a simple example of a billing information input form for non-operated ventures:
NBFM LineId Non-billing Line Text SummId JV Account
NBL1 * Non-Op Billing Form 1
NBL1 100000 Subtotal - Cost Centers * 404000
NBL1 200000 Cost Centers 100000
NBL1 300000 Subtotal - Projects * 403000
NBL1 400000 Projects 300000
NBL1 500000 Subtotal - Asset Add. * 405000
NBL1 600000 Asset Additions 500000
NBL1 700000 Asset Retirements 500000
Each line item in a non-operated billing form references the billing form in the first field. The second field is the line number of the line item in the form, which may not be the same as its position on the input screen in processing. For example, the subtotal line for cost centers is specified on the form before the line item for cost centers, but this order will be reversed in processing because the subtotal line is the summary line for cost centers, as indicated by the entry of the cost center subtotal line number in the SummId field. Aggregations that represent totals that should be posted include a designation for the G/L account to receive the posting.
Additional information such as cost objects can also be designated on the detailed screen.
Requirements
Before you can enter data during processing on the input form defined in this step, you must create the cost objects referenced by the line items defined in the input form.
Standard settings
When you have fully defined the non-operated billing form, you must assign it to the non-operated ventures for which it will be used on the Joint Venture Master: Basic screen.
Recommendation
Activities
In addition to the fields for line items in the non-operated billing form documented in the example above, there are other settings that allow more extensive formatting control and limitation of the cost objects referenced by the line item. Each characteristic can be customized for the particular line item.
Further notes
For overview on configuration required for Non-Operated Billing as a whole, refer to Non-Operated Billing Configuration Document.
Business Attributes
| ASAP Roadmap ID | 259 | Establish Forms and Messages |
| 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_T8J3C | V - View | GJ53 | NOP_0002 | Non-operated billing form lines |
History
| Last changed by/on | SAP | 20010306 |
| SAP Release Created in |
