Customization Process of PI

Dear All,
There is a query regarding the Customization Process of PI, so
Please give me the customization process link or tutorial to configure it.
Thanks in Advance for The Valuable answers
with Rgard
Saurabh Sharma
SAP PP

Thanks Uday for the response.
Yes our system is 32 bit. Thanks for the link and I read the blog. However, I still have questions.
Does SAP Netweaver 7.0 SR3 runs on 64 bit only? The CDs that I have recieved doesn't say anything about 64Bit or 32Bit, so I am little bit confusted. Could you please let me know if I need 64Bit to install this? I would appreciate it.
Also, if they don't support 32 bit, then what is the need for the executables under directory IMJ_WINDOWS_I386?
Sorry, I am not a BASIS guy but certified in XI. Since we don't have BASIS person in our company, I have been asked by my management to do it reading books and so am depending on help from experts on this forum. So please excuse my foolish questions.
Thanks
Ram
Edited by: Prasad Ram on Sep 27, 2010 6:54 PM

Similar Messages

Third party customization process

pls send me third party customization process.
It's very urgent.
pls.....................................................

http://help.sap.com/saphelp_46c/helpdata/en/e6/4a6dc89e0311d189b70000e829fbbd/frameset.htm
THIRD PARTY SCENARIO
in third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. A sales order may consist partly or wholly of third-party items. Occasionally, you may need to let a vendor deliver items you would normally deliver yourself.
Process Flow
the processing of third-party orders is controlled via material types. Material types define whether a material is produced only internally can be ordered only from third-party vendors, or whether both are possible. For example, a material that is defined as a trading good can only be ordered from a third-party vendor. However, if you manufacture your own finished products, you may also want, from time to time, to be able to order the same type of product from other vendors.
Processing Third-Party Orders in Sales
Third-party items can be created automatically by the system, depending on how your system is set. However, you can also change a standard item to a third-party item during sales processing manually.
Automatic third-party order processing:-
if a material is always delivered from one or more third-party vendors, you can specify in the material master that the material is a third-party item. During subsequent sales order processing, the system automatically determines the appropriate item category for a third-party item: TAS. To specify a material as a third-party item, enter BANS in the Item category group field in the Sales 2 screen of the material master record.
Manual third-party order processing
In the case of a material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing. For a material that you normally deliver yourself, you specify the item category group NORM in the material master.
If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
If address data for the ship-to party is changed in the sales order in third-party business transactions, the changed data will automatically be passed on to purchase requisition and also to the purchase order ,if one already exists. In the purchase order, you can display the address data for the ship-to party in the attributes for the item.
You can only change the address data for the ship-to party in the sales order for third-party business transactions, and not in the purchase order.
Processing Third-Party Orders in Purchasing
when you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order
you process third-party items by creating a normal sales order. In overview for the order, you can then overwrite the default item category (TAN in the standard system) with the special item category for third-party items: TAS
Billing Third-Party Orders
If relevance for billing indicator for the item category has been set to B (relevant for order-related billing on the basis of the order quantity) in Customizing, the system includes the order in the billing due list immediately. If, however, the indicator has been set to F (relevant to order-related billing on the basis of the invoice quantity), the system does not include the order in the billing due list until an invoice from the vendor has been received and processed by the purchasing department. In the standard system, item category TAS (third-party order processing) has been given billing-relevance indicator F.
In the first case, the third-party order is considered to be completely billed only when the invoiced quantity equals the order quantity of the sales order item. In the second case, each time a vendor invoice is received, a customer invoice is created for the quantity in the vendor invoice and the order is considered to be fully invoiced until the next vendor invoice is received.
If you have activated billing-relevance indicator F for item categories in Customizing, billing can refer to the goods receipt quantity instead of the incoming invoice quantity.
You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing in Customizing for copying control for billing at item level.
FOR YOUR PROCESS Individual Purchase Orders WELL GIVE THE RIGHT SOLUTION
Individual purchase orders are used when your customer orders goods from you that are not in stock and must be ordered from one or more external vendors.
Process Flow
During sales order entry, the system automatically creates a purchase requisition item. The purchasing department creates a purchase order based on the requisition and the vendor ships the goods directly to you (unlike third party order processing, where the vendor ships directly to your customer). You then ship the goods to your customer. While the goods are part of your inventory, you manage them as part of the sales order stock. Sales order stock consists of stock that is assigned to specific sales orders and cannot be used for other purposes.
Process Flow for 3rd Party Sales
Customize the third party sales in summary:
Prerequisites for 3rd party sales,
Purchasing org,
purchasing group,
assign the Purchase org to company code
assign Purchase org to plant,
should not maintain the stock in material, it should be trading goods,
1. Create Vendor XK01
2. Create Material Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
7. Goods receipt MIGO
8. Goods issue
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing *--
SD - 3rd party sales order Create Sales Order
VA01
Order Type
Sales org, distr chnl, div
Enter
Sold to
PO #
Material
Quantity
Enter
Save
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
Order Number
Goto Item Overview
Item ->Schedule Item
SD - 3rd party sales order View the PR that is created
ME52N
Key in the PR number
Save
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
Key in the PR number
Toggle the "Assigned Purchase Requisition"
Execute
Check the box next to the material
Assign Automatically button
Click on "Assignments" button
Click on "Process assignment"
The "Process Assignment Create PO" box , enter
Drag the PR and drop in the shopping basket
Save
SD - 3rd party sales order Receive Goods
MIGO_GR
PO Number
DN Number
Batch tab , click on classification
Serial Numbers tab
Date of Production
Flag Item OK
Check, just in case
Post
Save
SD - 3rd party sales order Create Invoice
MIRO
Invoice Date
Look for the PO , state the vendor and the Material
Check the box
Click on "Copy"
Purchase Order Number (bottom half of the screen)
Amount
State the baseline date
Simulate & Post
Invoice Number
*Invoice blocked due to date variance
SD - 3rd party sales order Create a delivery order
VL01N
In the order screen , go to the menu Sales Document , select "Deliver"
Go to "picking" tab
State the qty and save
SD - 3rd party sales order Create a billing document
VF01
Ensure that the delivery document is correct in the
Enter
Go to edit -> Log
Save
rewards if it helps

