How to migrate Themes, HTML templates, MIME objects to ECC6.0
Hi Friends
How to migrate Themes, HTML templates, MIME objects which are developed in SAP Web@Studio.
or How to use program SIAC_UPLOAD ??
regards
siddharth
Hello Murray,
Your steps sound correct. I would add that you generally need the following:
1. publish the IAC, SYSTEM, and WEBGUI Internet Services (also from SE80)
2. make sure the Integrated ITS is working. Meaning you should activate the ITS in the profile parameter, this can be seen in transaction SITSPMON. Some services in transaction SICF also need to be activated, like the default_host/sap/public/bc/its
From your error message though it looks like the URL you have used is either incorrect or you have used the External Alias feature in SICF? The URL for the ITS is usually http://host:port/sap/bc/gui/sap/its/service. Second, the error is about a language resource file (.htrc), you have not specified if you created one or not. To create one in the language you are logged in with just go to SE80, open your Internet Service and double click on the "Topic xx". Don't forget to publish after creating and saving it.
Edgar
Similar Messages
-
How to import all HTML templates into your IT Server?
Hi All,
I am trying to configure Leave Request workflow (WS200000081).I have read that Html Templates need to be import/published in your ITS server. I am not clear as to what is an html template and how to publish it?
Regards,
Pavanmeet.Hi Pavanmeet,
Since this is a standard service file provided by SAP no need to publish it.
For the error you mentioned, you can do the setting as below.
Go to SE80. In the menu go to "UTILITIES" select "SETTINGS". The screen is displayed. In the tab select ITS. Here you can set the ITS server path. This ITS will be selected when you publish the service file.
Regards
Arun -
How to avoid Multiple download of Mime Objects with cleared Cache
Hii!!
When using IC we client and when we are searching for the CSR multiple Mime Objects are getting Downloaded ..Can anybody tell me exactly in which class or function module these mime objects are getting downloaded or where the URL of the same is getting generated?I think I've figure out what is happening here. Previous post didn't descript the situation quite clear, it is acturally like this:
// previous code:
var container:Sprite = new Sprite();
var bitmapCantainer:Sprite = new Sprite();
bitmapCantainer.addChild(bitmapCache);
bitmapCantainer.mouseEnabled = false;
bitmapCantainer.mouseChildren = false;
container.addChild(bitmapCantainer);
container.hitArea = someSpriteMadeUp;
// it turns out there'is a parent container of the "container" sprite I created
// and I disable that
parentContainer.mouseEnabled = false;
So now I don't need to avoid any interaction of transparent part of bitmap with mouse evnets, JUST set mouseEnabled property to false of the parent display object which is in the same depth of display list of which those display objects you don't what be "covered" are in. -
How do you create HTML templates in Safari
Internet explorer allows you to create templates with embedded images. How is this done in Safari? Safari Help is no help. I want to create an e-card. Can anyone help and point me in the right direction? Thanks.
Select
Safari ▹ Preferences ▹ Extensions
from the Safari menu bar. If any extensions are installed, disable them and test. -
Deciphering Aperture Web Themes: the html templates v3
version 3 of my Aperture Web Theme html template reference. enjoy
the html templates.
rkid attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
<ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
"navbar"
a <ul> element containing all of the navigation elements.
"active" and "inactive"
rkid attributes to enable the coder to place different formatting on
current and non-current page numbers in the navbar.
eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
<li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
"content"
a <div> containing all of the album images and their metadata.
"pictureblock"
a mandatory <table> in which the images are placed, one image per <td>.
the <table> must even be used on the Detail page where only one image is
displayed.
the metadata will be within the "pictureblock" table if more than one
image is displayed so that the metadata can be tied to the image. if
only one image is displayed; i.e., the Detail page; the metadata may be
in a <td> outside of the table that the image is in but still within the
"content" div, usually in the following format:
<div rkid="content">
<table>
<td>metadata
<td><table rkid="pictureblock">
"image"
the rkid for the <img> elements containing the album images, frequently
placed in <dt> elements within the table's cells.
"metadata" (added in Decipher v3)
all metadata for the respective image is specified within this element.
everything within the element is repeated for every metadata value.
the Aperture themes use the <ul> element but <div> also works:
<div rkid="metadata"><p>metaname: metavalue</p></div>
"titleblock"
a <div> containing the title text; usually <h3>; for Journals. the <h3>
element within this element must be given the attribute rkid="text" or
Aperture will ignore it.
"textblock"
a <div> containing the description text for Journals. as with the
titleblock, the <p> element/s within this div must be given the
attribute rkid="text".
"text"
the rkid given to the text data within the titleblock and textblock
elements.
Place holders:
PageTitle
used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
IndexPageURL
the gallery page/s URLs; may be more than one.
ThumbImageURL
the href links for the images, whether thumbnails or detail full size.
DetailPageURL
used within navbar:
PageCount
PageNumber
PreviousPageNumber
PreviousPageURL
NextPageNumber
NextPageURL
PageCount the total number of pages
PageNumber includes all of the page numbers listed in the navbar, one
occurrence for each page.
_Previous and _Next are more specific and are currently used to draw the
prev/next arrows in the navbar.
ImageName
ImageNameSpace
PlateNameSpace
PlateNumberSpaceSlash
*only seen* when 'Enable Plate Metadata' option in the tag popup menu is
chosen.
used to represent an index of the image in the album. the first image
shown gets the index 1, the second 2 and so on.
for the Image placeholders, the word 'Image' is used.
for the Plate placeholders, the word 'Plate' is used.
space indicates an extra space after the index, probably for html
formatting purposes because it's only used within <dt> elements.
slash indicates an extra / character after the index.
examples:
ImageName > 'Image 1'.
ImageNameSpace > 'Image 1 '.
PlateNameSpace > 'Plate 1 '.
PlateNumberSpaceSlash > '1 / '.
metaname
metavalue
the placeholders for all of the metadata names/values in the selected
metadata set.
PageWidth
not sure if Aperture calculates it based on the width and number of
images being displayed in both gallery and detail pages.
don't know why it's only used in the Special Occasion theme.
CellWidth
the width of the table cells containing the album images. not
necessarily the width of the images. may include margins as specified in
the albuminfo.plist files.
ImageWidth
the width of the image.
TableWidth
the width of the pictureblock table. it can probably be applied to other
elements too but it's length is almost certainly calculated from the
pictureblock table.
Operative attributes:
removeonfirstpage="yes"
used in the navbar to remove the Prev link from the first page.
because it's applied to the <a> element, the <a> element is removed
while leaving an empty <li> in place.
removeonlastpage="yes"
used in the navbar to remove the Next link from the last page.
because it's applied to the <a> element, the <a> element is removed
while leaving an empty <li> in place.
removeonsinglepage="yes"
used in the navbar to remove elements when there's only one page.
used in a <div> in the Art Collection to remove the whole navbar on
single pages.
contenteditable="yes"
used in text elements to indicate that the user can customise the text.
not necessary in titleblock and textblock rkid="text" elements.
in elements outside of the titleblock and textblock elements, content
will not be truly editable unless a textid is assigned to the text
elements. unfortunately, all text elements with textids are always
'common' and can not be specific to any one image.
common="yes"
the element is seen on all pages.
Other attributes:
metaseparator="|"
used in metadata formatting, within the metadata lists.
you can add additional characters. for example, the metaseparator
in the Stock Black theme is " | "; ie, a | bar with a space on both
sides. (Decipher v3)
if the metaseparator is specified and the html template places the
metadata into <li> elements as it does in most of the current themes,
then it produces non-standard html code with the metaseparator between
concurrent <li> elements.
metalayout="paragraph"
used in metadata formatting, within the metadata lists.
if not specified, the metadata will not be exported. (Decipher v3)
singlenesting="yes"
used in metadata formatting. not sure what it does yet.
textid="x"
used to id text elements outside of the titleblock and textblock
elements.
possibly no limit to the number and id names used.
examples used:
textid="copyright"
textid="header1"
picturename="x"
pictureimage="true"
picturename gives the image an id.
pictureimage="true" tells Aperture that the image is a static image
which can be designated by the user during setup of the album. they show
up in Aperture as grey blank rectangles with cross-eyes in the middle.
they do not need to be inside the "content" element
with picturename and pictureimage, we can place as many static images on
the page as we wish.
Assertions:
Aperture uses the rkid values to identify the areas of the html to be
repeated for the respective objects.
standard id and class attributes are only used by the css for formatting and
not by Aperture to write the html data.
Notes:
Aperture is hardcoded to expect and require that the album images are always
within a <table rkid="pictureblock"> element. it is not possible to place
album images outside of the table. all album images must be placed within
<td> cells within the table. the <td> code is repeated for each image.
image metadata is also normally within the rkid="content" element although
it can be outside of the rkid="pictureblock" element.
by default, the textblock rkid="text" element is added when the T+ button is
pressed within Aperture. the textblock element is switched with the
titleblock element when the Title/Text toggle button is clicked.
width and height attributes of <img> elements are rewritten by Aperture
based on the inserted images. placeholders aren't necessary within <img>
elements.
comments are stripped from the html before export some but some
Aperture-proprietary attributes are forgotten and left behind.
some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
doctype.
all markup is converted and exported in UPPER-CASE. personally, I prefer
lower-case.
high-ascii characters entered by the user are not converted to their html
entities when available. eg, the © character.
multiple <p> elements can be inserted into the titleblock and textblock
<div> elements but each of them must have the rkid="text" attribute. any
element without this attribute will be ommitted by Aperture.
the reason there are Smart Galleries but no Smart Journals is because you
need to write text between each row of images.
titleblock and textblock elements will not be applied to Galleries or Detail
templates; only to Journals.
if there are more than one titleblock or more than one textblock, only the
first will be used by Aperture.
upon export, Aperture will remove everything from within the rkid="content"
element which is not the pictureblock, titleblock or textblock elements.
(Decipher v3)
some of the Aperture templates have xhtml doctypes but are exported from
Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
that UPPER-CASE element names is not permitted with xhtml which is
case-sensitive. (Decipher v3)
Questions:
are there variable scopes with each rkid? eg, within the "content" rkid, can
every variable/placeholder be accessed?
why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
the images and related metadata in the table? easier css formatting?
JavaScript: (Decipher v3)
you can include JavaScript in the html code but cannot wrap it in html
comments because Aperture will remove everything within comments.
Aperture variables such as PageNumber will not be replaced within
attributes such as <body onload="dialog(PageNumber);">.
it is very difficult to use document.write anywhere within the html <body>.
Aperture seems to be using JavaScript to export the html and its code is not
able to cope with more than one instance of document.write in the html
templates. after hours of trial and error, I found that the most stable way
to use JavaScript within the html <body> was to only use one <script>
element and place everything within it. using document.write within a second
<script> element would almost certainly lead to unpredictable exported html,
and instability and crashes in Aperture.
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
1) one large image per thumbnail page (like a photo essay or photo blog style)
2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
This is great because I hate javascript but sometimes like the immediate visual effects it allows.
This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today. -
Deciphering web themes: the html templates; expanded reference.
the html templates.
RKID attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
<ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
"navbar"
a <ul> element containing all of the navigation elements.
"active" and "inactive"
rkid attributes to enable the coder to place different formatting on
current and non-current page numbers in the navbar.
eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
<li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
"content"
a <div> containing all of the album images and their metadata.
"pictureblock"
a mandatory <table> in which the images are placed, one image per <td>.
the <table> must even be used on the Detail page where only one image is
displayed.
the metadata will be within the "pictureblock" table if more than one
image is displayed so that the metadata can be tied to the image. if
only one image is displayed; i.e., the Detail page; the metadata may be
in a <td> outside of the table that the image is in but still within the
"pictureblock" table, usually in the following format:
<div rkid="content">
<table>
<td>metadata
<td><table rkid="pictureblock">
"image"
the rkid for the <img> elements containing the album images, frequently
placed in <dt> elements within the table's cells.
"titleblock"
a <div> containing the title text; usually <h3>; for Journals. the <h3>
element within this element must be given the attribute rkid="text" or
Aperture will ignore it.
"textblock"
a <div> containing the description text for Journals. as with the
titleblock, the <p> element/s within this div must be given the
attribute rkid="text".
"text"
the rkid given to the text data within the titleblock and textblock
elements.
Place holders:
PageTitle
used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
IndexPageURL
the gallery page/s URLs; may be more than one.
ThumbImageURL
the href links for the images, whether thumbnails or detail full size.
DetailPageURL
used within navbar:
PageCount
PageNumber
PreviousPageNumber
PreviousPageURL
NextPageNumber
NextPageURL
PageCount the total number of pages
PageNumber includes all of the page numbers listed in the navbar, one
occurrence for each page.
_Previous and _Next are more specific and are currently used to draw the
prev/next arrows in the navbar.
ImageName
ImageNameSpace
PlateNameSpace
PlateNumberSpaceSlash
*only seen* when 'Enable Plate Metadata' option in the tag popup menu is
chosen.
used to represent an index of the image in the album. the first image
shown gets the index 1, the second 2 and so on.
for the Image placeholders, the word 'Image' is used.
for the Plate placeholders, the word 'Plate' is used.
space indicates an extra space after the index, probably for html
formatting purposes because it's only used within <dt> elements.
slash indicates an extra / character after the index.
examples:
ImageName > 'Image 1'.
ImageNameSpace > 'Image 1 '.
PlateNameSpace > 'Plate 1 '.
PlateNumberSpaceSlash > '1 / '.
metaname
metavalue
the placeholders for all of the metadata names/values in the selected
metadata set.
PageWidth
not sure if Aperture calculates it based on the width and number of
images being displayed in both gallery and detail pages.
don't know why it's only used in the Special Occasion theme.
CellWidth
the width of the table cells containing the album images. not
necessarily the width of the images. may include margins as specified in
the albuminfo.plist files.
ImageWidth
the width of the image.
TableWidth
the width of the pictureblock table. it can probably be applied to other
elements too but it's length is almost certainly calculated from the
pictureblock table.
Operative attributes:
removeonfirstpage="yes"
used in the navbar to remove the Prev link from the first page.
because it's applied to the <a> element, the <a> element is removed
while leaving an empty <li> in place.
removeonlastpage="yes"
used in the navbar to remove the Next link from the last page.
because it's applied to the <a> element, the <a> element is removed
while leaving an empty <li> in place.
removeonsinglepage="yes"
used in the navbar to remove elements when there's only one page.
used in a <div> in the Art Collection to remove the whole navbar on
single pages.
contenteditable="yes"
used in text elements to indicate that the user can customise the text.
not necessary in titleblock and textblock rkid="text" elements.
common="yes"
the element is seen on all pages.
Other attributes:
metaseparator="|"
used in metadata formatting, within the metadata lists.
metalayout="paragraph"
used in metadata formatting, within the metadata lists.
singlenesting="yes"
used in metadata formatting. not sure what it does yet.
textid="x"
used to id text elements outside of the titleblock and textblock
elements.
possibly no limit to the number and id names used.
examples used:
textid="copyright"
textid="header1"
picturename="x"
pictureimage="true"
picturename gives the image an id.
pictureimage="true" tells Aperture that the image is a static image
which can be designated by the user during setup of the album. they show
up in Aperture as grey blank rectangles with cross-eyes in the middle.
they do not need to be inside the "content" element
with picturename and pictureimage, we can place as many static images on
the page as we wish.
Assertions:
Aperture uses the rkid values to identify the areas of the html to be
repeated for the respective objects.
standard id and class attributes are only used by the css for formatting and
not by Aperture to write the html data.
Notes:
Aperture is hardcoded to expect and require that the album images are always
within a <table rkid="pictureblock"> element. it is not possible to place
album images outside of the table. all album images must be placed within
<td> cells within the table. the <td> code is repeated for each image.
image metadata is also normally within the rkid="content" element although
it can be outside of the rkid="pictureblock" element.
by default, the textblock rkid="text" element is added when the T+ button is
pressed within Aperture. the textblock element is switched with the
titleblock element when the Title/Text toggle button is clicked.
width and height attributes of <img> elements are rewritten by Aperture
based on the inserted images. placeholders aren't necessary within <img>
elements.
comments are stripped from the html before export some but some
Aperture-proprietary attributes are forgotten and left behind.
some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
doctype.
all markup is converted and exported in UPPER-CASE. personally, I prefer
lower-case.
high-ascii characters entered by the user are not converted to their html
entities when available. eg, the © character.
multiple <p> elements can be inserted into the titleblock and textblock
<div> elements but each of them must have the rkid="text" attribute. any
element without this attribute will be ommitted by Aperture.
the reason there are Smart Galleries but no Smart Journals is because you
need to write text between each row of images.
titleblock and textblock elements will not be applied to Galleries or Detail
templates; only to Journals.
if there are more than one titleblock or more than one textblock, only the
first will be used by Aperture.
Questions:
are there variable scopes with each rkid? eg, within the "content" rkid, can
every variable/placeholder be accessed?
why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
the images and related metadata in the table? easier css formatting?
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)IMPORTANT!
An updated version is available in thread:
Deciphering Aperture Web Themes: the html templates v3. -
Global mime objects used in templates
Hi all
How can I upload an image to some global mime repository and then use the image in a HTML-template?
Please help fellow sapians.....are you taling about ITS HTML templates or? BW web templates?
which version of R/3 you are using? -
How to migrate the Objects from 3.1c to BI7
Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anilBW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task How-To Who
Review BI 7.0 feature lists Review BI 7.0 feature lists for possible inclusion in developments. Basis/BW
Obtain the BI 7.0 upgrade guide Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
Basis/BW
Review all upgrade SAP notes In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
BI 7.0 Upgrade notes
SAP Web Application Server 6.40 upgrade notes
OS and DB specific upgrade notes
SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
Plug-In upgrade SAP notes
Other notes identified in above notes and/or upgrade guides.
Basis/BW
Check DB and OS requirements for the target SAP BW release Check DB version/patch level and OS version/patch level required for upgrade
First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
Basis
Check SAP BW Add-on upgrade requirements Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
Basis
Check SAP BW upgrade requirements Minimum Support Package and kernel levels for upgrade
SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
Source system Plug-In requirements Basis
Check compatibility requirements with 3rd party software 3rd Party Reporting tools (example: Crystal)
ETL Tools (example: Ascential, DataStage, etc)
Scheduling tools (example. Control-M, Maestro, etc)
Monitoring tools (example: HP OpenView, Patrol, etc)
Other OS or DB related tools Basis
Check new component requirements for BI 7.0 If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
Basis
Test and distribute new SAP BW Frontend
Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool) Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
BW
Upgrade SAP Note updates Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
Basis
Alignment of SAP BW objects within your SAP BW system landscape Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
Basis/BW
Confirm all developments are deployed. Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
BW
Implement BI 7.0 Business Explorer Frontend Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
Basis
Apply latest Support Package tool patch Apply latest SPAM patch before executing PREPARE Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency Check Database consistency
Transaction DB02:
o Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o Check missing database objects (indices, tables, etc)
o Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o Check DDIC/DB consistency
Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
BW
Remove unnecessary SAP BW temporary database objects Delete all SAP BW temporary database objects:
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
This reduces the numbers of database objects that need to be copied during the upgrade.
Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
BW
Validate your SAP BW Objects for correctness prior to your upgrade Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
Ensure that any inconsistencies are identified and corrected
RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
BW
Ensure DB Statistics are up to date prior to the upgrade Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
Check DB statistics for missing Indexes for InfoCubes and Aggregates
o User transaction RSRV to check BW
Check SAP BW Support Package status Check the status of all support packages (via transaction SPAM)
Ensure the Support Package queue is empty
Confirm all applied Support Packages Basis
Check all u2018Repairsu2019 Check for unreleased repair transports
Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
BW
Check InfoObject status Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o Determine if revision should be activated or removed.
'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
BW
All ODS data loads must be activated. Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
BW
All Transfer and Update rules should be active Check for inactive Update and Transfer Rules
o All update rules and transfer rules should be active or deleted.
o Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure. BW
All InfoCubes should be active Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o All InfoCubes should be activated or deleted.
o Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
BW
All Web Report objects should be consistent prior the upgrade. Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
BW
Backup your system before starting PREPARE Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
Database admin
Address any instructions/errors generated by PREPARE Address any issues listed in log files Checks. Log generated by PREPARE.
o Repeat PREPARE until all checks are successful. Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
BW
Complete any data mart data extractions and suspend any data mart extractors Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
BW
Check that your customer defined data class definitions conform to SAP standards Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o Incorrect data classes could create activation errors during the upgrade.
BW
Remove unnecessary SAP BW temporary database objects Delete all SAP BW temporary database objects:
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
This reduces the numbers of database objects that need to be copied during the upgrade.
Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
Basis/BW
Backups! Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
Database Admin
Before Execution:
All SAP BW administration tasks should have ceased Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
Basis/Admin
Remove unnecessary SAP BW temporary database objects Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
BW
Check system parameters Check OS, DB, and Instance profile parameters.
Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
Check for any DB specific parameters for BI 7.0
Check for any new OS parameters Basis
Check Database archiving mode Turn database archive log mode back on if it was disabled during the upgrade!
Database Admin
After Execution:
Check the systemu2019s installation consistency Execute Transaction SICK to check installation consistency
BW
Check the system logs Perform a technical systems check.
Example: Check system and all dispatcher logs (inc. ICM logs)
Basis
Apply latest executable binaries Apply the latest 6.40 Basis Kernel for all executables
Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
Basis
Review BI 7.0 Support Packages for follow-up actions. Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o Follow any required instructions identified in the SAP Notes
Basis
Apply latest patches Apply the latest SPAM patch
Apply any required support packages that were not bound into the upgrade.
Basis
Apply additional BI 7.0 Support Packages
(if required) SAP recommends that customer remain current on SAP Support Packages.
Review SAP Notes for all SAP BW Support packages applied in previous task.
o Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o Follow any required instructions identified in the SAP Notes
Basis
Resolve any modified SAP delivered Role issues If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
Review and implement SAP note 569128 as required Basis
Configuring Information Broadcasting EP/KMC Connections
If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
Basis
Re-check SAP BW Object and consistency Execute RSRV to check SAP BW Object consistency
Repeat tests that we executed prior to the upgrade.
Validate results BW
Check InfoCube views for consistency Check consistency of InfoCube fact table views
It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
Check that all other Source Systems are active.
o Activate as required. Basis/BW
Check SAP BW Personalization is implemented (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
To activate highlighted Personalization, click Execute. BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
Re-create all indexes in the ODS Object definition screen in transaction RSA1.
ODS indexes must conform to the new naming convention
BW
Converting IGS chart settings
Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o Test via transaction RSRT
Execute the conversion process as directed the BI 7.0 upgrade guide.
Note: This step is required for all BI 7.0 upgrades Basis
Backup your SAP BW system Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
Database Admin -
Loading of MIME objects into HTML pages
Hi Everyone
I am trying to load two logos as mime objects into an HTML page.
I am using
call method web_page->load_mime_object
After that I use
call method web_page->show_url
Whenever I call this last method with parameter in_place as a space (to call an external browser) my logos are not displayed.
If I call the method with in_place as 'X' the logos appear.
The mime objects reside in the SAP web repository (trans smw0).
Any ideas how to pull the logos into the external page?
Regards
JohanHi Satya
Thanks very much for your reply. I do not use ITS for my purposes but it is something to be remembered for next time.
I have actually solved the problem but only with a "second price" solution.
In the HTML form I have pointed the source of my two images to a shared folder somewhere on our dev server. For our purpose this will always work.
What I am thinking is that if SAP allows an external browser to be used it should also give the means of loading the images. Maybe I just don't know how.
Now that I think about it more - I should go and try your suggestion in any case and see if it works.
I thank you again and if anyone comes with more ideas they will be as welcome.
Regards
Johan -
Mime Objects and non-static template
Hi All,
When I bring up a non-static web template, icons stored as mime objects are not initially displayed. When I do a drill down or any other operation these are then displayed.
I know that this is not an issue with static layouts.
Does anyone know how to force it so that these are displayed when the template is first called up?
Cheers,
Robert Zovic
Arinso InternationalSorry Max,
I originally included this in this group, although it is a web template designed using the Web Application Design tool.
The template itself has had it's property set to non static. This is to overcome issues with the connection/resources remaining locked by the ICM.
The icons have been uploaded through se80. It's strange but on the initial callup of the template they don't appear. On each subsequent access, they do.
Robert -
How to migrate rtf Templates in XML Publisher ?
Hi All,
I want the script so that i can download and upload the RTF files directly from my development instance to my production instance.
For this i have come across 3 links
How to migrate rtf Templates in XML Publisher?
http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120xdoig.pdf
unable to migrate physical files using XDO Loader utility
and from here i am running this command from /home/aryan directory
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD -DB_USERNAME apps -DB_PASSWORD fnd -JDBC_CONNECTION sharp.apps.com:1522:tst1 -LOB_TYPE TEMPLATE -APPS_SHORT_NAME CUSTOM -LOB_CODE ZEMP -LANGUAGE en -TERRITORY US
but it is giving me error "ksh: java: not found". could anyone can tell me how and from where i have to run the download and upload command
Thanks
AryanHi Hussein,
I tried with applmgr also and still for java -version it is giving me error ksh Java not found
and for which java it is giving me error no java found in different directories path.
Thanks
Aryan -
I have Pages 09. I have created custom templates and want to delete them. How do I delete a template I have created in Pages 09?
Pages stores those you created & saved as templates in (your account) > Library > Application Support > iWork > Pages > Templates > My Templates. The door to the user's Library is hidden in Lion but it is easy to open. In Finder, hold down the Option key while clicking on the Go menu & your users Library will appear about halfway down the list.
-
How can i reference a MIME object within a correspondence format through...
how can i reference a MIME object within a correspondence format through TX oofo or se71?
Hi, I need to put a MIME object within a correspondence's format that i've already done through Tx oofo. My problem is, that i don't know exactly how can i make the reference of that MIME object in the format? and What structure type do i have to use in order to make appear the MIME object in my correspondence's format? Does anybody can help me with this?
Regards HectorFrank,
I tried to find some examples/samples on how to create CollectionModel for a table component but not successful.
Can you clarify the following ?
1. "CollectionModel" is referenced only by af:table attributes "value", "selectedRowKeys" and "selectionListener".
The rest of af:table attributes such as "rows", "fetchSize" used to reference the iterator binding in the binding container via the EL expression "#{bindings.VOIteratorBinding.xxx} .
What should I replace that EL expression with?
2. I heck out the bean method to create the CollectionModel as following, is it close to what you mean?
public void initBusinessDataDashboardView() {
OperationBinding operation = BeanUtils.getOperationBinding("getPanelBusinessData");
Map params = operation.getParamsMap();
Key panelKey = getPanelInfoView().getKey();
params.put("panelKey", panelKey);
params.put("maximizedView", false);
panelView = (ViewObject)operation.execute();
// Heck code to create CollectionModel
RowSet rowSet = panelView.getRowSet();
ArrayList rowList = new ArrayList();
while (rowSet.hasNext()) {
rowList.add(rowSet.next());
model = new ChildPropertyTreeModel(rowList, null);
// To be used to set up af:table value, selectRowKeys, selectionListener via EL expr #{backingBeanScope.MyBean.model.xxx}
public CollectionModel getModel() {
return model;
Am I on the right track?
Edited by: Pricilla on May 4, 2010 2:20 PM -
Missing Templates in iphoto how to get them back?
I'm using Macbook Pro with OS X 10.7.2 , i have iphoto version 9.2.1 (628) , Now when i use email in iphoto and i want to use the templates so they are missing can someone help me how to get them back?
You'll need to reinstall iPhoto from the source it came from, i.e. the Software Install disk that came with your MBP or an iLife11 disk. If the MPB came with Lion install you'll have to download iPhoto from the App Store.
To reinstall iPhoto you'll have to delete the current application and all files with "iPhoto" in the file name with either a .PKG or .BOM extension that reside in the HD/Library/Receipts folder and from the /var/db/receipts/ folder,
Click to view full size
Then install iPhoto and apply any needed updaters.
I may be presching to the choir here but in Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
OT -
Web Dynpro ABAP: How to access the content of a mime object?
Hi everyone,
does anybody know how to access the content of a mime object of a Web Dynpro component? I added a XML file as mime object to a web dynpro component. Now I want to read the content of this xml file within a method of the component controller. The code would look something like:
DATA: xml_content type xstring.
xml_content = read_mime_object("test_123.xml").
Any ideas?
Regards,
Nilsdude here's the modification that i've done but I can't still access the content of the properties...
Mail mail = new Mail();
String message2 = sqlException.getMessage();
File file = new File("Add.properties");
Properties props = new Properties();
props.load(new FileInputStream(file));
String[] emailadd = {props.getProperty("emailadd","defaultValue")};
mail.postMail(emailadd,"An error has occurred, Auto-archive was unsuccessful.", message2,"[email protected]");
Message was edited by:
ryshi1264
Maybe you are looking for
-
Shift key appears to be stuck...
I just recently installed Snow Leopard on my MacBook Air, and I can no longer type numbers. It seems as if the Shift key is being pressed. Any advice?
-
Reports 3.0 - Drill Down Reports over the Web
Can anyone tell me how to code a button to run a drilldown report over the Web ? I have read about bookmarks, hyperlinks and hypertext and found the on-line documentation to be rather unclear. Thanks null
-
Trying to find a way to make Surface 2 usable as a thin client
We are looking for a low maintenance and low cost device that can employees can securely use to remote desktop to their work PCs from home. The only thing these users should be doing is logging in, getting connected to Internet, connect to VPN and t
-
Install/Uninstall problem... IE?
I'm having a problem upgrading my current version of the Flash player. I went to the live chat and they sent me here. I get thru all the "run" boxes, then a black/grey installation box comes up. Installation begins, then it tells me I need to close
-
Getting blank error messages for no apparent reason.
Firefox randomly freezes and the top bar says "Firefox (Not Responding)". This lasts for a little bit, then a blank error message pops up. It has no text anywhere, and the only thing I can do is x out. When I do, Firefox returns to normal. However, t