Authorizations & Roles

...

AnchorTableofcontentsTableofcontents Anchor_Toc45612198_Toc45612198 Anchor_GoBack_GoBack Table of contents
1 Objective and Scope
1.1 Objective of this Procedure
1.2 Scope
2 Abbreviations
3 Responsibility
4 Budget approval and budgeting
4.1 Target process for Projects
4.2 Project Creation
4.2.1 The Standard Project definition
5 Projects types that could be managed for PF1 PF2 and WP1 WP2 
6 Standard Project Definition Creation for PF1 PF2 only
6.1 Standard Project Definition (SPD) with country Specificities
7 Demolition Project Creation
7.1 Demolition Project Creation:
7.2 Changing Project – CJ02:
7.3 Project deletion
8 BUDGETING
8.1 Original Budget- CJ30
8.2 Transfer of Original Budget - CJ34
8.3 Change Supplement - CJ37
8.4 Change Return - CJ38
9 Project creation using transaction ZZJ01
9.1 Create PS projects before COLMAR-Start transaction ZZJ01
9.2 Complete the following fields :
9.3 Create Budget and Planned costs-Start transaction ZZJ01 for file before COLMAR
9.4 Complete the following fields :
10 Uploading COLMAR file format
10.1 Create PS projects for COLMAR-Start transaction ZZJ01
10.2 Complete the following fields :
10.3 Create/Change Authorized Budget for COLMAR-Start transaction ZZJ01
10.4 Complete the following fields :
11 Plan Versions only for PF1 PF2 
12 Cost Planning - CJ40
13 Reports for Budget and Planned costs
13.1 Report CJE0 for PF1 PF2 
13.2 Report S_ALR_87013558 for WP1 WP2 

Anchor
_Toc486435684 _Toc486435684

Objective and Scope

...

This operating procedure (OP) applies to the necessary transactions for approval and planning process of the current PF1 PF2 & WP1WP2.

Anchor
_Toc486435687 _Toc486435687

Abbreviations

...

Anchor
_Toc486435693 _Toc486435693

Projects types that could be managed for

...

PF2 and

...

WP2

Project types which could be managed are:
N: Normal
C : Current
M: Medium
J: Major
D: Demolition
P: Preliminary/Approach/Test

Anchor
_Toc241821409 _Toc241821409

Anchor
_Toc241822010 _Toc241822010

Anchor
_Toc486349284 _Toc486349284

Anchor
_Toc486435694 _Toc486435694

Standard Project Definition Creation for

...

PF2 only

...

...

Anchor
_Toc486349285 _Toc486349285

Anchor
_Toc486435695 _Toc486435695

Standard Project Definition (SPD) with country Specificities

...

...

All companies/all plants – always copy

...

solvay.taxsupport@Ryan.com

...

Solvay Chemicals, Inc. (all plants)

...

newcapex.SCI-US@solvay.com

...

Solvay Fluorides LLC (all plants)

...

newcapex.SFLLC-US@solvay.com

...

 Solvay Solexis, Inc. (all plants)

...

newcapex.SSI-US@solvay.com

...

Solvay Specialty Polymers USA (LLC)

...

 Alpharetta plant (AIS)

...

newcapex.SSP-alpharetta@solvay.com

...

Augusta plant  (AQS)

...

newcapex.SSP-augusta@solvay.com

...

Greenville plant (GDS)

...

newcapex.SSP-greenville@solvay.com

...

Marietta plant (MJS)

...

newcapex.SSP-marietta@solvay.com

...

Solvay America Inc. (all plants)

...

newcapex.sis-nafta@solvay.com

Anchor
_Toc486435696 _Toc486435696

Demolition Project Creation

Anchor
_Toc486435697 _Toc486435697

Demolition Project Creation:

There are two situations that might occur with Demolition Project Creation:

1. The demolition project corresponds to a construction project. In this case, the demolition project should get the same numbering (YYAAA) of an existing normal or special project and this demolition project should be created as a WBS under the project XXX/NYYAAA or XXX/SYYAAA, under the following steps:

...

• Insert in the field Proj. Type - DEMOLITION (ERP)
  
  
  
  
  Then go to Tab Assignments and check the Field Object Class inserting OCOST Overhead.
  
  
  
  
  |

  Anchor
  _Toc486349287 _Toc486349287

  Anchor
  _Toc486435698 _Toc486435698

  Changing Project – CJ02:

  
  

The project update is performed in transaction CJ02.

Before update any project SU MAC has to check if there is any posting amount on WBS Project:

In case of:

• 
  

  1. No posting amount on WBS:
     RTR
     
     SU MAC can proceed in changing the Business Area, Profit Center and Texts fields of general and WBS data.
  2. Posting amount on WBS :
• RTR SU MAC can proceed in changing the Business Area, Profit Center and Texts fields of general data and WBS " level 4 " without any amounts posted data.
• How to proceed regarding WBS "level 4" with posting amounts:
  
  Send a communication to Local Accountants explaining the need to change the original data and informing that they should:
  
  a) Create another WBS " level 4 " for the ones already with value,
  b) Transfer the amounts from the old WBS to the new one.
  

  Anchor
  _Toc241821420 _Toc241821420

  Anchor
  _Toc241822021 _Toc241822021

  c) And block the first one.
  |
  

  Anchor
  _Toc241821421 _Toc241821421

  Anchor
  _Toc241822022 _Toc241822022

  
  
  
  

  Anchor
  _Toc486435699 _Toc486435699

  Project deletion

  
  

  Deletion of projects without budget or planning values

  
  If projects have been created by mistake and the status is still "Created" and neither budget nor planning values have been maintained, it is possible to delete such projects.
  First step is always to check the project status and budgeting. Call up transaction CJ02, enter the project number and push "Enter":
  
  
  
  
  
  
  
  
  
  
  
  
  

  Scroll to the right an check system status: In this case the project could not be deleted directly; you have to set the deletion flag (see SAP description below). If you want to reuse the project number in a new project, you have to rename your project before setting the deletion flag.

  
  
  Call up CJ02. Replace 550 by XXX and click on project definition button :
  
  Replace 550 by XXX like in WBS element:
  
  Click on "Edit", "Status", "Deletion Flag":
  
  Save your data .

  	Deletion of projects with a budget assigned If a project was created by mistake and a budget was already assigned to it, it is not possible to simply delete the project. However, if there are no costs associated to the project, there is a way to correct it. First, go to transaction CJ30 and set the annual and the overview budget values to zero: Save the changes made in the original budget. Then, go to transaction CJ02 and set the status to technically complete (TECO):
  	To have the status set, save the project. After that, set the status closed for the project created incorrectly (CLSD): Save the project. You will have the following system status: Remark: If you want to reuse the project number in a new project, you have to rename your project before setting the deletion flag.
  	Deleting WBS elements ( SAP documentation ) Use Under certain prerequisites you can delete WBS elements directly, that is, delete physically. You cannot undo the physical deletion of WBS elements. You can give WBS elements that cannot be deleted directly the Deletion flag status. They are deleted from the project logically. Prerequisites You can only delete WBS elements directly, if they have the status Created or Released and no postings or assignments to other objects exist. Integrated planning WBS elements can be deleted as long as no planned costs or revenues have been posted. You cannot delete WBS elements with the status Released. Features Set the Deletion flag status for WBS elements if they have any other status than Created or Released. As long as the WBS elements have the status Deletion flag and deletion indicators have not been set, you can cancel the deletion flag. Activities
  Function	Menu Path
  Delete WBS elements directly	Edit  _Delete   → Delete → Delete object _ or
  Provide the WBS element with a deletion flag.	Edit  _Status   → Status → Deletion flag_
  Canceling Deletion Flags	Edit  _ → Status  → Revoke deletion flag_

  
  If you delete WBS elements or set a deletion flag for them, subordinate WBS elements, and assignments are also deleted or have a deletion flag set.
  
  
  | | |

  To be able to revoke the deletion flag, you must first show the WBS elements that have been flagged for deletion. To do this, choose Edit  → Object  → _Display deleted  → Disp._ The WBS elements with deletion flags are highlighted in grey. You can now cancel the deletion flag for the required WBS elements.

  Anchor
  _Toc241821422 _Toc241821422

  Anchor
  _Toc241822023 _Toc241822023

  Anchor
  _Toc486349289 _Toc486349289

  Anchor
  _Toc486435700 _Toc486435700

  BUDGETING

  Anchor
  _Toc486435701 _Toc486435701

  Original Budget- CJ30

  The original budget has to be recorded after approval, release and creation of a new project in the system.
  Call up transaction CJ30.
  Insert Project Definition and click on "Original Budget":
  
  
  First step is the total amount on top WBS element level:
  
  Second step is the annual overview:
  
  Finally: save your data !
  
  For Subsidies Projects you must enter the budget with negative values.
  

  Anchor
  _Toc203210691 _Toc203210691

  
  
  To save you have to do it without checking:
  
  
  If for some reason the system doesn't allow you to do that, you have to change the budget profile in CJ02:

...

• Column C: Approval year
• Column D: PS Project ID
• Column E: PS Project description
• Column F: Status (only budget with status FA or AB will be treated by the program for Project creation and Status TC for Change Project status)
• Column O: Plant code (2 or 3 digits plant code)
• Column U: company code
• Column W: BFC GBU
• Column Y: Family Inv. Project
• Column AC: Investment reason
• Column AE: Investment type (in PF1 PF2 called Scale)
• Column AG: Forecaster (in PF1 PF2 linked to Responsible person) - it is the user ID of Project forecaster in COLMAR which we are linked to field Responsible person
• Column AH: Currency
• Column AI: Project group
• Column AJ : Profit center/Business Area
• Column AK: Authorized (Total) amount (should be w/o Currency format)
• Columns AL to AQ: yearly amounts. (The year is shifted left every year (Y+1). For new budgets, column C corresponds to the year of the Approval Year (specified in column AM).Example: End 2015/begin 2016 (= approval year 2016), columns AM to AR range from = 2016 till >=2021; column AM contains amount for 2016).

Notes:
Field Family Inv. Project (Column Y):
In the table below we have possible entries for field Family Inv. Project. As we have difference between values in COLMAR and PS PF1 PF2 system, we use table ZZS_T900 to make the mapping between both:
*in yellow color are entries in the table ZZS_T900

Field: Investment type – Scale
In the table below we have possible entries for field Investment type in COLMAR application which corresponds to field Scale in PS module. As we have difference between values in both systems, we use table ZZS_T900 to make the mapping between both.

Field Responsible person: As in COLMAR we do not support the Responsible Persons numbers we can link another field called Forecaster User ID to the proper person in PS. To find the proper Responsible person code in PS module we have accurately to update current table to manage both fields.
Transaction: OPS6
Table: TCJ04, access with transaction SM30
System: PF1PF2_020

1. Format the file as required by the program:

...

Anchor
_Toc486435715 _Toc486435715

Plan Versions only for

...

PF2

0 Initial cost estimate (SAP standard version for CO objects)

AFC Anticipated Final Cost (up to date best forecast) is the Solvay Syensqo version for revision of plan data.

...

The report includes the most important figures: plan, budget, actual cost and down payments, commitments, assigned and available amount

Anchor
_Toc486435719 _Toc486435719

Report S_ALR_87013558 for

...

WP2

|