Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

1 (6)

Finance
Creation Date 04/14/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/14/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: 14/04/2010 2008 Accenture. All Rights Reserved.

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

2 (6)

Finance
Creation Date 04/14/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 Equity Adjustments
<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. We have JVA Equity Adjustment for Pre-Cutback and Prior Period Equity Adjustments.

1.1.1

Equity Adjustment Document Types and Number Range

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

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

3 (6)

Finance
Creation Date 04/14/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

Maintain a separate Document Type for Equity Adjustments. We may consider to define EA as the Document Type for Operator Cutback. Document Type Number Range 57 Reverse Document Type EA Account Types Allowed Customer, Vendor, GL Account Debit Recovery Indicator CB Credit Recovery Indicator CB Number Range for the Document Type EA may be considered as 57: Number Range 57 Year - 9999 From Number 5700000000 To Number 5799999999 External Number NO

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

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

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

4 (6)

Finance
Creation Date 04/14/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

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 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,

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

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

5 (6)

Finance
Creation Date 04/14/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

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. 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

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

Last modified by: Amit Agarwal

Document Name

C_1V_FIN_AP326_14.04.2010 JVA Equity Adjustment Configs

Team Prepared by

Version

Page

1.0
Approver

6 (6)

Finance
Creation Date 04/14/2010

Amit Agarwal
Forecast Date

Chris Hebdon
Status

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 Criteria:

Related Entry Criteria Document:

Corrected by:

Correction Date:

7. Metrics Complexity

Related AP322 to be created

Estimated effort

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

Last modified by: Amit Agarwal