The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>PLANTALinkDocumentation>PLANTALinkStandardInterfaces

PLANTA link: Standard Interfaces

New from DB 39.5.15

Standard Interfaces for Jira

Jira: Create User

  • Creates PLANTA users in Jira
    • The default password is start1234 and should be changed during the first login

Jira: Link Jira user with PLANTA

  • Links PLANTA and Jira users who have the same e-mail address

Jira: Refresh all users

  • Refreshes all values of the synchronized Jira users in accordance with the corresponding PLANTA users

Jira: Create project

  • For a project to be synchronized in PLANTA project, a respective project is created in Jira

Jira: Refresh project

  • Refreshes the project in Jira which corresponds to the project in PLANTA project to which changes were made

Jira: Create issue

  • For a task to be synchronized in PLANTA project, a respective issue is created in Jira

Jira: Refresh issue

  • Refreshes the issue in Jira which corresponds to the task in PLANTA project to which changes were made

Jira: Import work loads

  • Imports the hours worked recorded on issues in Jira to the respective tasks in PLANTA project

New from DB 39.5.11

Standard interfaces for PLANTA pulse (Hybrid)

Pulse: Create User

  • Creates PLANTA users in PLANTA pulse

Pulse: Link Pulse user with PLANTA

  • Links PLANTA and PLANTA pulse users who have the same e-mail address

Pulse: Refresh all users

  • Refreshes all synchronized PLANTA pulse users in accordance with the values from their corresponding PLANTA users

Pulse: Create board container

  • Creates a PLANTA project project as a BoardContainer in PLANTA pulse

Pulse: Refresh BoardContainer

  • Refreshes the BoardContainer in PLANTA pulse which corresponds to the changed PLANTA _project_project

Pulse: Refresh all BoardContainer

  • Refreshes the values of all synchronized BoardContainer in PLANTA pulse in accordance with the values of their corresponding PLANTA project projects.

Pulse: Create boards

  • Creates PLANTA project tasks as boards in PLANTA pulse

Pulse: Refresh boards

  • Refreshes the boards in PLANTA pulse which correspond to PLANTA project tasks of the project currently selected for editing

Pulse: Refresh all boards

  • Refreshes the values of all synchronized boards in PLANTA pulse in accordance with the values of their corresponding PLANTA project tasks.

Pulse: Create list

  • Creates default lists within a board
  • Is opened once for each board by the Create board interface

Pulse: Create BoardMember

  • Creates PLANTA project resource assignments as resource assignments in PLANTA pulse

From DB 39.5.16

Standard Web Interfaces for PLANTA pulse (Hybrid)

Since web interfaces do not possess a template system, these interfaces cannot be used as templates for the creation of new web interfaces.

Time Recording NEW

  • Transfers the hours reported on PLANTA project tasks in PLANTA pulse to the same tasks in PLANTA project
go to the description

Workload - Load

  • Transfers the hours reported on cards in PLANTA pulse to the tasks in PLANTA project

Member - Resource Assignment

  • Copies the member assignments created in PLANTA pulse to PLANTA project as resource assignments for the respective task

New from DB 39.5.11

Standard Web Interfaces for PLANTA pulse (Hybrid)

Since web interfaces do not possess a template system, these interfaces cannot be used as templates for the creation of new web interfaces.

Workload - Load

  • Returns the work reporting created in PLANTA pulse to PLANTA project

Member - Resource Assignment

  • Copies the member assignments created in PLANTA pulse to PLANTA project as resource assignments for the respective task

Standard Interfaces for SAP

New from DB 39.5.11

BAPI_BUS2054_GETDATA

Information
  • This interface imports data of the BAPI to the PLANTA SAP WBS Element Table. The WBS elements are imported shallowly with their names.

BAPI_PROJECT_GETINFO

Information
  • This interface imports data of the BAPI to the PLANTA SAP WBS Element Table. The WBS elements are imported with structure and costs.

From DB 39.5.11

SAP WBS Import

Information
  • The SAP WBS Import interface serves to import an alternative WBS, in this case the SAP WBS, to link it to the PLANTA structure subsequently by assigning PLANTA WBS elements (tasks) to the SAP-WBS elements.
    • NEW The WBS is imported with account assignment elements via which the effort/costs is (are) imported/exported. See the SAP planned costs export and SAP planned costs import interfaces.
  • The import is done from a CSV file via the pool to PLANTA project.

SAP Planned Costs Export

