You are on page 1of 9

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

1 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

Document Control: Road Map Reference: Team: Status: AP326 Configuration Rationale High-Level Design Finance Created

Last update: Reviews: Review # 0.1

4/07/2010

Date:

Revised by:

Revised Section:

Approvals: Name: Chris Hebdon

Position: Operations Manager

Date:

Signature:

Request Overview
Module Criticity Request Description FI // <Number > <Short Description of the Request>

Areas / Users Involved


Financeira

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

2 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

Related Process
Level of Business Process Process Sub-process Activities Related Documents (BP310) Configuration GAPs Name and Code FINANCE Joint Venture Accounting JVA Maintain Joint Venture Master
<List BP310 documents affected or covered by this requirement > N/a

New?

Type of Configuration
Use an X to indicate the type of request in the column bellow.

Change of existing configuration New configuration X

1. Request Description The Joint Venture Accounting sub-process outlines that activities being carried out in any Joint Venture environment. The following types of Joint Ventures (JV) would be used in Vale given business scenario:

1) Corporate JV 2) Operated JV 3) Non-Operated JV

Corporate JV

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

3 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

The following consideration should be taken for maintaining Corporate JV:

1) We would essentially have only one Corporate JV 2) Use a JV number from the JV Number Range maintained for Corporate JV 3) The JV Class for Corporate Venture should be CP
4) Relate / Assign the Corparate JV with the Corporate JOA 5) Select Venture Type as Corporate 6) A reference to an existing Corporate JV can also be assigned to copy the settings of the JV Master Basic Data Tab: a) Select the Status of the Venture as Active b) Funding Group is a required field to be maintained, assign the Funding Group CP0001 c) Select Check Funding Currency as Active. Equity Types/Equity Assignment Tab:

a) Select the respective Equity Type and assign the corresponding Equity
Group/Groups b) Assign the Validity Period for the Equity Group in the Equity Type c) Assign the status as Active for the appropriate Equity Group, if there are multiple Equity Group assigned for the sme Equity Type. d) We assign Equity Group E01 Equity Groups Tab:

a) Select the Funding Currency Tab and assign the Funding Currency. The Funding
Currency assigned would be the Company Code Local Currency. However, the House Bank Currency can also be maintained which is determined to be assigned to Funding Group from which all the Venture transactions would be processed.

Operated Joint Venture:

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

4 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

The following consideration should be taken for maintaining Operated JV:

1)

In Vale given business scenario, we would have only one Operated Joint Venture per Company 2) Use a JV number from the JV Number Range maintained for Operated JV 3) The JV Class for Operated Venture should be OP 4) Relate / Assign the Operated JV with the Operated JOA 5) Select Venture Type as Operated (no tax) 6) A reference to an existing Operated JV can also be assigned to copy the settings of the JV Master Basic Data Tab: a) b) c) d) Select the Status of the Venture as Active Posting Method: Cash Call CCL Billing Format: VAO1 Vale Operated Billing Format Billing Extract based on Inception to Date Data: YES e) Funding Group: OP0001 f) Select Check Funding Currency as Active. Equity Types/Equity Assignment Tab: a) Select the respective Equity Type and assign the corresponding Equity Group/Groups b) Assign the Validity Period for the Equity Group in the Equity Type c) Assign the status as Active for the appropriate Equity Group, if there are multiple Equity Group assigned for the sme Equity Type. d) We assign Equity Group E01 Equity Groups Tab: a) Select Cross Company Tab and assign the Inter-Company Joint Venture Number and the corresponding Inter-Company Joint Venture Equity Group for the respective Inter-Company Joint Venture Partners as appearing therein. b) Select the Funding Currency Tab and assign the Funding Currency. The Funding Currency assigned would be the Company Code Local Currency. However, the House Bank Currency can also be maintained which is determined to be assigned to Funding Group from which all the Venture transactions would be processed.

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

5 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

Non-Operated Joint Venture: The following consideration should be taken for maintaining Non-Operated JV:

