Determine View

Hi all,
I am new to webdynpro, just ned to check a few things. How do i find out the view name of the standard shopping cart view I see in my web browser??
Thank in advance.
Quick Points will be awarded!

Hi Mohammad,
Right click on your screen in the browser and select "View source". You will see HTML generated by WD runtime. To figure out name of component and view you need to find HTML tag for appropriate UI element which has action. For example:
<i><a href="javascript:void(0);" ... id="MPLE.ProfileViewerCV.btnCollapse" ...</i>
In this case name of view is "ProfileViewerCV" and ID of corresponding UI element on WD side is "btnCollapse".
Best regards, Maksim Rashchynski.

Similar Messages

Recording view in results recording

Hi all,
I have used 89 insp type for manual lot and in results recording i want the tab that unit to be inspected . In develpement it is coming .but in prod sever it is appearing and in production also for some insp types it is coming why .
please suggest settings .
regards
prasad

Hi arun,
alredy i did the setting in IMG for that 89 insp type .even though it is not appearing .
now my query is if we did not do that setting also i think tab should be appear.but curser will go to other tab.
please correct if I am wrong .
plz suggest me how to do get the tab.It is very urgent for me .
regards
prasad
Edited by: prasad.k on Apr 2, 2008 4:08 PM
just now i have seen that message is giving by the system:
*view for characterstic overview was changed *
if you see the details of that message that like follow----
View for characteristic overview was changed
Message no. QE044
Diagnosis
The predefined view from the operation or inspection type has been changed by the program. This may be due to the following:
In the user master, a recording view is assigned to the user parameter 'QER'. If there is no default value for this user parameter, the general view (single values and summarized results) is used.
The determined view is marked as obsolete.
Procedure
The user parameter 'QERSMAL' must be initialized to be able to use obsolete recording views. You cannot delete the user parameter from the user master.

BI Content Activation & Installation

Hi Experts,
                 Could you please ellaborate all steps(R/3 Side & BW Side) involved in Business Content Activation(interms of D,M,A Version) and Installation.Thank you.
Vasanth.D

Hi Vasanth,
To specify which objects you want to install from BI Content or transport using the BI transport connection, you collect the relevant objects in the BI Content or Transport Connection (transaction RSOR) functional areas of the Data Warehousing Workbench
Note
Since BI Content is highly integrated, you should familiarize yourself with the procedures for collecting BI Content.
Avoid collecting BI Content objects from application areas that you do not want to use. If you collect BI Content objects that you do not need, you waste time and increase the number of active, but unused, objects in your BI system.
Prerequisites
●      You are familiar with the dependencies between BI object types. This knowledge is essential to be able to create consistent requests.
More information: Object Dependencies and Consistency
●      To copy BI Content to the active version: You have replicated the source systems for which you want to install source system-dependent BI Content. The delivery versions (pseudo D versions) are not available to the source system-dependent objects until after this replication.
More information:
Structure link Replication of DataSources
Special Features of Source System-Dependent Objects
Procedure
1. Specify the target source systems
If you also want to collect source system-dependent objects, choose This graphic is explained in the accompanying text Source System Assignment to specify the source systems for which you want to collect objects. Only those objects that are assigned to the selected source systems are collected. If you want to collect source system-dependent objects but have not selected a source system, the dialog box for assigning source systems is displayed automatically.
Recommendation
We recommend that you only select those source systems that you require; otherwise, you may have to wait longer than required when objects are collected.
Note
This setting is particularly relevant when you activate BI Content because you use it to specify for which source systems you want to activate BI Content.
When you transport objects, you specify the target source systems in the target system for the transport. In this case, the setting is required to specify for which source systems the objects are to be exported.
More information: Defining the Target Source System
2. Group objects to be included
In the This graphic is explained in the accompanying text Grouping selection list in the right screen area, specify which objects are to be included. The groupings combine the objects from a scenario. By default, only those objects are collected that are essential to activate an object. If you also want to collect the objects that are required to activate all other objects that are collected at the same time, you can select the relevant option:
●      Only Necessary Objects (default setting)
●      In Data Flow Before
●      In Data Flow Afterwards
●      In Data Flow Before and Afterwards
Note
If you change the default setting, the new setting becomes the default setting for your user.
Caution
The grouping option selected has a significant impact on system performance while the objects are collected.
We recommend the following alternative for installing BI Content:
○       Collect objects for roles In Data Flow Before and install the collected objects.
○       Collect objects for InfoCubes and InfoProviders In Data Flow Before and install the collected objects. Finally, collect objects In Data Flow Afterwards and reinstall.
More information:
Defining Grouping Mode
Object Dependencies and Consistency
3. Specify the collection mode for objects
In the Collection Mode selection list in the right screen area, specify how you want to collect the objects.
●      Collect Automatically (default setting): The data is collected as soon as the objects are selected.
●      Start Manual Collection: The data is not collected until you choose This graphic is explained in the accompanying text Collect Dependent Objects.
Recommendation
Set the collection mode to Start Manual Collection. This allows you to select all the objects without having to wait.
4. Determine view of objects
In the left navigation window, specify which criteria you want to use to display the objects that you are collecting to install as BI Content or to transport.
If you selected a particular view in the left navigation window, the available objects are selected and arranged in the tree structure in the center screen area as follows:
View of Objects in Left Navigation Window
Display of Objects in Tree Structure in Center Screen Area
This graphic is explained in the accompanying text InfoProviders by InfoAreas
List of InfoCubes and DataStore objects, sorted by InfoArea
This graphic is explained in the accompanying text InfoObjects by Application Component
List of InfoObjects, sorted by InfoObject catalog and by InfoArea
This graphic is explained in the accompanying text InfoSources by Application Component
List of InfoSources for master data and transaction data
This graphic is explained in the accompanying text Roles
List of standard roles and industry roles
This graphic is explained in the accompanying text Object Types
List of the most important objects according to types
This graphic is explained in the accompanying text Objects in BI Patch
List of the BI patches installed, including a list of the new and modified objects delivered with each patch.
This graphic is explained in the accompanying text Transport Request
The Select Request/Task dialog box appears. Choose the request that you want to use.
This graphic is explained in the accompanying text Packages
List of packages containing SAP objects
5. Specify display mode for collection objects
In the Display selection list in the right screen area, specify whether the collected objects are to be displayed as a hierarchy or a list.
Recommendation
We recommend that you display the objects as a list if you want to keep a clear overview of the collected objects. If you want to identify why a specific object was collected or want to work through related objects scenario by scenario, choose the tree display (Hierarchy).
6. Install the objects in Collected Objects
In the center screen area, select the objects that you want to collect, and drag and drop them to the right screen area Collected Objects.
Note
The This graphic is explained in the accompanying text Find Object function allows you to use strings of characters (for example, 0CUST) or wildcard searches (for example, 0CUST_*B) to search for objects.
In the object types view, you can use the input help: By double-clicking the This graphic is explained in the accompanying text Select Objects icon in the tree structure of the corresponding object type, you can display the Input Help for Metadata screen. Select the required objects. Choose This graphic is explained in the accompanying text Transfer Selections.
Caution
If you implement SAP Basis Plug-In releases lower than 2005.1 in the source system, you have to copy the BI Content DataSources of this source system to the active version and replicate them to the BI system before you can use them to transfer data.
More information:
Structure linkCopying the BI Content DataSource to the Active Version
Defining Grouping Mode
In the Collected Objects area of the screen, the system displays the selected objects and all their dependent objects. Collected objects are stored by default in the repository cache. This reduces the time it takes to access these objects when you want to use them again.
Note
When you copy objects to the Collected Objects screen area, these objects are also added to the tree structure of the corresponding object type in the center screen area and are stored for your user. This personal object list is available for each user every time the program is started.
If you want to remove objects from your personal list, select the objects that you want to remove and choose Remove Object from Display in the context menu or choose the corresponding icon.
Objects that are used by other objects are only displayed as changeable in the tree display for collected objects the first time they are listed. Any further instances of these objects are grayed out so you cannot modify them. If you need to edit the object, switch to the list display for collected objects.
7. Check the setting in the Collected Objects screen area
Check the settings for the BI Content installation or transport.
More information: Checking Settings
Result
You can now install the BI Content or start the transport.
Regards
Ramakrishna Kamurthy

