XSQL and basic flow control

Hello again,
Is there any mean to execute more that one time the same XSQL action-element, like this (future XSQL version?):
<xsql:for-each test="{@selectedITEMS}">
<xsql:dml>
DELETE FROM ITEMS
WHERE ItemID = {.}
</xsql:dml>
</xsql:for-each>
Yes the duty can still be transferred outside XSQL, in the form of a DB proc or a custom action-element, but if some form of basic flow control exists/ed here inside XSQL, this would certainly come in handy!
Thanks
JRoch

A simple way to do this would be to write an action handler that processes the value of the "selectedITEMS" parameter and sets a page-private parameter to the equivalent value with commas between them, then do:
<xsql:dml>
delete from items
where ItemId IN ({@ListOfLitems})
</xsql:dml>
then you do it all in one trip to the database.

Similar Messages

  • Problems with parity and flow control using visa serial

    I am trying to create a basic user interface with the options that my
    company uses most often for a force indicator.  You can configure
    the indicator over serial, as well as read the values off the
    indicator.  I am trying to create the user interface so that using
    producer/consumer loops with events, once you change a value, it will
    write that new value to the serial port, ie the device. 
    The problem I am having is transfering the parity and flow control
    values for the serial config to the Basic read write VI.  The
    problem is that once the consumer loop executes, it will write the
    values correctly to the VI, but then the outer loop executes 200 ms
    later and clears the values.  I know that this is normal behavior
    and that in order to keep the values stored, normally you would use a
    shift register.  I tried to use this and had some issues with
    correct data types/array mis-mtaches, ets, so I created an indicator
    and had a local vaible read the indicator, which seems to be working
    for the stop bits, read bits, baud rate, etc, but not the parity anf
    flow control.  I always get "blank" outputs for theses values (if
    you enable the digital display you can see that they are outputing the
    value 0 which correspondes to None in both cases, which is
    correct).  Even though it appears that it is outputting the
    correct value, I get an error that says the VISA property is
    invalid.  I initally did a search and found that my stop bit
    control was wrong (outputting double instead of integer), but I could
    not find anything on the parity/flow control issue.  I even tried
    to copy the serial config controls from the basic serial read/write to
    my dialog box and that did not work either.
    I would be grateful for any suggestions.
    Thanks
    Kenny
    Kenny
    Attachments:
    BGI_main pandc.zip ‏232 KB

    I should add that I am using LV 8.0 and that the serial config
    indicator in the consumer loop will be off the frontpanel in the final
    VI so that it is not visible to the user.
    Kenny

  • Basic Flow Of SD and T-Codes , Tables

    Hi
    Im SA-BW Consultant . I want some basic knowledge for SD . I mean the flow of SD and Basica Tables and transactions .
    Pls let me know
    kumar

    Hi Ravi Kumar,
    SD Flow Cycle:
    INQUIRY ( VA11)
    |
    QUOTATION (VA21)
    |
    PURCHASE ORDER (ME21)
    |
    ORDER CONFIRMATION (VA01)
    |
    PICKING LIST – (VL36)
    |
    PACKING LIST - (VL02, VL01)
    |
    SHIPPING – (VT01)
    |
    INVOICE – (VF21, VF01)
    |
    AR
    SD FLOW OVERVIEW:
    Sales
    Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.
    Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.
    Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.
    The sales area that accepts the inquiry is responsible for completing the agreement.
    Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.
    b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).
    c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.
    Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
    Sales Order Management Transactions
    SALES ORDER PROCESSING
    Creating Sales Order - VA01
    Maintaining a Sales Order - VA02
    Displaying a Sales Order - VA03
    Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1
    Display List of RMAs by Customer - VA05
    Confirm RMA Goods Receipt - VL02
    Generate list of open return orders for deletion - VA05
    Display Customer returns eligibility - MCSI
    Removing a Billing Block (Approving Credit/Debit Requests) - V.23
    PRICING MASTER DATA
    Create Pricing - VK11
    Creating a Sales Deal - VB21
    Maintaining a Sales Deal - VB22
    Displaying a Sales Deal - VB23
    Maintaining Prices - VK12
    Displaying Prices - VK13
    MATERIAL MASTER DATA
    Creating Material Substitution Master Data - VB11
    Maintaining/Deleting Material Substitution Master Data - VB12
    Displaying Material Substitution Master Data - VB13
    Creating a Bundled Master - MM01
    Creating a Sales BOM - CS01
    Maintaining a Sales BOM - CS02
    Displaying a Sales BOM - CS03
    CUSTOMER MASTER DATA
    Creating Partner Records - XD01
    Maintaining Customer Master Data - XD02
    Displaying Customer Master Data - XD03
    Deactivating a Partner - VD06
    CUSTOMER CREDIT INFO
    Creating/Maintaining New Customer Credit Information - FD32
    Displaying Customer Credit Information - FD33
    Blocking or Unblocking a Customer - VD05
    SHIPPING
    Creating a Delivery - VL01N
    Displaying a Delivery - VL03N
    Changing a Delivery - VL02N
    Shipment Inquiry / Display - VT03
    Adjusting Transfer Order - Confirmation Quantity - LT12
    Collectively Confirm Transfer Order - LT25
    Batch Shipment Confirmation - VL19
    PGI Reversal Cancellation - VL09
    Creating Service Provider/Carrier Master Data - XK01
    Maintaining Serive Provider/Carrier Master Data - XK02
    Displaying Service Provider/Carrier Master Data - XK03
    Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02
    IDoc Inquiry - WE02 / WE05
    BILLING
    Invoicing a Customer Shipment - VF01
    Reprinting an Invoice - VF31
    Releasing a Sales Order for Billing - V.23
    Creating an Invoice by Using the Billing Due List - VF04
    Checking Open Billing Documents - VF05
    Create Credit/Debit Memo - FB01
    A/R
    Controlling Total Debit/Credit bkgs - F.03
    Generate FI Account balance - F.08
    Generate Month-to-date Inv. register - F.02
    Process payments - FBZ1
    Rqst Individual Customer Corresp. - FB12
    Generate Customer Correspondence - F.61
    Enter Batch totals under Control ttl - FB07
    Display G/L Acct. totals - FBL3N
    Reverse Posted Amounts - FB08
    Customer Refunds - FBL6
    Customer Refund to other than Payer - FB05
    Clearing Debit/Credit on Cust. acct. - FB1D
    Customer Balance in Local Currency - F.23
    G/L Account Balance Report - F.08
    Create Invoice - legal entity adjust - FB01
    Generate Cust. Acct. statements - F.27
    Generate Dunning Letters - F150
    Generate Billing Due List - VF04
    Generate Blocked Billing Doc list - VFX3
    Inq. via Credit Release Screen - VKM1
    List orders by partner - VA05
    Past Due invoices by customer - FD11
    Check number info by G/L account - FBL3N
    Display customer Line items - FBL5N
    SD TABLES:
    Important Tables for SAP SD
    Sales and Distribution:
    Customers : Table Description
    KNA1 General Data
    KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
    KNB4 Customer Payment History
    KNB5 Customer Master – Dunning info
    KNBK Customer Master Bank Data
    KNKA Customer Master Credit Mgmt.
    KNKK Customer Master Credit Control Area Data (credit limits)
    KNVV Sales Area Data (terms, order probability)
    KNVI Customer Master Tax Indicator
    KNVP Partner Function key
    KNVD Output type     
    KNVS Customer Master Ship Data
    KLPA Customer/Vendor Link
    Material Master:
    MARA Material master
    MAKT Material text
    MARC Material per plant / stock
    MVKE Material master, sales data
    MARD Storage location / stock
    MSKA Sales order stock
    MSPR Project stock
    MARM Units of measure
    MEAN International article number
    PGMI Planning material
    PROP Forecast parameters
    MAPR Link MARC <=> PROP
    MBEW Material valuation
    MVER Material consumption
    MLGN Material / Warehouse number
    MLGT Material / Storage type
    MPRP Forecast profiles
    MDTB MRP table
    MDKP Header data for MRP document
    MLAN Tax data material master
    MTQSS Material master view: QM
    Sales Documents
    VBAKUK VBAK + VBUK
    VBUK Header Status and Administrative Data
    VBAK Sales Document - Header Data
    VBKD Sales Document - Business Data
    VBUP Item Status
    VBAP Sales Document - Item Data
    VBPA Partners
    VBFA Document Flow
    VBEP Sales Document Schedule Line
    VBBE Sales Requirements: Individual Records
    VBKA Sales activities
    VBFA Sales Document Flow
    Logical databases: AAV, AKV, ARV, VFV
    Sales requirements
    VBBE Sales Requirements: Individual Records
    VBBS Sales Requirement Totals Record
    SD Delivery Documents:
    LIPS Delivery Document item data, includes referencing PO
    LIKP Delivery Document Header data
    Shipping:
    VTTK Shipment header
    VTTP Shipment item
    VTTS Stage in transport
    VTSP Stage in transport per shipment item
    VTPA Shipment partners
    VEKP Handling Unit - Header Table
    VEPO Packing: Handling Unit Item (Contents)
    VTFA Flow shipping documents
    Billing Document:
    VBRK Billing Document Header
    VBRP Billing Document Item
    SD Shipping Unit VEKP Shipping Unit Item (Content)
    VEPO Shipping Unit Header.
    Pricing:
    KONAIND Index: Groups of Conditions/Header Record Conditions
    KOND Conditions (Data)
    KOND3 Conditions: Campaign Determination - Data Part
    KONDD Material Substitution - Data Division
    KONDDP Conditions: Additional Materials for Material Determination
    KONDH Conditions: Batch Strategy - Data Division
    KONDI Conditions: Data part for certificates
    KONDIND General Document Index for Conditions
    KONDN Conditions: Free goods - Data section
    KONDNS Conditions: Free goods determination - scales
    KONDP Conditions: Packing Object Data Section
    KONDR Conditions: Derivation strategy - data part
    KONDRPR Conditions: Derivation strategy - recipient item data
    KONDRPS Conditions: Derivation strategy - sender item data
    KONDV Conditions: Data part for certificates
    KONH Conditions (Header)
    KONM Conditions (1-Dimensional Quantity Scale)
    KONP Conditions (Item)
    KONV Conditions (Transaction Data)
    KONW Conditions (1-Dimensional Value Scale)
    KOTN900 LSI Free Goods Condition Table
    KONV Conditions for Transaction Data
    KONP Conditions for Items
    LIKP Delivery Header Data
    LIPS Delivery: Item data
    VBAK Sales Document: Header Data
    VBAP Sales Document: Item Data
    VBBE Sales Requirements: Individual Records
    VBEH Schedule line history
    VBEP Sales Document: Schedule Line Data
    VBFA Sales Document Flow
    VBLB Sales document: Release order data
    VBLK SD Document: Delivery Note Header
    VBPA Sales Document: Partner
    VBRK Billing: Header Data
    VBRP Billing: Item Data
    VBUK Sales Document: Header Status and Administrative Data
    VBUP Sales Document: Item Status
    VEKP Handling Unit - Header Table
    VEPO Packing: Handling Unit Item (Contents)
    VEPVG Delivery Due Index
    Bill of Material:
    MAST Material to BOM Link
    EQST Equipment to BOM Link
    STAS BOMs header
    STKO BOM header
    STPN BOM follow-Up control
    STPO BOM item
    STPU BOM sub-item
    STST Standard BOM link
    STVB Bills of material - Serialization of posting
    STZU Permanent BOM data
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.

    how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
    please explain the important questions.

    How to deal with table control / step loop in BDC
    Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
    Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
    Demo ABAP code has two purposes:
    1. how to determine number of visible lines and how to calculte page number;
    (the 'calpage' routine has been modify to meet general purpose usage)
    2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
    Now I begin to describe the step to implement my method:
    (I use transaction 'ME21', screen 121 for sample,
    the method using is Call Transation Using..)
    Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
    (Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
    Now we have : FixedLine = 9
                  LoopLine  = 2(for table control, LoopLine is always equal to 1)
    Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
    Now we have: FirstLine = 0
              or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
    Step3: write a subroutine calcalculating number of pages
    (here, the name of actual parameter is the same as formal parameter)
    global data:    FixedLine type i, " number of fixed line on a certain screen
                    LoopLine  type i, " the number of lines occupied by one steploop item
                    FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new                                                               " scrolling screen is empty, otherwise is 1
                    Dataline  type i, " number of items you will use in BDC, using DESCRIBE to get
                    pageno    type i, " you need to scroll screen how many times.
                    line      type i, " number of lines appears on the screen.
                    index(2)  type N, " the screen index for certain item
                    begin     type i, " from parameter of loop
                    end       type i. " to parameter of loop
    *in code sample, the DataTable-linindex stands for the table index number of this line
    form calpage using FixedLine type i (see step 1)
                       LoopLine  type i (see step 1)
                       FirstLine type i (see step 2)
                       DataLine  type i ( this is the item number you will enter in transaction)
              changing pageno    type i (return the number of page, depends on run-time visible                                                                             line in table control/ Step Loop)
              changing line      type i.(visible lines one the screen)
    data: midd type i,
          vline type i, "visible lines
    if DataLine eq 0.
       Message eXXX.
    endif.
    vline = ( sy-srows - FixedLine ) div LoopLine.
    *for table control, you should compare vline with maximum line of
    *table control, then take the small one that is min(vline, maximum)
    *here only illustrate step loop
    if FirstLine eq 0.
            pageno = DataLine div vline.
            if pageno eq 0.
               pageno = pageno + 1.
            endif.
    elseif FirstLine eq 1.
            pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
            midd = ( DataLine - 1 ) mod ( vline - 1).
            if midd = 0 and DataLine gt 1.
                    pageno = pageno - 1.
            endif.
    endif.
    line = vline.
    endform.
    Step4 write a subroutine to calculate the line index for each item.
    form calindex using Line type i (visible lines on the screen)
                        FirstLine type i(see step 2)
                        LineIndex type i(item index)
              changing  Index type n.    (index on the screen)
      if  FirstLine = 0.
            index = LineIndex mod Line.
            if index = '00'.
                    index = Line.
            endif.
      elseif FirstLine = 1.
            index = LineIndex mod ( Line - 1 ).
            if ( index between 1 and 0 ) and LineIndex gt 1.
                    index = index + Line - 1.
            endif.
            if Line = 2.
                    index = index + Line - 1.
            endif.
    endif.
    endform.
    Step5 write a subroutine to calculate the loop range.
    form calrange using Line type i ( visible lines on the screen)
                        DataLine type i
                        FirstLine type i
                        loopindex like sy-index
            changing    begin type i
                        end type i.
    If FirstLine = 0.
       if loopindex = 1.
            begin = 1.
            if DataLine <= Line.
                    end = DataLine.
            else.
                    end = Line.
            endif.
       elseif loopindex gt 1.
            begin = Line * ( loopindex - 1 ) + 1.
            end   = Line * loopindex.
            if end gt DataLine.
               end = DataLine.
            endif.
       endif.
    elseif FirstLine = 1.
      if loopindex = 1.
            begin = 1.
            if DataLine <= Line.
                    end = DataLine.
            else.
                    end = Line.
            endif.
      elseif loop index gt 1.
            begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
            end =   ( Line - 1 ) * ( loopindex - 1 ) + Line.
            if end gt DataLine.
                    end = DataLine.
            endif.
      endif.
    endif.
    endform.
    Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
    form creat_bdc.
    field-symbols: <material>, <quan>, <indicator>.
    data: name1(14) value 'EKPO-EMATN(XX)',
          name2(14) value 'EKPO-MENGE(XX)',
          name3(15) value 'RM06E-SELKZ(XX)'.
    assign:         name1 to <material>,
                    name2 to <quan>,
                    name3 to <indicator>.
    do pageno times.
    if sy-index gt 1
    *insert scroll page ok_code"
    endif.
            perform calrange using Line DataLine FirstLine sy-index
                             changing begin end.
    loop at DataTable from begin to end.
            perform calindex using Line FirstLine DataTable-LineIndex changing Index.
            name1+11(2) = Index.
            name2+11(2) = Index.
            name3+12(2) = Index.
            perform bdcfield using <material> DataTable-matnr.
            perform bdcfield using <quan>     DataTable-menge.
            perform bdcfield using <indicator> DataTable-indicator.
    endloop.
    enddo.
    An example abap program of handling Table Control during bdc programming.
    REPORT zmm_bdcp_purchaseorderkb02
           NO STANDARD PAGE HEADING LINE-SIZE 255.
                    Declaring internal tables                            *
    *-----Declaring line structure
    DATA : BEGIN OF it_dummy OCCURS 0,
             dummy(255) TYPE c,
           END OF it_dummy.
    *-----Internal table for line items
    DATA :  BEGIN OF it_idata OCCURS 0,
              ematn(18),      "Material Number.
              menge(13),      "Qyantity.
              netpr(11),      "Net Price.
              werks(4),       "Plant.
              ebelp(5),       "Item Number.
            END OF it_idata.
    *-----Deep structure for header data and line items
    DATA  :  BEGIN OF it_me21 OCCURS 0,
               lifnr(10),      "Vendor A/c No.
               bsart(4),       "A/c Type.
               bedat(8),       "Date of creation of PO.
               ekorg(4),       "Purchasing Organisation.
               ekgrp(3),       "Purchasing Group.
               x_data LIKE TABLE OF it_idata,
             END OF it_me21.
    DATA  :  x_idata LIKE LINE OF it_idata.
    DATA  :  v_delimit VALUE ','.
    DATA  :  v_indx(3) TYPE n.
    DATA  :  v_fnam(30) TYPE c.
    DATA  :  v_count TYPE n.
    DATA  :  v_ne TYPE i.
    DATA  :  v_ns TYPE i.
    *include bdcrecx1.
    INCLUDE zmm_incl_purchaseorderkb01.
                    Search help for file                                 *
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          program_name  = syst-cprog
          dynpro_number = syst-dynnr
        IMPORTING
          file_name     = p_file.
    START-OF-SELECTION.
           To upload the data into line structure                        *
      CALL FUNCTION 'WS_UPLOAD'
        EXPORTING
          filename = p_file
          filetype = 'DAT'
        TABLES
          data_tab = it_dummy.
        Processing the data from line structure to internal tables       *
      REFRESH:it_me21.
      CLEAR  :it_me21.
      LOOP AT it_dummy.
        IF it_dummy-dummy+0(01) = 'H'.
          v_indx = v_indx + 1.
          CLEAR   it_idata.
          REFRESH it_idata.
          CLEAR   it_me21-x_data.
          REFRESH it_me21-x_data.
          SHIFT it_dummy.
          SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
                                           it_me21-bsart
                                           it_me21-bedat
                                           it_me21-ekorg
                                           it_me21-ekgrp.
          APPEND it_me21.
        ELSEIF it_dummy-dummy+0(01) = 'L'.
          SHIFT it_dummy.
          SPLIT it_dummy AT v_delimit INTO it_idata-ematn
                                           it_idata-menge
                                           it_idata-netpr
                                           it_idata-werks
                                           it_idata-ebelp.
          APPEND it_idata TO it_me21-x_data.
          MODIFY it_me21 INDEX v_indx.
        ENDIF.
      ENDLOOP.
                    To open the group                                    *
      PERFORM open_group.
            To populate the bdcdata table for header data                *
      LOOP AT it_me21.
        v_count = v_count + 1.
        REFRESH it_bdcdata.
        PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0100',
                                        ' ' 'BDC_CURSOR'  'EKKO-LIFNR',
                                        ' ' 'BDC_OKCODE'  '/00',
                                        ' ' 'EKKO-LIFNR'  it_me21-lifnr,
                                        ' ' 'RM06E-BSART' it_me21-bsart,
                                        ' ' 'RM06E-BEDAT' it_me21-bedat,
                                        ' ' 'EKKO-EKORG'  it_me21-ekorg,
                                        ' ' 'EKKO-EKGRP'  it_me21-ekgrp,
                                        ' ' 'RM06E-LPEIN' 'T'.
        PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0120',
                                        ' ' 'BDC_CURSOR'  'RM06E-EBELP',
                                        ' ' 'BDC_OKCODE'  '/00'.
        MOVE 1 TO v_indx.
    *-----To populate the bdcdata table for line item data
        LOOP AT it_me21-x_data INTO x_idata.
          CONCATENATE 'EKPO-EMATN(' v_indx ')'  INTO v_fnam.
          PERFORM  subr_bdc_table USING ' ' v_fnam x_idata-ematn.
          CONCATENATE 'EKPO-MENGE(' v_indx ')'  INTO v_fnam.
          PERFORM  subr_bdc_table USING ' ' v_fnam x_idata-menge.
          CONCATENATE 'EKPO-NETPR(' v_indx ')'  INTO v_fnam.
          PERFORM  subr_bdc_table USING ' ' v_fnam x_idata-netpr.
          CONCATENATE 'EKPO-WERKS(' v_indx ')'  INTO v_fnam.
          PERFORM  subr_bdc_table USING ' ' v_fnam x_idata-werks.
          v_indx = v_indx + 1.
          PERFORM subr_bdc_table USING:  'X' 'SAPMM06E'    '0120',
                                         ' ' 'BDC_CURSOR'  'RM06E-EBELP',
                                         ' ' 'BDC_OKCODE'  '/00'.
        ENDLOOP.
        PERFORM subr_bdc_table USING:    'X' 'SAPMM06E'    '0120',
                                         ' ' 'BDC_CURSOR'  'RM06E-EBELP',
                                         ' ' 'BDC_OKCODE'  '=BU'.
        PERFORM bdc_transaction USING 'ME21'.
      ENDLOOP.
      PERFORM close_group.
                      End of selection event                             *
    END-OF-SELECTION.
      IF session NE 'X'.
    *-----To display the successful records
        WRITE :/10  text-001.          "Sucess records
        WRITE :/10  SY-ULINE(20).
        SKIP.
        IF it_sucess IS INITIAL.
          WRITE :/  text-002.
        ELSE.
          WRITE :/   text-008,          "Total number of Succesful records
                  35 v_ns.
          SKIP.
          WRITE:/   text-003,          "Vendor Number
                 17 text-004,          "Record number
                 30 text-005.          "Message
        ENDIF.
        LOOP AT it_sucess.
          WRITE:/4  it_sucess-lifnr,
                 17 it_sucess-tabix CENTERED,
                 30 it_sucess-sucess_rec.
        ENDLOOP.
        SKIP.
    *-----To display the erroneous records
        WRITE:/10   text-006.          "Error Records
        WRITE:/10   SY-ULINE(17).
        SKIP.
        IF it_error IS INITIAL.
          WRITE:/   text-007.          "No error records
        ELSE.
          WRITE:/   text-009,          "Total number of erroneous records
                 35 v_ne.
          SKIP.
          WRITE:/   text-003,          "Vendor Number
                 17 text-004,          "Record number
                 30 text-005.          "Message
        ENDIF.
        LOOP AT it_error.
          WRITE:/4  it_error-lifnr,
                 17 it_error-tabix CENTERED,
                 30 it_error-error_rec.
        ENDLOOP.
        REFRESH it_sucess.
        REFRESH it_error.
      ENDIF.
    CODE IN INCLUDE.
    Include           ZMM_INCL_PURCHASEORDERKB01
    DATA:   it_BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
    DATA:   it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
    DATA:   E_GROUP_OPENED.
    *-----Internal table to store sucess records
    DATA:BEGIN OF it_sucess OCCURS 0,
           msgtyp(1)   TYPE c,
           lifnr  LIKE  ekko-lifnr,
           tabix  LIKE  sy-tabix,
           sucess_rec(125),
         END OF it_sucess.
    DATA: g_mess(125) type c.
    *-----Internal table to store error records
    DATA:BEGIN OF it_error OCCURS 0,
           msgtyp(1)   TYPE c,
           lifnr  LIKE  ekko-lifnr,
           tabix  LIKE  sy-tabix,
           error_rec(125),
         END OF it_error.
           Selection screen
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS session RADIOBUTTON GROUP ctu.  "create session
    SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
    SELECTION-SCREEN POSITION 45.
    PARAMETERS ctu RADIOBUTTON GROUP ctu.     "call transaction
    SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS group(12).                      "group name of session
    SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
    "A: show all dynpros
    "E: show dynpro on error only
    "N: do not display dynpro
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS: keep AS CHECKBOX.       "' ' = delete session if finished
    "'X' = keep   session if finished
    SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS e_group(12).             "group name of error-session
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS: e_keep AS CHECKBOX.     "' ' = delete session if finished
    "'X' = keep   session if finished
    SELECTION-SCREEN END OF LINE.
    PARAMETERS:p_file LIKE rlgrap-filename.
      at selection screen                                                *
    AT SELECTION-SCREEN.
    group and user must be filled for create session
      IF SESSION = 'X' AND
         GROUP = SPACE. "OR USER = SPACE.
        MESSAGE E613(MS).
      ENDIF.
      create batchinput session                                          *
    FORM OPEN_GROUP.
      IF SESSION = 'X'.
        SKIP.
        WRITE: /(20) 'Create group'(I01), GROUP.
        SKIP.
    *----open batchinput group
        CALL FUNCTION 'BDC_OPEN_GROUP'
          EXPORTING
            CLIENT = SY-MANDT
            GROUP  = GROUP
            USER   = sy-uname.
        WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
                (12) 'returncode:'(I05),
                     SY-SUBRC.
      ENDIF.
    ENDFORM.                    "OPEN_GROUP
      end batchinput session                                             *
    FORM CLOSE_GROUP.
      IF SESSION = 'X'.
    *------close batchinput group
        CALL FUNCTION 'BDC_CLOSE_GROUP'.
        WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
                (12) 'returncode:'(I05),
                     SY-SUBRC.
      ELSE.
        IF E_GROUP_OPENED = 'X'.
          CALL FUNCTION 'BDC_CLOSE_GROUP'.
          WRITE: /.
          WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
        ENDIF.
      ENDIF.
    ENDFORM.                    "CLOSE_GROUP
           Start new transaction according to parameters                 *
    FORM BDC_TRANSACTION USING TCODE TYPE ANY.
      DATA: L_SUBRC LIKE SY-SUBRC.
    *------batch input session
      IF SESSION = 'X'.
        CALL FUNCTION 'BDC_INSERT'
          EXPORTING
            TCODE     = TCODE
          TABLES
            DYNPROTAB = it_BDCDATA.
        WRITE: / 'BDC_INSERT'(I03),
                 TCODE,
                 'returncode:'(I05),
                 SY-SUBRC,
                 'RECORD:',
                 SY-INDEX.
      ELSE.
        REFRESH it_MESSTAB.
        CALL TRANSACTION TCODE USING it_BDCDATA
                         MODE   CTUMODE
                         UPDATE CUPDATE
                         MESSAGES INTO it_MESSTAB.
        L_SUBRC = SY-SUBRC.
        WRITE: / 'CALL_TRANSACTION',
                 TCODE,
                 'returncode:'(I05),
                 L_SUBRC,
                 'RECORD:',
                 SY-INDEX.
      ENDIF.
      Message handling for Call Transaction                              *
      perform subr_mess_hand using g_mess.
    *-----Erzeugen fehlermappe
      IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
        IF E_GROUP_OPENED = ' '.
          CALL FUNCTION 'BDC_OPEN_GROUP'
            EXPORTING
              CLIENT = SY-MANDT
              GROUP  = E_GROUP
              USER   = sy-uname
              KEEP   = E_KEEP.
          E_GROUP_OPENED = 'X'.
        ENDIF.
        CALL FUNCTION 'BDC_INSERT'
          EXPORTING
            TCODE     = TCODE
          TABLES
            DYNPROTAB = it_BDCDATA.
      ENDIF.
      REFRESH it_BDCDATA.
    ENDFORM.                    "BDC_TRANSACTION
         Form  subr_bdc_table                                            *
          text
         -->P_0220   text                                                *
         -->P_0221   text                                                *
         -->P_0222   text                                                *
    FORM subr_bdc_table  USING      VALUE(P_0220) TYPE ANY
                                    VALUE(P_0221) TYPE ANY
                                    VALUE(P_0222) TYPE ANY.
      CLEAR it_bdcdata.
      IF P_0220 = ' '.
        CLEAR it_bdcdata.
        it_bdcdata-fnam     = P_0221.
        it_bdcdata-fval     = P_0222.
        APPEND it_bdcdata.
      ELSE.
        it_bdcdata-dynbegin = P_0220.
        it_bdcdata-program  = P_0221.
        it_bdcdata-dynpro   = P_0222.
        APPEND it_bdcdata.
      ENDIF.
    ENDFORM.                    " subr_bdc_table
         Form  subr_mess_hand                                            *
          text                                                           *
         -->P_G_MESS  text                                               *
    FORM subr_mess_hand USING  P_G_MESS TYPE ANY.
      LOOP AT IT_MESSTAB.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            ID     = it_messtab-msgid
            LANG   = it_messtab-msgspra
            NO     = it_messtab-msgnr
            v1     = it_messtab-msgv1
            v2     = it_messtab-msgv2
          IMPORTING
            MSG    = P_G_MESS
          EXCEPTIONS
            OTHERS = 0.
        CASE it_messtab-msgtyp.
          when 'E'.
            it_error-error_rec   =  P_G_MESS.
            it_error-lifnr       =  it_me21-lifnr.
            it_error-tabix       =  v_count.
            APPEND IT_ERROR.
          when 'S'.
            it_sucess-sucess_rec =  P_G_MESS.
            it_sucess-lifnr      =  it_me21-lifnr.
            it_sucess-tabix      =  v_count.
            APPEND IT_SUCESS.
        endcase.
      ENDLOOP.
      Describe table it_sucess lines v_ns.
      Describe table it_error  lines v_ne.
    ENDFORM.                    " subr_mess_hand
    Also refer
    http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
    and
    http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
    Regards,
    srinivas
    <b>*reward for useful answers*</b>

  • Introduction of flow control and synchronization steps in Test Description

    Hi ALL,
              I am working on developing of Test Scripts in ATML standards. Can any one inform me how to introduce flow control (if, else, end, for, while, break etc)  and synchronization (wait etc) steps into the Test scripts. Thanks in advance.
    With Best Regards,
    Kalyan 

    I had a similar issue in a project I am working on. I'm not sure if I did this the "Best Practices" way or not, but it works perfectly.
    In the head area of my JSP I include the following:
    <f:view>
        <h:outputText id="refresher1" rendered="#{queryHandler.queryRunning}">
            <f:verbatim escape="false">
                <meta http-equiv="refresh"
                      content="5,<%=response.encodeURL(request.getContextPath()+
                              "/queryStatus.jsf")%>">
            </f:verbatim>
        </h:outputText>
        <h:outputText id="refresher1" rendered="#{queryHandler.queryFinishedRunning}">
            <f:verbatim escape="false">
                <meta http-equiv="refresh"
                      content="5,<%=response.encodeURL(request.getContextPath()+
                              "/queryResults.jsf")%>">
            </f:verbatim>
        </h:outputText>This puts a 5 second refresh meta in the header to direct the browser to the correct page based on the status of the query thread.
    There are many ways to accomplish the effect you want. I suggest putting all the controls into the JSP and making use of the rendered attributes instead of the JSTL conditionals to show the controls you want for the state of the application.
    -jeffhoward

  • Difference between STATIC and FLOW CONTROL in IKM

    Hello,
    Can someone explain the difference between STATIC and FLOW control in IKM ? What is the best situation to use them with some example ?
    Can we have more than one ODI Constraint at the target table.
    Thanks
    Edited by: cdmnagaraj on 19-Oct-2008 21:59

    Hi Nagaraj,
    Suppose your Lookup table -> column "VALUE" is 101.
    How many rows in your source table (column) have "Balance" = 101 ??
    I hope only One.
    From your Source table all the recors will be moved to your I$ . then from your I$ it will check for the condition
    and all the violated records will be moved to your E$
    please check your "Insert CK Errors" from your operator
    it will be like this....
    insert into E$_TargetTable
         ERR_TYPE,
         ERR_MESS,
         CHECK_DATE,
         ORIGIN,
         CONS_NAME,
         CONS_TYPE,
         col1,
         col2,
         balance
    select
         'F',
         sysdate,
         '(3367100)TESTPROJECTS.TestTable',
         'conditionTest',
         'CK',     
         col1,
         col2,
         balance
    from     I$_TargetTable CHI
    where     not      (
              Balance = (Select value from LOOKUP)
    So in your case it will check for balance not equal to 101 . and it will push those records into your E$ table
    Rathish

  • SD  and MM FLOW with example

    Hi friends,
    Can any one tell me the SD and MM Flow with respect to company and customer like what the company and customer will do in various stages?

    hai  Reddy,
    SAP Sales and Distribution Processing Document Flow
    Document Flow in Sales
    The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
    The following graphic shows how the various types of sales documents are inter-related and how data subsequently flows into shipping and billing documents.
    D Transaction Code Flow:
    Inquiry / Document type IN
    Tcode for creation VA11,VA12, VA13. Tables VBAK, VBAP
    Quotation / QT
    Tcode for creation VA21,VA22,VA23. Tables VBAK, VBAP
    Purchase Order PO
    Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
    Sales Order OR
    Tcode for creation VA01,VA02,VA03. Tables VBAK,VBAP
    Delivery LF
    Tcode for creation VL01,VL02,VL03. Tables LIKP,LIPS
    Billing MN
    Tcode for creation VF01,VF02,VF03. Tables VBRK,VBRP
    To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
    To create vendor tcode is
    xk01(create), xk02(change) , xk03(display)
    Tables are lfa1.
    To create custmer tcode is xd01, xd02, xd03.
    Table is kna1.
    After creating sales order using this no we can create delivery note tcode is vl01.
    MM  FLOW.
    Tables
    PO
    EKKO---Header level
    EKPO-Item level
    PR
    EBAN
    GR/Material document
    MKPF--Header
    MSEG-Item
    Invoice
    RBKP-header
    RSEG-Item
    Accounting doc
    BKPF--header
    BSEG--Item
    ServicesSSR--Header
    ESLL-Item
    It really depends on the company and their business process. Generally though:
    Purchase Requisition (user reqests stuff, either for manuf/stock, or supplies). -> then the PReq would go through an approval process (Release Strategy). Once approved, one can either create a Request for Quote (RFQ) to multiple vendors to obtain the best prices - and/or create the Purchase Order (either directly from the PReq or from the RFQ).
    Once the PO is created -> then a Goods Receipt is necessary (to indicate you received the goods ordered). Then Invoice Verification (again - if this is set up) - which basically prevents overpayment to a vendor (won't allow you to pay for goods not received through Goods Receipt). Then ultimately the payment to the Vendor.
    So - Transaction flow for create (common):
    PReq -> RFQ -> PO -> G/R -> Invoice -> payment (?)
    ME51N -> ME41 -> ME21N -> MIGO -> MIRO -> payment (?)
    Tables for Purchase Requisition:
    EBAN -
    EBKN - Account Assignment
    Tables for Purchase Orders:
    EKKO - Header
    EKPO - Item
    EINA - Purchasing Info Record (oops forgot to mention that above - PInfoRec has the vendor/material/price for future sourcing)
    Tables for Request for Quote:
    same as PO above
    Tables for Goods Receipt:
    MKPF - Material Document Header
    MSEG - Material Document Item
    EKBE - History of PO
    Tables for Invoice Verification:
    BSIS (good substitute for BSEG, which is a monster)
    If Found Helpfull Do Reward.
    Regards.
    EShwar.

  • Standard flow control

    JSTL support for standard flow control.
    what that means ?
    I am aware of that JSTL can help in SQL processing , XML processing through Tag libraries.
    But however, how the JSTL supports standard flow control ? is it the JSTL iterator we are talking about ?

    Although you can apparently access a database on the JSP page using JSTL tags, it doesn't mean its a good idea. I suggest you use the MVC design. You separate the layers and not put database functionality in the presentation layer (JSP).
    Hers is one MVC approach in which a single servlet acts as the control. There are other ways of doing it via Spring, Structs, etc. However, I suggest you master this approach before moving onto those.
    presentation layer:
    JSP, CSS, Javascript, and JSTL.
    The JSP page and its supporting languages is responsible for displaying data and submitting user input back the controller. The Javascript is typically responsible for basic client side validation of user input. JSP gets its data that it is to display from request scope (and perhaps some from session scope). JSTL assists JSP in displaying data by doing such tasks as looping though a Java collection from the request scope and displaying it. The JSP page should not contain any logic from the other layers (below). The page will get complicated enough over time just displaying data without making it even more difficult to read by inserting business logic into it.
    control layer:
    A single servlet. This servlet takes in all url request and page submits coming from JSP pages. Avoid JSP to JSP page naviigation (there are exceptions to this rule). Go through the control layer. This servlet calls business logic to get data that the page requests. It puts it in request and/or session scope, and dispatches to the appropriate JSP page. Because all url request go through this servlet, the servlet can do centralized authentication (log in) and authorization (user assigned to a role). Dont generate presentation data (html) from this layer.
    business layer:
    Java classes that carry out requests from the control layer. It calls the database layer for raw data from the database and performs business logic on the data (if any) before sending it to the control layer.
    database layer:
    Takes in requests from the business layer. Queries the database via SQL. Is the only layer that has sql in it. Reads the resultSet from the database and puts the data in some kind of Java collection before returning it to the business layer. Never return the resultSet (a database concept) to the business layer.

  • Debugging -  Process flow control

    Hi All,
    I am doing initial load for one condition object(R3AS), and when I check SMW01 I am getting BDoc validation Error.
    I want to debug the BDoc flow context i.e MI0(validation function module) where Bdoc posting is failing.
    I followed OSS note- 432661- Debugging and process support of flow control: Enhancement
    Here is the Note:
    Symptom
    Error analysis requires debugging flow control services.
    Other terms
    SMW01, Flow Control, BDOC, BDoc, BDoc Message, Flow Service, Update task, qRFC step, asynchronous step
    Reason and Prerequisites
    Error analysis requires debugging flow control services.
    Solution
    This feature is available with CRM 3.0 starting SP04 and higher releases.
    Usage:
    •     The flow header structure SMW3_FHD is extended to hold a flag indicating debug mode. To debug, set this flag before calling CL_SMW_MFLOW=> PROCESS_OUTBOUND (Parameter IN_HEADER, Field DBGMODE), PROCESS_NOTIFICATION (Parameter HEADER, Field DBGMODE) or PROCESS_NOTIFICATION_MULT (Parameter HEADER, Field DBGMODE). If update task and/or asynchronous tRFC/qRFC step is done, the message is not written into a qRFC queue or tRFC. Instead the message get's a new state 'D01': To be processed (Debug).
    The message processing can then be continued from transaction SMW01.
    •     Select messages in state D01 possibly with bdoc type, send date, creation time, and user.
    •     In the list display check the message check box that you want to debug.
    •     Choose function Retry to process.
    The message will be processed by flow service function modules in the order shown in transaction SMO8FD. Processing occurs directly. Therefore all active breakpoints can be used to stop processing for further analysis.
    I set HEADER-DBGMODE = ‘X’, and passed this structure to CL_SMW_MFLOW=> PROCESS_OUTBOUND
    But none of the message is set to ‘D01’. Anyone have idea where I am missing?
    I basically want to debug this validation function module while Bdoc comes in CRM, Any other way other than this OSS note..?
    Thanks,
    Vijay Raheja

    what the description of the error?
    Give details. Just by saying bdoc validation error does not nelp.
    Click on the error details icon and see wat it says.
    let us know then only can we help
    Julius

  • Console flow control

    With no flow control on the console port, it's common to overrun the port when sending large config files from a terminal emulator. Is there any way to avoid this, other than manually breaking up the file and sending a chunk at a time, maybe by adjusting the console buffer size, if possible?

    Michael
    Most terminal emulator programs (like Hyperterm, or TeraTerm, or SecurCRT, etc) have a setting where you can specify character delay and or line delay. If you use these parameters to specify some delay you can send the config file (even very large configs) without over-running the console.
    HTH
    Rick

  • Want to know what exactly is flow control in odi

    Hi Experts
    I want to know what exactly is flow control in odi.can anybody explain with an example.i have created a simple interface ie using contol append km .in this both the tables are in one data server ie in different schemas.in this interface i have set the flow control as false.in what circumstances we will use this flow control.
    Regards
    sree

    Hi Sree,
    Couple of points u need to aware.
    There are two ways of Constraint checking in ODI (PK, FK, Condition, NOT NULL etc) using CKM.
    FLOW_CONTROL: If u enable this in ur IKM all the constraints checking will be done at I$ table (before target table loading).
    STATIC_CONTROL: If u enable this in ur IKM all the constraints checking will be done at TARGET table (after target table loading). In this case u need to DISABLE the constraint first and once STATIC_CONTROL is done then u need to ENABLE it.
    So all the violated/errored record will be moved to E$ table in both approach.
    Makes sense?
    Thanks,
    Guru

  • How to implement autotuning pid in labview in flow control process????

    I tried the same way as Example available in LabVIEW..... that is general auto PID simulator... But that didn't worked out for me.....

    The 'General Auto PID Simulator.vi' example uses the technique "PID Relay" feedback where it tries to calculate the PID values based on the relay feedback, but using the PID also in the loop:
    (http://zone.ni.com/reference/en-XX/help/370401H-01/lvpidmain/pidrelay_alg/)
    This technique works, but it requires initial PID parameters that will make the relay setpoint stable and it is able to obtain the results you are expecting.
    Now, for flow control, you can try the most classic techniques. Please use other shipping examples that start with "autotuning" and in special this:
    C:\Program Files (x86)\National Instruments\LabVIEW 2013\examples\control\PID\Autotuning PID Online.vi
    In this VI, you can choose other techniques like open-loop step response, closed-loop step response and the original 'relay feedback' where it doesn't have a PID inside the estimation loop.
    Anyway, here you have more information about those techniques http://zone.ni.com/reference/en-XX/help/370401H-01/TOC4.htm.
    One more thing: keep in mind that depending on the plant parameters, a PID could not be suited for your application and a more complex controller need to be developed.
    Hope this can help you...
    Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

  • ORA-25307: Enqueue rate too high, flow control enabled

    I am stuck. I have my stream setup and they were previously working on two of my dev environments well. Now when I get the streams setup the CAPTURE process has a state of "CAPTURING CHANGES" for like 10 seconds and then changes to state "PAUSED FOR FLOW CONTROL". I believe this is happening because the PROPAGATION process is showing an error of "ORA-25307: Enqueue rate too high, flow control enabled".
    I don't know what to tweak to get rid of this error message. The two environments are dev databases and there is minimal activity on them so i don't think it's a case of the APPLY process is lagging behind the PROPAGATION process. Has anyone run into this issue?? I've verified my db link works, my stream admin user has dba access. Any help or advise would be greatly appreciated.
    thanks, dave

    As rule of thumb, you don't need to set GLOBAL_NAME=TRUE as long as your are 100% GLOBAL_NAME compliant.
    So, setting GLOBAL_NAME=TRUE will not have any effect if your dblink is not global_name compliant
    and if your installation is global_name compliant, you don't need to set GLOBAL_NAME=TRUE.
    The first thing when you diagnose is to get the exact facts.
    Please run this queries both on source and target so that to see what are in the queues and where.
    Run it multiple time to see if figures evolves.
    - If they are fixed, then your Streams is stuck in its last stage. As a cheap and good starting point, just stop/start the capture, propagation and target apply process. Check also the alert.log on both site. when you have a propagation problem, they do contains information's. If you have re-bounced everything and no improvement then the real diagnose work must start here but then we know that the message is wrong and the problems is elsewhere.
    - if they are not fixed then your apply really lag behind for what ever good reason, but this is usually easy to find.
    set termout off
    col version new_value version noprint
    col queue_table format A26 head 'Queue Table'
    col queue_name format A32 head 'Queue Name'
    select substr(version,1,instr(version,'.',1)-1) version from v$instance;
    col mysql new_value mysql noprint
    col primary_instance format 9999 head 'Prim|inst'
    col secondary_instance format 9999 head 'Sec|inst'
    col owner_instance format 99 head 'Own|inst'
    COLUMN MEM_MSG HEADING 'Messages|in Memory' FORMAT 99999999
    COLUMN SPILL_MSGS HEADING 'Messages|Spilled' FORMAT 99999999
    COLUMN NUM_MSGS HEADING 'Total Messages|in Buffered Queue' FORMAT 99999999
    set linesize 150
    select case
      when &version=9 then ' distinct a.QID, a.owner||''.''||a.name nam, a.queue_table,
                  decode(a.queue_type,''NORMAL_QUEUE'',''NORMAL'', ''EXCEPTION_QUEUE'',''EXCEPTION'',a.queue_type) qt,
                  trim(a.enqueue_enabled) enq, trim(a.dequeue_enabled) deq, x.bufqm_nmsg msg, b.recipients
                  from dba_queues a , sys.v_$bufqm x, dba_queue_tables b
            where
                   a.qid = x.bufqm_qid (+) and a.owner not like ''SYS%''
               and a.queue_table = b.queue_table (+)
               and a.name not like ''%_E'' '
       when &version=10 then ' a.owner||''.''|| a.name nam, a.queue_table,
                  decode(a.queue_type,''NORMAL_QUEUE'',''NORMAL'', ''EXCEPTION_QUEUE'',''EXCEPTION'',a.queue_type) qt,
                  trim(a.enqueue_enabled) enq, trim(a.dequeue_enabled) deq, (NUM_MSGS - SPILL_MSGS) MEM_MSG, spill_msgs, x.num_msgs msg,
                  x.INST_ID owner_instance
                  from dba_queues a , sys.gv_$buffered_queues x
            where
                   a.qid = x.queue_id (+) and a.owner not in ( ''SYS'',''SYSTEM'',''WMSYS'')  order by a.owner ,qt desc'
       end mysql
    from dual
    set termout on
    select &mysql
    /B. Polarski

  • Communicat​ing between LabVIEW and Basic Stamp 2.0

    Hello,
    We are trying to control the movement of a Parallax Boe-Bot (robot with
    Board of Education) via LabView programming.  The BOE operates on
    Basic Stamp programming to control the pulse width sent to two servo
    motors.
    Is there a way to establish communication between LabVIEW and Basic
    Stamp 2.0?   We need to send commands from LabVIEW to the
    Basic Stamp to control the pulse width and therefore the rotation of
    the two servo motors.  We also need to send a signal from an
    accelerometer based on the robot to the LabVIEW ADC. 
    The ultimate goal is to do this with wireless communication, but for
    right now we are simply trying to figure out any way to send the data
    between LabVIEW and the Basic Stamp.
    Any ideas?
    Thank you,
    Adam

    Hi Adam,
    You can communicate with a BASIC Stamp microcontroller over GPIB using VISA.  To see some LabVIEW example code, just search for GPIB in the NI Example Finder (Help>>Find Examples). This will show you the basics of GPIB communication in LabVIEW.  I also found this link by searching the NI discussion forums for "basic stamp"
    http://www.parallax.com/html_pages/downloads/softw​are/software_basic_stamp.asp
    Here you can download an example using LabVIEW 7.0 or higher to communicate with a BASIC Stamp 2.
    I hope this is helpful!  Let us know if you have further questions.
    Megan B.
    National Instruments

  • BPC Balance sheet , Profit loss and cash flow planning

    Hi Friends,
    Can anybody have the documents or links for BPC balance sheet and Profit loass and cash flowing for data flow from R/3 to BW abd BW to BPC as wells as what is process form business point of view. what are the EVdre reports and input scdules and we deelope and also data source for balancesheet and Profie and loss and Cash flow planning in BPC/
    PLease share any documents if you hae.
    Thanks
    Best regards
    SG

    Hi SG,
    What Raghu has shared are the best practices. However, what you need is the understanding of the these financial statements from a general perspective (not BPC). These documents are just financial statements. BPC is just a tool, in which you can create these statements. But, in order to create these statements in BPC, you need to understand the basic terminologies of the financial statements.
    You can search them directly. on the internet.
    Hope this helps.

Maybe you are looking for

  • Questions about AS2 Tree Component (Flash CS3)

    I have Flash application with a Tree component on the Stage. I'm using an XML file to create the structure of the Tree component. Each entry on my XML has the attributes id, label, heading, desc, and icon. My problem is that I can't seem to be able t

  • Error: sql.SQLError: [-4008] (at 1) Unknown user name/password combination

    Hello Experts, After a Test refresh for SCM system, we restored Livecache. The database has been changed and starts using database manager, during registration (Register LCApps) it gives the following error: Logical Command: DBMRFC Parameter: exec_lc

  • Can't start OC4J container

    Hi! I can't start my OC4J container. I've pasted here the error message. Can anyobody help me? Thanks. C:\Documents and Settings\zoli>java -jar "C:\Program Files\Jdeveloper 10.1.3\j2e e\home\oc4j.jar" 2006-10-09 14:10:29.031 ERROR Failed to set the i

  • Can you edit text after saving your file as pdf

    I have recently created a letterhead in Illustrator. Is there a way to change a person name and title after saving it as a pdf file? I heard something about creating a form in Acrobat professsional. I need to print out a letterhead with different peo

  • Plz friends help me...

    Hello, i am scrolling ticker on mobile screen sucessfully.. But problem is that i want to use image as a seperator between two information. plz tell me how can i add image with ticker in j2me..(if possible). If possible plz give me an example. Aman G