Data Crawler in Condition
Data Crawler in Condition
This document describes in brief how to use the data crawler to define input for conditions. The
example describes how to read TRQ root data for a condition which is called for a Freight Unit, e.g.
the default MTR determination.
The DC profile can be maintained in TA SM34 (no standard TA code so far). Enter the View Cluster
/SCMTMS/V_DCPRF and press “Maintain”.
In the TA you first enter a DC Profile ID and the BO name and node. This is the BO and node which is
the starting point, e.g. /SCMTMS/TOR ROOT if you start from a freight unit. Basically it should match
the entry in the condition type. In the example the Profile is called FU_TO_TRQ_ROOT.
In a next step you define what you want to read from there, in our example we want to go to the
/SCMTMS/TRQ ROOT . To define this step you have to select the DC profile ID and create a so called
path step. In our case this is STEP 10 which goes from /SCMTMS/TOR-ROOT with ASSOCIATION
BO_TRQ_ROOT to the TRQ_ROOT. And that´s already everything we have to do in the DC profile!
Now, how can I use the DC-Profile as input for a condition?
The next step is now to make use of this nicely defined input. To do so you must assign the DC profile
to a data access definition. You define the Data Access definition in IMG:
In the Data Access Definition you now assign the profile and the step (This defines the node that you
can use as input) and the field from the node you want to use:
Don´t forget to assign a data element for the F4 help of the DAD.
Yes, there is no F4 help and no validation, we fully trust in your skills and we wanted to leave some
room for improvement.
From now on it´s easy, you can assign the Data Access Definition to the condition type in IMG:
Finally…use it in a condition
And here is the result in the condition maintenance when using a condition where the DAD is
assigned to the type: