Kontakt

Ansicht
Dokumentation

FTR_TARO_DER_DER_CNT - Determine Field Values for TARO-Derived Content Data

FTR_TARO_DER_DER_CNT - Determine Field Values for TARO-Derived Content Data

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can define derivation rules for field values of the derived content data of trade repository objects.

These derivation rules are called after the active BAdI implementation for filling the derived content data of the trade repository object ( BAdI: Fill Derived Content Based on TARO Content, method FILL_DERIVED_CONTENT) has filled the fields of the derived content data with values.

You can base your derivation rules on the values of the content and administrative data of the trade repository object to fill the derived content data fields that have not been filled by the BAdI implementation or change the values filled by the BAdI implementation.

You can use the fields of the following origins as source fields:

Origin Name DDIC Structure
CONTENT TARO Content TLRS_TARO_CNT_DATA
ADMINISTRATIVE_DATA TARO Adminstrative Data TLRS_TARO_ADM_DATA

The target fields are all fields of the following origin:

Origin Name DDIC Structure
DERIVED_CONTENT TARO Derived Content TLRS_TARO_CNT_DERIVED

Derivation steps are processed in the following way:

  1. If you have defined a condition for performing a derivation step (see below), this is checked first. If the condition is not met, the step is not performed. When the condition is met, the step is performed.
  2. The system checks the source and target fields according to your settings in the derivation step and executes the step.
  3. If the system cannot find suitable target values in this derivation step, the target fields are not changed. Otherwise, the new values are written in the target fields.
TARO Derived Content

TARO Derived Content

TARO Derived Content
  1. Call the Customizing activity. The Derivation of Derived Content for Trade Repository Objects: Change Strategy screen appears.
In this screen, you can enter rules to derive the values for the content fields of the trade repository objects.
The rule can involve various steps. The system follows these steps in order until it is able to determine a value for the target field.
A step can consist of a derivation rule, table lookup, or a move:
  • Step type Derivation Rule

Step types are used as the basis for deriving the field value for the target field.
  • Step type Table Lookup

Table lookups let you read individual records from any table to determine characteristic values. Here the source fields must make up the key of a specific table from which the system can copy certain contents to the target fields of the TARO-derived content data table (TLRS_TARO_CNT_DERIVED).
  • Step type Move

In the case of a move, you specify the value to be written to the target field.
On the Condition tab page, you can define for each derivation step a condition that must be met for the step to be executed.
On the Attributes tab page, you can use the step attributes for each derivation step to control whether:
  • An error message is issued when no target values are found.

  • Processing of strategy is terminated when no values are found.

For derivation type Move, this function is not available.
You can also make settings for derivation rules to allow expiration dates to be maintained for rule entries. If you activate this attribute, you can define a "Valid From" date for your entries for a derivation rule.
Field Attributes
You can determine field attributes by choosing Details for the source and target fields.
You can make settings to allow blank values for a source field. This means that derivation will still be performed, even if the given source field does not contain a value.
You can stipulate the following for a target field:
  • Do not overwrite with new value if field already filled

  • Overwrite with new value even if the new value is initial

  • Overwrite with new value only if new value found

This allows you to ensure that, whatever the value determined by the derivation step, it is copied to the target field irrespective of whether the field already contains a value. After this derivation, you will not be able to overwrite this value manually.
In the case of table lookups, you can choose further options for selecting field attributes for source and target fields. For example, you can choose to consider just one part of each field.
  1. Defining a derivation rule
    1. Choose the Create Step pushbutton. In the dialog box, select Derivation Rule and confirm your entry.
    2. Enter a text for the derivation rule.
    3. On the Definition tab, enter the fields that you want to use in the Source Fields section. In the Target fields section, choose the Content field from the list.
    4. You can enter conditions for applying the derivation rule on the Conditions tab.
    5. The settings on the Attributes tab are not supported.
    6. You now have to assign the target field values to the values of the source fields. To do this, choose the Maintain Rule Values pushbutton.
In the table that follows, you can assign the target field values to combinations of source field values. The first column contains the first source field that you selected, the second column the second source field, and so on. The last column contains the target field.
  1. Define a Table Lookup
    1. Choose the Create Step pushbutton.
    2. In the dialog box that appears, enter the table name.
    3. Enter a text for the derivation rule.
    4. On the Definition tab, assign the corresponding source fields to the key fields of the table. Then assign the table fields to the target fields and define the field attributes (by choosing Details).
    5. You can enter conditions for applying the derivation rule on the Conditions tab.
    6. On the Attributes tab page, you can use the step attributes for each derivation step to control whether an error message is issued when no target values are found.
  2. Define a move.
    1. Choose the Create Step pushbutton. Select Move in the dialog box and confirm your entry.
    2. Enter a text for the move.
    3. On the Definition tab, you have two options:
- You can choose a source field, the value of which is then written to the target field [in this case, all the values of the source field must correspond to short keys for target field].
- You can enter the field value directly in the Constant field.
  1. Select the target field.
  2. On the Condition tab, you can make the assignment dependent on the fulfillment of a condition.
  3. The settings on the Attributes tab are not supported.
  • Changing the order of the steps
    • You can change the order of the steps after they have been defined. To do this, proceed as follows:
    1. Select the step that you want to move.
    2. Position the cursor beneath the target position.
    3. Choose Move.





    SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
    This documentation is copyright by SAP AG.

    Length: 10344 Date: 20240523 Time: 192353     sap01-206 ( 108 ms )