Configuration of automatic Business Unit determination

Transaction / EDGE / FC_SPRO → Configuration folder "Automatic determination of interpreter".

This configuration is useful in cases where, depending on certain initial variables, a Business Unit or another must be started. If you have several Business Units for a similar scenario, for example, several for receipt of invoices (one for invoices, another for credit notes and another for debit notes); you can use this determination to select dinamically through which Business Unit the process should go.

Another example could be for the invoice issue, where only the Business Unit that is going to execute the issuance of SD invoices is required to be instantiated for a group of document classes or for any other group depending on a field in a table that is in the context at the beginning of the process. A concrete example could be: the invoice Business Unit corresponds only to the document classes XX, YY, ZZ, the credit notes to the document types AA, BB, CC, and the debit notes to the document types DD , EE, FF.

It can also be indicated that only a certain Business Unit is started if it comes from a particular transaction.

N automatic determinations of Business Unit can be defined, even several can be defined for the same Business Unit, however, the system will take the first one that meets the condition.

Together with this configuration it is necessary to configure the class for the external start of the processes in the Core Framework general parameters. Likewise, the class / EDGE / CL_FC_START_PROCESS_EXT must be configured there, which contains all the logic that will be described next.

The fields that comprise the configuration of an automatic determination are defined below:

ID.Det.Int
Unique identification of the Business Unit´s determination.
Name of the determination
Business Unit determination name.
BU ID
Business Unit that will be assigned in case this determination results in true.
Sec.Deter.
Sequence for execution of the determination. This field tells the order which the system must execute the determination. The system stops when some returns true or when in the end none returned true.
Dete. type
Indicates logic type that will be used for the determination of the Business Unit. There are four types of logic that can be assigned:
- C → for Class:
  It indicates that the logic of the determination is made through a class that implements the interface / EDGE / IF_FC_DETERMINE_INTERPRE.
- T → for Table/Field structure:
  It indicates that the logic of the determination is made through the configurations that are entered in the options that are inside this folder; which correspond to verify if in the context of the beginning of the process there is an internal table or structure with the name configured and whose field or fields have some value of those that are configured here:
- X → for XML scheme:
  Not in use.
- Y → mixed for Table/Field structure and Class:
  It corresponds to the determination using first the type T and if this one gives a true as result, it proceeds to verify by the type C; if at the end both result in true, the final result of the determination will be true, otherwise it will be false.
ABAP Class
Class that implements the logic of the determination. It is only used if it has been marked as determination type C or Y. You have to implement the interface / EDGE / IF_FC_DETERMINE_INTERPRE.
External document type
It is only used if it has been marked as determination type X. Not in use.
XML interface definition
It is only used if it has been marked as determination type X. Not in use.
Method with the definition of XML
It is only used if it has been marked as determination type X. Not in use.

The only types of determination where additional functional configuration is used for the determination procedure are for the types: T and Y. In these types, references to internal tables or structures and their fields are used to verify if it meets the conditions to assign or instantiate the Business Unit.