Difference between Body pages and Master Pages in Adobe forms?

Hi SAP Gurus,
Please can any one tell me the difference between the Body pages and Master Pages in Adobe Forms?
In what scenarios we use Body pages and Master pages?
And also please tell me what is Boiler plates? When these used?
Thanks and Regards
Abinava Siri..

Hi,
Master Pages:
Does not included in the content area
Master page we will design logo,company address and header information
Here we can desing footer information
whatever you desing in the master page it will show for all the body pages
Body pages:
Included in the content area
Where we can design table data, it should repeat for line times.
Regards
Ramakrishna Pathi

Similar Messages

Difference between Golden Client and Master Client

Dear,
What is the Difference between Golden Client and Master Client?
Thanx & Regards,
Mohammad Nabi,
[email protected]

Golden Client is similar or is the the same as Development Client, which should not be used for testing.
Master Client ???
Note on SAP Landscape:
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different landscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
- QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving every time. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful transport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new development is done is development client and the request is transported to production.
These three are landscape of any Company. They organized their office in these three way. Developer develops the program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI has.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
Regards,
Rajesh Banka
Reward points if helpful

Difference between Next Set and Next Page

Hi,
does anyone know what is the difference between Next Set Template and Next Page Template in a Report Template?
Thanks,
Gari.

When you have a report with say 15 pages you can split it into a set like:
page 1 -5 , 6 - 10, 11 -15
When you select the next set HTML DB wil go from
1,2,3,4,5 [next set] to 6,7,8,9,10 [next set]
When you go to the next page is just shows the next page. You can go from page 5 to 6 with the next page and still end up on the next set :-).
Chris

Defferece between cost centre and Master Cost Centre

Can any body explain defferece between cost centre and Master Cost Centre.
Appreciate your help.
Kavitha

Hi kavitha
I dont think there is difference between Cost centre and master Cost Centre.
It may be Possible that under Cost Centre Hirarchy One Cost Centre is at Top node and other is Child of that Cost Centre.
Thank YOu.
Thank YOU.

Difference between Business Partner and Customer Master repository

What is the difference between Business Partner and Customer Master repository ?
Is the Business Partner repository to be used in case CRM is also in landscape ? or Customer master repository is good enough ?
Sandesh

Hi,
If the landscape has both CRM and SAP ECC a business partner repository model should be good.
If it has ECC alone.a Customer Repository is needed.
But when there are many legacy systems which also contains master data fields, the standard business repository provided by SAP wont provide a good solution as it wont cover the legacy master fields..In this case its better to go for a customized repository and you can use the standard repository as a reference.
Thanks

Differentiate between oa page and iStore page(jsp)

Hi,
How to Differentiate between OA page and iStore pages?

If the URL contains the JSP tag as OA.jsp or RF.jsp, then its an OAF application else if you see some custom jsp, eg, jftchrome.jsp etc, then the application is JTT/JTF based application:
eg:
OAF application:
http://sampledomain.oracle.com:5000/OA_HTML/*OA.jsp*?.......
http://sampledomain.oracle.com:5000/OA_HTML/*OA.jsp*?.......
JTT Application
http://sampledomain.oracle.com:5000/OA_HTML/*jtfchorme.jsp*?.......

Question about main difference between Java bean and Java class in JSP

Hi All,
I am new to Java Bean and wonder what is the main difference to use a Bean or an Object in the jsp. I have search on the forum and find some post also asking the question but still answer my doubt. Indeed, what is the real advantage of using bean in jsp.
Let me give an example to illustrate my question:
<code>
<%@ page errorPage="errorpage.jsp" %>
<%@ page import="ShoppingCart" %>

<jsp:useBean id="cart" scope="session" class="ShoppingCart" />
<html>
<head><title>Shopping Cart</title></head>
<body bgcolor="#FFFFFF">
Your cart's ID is: <%=cart.getId()%>.
</body>
<html>
</code>
In the above code, I can also create a object of ShoppingCart by new operator then get the id at the following way.
<code>
<%
ShoppingCart cart = new ShoppingCart();
out.println(cart.getId());
%>
</code>
Now my question is what is the difference between the two method? As in my mind, a normal class can also have it setter and getter methods for its properties. But someone may say that, there is a scope="session", which can be declared in an normal object. It may be a point but it can be easily solved but putting the object in session by "session.setAttribute("cart", cart)".
I have been searching on this issue on the internet for a long time and most of them just say someting like "persistance of state", "bean follow some conventions of naming", "bean must implement ser" and so on. All of above can be solved by other means, for example, a normal class can also follow the convention. I am really get confused with it, and really want to know what is the main point(s) of using the java bean.
Any help will be highly apprecaited. Thanks!!!
Best Regards,
Alex

Hi All,
I am new to Java Bean and wonder what is the main
difference to use a Bean or an Object in the jsp. The first thing to realize is that JavaBeans are just Plain Old Java Objects (POJOs) that follow a specific set of semantics (get/set methods, etc...). So what is the difference between a Bean and an Object? Nothing.
<jsp:useBean id="cart" scope="session" class="ShoppingCart" />
In the above code, I can also create a object of
ShoppingCart by new operator then get the id at the
following way.
ShoppingCart cart = new ShoppingCart();
out.println(cart.getId());
...Sure you could. And if the Cart was in a package (it has to be) you also need to put an import statement in. Oh, and to make sure the object is accessable in the same scope, you have to put it into the PageContext scope. And to totally equal, you first check to see if that object already exists in scope. So to get the equivalant of this:
<jsp:useBean id="cart" class="my.pack.ShoppingCart"/>Then your scriptlet looks like this:
<%@ page import="my.pack.ShoppingCart %>
<%
ShoppingCart cart = pageContext.getAttribute("cart");
if (cart == null) {
 cart = new ShoppingCart();
 pageContext.setAttribute("cart", cart);
%>So it is a lot more work.
As in my mind, a normal class can also
have it setter and getter methods for its properties.True ... See below.
But someone may say that, there is a scope="session",
which can be declared in an normal object.As long as the object is serializeable, yes.
It may be
a point but it can be easily solved but putting the
object in session by "session.setAttribute("cart",
cart)".Possible, but if the object isn't serializable it can be unsafe. As the point I mentioned above, the useBean tag allows you to check if the bean exists already, and use that, or make a new one if it does not yet exist in one line. A lot easier than the code you need to use otherwise.
I have been searching on this issue on the internet
for a long time and most of them just say someting
like "persistance of state", "bean follow some
conventions of naming", "bean must implement ser" and
so on. Right, that would go along the lines of the definition of what a JavaBean is.
All of above can be solved by other means, for
example, a normal class can also follow the
convention. And if it does - then it is a JavaBean! A JavaBean is any Object whose class definition would include all of the following:
1) A public, no-argument constructor
2) Implements Serializeable
3) Properties are revealed through public mutator methods (void return type, start with 'set' have a single Object parameter list) and public accessor methods (Object return type, void parameter list, begin with 'get').
4) Contain any necessary event handling methods. Depending on the purpose of the bean, you may include event handlers for when the properties change.
I am really get confused with it, and
really want to know what is the main point(s) of
using the java bean.JavaBeans are normal objects that follow these conventions. Because they do, then you can access them through simplified means. For example, One way of having an object in session that contains data I want to print our might be:
<%@ page import="my.pack.ShoppingCart %>
<%
ShoppingCart cart = session.getAttribute("cart");
if (cart == null) {
 cart = new ShoppingCart();
 session.setAttribute("cart", cart);
%>Then later where I want to print a total:
<% out.print(cart.getTotal() %>Or, if the cart is a JavaBean I could do this:
<jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session"/>
Then later on:
<jsp:getProperty name="cart" property="total"/>
Or perhaps I want to set some properties on the object that I get off of the URL's parameter group. I could do this:
<%
ShoppingCart cart = session.getAttribute("cart");
if (cart == null) {
 cart = new ShoppingCart();
 cart.setCreditCard(request.getParameter("creditCard"));
 cart.setFirstName(request.getParameter("firstName"));
 cart.setLastName(request.getParameter("lastName"));
 cart.setBillingAddress1(request.getParameter("billingAddress1"));
 cart.setBillingAddress2(request.getParameter("billingAddress2"));
 cart.setZipCode(request.getParameter("zipCode"));
 cart.setRegion(request.getParameter("region"));
 cart.setCountry(request.getParameter("country"));
 pageContext.setAttribute("cart", cart);
 session.setAttribute("cart", cart);
}Or you could use:
<jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session">
<jsp:setProperty name="cart" property="*"/>
</jsp:useBean>The second seems easier to me.
It also allows you to use your objects in more varied cases - for example, JSTL (the standard tag libraries) and EL (expression language) only work with JavaBeans (objects that follow the JavaBeans conventions) because they expect objects to have the no-arg constuctor, and properties accessed/changed via getXXX and setXXX methods.
>
Any help will be highly apprecaited. Thanks!!!
Best Regards,
Alex

Differences between Publishing sites and publishing enabled document library

Hi
what is the main differences between Publishing sites and publishing enabled document library
and how to enable publishing for document library?
adil

Publishing Sites is an out-of-the-box site template designed to publish web pages and it comes with a pre-built workflow or without (depends on which template you pick). It comes with libraries such as Pages library, Publishing Images, or Site Images.
It is configured to fully customized the master pages (or add new ones), and page layouts.
There is no such thing as publishing enabled document library. A document library is not designed to publish web pages. You can have Site Pages library in a team site, but if you are looking to fully brand a site collection, then this is not your answer.
You will need to use a Publishing Site to fully brand your Internet or Intranet site.
You can enable the publishing infrastructure on any site that is NOT a publishing site, but this does not turn your provisioned site to a publishing site. It simply turns on publishing features, such as navigation management, master pages/page layouts management,
publishing workflows, etc....

Difference between co-product and By-product

Hi,
Can anyone tell me Difference between co-product and By-product with example?
What is their impact on costing?

Hi,
By-Product : By-Product is a Product Created While Making Production
1. The System Does not create a separate order item for each by-Product
2. The Material Valuation of a by-Product is always based on the price, specified by the price control in the material master
3. The by-product must be listed as an item in the bill of material of the main product .The bill of material item must have a negative quantity (for example 1 -)
4. Byproduct has only the -ve quantity in BOM component, it does not go for joint production costing.
5. Movement type 531 to post the By-Product during Confirmation.
6. Settlement of cost is done to the header of the material
Co-Product :A co-product is a product that is produced in conjunction with other products. The system creates a separate order item in the production order for each co-product. As a result, it is possible to display actual costs at co-product
Settings: 1.) You have to activate check box in MRP2 view for co product.
2.) For co products we also need to define the apportionate structure with equivalence number for costing purpose, this will be done in "Joint Production" details in the same view. (30:30:20:20)
Prerequisite for the main product:
1.) The indicator Co-product must be activated in the material master of the main product (MRP area)
Prerequisites for a co-product:
1.) The indicator Co-product must be activated in the material master of the co-product (MRP area)
The co-product must be listed as an item in the bill of material of the main product
2.) On the Basic data tab page of the BOM item, the indicator Co-product must be activated in the field group General data
Regards
Sunil Kumar

Difference between Window Subwindow and Mainwindow

Hi I am new to smartforms. I want to know Difference between Window Subwindow and Mainwindow. are all these same ? Can i create a subwindow inside a main window ?

Hi
see the different types of Windows
What are the different types of windows in SAP Scripts?
Windows are defined in the Layout sets which define the position and the text to displayed.
The different types of windows are:
MAIN - Main Window
The main window is a continous window which can extend over several pages. If the text in the main window fills up a page, a new page is created.
Only one main window can be defined in the SAP Script whereas upto 100 instances of main window can be created in a page.
VAR - Variable Window
This window can have the variable contents displayed on them. The contents of the window cannot exceed the window size. The content can be formatted for each page.
CONST - Constant Window
The constant window can have a fixed content and is formatted only once.
Main Windows (MAIN)
Each form must have one window of type MAIN. Such a window is called the main window of the form. For SAPscript forms, the main window has a central meaning:
It controls the page break.
It contains the text body that may cover several pages.
It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the form. The SAPscript composer thus avoids reformatting of the text after each page break.
Variable Windows (VAR)
The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different form pages.
Constant Windows (CONST)
Starting with Release 4.0, the system internally processes windows of type CONST similar to windows of type VAR. Therefore, if you create a new window, always use type VAR.
Regards
ANJI

Difference between Plannnig Horizon and Production Horizon

Hai Can somebody explain me the difference between "Planning Horizon and Production Horizon"?
Here is the text that led me to this question:
"If the Production Horizon of SNP is smaller than PP/DS horizon, the planning horizons of SNP and PP/Ds overlap with each other." In this horizon, SNP determines the receipts with most cost effective sources of supply and lot sizes and PP/DS receipts generated by SNP in more detail.

