Attune for Manufacturers

Extras in Queries
User Guide

Document Version: 0.1 (Draft)

attune USA

1400 Main St. Waltham, MA 02452 USA T+1 781 8990664 F+1 781 8990664
www.attuneconsulting.com

Copyright 2006-2009 attune. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from attune. All copyright, confidential information, patents, design rights and all other intellectual property rights of whatsoever nature in and to any source code contained herein (including any header files and demonstration code that may be included), are and shall remain the sole and exclusive property of attune. The information furnished herein is believed to be accurate and reliable. However, no responsibility is assumed by attune for its use, or for any infringements of patents or other rights of third parties resulting from its use. SAP and AFS are registered trademarks of SAP. Microsoft and Microsoft Windows XP are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners.
attune USA LLC, attune Lanka pvt ltd, attune Germany Gmbh, attune UK Limited, attune Italia S.r.L., attune Australia (Pvt) Ltd, attune Hong Kong, attune Consulting India Pvt. Ltd., attune do Brasil are all subsidiaries of attune holdings.

Logo is the property of attune holdings.

Document Control
Document Version 0.1 (Draft) 0.1 (Draft) Description Date Changed/ Reviewed

Initial Draft Reviewed

16/06/2009 16/06/2009

Gunith de Silva/Tharaka Perera Eshan Weeratunga

Icons
Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions
Type Style Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

EXAMPLE TEXT

Example text <Example text>

Table of Contents
1. 2. 3. 4. 5. Introduction .......................................................................................................................................... 1 Creating an Additional Field .................................................................................................................. 2 Coding for the Traffic Lights .................................................................................................................. 3 Adding a Local Field .............................................................................................................................. 7 Assigning Transaction Code for Query .................................................................................................. 9

1. Introduction
This user guide will enable the user to generate query reports more effectively with additional functionality. The user manual will provide some tips for the users to enhance the query reports.

In addition to the basic functionality of a query, the user can add extra features such as additional fields with coding and selection fields. This done in the following manner in the particular info set. Transaction code SQ02

2. Creating an Additional Field

3. Coding for the Traffic Lights

Query reports have the functionality of providing traffic light system, which will provide a graphical insight of the status for the users.

Once the field has been created the user needs to write the coding necessary for the inclusion of the traffic lights for the Status field.

For this scenario the coding is written for the following requirement for the DIFOT report. If Schedule Qty & Delivered Qty and Oder Date & Posting Date are equal the traffic light will be GREEN. If Qty condition has been met and the Posting Date is prior to the Order Date the traffic light will be GREEN. If either of the above conditions have not been met the traffic light will be ORANGE. If both the conditions have not been met the traffic light will be RED.

Check and Save the coding.

How to get the ID of the Symbol Transaction code SE38

Give program name as icons and double-click on icon

Select the ID for the required symbol.

Then

the Info Set again prior to creating the query.

4. Adding a Local Field

Transaction code SQ01

This will give the user text boxes to enter short names. Assign variants for the fields required. Scheduled Qty and Qty of Goods Received is required for the new local field Balance Qty. Therefore SCH variant is assigned to Scheduled Qty and DEL variant is assigned to Qty of Goods Received and the calculation formula is given based on these variants.
7

Specify the Heading as wanted to appear in the query report and specify the basic calculation for the additional field.

The additional local field can depicted as follows.

5. Assigning Transaction Code for Query

Step 1 Get the program name.

Step 2 Assign Transaction code Transaction code SE93

10

11