What is the use of version attribute in jnlp tag??

Hello,
I want to know what is the use of version attribute in jnlp tag.
For ex:
<jnlp spec="6.0+" codebase="$$codebase" href="$$name" version="1.1">
</jnlp>
In the spec it explains:
In the Jnlp tag:
version = The version of the application being launched, as well as the version of the JNLP file itself.
1. Is this version attribute would work as version attribute in jar tag. Ex: <jar href="application.jar" version="1.1"/> ?
i.e. can we specify different jnlp's with the same name as we do for jar's with the help of version.xml.
Any help is greatly appreciated.
//Anjali

Hi Reddy,
If one Info Object depends on another info object we will make that dependent info object as a compounding attribute of main Info object.
Eg: Storage Location – Plant
In above eg there is no meaning of Storage Location without Plant. So, we will make storage location as compounding attribute of Plant.
Regards,
Sreehari.

Similar Messages

What is the use of version in workflow

what is the use of versioning in workflow. how can i use it in real time senarios.

Hi,
Its the same way as in reports and other areas. You can generate a current version and keep making changes to the latest version so that you can always revert back to the older one in case of problems.
It is also used when you transport the workflow from one system to other. Assume you have already transported a workflow definition to the production system. Now this workflow also has been instantiated and some instances are running in production. Now if you make some modifications in this workflow and transport (even with the same version number) it will get transported to the production under a new available version number. The previous instances of the workflow (in production) will continue to run referring to the older version available and any new instances will continue with the latest transported workflow definition.
Thanks,
Prasath N

What is the use of checking Attribute Only in IO?

Hi,
Can some one explain what is the use of checking Attribute Only in IO?
I couldn't find the right answer in the forums.
Thanks,
Sam

'Attributes only ' won't create any Extra Tables.
If you Create Attributes only, you can't use this IO as Charecterstic or Navigation Attribute to other IO.
You can only use this As Display Attribute.
Assume, Customer Phone No. You don't want to provide Navigation with this. As well as you need only Latest Value. You don't want history of Customer Phone Numbers.
You need to Create Customer Phone no with 'Attributes only' and Assign this to Customer IO. You can't navigate with Phone No in Queries.
Nagesh Ganisetti.
Assign points if it helps.

What's the use for "name" attribute?

Almost every object has a "name" attribute and "display name" attribute, e.g. page, tab, template.
What is the exact use of the name attribute. For my understanding, one of its use to is contruct a URL for the object. For example, when I want to add one item to a page, the shows me the path to the page is:
PAGE / HELLO_PAGE_GROUP / HELLO_PAGE / TAB37465 / TAB37469 /
TAB37465 is the name of the tab attribute. I realized this and went to change the name of the tab to a more meaningful value. However, when I try to add the item, the page Path did not change. Is this a oracle internal bug?
I have similar problem with navigation page. I published a navigation page as portlet. I changed the name of the navigation page and use the name as the portlet name, the new name of the portlet can not be reflected in the portlet repository.

Jerry,
1. I tried to add an item to the page within the tab. On the "add item" page, it shows me the path to the current page. Ok, Let's forget about "item", and just talk about the path to a tabbed page. The path/URL never changes, even after I change the tab "name" attribute.
2. I am talking about the name of the portlet within portlet repository. Let's see within page group A, I created navigation page with name of "test". I published the page as a portlet. In the portlet repository, I can see a new portlet "test" under "new/A". I changed navigation page name from "test" to be "B", however, the portlet name never changed in the portlet repository. It's always "test".

The use of id attribute in html tags

Hi
I use http://java.sun.com/jsf/html as follows:
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<h:form id="myid">
<h:panelGrid id="mypanelgrid" columns="1">
</h:panelGrid>
</ht:form>When I don't use the id attribute with the UI components, the components are not displayed.
I would like to confirm that id attribute is MUST in jsf.
Your kind response is appreciated.
Thanks
Murthy

