Skip to main content
Dassian

Configuration

Transaction SICF – Internet Connection Framework 

In this initial step, the services for the Dassian Simple Projects Workbenches must be activated, launch transaction SICF.

First activate the service for the web based user interface, in the Service Name field enter ‘DSNPPCWB’ and click continue.

 

In the resulting screen, right click the service node ‘DSNPPCWB’ and then choose ‘Activate Service’.

 

When prompted to activate the service, choose   to activate all nodes beneath the main service node.

Next activate the service for the data provider, from the initial screen click continue to show all service nodes;

  • If the Dassian Simple Projects Workbenches are to be deployed using the SAP Netweaver Gateway, activate the following service;
    • default_host > sap > opu > odata > dsn > ppc_wb_01_srv
  • If the Dassian Simple Projects Workbenches are to be deployed using the Dassian oData connector, activate the following service;
    • default_host > dsnodata

When prompted to activate the service, choose SimpleProjects_Config (4).png  to activate all nodes beneath the main service node.

Transaction /DSN/PPC_WB_URL - Workbench Data URL

This configuration transaction is used to setup the Data URL which will be used to deploy the workbenches.

Click  to setup the data URL;

  • in the Application field enter /DSN/PPCWB01
  • in the Data URL field choose the option for the desired deployment method, either SAP Gateway or Dassian oData Connector.

 

Click save

Transaction /DSN/PPC_WB_WC - Workbench Work Centres

In this step, setup the list of work centres for use with the Dassian Simple Projects workbench, this is essentially a subset of the work centre list from the backend system. Click  and then choose;

  • Plant
  • Work Centre

Click save

Transaction /DSN/010S – Default Cost Elements

In this step, setup the list of cost elements for use with the Dassian Simple Projects workbench, this is essentially a subset of the cost element list from the backend system, click  and then choose;

  • Controlling area
  • Cost element

Click save  

Transaction /DSN/PPC_WB_CFG - PPC Workbench Configuration

In this step, setup the Planning Profile settings and the planning and EAC versions settings for the planning profile/s configured in your system.

This step is needed to ensure the system knows not only the profile level specific settings but also which are the working and approved versions. 

Together with this, create a list of reason codes for use with the Dassian Simple Projects workbench, this is a list of reasons which are used when submitting and approving data in the workbenches, a reason code may be used in multiple workbench applications if necessary.

Firstly at planning profile level, the following settings must be made;

  • A level at which your users will submit their planning data for approval, the default setting is "Submit at level where data is planned" but is also possible to submit the planning data at control account level in the Status Management view, this is useful if there is a significant amount of planning data in many work packages.
  • The planning cycle for the web workbench, currently, weekly and monthly planning cycles are supported.
  • If Time phased actual cost data will be displayed. (if this is not set, actual costs will be cumulated)

Note that with the 'submit level' setting of "Plan at Work Package Level, Submit at Control Account level" option, it is only possible to submit planning in the Status Management view.

Click  and define the planning profile level settings as shown below;

Setting up the Planning Versions

Select the planning profile and choose the "Working Planning Versions" option.

In the resulting screen, click  and then enter;

  • Working Planning version
  • Approved Planning version
  • Approval sequence (options are series or parallel)
  • Align Start Date (this will force the adherence to the work package start date when creating or editing resources in the workbench)
  • Align End Date this will force the adherence to the work package end date when creating or editing resources in the workbench)

Setting up the EAC Versions

Select the planning profile and choose the "Working EAC Versions" option.

In the resulting screen, click  and then enter;

  • Working EAC version
  • Approved EAC version
  • Approval sequence (options are series or parallel)
  • Approved Planning version (used to determine the basis of "previous period" data shown in the workbench)
  • Align Start Date (this will force the adherence to the work package start date when creating or editing resources in the workbench)
  • Align End Date this will force the adherence to the work package end date when creating or editing resources in the workbench)

Creating Reason Codes

Click  and then enter;

  • Reason Code
  • Description

 

To assign the reason codes for use with specific workbench applications,  select the reason code in the list and double click on the Workbench Reason Codes

 

 

In the next screen, click  and then choose the workbench type/s to which the reason code should be assigned.

Click save

Transaction code /DSN/010Z – Planning Profile Considerations

Available Object Maintenance

 

Dassian Simple Projects Web Workbench is designed to support planning at a single level in the project structure, however, there are multiple possibilities, in hierarchical order, Control Account, Work Package or Below Work Package.

It is important to understand that the application will always use the lowest level of the options checked as the level at which planning data is entered in the web workbench.

TransactionCode: SNUM - Number Range Maintenance

The workbenches use number ranges to control the planning objects in the background. In addition, workflow master data uses two number ranges to automatically assign to profiles. It is REQUIRED to set-up the number ranges in YOUR system. Number ranges are usually controlled by the finance organizations and are NOT normally transported. Therefore, they will have to be set-up in EACH client as the product is implemented.

Workbench Object: /DSN/OBJNR Range: 01: 1 – 9999999999

TransactionCode: SU3 - User Parameters

Each user of Simple Projects and the web workbenches must have the following parameter IDs in their username

  • Controlling Area maintained (CAC)
  • Factory Calendar Key (FCI)

 

  • Was this article helpful?