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_BIL_0015 | Layout Set Assignment |
| Transaction Code | S_KK4_66000060 | IMG-Aktivität: SIMG_BIL_0015 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_BIL_0015 | Layout Set Assignment |
| Customizing Activity | SIMG_BIL_0015 | Layout Set Assignment |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_BIL_0015 |
When you have created SAPscript layout sets for the various billing documents (i.e., invoice, statement, expenditure detail) that your JVA company will issue to its non-operating joint venture partners, you can proceed to the following tasks:
- Assign the layout sets to a document type and to the company's billing structure
- For invoices and statements, define the billing indicator mapping for line items on the document
- Assign the text elements defined in the layout set to JVA billing levels or events to control where data will appear on the billing document
Example
The following example shows how the layout set, created in the previous step of configuration (Layout Set Maintenance), can be assigned to a billing document type and the company billing structure:
Layout Set FT Billing Type Text BStr
JVA_INVOICE IV Joint Venture Invoice COBS
Since this layout set is assigned to a document type that indicates it is an invoice, it is necessary to map billing indicators to line items in the billing document. An example follows:
FT No PT BI
1 1
4 1 7
6 1 7
6 2 6
8 1 6
The FT or form type is a number which should correspond to the number of a total field entered in the billing level field of the JV Billing Events screen (see below). The No field is a sequence number field that allows multiple entries to be combined in one output field. Here the amounts for billing indicators 6 - Regular expenditure and 7 - partner direct charges are combined in the final total line. The PT field can be used to recall a previously generated sub-total. The BI field is used to select types of expenses for display on the document based on billing indicator.
The JV Billing Events screen that corresponds to the billing indicator mapping example above follows:
BiLev No Window Element + FT
EGR01 1 MAIN EGROUP_DETAIL 3
EGR04 1 MAIN GROSS_EXPND 3
EGR08 1 MAIN PARTNER_DIRECT 3
VEN06 1 MAIN NET_EXPENDITURE 3
The combination of billing indicator mapping definitions and assignment of text elements of the layout set to billing levels would result in the following formatting of output:
Venture: V18 - Operated JV
Equity Group: EG9 - Equity Group 9
Expenditures 2,500.00
Partner Direct 4,812.00
Net Expenditures: 7,312.00
Requirements
You must create the billing structure for the company before you can assign billing layout sets to it. You must also assign the billing structure to the company before you can execute the periodic billing process.
You must create the SAPscript layout sets for JVA billing documents before you can assign them to a document type and a company billing structure.
Standard settings
Recommendation
Activities
Assigning formatting and content to your company's billing documents requires performing the following tasks:
- Assign layout sets to documents and to the billing structure
- Define billing indicator mapping for line items
- Assign layout set text elements to JVA billing levels
Assign Layout Sets to Documents and to the Billing Structure
On the JV Layout Sets: Overview screen, you can assign a layout set to one of the following billing document types (FT field) by entering one of these codes:
FT Type of
Code Document
IV Invoice
ST Statement
EX Expenditure Detail
At the same time, you should assign the layout set for the type of document to the company's billing structure (BStr field)
Define Billing Indicator Mapping for Line Items
Data for all the JVA billing documents except the invoice (expenditure detail and supplemental detail for both invoices and expenditure details) is derived from the JVA summary ledger. There is no need to map expenditures by billing indicators because billing indicators have not yet been assigned to expense entries in this ledger.
The data used to generate invoices and statements is derived from the JVA billing ledger. Since billing indicators have been assigned to the expenses contained in this ledger, it is possible to map expenses by billing indicator.
As a result, it is necessary to map lines on the invoice or statement to specific billing indicators. The billing indicator mapping must be compatible with the billing levels specified on the JV Billing Events screen. Specifically, a form total number specified in the FT field of the Billing Indicator Mapping screen must correspond to the number of the billing level entered in the BiLev field on the JV Billing Events screen.
Assign Layout Set Text Elements to JVA Billing Levels
By assigning billing levels to text elements from the billing layout set, you determine what data will be printed on the document and where it will appear.
The available billing levels for invoices, statements, and expenditure details are fixed. You can select which of the available billing levels will appear in the output, but you cannot specify the order in which they will appear.
The billing level assigned in the BiLev field should correspond to the billing structure and field within the structure referenced in the text element specified in the Element field.
For example, billing level EGR04 references the Total04 field at the equity group level. On the second line of the example above, this billing level is assigned to the text element entitled GROSS_EXPND. This text element references the contents of the following billing structure and field: t8jvb05-total04. T8jvb05 is the equity group level billing structure and field total04 corresponds to EGR04.
With reference to billing level specification, the No should always be set to 1, the Window should always be MAIN, and the even type ( field) should always be set to 3 for current.
Further notes
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory 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 |
| VC_T8J0M | C - View cluster | GJVL | BIL_0015 | JV layout sets |
History
| Last changed by/on | SAP | 20010306 |
| SAP Release Created in |