TAN item and LEIS item in standard sales order OR

Hi,
I have a requirement to handle standard item (item category TAN) and service item (item category LEIS) in the same order.
One with delivery and and the other without delivery. How to handle this ? Can I have two different billing document for this?
One is order related billing (for LEIS) and the other is for delivery related billing (for TAN items) from the same sales document?
Regards,
SAM

Hi,
Please follow the guidlines and get the solution:
1, Maintain a copy controlls w.r.t order and billing type documents. (use VTFA)
2, for the service Item to popup in billing maintain 'DIP Profile" use "ODP1" and maintain service item in Material determination view/tab with its cost element / G/L account., Also specifiy this DIP profile in Sales B tab of ITEM view .
3, maintain proper values / condition record for the Material / service item.
4, After saviong order for your service item and material please do PGI ( only for material)
5, finally do billing w.r.t order you will get the result.
Note: We normally use this DIP profile for resource related billing: i.e. for service items.
Please try out as guided above you must get the result.
regards
DSR
Edited by: D.Srinivasa Rao on Nov 3, 2011 6:36 AM

Installation of machine after delivery & Resite of machine

Kindly refer the below process u2013
1. Scenario u2013
u2022     Customer has one machine installed in one location and he requests to relocate the machine from one location to another
It could be from one branch to another branch ( Both branch are in different cities )
u2022     The relocation of machine can happen within one city (e.g destination location and the current location of machine is in same city and under one branch)
u2022     Sometimes client charges for its service and sometimes it does not charge ( e.g If relocation to be happen is in same building )
2. After delivery of machine to customer premises client sends his service engineer to install the machine and after the successful installation only client raises the bill to customer .
How could i capture this installation process in SAP
Kindly provide your inputs
Regards,

Hi Ravi,
This Scenario is related to Customer Services module in SAP, Please fallow these steps.
1, you need to maintain all SD relevant data along with Customer master data and material master (Create also a service material for billing on installation) for the machine as well.
2, Under Plant maintenance & Customer Services Menu in SAP configure the following:
     a), Define the Functional locations of the customer where you have to install the machine.
     b), Define machine or Equipment as per your requirement. Also work centre if required.
     c), for service processing (External) configure the service order types I.e. u201CSM02u201D.
Also ref. the link: http://help.sap.com/saphelp_46c/helpdata/en/e6/4a903f9e0311d189b70000e829fbbd/frameset.htm
3, for Billing please ref. Resource related billing, here you need to maintain a DIP Profile using u201CODP1u201D and check the consistency with u201CODP2Au2019.
Also maintain copy controls for order type (DR) to billing type.
     Maintain Cost elements for the service material in the DIP profile in material determination view.
Further you follow the Service processing through service order creation till billing (Broadly) :
Service notification (IW51) -> Service order creation- > Entry of equipment, SP, components-etc>,service order confirmation (IW41) - >, Debit memo request - > Billing
Once you create service order only you can send the service technician to the customer site, and do resource related billing. Any doubts please get back.
Please try all the best.
Regards
DSR

How to deactivate the Keyboard shortcuts (QuickTime PlugIn)

Hi,
Is there a way, to Disable the Keyboard Shortcuts when using the QuickTime PlugIn within IE and/or Firefox ?

Are you viewing or are you serving these QuickTime files?
The QuickTime Control Panel offers options to run in "kiosk" mode so that the viewed file can't be saved via the Pro upgrade. Each user account has their own settings.
To prevent the keyboard option in the QuickTime movie controller from appearing in a Web based file you would set the object and embed tags to use kioskmode="true". This removes it from the controller menu and stops drag and drop capture but will not stop a determined viewer from obtaining a local copy of your file.
Other QuickTime keyboard options also exist and many people don't know about them.
For example (once the QuickTime file has "focus" in the browser) the arrow keys adjust the movie volume (up/down) and the spacebar starts and stops playback.

How to install business content Info Objects..

Hello all.
I am trying to do some BW extraction in our sandbox. Unfortunately I dont know how to install BC infoobjects. I have searched thru this forum but am still not fully sure. I have the source system client connected to BI. I replicated the datasources and see a ton of datasources under the UNASSIGNED NODES tree.
Eg: How do I install the InfoObject 0Material. Can somone tell me steps..I think I can figure out the rest after that.
Thanks in advance.

Hi
The Data Warehousing Workbench for installing BI Content has three navigation windows:
In the left-hand window you determine the view of the objects in the middle area of the screen.
In the middle window, you select the objects that you want to activate.
In the right-hand window, you make the settings for installing the BI Content. The right-hand window also contains an overview of the objects you have selected, and it is here that you start installation of BI Content.
In the Data Warehousing Workbench, you use the Navigation Window On/Off pushbutton in the toolbar to display or hide the left-hand navigation window. The rest of this section assumes that the left-hand navigation window is displayed.
2. Assign Relevant Source Systems
If you want to assign a source system, select the Source System Assignment function. The Choose Source System by Default? dialog box appears.
Select one or more source systems by setting the corresponding indicators in the Default Assignment column.
Only ever select the source systems that you really need, otherwise you may have to wait unnecessarily when objects are collected.
The assignment of the source system is only relevant for source-system dependent objects (such as transfer rules, file DataSources, and InfoPackages). If more than one source system is available, only those objects assigned to the specified source system are collected ready for the transfer. Objects that have not been assigned to the specified source systems are ignored.
For more information about the special features inherent in activating process chains that can reference source-system dependent objects, see the Customer Content documentation, under Process Chains and Process Variants.
If you do not select a source system, all the source systems are assigned automatically. You can change your selection later using the Source System Assignment function.
3. Group Objects To Be Included, Determine Mode of Collection for Objects
Make the settings you require from the following selection lists on the right-hand side of the screen:
Grouping
Choose the objects that you want the system to include. The groupings combine the objects from a particular area. You have the following options:
Only Necessary Objects (default setting)
Data Flow Before
Data Flow Afterwards
Data Flow Before and Afterwards
If you change the default setting (Only Necessary Objects), the new setting becomes the default setting for your user.
The grouping selection has an impact on system performance during BI Content installation. For more information, see View of Objects and Object-Specific Recommendations.
Collection Mode
Select how you want to collect the objects:
Collect Automatically (default setting): The data is collected when the objects are selected.
Start Manual Collection: The data is only collected when you choose Collect Dependent Objects.
Set the collection mode to Start Manual Collection. You can select all the objects without having to wait.
4. Determine View of Objects
In the left-hand navigation window, specify how you want the objects to be displayed. For more information, see View of Objects and Object-Specific Recommendations.
5. Transfer the Objects to Collected Objects
In the central area of the screen, select the objects that you want to install, and drag and drop them into the right-hand Collected Objects area of the screen.
The Find Object function allows you to use strings of characters (for example, 0CUST) or wild card searches (for example, 0CUST_*B) to search for objects.
Input help is available for every type of object: Double-click on the Select Objects icon in the tree structure of the corresponding object type to display the Input Help for Metadata screen. Select the required objects. Choose Transfer Selection.
If you implement BI Service API Releases lower than 7.0 in the source system, you have to install the active version of the BI Content DataSources in the source system and replicate them in the BI system before you can use them for transferring data into BI. For more information, see Installing BI Content DataSources and Metadata Upload for SAP Systems.
In the Collected Objects area of the screen, the system displays the selected objects and all dependent objects. Collected objects are stored by default in the repository cache. This reduces the time it takes to access these objects when you want to use them again.
When you transfer objects into the Collected Objectsarea of the screen, these objects are also added to the tree structure of the corresponding object type in the central area of the screen and stored for your user. This personal object list can be called up each time the program is restarted.
If you want to remove objects from your personal list, select the objects that you want to remove and choose the Remove Object from Display option from the context menu or click on the icon.
Objects that are listed in several tree structures can only be changed in the place where they first appear. All additional instances of these objects are grayed out so you cannot modify them.
6. Check Settings for Collected Objects
Check the following columns in the Collected Objects area of the screen:
Install
The following BI Content objects are highlighted in this column by default:
Objects that are being transferred for the first time. There is not an active version of these objects in the system.
BI Content objects that have been redelivered in a new version. These objects can be identified by the Content time stamp in the corresponding object tables.
When setting this indicator, check whether the checkbox refers to a folder of an individual object: If the checkbox refers to a folder, the indicator is set for all the objects that belong to this folder. If the checkbox refers to an individual object, the indicator is set for a single object and the indicators for the other objects in the folder are not changed. The same applies if you deselect this indicator.
In the context menu, the following options are available for the installation:
a. Install All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Install.
b. Do Not Install All Below
The Install indicators are deselected for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy.
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
Note that the InfoSource TRCS supports the match, but the 3.x InfoSource ISTD does not.
From a technical point of view, the SAP delivery version (D version) is matched against the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. If you are sure that the object will be used in the same way after you install BI Content, you can perform an automatic match for those properties. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be copied from the delivery version.
Assign points if useful.
Thanks & Regards,
Hari

No BI Content available at all...

Dear All,
Our SAP BI 2004s system is set up technically. Now I want to set up some Business Content cubes. But they don´t appear in the AWB Business Content Tab....
Can it be that the technical consultant didn´t install the BC?
You're helpfull reaction will be rewarded and appriciated!
Thanks in advance.

Hi,
Try transporting just those info objects before you transport the cube. See if they reflect in active version in the target system. Then you can transport the cube. Its not a best pratice to send all the objects related to cube (dataflow before/after) in one huge request. Due to the dependencies, the transposrts tend to fail when they dont find the necessary dependent objects in the target
try running RSDG_IOBJ_ACTIVATE program in the target system.
Installing Business Content
Use
Before you are able to work with Business Content objects, you have to convert them from the SAP delivery version (D version) into the active version (A version). For more information, see Business Content (Versions).
SAP recommends that you install Business Content objects in the following cases:
·        After a Content release upgrade
An upgrade to a new Content release usually contains a large number of new and modified Business Content objects. If you want to be able to use the new and modified Business Content, you have to reinstall the Business Content objects. Refer to the Release Notes published with the upgrade. In some cases, SAP will recommend explicitly that you install the A versions of certain objects.
·        After installing a Content Support Package
Refer to the SAP Notes that are delivered with each Content Support Package. These notes contain information on why certain Business Content objects are being redelivered.
Procedure
The following is an overview of the individual steps in the procedure: These steps are subsequently explained in more detail.
       1.      Navigate to the Administrator Workbench to install Business Content (selection of objects, settings for the transfer, starting the transfer).
       2.      Assign relevant source systems.
       3.      Group objects to be included, determine mode of collection for the objects.
       4.      Determine the view of the objects.
       5.       Transfer the objects in Collected Objects.
       6.      Check the settings for the Collected Objects with reference to the Install,Match or Copy and Active Version Available functions.
       7.      Make settings in the selection list and Transfer.
       8.      Correct errors.
1. Navigate to the Administrator Workbench to Install Business Content
In the main menu of the SAP Business Information Warehouse select Modeling ® Administrator Workbench: Business Content. If you are already in the Administrator Workbench, select the Business Content function area by clicking on the corresponding pushbutton in the left-hand navigation window or by choosing the path Goto ® Install Business Content.
The Administrator Workbench for installing Business Content has three navigation windows:
·        In the left-hand window you determine the view of the objects in the middle area of the screen.
·        In the middle window, you select the objects that you want to activate.
·        In the right-hand window, you make the settings for installing the Business Content. The right-hand window also contains an overview of the objects you have selected, and it is here that you start the installation of the Business Content.
You use the Navigation Window On/Off pushbutton on the toolbar in the Administrator Workbench to display or hide the left-hand navigation window. The rest of this section assumes that the left-hand navigation window is displayed.
2. Assign Relevant Source Systems
If you want to assign a source system, select the Source System Assignment function. The Choose Default Source Systems dialog window appears.
Select one or more source systems by setting the corresponding indicators in the Default Assignment column.
Only ever select the source systems that you really need, otherwise you may have to wait unnecessarily when objects are collected.
The assignment of the source system is only relevant for source-system dependent objects (such as transfer rules, file DataSources, and InfoPackages). If more than one source system is available, only those objects assigned to the specified source system are collected ready for the transfer. Objects that have not been assigned to the specified source systems are ignored.
For more information about the special features inherent in activating process chains that can reference to source-system dependent objects, see the Customer Content documentation, under Process Chain and Process Variant.
If you do not select a source system, all the source systems are assigned automatically. You can subsequently change your selection by using the Source System Assignment function.
3. Group Objects To Be Included, Determine Mode of Collection for Objects
Make the settings you require from the following selection lists on the right-hand side of the screen:
·         Grouping
Choose the objects that you want the system to include. The groupings combine the objects from a particular area. You have the following options:
¡        Only Necessary Objects (default setting)
¡        In Data Flow Before
¡        In Data Flow Afterwards
¡        In Data Flow Before and Aftrwds
For more information about groupings, see Collection Object Grouping.
If you change the default setting (Only Necessary Objects), the new setting becomes the default setting for your user.
The grouping selection has an impact on system performance when installing Business Content. For more information, see View of Objects and Object-Specific Recommendations.
·        Collection Mode
Select how you want to collect the objects:
¡        Collect Automatically (default setting): The data is collected directly when the objects are selected.
¡        Start Manual Collection: The data is collected only when you click on the Gather Dependent Objects icon.
Set the collection mode to Start Manual Collection. You can then select all objects without having to wait.
4. Determine View of Objects
In the left-hand navigation window, specify how you want the objects to be displayed. For more information, see View of Objects and Object-Specific Recommendations.
5. Transfer the Objects in Collected Objects
In the central area of the screen, select the objects that you want to install, and use the drag and drop function to transfer them into the right-hand Collected Objects area of the screen.
The Find Object functionenables you to use strings of characters (for example, 0CUST) or wild card searches (for example, 0CUST_*B) to search for objects.
Input help is available for every type of object: Double-click on the Select Objects icon in the tree structure of the corresponding object type to display the Input Help for Metadata screen. Select the required objects. Choose Transfer selection.
You can only use the Business Content DataSources of a source system for transferring data in BW if you have transferred these in their active forms and then copied them into the BW system. For more information, see Implementing Business Content DataSources .
In the Collected Objects area of the screen, the system displays the selected objects and all dependent objects. To reduce the time taken to access the objects when wanting to use them again, the collected objects are stored by default in the Repository Cache.
When you transfer objects into the Collected Objects area of the screen, these objects are also added to the tree structure of the corresponding object type in the central area of the screen and stored for your user. This personal object list can be called up each time the program is restarted.
If you want to remove objects from your personal list, select the objects that you want to remove and choose the Remove Object from Display option from the context menu or click on the icon.
Objects that are listed in several tree structures can only be changed in the place where they first appear. All additional instances of these objects are grayed out so you cannot modify them.
6. Check Settings for Collected Objects
Check the following columns in the Collected Objects area of the screen:
·        Install
The following Business Content objects are highlighted in this column by default:
¡        Objects that are being transferred for the first time. There is not an active version of these objects in the system.
¡        Business Content objects that have been redelivered in a new version. These objects are identified by the Content time stamp in the corresponding object tables.
When setting this indicator check whether the checkbox refers to a folder of an individual object: If the checkbox refers to a folder, the indicator is set for all the objects that belong to this folder. If the checkbox refers to an individual object, the indicator is set for a single object and the indicators for the other objects in the folder are not changed. The same applies when removing this indicator.
In the context menu, the following two options are available for the installation:
                            a.      Install all Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Install.
                            b.      Do Not Install All Below
The Install indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy.
·        Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡        the match indicator is not set and
¡        the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
                            a.      Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                            b.      Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
When referring to InfoObjects it is important to differentiate between:
§         Characteristics
§         Time characteristics
§         Key figures and
§         Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        Texts
·        Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
·        Attribute only (flag)
·        Short and long text (description)
·        Time dependency of attributes
·        Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
·        Compounding
New InfoObjects are included in compounding
·        Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
·        Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
·        Application components
If the entry for the active version is initial, the delivery version is used.
·        BEx display
·        Characteristic constants
·        Default member
·        Authorizations (flag and field)
·        Selection (CHASEL)
·        InfoObject is document attribute
·        Data type
·        Length
·        Output length
·        Conversion routines
·        Lower case allowed (flag)
·        Contains master data (flag)
·        Master data is authorization relevant (flag)
·        Export DataSource (Flag)
·        F4 query design
·        F4 query runtime
·        Check ODS object
·        Contains text tables (flag)
·        Texts are language-dependent (flag)
·        Short, medium and long texts exist (each with flag)
·        Default currency
·        GIS attribute
·        Hierarchies exist (flag)
Valid for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
·        Type of key figure
·        Fixed unit
·        Fixed currency
·        Aggregation
·        Exception aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
¡        MultiProviders
¡        InfoCubes
¡        ODS Objects and
¡        InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
·        New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
·        Active Version Available
In this column, the following display options are available:
¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active the object has to be postprocessed. You find notes on postprocessing in the activation log.
Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
¡        No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in background
The selected objects are installed in the background.
Install and transport
The selected objects are installed immediately and then written to a transport request.
SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
8. Correct Errors
Any errors that occur during the installation of the Business Content are listed in a log. Click on the Log pushbutton to view this log. In the relevant maintenance transaction, repair any errors that occurred during the installation. Install the Business Content again.

Can any one help me pls

Hi Gurus,
Can anyone tell me how to do transportation and business content installation? Please send my screen shots if u have any. And what are the errors we will get when we do transportation and Business content installation?
Regards,
KM.

Hi,
   Before you are able to work with Business Content objects, you have to convert them from the SAP delivery version (D version) into the active version (A version). For more information, SAP recommends that you install Business Content objects in the following cases:
      After a Content release upgrade
An upgrade to a new Content release usually contains a large number of new and modified Business Content objects. If you want to be able to use the new and modified Business Content, you have to reinstall the Business Content objects. Refer to the Release Notes published with the upgrade. In some cases, SAP will recommend explicitly that you install the A versions of certain objects.
        After installing a Content Support Package
