null

Skip to end of banner
Go to start of banner

BPF Process Modeling

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Please note that regarding the formulas used in different places in the definition of the processes, the following restriction applies:

Numeric greater than / less than comparisons and on numeric values from ProRequest form cannot be evaluated correctly.

Technical explanation:
Since internally the field properties of ProRequestForm data are not known and thus a string comparison takes place, e.g. the value 499.00 is smaller than 50.00.

A special, graphically supported, highly dynamic and functional modeling interface is available for the modeling of processes. The modeling environment can be started directly from the SAP IMG node or with transaction /PCH/BPF_DESIGNER.

The generated data is customizing data. Accordingly, data can only be changed if a change to customizing is allowed in the current client. Transport recording also does not take place at all, only manually or fully automatically.

When a process or process version is activated, an SAP Business Workflow template is created automatically. For a workflow template to be created, either changes to repository objects must be allowed in the current client or a corresponding RFC connection must be set up to another client with a changeable repository (see also Transports).

When transporting, make sure that both the customizing request and any workbench transport request are transported together.

If processes are to be recorded in different customizing requests, you must ensure that separate Workbench requests are also used when activating or creating/updating SAP Workflow templates.

Processes must only be changed in the corresponding source system/client, as otherwise (even with separate number ranges) inconsistent data will occur after an import of customizing transports.

As of BPF V4.0, this is ensured by assigning the process to the source system/client, so that processes can only be changed and activated in the source client.

Processes should only be activated in the corresponding source client.

The generated workflow template is a client-independent object, but the required workbench transport has a client assignment, therefore it can usually only be changed in this client.

  • No labels