Information
  • The SAP Planned Costs Export interface serves to export effort and costs planned in PLANTA to SAP to, e.g., plan budgets in SAP in that way.
    • The export is done on the basis of the SAP WBS which must have been exported to PLANTA (see SAP WBS Import interface above) and linked to the PLANTA structure (by assigning SAP WBS elements to PLANTA tasks), to guarantee the summarization of costs from PLANTA tasks to SAP WBS elements.
  • The export is done from PLANTA project via Pool to a CSV file.
  • NEW It is exported from account assignment level.

SAP Work Planned Costs Import

Information
  • The SAP Plan Cost Import interface serves to import costs from the SAP system to PLANTA project to compare them to PLANTA costs and to make efficient cost controlling in PLANTA project on this basis.
    • Import is done on the basis of the SAP WBS which must have been imported to PLANTA previously (see SAP WBS Import above).
  • The import is done from a CSV file via the pool to PLANTA project.
  • NEW It is imported to account assignment level.

New from DB 39.5.9

SAP WBS Import

Information
  • The SAP WBS Import interface serves to import an alternative WBS, in this case the SAP WBS, to link it to the PLANTA structure subsequently by assigning PLANTA WBS elements (tasks) to the SAP-WBS elements.
  • The import is done from a CSV file via the pool to PLANTA project.

SAP Planned Costs Export

Information
  • The SAP Planned Costs Export interface serves to export effort and costs planned in PLANTA to SAP to, e.g., plan budgets in SAP in that way.
    • The export is done on the basis of the SAP WBS which must have been exported to PLANTA (see SAP WBS Import interface above) and linked to the PLANTA structure (by assigning SAP WBS elements to PLANTA tasks), to guarantee the summarization of costs from PLANTA tasks to SAP WBS elements.
  • The export is done from PLANTA project via Pool to a CSV file.

SAP Planned Costs Import

Information
  • The SAP Plan Cost Import interface serves to import costs from the SAP system to PLANTA project to compare them to PLANTA costs and to make efficient cost controlling in PLANTA project on this basis.
    • Import is done on the basis of the SAP WBS which must have been imported to PLANTA previously (see SAP WBS Import above).
  • The import is done from a CSV file via the pool to PLANTA project.

Standard Interfaces for Files

New from DB 39.5.11

Conversion Factor Import

Information
  • This interface imports conversion factor positions from a CSV file and can create new ones or update existing ones if the Valid from date is included.

New from DB 39.5.8

Import of Absence

Information
  • This interface serves to import absence data of the employees to PLANTA project.

Load Import

Information
  • The template serves to import hours or costs in PLANTA.
  • Here it is exemplified how such an import is done.

What does this interface do?

From DB 39.5.7

  • This interface imports hours/costs from a CSV file.
  • There is a mapping that consists of two steps.
  • In the first step, the data is transferred from a CSV file to a load pool table (DT563).
  • In the second step, the data is written in the source table (DT472).
  • This mapping has been designed especially for load import since the transferred records are stamped in the target table (in the SAP status field and NEW additionally in the Imported on, Imported by fields).
    • In order to see which values have already been exported, PLANTA recommends to include the SAP status data field in the mapping.
  • This way you can make sure that the load can no longer be changed after export (except for deletion).