Refer to the SAP Notes that are delivered with each Content Support Package. These notes contain information on why certain Business Content objects are being redelivered.
       1.      Navigate to the Administrator Workbench to install Business Content (selection of objects, settings for the transfer, starting the transfer).
       2.      Assign relevant source systems.
       3.      Group objects to be included, determine mode of collection for the objects.
       4.      Determine the view of the objects.
       5.       Transfer the objects in Collected Objects.
       6.      Check the settings for the Collected Objects with reference to the Install,Match or Copy and Active Version Available functions.
       7.      Make settings in the selection list and Transfer.
       8.      Correct errors.
1. Navigate to the Administrator Workbench to Install Business Content
In the main menu of the SAP Business Information Warehouse select Modeling ® Administrator Workbench: Business Content. If you are already in the Administrator Workbench, select the Business Content function area by clicking on the corresponding pushbutton in the left-hand navigation window or by choosing the path Goto ® Install Business Content.
The Administrator Workbench for installing Business Content has three navigation windows:
·        In the left-hand window you determine the view of the objects in the middle area of the screen.
·        In the middle window, you select the objects that you want to activate.
·        In the right-hand window, you make the settings for installing the Business Content. The right-hand window also contains an overview of the objects you have selected, and it is here that you start the installation of the Business Content.
You use the Navigation Window On/Off pushbutton on the toolbar in the Administrator Workbench to display or hide the left-hand navigation window. The rest of this section assumes that the left-hand navigation window is displayed.
2. Assign Relevant Source Systems
If you want to assign a source system, select the Source System Assignment function. The Choose Default Source Systems dialog window appears.
Select one or more source systems by setting the corresponding indicators in the Default Assignment column.
Only ever select the source systems that you really need, otherwise you may have to wait unnecessarily when objects are collected.
The assignment of the source system is only relevant for source-system dependent objects (such as transfer rules, file DataSources, and InfoPackages). If more than one source system is available, only those objects assigned to the specified source system are collected ready for the transfer. Objects that have not been assigned to the specified source systems are ignored.
For more information about the special features inherent in activating process chains that can reference to source-system dependent objects, see the Customer Content documentation, under Process Chain and Process Variant.
If you do not select a source system, all the source systems are assigned automatically. You can subsequently change your selection by using the Source System Assignment function.
3. Group Objects To Be Included, Determine Mode of Collection for Objects
Make the settings you require from the following selection lists on the right-hand side of the screen:
         Grouping
Choose the objects that you want the system to include. The groupings combine the objects from a particular area. You have the following options:
        Only Necessary Objects (default setting)
        In Data Flow Before
        In Data Flow Afterwards
        In Data Flow Before and Aftrwds
If you change the default setting (Only Necessary Objects), the new setting becomes the default setting for your user.
The grouping selection has an impact on system performance when installing Business Content. For more information, see View of Objects and Object-Specific Recommendations.
        Collection Mode
¡        Collect Automatically (default setting): The data is collected directly when the objects are selected.
¡        Start Manual Collection: The data is collected only when you click on the Gather Dependent Objects icon.
Set the collection mode to Start Manual Collection. You can then select all objects without having to wait.
4. Determine View of Objects
In the left-hand navigation window, specify how you want the objects to be displayed. For more information, see View of Objects and Object-Specific Recommendations.
5. Transfer the Objects in Collected Objects
In the central area of the screen, select the objects that you want to install, and use the drag and drop function to transfer them into the right-hand Collected Objects area of the screen.
The Find Object functionenables you to use strings of characters (for example, 0CUST) or wild card searches (for example, 0CUST_*B) to search for objects.
Input help is available for every type of object: Double-click on the Select Objects icon in the tree structure of the corresponding object type to display the Input Help for Metadata screen. Select the required objects. Choose Transfer selection.
You can only use the Business Content DataSources of a source system for transferring data in BW if you have transferred these in their active forms and then copied them into the BW system.
In the Collected Objects area of the screen, the system displays the selected objects and all dependent objects. To reduce the time taken to access the objects when wanting to use them again, the collected objects are stored by default in the Repository Cache.
When you transfer objects into the Collected Objects area of the screen, these objects are also added to the tree structure of the corresponding object type in the central area of the screen and stored for your user. This personal object list can be called up each time the program is restarted.
If you want to remove objects from your personal list, select the objects that you want to remove and choose the Remove Object from Display option from the context menu or click on the icon.
Objects that are listed in several tree structures can only be changed in the place where they first appear. All additional instances of these objects are grayed out so you cannot modify them.
6. Check Settings for Collected Objects
Check the following columns in the Collected Objects area of the screen:
·        Install
The following Business Content objects are highlighted in this column by default:
¡        Objects that are being transferred for the first time. There is not an active version of these objects in the system.
¡        Business Content objects that have been redelivered in a new version. These objects are identified by the Content time stamp in the corresponding object tables.
When setting this indicator check whether the checkbox refers to a folder of an individual object: If the checkbox refers to a folder, the indicator is set for all the objects that belong to this folder. If the checkbox refers to an individual object, the indicator is set for a single object and the indicators for the other objects in the folder are not changed. The same applies when removing this indicator.
In the context menu, the following two options are available for the installation:
                            a.      Install all Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Install.
                            b.      Do Not Install All Below
The Install indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy.
·        Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡        the match indicator is not set and
¡        the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
                            a.      Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                            b.      Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
When referring to InfoObjects it is important to differentiate between:
         Characteristics
         Time characteristics
         Key figures and
         Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
        Texts
        Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
        Attribute only (flag)
        Short and long text (description)
        Time dependency of attributes
        Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
        Compounding
New InfoObjects are included in compounding
        Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
        Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
·        Application components
If the entry for the active version is initial, the delivery version is used.
        BEx display
        Characteristic constants
        Default member
        Authorizations (flag and field)
        Selection (CHASEL)
        InfoObject is document attribute
        Data type
        Length
        Output length
        Conversion routines
        Lower case allowed (flag)
        Contains master data (flag)
        Master data is authorization relevant (flag)
        Export DataSource (Flag)
        F4 query design
        F4 query runtime
        Check ODS object
        Contains text tables (flag)
        Texts are language-dependent (flag)
        Short, medium and long texts exist (each with flag)
        Default currency
        GIS attribute
        Hierarchies exist (flag)
Valid for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
        Type of key figure
        Fixed unit
        Fixed currency
        Aggregation
        Exception aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
        MultiProviders
        InfoCubes
        ODS Objects and
        InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
        New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
        Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
        New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
        Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
       New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
       Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
        Active Version Available
In this column, the following display options are available:
   The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active the object has to be postprocessed. You find notes on postprocessing in the activation log.
Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
       No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in background
