Asynchronous Coupling with Pools in one Process

Hi everybody,
i try to  call a BPM Pool (POOL_B) by another BPM Pool (POOL_A) within the same process but unfortunately without success.
This are my steps:
a) for my START Event (Pool_B) i created a new Message Trigger with a Asynchron Service Interface (Wsdl File with two import parameters)
b) in my Service Activity (Pool_A) i use the created Asynchron Service Interface in order to process Pool_B
c) in Pool_B i have also created a Notification to get an info Mail after the process was started
d) i add SAP_BPM_SuperAdmin to SAP_BPM_Service
e) Consumer and Provider are also be configured
After starting the process i didn't get an info Mail, but everything in Pool_A seems to work fine.
If i activate Pool_B (Pool_A becomes inactive) only the WS for Pool_B works.
Please Help.
regards,
Sid
Edited by: Sid on Sep 26, 2011 6:13 PM

You need two Physical databases each with its own Connection Pool, within that database will be a single Physical Schema.
Or you could have a single Database/Connection Pool if it has read access to both schemas.

Similar Messages

  • How to delete the row in table control with respect to one field in module pool programming?

    Hi,
    Can I know the way to delete the row in table control with respect to one field in module pool programming
    Regards
    Darshan MS

    HI,
    I want to delete the row after the display of table control. I have created push button as delete row. If I click on this push button, the selected row should get deleted.
    I have written this code,
    module USER_COMMAND_9000 input.
    DATA OK_CODE TYPE SY-UCOMM.
    OK_CODE = SY-UCOMM.
    CASE OK_CODE.
         WHEN 'DELETE'.
            LOOP AT lt_source INTO ls_source WHERE mark = 'X'.
                APPEND LS_SOURCE TO LT_RESTORE.
                DELETE TABLE LT_SOURCE FROM LS_SOURCE.
                SOURCE-LINES = SOURCE-LINES - 1.
            ENDLOOP.
    But I'm unable to delete the selected rows, It is getting deleted the last rows eventhough I select the other row.
    So I thought of doing with respect to the field.

  • Peformance of one process is slow ( statspack report is attached)

    Hi,
    My version is 9.2.0.7 (HP-UX Itanium)
    we have recently migrated the DB from windows 2003 to Unix (HP-UX Itanium 11.23).
    we have one process which usually takes 15 mins before migration, now it is taking 25 mins to complete. I did not change anything at db level. same init.ora parameters. tables and indexes statistiscs are upto to date.
    Please guide me, what might be the wrong at instance level. Here I am skipping the sql query portion of statspack report due to security reasons.
    this statspack report is taken before running the process and after completion of process.
    STATSPACK report for
    DB Name         DB Id    Instance     Inst Num Release     Cluster Host
    UAT        496948094 UAT             1 9.2.0.7.0   NO      dbt
                  Snap Id     Snap Time      Sessions Curs/Sess Comment
    Begin Snap:         2 15-Jul-09 10:59:05       11       2.7
      End Snap:         3 15-Jul-09 12:42:18       17       4.4
       Elapsed:              103.22 (mins)
    Cache Sizes (end)
    ~~~~~~~~~~~~~~~~~
                   Buffer Cache:       400M      Std Block Size:          8K
               Shared Pool Size:       160M          Log Buffer:        512K
    Load Profile
    ~~~~~~~~~~~~                            Per Second       Per Transaction
                      Redo size:             44,830.27            435,162.76
                  Logical reads:             15,223.37            147,771.73
                  Block changes:                198.12              1,923.15
                 Physical reads:                 47.02                456.37
                Physical writes:                  7.05                 68.45
                     User calls:                 50.01                485.42
                         Parses:                 25.99                252.26
                    Hard parses:                  0.24                  2.38
                          Sorts:                  3.40                 33.00
                         Logons:                  0.02                  0.16
                       Executes:                 34.64                336.27
                   Transactions:                  0.10
      % Blocks changed per Read:    1.30    Recursive Call %:     27.05
    Rollback per transaction %:   33.70       Rows per Sort:   1532.57
    Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                Buffer Nowait %:  100.00       Redo NoWait %:    100.00
                Buffer  Hit   %:   99.69    In-memory Sort %:    100.00
                Library Hit   %:   99.38        Soft Parse %:     99.06
             Execute to Parse %:   24.98         Latch Hit %:    100.00
    Parse CPU to Parse Elapsd %:   48.39     % Non-Parse CPU:     99.53
    Shared Pool Statistics        Begin   End
                 Memory Usage %:   94.56   94.19
        % SQL with executions>1:   74.01   62.51
      % Memory for SQL w/exec>1:   52.89   54.29
    Top 5 Timed Events
    ~~~~~~~~~~~~~~~~~~                                                     % Total
    Event                                               Waits    Time (s) Ela Time
    CPU time                                                          895    48.10
    db file sequential read                           195,597         443    23.83
    log file parallel write                             1,706         260    13.97
    log buffer space                                      415         122     6.54
    control file parallel write                         2,074          66     3.53
    Wait Events for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> s  - second
    -> cs - centisecond -     100th of a second
    -> ms - millisecond -    1000th of a second
    -> us - microsecond - 1000000th of a second
    -> ordered by wait time desc, waits desc (idle events last)
                                                                       Avg
                                                         Total Wait   wait    Waits
    Event                               Waits   Timeouts   Time (s)   (ms)     /txn
    db file sequential read           195,597          0        443      2    306.6
    log file parallel write             1,706          0        260    152      2.7
    log buffer space                      415          0        122    293      0.7
    control file parallel write         2,074          0         66     32      3.3
    log file sync                         678          4         51     75      1.1
    db file scattered read              6,608          0         21      3     10.4
    log file switch completion              9          0          2    208      0.0
    SQL*Net more data to client        24,072          0          1      0     37.7
    log file single write                  18          0          0     19      0.0
    db file parallel read                   9          0          0     13      0.0
    control file sequential read          928          0          0      0      1.5
    SQL*Net break/reset to clien          292          0          0      0      0.5
    latch free                             25          2          0      3      0.0
    log file sequential read               18          0          0      2      0.0
    LGWR wait for redo copy                37          0          0      0      0.1
    direct path read                       45          0          0      0      0.1
    direct path write                      45          0          0      0      0.1
    SQL*Net message from client       308,861          0     30,960    100    484.1
    SQL*Net more data from clien       26,217          0          3      0     41.1
    SQL*Net message to client         308,867          0          0      0    484.1
    Background Wait Events for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> ordered by wait time desc, waits desc (idle events last)
                                                                       Avg
                                                         Total Wait   wait    Waits
    Event                               Waits   Timeouts   Time (s)   (ms)     /txn
    log file parallel write             1,706          0        260    152      2.7
    control file parallel write         2,074          0         66     32      3.3
    log buffer space                       10          0          1    149      0.0
    db file scattered read                 90          0          1      7      0.1
    db file sequential read               104          0          1      5      0.2
    log file single write                  18          0          0     19      0.0
    control file sequential read          876          0          0      0      1.4
    log file sequential read               18          0          0      2      0.0
    latch free                              4          2          0      9      0.0
    LGWR wait for redo copy                37          0          0      0      0.1
    direct path read                       45          0          0      0      0.1
    direct path write                      45          0          0      0      0.1
    rdbms ipc message                   7,222      5,888     21,416   2965     11.3
    pmon timer                          2,079      2,079      6,044   2907      3.3
    smon timer                             21         21      6,002 ######      0.0
    Instance Activity Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    Statistic                                      Total     per Second    per Trans
    CPU used by this session                      89,478           14.5        140.3
    CPU used when call started                    89,478           14.5        140.3
    CR blocks created                                148            0.0          0.2
    DBWR buffers scanned                         158,122           25.5        247.8
    DBWR checkpoint buffers written               11,909            1.9         18.7
    DBWR checkpoints                                   3            0.0          0.0
    DBWR free buffers found                      136,228           22.0        213.5
    DBWR lru scans                                    53            0.0          0.1
    DBWR make free requests                           53            0.0          0.1
    DBWR summed scan depth                       158,122           25.5        247.8
    DBWR transaction table writes                     43            0.0          0.1
    DBWR undo block writes                        19,283            3.1         30.2
    SQL*Net roundtrips to/from client            308,602           49.8        483.7
    active txn count during cleanout               6,812            1.1         10.7
    background checkpoints completed                   3            0.0          0.0
    background checkpoints started                     3            0.0          0.0
    background timeouts                            7,204            1.2         11.3
    branch node splits                                 4            0.0          0.0
    buffer is not pinned count                35,587,689        5,746.4     55,780.1
    buffer is pinned count                   202,539,737       32,704.6    317,460.4
    bytes received via SQL*Net from c        106,536,068       17,202.7    166,984.4
    bytes sent via SQL*Net to client          98,286,059       15,870.5    154,053.4
    calls to get snapshot scn: kcmgss            346,517           56.0        543.1
    calls to kcmgas                               42,563            6.9         66.7
    calls to kcmgcs                                7,735            1.3         12.1
    change write time                             12,666            2.1         19.9
    cleanout - number of ktugct calls              9,698            1.6         15.2
    cleanouts and rollbacks - consist                  0            0.0          0.0
    cleanouts only - consistent read               1,161            0.2          1.8
    cluster key scan block gets                   15,789            2.6         24.8
    cluster key scans                              6,534            1.1         10.2
    commit cleanout failures: block l                199            0.0          0.3
    commit cleanout failures: buffer                  69            0.0          0.1
    commit cleanout failures: callbac                  0            0.0          0.0
    commit cleanouts                              40,688            6.6         63.8
    commit cleanouts successfully com             40,420            6.5         63.4
    commit txn count during cleanout               4,652            0.8          7.3
    consistent changes                               150            0.0          0.2
    consistent gets                           93,071,913       15,028.6    145,880.7
    consistent gets - examination              1,487,526          240.2      2,331.6
    cursor authentications                           322            0.1          0.5
    data blocks consistent reads - un                 51            0.0          0.1
    db block changes                           1,226,967          198.1      1,923.2
    db block gets                              1,206,448          194.8      1,891.0
    deferred (CURRENT) block cleanout             13,478            2.2         21.1
    dirty buffers inspected                        9,876            1.6         15.5
    enqueue conversions                               41            0.0          0.1
    enqueue releases                              12,783            2.1         20.0
    enqueue requests                              12,785            2.1         20.0
    enqueue waits                                      0            0.0          0.0
    execute count                                214,538           34.6        336.3
    free buffer inspected                          9,879            1.6         15.5
    free buffer requested                        349,615           56.5        548.0
    hot buffers moved to head of LRU             141,298           22.8        221.5
    immediate (CR) block cleanout app              1,161            0.2          1.8
    immediate (CURRENT) block cleanou             23,894            3.9         37.5
    Instance Activity Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    Statistic                                      Total     per Second    per Trans
    index fast full scans (full)                      19            0.0          0.0
    index fetch by key                           671,512          108.4      1,052.5
    index scans kdiixs1                       56,328,309        9,095.5     88,288.9
    leaf node 90-10 splits                            16            0.0          0.0
    leaf node splits                               2,187            0.4          3.4
    logons cumulative                                105            0.0          0.2
    messages received                              1,653            0.3          2.6
    messages sent                                  1,653            0.3          2.6
    no buffer to keep pinned count                     0            0.0          0.0
    no work - consistent read gets            35,118,594        5,670.7     55,044.8
    opened cursors cumulative                      4,036            0.7          6.3
    parse count (failures)                            43            0.0          0.1
    parse count (hard)                             1,516            0.2          2.4
    parse count (total)                          160,939           26.0        252.3
    parse time cpu                                   421            0.1          0.7
    parse time elapsed                               870            0.1          1.4
    physical reads                               291,165           47.0        456.4
    physical reads direct                             45            0.0          0.1
    physical writes                               43,672            7.1         68.5
    physical writes direct                            45            0.0          0.1
    physical writes non checkpoint                41,379            6.7         64.9
    pinned buffers inspected                           3            0.0          0.0
    prefetched blocks                             88,896           14.4        139.3
    prefetched blocks aged out before                 22            0.0          0.0
    process last non-idle time                    75,777           12.2        118.8
    recursive calls                              114,829           18.5        180.0
    recursive cpu usage                           11,704            1.9         18.3
    redo blocks written                          275,521           44.5        431.9
    redo buffer allocation retries                   419            0.1          0.7
    redo entries                                 623,735          100.7        977.6
    redo log space requests                           10            0.0          0.0
    redo log space wait time                         192            0.0          0.3
    redo ordering marks                                3            0.0          0.0
    redo size                                277,633,840       44,830.3    435,162.8
    redo synch time                                5,185            0.8          8.1
    redo synch writes                                675            0.1          1.1
    redo wastage                                 818,952          132.2      1,283.6
    redo write time                               26,562            4.3         41.6
    redo writes                                    1,705            0.3          2.7
    rollback changes - undo records a                395            0.1          0.6
    rollbacks only - consistent read                  49            0.0          0.1
    rows fetched via callback                    553,910           89.4        868.2
    session connect time                          74,797           12.1        117.2
    session logical reads                     94,278,361       15,223.4    147,771.7
    session pga memory                         2,243,808          362.3      3,516.9
    session pga memory max                     1,790,880          289.2      2,807.0
    session uga memory                         2,096,104          338.5      3,285.4
    session uga memory max                    32,637,856        5,270.1     51,156.5
    shared hash latch upgrades - no w         56,430,882        9,112.0     88,449.7
    sorts (memory)                                21,055            3.4         33.0
    sorts (rows)                              32,268,330        5,210.5     50,577.3
    summed dirty queue length                     53,238            8.6         83.5
    switch current to new buffer                  37,071            6.0         58.1
    table fetch by rowid                      90,385,043       14,594.7    141,669.4
    table fetch continued row                    104,336           16.9        163.5
    table scan blocks gotten                     376,181           60.7        589.6
    Instance Activity Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    Statistic                                      Total     per Second    per Trans
    table scan rows gotten                     5,103,693          824.1      7,999.5
    table scans (long tables)                         97            0.0          0.2
    table scans (short tables)                    53,485            8.6         83.8
    transaction rollbacks                            247            0.0          0.4
    user calls                                   309,698           50.0        485.4
    user commits                                     423            0.1          0.7
    user rollbacks                                   215            0.0          0.3
    workarea executions - opt                 37,753            6.1         59.2
    write clones created in foregroun                718            0.1          1.1
    Tablespace IO Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    ->ordered by IOs (Reads + Writes) desc
    Tablespace
                     Av      Av     Av                    Av        Buffer Av Buf
             Reads Reads/s Rd(ms) Blks/Rd       Writes Writes/s      Waits Wt(ms)
    USERS
           200,144      32    2.3     1.4       22,576        4          0    0.0
    UNDOTBS1
                38       0    9.5     1.0       19,348        3          0    0.0
    SYSTEM
             2,016       0    4.7     1.5          505        0          0    0.0
    TOOLS
                14       0    9.3     1.3        1,237        0          0    0.0
    IMAGES
                 3       0    6.7     1.0            3        0          0    0.0
    INDX
                 3       0    6.7     1.0            3        0          0    0.0
    Buffer Pool Statistics for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> Standard block size Pools  D: default,  K: keep,  R: recycle
    -> Default Pools for other block sizes: 2k, 4k, 8k, 16k, 32k
                                                               Free    Write  Buffer
         Number of Cache      Buffer    Physical   Physical  Buffer Complete    Busy
    P      Buffers Hit %        Gets       Reads     Writes   Waits    Waits   Waits
    D       49,625  99.7  94,278,286     291,074     43,627       0        0       0
    Instance Recovery Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> B: Begin snapshot,  E: End snapshot
      Targt Estd                                    Log File   Log Ckpt   Log Ckpt
      MTTR  MTTR   Recovery    Actual     Target      Size     Timeout    Interval
       (s)   (s)   Estd IOs  Redo Blks  Redo Blks  Redo Blks  Redo Blks  Redo Blks
    B    38     9       2311      13283      13021      92160      13021
    E    38     7        899       4041       3767      92160       3767
    Buffer Pool Advisory for DB: UAT  Instance: UAT  End Snap: 3
    -> Only rows with estimated physical reads >0 are displayed
    -> ordered by Block Size, Buffers For Estimate (default block size first)
            Size for  Size      Buffers for  Est Physical          Estimated
    P   Estimate (M) Factr         Estimate   Read Factor     Physical Reads
    D             32    .1            3,970          2.94          2,922,389
    D             64    .2            7,940          2.54          2,524,222
    D             96    .2           11,910          2.38          2,365,570
    D            128    .3           15,880          2.27          2,262,338
    D            160    .4           19,850          2.19          2,183,287
    D            192    .5           23,820          1.97          1,962,758
    D            224    .6           27,790          1.30          1,293,415
    D            256    .6           31,760          1.21          1,203,737
    D            288    .7           35,730          1.10          1,096,115
    D            320    .8           39,700          1.06          1,056,077
    D            352    .9           43,670          1.04          1,036,708
    D            384   1.0           47,640          1.02          1,012,912
    D            400   1.0           49,625          1.00            995,426
    D            416   1.0           51,610          0.99            982,641
    D            448   1.1           55,580          0.97            966,874
    D            480   1.2           59,550          0.89            890,749
    D            512   1.3           63,520          0.88            879,062
    D            544   1.4           67,490          0.87            864,539
    D            576   1.4           71,460          0.80            800,284
    D            608   1.5           75,430          0.76            756,222
    D            640   1.6           79,400          0.75            749,473
    PGA Aggr Target Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> B: Begin snap   E: End snap (rows dentified with B or E contain data
       which is absolute i.e. not diffed over the interval)
    -> PGA cache hit % - percentage of W/A (WorkArea) data processed only in-memory
    -> Auto PGA Target - actual workarea memory target
    -> W/A PGA Used    - amount of memory used for all Workareas (manual + auto)
    -> %PGA W/A Mem    - percentage of PGA memory allocated to workareas
    -> %Auto W/A Mem   - percentage of workarea memory controlled by Auto Mem Mgmt
    -> %Man W/A Mem    - percentage of workarea memory under manual control
    PGA Cache Hit % W/A MB Processed Extra W/A MB Read/Written
              100.0              851                         0
                                                 %PGA  %Auto   %Man
      PGA Aggr  Auto PGA   PGA Mem    W/A PGA    W/A    W/A    W/A   Global Mem
      Target(M) Target(M)  Alloc(M)   Used(M)    Mem    Mem    Mem    Bound(K)
    B       320       282       12.6        0.0     .0     .0     .0     16,384
    E       320       281       15.3        0.0     .0     .0     .0     16,384
    PGA Aggr Target Histogram for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> Opt Executions are purely in-memory operations
        Low    High
    Opt Opt    Total Execs Opt Execs 1-Pass Execs M-Pass Execs
         8K     16K         37,010        37,010            0            0
        16K     32K             70            70            0            0
        32K     64K             11            11            0            0
        64K    128K             34            34            0            0
       128K    256K              9             9            0            0
       256K    512K             54            54            0            0
       512K   1024K            536           536            0            0
         1M      2M              7             7            0            0
         2M      4M             24            24            0            0
    PGA Memory Advisory for DB: UAT  Instance: UAT  End Snap: 3
    -> When using Auto Memory Mgmt, minly choose a pga_aggregate_target value
       where Estd PGA Overalloc Count is 0
                                           Estd Extra    Estd PGA   Estd PGA
    PGA Target    Size           W/A MB   W/A MB Read/      Cache  Overalloc
      Est (MB)   Factr        Processed Written to Disk     Hit %      Count
            40     0.1          3,269.7             98.2     97.0          0
            80     0.3          3,269.7              9.6    100.0          0
           160     0.5          3,269.7              9.6    100.0          0
           240     0.8          3,269.7              0.0    100.0          0
           320     1.0          3,269.7              0.0    100.0          0
           384     1.2          3,269.7              0.0    100.0          0
           448     1.4          3,269.7              0.0    100.0          0
           512     1.6          3,269.7              0.0    100.0          0
           576     1.8          3,269.7              0.0    100.0          0
           640     2.0          3,269.7              0.0    100.0          0
           960     3.0          3,269.7              0.0    100.0          0
         1,280     4.0          3,269.7              0.0    100.0          0
         1,920     6.0          3,269.7              0.0    100.0          0
         2,560     8.0          3,269.7              0.0    100.0          0
              -------------------------------------------------------------

    Rollback Segment Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    ->A high value for "Pct Waits" suggests more rollback segments may be required
    ->RBS stats may not be accurate between begin and end snaps when using Auto Undo
      managment, as RBS may be dynamically created and dropped as needed
            Trans Table       Pct   Undo Bytes
    RBS No      Gets        Waits     Written        Wraps  Shrinks  Extends
         0           22.0    0.00               0        0        0        0
         1          650.0    0.00       1,868,300        0        0        0
         2        1,987.0    0.00       4,613,768        9        0        7
         3        6,070.0    0.00      24,237,494       37        0       36
         4          223.0    0.00         418,942        3        0        1
         5          621.0    0.00       1,749,086       11        0       11
         6        8,313.0    0.00      48,389,590       54        0       52
         7        7,248.0    0.00      14,477,004       19        0       17
         8        1,883.0    0.00      12,332,646       14        0       12
         9        2,729.0    0.00      17,820,450       19        0       19
        10        1,009.0    0.00       2,857,150        5        0        3
    Rollback Segment Storage for DB: UAT  Instance: UAT  Snaps: 2 -3
    ->Opt Size should be larger than Avg Active
    RBS No    Segment Size      Avg Active    Opt Size    Maximum Size
         0         450,560               0                         450,560
         1       8,511,488           6,553                       8,511,488
         2       8,511,488       4,592,363                      18,997,248
         3      29,351,936      14,755,792                      29,483,008
         4       2,220,032         105,188                       2,220,032
         5       3,137,536       3,416,104                      54,648,832
         6      55,697,408      21,595,184                      55,697,408
         7      26,337,280       9,221,107                      26,337,280
         8      13,754,368       5,142,374                      13,754,368
         9      22,011,904      10,220,526                      22,011,904
        10       4,317,184       3,810,892                      13,754,368
    Undo Segment Summary for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> Undo segment block stats:
    -> uS - unexpired Stolen,   uR - unexpired Released,   uU - unexpired reUsed
    -> eS - expired   Stolen,   eR - expired   Released,   eU - expired   reUsed
    Undo           Undo        Num  Max Qry     Max Tx Snapshot Out of uS/uR/uU/
    TS#         Blocks      Trans  Len (s)   Concurcy  Too Old  Space eS/eR/eU
       1         19,305    109,683      648          3        0      0 0/0/0/0/0/0
    Undo Segment Stats for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> ordered by Time desc
                         Undo      Num Max Qry   Max Tx  Snap   Out of uS/uR/uU/
    End Time           Blocks    Trans Len (s)    Concy Too Old  Space eS/eR/eU
    15-Jul 12:32           10   13,451       3        2       0      0 0/0/0/0/0/0
    15-Jul 12:22           87   13,384       6        1       0      0 0/0/0/0/0/0
    15-Jul 12:12        3,746   13,229      91        1       0      0 0/0/0/0/0/0
    15-Jul 12:02        8,949   13,127     648        1       0      0 0/0/0/0/0/0
    15-Jul 11:52        1,496   10,476      24        1       0      0 0/0/0/0/0/0
    15-Jul 11:42        3,895   10,441       6        1       0      0 0/0/0/0/0/0
    15-Jul 11:32          531    9,155       1        3       0      0 0/0/0/0/0/0
    15-Jul 11:22            0    8,837       3        0       0      0 0/0/0/0/0/0
    15-Jul 11:12            4    8,817       3        1       0      0 0/0/0/0/0/0
    15-Jul 11:02          587    8,766       2        2       0      0 0/0/0/0/0/0
    Latch Activity for DB: UAT  Instance: UAT  Snaps: 2 -3
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
      willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
                                               Pct    Avg   Wait                 Pct
                                  Get          Get   Slps   Time       NoWait NoWait
    Latch                       Requests      Miss  /Miss    (s)     Requests   Miss
    Consistent RBA                    1,708    0.0             0            0
    FIB s.o chain latch                  40    0.0             0            0
    FOB s.o list latch                  467    0.0             0            0
    SQL memory manager latch              1    0.0             0        2,038    0.0
    SQL memory manager worka        174,015    0.0             0            0
    active checkpoint queue           2,081    0.0             0            0
    archive control                       1    0.0             0            0
    cache buffer handles            162,618    0.0             0            0
    cache buffers chains        190,111,507    0.0    0.2      0      426,778    0.0
    cache buffers lru chain         425,142    0.0    0.2      0       65,895    0.0
    channel handle pool latc            202    0.0             0            0
    channel operations paren          4,405    0.0             0            0
    checkpoint queue latch          228,932    0.0    0.0      0       41,321    0.0
    child cursor hash table          18,320    0.0             0            0
    commit callback allocati              4    0.0             0            0
    dml lock allocation               2,482    0.0             0            0
    dummy allocation                    204    0.0             0            0
    enqueue hash chains              25,615    0.0             0            0
    enqueues                         15,416    0.0             0            0
    event group latch                   104    0.0             0            0
    hash table column usage             410    0.0             0      191,319    0.0
    internal temp table obje          1,048    0.0             0            0
    job_queue_processes para            103    0.0             0            0
    ktm global data                      21    0.0             0            0
    lgwr LWN SCN                      3,215    0.0    0.0      0            0
    library cache                 1,657,451    0.0    0.0      0        1,479    0.1
    library cache load lock           1,126    0.0             0            0
    library cache pin             1,112,420    0.0    0.0      0            0
    library cache pin alloca        670,952    0.0    0.0      0            0
    list of block allocation          2,748    0.0             0            0
    loader state object free             36    0.0             0            0
    longop free list parent               1    0.0             0            1    0.0
    messages                         19,427    0.0             0            0
    mostly latch-free SCN             3,229    0.3    0.0      0            0
    multiblock read objects          15,022    0.0             0            0
    ncodef allocation latch              99    0.0             0            0
    object stats modificatio             28    0.0             0            0
    post/wait queue                   1,810    0.0             0        1,102    0.0
    process allocation                  202    0.0             0          104    0.0
    process group creation              202    0.0             0            0
    redo allocation                 629,175    0.0    0.0      0            0
    redo copy                             0                    0      623,865    0.0
    redo writing                     11,487    0.0             0            0
    row cache enqueue latch         197,626    0.0             0            0
    row cache objects               201,089    0.0             0          642    0.0
    sequence cache                      348    0.0             0            0
    session allocation                3,634    0.1    0.0      0            0
    session idle bit                621,031    0.0             0            0
    session switching                    99    0.0             0            0
    session timer                     2,079    0.0             0            0
    Latch Activity for DB: UAT  Instance: UAT  Snaps: 2 -3
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
      willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
                                               Pct    Avg   Wait                 Pct
                                  Get          Get   Slps   Time       NoWait NoWait
    Latch                       Requests      Miss  /Miss    (s)     Requests   Miss
    shared pool                     786,331    0.0    0.1      0            0
    sim partition latch                   0                    0          193    0.0
    simulator hash latch          5,885,552    0.0             0            0
    simulator lru latch              12,981    0.0             0       66,129    0.0
    sort extent pool                    120    0.0             0            0
    transaction allocation              249    0.0             0            0
    transaction branch alloc             99    0.0             0            0
    undo global data                 27,867    0.0             0            0
    user lock                           396    0.0             0            0
    Latch Sleep breakdown for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> ordered by misses desc
                                          Get                            Spin &
    Latch Name                       Requests      Misses      Sleeps Sleeps 1->4
    cache buffers lru chain           425,142          82          15 67/15/0/0/0
    library cache                   1,657,451          76           3 73/3/0/0/0
    shared pool                       786,331          37           2 35/2/0/0/0
    redo allocation                   629,175          31           1 30/1/0/0/0
    cache buffers chains          190,111,507          21           4 19/0/2/0/0
    Latch Miss Sources for DB: UAT  Instance: UAT  Snaps: 2 -3
    -> only latches with sleeps are shown
    -> ordered by name, sleeps desc
                                                         NoWait              Waiter
    Latch Name               Where                       Misses     Sleeps   Sleeps
    cache buffers chains     kcbget: pin buffer               0          2        0
    cache buffers chains     kcbgtcr: fast path               0          2        0
    cache buffers lru chain  kcbbiop: lru scan                2         12        0
    cache buffers lru chain  kcbbwlru                         0          2        0
    cache buffers lru chain  kcbbxsv: move to being wri       0          1        0
    library cache            kgllkdl: child: cleanup          0          1        0
    library cache            kglpin: child: heap proces       0          1        0
    library cache            kglpndl: child: before pro       0          1        0
    redo allocation          kcrfwi: more space               0          1        0
    shared pool              kghalo                           0          2        0
              -------------------------------------------------------------

  • I created one apple I'd when I started using the iPad.  After some days, I had to create a new apple I'd as there was some problem with the first one. Now at some places still my old apple I'd is appearing.  Pls adv how I change this to my new apple Id.

    I created one apple I'd when I started using the iPad.  After some days, I had to create a new apple id
    as there was some problem with the first one. Now at some places still my old apple Id is appearing.  Pls adv how I change this to my new apple Id.

    Anything you downloaded with the first Apple Id will forever be tied to it, and will always require it to update.
    The question here is, why did you think you needed to create a new Apple ID? What was the problem with the first one?
    To get rid of th old one, you'll need to delete everything you downloaded with it, and then sign out of the ID in several places around the iPad. 
    Go to Settings->iTunes & App Stores->Apple ID->Sign out.
    Repeat the process, for Facetime, Messages, Mail and any other App you need to sign out of.

  • Can't remove or redeploy one process on 10.1.3.5

    The 10.1.3.5.0 WEB BPEL Console appears to be different from the older one. I use to always be able to undeploy a BPEL process to clean up an deployment issue, but this new interface is different. I have one BPEL process which some how got deployed (sorta) on the server, and I can't get rid of it. The process has a yellow triangle showing and when I click on the triangle or process name I get the following WEB page:
    >
    ServerException
    The process handle "MSS_DEV_Master" (revision "2.6") has not been loaded. The process may have failed to load properly. Please use the method "getErrors" for more information.
    An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
    Build Information
    Oracle BPEL Server version 10.1.3.5.0
    Build: 0
    Build time: Thu Aug 06 22:23:54 PDT 2009
    Build type: release
    Source tag: PCBPEL_10.1.3.5.0_GENERIC_090806.2156.1900
    Exception Trace
    1. com.oracle.bpel.client.BPELProcessHandle.checkIfLoaded BPELProcessHandle.java@671
    2. com.oracle.bpel.client.BPELProcessHandle.getMetaData BPELProcessHandle.java@234
    3. displayProcess.jspService _displayProcess.java@96
    4. com.collaxa.cube.fe.JspPage.service JspPage.java@42
    5. javax.servlet.http.HttpServlet.service HttpServlet.java@856
    6. oracle.jsp.runtimev2.JspPageTable.service JspPageTable.java@473
    7. oracle.jsp.runtimev2.JspServlet.internalService JspServlet.java@594
    8. oracle.jsp.runtimev2.JspServlet.service JspServlet.java@518
    9. javax.servlet.http.HttpServlet.service HttpServlet.java@856
    10. com.evermind.server.http.ResourceFilterChain.doFilter ResourceFilterChain.java@64
    11. oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
    12. java.security.AccessController.doPrivileged
    13. javax.security.auth.Subject.doAsPrivileged Subject.java@517
    14. oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
    15. com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@644
    16. com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
    17. com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward ServletRequestDispatcher.java@280
    18. com.evermind.server.http.ServletRequestDispatcher.access$100 ServletRequestDispatcher.java@68
    19. com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun ServletRequestDispatcher.java@214
    20. oracle.oc4j.security.OC4JSecurity.doPrivileged OC4JSecurity.java@284
    21. com.evermind.server.http.ServletRequestDispatcher.forward ServletRequestDispatcher.java@219
    22. com.collaxa.cube.fe.DomainFilter.doFilter DomainFilter.java@231
    23. com.evermind.server.http.EvermindFilterChain.doFilter EvermindFilterChain.java@15
    24. oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
    25. java.security.AccessController.doPrivileged
    26. javax.security.auth.Subject.doAsPrivileged Subject.java@517
    27. oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
    28. com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@642
    29. com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
    30. com.evermind.server.http.HttpRequestHandler.doProcessRequest HttpRequestHandler.java@908
    31. com.evermind.server.http.HttpRequestHandler.processRequest HttpRequestHandler.java@458
    32. com.evermind.server.http.AJPRequestHandler.run AJPRequestHandler.java@313
    33. ...
    >
    How can I clear this up for the server? I tried redeploying with the same BPEL process and version, but that appears to be ignored (though the server says it was successful). I then got rid of the *.../bpel/domains/grc/tmp/{bpel suitcase folder}* but that didn't affect anything as well. Bouncing the 10g server after removing the TMP folder for the suitcase jar didn't do anything as well.
    Any suggestions would be appreciated.

    ok... please follow the below steps.
    go to your orabpel schema in the db and execute the below queries
    delete from process where process_id="BPEL_PROCESS_NAME"
    delete from process_descriptor where process_id="BPEL_PROCESS_NAME"
    delete from process_log where process_id="BPEL_PROCESS_NAME"
    delete from process_default where process_id="BPEL_PROCESS_NAME"
    and the rebounce the server.. you will not see that process in the BPEL Console

  • Xi 3.0: Mail adapter fails with "exception in method process"

    Hi.
    I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
    Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
    I tried both async and sync case with the same result. In the sync case, the response contains:
    <!--  Call Adapter   -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="PARSING">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Any idea???

    Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
    Anyway, in my server i get a 404 for the link you suggested.
    In the async case i don't get any error on the SXMB_MONI but only on the A.F.
    I attach the audit log for the async case:
    Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
    Time Stamp Status Thread ID Sequence No. Description
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
    2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
    2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
    2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
    2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
           Total: 33 Entries   1020304050 messages displayed per page; this is page 1 of  1 page(s)     

  • Document/literal style wsdl with more than one port

    Recently I have changed wsdl style from rpc/encoded to document/literal as BPEL does not handle soapenc:arrayType. The wsdl contains 2 operations and few complex type definitions.
    In BPEL Designer I have created a process that invokes all operations defined in the wsdl, but only one of them will have some data in the response message and the other one will have an empty message. On the other hand, when I use stub generation to invoke Web Service everything is working fine.
    If I provide separate wsdl for each operation (in BPEL process I would have two partnerLinks instead of one) than it works fine.
    Does this mean that BPEL does not handle document/literal style endpoints with more than one port (operation)?
    I have tested this with the orabpel_2.0_J1_win32.exe and orabpel_2.0rc9_win32.exe. Web Services, used for this test, are deployed in Jboss 3.2.3 and axis-1_2beta3.
    WSDL used as partnerLink:
    <?xml version="1.0" encoding="UTF-8" ?>
    <wsdl:definitions targetNamespace="http://test" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://test" xmlns:intf="http://test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
    <schema elementFormDefault="qualified" targetNamespace="http://test" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="CardId">
    <sequence>
    <element name="cardType" nillable="true" type="xsd:string" />
    <element name="number" nillable="true" type="xsd:string" />
    </sequence>
    </complexType>
    <complexType name="CardIdArray">
    <sequence>
    <element maxOccurs="unbounded" name="item" nillable="true" type="impl:CardId" />
    </sequence>
    </complexType>
    <element name="getCardsReturn" type="impl:CardIdArray" />
    <complexType name="CardholderCards">
    <sequence>
    <element maxOccurs="unbounded" name="cards" nillable="true" type="impl:CardId" />
    <element name="serialNumber" nillable="true" type="xsd:string" />
    </sequence>
    </complexType>
    <element name="retrieveChReturn" type="impl:CardholderCards" />
    </schema>
    </wsdl:types>
    <wsdl:message name="retrieveChRequest" />
    <wsdl:message name="getCardsRequest" />
    <wsdl:message name="retrieveChResponse">
    <wsdl:part element="impl:retrieveChReturn" name="retrieveChReturn" />
    </wsdl:message>
    <wsdl:message name="getCardsResponse">
    <wsdl:part element="impl:getCardsReturn" name="getCardsReturn" />
    </wsdl:message>
    <wsdl:portType name="TestService">
    <wsdl:operation name="getCards">
    <wsdl:input message="impl:getCardsRequest" name="getCardsRequest" />
    <wsdl:output message="impl:getCardsResponse" name="getCardsResponse" />
    </wsdl:operation>
    <wsdl:operation name="retrieveCh">
    <wsdl:input message="impl:retrieveChRequest" name="retrieveChRequest" />
    <wsdl:output message="impl:retrieveChResponse" name="retrieveChResponse" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="TestServiceSoapBinding" type="impl:TestService">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="getCards">
    <wsdlsoap:operation soapAction="" />
    <wsdl:input name="getCardsRequest">
    <wsdlsoap:body use="literal" />
    </wsdl:input>
    <wsdl:output name="getCardsResponse">
    <wsdlsoap:body use="literal" />
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="retrieveCh">
    <wsdlsoap:operation soapAction="" />
    <wsdl:input name="retrieveChRequest">
    <wsdlsoap:body use="literal" />
    </wsdl:input>
    <wsdl:output name="retrieveChResponse">
    <wsdlsoap:body use="literal" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="TestServiceService">
    <wsdl:port binding="impl:TestServiceSoapBinding" name="TestService">
    <wsdlsoap:address location="http://localhost:8080/axis/services/TestService" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

    Hi Dragana,
    We definitely support the ability to call a web service that exposes two operations (document/literal or not).
    Glancing through your WSDL, it looks good.
    Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
    Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
    Thank you,
    Edwin
    [email protected]
    please rename .zip to .zap

  • Some images do not display in browser, iPad Air 2.  When I load a page with several jpgs (one 1920x720, then 8-10 800x800px), only the first few are shown.  Behaviour is similar for Safari and Chrome. Website issue or iPad?

    I have just bought an iPad, partly to check that my websites work OK on mobile devices.   When I load a page with several jpgs (e.g. one 1920x720, then 8-10 800x800px), only the first few are shown.  If I remove the large one, that sometimes fixes the problem. Behaviour is similar for Safari and Chrome. Is this a website issue or iPad?

    Sorry, I didn't make myself clear.  I'm using a new Wordpress theme that is meant to be responsive.  The large image is for a header, than you scroll down to see the rest, one by one.  Some one the pages work OK on my iPad, typically the old ones where the maximum image size was 500 x 500.  It's the new pages and those I've updated that are causing the problem.  On the iPad the large image loads, then a couple of the small ones become visible as I scroll down, but then darkness (rather like my knowledge level).
    Being new to IOS and iPads, I'm trying to work out whether I should be looking here, or amongst the Wordpress stuff for a solution.
    Here's the website with its new theme: http://www.new-zealand-pictures.com/

  • Service interface with more than one operation

    Hi all,
    is it possible to have a service interface with more than one operation?
    I have found this blog:
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0209118050DB10459657028039341762End?blog=/pub/wlg/15123
    But this sentence:
    ABAP proxy (inbound/ outbound) cannot be developed out of a Service Interface having Operations with different type of messages included. If an ABAP proxy is to be developed then all the messages included should be of one type i.e. either the included messages should be Message Type, External Message, IDOC or RFC Message. This behavior can be observed when a Service Interface is created and then subjected for a check
    regards

    Hi,
    now the interface is running but I get another error in .NET.
    "The header 'Diagnostic' from the namespace 'http://sap.com/xi/XI/Message/30' was not understood by the recipient of this message, causing the message to not be processed.  This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process.  Please ensure that the configuration of the client's binding is consistent with the service's binding. "
    Any ideas?
    regards

  • Should we use only one process order for each CO-product?

    Dear All,
    We have process orders.  One process order opens per day.
    Now we need to use CO-products and calculate actual cost of goods manufactured for them.
    Suppose we have 30 process orders. We have specified  Apportionment Structure in Material Master.
    Then when we create process order we  define actual Apportionment Structure in setllement rule as well.
    After we have setlled all process orders would Material Ledger/ Actual costing run consider this Apportionment Structures from all 30 process orders?
    I heard opinion from Consultant from SAP that it will not work.
    Has anyone heard anything?
    Best regards,
    Kamila.

    Hi Evgeniy,
    Thanks for response
    But we use process orders, not CO-production orders.
    We open process order each day because management wants to have information about KPI of each schift.
    We have defined in material master apportionment structure, When we create process order we define apportionment structure in settlement rule as well.
    When we settle process orders our cost distributes to finished good and CO-product according with this apportionment structure.
    But when we run ckmlcp ML/actual costing doesn't distribute raw material's price differences and Semifinished good's price differences according with this apportionment structure.
    What can we do here?
    Best regards,
    Kamila.

  • Create a dynamic search in JSP with more than one datasource

    Hello,
    In the ViewCiteria tag you can specify the datasource in which you want to place the criteria. Is it also possible to work with more than one datasource ?
    In my project I want one query form for specifying criteria for more than one datasource. When I send the query form, I want the right view criteria will be coupled with the right datasource.
    Has someone more experience with that ???
    Thanks!!!

    Hi,
    I think I got the same problem! I tried to combine all the tables in a new view and create a query on this view.
    But when I search and my result has to be one record from the main table, I get this record more than once.
    I tried to use distinct but that does not work because each column has a different value, so the record is never the same.
    I hope someone can help us!

  • EAX issues in games with Audigy SE, one way or the ot

    Hello everyone. I hope I'm asking for help in the correct forum. If not, please forgive my noobishness. =)?I don't know what's wrong, but EAX in Bioshock has terrible issues. I have XPx64 SP2, Audigy SE and when my corvette was new, I obtained SoundBlaster drivers specifically for x64 from April 06. But these were terrible. In many games (f.e. FEAR) the sound was terribly distorted after a while with unbearable loud mechanic buzzing. I had a serious issue in Oblivion as it was rebooting my computer when I was loading a game and it took me a while until I realized that the x64 drivers are causing it. I got rid of them and installed reference drivers I bought on CD with the card and everything was fine. Now Bioshock came out. Overall the EAX works good in it, but I have some serious crackling. I tried to lower the sound channels/streams values in INI, but it didn't remove crackling. So I though I would update drivers again. Indeed, Creative has released unified drivers for XP and Vista last July. I installed them, launched Bioshock with EAX ON, loaded a game and ... AARGH, my ears! The sound was like zapping loudly and rapidly, a real acoustic horror. This means I have serious EAX issues with all newer drivers than the reference ones on CD, but even with the new ones I have crackling in Bioshock anyway, with addition of the audio distortion. I have tried to turn off EAX and use CMMS3D instead, with Reverb which doesn't seem to cause any problems in BS. The sound was deep and rich, except that the crackling and stuttering is still there!?No flawless sound for me. Is my Soundblaster physically borked or something... =(?

    Well, I know that with SE, EAX processing is left for the CPU. You think this would be the source of problem?
    I have no option to select from software or hardware mode in games' audio menu, devs normally don't do add that option to audio menus (at least I never seen it in any game yet). In games I can normally only select whether I want EAX or not, or just like in case of BioShock, whether I want to turn Reverb on or off, and it would be left for the drivers to call the CPU to process EAX.Message Edited by RogueKeeper on 0-6-200707:5 AM

  • How to deal with Fixed Assests in Process Enabled Orgs?

    How to deal with Fixed Assests in Process Enabled Orgs
    We have a Process Organization - Food Industry , We are implimenting the Process Manufacturing . But we also have plenty of machines etc i.e. Fixed assets.
    Can any one suggest how to deal with this Process Org, So that i dont need to create another Discrete Org only for Fixed Assets.
    Also note that EAM is also in scope in the next Phase, Any suggestion is highly appreciated.

    Hi
    There is no possiblity of making your Process enabled Org as EAM enabled, and you must have to create a Discrete Org where in you can make this as EAM enabled.
    In R12/11i Process Enabled items/inventory items are dealt with only process, and that is the reason we can maintain an Assest item to Process enabled org which is a constriant. Hence it is adviced that, create an Inv Org (Discrete) and Enable this for EAM.
    Hope this is clear.
    Regards
    Raj
    Sierra Atlantic

  • Add at least one process to the chain before saving !!!

    Hello SDN s,
    How ya all ?
    I am building a Process Chain which loads around 35 Transactional Data InfoPackages. For this the requirement is to Delete Indexes collectively before the 35 data loads and after the data loads the Indexes has to be Generated.
    Here i D&D the Data Target Administration -> Delete Index with that Create Index (Generated from DROPINDEX) came automatically. I removed the link between these 2, and tried to keep the 1 st InfoPackage with Execute InfoPackage, it gave me the message
    Display More Chains:
    Process Z_DELODS (type DROPCUBE) has already been used in other chains
    Do you want these chains to be displayed in the maintenance screen too
    Yes / No / Cancel
    Then i tried to save or activate the PC it throws this message "Add at least one process to the chain before saving"
    What could be the problem here ?
    Best Regards....
    Sankar Kumar
    +91 98403 47141

    Hi,
    Please select <b>No</b> when it displays the message
    Display More Chains:
    Process Z_DELODS (type DROPCUBE) has already been used in other chains
    Do you want these chains to be displayed in the maintenance screen too
    Yes / No / Cancel
    Include atleast one process after the start process before saving..
    Hope this helps you...

  • Problem with a stuck yellow process chain

    Hi all,
    I have a problem with a stuck yellow process chain.
    A Meta chain calling a sub chain. The sub chain loads some master data.
    Some months ago one process stopped in yellow, no processes still running.
    So after that day when the meta chain runs the error msg is as follows
    Diagnosis                                                                               
    The previous run of the current subchain, BW_METADATA_MD_ST , is not yet   
         complete. This leads to communication errors with the metachain called,    
         BW_METADATA_MD .                                                                               
    System response                                                                               
    The current run of the metachain is cancelled.                                                                               
    Procedure                                                                               
    1.  End the previous run of the subchain, or wait until the run is         
             complete.                                                              
             It does not matter whether the run was successfully completed or       
             not.                                                                               
    2.  Restart the metachain.                                                 
    How do I end the previous run of the subchain?
    There is no process running, just want to set the flag to ended.
    Thanks in advance.
    BR
    Lars
    Message was edited by:
            Lars Johnsson

    Hi Lars,
       Have a look this web log : Restarting Processchains
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Hope it Helps
    Srini

Maybe you are looking for