1) In Vale given business scenario, we would have only one Non-Operated Joint Venture 2) 3) 4) 5) 6)
per Company Use a JV number from the JV Number Range maintained for Non-Operated JV The JV Class for Non-Operated Venture should be NP Relate / Assign the Non-Operated JV with the Non-Operated JOA Select Venture Type as Non-Operated A reference to an existing Non-Operated JV can also be assigned to copy the settings of the JV Master

Basic Data Tab: a) Select the Status of the Venture as Active b) Operator: Assign the Operated Partner Customer Account Number c) Posting Method: Cash Call CCL d) Funding Group: NO0001 Equity Types/Equity Assignment Tab: e) Select the respective Equity Type and assign the corresponding Equity Group/Groups f) Assign the Validity Period for the Equity Group in the Equity Type g) Assign the status as Active for the appropriate Equity Group, if there are multiple Equity Group assigned for the sme Equity Type. h) We assign Equity Group E01

Equity Groups Tab: a) Select the Funding Currency Tab and assign the Funding Currency. The Funding Currency assigned would be the Company Code Local Currency. However, the

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

6 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

House Bank Currency can also be maintained which is determined to be assigned to Funding Group from which all the Venture transactions would be processed.

Describe the business scenario that will be covered by this request. 2. Requirements and Assumptions N/A 2.1. Specific Requirements 2.1.1. Legal and Fiscal Requirements N/A 2.2. Assumptions 2.2.1. Business Scenario/Activity to be based N/A Inform if there is a similar business scenario already defined on which this one could be based. 2.2.2. Business Definitions to be used in the Scenario O Travel sera implementado na Urucun e na Vale Describe all business definitions that directly affect the processes involved in this request, such as: need for substitution of legacy systems by SAP, current process changes, cost reductions, etc. 2.2.3. General Assumptions N/A

Describe relevant assumptions for the process involved in this request that were not described in the items above.

2. Scenario Changes N/A

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

7 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

The objective of this section is to describe possible process changes for different business scenarios. 3.1. Due to Material Categories N/A Inform if the processes involved in the request changes due to material categories. E.g.: taxes, stock movements, accounting, pricing, etc. 3.2. Due to Client Categories N/A Inform if the processes involved in the request changes due to client categories. E.g.: taxes, stock movements, accounting, pricing, etc. 3.4. Due to Plants N/A

Inform if the processes involved in the request changes due to supplier categories. E.g.: taxes, accounting, different pricing, etc. Inform if the process involved in the request changes due to plants. E.g.: taxes accounting, pricing, etc. 3.5. Due to Sales Organization (and/or other level of the Sales Organizational Hierarchy) N/A Inform if the processes involved in the request changes due to supplier categories. E.g.: taxes, accounting, different pricing, etc. Inform if the processes involved in the request changes due to Sales Organizational Hierarchy. E.g.: taxes, accounting, pricing, etc. 3.6. Due to Purchase Organization (and/or other level of the Purchase Organizational Hierarchy) N/A Inform if the processes involved in the request changes due to Sales Organizational Hierarchy. E.g.: taxes, accounting, pricing, etc.

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

8 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

3.7. Due to Production Lines N/A Inform if the processes involved in the request changes due to production lines. 3.8. Due to Seasons N/A Inform if the processes involved in the request changes due to seasons. E.g.: pricing. 3.9. Due to Operation Type N/A Inform if the processes involved in the request changes due to operation category (e.g. operation inside or outside a state). 3.10. Others N/A Inform if the processes involved in the request changes due to criterions not listed above. 4. Configuration Impacts In the case of repeating configurations (creation of planned center, load point, store location etc.), inform the number of them. N/A 5. Test Conditions List all possible business scenarios involved in the request that should be tested. Business Scenario Test Condition Expected Output

The sections bellow are exclusively for DC use 6. Entry Criteria Version Responsible:

Data

Entry

Related

Entry

Corrected

Correction

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture


Team Prepared by

Version

Page

1.0
Approver

9 (9)

Finance
Creation Date 04/07/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

Criteria:

Criteria Document:

by:

Date:

7. Metrics Complexity

Related AP322 to be created

Estimated effort

Modified: 07/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal