Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

Authorizations & Roles

Author(s)

Verification

Approval

João Matos Machado
RtR I&D
Hugo Vinagre
RtR I&D Operational Specialist

Cátia Pinto
RtR SC Transv. Project & Optimization OPS L2

Michel Berger
Process Expert WW
Invest & Divest

29/07/2017

01/07/2017

15/07/2017

...

Version

Date

Description

01

29/07/2017

New Document

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

Anchor
_Toc486435685
_Toc486435685
Objective of this Procedure
Anchor
Application
Application
Anchor
_Toc364693744
_Toc364693744
Anchor
_Toc45612200
_Toc45612200

The purpose of this document is to describe the transactions related to the process of investment budget requirement and approval as well as depreciation planning

Anchor
_Toc364932388
_Toc364932388
Anchor
_Toc486435686
_Toc486435686
Scope
Anchor
Definitions
Definitions
Anchor
_Toc45612201
_Toc45612201
Anchor
_Toc364693745
_Toc364693745

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

Anchor
_Toc486435687
_Toc486435687
Abbreviations

...

SPD


SU MAC - Service Unit - Management accounting

SPD - Standard

...

Project Definition

...

PS

...

PS   - Project System (SAP module)

Capex/COLMAR Team

...

- Department that manage and approve the Budget

BDG - Budget

...

Anchor
_Toc486435688
_Toc486435688
Responsibility


SBS

SU MAC

Creation of new projects, insert and maintain Budget + Planned Cost

Capex/COLMAR Team

Department that manage and approve the Budget and sent to

SBS for

SU MAC for creation/update

 


Anchor
_Toc486435689
_Toc486435689
Budget approval and budgeting

Anchor
_Toc486435690
_Toc486435690
Target process for Projects


Anchor
_Toc486435691
_Toc486435691
Project Creation

Anchor
_Toc486435692
_Toc486435692
The Standard Project definition

Responsibility


SBS

SU MAC

SBS

SU MAC is responsible to create and maintain SPD – Standard Project Definition .

IS

Anchor
_Toc241821407
_Toc241821407
Anchor
_Toc241822008
_Toc241822008
IS is responsible to create the project profile under

SBS request

SU MAC request.

Local Accountants

Local accountants have to validate the SPD created / modified by

SBS.

SU MAC
Local accountants might adjust or modify the WBS structure accordingly with their needs.



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


SPD
Notion

Solvay



Syensqo Core Structure


Standard Project Definitions are used as a template to create new projects in SAP module PS. To avoid errors or mistakes, Standard Project Definitions are created per company code/plant code/business area (division/profit center).

In the scope of

Solvay

Syensqo development, a standard structure for investment projects was developed. The SPD structure could be as follows:



The codification for Standard Project Definition numbers is as follows:

Plant Code

Slash

Budget Size (C or S)

0

Business Area

BWF

/

C

0

7336


Note: For Germany, please refer to the Country Specificity topic, on this operational procedure.
|

...


The transactions for Standard Project Definitions are:

CJ91 Create
CJ92 Change
CJ93 Display
















































The project profile is the main requisite to create a SPD.
Therefore, before starting to create a SPD it is necessary to check if there is any project profile under Plant/Business Area/(Profile – Investment) related to.



Use transaction CJ91 to check the project profile:
Image Modified


The creation of the project profile has to be requested to IS, via

Fresdesk

SYRA, pointing out the following data:

  • Controlling area
  • Company Code
  • Plant
  • Profit center
  • Project currency
  • Investment Profile
  • Business Area


    The SPD creation can proceed, if the required project profile is available.







    To create the SPD perform transaction CJ91:
  1. Insert the codification of the SPD to be created and then select the relevant project profile:

    Image Modified

    Click in Image Modified and you will have a new screen with the main information about the SPD.
    Image Modified
  2. Insert the description of the SPD and if needed update some fields (e.g. company code).
  3. Once finished click in Image Modified to access the WBS elements overview where you should include the basic WBS structure:


    Image Modified

    Then Save Image Modified and the SPD is created.

Anchor
_Toc254605003
_Toc254605003
Anchor
_Toc254605523
_Toc254605523
Anchor
_Toc254605570
_Toc254605570
Anchor
_Toc254615243
_Toc254615243

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)

...

All
Germany
France
United States
  • Normally a standard project definition is created for each combination of Plant/Business Area/Company Code

