<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/adv/ttadv3531m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Report Layouts (ttadv3531m000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to display the layouts of a report.</Paragraph>
		</AimSection>
		<GeneralSection><List><ListIntro>Via the <GUIRef href="" role="manual">Specific</GUIRef> menu, you can:</ListIntro>
				<ListItem>Edit a selected layout. Refer to <GUIRef href="/baanerp/tt/adv/ttadv3531m000#exec.user.0" role="command">Edit Layout...</GUIRef> for details.</ListItem>
				<ListItem>Edit all layouts simultaneously. Refer to <GUIRef href="/baanerp/tt/adv/ttadv3531m000#exec.user.2" role="command">Edit All Layouts...</GUIRef> for details.</ListItem>
				<ListItem>Copy layouts from another report. Refer to <GUIRef href="/baanerp/tt/adv/ttadv3531m000#exec.user.1" role="command">Copy from Other Layout...</GUIRef> for details.</ListItem>
			</List>
			<Paragraph class="Default">You can start the report editor to display a specific layout by marking it.</Paragraph>
		</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="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="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.layt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Layout</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/domains/adv.layt" role="domain">Layout Type</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv331.fldn"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Name</Title>
			</Header>
			<FuncDesc>The field name is only applicable for <Link href="/baanerp/tt/domains/adv.layt#before.field" role="option">Before.field</Link> and <Link href="/baanerp/tt/domains/adv.layt#after.field" role="option">After.field</Link> layouts. You can only specify fields, which are defined as a sorted input field in the <GUIRef href="/baanerp/tt/adv/ttadv3532m000" role="session">Report Input Fields (ttadv3532m000)</GUIRef> session. Before.field and After.field 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 per 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 per 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.</FuncDesc>
			<SimpleSection><SectionTitle>Examples</SectionTitle>
				<List><ListItemHead>1</ListItemHead>
					<ListItem>Layout will always be printed</ListItem>
					<ListItemHead>0</ListItemHead>
					<ListItem>Layout will never be printed</ListItem>
					<ListItemHead>print.detail = 1 or print.detail = 2</ListItemHead>
					<ListItem>Layout will be printed if variable print.detail is 1 or 2</ListItem>
					<ListItemHead>strip$(tdsls041.cprj) &lt;&gt; ""</ListItemHead>
					<ListItem>Layout will be printed if field tdsls041.cprj is not empty</ListItem>
				</List>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If variables are used in the output expression, then those variables must be defined as input field for the report, specified in the <GUIRef href="/baanerp/tt/adv/ttadv3532m000" role="session">Report Input Fields (ttadv3532m000)</GUIRef> session.</Paragraph>
			</Note>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="exec.user.0"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Edit Layout...</Title>
			</Header>
			<FuncDesc>Starts the <GUIRef href="/baanerp/tt/adv/ttadvformedit" role="session">Form/Report Editor (ttadvformedit)</GUIRef> where you can view or edit the selected layout.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can only edit report layouts if the report belongs to your current package VRC. If the report belongs to another VRC, the report editor is started in display mode.</Paragraph>
			</SimpleSection>
		</CommandHelp>
		<CommandHelp ID="exec.user.1"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Copy from Other Layout...</Title>
			</Header>
			<FuncDesc>Use this option to copy a layout from another report to a new layout in the current report.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The <GUIRef href="/baanerp/tt/adv/ttadv3535s000" role="session">Display Report Layout Data (ttadv3535s000)</GUIRef> session is started, where you can find and select a layout of a different report. When you click <GUIRef href="" role="manual">OK</GUIRef> in this session, the <GUIRef href="/baanerp/tt/adv/ttadv3131s000" role="session">Report Layouts (ttadv3131s000)</GUIRef> details session is started. Here you must specify the name of the new layout in the current report.</Paragraph>
			</SimpleSection>
		</CommandHelp>
		<CommandHelp ID="exec.user.2"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Edit All Layouts...</Title>
			</Header>
			<FuncDesc>Starts the <GUIRef href="/baanerp/tt/adv/ttadvformedit" role="session">Form/Report Editor (ttadvformedit)</GUIRef> where you can view or edit all layouts of the current report. This option is especially useful if you want to have an overview of the entire report structure, or if you want to move components from one layout to another. For example if you want to move a label from the header to a before.field.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can only edit layouts if the report belongs to your current package VRC. If the report belongs to another VRC, the report editor is started in display mode.</Paragraph>
			</SimpleSection>
		</CommandHelp>
	</FormCommands>
</Session>
