Kontakt

Ansicht
Dokumentation

SIMG_SWFMOD_CONTENT - Define own content (components, templates library)

SIMG_SWFMOD_CONTENT - Define own content (components, templates library)

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Due to upgrade, we highly recommend you not to make any direct changes on SAP content objects. For example, if enhancements are necessary for a component (new input, new name and so on), you should better copy its workflow definition first using the workflow builder and publish then the newly created workflow within the modeler.

Some SAP software components deliver business content for the modeler that means library of components or templates stored in a predefined folders hierarchy.

The workflow modeler allows you creating your own content. When you create your own library of components and template, keep the following in mind:

  • Components are activated workflows or released tasks done in the modeler -for workflow only - or in the builder that you decide to publish. They have input and output parameters corresponding to input output element of the container. To provide organisational management in a component you must include in the container one of these two data elements:
  • SWFMOD_ORG_ACT: provide the list of all Roles, Rules, Organisational Units, Jobs, Positions, Work centers, Users in the system.

  • SWFMOD_ORG_MAIL: provide the same list except Roles and Rules

  • Templates and components must be assigned to a folder; access rights being not managed at components or templates level but at a folder level. By consequence, build your folder hierarchy in respect with your role strategy. For example, if you want to organize your roles by business area, you should better create a hierarchy by functional area. For example:

,,CRM (Name: Customer relationship management)

,,,,CRM_SALES (Sales)

,,,,,,CRM_SALES_DISTRIBUTION (Distribution)

,,CRM_SALES_PLANNING

,,,,CRM_SERVICES (Services)

,,Nevertheless, because component or template can only be assigned to one folder, you should for shared ,,components

,,Create a folder "Common" or "Miscellaneous"

,,or

,,Assign them to the Top-level folder CRM

,,For Role Sales, you restrict the access to CRM folder (no *) and CRM_SALES* folder.

,,Forcing the technical name of a subfolder to Parent technical name (as prefix) + _ + free input, the modeler ensure that your admin will be able to give access to a complete branch by giving authorization to the top level folder + * (example: see the branch CRM and sub-folders by setting access right to CRM*).

Your content can be transported using transaction SWFMOD_TRANSPORT.






rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2890 Date: 20240523 Time: 171430     sap01-206 ( 63 ms )