We need to use SPD with a specific structure for the countries mentioned below (France, Belgium, Italy - exception for Spinetta and Bollate, Spain and Germany):


Type 1:
Project Definition TAE/C13000
Level 1 WBS TAE-C13900
Level 2 WBS TAE-C13800.NA (for Not Assigned Costs)
End

Type 2:
Project Definition TAE/C13800
Level 1 WBS TAE-C13800
End

  • By using this structure Local Team will be able to update WBS using IS Excel development.
In Germany the last digit of the business area is used to identify the site

Site

Plant

Business Area

Hannover

H**

***0

Rheinberg

R**

***1

Bernburg

B**

***2

Frankfurt

FRF

***3

Bad Wimpfen

BW*

***6

France
  • There is an exception for France, where we have more than one SPD by Plant/Business Area/Company Code.
    Other data is needed to define projects in France, which is the reason for Investment.
  • Therefore, if in Capex file the Reason for Investment is B4 – Major Repairs, the SPD to be used will be the one with Investment Profile ZFR013 or ZXX003 for other counties.
    Profile ZFR003 is used to register the budgets of Stops for Major Repairs as Assets in IFRS Accounts, but in French accounting they are registered as provisions
  • If the last digit of the SPD is :
  • 1 than mean that it is an investment project.
  • 2 than mean that it is a Demolition project.
  • 3 than mean that it is a Subsidies project.
  • 4 than mean that it is a Major repair project.

Germany


Site

Plant

Business Area

Hannover

H**

***0

Rheinberg

R

Bad Hönningen

H

**

***

7

1

Bad Hönningen

Bernburg

HOR

B**

*0

Epe

EPS

***8

...

***2

Frankfurt

FRF

***3

Bad Wimpfen

BW*

***6

Bad Hönningen

H**

***7

Bad Hönningen

HOR

***0

Epe

EPS

***8

  • For the Germany companies the demolition project creation should be done using Investment Project Profile.
  • The SPD to use is YYY/C1XXXX instead of YYY/C0XXXX (that is the codification for all countries)



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:
  • Check if the WBS is already added in the WBS structure of the normal or special project, if not SBS SU MAC has to add it using transaction CJ02;
  • Insert the budget and cost planning values in the demolition WBS level (CJ30 and CJ40).


    2) The demolition project is not connected to any further construction. In this case, the demolition project should be created as a new project in transaction CJ01 with the codification sent in the request by Capex/COLMAR team.
    After the creation, the budget and cost planning values should be inserted using CJ30 and CJ40.


    Demolition Project Remark:

    To create a new Project Demolition it is used a SPD as reference. If the SPD used is related to a Investment project you should check the Demolition WBS properties, because it can assume the Investment properties of this SPD.

    The WBS Demolition should have the following data.

    a) Select the Level 1 Demolition WBS and click in detail :



    b) In Tab Basic Data:
    In ERP:
  • 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":







    Image Modified




    Image Modified


    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 Image Modified :
    Image Modified
    Replace 550 by XXX like in WBS element:
    Image Modified
    Click on "Edit", "Status", "Deletion Flag":
    Image Modified
    Save your data Image Modified .

     



    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:

    Image Modified

    Save Image Modified the changes made in the original budget.

    Then, go to transaction CJ02 and set the status to technically complete (TECO):

    Image Modified

     

     

     

     





    To have the status set, save Image Modified the project.

    After that, set the status closed for the project created incorrectly (CLSD):

    Image Modified

    Save Image Modified the project.

    You will have the following system status:

    Image Modified


    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 Image Modified

    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:
  • To ZZ2003 – Investment w/o ATB-check


Anchor
_Toc486349291
_Toc486349291
Anchor
_Toc486435702
_Toc486435702
Transfer of Original Budget - CJ34


The original budget is never changed with CJ30. To transfer amounts from project or to project or from year to year use CJ34. Call up CJ34 and enter "sender year", "receiver year" and "text".

Enter the "sender WBS element", the "receiver WBS element", "currency" and "amount to be transferred (always use the thousand format , for instance if the related amount is 30 K Eur, it should be inserted the amount 30.000,00 Eur)" and click on button "check (F9)" and save.



Anchor
_Toc486435703
_Toc486435703
Change Supplement - CJ37

This transaction is used to increase the budget amount. Call up CJ37, make the required entry project definition:

