Logon CMC.
Area 'Manage'
Escoger 'Aplicativos'
Escoger 'Infoview'
Opciones:
Header and Style
Hola de estilos: default.css
Logo:
Do Not Display Logo: No logo is displayed and the colors selected for the header are displayed.
Display Business Objects Logo
This is the default setting and the image can be located at /BusinessObjects Enterprise 11/Web Content/Enterprise11/InfoView/images/banner_logo.gif.
Display Custom Logo
Specify the URL where the custom logo is located. Ensure that this URL is mapped to the web server.
Use Custom Header Colors
Change the default colors on the header.
Style Sheet
Found at /BusinessObjects Enterprise 11/Web Content/Enterprise11/InfoView/default.css, this style sheet can be replaced with your own or the default can be modified. The style sheet can be used to change such items as font, color, and size. Each entry in the style sheet is documented; however, make a backup copy of the default before making changes.
Display
This section hides or displays certain features, as described in Table 24.9.
Table 24.9. Global Display Features of InfoView Option
Description
Show Preferences Button
If checked, this displays the Preferences icon. If this is not displayed, users will have no control over setting their preferences.
Show Type Drop-Down List
Removes the ability to filter the page by object type and all objects are displayed.
Show Filters Tab on the Schedule Tab
Administrators might not want users applying filters to reports. The filters section gives the user the ability to rewrite the filter or SQL WHERE clause, and this is recommended only for advanced users.
Default Navigation View
Administrator can select either Category or Folder as an initial view of the navigation section.
Maximum Number of Pages of Objects to Show
Pages of objects are created by the number of objects the user chooses to display on a page. If more objects are available than are displayed on the page, additional page numbers are shown.
SAP Note 1414285 that will give you some pointers, here are the details of the Note:
Customizing the InfoView logon screen:
- Go to folder: C:\Program Files\BusinessObjects\Tomcat55\webapps\InfoViewApp\res\schema.blue\
- Rename the file: login_banner_center.gif to login_banner_center_OLD.gif
- Save the new logo file as login_banner_center.gif
- Restart the Tomcat server and open the InfoView.
- After opening the InfoView you will find the new logo
- Customizing the InfoView top banner logo:
After login to InfoView you want to change the logo that appears above the Menu
- Go to folder: C:\Program Files\BusinessObjects\Tomcat55\webapps\InfoViewApp\res\schema.blue\
- Rename the file: IV_left_topbanner.gif to IV_left_topbanner_OLD.gif
- Save the new left logo file as IV_left_topbanner.gif
- Rename the file: IV_right_topbanner.gif to IV_ right_topbanner_OLD.gif
- Save the new right logo file as IV_ right_topbanner.gif
- Take the backup of the file default.css as default_OLD.css
- Open the file default.css and adjust the following parameters in the “/* InfoView banners */” session as appropriated
.bannerCustomLeft
.bannerCustomRight
.bannerLogo
.bannerLeft
.bannerUserName
.bannerCenter
.bannerRight
- You may want to change the background-color and the banner height and width
- Save and close the file
- Restart the Tomcat server
- Open the InfoView and log in
- Check if the logo is according with your needs.
1. Log into CMC
2. Click BusinessObjects Enterprise Applications
3. Once inside, click Infoview
4. Click properties in infoview. In the section Header and Style you can put customer logo.
Please note: you should have rights to do the view/change etc in CMC.
viernes, 18 de febrero de 2011
viernes, 4 de febrero de 2011
Transportar el contenido de una tabla
A veces tenemos que transportar el contenido de algunas tablas de un entorno a otro. Esto lo haremos con tablas Z. Las tablas estándard de SAP no es recomendable realizarlo por este método porque no sabemos las implicaciones que esto puede tener en los diferentes módulos y porque siempre es mejor realizar los cambios por parametrización.
El ejemplo que tenemos a continuación es una tabla Z utilizada en BW. Esta tabla la tenemos definida en R3 y cada actualización que realicemos sobre ella se deberá realizar en desarrollo y deberá transportarse a los diferentes entornos.
Esta es la orden de transporte que tenemos de ejemplo:

Es importante indicar el ID de programa R3TR y el tipo de objeto TABU. En el objeto pondremos el nombre de la tabla.
Para crear una nueva orden de transporte iremos al folio en blanco o por Orden/Tarea -> Crear. En ese momento el sistema nos pedirá saber de que orden se trata: Customizing o Workbench. En este caso será de Workbench.
El ejemplo que tenemos a continuación es una tabla Z utilizada en BW. Esta tabla la tenemos definida en R3 y cada actualización que realicemos sobre ella se deberá realizar en desarrollo y deberá transportarse a los diferentes entornos.
Esta es la orden de transporte que tenemos de ejemplo:

Es importante indicar el ID de programa R3TR y el tipo de objeto TABU. En el objeto pondremos el nombre de la tabla.
Para crear una nueva orden de transporte iremos al folio en blanco o por Orden/Tarea -> Crear. En ese momento el sistema nos pedirá saber de que orden se trata: Customizing o Workbench. En este caso será de Workbench.

Botanita, Botana, SAP, BW, Ponte Carreira
Truquis BW
miércoles, 2 de febrero de 2011
Ejemplo Rutina INIT
"loop at source_package assigning .
IF NOT (-PO_STATUS NE 'K'
** PO is not a replication from SRM System (in case of Extended Scenario
** PO is created in SRM and a copy of the PO is created in ERP with
** PO_STATUS = K)
*
AND (-PROCESSKEY = '001' OR "Normal purchasing order
-PROCESSKEY = '011' OR "Stock transport order
-PROCESSKEY = '021' OR "Cross company order
** Only Purchase Orders
*
-PROCESSKEY = '004' OR "Normal scheduling agreement
-PROCESSKEY = '014' OR "Stock transport agreement
-PROCESSKEY = '024') "Cross company agreement -
** or Call Offs from schedule agreements
*
AND-BWAPPLNM EQ 'MM' ).
DELETE source_package.
ENDIF.
ENDLOOP."
**************************
********************
IF NOT (
** PO is not a replication from SRM System (in case of Extended Scenario
** PO is created in SRM and a copy of the PO is created in ERP with
** PO_STATUS = K)
*
AND (
** Only Purchase Orders
*
** or Call Offs from schedule agreements
*
AND
DELETE source_package.
ENDIF.
ENDLOOP."
delete DATA_PACKAGE where (
CUST_MKT ne '009' and
CUST_MKT ne '020' ) and
(
DOC_TYPE ne 'ZA11' and
DOC_TYPE ne 'ZD11' and
DOC_TYPE ne 'ZD21' and
DOC_TYPE ne 'ZD31' and
DOC_TYPE ne 'ZR11' and
DOC_TYPE ne 'KE' ) and
(
MATL_TYPE eq 'ZPPT' or
MATERIAL eq '000000000001200002' ).
Botanita, Botana, SAP, BW, Ponte Carreira
ABAP
Suscribirse a:
Entradas (Atom)