The selected objects are installed in the background.
Install and transport
The selected objects are installed immediately and then written to a transport request.
SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
8. Correct Errors
Any errors that occur during the installation of the Business Content are listed in a log. Click on the Log pushbutton to view this log. In the relevant maintenance transaction, repair any errors that occurred during the installation. Install the Business Content again.
For R/3 plug-in PI 99(-A) the concept of the delivery version and the active version of BW objects for DataSources in the source system has been introduced. The DataSources delivered by SAP with Business Content are in the source system in the SAP delivery version (D version). If you want to transfer data from a source system into a BW using a Business Content DataSource, then you have to first transfer the data from the D version into the active version (A version). With a Metadata upload, the active version of the DataSource is finally replicated in BW.
Business Content DataSources of a source system are only available to you in BW for transferring data, if you have transferred these in their active versions in the source system and then carried out a Metadata upload.
In order to transfer and activate a DataSource delivered by SAP with Business Content, select your source system in the source system tree of the BW Administrator Workbench and select Customizing Extractors à Business Information Warehouse à Business Content DataSources/Activating SAP Business Content à Transfer Business Content DataSources using the context menu (right mouse button).

Gateway services

I'm trying to diagnose an issue with a dbms scheduler job. It uses Oracle Gateway to SQL server database to place data within an Oracle database. The job had been running for 3 days before user noticed there was an issue. I had to forcefully stop the job using grid control interface. I received a message saying that the CAUSE can be determined viewing trace file. I cannot locate related trace file. I've checked under 'GateWay11.2/dg4msql/log'? Is there another location that I can check?

Did you check in the database DIAG structure to if any trace information was written there?
Did you check the database alert log?
HTH -- Mark D Powell --

TS4000 removing categories

I added three categories to Reminders
A
B
C
i deleted them on all three devices and in icloud but they keep appearing. Does anyone knwo how to permanently delete them?

Hi! Rajeev
Kindly do the following:
PATH
IMG-Personnel management-Managers desktop-customer adjustment-Determine views per category.
In thsi particular table there are four columns-
Column 1- Corresponds to the scenario name
Column 2- Corresponds to the Theme Category. Function Codes that are stored in table - Define Structure of Function Codes / T77MWBFCH with function code type HOME represents your any theme category. This theme category actually falls in the category of the un-executable function code. So in order to remove any Theme category u just have to delete the entries given under the Column 2.
Column 3- Corresponds to the various views/category
Column 4- Corresponds to the value defined in the 'Determine views' step.
Hope this will be of some help.
Regards,
Vaishali

MSS Reports iview is not working

I can see a list of reports in MSS but when I click on any of the report, nothing change, it seems like it processed, then it present nothing on the screen. No error message, no report. I have configured the backend and I wonder if there is something that needs to be done on the portal or something is wrong with my configuration. I have done the following R/3 and portal config, can someone please let me know what else I need to do to make it work?
1. Created a new MDT scenario ( PM --> Mgr's DT --> Customer Adjustment -->
Define scenario-specific settings --> Define application scenario:
ZSS0 Manager Self-Service - Reports
SAP_MANG MAC_PICTURE
2. Under Define Standard Scenario, I also put the new scenario ZSS0 -
Background pict. MANAGER SELF-SERVICE - REPORTS
Enterprise log SAP_MANG
Skip initial screen
Hide virtual root
Reorg. not permitted
3. Under PM --> Mgr's DT --> Customer Adjustment --> Determine views of
organizational structure - T77MWBD (I can send you the table output if that helps).
4. Under PM-->Mgr's DT --> Enhancement of Function Codes -->Define Structure of
Function Codes....(T77MWBFCH)I can send you the table output if that helps).
5. Also table T77MWBFCO - I can send you the table output if that helps).
Portal config:
1. On the portal - I have entered ZSS0 in the properties of the Reports Iview.
Please let me know what I am missing..... Thank you very much for your help.

Hi,
May I suggest you to look to the iView documentation : <a href="https://www2.iviewstudio.com/sdn/catalog/index.cfm?action=doc_links">https://www2.iviewstudio.com/sdn/catalog/index.cfm?action=doc_links</a> or <a href="https://www2.iviewstudio.com/support_content/_16271/MSS_60_1_EN.pdf">https://www2.iviewstudio.com/support_content/_16271/MSS_60_1_EN.pdf</a>
Note that most of the iviews need to be on the same page as the "Team Viewer" iview
Kind regards

What is BI?

Hi
What is BI? Give me some links on BI