Enter the amount to be added in the budget:

Click button "Annual Overview" and enter the annual amounts (only the value to be added in the budget):

Click button "Check (Shift + F4)" and "Save (Ctrl + S)".

Anchor
_Toc486435704
_Toc486435704
Change Return - CJ38



This transaction is used to return unnecessary budget amounts. The screens are similar to CJ37.

Anchor
_Toc486435705
_Toc486435705
Project creation using transaction ZZJ01

For each Project to be created, the program selects the Standard Project created in the corresponding Company/Plant/Business Area, and uses it as template to create the WBS elements.
Notes:

...





Preliminary:
The file used by CAPEX/COLMAR to exchange data related to CAPEX budgets must be checked and converted to a format accepted by the program:

  1. Check the file is correctly completed (especially lines corresponding to Projects to be created). Here are the columns used by the program:

...



Example attached in Excel format:

Anchor
_MON_1560174244
_MON_1560174244

Anchor
_Toc486349295
_Toc486349295
Anchor
_Toc486435706
_Toc486435706
Create PS projects before COLMAR-Start transaction ZZJ01

You get the following screen:

Anchor
_Toc486349296
_Toc486349296
Anchor
_Toc486435707
_Toc486435707
Complete the following fields :


Colmar file

DO NOT flag the checkbox

Creation PROJECTS

Select the option "Create PROJECT"

Input file

Use the button at the end of the field ( Image Modified ) to select the TXT file used as input.

Session name

Give any name. (this name will be given to the batch input file that will be created by the program).

Year

The year entered in this field is used by the program to select records to be treated. (check on column AK : "Approval Year").Note: the program also checks that the status of the project is REL.

Test run

This flag allows to run the program in test mode, in order to check the content of the file.


Click on   to start the program.
Output of the transaction:
1. If executed in test mode, the program will:

...


Check the list issued by the program; if the Projects and WBS are correct, then execute the SBDC session with transaction SM35 (background mode).
When the SBDC has finished to run, check its status and correct errors if any.

Anchor
_Toc486349297
_Toc486349297
Anchor
_Toc486435708
_Toc486435708
Create Budget and Planned costs-Start transaction ZZJ01 for file before COLMAR

You get the following screen:

Anchor
_Toc486349298
_Toc486349298
Anchor
_Toc486435709
_Toc486435709
Complete the following fields :

Colmar file

DO NOT flag the checkbox

Creation BUDGET + PLANNED COSTS

Select the option "Creation BUDGET+PLANNED COSTS"

Input file

Use the button at the end of the field ( Image Modified ) to select the TXT file used as input.

Session name

Give any name. (this name will be given to the batch input file that will be created by the program).

Year

The year entered in this field is used by the program to select records to be treated.Note: the program also checks that the status of the project is REL.

Test run

This flag allows to run the program in test mode, in order to check the content of the file.


Click on   to start the program.
Output of the transction:
If flag "Test run" not set, the program will:

...


Then, execute the SBDC sessions with transaction SM35 (background mode).
When the SBDC has finished to run, check its status and correct errors if any.


Remark: PS Projects created by the program, with their budget planned costs can be listed using transaction CN41 and PSIS report CJE0 – 12KST1A.

...





Transaction S_ALR_87013560
This transaction is used for the general overview of budget updates. Call up the transaction, enter the WBS element and press button "Execute (F8)":

Image Modified


Anchor
_Toc241821428
_Toc241821428
Anchor
_Toc241822029
_Toc241822029
Anchor
_Toc486349299
_Toc486349299
Anchor
_Toc486435710
_Toc486435710
Uploading COLMAR file format





COLMAR format could be uploading only for the following three options:

  • To create PS Projects + WBS level 1 for investment budgets.
  • To create/update Budget for these PS projects
  • To change Project status to Technical complete (TECO)

...

Preliminary:
The file used should be downloading of proper Query in COLMAR application. It must be checked by BO team and converted to a format accepted by the program:

  1. Check the file is correctly completed (especially lines corresponding to Projects to be created). Here are the columns used by the program:
  • 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




COLMAR

 

 



PS in

PF1

 

 

PF2



FAMILY

Family Name

PROJ-ZZFAMILY

 


Family Name

FACILITIES

Facilities

FACILITIES

 


Facilities

GEC

GEC

GEC

 


Group Engineering & Construction

RI

R&I

