<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/adv/ttadv3535s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Display Report Layout Data (ttadv3535s000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to display general data of a report layout. This session is called by the report editor and can be used to read a layout and fill a buffer.</Paragraph>
		</AimSection>
		<GeneralSection><Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If you have started this session by zooming, you can only find and select a record.</Paragraph>
			</Note>
		</GeneralSection>
	</HelpTopic>
	<Fields><FieldHelp ID="ttadv331.clan"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Language</Title>
			</Header>
			<FuncDesc>The language code of the report. When a user runs a session with a report, the report in his own language will be run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad110.dsca"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Language</Title>
			</Header>
			<FuncDesc>The description of the language code.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.cpac"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Package</Title>
			</Header>
			<FuncDesc>A set of related modules that implements a complete part of the functionality, for example, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, or <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>. Packages are designed to function as independent as possible, to enable a customer to implement only particular packages.</FuncDesc>
			<SimpleSection><Paragraph class="Default">A package code consists of two characters. For example, tt is the code of the <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef> package.</Paragraph>
				<Paragraph class="Default">Each package has a unique version structure, the VRC structure.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv100.dsca"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Package</Title>
			</Header>
			<FuncDesc>The description of the package.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.vers"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">VRC</Title>
			</Header>
			<FuncDesc>An upgrade of a package, for example, B61. Each change in the functionality of a package results in a new version. A version can contain several releases.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.rele"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">VRC</Title>
			</Header>
			<FuncDesc>An update in a version. For example, 'B61 a', where 'B61' represents the version code, and the 'a' represents the release code. Each update results in a new release with a new release code.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.cust"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">VRC</Title>
			</Header>
			<FuncDesc>A code that identifies a customized software package. For example, B61O_a_cus1, where 'B61O' represents the version, 'a' represents the release, and 'cus1' represents the customer extension of the customized software.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.cmod"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Report</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/glossary/glossary#100004" role="glossary">module</Link> to which the report belongs.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.crep"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Report</Title>
			</Header>
			<FuncDesc>The identification code of the report. A report is uniquely identified by the combination of package code, module code, report code and language.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.fldn"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Name</Title>
			</Header>
			<FuncDesc>Only applicable for <GUIRef href="/baanerp/tt/domains/adv.layt#before.field" role="option">Before.field</GUIRef> and <GUIRef href="/baanerp/tt/domains/adv.layt#after.field" role="option">After.field</GUIRef> layouts. You can only specify fields, which are defined as a sorting input field in <GUIRef href="/baanerp/tt/adv/ttadv3532m000" role="session">Report Input Fields (ttadv3532m000)</GUIRef>. The <GUIRef href="/baanerp/tt/domains/adv.layt#before.field" role="option">Before.field</GUIRef> and <GUIRef href="/baanerp/tt/domains/adv.layt#after.field" role="option">After.field</GUIRef> layouts will be printed when the value of the specified field changes.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.rseq"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">No.</Title>
			</Header>
			<FuncDesc>It is possible to define more than one layout by Layout/Fieldname combination. The layouts of the same Layout/Fieldname will be printed in the order of the sequence number of the layouts.</FuncDesc>
			<SimpleSection><List><ListIntro>There are two reasons to define more than 1 layout by Layout/Fieldname combination:</ListIntro>
					<ListItem>The maximum size of a layout is 22 lines. If your layout should have more lines, you can make a second layout of the same type with a higher sequence number.</ListItem>
					<ListItem>If a particular layout must be printed under certain conditions and another layout under other conditions, you have to define more than one layout with different output conditions.</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv331.outc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Output Expression</Title>
			</Header>
			<FuncDesc>The output expression is an expression which is evaluated at runtime. The result is always true or false. The expression syntax is equal to the 3 GL syntax. At the moment a layout has to be printed, the system will evaluate the output condition of the layout. Only if the result at that moment is true, the layout is printed. Examples: 1 Layout will always be printed print.detail = 1 or print.detail = 2 Layout will be printed if variable print.detail is 1 or 2. strip$(tdsls041.cprj) &lt;&gt; "" Layout will be printed if field tdsls041.cprj is not empty. Note If variables are used in the output expression that variable must be an input field for the report, specified at <GUIRef href="/baanerp/tt/adv/ttadv3532m000" role="session">Report Input Fields (ttadv3532m000)</GUIRef>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.font"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Ft</Title>
			</Header>
			<FuncDesc>Only applicable, if the report layouts in one report have different fonts ("Fixed Font = "yes" on general report data). It determines the font in which the layout will be printed.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.page"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Page</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the report layout is printed on a new page. Skipping to a new page always causes printing of present footers, headers and before.field layouts. If the current line is already at the top of the page, the page command will be ignored.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Not applicable for header and footer layouts.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv331.need"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Nd</Title>
			</Header>
			<FuncDesc>This number indicates how many extra lines are needed for the layout on the same page.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Before printing a layout the report writer calculates the free space at the current page. If the layout does not fit on the same page, then the layout will be printed on a new page. If the value of "Extra need" is 0, only the number of lines of the layout itself are taken into account. With "Extra need" you can increase the number of extra needed free lines for the layout. Increasing this number of lines can be useful e.g. if you want to print at least 2 detail layouts on the same page together with a "before.field" layout.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">For headers and footers you cannot specify Extra need lines.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv331.rows"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Lns</Title>
			</Header>
			<FuncDesc>The number of lines of the report layout. This number is calculated automatically according the layout. This field cannot be accessed by the user.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.mcol"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Mult.col</Title>
			</Header>
			<FuncDesc>Indicates whether the report layout must be printed in more than one column or not. The number of columns depends on the size of the layout and the paper width. You can change the layout size with the command &lt;Esc&gt;[S] in the report layout editor. Page Width Number of columns = -------------- Layout Width</FuncDesc>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="command.save.def"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Save Defaults</Title>
			</Header>
			<FuncDesc>Saves the current settings as your default settings.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="command.get.def"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Get Defaults</Title>
			</Header>
			<FuncDesc>Restores your default settings.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
