Need information on 'Repeat Delta' process

Deleted failed request from InfoCube 0PY_C02
Checked Data Mart Status from ODS ZPY_O50 for failed load.
When attempting to push the data from the ODS to InfoCube get error message:
     Last delta update is not yet completed
     Therefore, no new delta update is possible.
     You can start the request again
     if the last delta request is red or green in the monitor (QM activity).
To get load to start, opened process chain and selected ‘Repeat’ from context menu. This enabled the job to start without the above mentioned error.
Questions to answer:
1. BW is expecting less than 8019027 records to be uploaded to the InfoCube, currently looking in the monitor I see that 44204420 records have been processed. Does this mean that the repeat process is loading all data to InfoCube from ODS?
2. When doing a repeat last delta, does the system repeat only the last successful delta?
3. When doing a repeat last delta, does the system read the entire contents of the ODS then update the InfoCube with the correct records, or just read the last request loaded to the ODS?

Normally the repeat should pull only the failed delta, but for some reason I experienced that too having the repeat was pulling more record that the earlier delta. I would say the delta pointer is not working properly.
Normally, before deleting the failed request, you need to turn the request to red, but that is too late now to do.
You need to reint delta, but you need to make sure that you don't miss the last delta.
Steps:
1. Delete the failed request from the cube.
2. Delete the successful request from the ods
3. Delete initialization from ods to the cube
4. Do init without data transfer from ODS to the cube
5. Reconstruct the last deleted request in the ODS
6. Do Delta from ods to the cube.
Now you have reinitialized and got the last delta which is in the ods.
thanks.
Wond

