Skip to Content
author's profile photo Former Member
Former Member

Modification / Enhancing Datastream Upload in BCS

Scenario:

Transactional data is loaded via Extractor 0FI_GL_7 into BW Staging Area (ZBCS_O20) in delta mode,

After Delta Load from source system (AFS) data will be loaded into 2nd DSO (ZBCS_O21) in Consolidation Area.

Data in 2nd DSO gets deleted before full load from entry layer is being started.

From deletion Data in 2nd DSO until loading and activating data in 2nd DSO we can get into trouble.

If anybody is starting a BCS datastream load at this time 0 values are delivered to BCS.

In this case existing values in actual period are calculated into zero values u2013 and this should not happen.

Needed Solution:

We need a solution to prevent data loads into BCS-Cube when source DSO (ZBCS_O21) represents no active Data.

We tried to find a place for enhancing implementation of class CL_UC_* but we do not find right place to do an enhancement when debugging BCS upload functionality.

Do anybody of you have an idea on in class or method we can or should do such an enhancement?

Or do you have other ideas how we can prevent loading BCS datastream loads until our Sourceobject is empty?

Thanks a lot.

Regards,

Timo

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Aug 16, 2011 at 01:47 PM

    It might be useful to consider having a custom task or tasks in the BCS monitor to execute these DSO loads. Such tasks would be in the task hierarchy prior to the data collection for load from datastream.

    Add a comment
    10|10000 characters needed characters exceeded

    • You will see above that I initially suggested a custom task.

      SAP Help for BCS explains this as:

      Custom Task

      Use

      You can use this function to execute tasks that contain functionality, which you as an SAP customer define yourself.

      When a custom task is executed, the system calls the active implementation of the delivered Business Add-In (BAdI) UC_TASK_CUSTOM. This BAdI is freely programmable.

      As in other tasks, when a custom task is executed, the system first checks the authorization and the task status.

      Then the system updates the task status and creates a task log (with messages only).

      Integration

      Custom tasks can reside anywhere in the task sequence. You can specify that other tasks must precede the custom task (u201Cpreceding tasksu201D). You might require preceding tasks if the custom task employs the results of other tasks within the same task group.

      Features

      The BAdI UC_TASK_CUSTOM provides you with the interface methods EXECUTE and EXECUTE_FINAL.

      You implement the function of the custom task in the EXECUTE method. When the EXECUTE method is called, the system passes the following parameters (among others):

      · Consolidation area

      · Technical name of the custom task

      · Execution parameters, such as the consolidation units or groups to be processed, the group currency, version characteristics, and time characteristics

      For more information, see the documentation in the system.

      The Customizing settings for custom tasks let you determine whether it should be executed for consolidation units or consolidation groups:

      · If you choose processing per consolidation unit, the system executes the EXECUTE method collectively for all consolidation units to be processed, and then updates the status of each consolidation unit.

      · If you choose processing per consolidation group, the system executes the EXECUTE method individually for each consolidation group to be processed, and then updates the status of each consolidation group.

      The system executes the EXECUTE_FINAL method once only at the end of processing. You can use this method for cleanup activities u2013 for example, to free up working memory.

      The Customizing settings for custom tasks also let you determine whether to save the log when you run the task in update mode.

      Activities

      A. Customizing

      To set up a custom task:

      ...

      1. Create a new custom task. To do this, in the process view of the Consolidation Workbench choose Consolidation Functions ® Other Tasks ® Custom Tasks.

      2. Implement the BAdI UC_TASK_CUSTOM.

      To see the definition of the BAdI UC_TASK_CUSTOM, on the SAP Easy Access screen choose Tools ® Utilities ® Business Add-Ins ® Definition.

      3. Activate the implementation of the BAdI UC_TASK_CUSTOM.

      B. Execution of the Custom Task

      Execute the task in the Consolidation Monitor.

      The system calls the active implementation of the BAdI UC_TASK_CUSTOM. When processing is finished, the system displays the messages of the methods EXECUTE and EXECUTE_FINAL.

      Example

      Extracting Transaction Data

      Data collection in your business process is configured so that the data is first extracted from an SAP source system and written to SAP NetWeaver Business Intelligence (BI), where it is then processed by the consolidation component (or by another BI-based application) by means of reading the respective InfoProvider. You want this data collection to be triggered and monitored in the consolidation monitor.

      To do this, you create a custom task (processing per consolidation unit) and insert it into the Consolidation Monitor.

      You implement the EXECUTE method (see also the source text of the example implementation of this BAdI), and activate the implementation.

      Updating Custom Database Tables

      Your business process periodically writes and updates certain data in separate database tables specifically defined for this purpose. This data is then used in the consolidation process. For example, you want to load consolidation unit-specific exchange rates into a database table using a data file interface, which is then used by the BAdI to determine exchange rates during currency translation. You want this update to be triggered and monitored in the Consolidation Monitor.

      To do this, you create a custom task (processing per consolidation unit) and insert it into the Consolidation Monitor.

      You implement the EXECUTE method. This method reads the data, performs the update, and returns any error messages (for example, if the expected data cannot be found).

  • Posted on Aug 16, 2011 at 04:05 PM

    I see two options :

    1) As Dan mentions, you build a custom task in BCS to load the DSOs from the consolidation monitor. For that you need to create an implementation for the BADI "UC_TASK_CUSTOM" in t-code SE19. Insert your code here.

    2) On the opposite, you can sequence your upload tasks, i-e DSO upload and BCS data collection using a BW a process chain. Indeed you can schedule your BCS tasks using the UCBATCH01 program. With this process, you are sure that the tasks are executed in the good sequence

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.