R&I

 


Research & Innovation

REGAFFAIRS

REGAFFAIRS

REGAFFAIRS

 


Regulatory Affairs

RG

Regular

REGULAR

 


Regular

SBS

GBS-DPS

SBS

GBS-DPS

SBS SBS

GBS DPS

 


GBS - All services except IS

SBS

GBS-IS

SBS

GBS IS

SBS SBS

GBS IS

 


GBS - Informational System





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.

COLMAR

 


PS in

PF1 

PF2


Investment type

 


Scale

 

CUR

Current

CN

Current

STR

Major

ST

Major

NRM

Medium

NM

Medium

DEM

Demolition

BD

DEMOLITION BUDGET

PRE

Preliminary

PR

Preliminary


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:

...



Example for all the options attached in Excel format:

Anchor
_MON_1560177100
_MON_1560177100

Anchor
_Toc486349300
_Toc486349300
Anchor
_Toc486435711
_Toc486435711
Create PS projects for COLMAR-Start transaction ZZJ01

You get the following screen:

Anchor
_Toc486349301
_Toc486349301
Anchor
_Toc486435712
_Toc486435712
Complete the following fields :


Colmar file

Flag the checkbox

Creation PROJECTS

Select the option "Create PROJECT + WBS Level 1"

Input file

Use the button at the end of the field ( Image Modified ) to select the TXT file used as input.

Session name

Give any name. (this name will be given to the batch input file that will be created by the program).

Year

The year entered in this field is used by the program to select records to be treated. (check on column C : "Approval Year").Note: the program also checks that the status of the project is FA or AB.

Test run

This flag allows to run the program in test mode, in order to check the content of the file.


Click on   to start the program.
Output of the transaction:
1. If executed in test mode, the program will:

...


Check the list issued by the program; if the Projects and WBS are correct, then execute the SBDC session with transaction SM35 (background mode).
When the SBDC has finished, check its status and correct errors if any.





Anchor
_Toc486349302
_Toc486349302
Anchor
_Toc486435713
_Toc486435713
Create/Change Authorized Budget for COLMAR-Start transaction ZZJ01

You get the following screen:


Anchor
_Toc486349303
_Toc486349303
Anchor
_Toc486435714
_Toc486435714
Complete the following fields :


Colmar file

Flag the checkbox

Create/Change Author. Budget

Select the option "Create/Change Author. Budget"

Input file

Use the button at the end of the field ( Image Modified ) to select the TXT file used as input.

Session name

Give any name. (this name will be given to the batch input file that will be created by the program).

Year

The year entered in this field is used by the program to select records to be treated.Note: the program also checks that the status of the project is FA or AB.

Test run

This flag allows to run the program in test mode, in order to check the content of the file.


Click on   to start the program.
Output of the transction:
If flag "Test run" not set, the program will:

...


Then, execute the SBDC sessions with transaction SM35 (background mode).
When the SBDC has finished, check its status and correct errors if any.

 


As mentioned above the original budget in PS is only changed in a limited number of cases with special transactions. The tool for simulations, estimations and forecasts is the cost planning. To have a clear distinction, different plan versions are used.



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.











Anchor
_Toc486435716
_Toc486435716
Cost Planning - CJ40


This transaction includes initial cost estimate as well as changes (supplements, returns etc.). Entries are possible on all levels of WBS element. Call up the transaction, enter a project definition or WBS element and select the wanted version:


CJ40
Similar to transactions for budgeting, entries for overall and annual overview are possible:



For Subsidies Projects, the values must be negative!

 


Anchor
_Toc486435717
_Toc486435717
Reports for Budget and Planned costs

Anchor
_Toc486435718
_Toc486435718
Report CJE0 for

PF1

PF2



Reports Actual/planed costs
ZZJDOWNPAY for

PF1

PF2 
To keep track of budget and planning as well as actual cost, use report ZZJDOWNPAY.
Call up transaction CJE0, select ZZJDOWNPAY with a double click:
Image Modified Image Modified

Insert project and plan version (AFC), select the output type and click on button "
Execute (F8)":


 

 

 









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


|

Anchor
_Toc129428432
_Toc129428432
Anchor
_Toc191625960
_Toc191625960
Anchor
_Toc241821431
_Toc241821431
Anchor
_Toc241822032
_Toc241822032
Anchor
_Toc486349306
_Toc486349306



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





End of document