Ansicht
Dokumentation

/SMB/FO_SIMUL_COMPARE_CREATION - Flex Org: Simulate + Compare two Algorithm for all Creation Use Cases

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Simulation and Compare Tool of different Algorithm for the Creation use Cases in Organizational Structure Application (Flex-Org App)

All Creation Use-Cases are simulated and the relevant Subtasks for the copying process with the corresponding Files are determined.

The result (the to-be-copied Subtasks with the Files) of the following two Algorithm are compared:

* Algorithm 1 (A1): Current Algorithm driven with to-be-maintained Metadata (Relevance Criteria on Task Level).

* Algorithm 2 (A2): New Algorithm according to first stage of Redesign Project in the first approach without to-be-maintained Relevance Criteria. This Algorithm determines the maximum set of relevant Tasks (Subtasks and Files), which are technically reasonable by comparing all Org-Type Key-fields of a given File with pre-defined relevant Org-Types of the corresponding Use-Case. So it follows the principle copy as much as possible, but only in those cases, where it makes sense from a technical point of view.

Prerequisite:

Imported Solution XML including best Flex-Org Metadata and Installation Data.

Goal:

Now: Helper tool to identify tasks, where the Relevance Criteria of the current Algorithm should be checked.

Optionally later: If Algorithm 2 (with or without additional Relevance Criteria) is considered to be applied to simplify the work for the Build Colleagues, then the Result of this report may be a help for the decision.

Input:

Solution ID of the to-be-analyzed Solution.

Result (In DB-Tables and as UI-Output of Report):

Header information for every Use-Case / Run in Header Table /SMB/FO_SIM_H and UI-Output of Report:

Fields:

RUN_NR: Sequential number as Key. --> shown as "Nr" in the UI-Output of Report.

SOL_ID: Solution ID

USECASE_CAT: Usecase Category --> Shown in the Header Lines of the Usecases in UI-Output

PARENT_1_TYPE and TARGET_2_TYPE: The Key-Fields of Table /SMB/FO_EXT_META are used as identifier of the Use-Case.

CMP_A1_A2_RESULT: Result of Comparison between Algorithm 1 (A1) and Algorithm 2 (A2). X means that the results are equal. --> shown as green lines in the UI-Output of the Report.

NR_EQUAL: Number of equal Subtasks with the Files. --> shown as "Equals" in UI-Output.

NR_ONLY_A1: Number of Subtasks with the Files, which appear only in Algorithm 1 (A1). --> Shown as "Only A1" in UI-Output.

NR_ONLY_A2: Number of Subtasks with the Files, which appear only in Algorithm 2 (A2). --> Shown as "Only A2" in UI-Output.

Every single Sub Task per Algorithm per Use Case as Item in Item Table /SMB/FO_SIM_I:

Fields:

RUN_NR: Key from the Header Table to identify one Use Case

ALGO: Algorithm = 1 or 2.

BBID, SEQNUM, TASK_TYPE, TASK_ID, SUB_TASK_ID, FILENAME: Identifier of a Subtask with File.

ONLY_THIS_ALGO: Flag to mark all Subtasks, which appear only in one Algorithm: in Algorithm 1 OR in Algorithm 2 depending on the value of field ALGO.

Hints to get desired selections:

If you want to get all deviations of a given Use-Case, select with RUN_NR and with ONLY_THIS_ALGO = X.

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3412 Date: 20240425 Time: 231613     sap01-206 ( 53 ms )