Actually I see an exception thrown on Windows XP
10:24:45,717 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute
        at org.apache.catalina.session.StandardSession.setAttribute(StandardSess
ion.java:1233)
        at org.apache.catalina.session.StandardSessionFacade.setAttribute(Standa
rdSessionFacade.java:129)
        at com.sun.faces.context.SessionMap.put(ExternalContextImpl.java:556)
        at com.sun.faces.application.StateManagerImpl.saveSerializedView(StateMa
nagerImpl.java:88)
        at net.sourceforge.myfaces.taglib.core.ViewTag.doEndTag(ViewTag.java:138
        at org.apache.jsp.pages.template.TemplateRightPane_jsp._jspx_meth_f
_view_0(org.apache.jsp.pages.template.TemplateRightPane_jsp:246)
        at org.apache.jsp.pages.template.TemplateRightPane_jsp._jspService(
org.apache.jsp.pages.template.TemplateRightPane_jsp:121)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:322)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3
14)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:672)
        at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica
tionDispatcher.java:463)
        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD
ispatcher.java:398)
        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis
patcher.java:301)
        at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImp
l.java:322)
        at net.sourceforge.myfaces.application.jsp.JspTilesViewHandlerImpl.rende
rView(JspTilesViewHandlerImpl.java:178)
        at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha
se.java:87)
        at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
        at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at com.xyz.framework.security.authorization.AuthorizationFilter.doFilter
(Unknown Source)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:81)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrinc
ipalValve.java:39)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:153)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:59)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:856)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:744)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
kerThread.java:112)
        at java.lang.Thread.run(Unknown Source)
10:24:45,748 INFO [STDOUT] org.apache.jasper.JasperException: setAttribute: Non
-serializable attribute
10:24:45,748 INFO [STDOUT]     at org.apache.jasper.servlet.JspServletWrapper.s
ervice(JspServletWrapper.java:370)
10:24:45,748 INFO [STDOUT]     at org.apache.jasper.servlet.JspServlet.serviceJ
spFile(JspServlet.java:314)
10:24:45,748 INFO [STDOUT]     at org.apache.jasper.servlet.JspServlet.service(
JspServlet.java:264)
10:24:45,748 INFO [STDOUT]     at javax.servlet.http.HttpServlet.service(HttpSe
rvlet.java:810)
10:24:45,748 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.internalDoFilter(ApplicationFilterChain.java:252)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.doFilter(ApplicationFilterChain.java:173)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationDispatche
r.invoke(ApplicationDispatcher.java:672)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationDispatche
r.processRequest(ApplicationDispatcher.java:463)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationDispatche
r.doForward(ApplicationDispatcher.java:398)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationDispatche
r.forward(ApplicationDispatcher.java:301)
10:24:45,764 INFO [STDOUT]     at com.sun.faces.context.ExternalContextImpl.dis
patch(ExternalContextImpl.java:322)
10:24:45,764 INFO [STDOUT]     at net.sourceforge.myfaces.application.jsp.JspTi
lesViewHandlerImpl.renderView(JspTilesViewHandlerImpl.java:178)
10:24:45,764 INFO [STDOUT]     at com.sun.faces.lifecycle.RenderResponsePhase.e
xecute(RenderResponsePhase.java:87)
10:24:45,764 INFO [STDOUT]     at com.sun.faces.lifecycle.LifecycleImpl.phase(L
ifecycleImpl.java:200)
10:24:45,764 INFO [STDOUT]     at com.sun.faces.lifecycle.LifecycleImpl.render(
LifecycleImpl.java:117)
10:24:45,764 INFO [STDOUT]     at javax.faces.webapp.FacesServlet.service(Faces
Servlet.java:198)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.internalDoFilter(ApplicationFilterChain.java:252)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.doFilter(ApplicationFilterChain.java:173)
10:24:45,764 INFO [STDOUT]     at com.xyz.framework.security.authorization.Auth
orizationFilter.doFilter(Unknown Source)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.internalDoFilter(ApplicationFilterChain.java:202)
10:24:45,764 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.doFilter(ApplicationFilterChain.java:173)
10:24:45,764 INFO [STDOUT]     at org.jboss.web.tomcat.filters.ReplyHeaderFilte
r.doFilter(ReplyHeaderFilter.java:81)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.internalDoFilter(ApplicationFilterChain.java:202)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.ApplicationFilterCha
in.doFilter(ApplicationFilterChain.java:173)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.StandardWrapperValve
.invoke(StandardWrapperValve.java:213)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.StandardContextValve
.invoke(StandardContextValve.java:178)
10:24:45,779 INFO [STDOUT]     at org.jboss.web.tomcat.security.CustomPrincipal
Valve.invoke(CustomPrincipalValve.java:39)
10:24:45,779 INFO [STDOUT]     at org.jboss.web.tomcat.security.SecurityAssocia
tionValve.invoke(SecurityAssociationValve.java:153)
10:24:45,779 INFO [STDOUT]     at org.jboss.web.tomcat.security.JaccContextValv
e.invoke(JaccContextValve.java:59)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.StandardHostValve.in
voke(StandardHostValve.java:126)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.valves.ErrorReportValve.i
nvoke(ErrorReportValve.java:105)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.core.StandardEngineValve.
invoke(StandardEngineValve.java:107)
10:24:45,779 INFO [STDOUT]     at org.apache.catalina.connector.CoyoteAdapter.s
ervice(CoyoteAdapter.java:148)
10:24:45,779 INFO [STDOUT]     at org.apache.coyote.http11.Http11Processor.proc
ess(Http11Processor.java:856)
10:24:45,779 INFO [STDOUT]     at org.apache.coyote.http11.Http11Protocol$Http1
1ConnectionHandler.processConnection(Http11Protocol.java:744)
10:24:45,779 INFO [STDOUT]     at org.apache.tomcat.util.net.PoolTcpEndpoint.pr
ocessSocket(PoolTcpEndpoint.java:527)
10:24:45,779 INFO [STDOUT]     at org.apache.tomcat.util.net.MasterSlaveWorkerT
hread.run(MasterSlaveWorkerThread.java:112)
10:24:45,779 INFO [STDOUT]     at java.lang.Thread.run(Unknown Source)
10:24:45,779 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet
threw exception
java.lang.IllegalStateException
        at org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFac
ade.java:423)
        at com.xyz.framework.security.authorization.AuthorizationFilter.doFilter
(Unknown Source)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:81)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrinc
ipalValve.java:39)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:153)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:59)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:856)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:744)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoI'd appreciate your kind help.
Thanks
Murthy

What is the most advanced version of ACR that can be used with Photoshop CS5?

What is the most advanced version of ACR that can be used with Photoshop CS5?
Will it open RAW files from a Canon 5D Mark III ?

CS5 can use up to ACR 6.7.1. CS6 started with ACR 7.0.
The 5D Mark III was first supported with ACR 6.7.
ACR 6.7.1 can be downloaded from the Camera Raw Mac and Win links on the Adobe Download page:
http://www.adobe.com/downloads/updates.html
References:
http://helpx.adobe.com/x-productkb/global/camera-raw-compatible-applications.html
http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html

I have a mac powerbook g4 power pc processor, OS 10.5.8. what is the most current version of firefox i can use? i currently have 2.0.0.9 and am unable to auto or manual update

i have a mac powerbook g4 power pc processor, OS 10.5.8. what is the most current version of firefox i can use? i currently have 2.0.0.9 and am unable to auto or manual update edit

It was in the release notes for version 4 IIRC

What are the frequencies all versions of the iPhone 6 and what are they used for (e.g. GSM, 3G, LTE, WIFI, Bluetooth,etc...) provided with channel numbers per frequency

what are the frequencies all versions of the iPhone 6 and what are they used for (e.g. GSM, 3G, LTE, WIFI, Bluetooth,etc...) provided with channel numbers per frequency.

Click here

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT GIVE DETAILS

Hi,
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡        the match indicator is not set and
¡        the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
                            a.      Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                            b.      Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
When referring to InfoObjects it is important to differentiate between:
§         Characteristics
§         Time characteristics
§         Key figures and
§         Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        Texts
·        Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
·        Attribute only (flag)
·        Short and long text (description)
·        Time dependency of attributes
·        Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
·        Compounding
New InfoObjects are included in compounding
·        Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
·        Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
·        Application components
If the entry for the active version is initial, the delivery version is used.
·        BEx display
·        Characteristic constants
·        Default member
·        Authorizations (flag and field)
·        Selection (CHASEL)
·        InfoObject is document attribute
·        Data type
·        Length
·        Output length
·        Conversion routines
·        Lower case allowed (flag)
·        Contains master data (flag)
·        Master data is authorization relevant (flag)
·        Export DataSource (Flag)
·        F4 query design
·        F4 query runtime
·        Check ODS object
·        Contains text tables (flag)
·        Texts are language-dependent (flag)
·        Short, medium and long texts exist (each with flag)
·        Default currency
·        GIS attribute
·        Hierarchies exist (flag)
Valid for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
·        Type of key figure
·        Fixed unit
·        Fixed currency
·        Aggregation
·        Exception aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
¡        MultiProviders
¡        InfoCubes
¡        ODS Objects and
¡        InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
·        New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
·        Active Version Available
In this column, the following display options are available:
¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active the object has to be postprocessed. You find notes on postprocessing in the activation log.
Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
¡        No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in background
The selected objects are installed in the background.
Install and transport
The selected objects are installed immediately and then written to a transport request.
SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
Refer
Business Content (Versions)
http://help.sap.com/saphelp_nw04/helpdata/en/c1/ea683cc5e8ca68e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
Thanks,
JituK