Hi,
What is BI?
you mean compare to other data warehousing solutions... for this question we can say a lot of features..
BW provide End to End solutions.. that means.. The single bw system can only do the extractions... Modeling... Reporting... every thing we can do in bw system... but where as
remaining where housing softwares we need separate tools..
IN BW we can generate web reports and we can put into portal.. so, client can access reports directly in browser...
BW can support extracting the data from different source systems (by using DB connector, and UD connector) and loaded into BW system (in IFO CUBES and ODS' s)
so, in INFO CUBE you store ur data in Multiple dimensions (16 DIMENSIONS),
if you need any further information you can post a query.. plz dont forget to ASSIGN POINTS...
BI Content is delivered as an add-on to SAP BI. The naming is SAP NW 2004s BI Content Add-on 3 SP04. This is referred to as BI Content below.
BI Content is a preconfigured set of role and task-related information models that are based on consistent metadata in SAP Business Intelligence. BI Content provides selected roles within a company with the information they need to carry out their tasks.
This information model includes integral roles, workbooks, queries, InfoSources, InfoCubes, DataStore objects, key figures, characteristics, update rules, and extractors for SAP applications.
BI Content can:
Be used in particular industries without being modified
Be modified, meaning you can work with it to any degree of detail
Serve as a template or an example for customer-defined BI Content.
In addition, Demo Content, which includes example data and can be used as display material, is available with SAP Business Intelligence.
Implementation Considerations On one hand the comprehensive BI Content for SAP Business Intelligence enables a quick and cost-effective implementation. On the other hand, it provides a model that is based on experience gained from other implementations which can be used as a guideline during implementation.
SAP Business Intelligence delivers preconfigured objects under the collective term BI Content. These objects speed up the implementation of SAP Business Intelligence because they deliver complete solutions for business information needs.
BI Content includes:
Extractor programs for SAP systems
DataSources
Process chains
InfoObjects
InfoSources
InfoProviders (InfoCubes and DataStore objects)
Variables
Data mining models
Queries
Workbooks
Web templates
Roles
SAP DemoContent delivers example data alongside Business Content Metadata. It allows you to quickly display complete demonstration scenarios from different business areas, and to get to know your way around the Business Information Warehouse.
Because SAP DemoContent is designed specifically for demonstration purposes, it uses its own namespace. DemoContent objects all have technical names beginning with "0D_". This indicates that they are separate from the companys Business Content and not designed for productive use. But you can still use the objects as templates for structuring Content at a later date.
SAPs DemoCube offers you with a demonstration scenario that can be activated in a few steps. To transfer a specific object from SAP DemoContent, choose Administration ® Administrator Workbench ® Install Business Content from the main menu of the Business Information Warehouse. Under the object type "InfoCubes", choose ® SAP Demo and select the DemoContent objects you want to transfer. Follow the procedure for Installing Business Content to copy and activate DemoContent.
DemoContent covers objects from various areas:
SAP Purchasing DemoCube
Profitability Analysis (CO-PA) DemoCube
Sales DemoCube
SAP Sales DemoCube: Overview
Before you can work with BI Content objects, you have to convert them from the SAP delivery version (D version) into the active version (A version). For more information, see BI Content (Versions).
We recommend that you install BI Content objects in the following cases:
After a BI Content release upgrade
An upgrade to a new BI Content release usually contains a large number of new and modified BI Content objects. If you want to use the new and modified BI Content, you have to reinstall the BI Content objects. Refer to the Release Notes published with the upgrade. In some cases, we recommend explicitly that you install the A versions of certain objects.
After installing a BI Content support package
Refer to the SAP Notes that are delivered with each Content Support Package. These SAP Notes contain information on why certain BI Content objects are being redelivered.
The following is an overview of the individual steps in the procedure: These steps are subsequently explained in more detail.
1. Navigate to the Data Warehousing Workbench to install BI Content (object selection, installation settings, starting installation).
2. Assign relevant source systems.
3. Group objects to be included, determine mode of collection for the objects.
4. Determine the view of the objects.
5. Transfer the objects to Collected Objects.
6. Check the settings for the Collected Objects with reference to the Install,Match or Copy and Active Version Available functions.
7. Make settings in the selection list and Transfer.
8. Correct errors.
1. Navigate to the Data Warehousing Workbench to Install BI Content
From the main Business Intelligence menu, choose Modeling ® Data Warehousing Workbench: BI Content. If you are already in the Data Warehousing Workbench, select the BI Content functional area by clicking on the corresponding pushbutton in the left-hand navigation window, or by choosing the path Goto ® Install BI Content.
The Data Warehousing Workbench for installing BI Content has three navigation windows:
In the left-hand window you determine the view of the objects in the middle area of the screen.
In the middle window, you select the objects that you want to activate.
In the right-hand window, you make the settings for installing the BI Content. The right-hand window also contains an overview of the objects you have selected, and it is here that you start installation of BI Content.
In the Data Warehousing Workbench, you use the Navigation Window On/Off pushbutton in the toolbar to display or hide the left-hand navigation window. The rest of this section assumes that the left-hand navigation window is displayed.
2. Assign Relevant Source Systems
If you want to assign a source system, select the Source System Assignment function. The Choose Source System by Default? dialog box appears.
Select one or more source systems by setting the corresponding indicators in the Default Assignment column.
Only ever select the source systems that you really need, otherwise you may have to wait unnecessarily when objects are collected.
The assignment of the source system is only relevant for source-system dependent objects (such as transfer rules, file DataSources, and InfoPackages). If more than one source system is available, only those objects assigned to the specified source system are collected ready for the transfer. Objects that have not been assigned to the specified source systems are ignored.
For more information about the special features inherent in activating process chains that can reference source-system dependent objects, see the Customer Content documentation, under Process Chains and Process Variants.
If you do not select a source system, all the source systems are assigned automatically. You can change your selection later using the Source System Assignment function.
3. Group Objects To Be Included, Determine Mode of Collection for Objects
Make the settings you require from the following selection lists on the right-hand side of the screen:
Grouping
Choose the objects that you want the system to include. The groupings combine the objects from a particular area. You have the following options:
Only Necessary Objects (default setting)
Data Flow Before
Data Flow Afterwards
Data Flow Before and Afterwards
If you change the default setting (Only Necessary Objects), the new setting becomes the default setting for your user.
The grouping selection has an impact on system performance during BI Content installation. For more information, see View of Objects and Object-Specific Recommendations.
Collection Mode
Select how you want to collect the objects:
Collect Automatically (default setting): The data is collected when the objects are selected.
Start Manual Collection: The data is only collected when you choose Collect Dependent Objects.
Set the collection mode to Start Manual Collection. You can select all the objects without having to wait.
4. Determine View of Objects
In the left-hand navigation window, specify how you want the objects to be displayed. For more information, see View of Objects and Object-Specific Recommendations.
5. Transfer the Objects to Collected Objects
In the central area of the screen, select the objects that you want to install, and drag and drop them into the right-hand Collected Objects area of the screen.
The Find Object function allows you to use strings of characters (for example, 0CUST) or wild card searches (for example, 0CUST_*B) to search for objects.
Input help is available for every type of object: Double-click on the Select Objects icon in the tree structure of the corresponding object type to display the Input Help for Metadata screen. Select the required objects. Choose Transfer Selection.
If you implement BI Service API Releases lower than 7.0 in the source system, you have to install the active version of the BI Content DataSources in the source system and replicate them in the BI system before you can use them for transferring data into BI. For more information, see Installing BI Content DataSources and Metadata Upload for SAP Systems.
In the Collected Objects area of the screen, the system displays the selected objects and all dependent objects. Collected objects are stored by default in the repository cache. This reduces the time it takes to access these objects when you want to use them again.
When you transfer objects into the Collected Objectsarea of the screen, these objects are also added to the tree structure of the corresponding object type in the central area of the screen and stored for your user. This personal object list can be called up each time the program is restarted.
If you want to remove objects from your personal list, select the objects that you want to remove and choose the Remove Object from Display option from the context menu or click on the icon.
Objects that are listed in several tree structures can only be changed in the place where they first appear. All additional instances of these objects are grayed out so you cannot modify them.
6. Check Settings for Collected Objects
Check the following columns in the Collected Objects area of the screen:
Install
The following BI Content objects are highlighted in this column by default:
Objects that are being transferred for the first time. There is not an active version of these objects in the system.
BI Content objects that have been redelivered in a new version. These objects can be identified by the Content time stamp in the corresponding object tables.
When setting this indicator, check whether the checkbox refers to a folder of an individual object: If the checkbox refers to a folder, the indicator is set for all the objects that belong to this folder. If the checkbox refers to an individual object, the indicator is set for a single object and the indicators for the other objects in the folder are not changed. The same applies if you deselect this indicator.
In the context menu, the following options are available for the installation:
a. Install All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Install.
b. Do Not Install All Below
The Install indicators are deselected for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy.
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
Note that the InfoSource TRCS supports the match, but the 3.x InfoSource ISTD does not.
From a technical point of view, the SAP delivery version (D version) is matched against the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. If you are sure that the object will be used in the same way after you install BI Content, you can perform an automatic match for those properties. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be copied from the delivery version.
Example of an automatic match:
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. To be able to use the additional attributes, the delivery version has to be reinstalled from BI Content. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the BI Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match:
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When BI Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set by default to prevent the customer version being overwritten unintentionally. If the BI Content of the SAP delivery version is to be matched against the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if:
The match indicator is not set, and
The install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
a. Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
b. Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties that are taken into account when versions are matched are listed below.
When referring to InfoObjects it is important to differentiate between:
Characteristics
Time characteristics
Key figures and
Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
Texts
Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
Attribute only (indicator)
Short and long text (description)
Time dependency of attributes
Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
Compounding
New InfoObjects are included in compounding
Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
Application components
If the entry for the active version is initial, the delivery version is used.
BEx display
Characteristic constants
Default member
Authorizations (indicator and field)
Selection (CHASEL)
InfoObject is document attribute
Data type
Length
Output length
Conversion routine
Lower case allowed (indicator)
Contains master data (indicator)
Master data is authorization relevant (indicator)
Export DataSource (indicator)
F4 query design
F4 query runtime
Check DataStore object
Contains text tables (indicator)
Texts are language-dependent (indicator)
Short, medium and long texts exist (each with indicator)
Default currency
GIS attribute
Hierarchies exist (indicator)
Validty for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
Type of key figure
Fixed unit
Fixed currency
Aggregation
Exception Aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
MultiProviders
InfoCubes
DataStore objects and
InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
Active Version Available
In this column, the following display options are available:
: The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
Date symbol: The object is already available in an active version. However, the active version belongs to an older BI Content release. We recommend that you install the latest version.
Gray symbol : An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active, the object has to be postprocessed. In the activation log, you can find notes on postprocessing.
Postprocessing: An InfoObject may have status inactive if changes have been made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in Background
The selected objects are installed in the background.
Install and Transport
The selected objects are installed immediately and then written to a transport request.
We recommend that you use the Install in Background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time. Make sure that when you install objects in the background, the versions are not matched. It is always the delivery version that is installed. They are not matched against any available customer versions.
8. Correct Errors
You can find out if errors occurred during the installation of BI Content by displaying a log. Choose the Log pushbutton to access the log. In the relevant maintenance transaction, repair any errors that occurred during the installation. Install the BI Content again.
Thanks,
Sankar M

[Solved] Compile Secondlife/Firestorm with Autobuild on 32bit Arch

Hey all, this is my first forum post so hope it is an the right place here and you can help me I tried to complie the Firestorm Viewer for Secondlife with Autobuild but i get this error.
Someone know whats going wrong here or what is missing ? Hope you can help me. Im using Archlinux 32bit version and gcc 4.6 , the command i used to start was:
sudo autobuild configure -c ReleaseFS_open
Hope that helps and thank you!
[sonix@linux phoenix-firestorm-lgpl]$ sudo autobuild configure -c ReleaseFS_open
PLATFORM: 'linux32'
KDU: false
FMOD: false
PACKAGE: true
CLEAN: false
BUILD: false
CONFIG: true
PASSTHRU:
BTYPE: Release
Logging to /home/sonix/firestormsrc/phoenix-firestorm-lgpl/build-linux-i686/logs/build_linux32.log
Versioning...
/home/sonix/firestormsrc/phoenix-firestorm-lgpl /home/sonix/firestormsrc/phoenix-firestorm-lgpl/build-linux-i686
Nicht vertrauenswürdige Datei /home/sonix/firestormsrc/phoenix-firestorm-lgpl/.hg/hgrc vom Nutzer sonix, Gruppe users
Nicht vertrauenswürdige Datei /home/sonix/firestormsrc/phoenix-firestorm-lgpl/.hg/hgrc vom Nutzer sonix, Gruppe users
Channel : Firestorm-private-linux
Version : 3.2.1.24004
File "./scripts/update_version_files.py", line 63
print "Usage:"
^
SyntaxError: invalid syntax
/home/sonix/firestormsrc/phoenix-firestorm-lgpl/build-linux-i686
Configuring linux32...
Removing select previously packaged resources, they will refresh at build time
-- Building with OpenAL audio support
-- Building with OpenAL audio support
-- We seem to have an artwork bundle in the tree - brilliant.
File "/home/sonix/firestormsrc/phoenix-firestorm-lgpl/indra/../scripts/build_version.py", line 64
print get_version(name)
^
SyntaxError: invalid syntax
CMake Error at cmake/BuildVersion.cmake:16 (message):
Could not determine viewer version
Call Stack (most recent call first):
newview/CMakeLists.txt:1274 (build_version)
File "/home/sonix/firestormsrc/phoenix-firestorm-lgpl/indra/../scripts/build_channel.py", line 58
print get_channel(name)
^
SyntaxError: invalid syntax
CMake Error at cmake/BuildVersion.cmake:32 (message):
Could not determine channel
Call Stack (most recent call first):
newview/CMakeLists.txt:1275 (build_channel)
-- Configuring incomplete, errors occurred!
Finished
[sonix@linux phoenix-firestorm-lgpl]$
Btw tried it in Ubuntu too and there it is working. So maybe something is missing in my Arch install ?
Get it solved with the help of this Hompage:
http://axezn.tk/2011/09/16/compiling-viewers/
But i dont know how to mark this post as solved ...
Last edited by sonix1985 (2011-11-15 08:49:32)

You are welcome and I share your problems in debugging such errors.
By the way though: In Archlinux there is a section "AUR", which contains packages not in the official repositories, but provided by users for a million reasons. If you go to:
https://aur.archlinux.org/packages.php? … _Search=Go
you will find that different viewers are available there in 32/64 bit stable versions. Plus someone will have taken the time to sort out any specific problems to compile them with an Arch system and probably update them. Maybe you want to go there and use one of those.

Determining Hours Displayed in Day and Week View

Hi there,
Even though I have determined the Day hours to be, for example, 7am to 6pm in iCal Preferences, and I have determined the number of hours to be shown on the screen to be, for example, 11 hours, I still have to scroll down to fit my Day's hours in the view. In addition, the non-day hours (i.e. midnight to 7am, 6pm to midnight) are still being shown.
Is there any way of removing the non-day hours, and in effect the scrollbar so that on opening iCal, the correct hours as I have determined them are displayed?
Why would I want to open my Day or Week view and have at the top (what I would expect to be the first thing of my "Day") to in fact be Midnight (and go back to sleep)?
Am I missing something or does this not work the way I think it should, or thought it did?

See Fred Grieve's answer and John Maisey's solution here:
http://discussions.apple.com/thread.jspa?threadID=1868347&tstart=0

Determine View

Similar Messages

Maybe you are looking for