SAP ABAP IMG Activity BW_CONTENTDS_EDIT (Edit DataSources and Application Component Hierarchy)
Hierarchy
☛ PI_BASIS (Software Component) Basis Plug-In
   ⤷ BC-BW (Application Component) BW Service API
     ⤷ RSAI (Package) Release-Dependent Objects for OLTP IMG
IMG Activity
ID BW_CONTENTDS_EDIT Edit DataSources and Application Component Hierarchy  
Transaction Code S_AX6_42000025   IMG Activity: BW_CONTENTDS_EDIT 
Created on 19990930    
Customizing Attributes BW_CONTENTDS_EDIT   Edit Business Content DataSources 
Customizing Activity BW_CONTENTDS_EDIT   Edit DataSources (2.0A) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BW_CONTENTDS_EDIT    

To adjust existing DataSources to your requirements, you edit them in this step and transport them from a test system into a productive system.

You can also use this procedure to post-process the application component hierarchy.

Example

Requirements

Standard settings

Recommendation

Activities

DataSource

  • Transporting DataSources

    Select the DataSources that you want to transport from the test system into the productive system, and choose Transport. Specify a development class and a transport request, so that the DataSources can be transported.

  • Maintaining DataSources

    To edit a DataSource, select it, and choose Maintain DataSource. The following editing options are available:

    • Selection
      • When scheduling a data request in the BW Scheduler, you can enter selection conditions for the data transfer. You can, for example, determine that data requests are applied only to data from the last month.
      If you set the Selection indicator for a field in the extract structure, the data for this field is transferred according to the selection conditions determined in the scheduler.
    • Hide Field
      • To exclude a field in the extract structure from the data transfer, you must set this indicator. The field is used in the BW to determine the transfer rules, and can no longer be used to generate the transfer structure.
    • Cancelation Field
      • Reverse postings are possible for customer-defined key figures. Cancelations are therefore only active with certain transaction DataSources. These are DataSources that have a field designated as a cancelation field, for example, the Update Mode field in the DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reversal records in the BW.
      If you want to carry out a cancelation posting for a customer-defined field (key figure), set the Cancel indicator. The value of the key figure is transferred inverted (multiplied by -1)into the BW system.
    • Field Known Only in Exit
      • You can improve the quality of data by adding fields in append structures to the extract structure of a DataSource.
      For fields in an append structure, the indicator Field Known Only in Exit is set, meaning that, by default, these fields are not passed to the field list and the selection table in the extractor.
      Remove the Field Known Only in Exit indicator if you want the Service API to pass the field in the append structure to the extractor, along with the fields from the delivered extract structures in the field list and in the selection table.
  • Enhancing Extract Structures

    If you want to transfer additional information for an existing DataSource from a source system into the BW, you have to enhance the extract structure of the DataSource with additional fields.

    To do this, you create an append structure for the extract struture.

    1. Use the Enhance Extract Structure pushbutton to reach the field maintenance for the append structure. The name of the append structure is generated from the extract structure name in the customer namespace.
    2. Enter the fields you want to append and the data elements based on them into the field list. All functions available for field maintenance for tables and structures are available here.
    3. Save and activate the append.

      For more information on the append structure, see the ABAP Dictionary documentation for maintaining tables.

  • Function Enhancements

    To fill the fields of the append structure with data, create a customer-specific function module. Information on enhancing the SAP standard with customer-specific function modules can be found in the R/3 library under Basis -> ABAP Workbench -> Enhancements to the SAP Standard -> R/3 Enhancement Concept or under Enhancing DataSources.

  • Testing Extractions

    If you want to test the extraction in the source system independent of a BW system, choose DataSource -> Test Extraction.

Application Component Hierarchy

  • To create a node on the same level or under it, place the cursor on this node and choose Object -> Create Node. You can also create subordinate nodes by choosing >LS>Object -> Create Children.
  • To rename a node, to expand or compress it, place the cursor on the node and click the corresponding pushbutton.
  • To reassign a node or a subtree, select the node to be reassigned ( by positioning the cursor over it and clicking the Select Subtree pushbutton), position the cursor over the node to which the selected node is to be assigned, and click on the Reassign pushbutton.
  • If you select a node with the cursor and choose Set Section, the system displays this node with its subnodes. You can use the respective links in the line above the subtree to jump to subordinate nodes for this subtree.
  • When you select a node with the cursor and choose Position, the node in the first line in the view is displayed.
  • All DataSources for which no valid (assigned) application component could be found appear under the node NODESNOTCOLLECTED. The node and its sub-nodes are only constructed during the transaction runtime, and updated when saving in the display.

    NODESNOTCONNECTED is not stored persistently in the database. For this reason, it is not transferred into other systems when the application component hierarchy is transferred.

    Note that hierarchy nodes created under the NODESNOTCONNECTED node are lost when you save. After saving, only those nodes under NODESNOT- CONNECTED are displayed that were moved with DataSources under these nodes.

    Example

    A DataSource lies under an application component X. You transfer a new application component hierarchy from Business Content, which does not contain the application component X. The system then automatically assigns this DataSource under the component NODESNOTCONNECTED in this application component.

  • Special DataSources can be delivered with Business Content that are not used to extract data but to reconcile data with one of more Content DataSources. With these reconciliation DataSources you can check that the data loaded from other DataSources is correct.

    The RECONCILIATION node of the application component indicates that reconciliation DataSources of this type are assigned to the application component. If DataSources exist for an application component that can be flagged as DataSources for reconciliation, this is displayed in the corresponding RECONCILIATION lower-level node. If no DataSources exist for an application component that can be used for reconciliation, this node is not displayed.

Note that changes made to the application component hierarchy are only valid until the next transfer from Business Content takes place.

Further notes

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
OSOA L - Logical transport object RSA6 Edit DataSource (2.0A) 
History
Last changed by/on SAP  20020318 
SAP Release Created in