What are the SQL server versions those are compatible with XI 3.0.

Hi All,
Please suggest,
what are the SQL server versions those are compatible with XI 3.0.
or with which SQL server versions XI 3.0 will interact using JDBC Adapter.

Check in the [Product Availability Matrix |https://websmp201.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000192]in market place for more information on this
Thanks
SaNv...

What is the use of access level

Hi Experts,
What is the access level and what is use of each option in access level
1 Application
2 Superior component
3. Top Component
4. Sap
5. Global
and in Details section what is the use Properties tab
1. Application Component
2. Software Component
3. Development Package
4. Settings Class
Please explain Each option use.
Thank you in advance,
Srini M.

Hi Srini,
just read the documentation (although the current status on SAP Help Portal isn't really up-to-date):
1. [Entry point|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cc/85414842c8470bb19b53038c4b5259/frameset.htm]
2. [Setting an Access Level|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/32/6aba9c49fd41a5a14f710e121220f1/content.htm]
W/r to "Application Component" etc., docu on Help Portal is definitely not sufficient. Here, the following applies:
An application offers attributes for the application component and the software component. The application component and software component have to be the same as defined for the development package. Application and software component are automatically derived from the development package if they are not set explicitly.
For the definition of the development package, application component, and software component, we recommend that you choose the same values that are in effect for the software solution that you want to enhance by a new BRFplus application. This simplifies all activities related to the software infrastructure, especially transports.
CU
Claus

What is the use of initial value in a database table?

Hi can anyone help me in knowing what is the use of initial value which is present besides primary key while creating a table?

Initial Value:
Indicator that NOT NULL is forced for this field
Use
Select this flag if a field to be inserted in the database is to be filled with initial values. The initial value used depends on the data type of the field.
Please note that fields in the database for which the this flag is not set can also be filled with initial values.
When you create a table, all fields of the table can be defined as NOT NULL and filled with an initial value. The same applies when converting the table. Only when new fields are added or inserted, are these filled with initial values. An exception is key fields. These are always filled automatically with initial values.
Restrictions and notes:
The initial value cannot be set for fields of data types LCHR, LRAW, and RAW. If the field length is greater than 32, the initial flag cannot be set for fields of data type NUMC.
If a new field is inserted in the table and the initial flag is set, the complete table is scanned on activation and an UPDATE is made to the new field. This can be very time-consuming.
If the initial flag is set for an included structure, this means that the attributes from the structure are transferred. That is, exactly those fields which are marked as initial in the definition have this attribute in the table as well.
hope it helps,
Saipriya

What is the use of properites file

what is the use of properites file

Hi there
Usally a program has some variables that the user can set.
These variables are then saved in a file.
The Property class can read these files and search for special keys in that file for example
Lets say that the program that you have developed
can change its background color.
the user sets the color to pink
and the program stores the valu in the property file.
then the property file entry could look like this
color = pink
On windows systems this is verry much like the ini files if you are familiar with these. (I think allmost any OS has something similair)
In JDK 1.4 there is a new system for dealing with property files. This new class is storing the attributes directly to the register on the os
/Markus

What is the use of transaction code FAGLGA15

What is the use of transaction code FAGLGA15.What is its functionality.Please help.

Hello,
Yes, you are right. Before ECC 6.0 version the TC: KSU5 has been used for actual assessment. Now in ECC 6.0 the same transaction code has been changed to FAGLGA15. You can execute the actual assessment in test run and if it is ok then run in background.
Thanks
Para

What is the use of version attribute in jnlp tag??

Similar Messages

Maybe you are looking for