check the following entries in Product master
The SNP production horizon is maintained on the SNP 2 tab page in the product master (transaction /SAPAPO/MAT1).
It also appears in the PPDS tab page along with PPDS horizon
The PPDS Planning horizon and PPDS Production horizon are the same. PPDs only plans inside this Horizon.
What is outside the SNP production Horiozon lies in the SNP planning horizon. Actually thought the name is a bit misleading - SNP does not plan anything inside the production horizon.
If you do not enter a value or you enter the duration 0 for the PP/DS horizon, the system automatically uses the SNP production horizon as the PP/DS horizon during planning. Therefore, the PP/DS horizon is exactly the same length as the SNP production horizon and this means that the SNP and PP/DS planning periods follow on from each other seamlessly and without overlapping.
If the SNP production horizon is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap. SNP and PP/DS can both use this overlapping period for planning.
A gap between the end of the PP/DS horizon and the start of the SNP planning period is a time segment that is neither planned by PP/DS nor SNP. This can lead to inconsistencies.
So think of two lines - one with its right side shaded(PPDS) and the other with its left side(SNP) shaded. Depending on where you place these lines the shaded sections get planned. how you get the two regions to mesh will ensure the effectivity of your plan
you can also get a better understanding looking at the product view screen and changing the product master values for the horizons and running heuristics

Wat is the exact differences between clustered table and pooled table

hi,
can you tell me ravi...wat is the exact differences between clustered table and pooled table
with regards//
anilreddyg

Hi Anil Reddy
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
Table Pools
From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
Field Type Description
TABNAME CHAR(10) Table name
VARKEY CHAR(n) Maximum key length n =< 110
DATALN INT2(5) Length of the VARDATA record returned
VARDATA RAW(m) Maximum length of the data varies according to DBMS
Table Clusters
Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
Field Type Description
CLKEY1 CHAR(*) First key fields
CLKEY2 CHAR(*) Second key field
CLKEYN CHAR(*) nth key field
PAGENO INT2(5) Number of the next page
TIMESTMP CHAR(14) Time stamp
PAGELG INT2(5) Length of the VARDATA record returned
VARDATA RAW(*) Maximum length of the data section; varies according to database system
Working with Tables
The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
select Dictionary object Display from the menu.
In this screen, you can see table information such as
¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
¨ Short text description.
¨ Name of the user who made the last change, and the date of the change.
¨ Master language.
¨ Table status. On the screen, you can see this table is saved and active.
¨ Development class. For information on development classes, refer to Chap. 6.
Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
¨ Field name.
¨ Key indicator. When set, this field is the primary key, or part of it.
¨ Data element.
¨ Basic data type.
¨ Length.
¨ Check table.
¨ Short text, describing the field.
Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Index table:
The table can be a standard table or a sorted table.
Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
Regards
Sreeni

Difference between sy-uline and uline

Hi All,
Any one of you please update me what is the difference between sy-uline and uline. Also when i give sy-uline in top-of-page event it gives error.
Thanks
sankar

with ULINE u can specify the position from where the ULINE should start
corresponds to WRITE AT 3(10) SY-ULINE.
ULINE AT 3(10) NO-GAP will supress the spacess after the under line
ex : 1
uline at 4(10).
write : / 'My Program'.
uline at 4(10).
ex : 2
write : 'My Program' , sy-uline.

What is difference between Managed Bean and Backing Bean?

What is difference between Managed Bean and Backing Bean? Please guide me how to create them and when to use them?
Please post sample for both beans.

Hi,
managed beans and backing beans are quite the same in that the Java object is managed by the JavaServer Faces framework. Manage in this respect means instantiation. The difference is that backing beans contain component "binding" references, which managed beans usually don't. Do backing beans are page specific versions of managed beans.
Managed beans are configured either in the faces-config.xml file, or using ADF Faces and ADFc, in the adfc-config.xml file
Frank
Edited by: Frank Nimphius on Jan 31, 2011 8:49 AM

What is difference between SharePoint List and Libraries

What is difference between SharePoint List and Libraries

Hello,
You also might want to loot at here:
http://veroniquepalmer.com/2013/02/24/the-difference-between-sharepoint-2010-lists-libraries-and-pages/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/1d4152cd-92a6-4eed-9a52-a519ec71c674/what-is-the-difference-between-document-library-and-list-in-sharepoint
Hope it could help
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

Difference between Body pages and Master Pages in Adobe forms?

Similar Messages

Maybe you are looking for