Architecture of SEM-BCS 4.0

[Former Member]

I'm trying do understand how SEM-BCS 4.0 works and where the different processing-steps (mapping of R/3-fields to BW-InfoObjects, Validation of reported data via a rule set etc.) are done.

Is the reported data via a basic R/3-system transfered via the normal transfer-rules, psa and so on?

When is it useful to integrate a staging-cube for original data before the bcs-cube?

Do manuel entered data go directly into the bcs-cube or is there a step between?

The bcs-cube is a transactional cube. How can the problem of switching between manual entry and upload be solved if there is a demand for simultaneous upload and manual data entry?

I couldn't find any good information in the web about this! I would be grateful if somebody could help me with the basics of bcs.

Thanks in advance!

Greetings

Patrick

[Former Member]

Hi,

I am also trying to use the same function. I need to implement a function which I cannot do thru the SAP delivered functions. Has anyobe build functions in BPS and have been able to link it to the Monitor in BCS. Replies would be much appreciated

[Former Member]

Hi all,

We are trying to use this new Custom Task functionality in SEM-BCS 4.0. Does anyone has experience with this? We can't find any how to information about it. We want to include this custom task to directly link in the consolidation monitor to BPS and back, but we are not getting any further than defining this (empty) custom task). In the past you could implement SAP Note 610636 to solve this, but that doesn't apply for SEM-BCS 4.0 anymore. Anyone?

[GFV]

Hi Patrick,

about your questions ...

1 - Data are stored in a transactiona InfoCUbe and a serires of (some optional) ODSs (transactional too). Reports are executed via a Virtual Cube , so no PSA, no is involved at all, unless you use a basic InfoCube as source of a DataStream flow.

2 - The integration of a Basic IC is usefull if you need to extract (and transform) R/3 data before collecting such transformed info in BCS (via DataStream)

3 - Manual entries do generate some documents in ODS (if activated) and totals are stored in IC

4 - According to me you can try to swithc, but should be better using it as transactional ONLY (to be sure about controls related to Customizing) and integrate data via DataStream.

If you are searching for some docs see http://service.sap.com/sem ... there are some doc's both on BCS R/3 based and BW based.

Hope it helps

GFV

[Former Member]

Hi Gianfranco,

Thank you very much for your fast response!

I understood most of what you said. But what I don't get is this DataStream.

Correct me if i'm wrong, but i suggest that both, the uploaded data from a R/3-system or a flatfile and the manual entered data are treated the same way!? And this is why i don't have to switch the transactional bcs-cube to upload!

Am i right?

But how exactly does this DataStream work?

I read many of the documents at service.sap.com, but i couldn't find any understandable information about the technical construction of BCS. Do you have a specific document in mind?

Greets

Patrick

[Former Member]

Hi Patrick,

I implemented a huge SEM-BCS 3.2 project so most of my experience is based on this release.

A BCS cube is always a transactional cube. BCS delivers different data input options, basically a manual input or a flat file upload. At least in 3.2 there was no standard extraction from R/3 and it wasn't planned.

Anyway you can create level 0 data on a multitude of other ways, most noteworthy by upload or by BPS. We used lots of BPS functions to manipulate basic BCS data so it's no problem if you do it right.

SAP's recommendation is clear: Don't upload right into a BCS cube (so you don't need to switch). If you need an additional upload I would try BPS functions. You can handle all kinds of problems and requirements with BPS exit functions (we wrote about 40-50 during the project) so just try to do it.

Best regards

Dirk

[Former Member]

Hi Dirk,

I understand what you wrote and i had the use of BPS in mind, too. This will be very helpful when we have to implement a bcs, but your answer doesn't really help me to understand the datastream and the processes in BCS.

And as far as i know there are a lot of functional changes between the versions 3.2 and 4.0.

Greets

Patrick

[GFV]

Hi Patrick,

in my experience Upload from R/3 is possible in two ways (depending on BCS release). In fact you can load into a basic IC and then:

1) extract into a Flat file with OpenHub and reload into BCS InfoCube with Flexible Upload (up to BCS 3.5)

2) create a Datastream (with BCS 4.0) in order to load directly BCS CUbe (as if ther was a DataMart Interface)

Flat Files are treated with Flexible Upload, while manual entry is based on Layouts.

I wouldn't consider switching from trans to batch (and viceversa) as a standard solution, because all the ogics defined in UCWB won't be considered at all!

About New Features see the folllowing page in http://service.sap.com/sem mySAP ERP/mySAP ERP in Detail/Analytics in mySAP ERP/Analytics in mySAP ERP in detail/Strategic Enterprise Management/New Features by Release/4.0 -> <b>SEM-BCS Functions Overview</b>

and about DataStream (that according to me is one of most interesting functionalities)

http://service.sap.com/sem mySAP ERP/mySAP ERP in Detail/Analytics in mySAP ERP/Analytics in mySAP ERP in detail/Strategic Enterprise Management/Strategic Enterprise Management/Media Library/Help to use SEM/How to... -> <b>Automatic Data Transfer</b> (pre-released 4.0 DR docu) [page 22]

Hope it helps

GFV

[Former Member]

Hi Dirk,

I saw some files about the intergration between BPS and BPS. If you push the data from the BPS to BCS , will the BCS logic been applied? Or, you have to replicate those logics in BPS? By the way, does anyone apply note 610636 ( SEM-BCS: modification - customer defined task )?

Best Regards,

Jeff