Similar Messages

  • Need information-BW System administration-process chains

    Hi gurus,
    I need information about BW System administration-process chains
    can anyone send me the docs related to
    1)process chain modellin aspects
    2)process chain monitoring &error handling
    3)BW statistics and query tuning with aggregates
    Thanks in advance..
    regards
    s ram

    Hi,
    Check these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ce/dc87c1d711f846b34e0e42ede5ebb7/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/d5/e80d3dbd82f72ce10000000a114084/frameset.htm
    Process Chain
    process chain
    BW STATISTICS  
    If you are asking abt the flags that you see in RSA1 -> Tools -> BW Stats...you can check BW Stats for each and every infoprovider. Whenever you create an infopprovider you should always decide whether you want to turn on the BW Stats for this infoprovider. This is a manual step and can be done in each and every box individually or can be transported across the systems. Coming to your question...BW Stats are of two kinds...
    1) OLAP -
    If you check this flag for an infoprovider...all the statistical data for the queries built on this infoprovider gets updated into the corresponding infocubes (0BWTC_C02 and 0BWTC_C03). An example would be like number of users that ran the report in a given time, the average run time of the query and so on. This data is of immense value in deciding the steps for performance tuning techniques like aggregates!
    2) WHM (Warehouse Management) -
    If you turn this flag on for an infoprovider, all the statistical data like how often the cubes are loaded, when are the requests deleted from the infocubes, data abt condensing of cubes and so on is loaded into the corresponding cubes like 0BWTC_C04, 0BWTC_C05, 0BWTC_C09 and 0BWTC_C11.
    You have to activate the infopackages to load into these cubes and schedule them through process chain to run once in a while so that your statistical data is uptodate.
    Production support for maintaining the process chains primarily involves monitoring activities of all the chains that are running in the background...
    Errors in monitoring of process chains can be categorized into 4 different sections...
    Master data - Full Update
    Master data - Delta Update
    Transaction data - Full Update
    Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
    Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
    There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
    In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
    For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
    Majority of the issues will be based on these things only..
    ****Assign Points If Helpful****
    Regards,
    Ravikanth
    Message was edited by:
            RK.PNV

  • Need information about a CMTS process

    Hi all,
    Does anybody know what the “ADJ resolve proc” process do ?
    This process shows up on all our CMTSs.
    Thanks,
    Sinisa

    Hi Sinisa,
    The ADJ Resolve process is a process in charge of resolving adjacencies for IP packets received by the CMTS. Basically, when a packet is recieved, the CMTS looks for the destination address in an adjacency table to fast-forward the packet. If there is no adjacency entry, the packet is sent to the RP and the ADJ Resolve process tries to populate the adjacency table (using ARP). If ARP reply is received, the adjacency is created and subsequent packets can be fast-forwarded. If not reply is received, the process retries a few times. During that time, incomplete ARP entries will probably be seen in the CMTS.
    I hope this is the explanation you were looking for.
    Best regards.

  • Need information about creadit card process in ESS and transaction PR05

    Hello,
    Can anybody explain me the credit card clearing in ESS and information about transaction PR05...Its very urgent...No doubt...Good help will be appreciated and honoured...
    Thanks,
    Tushar

    Dear Sarthak M,
               Assume you have gone through the transaction BAPI,
    where you can find all relevant BAPI's .
    select the relevant text such as "sales orders" - from the right side of the screen - check "Tools" tab,where you will find "Create BAPI list", click to search for the Function moduels.

  • COPA Realignment in R/3 -do i need to Re-initialize the Delta Process in BI

    Hi frnds,
    Im facing an issue related COPA realignment,
    1.Once the COPA realignment is done in R/3, Do i need to Re-initialize the Delta Process in BI?
    Edited by: MohanDP on May 4, 2011 8:37 AM

    But i need historical data too,so how to avoid Re-initialization to get historical data.Can u please help
    if you need the changed historical data, you have no choice but to reinit. you can do this at anytime, you don't need any downtime for copa init.
    M.

  • Need information on BAPI for Sales Process ?

    Hello SAP folks,
    I am currently involved in Consumer Portal integration with SAP System. I need information about the right kind of BAPI that would help me to enter and retrieve data from SAP database. I have noted down following funtionality in Sales And Distribution areas where i require a BAPI :
    1. Account Management -- > There are concept of Sales rep, Dealer on the consumer Portal. My question is -- > Could anyone suggest some BAPI for creation of User ID for Sales rep and Dealer as well i need information on the BAPI which would also help me displaying the data from SAP database. As far i know, in Customer Master record, we maintain Contact person and Buiness Partners. So how to take up these development into consideration ???
    2. Mulitple Credit Card Management --> Please suggest the BAPI for meeting this functionality at Sales order level.
    3. Customer Inclusion/Exclusion --> Here the basic need is exclude certain customer from availabling some product. Please suggest the BAPI for this operation.
    Regards,
    Sarthak

    Dear Sarthak M,
               Assume you have gone through the transaction BAPI,
    where you can find all relevant BAPI's .
    select the relevant text such as "sales orders" - from the right side of the screen - check "Tools" tab,where you will find "Create BAPI list", click to search for the Function moduels.

  • Informatica Night Update (Delta) Process - More than one Delta Source

    We are setup to run a nightly process to update our DW with changes that took place that day in our Siebel OLTP environment. We refer to this as our "Delta Process" since it only updates rows that were chagned in the OLTP or adds new rows that were added to the OLTP. Here is our design:
    * In our Siebel OLTP we have a View (V table) created that contains a view of only the records that have been changed since the last "Delta Process". This way we can identify only those rows that need to be updated. So in these examles when you see a table that is prefixed as "S_" it references the entire table and a table prefixed as "V_" references on only the changes to the underlying "S_" table.
    Ex 1: Order Item table (S_ORDER_ITEM) joins to Account table (S_ORG_EXT). In the Informtica mapping SQ_JOINER we have a query to SELECT statements that with the results concatentated with a UNION statement. The first SELECT statement selects all rows from the V_ORDER_ITEM joined to the S_ORG_EXT so that all delta rows on the order item view are updated with the corresponding data from the account table (S_ORG_EXT). The second SELECT statement selects all rows from the S_ORG_ITEM joined to the V_ORG_EXT so that all of the order item records that contained account information that changed (per the view) are updated. The result is an updated Order Item DW table that contains all updates made to the Order Item and all any associated Accounts information that is stored on the Order Item.
    SELECT A.*, B.* FROM V_ORDER_ITEM A, S_ORG_EXT B WHERE A.ORG_ID = B.ROW_ID
    UNION
    SELECT A.*, B.* FROM S_ORDER_ITEM A, V_ORG_EXT B WHERE A.ORG_ID = B.ROW_ID
    The issues:_
    This works fine when you have two tables joined together that contain deltas and you need only on UNION statement. However, the issue is when I have 14 tables joined to S_ORDER_ITEM that contain deltas. This cannot be accomlised (that I can see) with one UNION statement but you would need a UNION statement for each delta table.
    Ex 2: This example contains just 3 tables. Order Item table (S_ORDER_ITEM) joins to Account table (S_ORG_EXT) and joins to Product table (S_PROD_INT). In this example you will need to have one UNION for each delta table. If you combine delta tables in the same union you will ultimately end up missing data in the final result. This is because the delta tables will only contain the rows that have changed and if one delta table contains a change and needs to pull data from another delta table that did not contain a corresponding change it will not pull the information.
    SELECT A.*, B.*, C.* FROM V_ORDER_ITEM A, S_ORG_EXT B, S_PROD_INT C WHERE A.ORG_ID = B.ROW_ID AND A.PROD_ID = C.ROW_ID
    UNION
    SELECT A.*, B.*, C.* FROM S_ORDER_ITEM A, V_ORG_EXT B, S_PROD_INT C WHERE A.ORG_ID = B.ROW_ID AND A.PROD_ID = C.ROW_ID
    UNION
    SELECT A.*, B.*, C.* FROM S_ORDER_ITEM A, S_ORG_EXT B, V_PROD_INT C WHERE A.ORG_ID = B.ROW_ID AND A.PROD_ID = C.ROW_ID
    The question:_
    1. Is my understanding of how the delta process works correct?
    2. Is my understanding that I will need a UNION for each delta table correct?
    3. Is there another way to perform the delta process?
    My issues are based upon the fact that I join roughly 15 delta tables and select about 100 columns to denormalize the data in the DW. If this is the only option that I have then this will generate an very large and complex query which would be very difficult to manage and udpate.
    Thanks...

    Hi,
    Going thru your post, I find that you have the delta view (V_) and the main table (S_) as drivers, i.e you have two driver tables and hence you make outer joins (w.r.t each other) and make a union to get the complete set of data.
    Can you please tell me why both are considered as drivers? Is there a possiability that the V_ view may not have some data but the corresponding S_table might have an update?
    Regards,
    Bharadwaj Hari

  • Need information on SMARTFORMS

    hi i m looking for some information on SMARTFORMS.
    why it is needed?
    what is difference between smartforms and sapscripting?
    if someone could send some docs. how to work on smartforms it will begreat

    Hi,
    Here I am sending the full information about smartforms. Reward if helpful.
    SAP Smart Forms (BC-SRV-SCR)
    Purpose
    You use SAP Smart Forms to create and maintain forms for mass printing in SAP Systems. As output medium SAP Smart Forms support a printer, a fax, e-mail, or the Internet (by using the generated XML output).
    In addition to the tool, SAP delivers a selection of forms for central business processes. This includes forms in Customer Relationship Management (CRM) as well as in the applications SD, FI, and HR of the R/3 Release.
    SAP Smart Forms offer the following advantages:
    •     Creating and maintaining forms requiring half the time
    •     Adapting forms without any programming knowledge due to entirely graphical user interface
    •     Web Publishing using the generated XML output
      The SAP Smart Forms replace the SAPscript forms. SAPscript forms will also be supported in the future; you can use them without making any changes for years to come. You can use SAPscript texts in the Smart Forms. Migration of SAPscript forms into Smart Forms is supported.
    Features
    SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all cases, this won't include any programming effort. Thus, a power user without any programming knowledge can configure forms with data from an SAP System for the relevant business processes.
    To print a form, you need a program for data retrieval and a Smart Form that contains the entire from logic. As data retrieval and form logic are separated, you must only adapt the Smart Form if changes to the form logic are necessary. The application program passes the data via a function module interface to the Smart Form. When activating the Smart Form, the system automatically generates a function module. At runtime, the system processes this function module.
    You design a form using the graphical Form Painter and the graphical Table Painter. The form logic is represented by a hierarchy structure (tree structure) that consists of individual nodes, such as nodes for global settings, nodes for texts, nodes for output tables, or nodes for graphics. To make changes, use Drag&Drop, Copy&Paste, and select different attributes. These actions do not include writing of coding lines or using a Script language.
    For Web publishing, the system provides a generated XML output of the processed form.
    You can insert static and dynamic tables. This includes line feeds in individual table cells, triggering events for table headings and subtotals, and sorting data before output.
    You can check individual nodes as well as the entire form and find any existing errors in the tree structure. The data flow analysis checks whether all fields (variables) have a defined value at the moment they are displayed.
    SAP Smart Forms allow you to include graphics, which you can display either as part of the form or as background graphics. You use background graphics to copy the layout of an existing (scanned) form or to lend forms a company-specific look. During printout, you can suppress the background graphic, if desired.
    SAP Smart Forms also support postage optimizing.
    General Concepts on Form Printing
    Form printing covers creating and maintaining a form for mass printing in SAP Systems. This includes design and layout of the form as well as form logic.
    The layout determines the page structure, that is the number of differently structured pages and the positions of the output areas on these pages. Within the output areas, you use tables, paragraphs, paragraph formats and character formats to structure and format texts and data.
    The form logic controls the dynamic formatting of the form. It allows you to display variable fields, to display texts only if a certain condition is true (for first dunning, use this text, for second dunning another), or to repeatedly process invoice items within a table.
    Forms can be:
    •     Order confirmations
    •     Invoices
    •     Account statements
    •     Checks
    •     Salary statements
    •     Delivery notes
    •     Customs forms
    •     Industry-specific forms, such as quality forms in automobile manufacturing
    The concepts on form printing presented below are independent of any tool. As of mySAP.com release 4.6C use the SAP Smart Forms [Extern] in SAP Systems.
    This documentation does not cover document output and control on printers. Description of the process ends with transferring a processed file to the output management, which in the R/3 System is the spool.
    Structure of a Form
    Definition
    A form consists of pages, output areas, addresses, graphics (such as company logo), and data or text contents. Within an output area, you can use static or dynamic tables to display data or texts in lines, columns, or cells. To further structure and format text and data, use paragraphs with the paragraph and character formats.
    SAP calls output areas "windows". You can position windows freely on a page (see also Pages of a Form [Seite 8] and Main Windows and Subwindows [Seite 8]).
    Example of a Form Structure
    We use a simple invoice. For certain customers, we display their flight bookings with prices in a table in a window. The invoice also contains other windows for the company logo, the sender address, the customer address, company-specific data (clerk, customer number, reference, date, and so on), bank data, and pagination.
    The first page displays the customer letter, followed by a table containing the flight bookings of that customer. The output length of the table depends on the number of booking items (dynamic table). The table header contains the column headings, the table footer contains the total. If the space on the first page is not sufficient to take all items, the table continues on the next page, thereby repeating the column headings. In addition, the first page contains:
    •     the company logo inserted as graphic in bitmap format.
    •     the customer address. This address appears only on the first page (for the window in the envelope) and is preceded by the sender address in small font.
    •     a window containing company-related data in several fonts and font sizes (invoice, clerk, phone/fax, reference, customer number, date).
    •     the footer containing the company and bank data.
    The second page contains the current page number and the total number of pages in the document.
    Pages of a Form
    Definition
    On the pages of a form you determine the page layout and the sequence of pages with different structures.
    The page layout includes the page format (for example, DIN A4, Letter, DIN A5 landscape) and the position of the windows on a page.
    Use
    The individual pages of a form differ in their structure. The first page of an invoice, for example, contains the address, which you do not want to display on the next page; and you want to display the General Terms of Business on the last page. For each page, you must specify a next page to make the page sequence clear. You can also repeatedly call the same page if you want recursive output (for example, if the list of invoice items is very long and does not fit onto one document page).
    The page break either is triggered automatically by the main window (see also Main Window and Subwindows [Seite 8]) or you code it manually into the form logic (see also Specifying the Page Sequence [Seite 52]).
    Many forms contain only two pages of different structure: the first page, which calls the next page, and the next page, which calls itself. If the text does not entirely fit onto the second page, another document page is automatically displayed.
    Main Window and Subwindows
    Definition
    On a page, there are two different types of output areas for texts and data: the main window and the subwindow.
    Use
    You can position windows anywhere on a page, even overlapping. You can position the same window (determined by the technical name) on several pages of a form, so that the same contents are displayed on all these pages. You can choose a different size for the window on each page, except for the main window.
    Main Window
    In a main window you display text and data, which can cover several pages (flow text). As soon as a main window is completely filled with text and data, the system continues displaying the text in the main window of the next page. It automatically triggers the page break.
    You can define only one window in a form as main window.
    The main window must have the same width on each page, but can differ in height.
    A page without main window must not call itself as next page, since this would trigger an endless loop. In such a case, the system automatically terminates after three pages.
    Subwindows
    In a subwindow you display text and data in a predetermined output area. There is no flow text display with page break. If you position a subwindow with the same name on several pages, the system displays the contents of this subwindow on each page.
    Text and data that do not fit into the subwindow are truncated and not displayed.
    Texts and Data in a Form
    Definition
    You enter text in an editor (see also Positioning Text on a Form [Seite 26]).
    Data can be character strings or numbers. The system reads this data from a database and uses fields (parameters) to dynamically display it (see also Using Parameters in a Form [Seite 37]).
    Use
    To display text and data in table format (for example, lists or invoice items), you use tables or templates.
    To format texts and fields (data), you use paragraph and character formats. You assign paragraph formats to entire paragraphs and character formats to individual character strings, for example, to highlight a word.
    The paragraph format determines:
    •     Font family and font size,
    •     Indents and spacing,
    •     Text alignment within the paragraph,
    •     Tabs,
    •     Outline options, such as numbering,
    •     Protection of paragraphs against page breaks.
    To determine the paragraph and character formats, use the Smart Styles (see also Smart Styles [Seite 54]).
    Overview
    This section describes the architecture  [Seite 10]of SAP Smart Forms and how to create a form [Seite 11]. Essential for creating forms is to understand the form logic [Seite 13].
    Architecture
    If you create forms for an application, you want to include application data into the form. The architecture of SAP Smart Forms separates application data retrieval from the actual definition of the form:
    In a Smart Form you describe:
    •     The layout of your form (element positions on a page)
    •     Individual elements you want to display (text, graphics, addresses, tables, and so on)
    •     the form logic you use, for example, to read application data from internal tables, to introduce conditions, and to control process flows (see also: Form Logic: Introduction [Seite 13])
    •     a form interface to transfer application data to the form definition
    When you activate the Smart Form, the system generates a function module that encapsulates all attributes of the Smart Form. As soon as the application program calls the function module, the Smart Form uses the modules interface (which corresponds to the form interface) to transfer any table data previously selected and to print the form according to the form description.
    The form description can also contain statements that select further data during form processing. However, you should not use this method of data retrieval. Especially if you print mass forms, performance will deteriorate considerably.
    Creating Forms Using SAP Smart Forms
    This section gives an overview of how to create a form in which to display application data from database tables.
    For more detailed information on this procedure, see Using SAP Smart Forms [Seite 14].
    When creating a form, you must:
    1.     Retrieve the application data [Seite 11].
    2.     Describe your form [Seite 12].
    3.     Pass the application data to the form [Seite 38].
    Printing the Form
    Call a function module generated by Smart Forms to print your form. Smart Forms support the forllowing output options:
    •     The form is printed on a printer connected to the SAP System. Before printing, use the print preview to check whether the form is correct.
    •     The function module generates an XSF datastream that transfers, for example, the form description including the retrieved data to programs of third-party companies.
    Retrieving Application Data
    Prerequisites
    To achieve a good performance when printing a form, you must separate data selection from the use of data in the form. Thus you can bundle database operations before you start processing the form.
    Before you retrieve data, you should know:
    •     Which application data you want to appear in the form
    •     Which database tables you must access to retrieve this data
    Process Flow
    Write an ABAP program to retrieve data or include a retrieval routine into your application. This code consists of statements that select data from the database according to certain selection criteria. Store the retrieved data in internal tables, structures, or variables and transfer it to the form in one step.
    While you initialize the form, you can format the data, which you passed to the form, for output in the form. Formatting data in the form and not in the data retrieval program allows you to use one data retrieval program for several forms with different formatting routines.
    Result
    You store the application data in internal tables of the data retrieval program. Since you know now which table types occur, you can define a form interface to transfer this data to the appropriate form.
    Describing the Form
    You describe a form using a Smart Form. To do this, use the Form Builder (see also: Graphical User Interface [Seite 15]):
    1.     Describe the interface of the form. It results from the application data previously selected.
    2.     Create one or more pages. On a page, you can position windows, addresses, and graphics. Within a window, you can create additional elements.
    3.     Create elements (text, graphics, tables, and so on) for each page, using other tools of the Form Builder:
         Use the Form Painter [Seite 17] to position windows, graphics, and addresses on a page (the other elements are displayed in an assigned window).
         Use the PC Editor [Seite 19] to write your texts.
         Use the Table Painter [Seite 20] to format your tables.
    For an overview of the elements available on page level, see Node Types: Overview [Seite 23].
    4.     Use the flow control [Seite 50] to control whether and when to print pages and elements.
    Result
    When you activate your Smart Form, the Form Builder generates a function module that encapsulates the form description.
    Form Logic: Introduction
    In the Form Builder you describe a Smart Form by a set of nodes. To do this, you build up a tree structure on the left side of the user interface:
    This graphic already contains some nodes. The node Global Settings as well as its three successors Form attributes, Form interface, and Global definitions always exist for any newly created forms. To describe the Form logic, create a hierarchy under the node Pages and windows. This hierarchy determines the rules used to process the nodes of the tree. Depending on the node type, this could include:
    •     printing the node contents (text, addresses, graphics).
    •     executing the node statements.
    •     executing the successors of a node according to other rules (for example, in a loop).
    You use the form logic to control the flow of the form output. The following rules apply throughout:
    1.     The nodes in the tree structure are processed from top to bottom. This is easier to understand, if you imagine all nodes to be expanded.
    2.     For each node there is a tab, which you can use to link the node to a condition [Seite 51]. If the condition is true, the system processes the node. If not, it skips the node and all its successors.
    3.     You must define a next page for each page. However, you can also go to other pages dynamically (see also: Flow Control [Seite 50]).
    In addition, the page break depends on how much space there is left on the current page.
    For the complete rules for processing the tree structure, see Processing a Form [Seite 63].
    Example for Form Logic
    The diagram below shows the tree structure of the root node Pages and windows:
    The numbering of the nodes also shows the sequence in which they are processed (from top to bottom). The first node is the root node. The successors of a node are all nodes included directly under this node in the hierarchy. For node 5 these are the nodes 6 to 9 (direct successors are only the nodes of the next hierarchy level, that is 6, 7, and 9).
    A node without a successor node is also called end node. Elementary nodes can never have successors (see also Node Types: Overview [Seite 23]). If the condition of node 7 is false, neither node 7 nor node 8 are processed. Processing resumes directly with node 9.
    In this example, we assume that no pages are called dynamically and that there is enough space on the page for the output.
    Using SAP Smart Forms
    Graphical User Interface
    Use
    SAP Smart Forms provide a graphical user interface that helps you create and maintain the layout and the form logic of a form: the SAP Form Builder. You need neither have any programming knowledge nor use a Script language to adapt standard forms. Basic ABAP programming skills are required only in special cases (for example, to call a function module you created or for complex and extensive conditions).
    Features
    The SAP Form Builder of the SAP Smart Forms consists of:
    •     Form Painter for creating the layout of a form,
    •     PC Editor for entering texts and fields into output areas,
    •     Navigation tree for maintaining the form logic,
    •     Table Painter for creating templates and tables,
    •     Form check.
    To define text formats, use style maintenance (transaction SMARTSTYLES;see also Smart Styles [Seite 54]).
    Activities
    The SAP Smart Forms initial screen is the starting point for maintaining forms, styles [Seite 54], and text modules [Seite 54]:
    1.     Choose transction SMARTFORMS.
    The dialog window SAP Smart Forms: Request appears.
    2.     Select Form, Style, or Text module, depending on which object you want to create, display, or change.
    3.     Enter the name of the object.
    4.     Choose Create, Change, or Display.
    Depending on the radio button you selected (Form, Style, Text module), the system branches to the Form Builder, the style maintenance (transaction SMARTSTYLES ), or to the text module maintenance.
    Navigating in the SAP Form Builder
    The screen capture below shows the three different areas of the SAP Form Builder: The navigation tree (hierarchy structure of a Smart Form) on the left, the maintenance screen in the middle, and the Form Painter on the right.
    If you select a tree in the node, the system updates the maintenance screen and marks the relevant window in the Form Painter. You can also select a window in the Form Painter; the system them marks the relevant node in the tree.
    In the tree you determine the hierarchy of the form logic (see also Form Logic: Introduction [Seite 13]); in the Form Painter you determine the layout. If you, for example, move a window in the tree, this does not effect the layout of the Smart Form.
    Tree Navigation
    Selecting a Node
    To select a node in the tree, double-click it. The system updates the maintenance screen accordingly.
    Drag&Drop
    Use Drag&Drop to move (left mouse button) or copy (Ctrl + left mouse button) subtrees.
    Drag&Drop is a "move" operation, consisting of a "cut" and a "paste" operation with its own clipboard. If the node you are moving can be appended either on the same level as the target node or as a successor of the target node, the context menu offers both possbilities.
    Context Menu
    Use the right mouse button to display a sensitive context menu in the tree (that is, depending on the current node type). The following functions exist:
    •     Creating or deleting (only in change mode)
    Depending on the selected node type only valid node types appear.
    •     Clipboard operations (see below), such as cutting, copying to clipboard, pasting from clipboard (only in change mode)
    •     Expanding and collapsing a subtree
    Clipboard
    There are three clipboard operations:
    •     Copy
    Copies the selected node with all its successor nodes into the clipboard.
    •     Cut
    Copies the selected node with all its successor nodes into the clipboard and deletes the copied nodes from the tree.
    •     Paste
    Before pasting, the system checks whether and where you are allowed to append the root node of the clipboard contents.
    Maintenance Screen
    On the maintenance screen you can select different tab pages depending on the node type. For more information see Node Types: Overview [Seite 23].
    Form Painter
    You can suppress or display the Form Painter (choose Form Painter on/off). For more information on how to work with the Form Painter see Graphical Form Painter [Seite 17].
    Form Painter
    Use
    You use the Form Painter to design the layout of the pages of a Smart Form. You can include windows and graphics on a page, determine their positions and choose the window sizes.
    The Form Painter offers the following functions:
    •     Design area with ruler, cursor with help lines, and grid and main grid
    •     Display of the cursor position in the ruler, which you can suppress and set
    •     Two-level grid with engage function, which you can customize at will
    •     When creating, changing, and moving a window, the window size appears in the ruler.
    •     Detachable toolbar containing the most important functions
    •     Autoscrolling when moving windows; placing windows into the background
    •     Zoom factors you can set to any value and autozooming of the design area to the window size
    •     Sensitive context menu
    •     Placing a scanned graphic into the background of the design area (see also Printing Graphics [Seite 31])
    Activities
    To display or suppress the Form Painter choose Form Painter on/off.
    To make detailed settings in the Form Painter (for example, step size of the grid, zoom factors, and so on), choose Settings in its toolbar.
    PC Editor
    You use the PC Editor to enter and format texts and fields.
    Among others, the PC Editor offers the following functions:
    •     Enter, delete, select, cut, and copy texts (see also Entering Text in the PC Editor [Seite 27]).
    •     Assign paragraph and character formats (for a list of the available formats use the list boxes Paragraph formats and Character formats)
    •     Include, change, and delete fields (see also Using Fields in the Form [Seite 42])
    The PC Editor displays fields with a gray background.
    Table Painter
    Use
    You use the Table Painter to design templates and tables in a window (see also Displaying a Table with Static Data [Seite 33]).
    The Table Painter offers the following functions:
    •     Drawing lines and columns
    •     Inserting, cutting, copying, and deleting lines
    •     Deleting cells
    •     Changing cell size and moving cell separator lines
    •     Splitting cells
    •     Selecting table patterns
    Activities
    To display or suppress the Table Painter, choose Table Painter on/off on the Table tab on the maintenance screen of a table or template.
    The design area does not mirror the size of your window into which you include the table. Therefore, remember to check the size in the ruler.
    If you want to insert two tables one after the other, you must create two tables in the window node one after the other.
    To execute a function, mark a cell and choose the function in the context menu (right mouse button).
    To select a table pattern, select the Table tab in the node and choose Select pattern.
    To make detailed settings in the Table Painter (for example, step size of the grid, zoom factors, and so on), choose Settings in its toolbar.
    Style Builder
    The screen capture shows the Style Builder that you use to define Smart Styles. On the left, you see the style tree which consists of predetermined nodes (header data, folder for paragraph formats, folder for character formats). You can navigate between the nodes and create new nodes. On the right, you see the maintenance screen with its tab pages (here, for example, standard settings for the font in the selected color blue). At the bottom you see the preview of the selected font.
    For detailed information on how to create and maintain a Smart Style see Smart Styles [Seite 54].
    Field List and Error List
    Field List
    The field list displays the following data in a tree structure:
    •     all tables, structures, and fields passed via the form interface [Seite 38].
    •     system fields [Seite 43] and fields you defined in the global definitions [Seite 41]
    This allows you to check that you enter the correct field name when you include a field, and that the Smart Form actually knows the field.
    To display the field list, in the Form Builder choose Field list on/off.
    Error List
    When you check the Smart Form and any errors occur, the system displays a list of errors and warnings at the bottom of the maintenance screen. To find the error or warning in the tree, select the node in the second column. The system then goes to the corresponding position in the tree and you can correct the error.
    To check the entire Smart Form choose Check. If an error occurs the error list appears.
    For more information on testing and checking forms see Checking and Testing a Smart Form [Seite 58].
    Node Types: Overview
    When you create a Smart Form, the tree structure of the Form Painter already contains two root nodes:
    •     You use the successors of the Global Settings node to maintain Form attributes, the Form interface, and Global definitions.
    •     You use the successors of the Pages and windows node to create the pages of your form, position elements on these pages, and determine the sequence in which you want to process these elements.
    Apart from the two root nodes, each node has attributes. You can maintain these attributes on tabs on the right half of the screen. The attributes you can maintain on the tabs General Attributes, Output Options, and Conditions are the same for most of the node types (see: Shared Attributes of the Node Types [Seite 24]).
    Successors of Node Pages and windows
    As direct successors to root node Pages and windows you can create only page nodes. The tables below describe these page nodes and the other successors:
    Output areas
    Node type     Description     Possible direct successors
    Page [Seite 25]
    A page of the form. Direct successors of this node can be placed directly on the page.     Window, graphic, address
    Window [Seite 26]
    Output area on a page. There are main windows and subwindows.     All except window and page nodes
    Elementary nodes (without successors)
    Node type     Description
    Text [Seite 26]
    You use this node to print any texts (and table contents), except addresses.
    Graphic [Seite 31]
    You use this node to position graphics in the form. To include background graphics, use node type Page.
    Address [Seite 30]
    You use this node to include an address. The system reads the address data directly from the database tables and formats them for print output.
    Table output
    Node type     Description     Possible direct successors
    Template [Seite 33]
    Output of a table containing static data     All except window, page, table, and template nodes
    Table [Seite 46]
    Output of a table containing application data     As with template node
    Flow control
    Node type     Description     Possible direct successors
    Command [Seite 52]
    Executes special commands (next page, paragraph numbering, printer control)     (no successor)
    Loop [Seite 52]
    Processes successor node repeatedly.     All except window and page nodes
    Alternative [Seite 51]
    Branches depending on condition.     Direct successors are automatically the nodes TRUE and FALSE. The direct successors of these are all nodes except window and page nodes.
    Other nodes
    Node type     Description     Possible direct successors
    Folder [Seite 36]
    Combines successor nodes to logical groups     All except window and page nodes
    Complex section [Seite 60]
    Combines all attributes of the node types template, table, loop, folder     All except window and page nodes
    Program lines [Seite 61]
    Executes ABAP program code (for example, conversion routines).     (no successors)
    Shared Attributes of the Node Types
    The following tab pages are used in common by several node types:
    Tabs for general node attributes
    Name     Description
    General Attributes     Shows contents or description of the node
    Output Options     Contains attributes such as position, style, box and shading
    Conditions [Seite 51]
    Allows to display the node only if certain conditions are true (see also: Flow Control [Seite 50])
    The node types Table, Template, Loop, Folder, and Complex section share a different tab in the place of General Attributes.
    Output Options
    Except for the page nodes in the subtree Pages and windows, you can always use this tab to determine a box and shading for the respective node. Nodes with text output also have the attribute Style. You use this attribute to overwrite for the current subtree the style that was set in the form.
    Depending on where you insert a node, it can have additional output options (for example, if the predecessor is a template [Seite 33]).
    Basic Elements of a Form
    Creating Pages
    Use
    Each form consists of one or more pages. The first page in the tree structure is the start page (when you create a form, the start page already exists). With this page, processing of the form starts.
    When you call pages repeatedly or process pages again because the main window is not filled yet, a page node creates several print pages.
    See also: General Concepts on Form Printing [Seite 7].
    Procedure
    1.     Open the context menu for an existing page node and choose Create  Page.
    2.     Enter a unique name for the node and a description (for example, business terms).
    3.     Determine the format and the mode of the page counter [Seite 53] on the General Attributes tab. In the default setting, the next page is the page itself.
    4.     Determine the print attributes of the page on the Output Options tab (see F1 help).
    5.     Determine a background graphic for the entire page on the Background tab. For information on how to select the graphic see Printing Graphics [Seite 31]. If you do not determine an Output mode in the Output attributes box (in print preview only, on the printer as well), the system ignores the background graphic.
    If you select an output mode, the user can still choose Background graphic in the print preview to display or suppress it.
    Result
    You can now define the page contents. For each page, the Form Painter shows an individual layout. Whether the page is included into the printout depends on whether it is evaluated during form processing [Seite 62] (a page can be omitted even though it is part of the tree structure).
    Creating Windows
    Use
    Windows are output areas for all output data. You can set the size and position of a window graphically in the Form Painter. There are main windows and subwindows [Seite 8]. The most important difference is that the output in a main window can cover several pages.
    After you created a form, a main window already exists on the first page.
    Prerequisites
    A page [Seite 25] exists on which you want to create a window.
    Procedure
    6.     Open the context menu for an existing page node and choose Create  Window.
    If you create the window in the Form Painter using the context menu, you can use the mouse to position it immediately.
    7.     Enter a unique name for the node and a description (for example, booked flights).
    8.     On the General Attributes tab indicate whether the window is a Main window. If you want to create a subwindow, leave the checkbox empty.
    For each page you can indicate only one main window.
    9.     The Position and Size values in the Output options box correspond to the position in the Form Painter. If you want to, maintain other attributes [Seite 24].
    Result
    You can see the window in the Form Painter and in the tree structure. You can always change the specification of the main window or subwindow.
    Positioning Texts on the Form
    Use
    You display all texts in the form using text nodes. The only exception are addresses [Seite 30], which use their own node.
    Integration
    The predecessor node [Seite 14] of the text node determines its use:
    Examples for using text nodes
    Predecessor node     Used to
    Subwindow     Exactly position text on one or more pages
    Main window     Display text in relation to other nodes in the main window; it may cover several pages
    Template     Display texts for table cells of a static table [Seite 33]
    Table     Display table contents
    Header and footer [Seite 49]
    Display column headings and grand totals in tables
    Event node [Seite 48]
    Display subtotals in a table
    Features
    There are the following text types:
    •     Text element: to enter new text in the PC Editor [Seite 27]
    •     Text module: to include a text module [Seite 28]
    •     Include text: to include an existing SAPscript text [Seite 29]
    Positioning the Text
    The position of the text depends on the direct predecessor node (for example, you can assign text of a table cell) as well as on the processing sequence in the tree structure. In addition, you determine output of a text node in relation to the preceding node on the same level [Seite 14]. You can append the text directly to the output of that node or start it in a new paragraph or a new line (select via radiobutton).
    Entering Texts in the PC Editor
    Use
    You use the PC Editor [Seite 19] to enter new text. The position of this text on the form is determined by the predecessor node.
    To include data from the form interface (data from application tables) or system data (date, time) into the text, use system fields or user-defined fields, respectively, in the text (see Using Parameters in the Form [Seite 37]). When processing the form, Smart Forms replace these fields with the corresponding values.
    Procedure
    1.     To create a text node, call the context menu for that node in the tree structure that should receive the text. Then choose Create  Text.
    2.     Enter a unique name for the node and a node description (for example, letter).
    3.     On the General Attributes tab choose Text element as text type.
    Since you edit a text element, an included text, or a text module exclusively using the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    4.     Enter your text in the PC Editor
         either directly on the tab if you use the inplace version of the PC Editor
         or choose Text editor to go to the fullscreen mode of the PC Editor. If, after entering the text, you use the green arrow (F3) to leave the fullscreen editor, the system transfers the text into the inplace version.
    5.     In the Text node box choose whether you want the text to start with a new paragraph or only in a new line. You can also choose to append the text directly to the end of the current paragraph.
    6.     If desired, choose the Output Options [Seite 24] tab to maintain the style or box and shading of the text.
    Result
    The system displays the node in the tree structure, including its name and description.
    Including Text Modules
    Use
    You use the text type Text module of the text node [Seite 26] to refer to an existing text module  [Seite 54]in the system. This allows you to easily use texts from text modules in several forms. In addition, it is not necessary to load the entire form description to maintain these texts.
    You can use text modules in two ways:
    •     Refer to the text module. The text then appears read-only in the PC editor and is included when you print the form.
    •     Copy the text module. The system then copies the text of the module and automatically converts the text node into an editable text element.
    Text modules can be used cross-client and are connected to the transport and translation systems.
    Prerequisites
    The text module you want to include must exist in the system. To create a text module use the SAP Smart Forms initial screen [Seite 15].
    Procedure
    5.     To create a text node, call the context menu for that node in the tree structure that shall contain the text and choose Create  Text.
    6.     Enter a unique name for the node and a description (for example, business terms).
    7.     On the General attributes tab select the text type Text module.
    Since you edit a text element, an included text, or a text module exclusively via the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    8.     Enter the name of the text module in the Text name field. Or click on the black arrow and enter the name of a field to be evaluated dynamically [Seite 37].
    9.     If you want to change the text of the text module for the current form, choose Copy. The Form Builder changes the text type to Text element and copies the text of the module into the PC Editor, where you can edit it. In this case, the original text module remains unchanged.
    10.     Use the checkbox Always copy style from text to determine that the style of the text module is of higher priority than that of the text node or any style inherited from a predecessor. This is important if you specified the name of a field in step 4 (see F1 help).
    11.     If required, use the Output options [Seite 24] tab to maintain attributes for style, box and shading of the text.
    Result
    The system displays the node including name and description in the tree structure. It includes the relevant text itself in the moment the form is processed. If you refer to a text module, it appears in the PC Editor in read-only mode, if you copy it you can edit it.
    Including SAPscript Texts
    Use
    You use the text type Include text of the text node to refer to a SAPscript text that already exists in the system. To identify the text, you need the text name, the text object, the text ID, and the language. Thus, you can easily use the texts in several forms. In addition, you need not load the entire form description [Seite 12] to maintain these texts.
    This text type corresponds to the SAPscript statement INCLUDE. However, Smart Forms do not allow any control statements in include texts. When processing the form, they are simply ignored.
    To administer application-specific form texts, applications use transaction SE75 to define their own text objects with subordinate text IDs. Use text object TEXT with text ID ST to enter general standard texts. To maintain them, use the standard text editor (transaction SO10).
    If there is no need for you to use old SAPscript texts, you better use text modules [Seite 28]. They can be used cross-client and are connected to the transport and translation systems.
    Procedure
    1.     To create a text node, call the context menu for that node in the tree structure that shall receive the text and choose Create  Text.
    2.     Enter a unique name for the node and a node description (for example, letter).
    3.     On the General Attributes tab choose Include text as text type.
    Since you edit a text element, an included text, or a text module exclusively via the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    4.     In the Text key box, identify the include text.
         To identify individual text objects, use the search help in this field.
         The search help of the Text name field allows you include the attributes of SAPscript texts into the search.
    7.     If required, use the Paragraph formats box to format the include text:
         The style assigned to the text node contains a format for the standard paragraph ('*'). If you enter a paragraph format in the Standard paragraph field, this format overwrites the style format for all standard paragraphs in the include text that use this paragraph format.
         Use the First paragraph field to set a paragraph format for the first paragraph of the include text. This format also overwrites the format set in the style. If you set the First paragraph field but leave the Standard paragraph field empty, the system uses the format set in the First paragraph field for any standard paragraphs in the include text.
    6.     In the Text node box choose whether you want the text to start in a new paragraph, in a new line, or directly at the end of the current paragraph.
    7.     If desired, choose the Output Options [Seite 24] tab to maintain the style or box and shading of the text.
    Result
    The system displays the node in the tree structure, including its name and description. The included text is included only at the moment the form is processed.
    Inserting Addresses
    Use
    In many applications, addresses are administered using the Central Address Administration [Extern]. Depending on how the address is used, the application uses a particular address type [Extern]. The addresses are stored in the database tables of the central address administration and identified by the application via a number.
    You use the address node to insert an address into the form. This guarantees that the address is formatted according to the postal rules of the sender country.
    Prerequisites
    Your application must administer addresses using the central address administration. Otherwise you must use the text node [Seite 26] to insert your addresses.
    Procedure
    1.     To create an address node, call the context menu for that node in the tree structure that you want to contain the text and choose Create  Text.
    Create the address node as direct successor of the page node or use the context menu in the layout of the Form Painter. You can then position the address anywhere on the page.
    2.     Enter a unique name for the node and a description (for example, customer address).
    3.     Determine the address type on the General attributes tab.
    For a description of how to determine the address type dynamically and how to use fields instead of fixed values, see Using Parameters in the Form [Seite 37].
    4.     For organization addresses you must specify only an address number. For any other address types, you must specify a person number and an address number. To do this, use the search help.
    5.     In the box Additional address specifications you can maintain other attributes to specify how you want to display the address:
         Use field Output starts with paragraph to set the paragraph format of the style that you want to use to display the address.
         If the number of lines you specify in the field Number of lines to be used is smaller than the number of lines required to display the address, the central address administration suppresses lines of the address.
         As default, the system uses as sender country the country that was specified when creating the address. You can use the parameter Sender country to overwrite this setting.
         For addresses that have a P.O. box as well as a street address, use the other fields in the box to determine which of these addresses to display.
    6.     If desired, you can use the Output Options [Seite 24] tab to maintain attributes for style, box, and shading of the text. In addition, you can set values for position and size of the output area (instead of in the Form Painter).
    Result
    The system displays the node including name and description in the tree structure. If you insert the address as direct successor of a page or by using the Form Painter, the system displays an extra output area for the address. The address itself is inserted only at the moment the form is processed. You cannot view it in the Form Builder.
    Printing Graphics
    Use
    You use the graphic node to display graphics, such as a company logo, on the form. For performance reasons, make sure that the graphics are held in the printer memory. SAP Smart Forms support this method, provided that:
    •     The printer can be controlled accordingly.
    •     There is enough memory space on the printer.
    •     You activated this property in transaction SE78 (see below).
    In this case, the system sends the graphics to the printer only once during one print job.
    To include background graphics, use the Background graphic tab of a page node.
    Prerequisites
    You use the SAPscript Graphic Administration (transaction SE78) to import graphics into the SAP-System:
    1.     Double-click on a graphic format in the tree structure in the forder Document server  GRAPHICS General graphics.
    2.     Choose Graphic  import.
    The transaction imports the graphic and stores it on the Business Document Server (BDS). Now you can display it on a form.
    See also: Graphic Administration [Seite 65]
    Procedure
    1.     To create a graphic node, call the context menu for that node in the tree structure that you want to contain the graphic and choose Create  Graphic.
    Create the graphic node as direct successor of the page node or use the context menu in the layout of the Form Painter. You can then position the graphic anywhere on the page.
    In the Form Painter the system displays a small box for the newly created node.
    2.     Enter a unique name for the node and a description (for example, company logo).
    3.     On the General Attributes tab determine whether you want to include a colored graphic or a graphic in black and white.
    4.     Use the fields Object, ID, and Name to identify the graphic. Use F4 help of the Name field to copy the values of these fields. If you copy them with ENTER, the system displays the graphic in the Form Painter.
    The box for the graphic in the Form Painter also contains the name of the graphic node, which in part overlays the graphic.
    5.     In the Technical Attributes box determine the graphic resolution according to what the printer supprts. Small resolutions increase the size of the graphic on the form, higher resolutions reduce the size.
    6.     For graphic nodes that are displayed in a window, there is a box Horizontal position in addition to the general output options [Seite 24]. The parameters Reference point and Alignment determine the horizontal position in the window, while the vertical position is determined by the previous output in the window.
    At present, you cannot overlay graphics with text. However, if you use a template node [Seite 33], you can display graphics and text side by side.
    Result
    The system displays the node with name and description in the tree structure. If you insert a graphic as direct successor of a page or if you used the Form Painter, the system displays the graphic. Graphics in windows are inserted only when the form is processed. You can therefore not see them in the Form Builder. In addition, the system automatically dispalys the graphic on the next page if there is not enough space left on the current page.
    Displaying a Static Table
    Use
    Use node type Template to display a table whose layout and size (number of lines and columns) is determined before the runtime of the print program.
    To create a template, define a table layout to determine the cell structure for each line. The cells are used to display the contents of the successor nodes of the template node. This allows you to position text and a graphic side by side (see Displaying Graphics in Templates [Seite 36]).
    The template node is also suited for label printing.
    Integration
    You can use system fields or your own fields  for example, to display the current date  in table cells (see also Using Parameters in the Form [Seite 37]).
    To display application data, use the table node. For this node type the number of table lines to be displayed is not known before the form is actually printed (the number depends on the volume of application data selected in the data retrieval program [Seite 38]).
    Prerequisites
    You can create a template node only as a successor to a window node. If you want to display the template in a particular area of the page, create a subwindow for it. Otherwise, use the main window.
    Features
    The node type displays a table layout [Seite 34]. You can either enter the table layout directly or use the Table Painter to define it.
    To set other attributes, use the attributes the node types share [Seite 24].
    Activities
    To use a template, you must:
    1.     Define the table layout [Seite 34].
    2.     Display contents in the table cells [Seite 35].
    Defining the Table Layout
    Use
    You use the table layout to determine:
    •     The number of lines and cells
    •     The height of each line
    •     The width of each cell
    •     The alignment of the table in the window
    •     Whether and where to display separator lines or frames
    Procedure
    Create a template node and maintain the attributes Width, Horizontal alignment, and Vertical alignment (See F1 help).
    Use the table control on the Template tab to define the layout of the lines. Each line of the template must have a definition. You can use one line in the table control to define either the layout of one template line or a common layout for several template lines:
    •     Use the columns From and To to specify the lines of your template, for which the definition applies. The numbering starts with 1. The intervals in the line definition may neither overlap nor leave gaps.
    •     The Height you specify applies for all cells of this line. Specify a Width for each cell you want to display. The sum of the width values must amount to the specified Width of the template.
    •     You can reuse the Name of the template line for other lines of the same template. Enter it in the Reference column of the desired lines. The system then copies the values you specified for the line height and the individual cell widths.
    Use the Pattern box to select the desired table pattern.
    Example
    You define the following lines in the table control (in the example without measurement units):
    Name     From     To     Reference     Height     1.     2.     3
    Line1_2     1     2          1     1     2     3
    Line3     3     3          2     2     2     2
    Line4     4     4     Line1_2     1     1     2     3
    You use the Pattern box to specify that all cells are separated by visible lines and that the template is framed.
    Result
    On the form, the template may look like this:
    Displaying Contents in Cells
    Use
    The template node defines the table layout [Seite 34]. The successor nodes of the template node determine the data to be displayed in the table cells.
    Prerequisites
    You already created a template node as successor of a window node and defined the table layout.
    Procedure
    1.     Use the context menu of the template node to create successor nodes.
    For clarity reasons create one folder node [Seite 36] for each line. The folder node is an outline node that you can use to combine related nodes. For folder nodes, you need not fill in the input fields in the Output structure box (see next step).
    2.     The Output options tabs of the inserted nodes now contain an additional box Output structure with the fields Line and Column. Assign each node to the cell in which you want the output to appear.
    You can assign several nodes to one cell. The output sequence within the cell is determined by the sequence of the nodes in the tree.
    Result
    The system displays the contents in the print preview or prints them, respectively.

  • Query on delta process

    Hi BW Experts,
    For AP(Accounts payable),AR(Accounts receivable) we can run delta process to pick delta records. How?
    Could anyone please let me know?
    Thanks

    FI extractors are worked on after image delta. Delta records are diractly selected from the R/3 tables using a time stamp mechanism.delta records are diractly transfored to bw no need to writen to the bw Plz go through reg FI OFI_Gl_4,OFI_AP_4,OFI_AR_4 0FI_GL_4 (G/L Accounts: line items) No redundant fields are transferred into BW: Only fields from the FI document tables (BKPF/BSEG) that are relevant to general ledger accounting (compare table BSIS), No customer or vendor related fields. 0FI_AP_4 (AP: line items) and 0FI_AR_4 (AR: line items) Vendor / Customer related information (e.g. payment/dunning data). “Coupled” consistent “snapshot” of FI data in BW:extraction G/L account extraction determines selection criteria (comp.code, fiscal period) and upper time limit of all extracted FI line-items. AP and AR extraction: no further selection criteria necessary / possible. “Uncoupled” extraction possible with PlugIn PI 2002.2, see OSS note 551044. 0FI_GL_4, 0FI_AP_4, 0FI_AR_4 use an After Image Delta Delta type “Extractor“: Delta records are directly selected from the R/3 tables using a timestamp mechanism. Delta records are directly transferred to BW. No record is written to the BW delta queue. After Image Delta: FI line items are transferred from the source system in their final state (= “After Image“). This delta method is not suitable for direct InfoCube update. ODS object is obligatory to determine the delta for InfoCube update. Delta queue and BW scheduler ensure correct serialization of the records (e.g. inserts must not pass changes) Distribution of delta records to multiple BW systems. Selection criteria of Delta-Init upload are used to “couple” the datasources logically. time mechanism... New FI documents Posted in R/3 since the last line-item extraction. Selection based on the field BKPF-CPUDT. Hierarchy Extractor for Balance Sheet & P&L Structure Technical name: 0GLACCEXT_T011_HIER Technical Data Type of DataSource Hierarchies Application Component FI-IO Use The extractor is used for loading hierarchies (balance sheetl/P&L structures) for the characteristic (InfoObject) 0GLACCEXT. Fields of Origin in the Extract Structure Field in Extract Structure Description of Field in the Extract Structure Table of Origin Field in Table of Origin .INCLUDE ROSHIENODE RFDT CLUSTD FIELDNM RSFIELDNM RFDT CLUSTD GLACCEXT GLACCEXT RFDT CLUSTD RSIGN RR_RSIGN RR_PLUMI RFDT CLUSTD PLUMI ROSHIENODE RFDT CLUSTD Features of Extractor Extractor: FBIW_HIERARCHY_TRANSFER_TO Extraction structure: DTFIGL_HIERNODE_1 Financial Accounting: Line Item Extraction Procedure General Information About the Line Item Extraction Procedure BW Release 3.1 makes consistent data extraction in the delta method possible for line items in General Ledger Accounting (FI-GL), and selected subsidiary ledgers (Accounts Receivable FI-AR and Accounts Payable FI-AP) and tax reporting. The extraction procedure delivered with BW Release 2.0B, based on DataSources 0FI_AR_3 and 0FI_AP_3 , can be replaced. This is described in note 0410797. The decisive advantage of choosing R/3 line item tables as the data source is that extra fields can be transferred to the BW. These were not available with transaction figures from table GLTO, the previous R/3 data source in General Ledger Accounting FI-GL. This provides more extensive and flexible analysis in BW. To enable you to assure consistent Delta data, four new InfoSources are provided in the OLTP system (with the corresponding DataSources and extractors in the SAP R/3 system): Application InfoSource Description FI-GL 0FI_GL_4 General Ledger: Line Items FI-AP 0FI_AP_4 Accounts Payable: Line Items (Extraction Linked to 0FI_GL_4) FI-AR 0FI_AR_4 Accounts Receivable: Line Items (Extraction Linked to 0FI_GL_4) FI-TX 0FI_TAX_4 General Ledger: Data for Tax on Sales/Purchases For the General Ledger, selection is made from tables BKPF and BSEG, while selection for the subsidiary accounts is made from tables BSID/BSAD (Accounts Receivable) and BSIK/BSAK (Accounts Payable). InfoSource 0FI_GL_4 transfers only those fields that are relevant for General Ledger Accounting from the Financial Accounting document (tables BKPF and BSEG) to the BW system. The consisten recording of data from General Ledger Accounting and Subledger Accounting is provided by means of coupled delta extraction in the time stamp procedure. General ledger accounting is the main process in delta mode and provides subsidiary ledger extraction with time stamp information (time intervals of previously selected general ledger line items). This time stamp information can also be used for a loading history: this shows which line items have previously been extracted from the SAP R/3 system. Delta Method Delta extraction enables you to load into the BW system only that data that has been added or has changed since the last extraction event. Data that is already loaded and is not changed is retained. This data does not need to be deleted before a new upload. This procedure enables you to improve performance unlike the periodic extraction of the overall dataset. Financial Accounting line items are read by extractors directly from the tables in the SAP R/3 system. A time stamp on the line items serves to identify the status of the delta data. Time stamp intervals that have already been read are then stored in a time stamp table. The delta dataset is transferred to the BW system directly, without records being transferred to the delta queue in the SAP R/3 system (extraktor delta method). The Financial Accounting line items are extracted from the SAP R/3 system in their most recent status (after-image delta method). This data method is not suitable for filling InfoCubes directly in the BW system. To start with therefore, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes) can be provided with data from this ODS object. Time Stamp Method With Financial Accounting line items that have been posted in the SAP R/3 system since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT). When a delta dataset has been selected successfully, the SAP R/3 system logs two time stamps that delimit a selection interval for a DataSource in table BWOM2_TIMEST: Field Name Key Description MANDT X Client OLTPSOURCE X DataSource AEDAT X SYSTEM: Date AETIM X SYSTEM: Time UPDMODE Data update mode (full, delta, deltainit) TS_LOW Lower limit of the time selection (time stamp in seconds since 1.1.1990) TS_HIGH Upper limit of the time selection (time stamp in seconds since 1.1.1990) LAST_TS Flag: 'X' = Last time stamp interval of the delta extraction TZONE Time zone DAYST Daylight saving time active? The time stamps are determined from the system date and time and converted to the format seconds since 1.1.1990, taking into account the time zone and daylight saving time. To ensure correct and unique reconversion to date and time, the time zone and daylight saving time must be stored in table BWOM2_TIMEST. Table BWOM2_TIMEST therefore serves to document the loading history of Financial Accounting line items. It also provides defined restart points following incorrect data requests. To provide a better overview, the time stamps in the example table are entered in the date format. The columns TZONE and DAYST were left out. OLTPSOURCE AEDAT/AETIM UPD DATE_LOW DATE_HIGH LAST_TS 0FI_GL_4 16 May 2000/20:15 Init 01 Jan. 1990 15 May 2000 0FI_GL_4 24 May 2000/16:59 Delta 16 May 2000 23 May 2000 0FI_GL_4 02 June 2000/21:45 Delta 24 June 2000 01 June 2000 0FI_GL_4 15 June 2000/12:34 Delta 02 June 2000 14 June 2000 0FI_GL_4 21 June 2000/18:12 Delta 15 June 2000 20 June 2000 X 0FI_AP_4 18 May 2000/21:23 Init 01 Jan. 1990 15 May 2000 0FI_AP_4 30 May 2000/12:48 Delta 16 May 2000 23 May 2000 0FI_AP_4 10 June 2000/13:19 Delta 24 June 2000 01 June 2000 X 0FI_AR_4 17 May 2000/18:45 Init 01 Jan. 1990 15 May 2000 0FI_AR_4 04 June 2000/13:32 Delta 16 May 2000 01 June 2000 0FI_AR_4 16 June 2000/15:41 Delta 02 June 2000 14 June 2000 X 0FI_TX_4 17 May 2000/18:45 Init 01 Jan. 1990 15 May 2000 0FI_TX_4 04 June 2000/13:32 Delta 16 May 2000 01 June 2000 0FI_TX_4 16 June 2000/15:41 Delta 02 June 2000 14 June 2000 X Constraints Per day, no more than one delta dataset can be transferred for InforSource 0FI_GL_4. The extracted data therefore has the status of the previous day. For further data requests on the same day, the InfoSource does not provide any data. In delta mode, data requests with InfoSource 0FI_AR_4 and InfoSource 0FI_AP_4 do not provide any data if no new extraction has taken place with InfoSource 0FI_GL_4 since the last data transfer. This ensures that the data in the BW system for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as the data for General Ledger Accounting. If you delete the initialization selection in the source system for InfoSource 0FI_GL_4 in the BW system Administrator Workbench, the time stamp entries for InfoSources 0FI_GL_4, 0FI_AP_4, 0FI_AR_4 and OFI_TX_4 are also removed from table BWOM2_TIMEST. Recording Changed Line Items In the case of Financial Accounting line items that have been changed since the last data request in the SAP R/3 system, there is no reliable time stamp that can document the time of the last change. For this reason, all line items that are changed in a way relevant for BW must be logged in the SAP R/3 system

  • Repeat delta extraction

    Hi,
    The Finance data is not coming to BW system.We are suppsed to repeat delta extractions.Can anyone tell me how I can proceed?

    Hi Prithwish......
    A cube will never be in Overwrite mode.........cube is always additive........due to this in some Delta Process.....we need an ODS inbetween.......bcoz in ODS both the Update mode is possible ie Overwritten or Additive......for an example........An after image provides the status after the change, a before image the status before the change with a minus sign. A reverse image sends the
    record with a minus sign too, indicating at the same time that it is to be deleted. The data packages are serialized in the process. The delta process controls whether adding or overwriting is allowed. In this case, both adding and overwriting is allowed. This process permits data to be updated in a DataStore object and in an InfoCube.
    In case of ODS.............if u r in BI 7.0 then check the update mode in Transformation and if u r in BW 3.X.....then check in Update rule......
    Regards,
    Debjani....

  • Repeat delta - thanks

    Hello thanks for the threads,it really helped me a alot,and also thanks for SRS,but i was left with small confusion after after reading all,
    1.is there any difeerence for repeat delta for Master data,transactional data and time stamps.
    2.if there is option repeat delta in rsa7,cant we go with that option.
    kindly help me

    1. If any failures happens to the delta load then repeat of the delta can be done. It should be first done in BW side by forcing the request to red and deleting it from target. Tehn if you trigger the IP it will ask for a pop up which pulls in the failed delta records again. there is no difference in process between master and transactional repeat delta. SOme datasource doesnt not support repeat delta option if thats the case then you need to do init and then continue with delta's
    2. Yes u can. But itz advisable to pull it from BW side.
    Regards,
    B

  • Duplication of data in BI, with 0FI_GL_10" which has a AIED delta process.

    Hi,
    I need some help!!
    In my actual proyect, we are using DS "0FI_GL_10", which has a AIED delta process. Someone knows, if this configuration could carry on any type of extraction problem, such as a duplication of data in BI? This is what it is happening in my proyect. In the inic of "0FI_GL_10", I extract "one" record, and after a few days when I run a delta extraction, I have a new same record in the PSA, (with the same key fileds and attributes than the other). Also, in my tranformation rule, that link my PSA with a DSO, the key figure 0SALE is parameterized as summation in the aggregation, this is wrong and or i have to use a overwrite aggregation? or my problem is in the type on process delta that has the extractor "0FI_GL_10"?
    Thanks in advance for any kind of help.
    Regards,
    Juan Manuel

    Hi
    There are chances that this datasource might send in the same records when run in delta mode and that is the reason a DSO is needed with overwrite mode in between.
    Also there are a couple of notes stating problems related to this datasource.
    Note 1002272,1153944, 1127034
    Refer this if you are having specific issues with this datasource
    Hope this helps
    Gaurav

  • SAP BW Purchasing - Scheduling Agreement delta processing

    Hi,
    I have a question about Scheduling Agreements coming from ECC to BW with delta processing.
    When a goods receipt happens for a Scheduling Agreement item, it registers process key 2.
    However, it seems that when a second goods receipt happens for that same scheduling agreement item, the old goods receipts updates with a process key 4, and the new receipt takes the process key 2 when we aggregate at an InfoCube level. In the first level write optimized DSO, the process keys are in tact for every line item & schedule line (all goods receipts process key 2 are there).
    Can somebody confirm this logic?
    We are having issues because we need all of that goods receipt history stored in our InfoCubes, and we do not know how to resolve. Please help! Points will be assigned...
    Thanks very much,
    Courtney

    are you saying that Process Key is 2 for both the good reciepts in write optimized DSO but in cube, first good reciept is having a process key 4 when second good reciept is also there?
    If yes, it seems that problem is with the info object for process key - is it a Key Figure or characteristic?
    It should be a characteristic so that the value is not added but overwritten.
    you are doing a full or delta from Data Source to DSO and DSO to Cbue?
    Regards,
    Gaurav

  • Repeat Delta in case we loss the data from BWP

    Dear Experts
    I am facing a critical Problem related to Delta records uploading in BWP server. I have uploaded the Delta records yesterday (16.06.2011) in the Morning from (6.00A.M. to 14.00P.M) and pull the delta records in SAPBW. then in the night due to some reason our BWP server crashed. Now its Up and the data is restored upto 16.06.2011 Morning upto 06.00 A.M. i.e. before the execution of process chains on 16.01.2011 . My Question is
    1. If I execute the Process chains today will it breing the Delta records of 16.06.2011 as well (Repeat delta) Automatically or do i have to perform some configration.
    2. Whether the Repeat delta is possible only if we make the request RED and not when we loose the data as we have.
    Pl advice Urgently........................
    Thanks in advance.
    Dinesh Sharma

    1. delta load done to PSA. records edited and loaded to targets.
    2. repeat delta done to PSA. It contains all records from step 1 and any new records written to delta queue. this is deleted.
    3. Next day repeat happens. This brings records from step 2 (already has records from step 1) and any new records written to delta queue.
    The procedure followed was not correct and hence resulted in duplicates. When a repeat delta is done, the delta records from the previous delta request will be fetched along with any new records that have come into the queue after that.

  • Need Information On R12 Error tables.

    Hi Friends,
    I need information on R12 Error Tables and Staging Error tables. Can you please send me any documention on this.
    Little bit urgent.
    Thanks

    Thanks for you Reply.
    Actually i am new to Apps. I am a OBIEE Developer. Here i will tell you the process. From Flat files to Staging area they are Loading the Data using some Scripts. After that they are using some concurrent programes for clensing the data and load them in to the Interface Tables. Then Those tables are loaded in to the Main oracle Tables.
    Mean while when they loading the data from staging to Interface they clensing the data. If Any errors occur they are moving those tables into some Built in Tables like (MTL_Interface_Errors). This is the process.
    And i don't know how to find the error tables..
    Thanks.
    Edited by: 806756 on Nov 9, 2011 1:34 AM

Maybe you are looking for

  • Performance Issues with large XML (1-1.5MB) files

    Hi, I'm using an XML Schema based Object relational storage for my XML documents which are typically 1-1.5 MB in size and having serious performance issues with XPath Query. When I do XPath query against an element of SQLType varchar2, I get a good p

  • I am getting an error message -41 when I try to send my project to IDVD

    I am getting and error message - 41 when i try to send my video project to IDVD. Does anyone know what i have to fix?

  • Report not displyed in web page

    Hi All, I am trying to execute the report in Query designer and when i click on execute button the internet explorer pops up with about blank page.Is thery any specific settings  i need to make in order to display the report in web page.Please provid

  • What is Business one ?

    Hi Guys, I am basically PI developer and our company is planning to use the business one. Can somebody give an over view of this product. For what purpouse it is used and what are the skills required to work on this ? any links or suggestions would b

  • Exceptions in FM in update task

    Hi, Do you know if it's possible to raise excptions in a Function Module called in Update Task mode ? Thanks