From S 39.5.8

  • This interface imports hours/costs from a CSV file.
  • There is a mapping that consists of two steps.
  • In the first step, the data is transferred from the CSV file into a pool table.
  • In the second step, the data is written in the source table (DT472).
  • This mapping has been designed to meet the requirements of load import since the transferred records are stamped in the source table (in the SAP status field).
    • NEW In order to see which values have already been exported, PLANTA recommends that you include the SAP status data field in the mapping.
  • This way you can make sure that the load can no longer be changed after export (except for deletion).

    • Up to S 39.5.8

  • This interface imports hours/costs from a CSV file.
  • There is a mapping that consists of two steps.
  • In the first step, the data is transferred from the CSV file into a pool table.
  • In the second step, the data is written in the source table (DT472).
  • This mapping has been designed especially for load import since the transferred records are stamped in the source table (in the SAP status field).
    • In the mapping, the SAP status (sap_state) is defined for the target (see template).
  • This way you can make sure that the load can no longer be changed after export (except for deletion).

    • Load Export

    Information
    • This template serves to export hours or costs from PLANTA.
    • It is an example of how such an import is done.

    What does this interface do?

    • This interface exports hours/costs to a CSV file.
    • There is a mapping that consists of two steps.
    • In the first step, the data is transferred from the source table (DT472) to the load pool table (DT563).
    • This mapping has been designed especially for load export since the transferred records are stamped in the source table (in the SAP status field and NEW additionally in the Exported on, Exported by fields).
    • This way you can make sure that the load can no longer be changed after export (except for deletion). If data has already been transferred, it is impossible to transfer it again.
    • The Position (Item) field must necessarily be available when loads are exported so that the source record can be stamped.
    • In the second step, the data is written in a CSV file.

    I want to output fewer fields in the file, while they remain available in the pool table.

    • The mapping can be adjusted arbitrarily. To get an idea, take a look at the item branch on the right hand side, which only consists of two mapping objects, SOURCE and POOL.
    • If you leave out the target, no columns are passed on to the file.

    In the external system, I always book to the same cost center. How can I have this displayed in the interface?

    • For this purpose, add a new mapping element between POOL and TARGET in the Cost center branch.
    • The mapping element is of the ENRICHER type and receives ConstantValue as an object.
    • Via the Edit parameters button you can enter the required cost center in the Value field.

    Employee Import

    Information
    • The employee import serves to fill or update all employee tables in the PLANTA system:
      • DT516 Person
      • DT511 User
      • DT526 Person Resource
      • DT467 Resource
      • DT518 Role
      • DT525 Stakeholder
    • The idea is that employees are loaded to the employee data pool table DT566 Employee pool from a CSV file.
    • Here, the records can be adjusted afterwards.
    • In a second step, the data is transferred from the pool to the above mentioned table.
    • In order for the transfer to work, you have to fill at least the Code (code) field which equates to the user code.
    • Upon transfer from the pool to the PLANTA data table, it is first checked on the basis of the code whether the person with the corresponding code already exists in the system. This is done in DT516.
      • If for a particular code no corresponding person can be found in DT516, a new person with a new person ID is created and the corresponding code from the pool is assigned. Subsequently, the code and other data to be imported is adopted in DT516 and other data tables.
        • DT525: A stakeholder is only created if the Create stakeholder (create_stakeholder) checkbox is activated.
        • DT518: By default, the user receives the roles that are stored in the global settings default_roles.
      • If persons already exist for searched codes in DT516, only the data that exists in PLANTA for these persons is updated with the data to be imported.

    Note

    • If the employee import is adjusted individually, you have to make sure that the Parent resource (parent_res_id) is not the last field which is changed.
      • Non-compliance with this rule leads to import errors. Reason: The parent resource has a value range which saves. If no further field is adjusted afterwards, there is nothing to be saved by SST and a message is displayed indicating that the record cannot save.

    New from DB 39.5.7

    Project Import and Main Project Export

    Information
    • The Project import interface imports the data from a CSV module in the pool (data table 567 Project pool) and from there to PLANTA project data table DT461. With the project import interface, it is possible to import structured projects.
    • The main project export interface now exports the data of the main projects. Requirement: the logged-on user has access rights to the main project to be exported (controlled via the cost center structure code).

    Details

    • The project pool data table contains all (real) data items from DT461, and the respective pool module contains all data fields from the pool table.
    • The project import interface accesses the functional ID of the projects but converts it to the technical ID subsequently.
    • Both interfaces use the new MtsProjectModule subclass.

    Liability Import

    From DB 39.5.11

    Information
    • This template serves to import liability data to DT281 Project/year/CTGr and DT282 Project/year/CTGr.

    Details

    Up to DB 39.5.0

    Information
    • This template serves to import liability data to DT461 Project.
    • It consists of a simple mapping without any specialties.

    Note

    • Please note that this template is adapted for versions up to DB 39.5.0, i.e. to the versions in which budget and cost planning work with 5 cost type groups.

    From DB 39.5.11

    Import of German Holidays

    Information
    • This template is used to import the official holidays for German federal states from a web service to the PLANTA calendar.
    Details

    Notes

    • Holidays are imported for each federal state since they differ from state to state.
    • A specialty is the import of holidays for the federal state of bavaria. Since in this federal state one holiday only applies to the city of Augsburg, NEW a query whether this holiday is to be included when importing to the calendar has been implemented in the import.

    New from DB 39.5.7

    Import of German Holidays

    Information
    • This template is used to import the official holidays for German federal states from a web service to the PLANTA calendar.
    Details

    Notes

    • Holidays are imported for each federal state since they differ from state to state.
    • A specialty is the import of holidays for the federal state of bavaria. Since in this federal state one holiday only applies to the city of Augsburg, the name of the respective day must be changed to non-working day after import.

    See also: Here you can find an overview of all PLANTA link contents

             PLANTA project







     
    • Suche in Topic-Namen

    • Suche in Topic-Inhalten
    This site is powered by the TWiki collaboration platform Powered by Perl