,Retail Integration Customization Process/Guide/Techniques

How can i get the information on the Retail Customization techniques.As what ever the document available in the Oracle site mostly deals about the whole rib.
I just want some information/standard process or steps to customize the RIB (like RIB for RMS,SIM etc ) for different customers.
If some one could help it will be great.
Thanks in Advance,
Edited by: user11095621 on May 7, 2009 4:29 PM

Yes, I know the process that you describe.
The RIB did not fulfill our integration requirements on a few points:
- not all needed message types and/or details are being published.
(An Oracle Retail senior consultant said to me that if we were missing information in the RIB, we had to reconsider our integration requirements, as they where likely to be not a valid retail scenario...)
- it is a publish/subscribe mechanism (JMS), while we also need request/response type integration (RSL provides something like this but has quite a short list of services and is also focused quite on the Oracle Retail internal architecture).
- it is not an ESB
(Now when you also purchase the BI Publisher option to the Oracle Application server for the Oracle Retail operational report, you need the Enterprise Edition of the OAS to be allowed to buy that OAS BIP option, and the OAS-EE comes wth the Oracle ESB (at least before the BEA acquisition) - we chose however for a different ESB, Progress Sonic.
- the RIB message model (any source specific datamodel) is not a valid source for a true canonical data model, as the enterprise canonical encompasses more attributes and business objects.
- the level of documentation on customization can be improved
We do not consult the database directly, in the sense that we build a plsql package with some custom functions, e.g. f_get_season_for_item(i_item_nr), and wrap them with Java and OC4J as a SOAP webservice (using the JPublisher framework). See it like this, we wrapped the database in a custom integration layer, the ESB processes interact with that custom layer, and in case of upgrade of RMS, we need to re-fit the integration wrapper, limiting the impact of the upgrade to there (except for some bigger changes) and hopefully not impacting the ESB processes.
Of course this approach is also not ideal - but we wanted the RIB to stay vanilla and blackbox. But integration is not ideal ever - especially when for a message or service based integration architecture you need to rely on the messages and services that the application vendor has provided. Oracle Retail is the best in that respect, our other ERP/OLTP systems up to now do not do anything with SOAP/JMS.
Additionally we have a different messaging system that is the core of our enterprise integration (Progress Sonic MQ), and RIB is just one of the several sources/targets for that system. Other systems post to the Sonic MQ - that is our core integration bus. Where possible we post back to the RIB from our ESB processes.
We are also building more classical integration using Oracle Warehouse Builder and PLSQL to create flatfiles and create custom batches - directly accessing the RMS data model - there is just no other solution. (We have decided to ban custom Pro*C, and use PLSQL and OWB where needed - yes OWB also for non-ETL style processes - OWB has a great advantage over PLSQL: you generate code and you don't write code, and it comes with the database license.)
And then we also have to fill our RDW and Corporate Datawarehouse - but that's a whole other piece of cake.
PS: what is the ESB that you use?
Regards,
Erik

Customize Process Task notification

Our goal is to send a notification to group of users (members of a Role) when a Siebel Account is successfully created.
To accomplish this task we used the legacy feature of OIM to send notification by doing the following:
- create a custom Email Definition of Type = "Provisioning Related" using OIM Design Console - Process Management - Email Definition
- add the above Email Definition to the provisioning task using OIM Design Console - Process Management - Process Definition - Siebel Process - Tasks - Create User - Notification
This works as expected except the following issues:
1. the Email Definition contains more than one field of type Date that are shown in English format (e.g. June 8, 2012) we would like to parse date values in a different format (e.g 2012-06-08).
We have already tried to change the Email Definition attributes Language/Region from values "en/US" to "it/IT" but the notification stops to be sent until we rollback to original values "en/US"; is this a know bug or a miss configuration?
In any case, is the Language/Region related to the date format?
2. some attribute values in the Email Definition should be "transformed"
Any suggestion how solve the above issues?
As a workaround we coded a Java Plugin that sends email notifications (in this case we are able to write the email content as we want) and trigger this Plugin by an Event Handler but only for events related to the OIM User (CRETE/MODIFY/DELETE/etc..); we have no idea how trigger the same Plugin/Event Handler for the Siebel Account events. Is it possible? How?
Thanks and regards,
Gabriele.

To "trigger the notification task (new task) upon Sucess response code of Siebel create user task" you mean:
- create a Java Plugin with all the code needed to create and send the email notification?
- create an Adapter of type Process Task that triggers the above Java Plugin passing all the required variables?
- create a new Process Task that trigger the above Adapter and maps all the defined variables?
- finally, set the above Process Task as of the original Create User Process Task?
Is this correct? Did I miss some steps? Did you tried it?
Thanks,
Gabriele.

OAM customization error

I wanted to change the font colour of user manager application to red.To get this done i followed the instructions given in the document.the steps have been done in the process are as below.
2.5.1 Prerequisites to Customizing Styles
Be sure to complete the following prerequisites before you start to customize a style. This enables you to keep the original Classic Style (\style0) intact for reference and in case you need to return to it as a last resort.
To prepare to customize styles
As an Identity Administrator, add your own named style as described in the Oracle Access Manager Identity and Common Administration Guide.
The original style stays in effect until an Identity Administrator makes your style the new system default.
As an Identity Administrator, select the new style as the default style so that you can see the effect of any changes you make.
2.5.2 Customization Facts
Style Updates and Maintenance: Default wrapper files in \style0 and default global stylesheets in \shared are periodically updated to instantiate improvements through patches and product upgrades.
The Release Notes notify you when such updates occur so you can propagate the changes to your custom styles. Oracle recommends that you compare the new file with your custom file and propagate any changes to your custom styles. It is risky to overwrite a default style with a customized style that bears the same name.
Be sure to record the changes you make and the files that are involved so you can more quickly update custom stylesheets when you update default styles.
Custom Directory: Stylesheet customization should occur only within your custom directory. Customized stylesheets must reside in your custom directory and relative pointers in all files must point to the files in your custom directory, not to files in \shared.
Registration Files: As discussed in "General Content of Registration Files", a common registration file and each application's registration file contain the names of the stylesheets and schema files needed to present pages for the application. For example, when you look at the User Manager registration file in identity\oblix\apps\userservcenter\userservcenterreg.xml, you can see the application name and the names of the stylesheets the application calls during the completion of various functions.
Also, given the application and the program name, you can locate the corresponding schema file name in the application's registration file.
Oracle recommends that only experienced developers using extreme care consider editing a registration file. Registration files are covered in more detail at "Registration Files".
Pointers: All wrapper files and stylesheets contain pointers as include statements that call another file. Most of these pointers are relative pointers that indicate where within the directory structure the file is without providing an absolute path name.
For example, when you look at the usc_profile.xsl stylesheet called by User Manager functions, you can see that it contains include statements with relative pointers that call the following files:
./basic.xsl
./selectorinfo.xsl
./usc_searchform.xsl
./usc_navbar.xsl
When you change the location of a file (place a copy of a stylesheet in your custom directory for customization), pointers to this file (whether relative or absolute) must be changed to reflect the new location in every file that calls it. All relative pointers in a stylesheet should point to files in your custom directory.
In addition, many stylesheets contain relative pointers to object files. If Oracle Access Manager cannot instantiate an object when the page is loaded, unexpected behavior may result. All relative pointers to object files should be absolute pointers, as discussed in "Editing Stylesheets".
Wrapper Files: Wrapper files include pointers to actual stylesheets in \shared. However, you cannot be assured that a wrapper file is called before the stylesheet because both the common registration file and the application's own registration file call stylesheets according to an internal ordering. For this reason, all wrapper files in your custom directory must be overwritten by a copy of the corresponding default stylesheet from the \shared directory.
Important:
Customizing stylesheets is an iterative process. Attempting to copy the entire contents of \shared into your custom directory at one time produce an error.
Rather than copying all stylesheets at once, you start by investigating registration files to learn which functions (programs) call which stylesheets. You then selectively copy base stylesheets and a function-related stylesheet into your custom directory to overwrite their wrapper files, as discussed in "Copying Stylesheets to Your Custom Directory". You then customize and test the style for that function. When this returns satisfactory results you repeat the process to customize another function.
2.5.3 Customization Guidelines
The following guidelines should help ensure a successful customization.
Retain all original files in the \style0 and \shared directories in pristine condition and store them safely for future use. Also, make a backup copy of your customized style files so that patches won't disrupt your customization.
Record all changes you make and the files that are affected.
Customize and test your new styles in a non-production environment before migrating them to your production environment.
Important:
Oracle recommends that you do not modify original style files in the \shared or \style0 directories. These may be overwritten by patch updates and product upgrades or you may want to refer to them later.
When you use only one style, consider breaking the dependence on stylesheets in the \shared directory (again, to prevent patch\release updates to \style0 and \shared from disrupting customizations). This means that no stylesheet in your custom directory should inherit from or reference a stylesheet in \shared or \style0.
When you use multiple custom styles, consider the pros and cons of sharing customizations between multiple custom styles with implementing individual customizations for each custom style. For example:
Two styles that share the same stylesheet: When two custom styles (custom_style1 and custom_style2) can share the same stylesheet you may be tempted to customize the stylesheet in the \shared directory despite the risk of having your custom style overwritten by an updated stylesheet in a product patch or upgrade.
Two individual styles: When two custom styles (custom_style1 and custom_style2) require their individually customized stylesheets you use the standard methodology and overwrite the wrapper files in your custom directory with the corresponding stylesheets in \shared.
Consider using parameter stylesheet files for a custom style collection, rather than using hard-coded values (tab id's, attribute names, table/link properties, and so on); this is similar to how program code is written using header files.
2.5.4 Customization Methodology Checklist
As mentioned earlier, customization is an iterative process and more of an art than a science. This Guide does not attempt to give precise instructions for getting the presentation you want. Instead, this section outlines the recommended approach for a minor change.
Important:
Oracle recommends that you focus on stylesheets for one function at a time. Attempting to copy all stylesheets from \shared into your custom style directory results in an error.
Table 2-28 Customization Methodology Checklist
Check Action Description
Add a New Style
See the Oracle Access Manager Identity and Common Administration Guide for details about adding a style and selecting your new style as the default.
Choose a Function to Customize
Decide which function to customize first. Oracle recommends that you customize stylesheets related to one function at a time.
Copy Selected Stylesheets into Your Custom Directory
Copy selected stylesheets from \shared to your custom directory to overwrite corresponding wrapper stylesheets:
Base stylesheets
Stylesheets included in base stylesheets
A function-related stylesheet identified in application registration file
Function-related stylesheets identified in oblixbasereg.xml
Customize Stylesheets in Your Custom Directory
Change relative pointers in copied stylesheets to point to files in your custom directory.
Change relative pointers to objects to absolute pointers.
Complete other changes to implement the function's customization.
Record Your Work
Keep a record of the files you change and the changes you make.
Copy Your Custom Directory Structure to WebPass
Build a custom directory structure on WebPass and copy customized styles and images into it.
Note: On WebPass, stylesheets are used only for client-side processing and are not required for server-side processing.
Test Your Customized Style
Test the customized style and make any alterations you need to the stylesheets in your custom directory.
Record the changes.
Customize Another Function
Repeat this process on a function by function basis:
Choose a function.
Copy related stylesheets from \shared to your custom directory.
Customize pointers and styles.
Record and test your work.
Propagate the Customized Style
When you have copied and customized all stylesheets for the application, copy the custom style directory to all Identity Servers and WebPass hosts in your environment.
2.6 Customizing the Identity System Pages
This example shows a method for changing the way a page looks, without changing what it does. The change is a simple font color alteration for a specific page in one application. After making the change you must verify that the change is successful. When you finish this functional customization, you must create the same custom style directory structure on WebPass and copy all image files into it so WebPass can display the appropriate images in response to queries. You then test the implementation.
The following topics demonstrate one sequence in the "Customization Methodology Checklist". You can complete the following procedures to gain first-hand experience:
Task overview: Customizing Identity System pages includes
Completing Prerequisites
Choosing a Function to Customize
Copying Stylesheets to Your Custom Directory
Editing Stylesheets
Copying Images and Styles to WebPass
Testing Your Customized Style
Propagating Styles
See also:
For details about localizing messages, see "Localizing XSL Files".
2.6.1 Completing Prerequisites
A prerequisite to customizing a style is to add a style and select the new style as the default, as described in the Oracle Access Manager Identity and Common Administration Guide. The resulting files and file structure provide the foundation for your customization.
Suppose you added a new style named Pastel in a directory named Pastel and requested files be copied from Classic Style (in directory \style0).
To confirm the results of adding a new style
Add a style and select it as the default, as described in the Oracle Access Manager Identity and Common Administration Guide.
New Custom Directory: Oracle Access Manager creates a directory that duplicates \style0 for the default language, English. If you have installed a Language Pack for French, Oracle Access Manager also creates a directory that duplicates \style0 in the French language directory.
Locate your new custom directory.
For example:
Identity_install_dir \identity\oblix\lang\en-us\Pastel
Identity_install_dir \identity\oblix\lang\fr-fr\Pastel
Wrapper Stylesheets: Your custom directory contains wrapper stylesheets that point to actual stylesheets in another directory. If you selected the Classic Style to copy from, your custom directory duplicates the content of the \style0 directory.
Open a wrapper stylesheet in your new custom directory, basic.xsl, and review the files that it includes.
For this example:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\basic.xsl
<?xml version="1.0" ?>
- 
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
<xsl:include href="../../shared/basic.xsl" />
</xsl:stylesheet>
The basic.xsl wrapper stylesheet includes the following three files:
style.xsl file in your custom directory
msgctlg.xsl, one directory up from your custom directory (in identity\oblix\lang\en-us)
basic.xsl in identity\oblix\lang\shared
Locate and review the content of the basic.xsl stylesheet in \shared.
For example:
Identity_install_dir\identity\oblix\lang\shared\basic.xsl
<?xml version="1.0" ?>
- 
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="obstringutil.xsl" />
- 
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
The basic.xsl stylesheet in the \shared directory includes additional files (font.xsl, title.xsl, obstringutil.xsl) and provides templates to define attributes and status and control display information. See "basic.xsl" for more information.
During your customization process, you copy selected stylesheets from the \shared directory into your custom directory. This overwrites wrapper files with corresponding stylesheets you can then edit in your custom directory.
New Custom XML Document: In addition to the custom directory structure, when you select the new custom style as the default style, Oracle Access Manager creates an XML document (a duplicate of style0.xml) named after the directory you created.
Locate and open the custom xml document that was created when you added the new style.
For this example:
Identity_install_dir\identity\oblix\config\style\Pastel.xml
<?xml version="1.0" ?>
- <ParamsCtlg xmlns="http://www.oblix.com" CtlgName="style0">
- <ValNameList ListName="">
<NameValPair ParamName="styleReady" Value="TRUE" />
</ValNameList>
</ParamsCtlg>
This new file, stored with style0.xml, provides the status of your custom style and the location of the original style directory from which wrapper files were copied. For example, if your custom style directory is named Pastel and you copied from Classic Style, the Pastel.xml file is created when you select Pastel as the default style.
You do not need to edit this file. The original style0.xml remains unchanged. Also, there is a .lck version, Pastel.xml.lck, which is a lock file. No other new files are created when you add a new style.
Updated styles.xml: The styles.xml file is updated to include a new NameValPair that provides both the directory and style names you supplied when creating the style.
Locate and open the styles.xml file to confirm it was updated with your new style information.
For example:
Identity_install_dir\identity\oblix\config\style\styles.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
- <ValNameList xmlns="http://www.oblix.com" ListName="styles.xml">
<NameValPair ParamName="style0" Value="Classic Style" />
<NameValPair ParamName="Pastel" Value="Pastel" />
</ValNameList>
In this example, both the default Classic Style and new custom Pastel style are identified. You do not need to edit this file.
After confirming your custom directory structure, new and updated files, you are ready to choose a function and begin your customization.
2.6.2 Choosing a Function to Customize
The first step in the customization process is to choose a function to customize. For this example, suppose you want to change the font color to red on a specific page of the User Manager without changing anything else.
To identify the function and source information
Log in to the Identity System, as usual.
Navigate to the desired page.
For this example, click:
Identity System Console, User Manager, and then click My Identity
The page appears, as shown in Figure 2-6.
Figure 2-6 Customization Example: A User Manager Page Displays Red Text
The following information on each Identity System application page is useful for customizing styles:
Application Name: The application name, User Manager, appears on a highlighted tab in the top left area of the screen.
Each application's \bin directory contains the registration file that you need to identify functions. See "Registration Files".
Page Name: The page name, in this example it is My Profile, is the first page that you want to customize so you can see text in a red font color.
Registration File Path: The URL for each page includes a path to the application page, for example, identity\oblix\apps\userservcenter\bin\userservcenter.cgi. You can use this to locate the relevant registration file on the Identity Server.
Function Name: The URL for each page also includes a segment, program=view in this case, that you can use to locate the relevant stylesheet name for the function in the registration file.
Record the required information to assist you during the customization.
For this example:
Application: User Manager
Page: User Profile
Registration File Path: Identity_install_dir\identity\oblix\apps\userservcenter\bin\
Function: program=view
2.6.3 Copying Stylesheets to Your Custom Directory
Once you have identified the function you want to customize, your next task in any customization is to copy relevant stylesheets into your custom directory from the \shared directory. This activity overwrites wrapper files in your custom directory with copies of stylesheets you can customize. This also retains the original stylesheets in \shared as well as the original default wrappers in \style0.
Locating and copying relevant stylesheets is an iterative process in itself. In the following procedure you must locate and copy:
Base stylesheets
Stylesheets included in base stylesheets
The specific function-related stylesheet identified for the program in the application's registration file, in this case the stylesheet associated with program=view
Stylesheets included in the function-related stylesheet
Eventually your custom directory must contain all stylesheets, including those identified in the application's registration file and in oblixbasereg.xml. Even if you do not need to edit a stylesheet, it must be copied to your custom directory.
Important:
Copying stylesheets is an iterative process that must be done in a selective manner. Attempting to copy all stylesheets from \shared to you custom directory at one time results in an error.
To locate and copy relevant stylesheets
Copy the base stylesheets to your custom style directory from \shared to overwrite the default wrappers with stylesheets you can customize.
For example:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ basic.xsl, font.xsl, searchform.xsl, navbar.xsl, title.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\
This retains the original base stylesheets in \shared as well as the original default wrappers in \style0.
Open each base stylesheet in your custom style directory and locate include statements that point to other stylesheets you must copy, as well as any style information you need to customize.
For this example, see Table 2-29:
Table 2-29 Base Stylesheet Pointers and Items to Customize
Base Stylesheets in Custom Directory Pointers to Related Stylesheets and Items to Customize
basic.xsl
Contains implied relative include pointers to other stylesheets you need in your local custom directory:
<xsl:include href="obstringutil.xsl" />
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
Record the names of additional stylesheets you must copy into your custom directory from \shared. In this case, obstringutil.xsl.
font.xsl
Does not contain include pointers to other files.
Does contain color information you can customize:
<xsl:variable name="subHeadingColor">#006699...
<xsl:variable name="contentTitleColor">#000000...
<xsl:variable name="contentTextColor">#000000...
searchform.xsl
Does not contain include pointers to other files.
Does not contain color information to customize. No changes needed to this stylesheet in your custom directory.
navbar.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later.
title.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later. No changes needed to this stylesheet in your custom directory.
Copy stylesheets included in base stylesheets to your custom directory from \shared.
For this example, obstringutil.xsl:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ obstringutil.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\obstringutil.xsl
Record the stylesheets you have copied from \shared to your custom directory so you can track your work.
Locate the required registration files.
For this example, oblixbasereg.xml and userservcenterreg.xml:
Identity_install_dir\identity\oblix\apps\common\bin\oblixbasereg.xml Identity_install_dir\identity\oblix\apps\userservcenter\bin\ userservcenterreg.xml
At some point, you typically need stylesheets included in the common registration file oblixbasereg.xml. However, stylesheets included in oblixbasereg.xml are not needed for this example.
For this example, you must locate only the function-related stylesheet in the userservcenterreg.xml file.
Open the application's registration file and locate the function-related stylesheet you need.
For this example, locate ObProgram name="view":
<?xml version="1.0" ?>
- <ObProgramRegistry>
- <ObApplication name="userservcenter">
- <ObProgram name="front">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="commonNavbar">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="view">
<ObStyleSheet name="usc_profile.xsl" />
<ObButton name="initiateDeactivateUser" />
- 
<ObButton name="userreactivate" />
<ObButton name="wfTicketDelete" />
<ObButton name="userModify" />
<ObSchema name="usc_profile.xsd" />
</ObProgram>
You can see in the registration file that the usc_profile.xsl stylesheet is associated with the function you want to customize (ObProgram name="view"). The usc_profile.xsl stylesheet is also associated with a number of other functions.
Copy the function-related stylesheet, usc_profile.xsl, to your custom style directory from \shared and record the stylesheet name.
For this example:
Copy From: Identity_install_dir\identity\oblix\lang\en-us\shared\ usc_profile.xsl
Copy To: Identity_install_dir\identity\oblix\lang\en-us\Pastel\ usc_profile.xsl
Open the function-related stylesheet and locate include statements that point to other stylesheets you must copy, record any information you plan to customize.
For this example, usc_profile.xsl:
Table 2-30 usc_profile.xsl Pointers and Items to Customize
usc_profile.xsl in Custom Directory Pointers to Related Stylesheets and Items to Customize
usc_profile.xsl
This main stylesheet for the User Manager includes stylesheets that must be copied to your custom directory:
<xsl:include href="./basic.xsl" />
<xsl:include href="./selectorinfo.xsl" />
<xsl:include href="./usc_searchform.xsl" />
<xsl:include href="./usc_navbar.xsl" />
Note: selectorinfo.xsl, usc_searchform.xsl and usc_navbar.xsl should be copied.
Also record pointers to objects that should be customized:
<object id="cenroll" classid= ...
codebase="../../common/bin/xenroll.cab" />
and
<script src="../../common/bin/installCert.vbx" ...
Repeat steps to copy relevant stylesheets, then record their names and details you plan to change.
For this example:
Copy From:
Identity_install_dir\identity\oblix\lang\en-us\shared\selectorinfo.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_searchform.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_navbar.xsl
Copy To:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\selectorinfo.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_searchform.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_navbar.xsl
These stylesheets do not contain include statements, other stylesheet names, nor parameters you need to change.
You have collected, copied, and recorded relevant stylesheets for this example.
2.6.4 Editing Stylesheets
After copying relevant stylesheets, you may need to edit them. As described in Table 2-29 the information that needs to be customized for this example includes:
Font colors defined in the base stylesheet font.xsl should be changed to red.
Pointers to objects defined in usc_profile.xsl should change from a relative path to an absolute path.
Note:
To help streamline development and testing, consider implementing XSL stylesheet control parameters. See "Caching Considerations".
To edit stylesheets for a simple font color change
Open the font.xsl stylesheet in your custom directory in a text editor.
For example,
Identity_install_dir\identity\oblix\lang\en-us\Pastel\ font.xsl
Edit the stylesheet to change all colors from the default color to red (FF0000), then save the change.
For example,
Change all Default Font Colors From:
... <xsl:variable name="pageHeaderColor">#006699</xsl:variable>
<xsl:variable name="subHeadingColor">#006699</xsl:variable>
<xsl:variable name="contentTitleColor">#000000</xsl:variable>
<xsl:variable name="contentTextColor">#000000</xsl:variable>
and others ...
To Red (#FF0000):
... <xsl:variable name="pageHeaderColor">#FF0000</xsl:variable>
<xsl:variable name="subHeadingColor">#FF0000</xsl:variable>
<xsl:variable name="contentTitleColor">#FF0000</xsl:variable>
<xsl:variable name="contentTextColor">#FF0000</xsl:variable>
and others ...
Record your changes to this file.
If you restarted the Identity Server now you would not yet see your changes. This is because you have not yet customized the function-related stylesheet that identifies where to apply the changes.
Edit the basic.xsl stylesheet in your custom directory as follows to add required include statements that were in the original basic.xml (but were lost when you copied over the basic.xsl from the shared folder).
Locate the line containing the following:
<xsl:include href="obstringutil.xsl"/>
Add the following information so that it precedes the line identified in a):
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
Edit the usc_profile.xsl stylesheet in your custom directory to change the relative path to objects, as shown in the following, then save the changes.
For example:
Change From a Relative Path:
- <head>
...<object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="../../common/bin/xenroll.cab" />
... <script src="../../common/bin/installCert.vbx" language="VBScript" />
</head>
Change To an Absolute Path:
- <head>
... <object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="/identity/oblix/apps/common/bin/xenroll.cab" />
... <script src="/identity/oblix/apps/common/bin/installCert.vbx" language="VBScript" />
</head>
This concludes the specific function-related change for this example.
Ensure that file system access control for new custom style directories and files is set to match the ownership and permissions of \style0.
Restart the Identity Server.
If you log in to the Identity System now and view the My Identity page, you see the red font color. However, the images supplied by WebPass won't appear until they are included in a corresponding custom style directory structure on the WebPass host.
After doing this i checked user manager application then iam being displayed the following error page.
style shhet error report form.
an error has occured while executing the application.
your browser does not support sending email automatically.
please send email to <a=" "><\a> with the following information.
you name
email adress
make sure to append the trace back in the mail
in the log file errors have been given as below
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl
"Failed to compile XSL file."     XSL file:^../../../lang/en-us/pastel2/usc_profile.xsl
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl
"OIS_LOG_PASSED_ERROR"     Error^writer\obhtmlpage.cpp:276: Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl

Hi Matt,
I think the page you are being redirected to is servererror.jsp, which is deployed within oam-server.ear, within its own ngsso-web.war application. You could deploy your own version of this. I assume you could also modify the ErrorPage setting in oam-config.xml to define your own page, though I have not tested this. This would be a customisation, so you would be responsible for the system behaviour when doing this.
Regards,
Colin

Automatic confirmation in process order

Hello everybody.
I need made automatic confirmation to some phases in process order, I hade read that this is possible using process messages.
Process management supports the direct confirmation from the PI sheet and process control system to the process order by sending process messages to predefined message destinations.
Someone know what are the steps I need to follow to customize process message?
What are the transactions that I need to use?
In some documentation say that for access process management, I need proceed as follows:
From the main R/3 menu, select the menu options Logistics u2192 Production - process u2192 Process management.
The system branches to the initial process management menu. From here, you can access all the application functions of process management.
But when I access that path there is not any transaction for use process management.
Something is missing for install or what is the transaction that I need use?
Thanks in advance.

Hi,
You can do that in T Code CORW.
For the required production scheduler select the batch creation for process order.
Also in the Assignment tab of the process order, there is a field for batch, next to it there is a Create button. Click that, you will get the batch number in that field.
Hope that helps.
Regards,
Rohit.
Added: I apologise, its not the Assignment tab in process order. It is Goods Receipt tab.
Edited by: Rohit Chauhan on Aug 3, 2009 9:42 AM

Can't add pin it button or amazon button and can't exit customization

I cannot add the pin it button or the amazon button through customization. I also have a problem with the whole customization process. I cannot exit. I have a little screen thing on customization that when I tried to open was in Japanese and really afraid of what it could have done to my computer. Here is the screen shot of it on customization.

You can try to click the Restore Defaults button in the Customize palette.
You can check for problems with preferences.
Delete a possible user.js file and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.
*http://kb.mozillazine.org/Preferences_not_saved
*http://kb.mozillazine.org/Resetting_preferences

BOS customization

HI,
According to client business (Construction & Service industry) process Contract creation ,then Actual service Entry & with reference to Sales order creation.
So please give me the customization process of Sales order creation with reference to Service entry sheet (BOS process)
Thanks,
Miku.

go to Logistics general-- Tax on goods movementIndiaBasic settings --- Maintian series group ( See if you have maintaines S2 here)
And then Assigned the same in
Tax on goods movementIndiaBusiness Transactions --- Outgoing Excise Invoice -- Maintian Default Excise and series Group for your Sale area
Cheers

ALE Process code

HI friends.....
1.if we create partner profile we need two systems or not
2. where these partner profile are stored(this means outbound partner profile table)
3. will we create process code both inbound and outbound?
4. will we create customize process code?
Stand alone program need to create process code
5. how to create the process code?
please tel me...
thanks & regards
mani

Hi,
1.if we create partner profile we need two systems or not?
    Ans. Yes we need two systems.
2. where these partner profile are stored(this means outbound partner profile table)
   TMSG1 Logical Messages and Process Codes in Outb. Procg
   TMSG2 Logical Messages and Process Codes in Inb. Procg
3. will we create process code both inbound and outbound?
     Process code is nothing but to identify the FM or Standalone program to
    create or process the idocs.
    So to create Idoc we need one program which is assigned to a FM or Program.
   and to process Idoc we need one program which is assigned to a FM or
   Program.
4. will we create customize process code? Yes
   Stand alone program need to create process code --Yes
5. how to create the process code?
    tcode WE41 --Outbound process code
             WE42---Inbound Process code
Click on new entries.
Don't forget to reward if useful

HCM Process and Forms

Hi All,
Using transaction HRASR_DT, I have created a Form Scenario, Adobe Form, workflow and Process.
How do I assign this process to EP?
Regards,
Ramya

Hi Ganga,
Could you please elaborate what you said. I'm totally new to ESS and MSS. Currently in my project, there's a scenario where a HCM form needs to be designed and implemented from scratch. Now how exactly does this affect the portal? As in what customization needs to be done? Is it all in ABAP webdynpro? As far as i know in EhP4 all HCM forms are embedded in abap webdynpro or something like that? but if i have to show this on the portal in an MSS iview, how do i do it and how do i define the customization process? Would be very helpful if I get your inputs.
Thanks & Regards,
Vaishnavi

Change Number and Process Route

Hi Experts,
I have seen in the Change Master Web-UI is a register for Process Route.
When I'm trying to create a Process Route, the Activities are missing.
Where is the customizing to set Process Route Activities for the Change Master?
And where is the customizing to create the event to start the Process Route?
I have allready done some customizing for the SAP Case Management and the Engineering Record.
I hope you can help me.
Regards,
Thomas

To customize process route to the change number in the Web-UI the following steps has to be done:
Create Activities
To create activities use TA SRMCUSTOMIZING: Records Management --> Customizing for Process Route --> Create or Change Activities and Activity Functions
Create new entries depending on ECN_DIS
Define Activities for GOS-Objects
To define activities for GOS-Objects use TA SPRO: SAP Customizing Implementation Guide --> Logistics - General --> Product Lifecycle Management (PLM) --> PLM Web User Interface --> Objects in PLM Web UI --> Process Route --> Define Activities for GOS Objects for Process Routes
Create new entries depending on the activities created before and for the Object Type PLM_ECN
Check Agent Assignment for all created Standard Tasks
Now it is prossilbe to add steps to the process route to a change number.
To start the workflow the following steps has to be done:
Define Type Linkages for Workflow
TA SWETYPV - Type linkages:
Create an entry if not existing
Object Category: CL
Object Type: /PLMB/CL_PROCESS_ROUTING_WF_BO
Event: START_WORKFLOW
Receiver Type: WS00100012
Receicer Function Module: SWW_WI_CREATE_VIA_EVENT_IBF
Linkage Activated: X
Behavior Upon Error Feedback: 3 - Do not change linkage
Define Instance Linkages for Workflow
TA SWEINST - Instance linkages:
Create an entry if not existing
Object Category: CL
Object Type: /PLMB/CL_PROCESS_ROUTING_WF_BO
Event: STOP_WORKFLOW
Receiver Type: WS00100012
Receicer Function Module: SWW_WI_COMP_EVENT_RECEIVE_IBF
Linkage Activated: X
Behavior Upon Error Feedback: 3 - Do not change linkage
Thanks for your help
Regards,
Thomas

Page customization for end user

is it possible to use other mechanism for end users to customize their own pages instead using the portal features since it's a little complicated cause each user needs to create new pages, add portlet, etc.
Can we use the mechanism like my cnn, my yahoo,excite and how to do that in a simple way?
thanks for helping

Hi,
I have the same question, but I would like to have a seperate page or application, showing only predetermined portlets, for users to choose from and place on their page. I do not want the end user to ever see the customization process Oracle uses. Can this be done???
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Karthika Siva ([email protected]):
A simple way to do this:
1. Create a page that will become the default page for end users. This page will have your branded look & feel (style) and contain a default set of portlets. These are portlets that you think your typical user will find useful.
2. Create portal user.
3. Grant one of the following privileges on the page to the user. Grant 'Full Customization' or 'Add Only Customization' depending on how much control you want to give the end user. Keep in mind that both of these privileges allow the end user to only customize their PRIVATE VERSION of the page. Others will see the default, or their own version if they have also personalized it. See the online help on the Access tab of the Customize Page screen for a description of the privileges.
4. Once that is done, set this page as the default home page for the user. You can do this using the Preferences tab on the edit user screen.
Now the portal user can log into the portal, and personalize his/her page by customizing portlets on the page, hiding/showing default portlets, and even adding other portlets to the page.<HR></BLOCKQUOTE>
null

Personal customizations , i.e. a new tab button, reset upon the closing of the window

further explanation of customizations: the buttons i may add or remove from a toolbar like copy, print, new tab, or home, will reset after closing firefox

Although the + appears at the far right end of the tab bar during the Customize process, it should snug up to the tabs once you click Done. Is your staying at the end??
(When you drop it any closer to the existing tabs, it goes all the way to the beginning of the bar, which for a right-handed person, is not convenient.)

Rule set customization Document

Hi ,
Can someone please help me to locate " GRC Access Control Effective Rule Set Design document " on SDN or on Google .
I have been searching for this documnet for some time , however couldnt locate this . This document was referenced in some earlier forum questions as well.
I am working for a rule set customization documnet for my client and would like to refer this document . Would also appreciate if someone can help me or guide me here to what all contents i can include in this document. As per the requirement , this has to be a high level document that explains the rule set customization process. Any refrence links or procedure here would be a great help for me to start with .
Thanks everyone for your valuable time.
Thanks guys ... Vikas

[http://download.oracle.com/docs/cd/B28359_01/server.111/b28321/strms_rules.htm#i1006137]

Hr_approval_custom customization

Hi,
I need help with the workflow customization process.
I have customized the hr_approval_custom.get_routing_details1() function. I have also bounced the apache server after comiling and committing the changes
After the workflow process is run the notifier is not being set.
In the workflow details the workflow attributes
Approval Routing ID1
Approval Routing Username1 do not have any value set.
Thank you in advance for your help.
Thanks & Regards,
Supriya
Edited by: [email protected] on Apr 21, 2009 6:43 AM

Hi , I have enhanced 0HR_PY_1. What question do you have?
Best Regards,
Brindha.

Customization Process of PI

Similar Messages

Maybe you are looking for