Ansicht
Dokumentation

_ISUCSFO_000004 - Define Front Office Processes

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

In this activity, you define front office processes.

You can execute front office processes from the IS-U Front Office or from CRM using the transaction starter. When you call a front office process, the action box automatically supplies parameters (such as the current business partner).

A front office process is made up of two components:

• Process container

• One or more process steps

The process container contains all data which is used or processed in the front office process. You must first define all the container elements required for your process. To do this, position the cursor on the Process containerline and choose Edit -> Create Container Element.

In the following dialog, you define whether the container element has a reference to a data dictionary field or whether it is a business object.

In the parameter attributes, you determine whether the container element is an import or an export parameter:

• Import parameter

This means that the value is supplied from outside (usually from the Front Office Workbench).

• Export parameter

This means that the value can be sent back (usually to the Front Office Workbench) after the process is complete.

The Mandatory indicator signifies that a data import must be carried out so that the process can be carried out.

The editing sequence determines where the field appears within the parameter dialog in the Front Office Workbench.

The process steps represent the actual processing that takes place within the process. To create a new process step, position the cursor on Process steps and choose Edit -> Create.

You can specify what the system calls when executing a step:

• Method of a business object

• Workflow

• Front office subprocess (processes can be grouped)

• CATT test procedure

• Editor step (see IMG activity Define Front Office Steps)

Each call has an interface (an import and export parameter) that is either supplied by the process container or which is sent back to it. You must define a dataflow for each step. To do this, position the cursor on the step and choose Edit -> Dataflow.

The dataflow dialog is made up of two components. In the top half you specify the export dataflow from the process container to the the call interface (step container). On the left, you can see all import parameters that are defined in the step interface. On the right, use the F4 input help to view all the elements of the process container. If the type of a process container element corresponds to the target object in the step container, the element is green. Complete type matches are dark green, type relationships are light green.

The same applies to the import dataflow from the step container to the process container in the bottom half of the dialog. On the right (data source) the parameters in the step container are offered as possible entries.

The data flow contains a predefined element <*MAINOBJ*> with a special meaning. If an object method is being called, <*MAINOBJ*> always contains the object reference relating to the method. If you want to maintain a business partner's step, for example, you can choose the method Edit for object type ISUPARTNER. The <*MAINOBJ*> element has type ISUPARTNER and must have a corresponding value. You can see this example in the BPCHAN01 process of delivery customizing. Export parameters are the same. If, for example a Create method creates an object first, the new object will be found in the import dataflow and in <*MAINOBJ*> (see process BPCHAN05, for example). <*MAINOBJ*> corresponds to the element _WI_Object_ID in a workflow task definition.

You cannot change the entries supplied. You may use the following namespaces: X*, Y*, Z* (customer namespaces).

Check the configuration provided by SAP in the standard system. Copy the standard configuration or add new front office processes.

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4746 Date: 20240523 Time: 171506     sap01-206 ( 89 ms )