27interviews.blogspot

This blog doesn't contain any copied information or copyright content from other sites. Every topic i presented in this blog is authored myself. Every time i tried to help the sapients to understand the concept in an easier way. Thats it. Have a Grt Day!

Translate

RSA1 GROUPING MODE OF BW OBJECTS IN TRANSPORTS:


RSA1 GROUPING MODE OF BW OBJECTS IN TRANSPORTS:


Many of them don’t know what exactly the RSA1 Grouping means.
Without thorough knowledge we can’t do anything perfectly.
I had elaborated the topic to make you understand the concept in depth.

Concept is below:
We often develop objects in SAP. Like InfoObjetcs, InfoCubes, Queries, WebTemplates, TransformationRules, InfoSources etc.

But where to develop the objects?
In Development Box or in Production Box?

We develop objects in Development Box because; it’s highly risky to develop objects in Production Box as:
·         We can lose the data,
·         And the data flow changes also.
After developing the objects in Development Box, then we transfer to Production Box
I.e. in SAP Terminology it’s simply Transporting.

The quality of data which is transported will affect the activation process and gives errors.
The dependencies of the objects are mapped by Grouping Mode by which the objects are collected.

SO BELOW ARE THE 5 GROUPING METHODS:
Here the mandatory point to be noted is that, data will be collected from DEV BOX and collected to PRO BOX.

·         Only necessary objects
·         In data flow before
·         In data flow after
·         In data flow before and after
·         Save for system copy

ONLY NECESSARY OBJECTS (DEFAULT OPTION):
If we select only necessary objects, only the necessary or related objects are selected and transported.

IN DATA FLOW BEFORE:
If you select this option, InfoCube, TransformationRules & InfoSources are collected and transported.

IN DATA FLOW AFTER:
If you select this option, Queries and WebTemplates are collected and transported.

IN DATA FLOW BEFORE AND AFTER:
If you select this option, InfoCube, TransformationRules & InfoSources, Queries and WebTemplates are collected and transported.

SAVE FOR SYSTEM COPY:
If you choose this option, it’s mainly used for copying or renaming the SourceSystem, i.e. recreation of objects for SAP DEV & SAP PRO systems are avoided. And all the objects are SourceSystem dependent DataSources are collected in a change/TransportRequest.

The main logic to understand is that, by selection save for system copy helps saving the mapping between the objects & SourceSystem is not deleted after the request is applied or imported.

GROUPING MODE CONCEPT IN DEPTH:
(All the figures for illustration purpose only)

Figure 1
 

Here in the above diagram Figure 1, you can see, I had mapped the newly developed objects to the grouping mode, shown graphically. In this we can see newly developed objects such as InfoObjetcs, InfoCubes, Queries, WebTemplates, TransformationRules, and InfoSources are mapped to the corresponding Grouping Modes.

MAPPING LOOKS LIKE THIS IN ABOVE ILLUSTRATION:
In Data Flow Before mapped to InfoCubes, TransformationRules & InfoSources.
In Data Flow After mapped to Queries & WebTemplates.
In Data Flow Before and Afterwards mapped to InfoCubes, TransformationRules, InfoSources, Queries and WebTemplates.

So see all the corresponding mappings.

Figure 2


In Figure2 above we can see the screen shots in depth, which I had mapped the Grouping mode.

Figure 3:


Actually this is the DataFlow of SAP BW and SAP BI. Here if you see, you can easily understand the whole concept about what we do in the In Data Flow Before & In Data Flow Afterwards.


COLLECTION MODE:
In the collection mode there are 2 options
One is default which is Collect Automatic ally
And second is Start Manual Connection

After doing the above Grouping and Collection we click on Transportto transport the objects.


Thanks for reading!

Correct me if there are any mistakes.

Template versus Reference InfoObjects - SAP BIW


Dear Readers,
This question is most important. Many of them don't know the exact difference between Template and Reference InfoObject. So I had tried maximum to explain in a very easier way to understand the concept.

So these are the differences between Template InfoObject and Reference InfoObject:

Differentiation point
Template InfoObjects
Reference InfoObjects
Use
We can use these both Template and Reference in Development projects as per requirement. And Creating new InfoObjects using Template and reference slims the time, in Development Projects.
Main Difference
When using Template, we can consider as Navigational Attributes.
When using Reference, we have only Display Attributes. If Navigation attributes used, they will reflect / seen as Display Attributes only
Restrictions
No restrictions
Restrictions
What will be copied
Master data attributes, compounding attributes and technical properties are copied to new InfoObjects.
Master data attributes, compounding attributes and technical properties are copied to new InfoObjects and all the reference InfoObjects data also can be used
Editing & Modifications
Yes by changing attributes, data type, length of the newly created InfoObjects
No, we cannot change the length, data type, master data attributes, compounding attributes
Maintain Master Data
maintain master data is possible
But maintain master data is not possible
Master Data Table
It will have its own master data table if we use Template InfoObject
It will have the same master data table as Reference InfoObject
Transformations
Yes possible
Not possible, error message occurs
Loading data
Yes
Not possible because reference not allow transformations
Used as Data Target (Insert Characteristic As InfoProvider)
Yes
No
Drill down Capability
Yes
No

Interview Point of View:

We can use these both Template and Reference in Development projects as per requirement. And creating new InfoObjects using Template and reference slims the time, in Development Projects.

Template InfoObjects:
When using Template, we can consider as Navigational Attributes. Master data attributes, compounding attributes and technical properties are copied to new InfoObjects. Editing and modifications are possible by changing attributes, data type, and length of the newly created InfoObjects using Template. It will have its own master data table if we use Template InfoObject. And maintain master data, Transformations, Loading data is possible, and can be used as Data Target (Insert Characteristic As InfoProvider) and Drill down capabilities for InfoCube are supported using Template InfoObject.

Reference InfoObjects:
When using Reference, we have only Display Attributes. If Navigation attributes used, they will reflect / seen as Display Attributes only. Master data attributes, compounding attributes and technical properties are copied to new InfoObjects and all the reference InfoObjects data also can be used, but we can’t change the length, data type, master data attributes, compounding attributes and it will have the same master data table as Reference InfoObject & maintain master data is not possible. Transformations not possible, Loading data not possible, Cannot be used as Data Target (Insert Characteristic As InfoProvider) (error message occurs: Not possible because reference not allow transformations) and Drill down capabilities for InfoCube are not supported using Reference InfoObject.

A InfoObject (Main InfoObject) and
B InfoObject is a situation (reference or Template) using A InfoObject.

Simplest way to understand this concept of Template Reference InfoObjects:
This below is my assumption to make u better understand the concept!

So when we take into consideration of Reference and Template, just think these are twin brothers at home with same faces.
So,
Using Template (brother), he will be readily available for modifications.
Using Reference (brother), he will not ready available for modifications.
But both will work with same faces (faces here faces means Master data attributes, compounding attributes and technical properties)

At last
Template will accept changes/modifications.
Reference will not accept changes/modifications.


Thank you






There was an error in this gadget