c 1v fin ap326 07.04.10 jva maintain joint venture v1-0

Document Name

C_1V_FIN_AP326_07.04.2010 JVA Maintain Joint Venture Version Page

1.0 1 (9)Team Prepared by Approver

Finance Amit Agarwal Chris HebdonCreation Date 04/07/2010 Forecast Date Status

Document Control:

Road Map Reference: AP326 – Configuration Rationale High-Level DesignTeam: FinanceStatus: Created

Last update: 4/07/2010

Reviews:Review # Date: Revised by: Revised Section:0.1

Approvals:Name: Position: Date: Signature:Chris Hebdon Operations Manager

Request OverviewModule FICriticity / / Request <Number >Description <Short Description of the Request>

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

1 Last modified by: Amit Agarwal

Document Name




Areas / Users InvolvedFinanceira

Related ProcessLevel of Business Process Name and Code New?

Process FINANCE

Sub-process Joint Venture Accounting

Activities JVA Maintain Joint Venture Master

Related Documents (BP310) <List BP310 documents affected or covered by this requirement >

Configuration GAPs N/a

Type of ConfigurationUse 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 JV2) Operated JV3) Non-Operated JV



Document Name




Corporate JV

The following consideration should be taken for maintaining Corporate JV:

1) We would essentially have only one Corporate JV2) Use a JV number from the JV Number Range maintained for Corporate JV3) The JV Class for Corporate Venture should be “CP”4) Relate / Assign the Corparate JV with the Corporate JOA5) 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 Typec) 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.



Document Name




Operated Joint Venture:

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 JV3) The JV Class for Operated Venture should be “OP”4) Relate / Assign the Operated JV with the Operated JOA5) 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) Select the Status of the Venture as “Active”b) Posting Method: Cash Call – “CCL”c) Billing Format: “VAO1” – Vale Operated Billing Formatd) Billing Extract based on Inception to Date Data: YESe) Funding Group: “OP0001”f) Select “Check Funding Currency” as Active.


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 Typec) 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



Document Name




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.

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 per Company

2) Use a JV number from the JV Number Range maintained for Non-Operated JV3) The JV Class for Non-Operated Venture should be “NP”4) Relate / Assign the Non-Operated JV with the Non-Operated JOA5) Select Venture Type as “Non-Operated”6) 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 Numberc) Posting Method: Cash Call – “CCL”d) Funding Group: “NO0001”


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 Typeg) 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:



Document Name




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.

Describe the business scenario that will be covered by this request.

2. Requirements and Assumptions

N/A2.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.



Document Name




2. Scenario Changes

N/A

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 PlantsN/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



Document Name




Inform if the processes involved in the request changes due to Sales Organizational Hierarchy. E.g.: taxes, accounting, pricing, etc.

3.7. Due to Production LinesN/A Inform if the processes involved in the request changes due to production lines.

3.8. Due to SeasonsN/A Inform if the processes involved in the request changes due to seasons. E.g.: pricing.

3.9. Due to Operation TypeN/A Inform if the processes involved in the request changes due to operation category (e.g.

operation inside or outside a state).

3.10. OthersN/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



Document Name




The sections bellow are exclusively for DC use

6. Entry CriteriaVersion Responsible: Data Entry

Criteria:Related Entry Criteria Document:

Corrected by:

Correction Date:

7. MetricsComplexity Related AP322 to be created Estimated

effort

