INV와 WIP TRANSACTION에 대한 COST MANAGER의 ERROR발생시 처리방법

제품 : MFG_INV
작성날짜 : 2004-05-20
INV와 WIP TRANSACTION에 대한 COST MANAGER의 ERROR발생시 처리방법
====================================================
PURPOSE
Inventory와 WIP Transaction에 대해 Inventory Cost manager가
정상적으로 작동하지 않고 Error가 발생한 경우, Data Fix방법에
대해 기술하고자 한다.
Explanation
Cost Manager는 다음의 Transaction들에 대해 처리한다.
1. Material transactions
2. WIP Resource transactions
Cost Manager가 수행 시 정상적으로 처리하지 못한 경우,
다음과 같이 Error처리를 한다.
(1) mtl_material_transactions의 costed_flag = 'E'
(2) wip_cost_txn_interface에 data가 존재한다.
:정상적으로 수행한 경우, Interface table에서 Record가 삭제된다.
1. To resolve the Material transactions:
Select request_id, costed_flag, transaction_group_id
from mtl_material_transactions
where costed_flag is not null;
(If this picks up any records - uncosted transactions exist).
update mtl_material_transactions
set request_id = null,
costed_flag = 'N',
transaction_group_id = null
where costed_flag is not null;
2. To resolve any WIP transactions:
Select request_id, group_id, process_status
from wip_cost_txn_interface;
(ie. only uncosted transactions exist in this table)
Update wip_cost_txn_interface
set request_id = null,
group_id = null,
process_status = 1;
The next Cost manager run should pick up the transactions and
reprocess them
Example
Reference Documents
-------------------

Similar Messages

  • No Cost management error

    Dear all,
    I have got an error while creating service notification with reference to service contract(wv). I am getting an error like " no cost management is provided for sales document item : item no: 40000146
    code : ix057 "
    please send me the solution as soon as
    thanks in advance

    Hi ,
    Your thread is related to Customer Services Module, you can post such issues in Forum called u201CEnterprice Asset Managemnt (EAM)u201D in sdn. Sap. Forum.
    This error is common when you maintain, service contract type u201CWVu201D.
    W.r.t  your proble just go to u201CVa42u201D and select your contract then for the line item you go to u201CProcurementu201D tab and change the u201CRequirment type u201C to  u201CSE or  KEu201D, save and execute.
    Please make sure to maintain all configurations pertaining to service contract type u201CWVu201D in CS module .
    I am sure this error will not be repeated.
    If your thread is solved then please mark thread as solved
    Thanks and Regards
    DSR
    Edited by: D.Srinivasa Rao on Nov 2, 2011 8:13 AM
    Edited by: D.Srinivasa Rao on Nov 2, 2011 12:15 PM

  • WIP TRANSACTION를 조회 화면에서

    제품 : MFG_WIP
    작성날짜 : 2005-05-30
    WIP TRANSACTION를 조회 화면에서 "DISTRIBUTION" BUTTON이 비활성화됨
    =====================================================
    PURPOSE
    WIP Transaction를 조회하는 화면에서 "Distribution" Button이
    비활성화된 원인 및 해결 방법
    Problem Description
    WIP Transaction를 조회하는 화면에서 "Distribution" Button이
    비활성화되어 distribution에 대한 정보를 조회할 수 없음.
    Workaround
    N/A
    Solution Description
    원인 > WIP Job관련 Transaction들에 대해 Cost manager를
    통해 Costing되지 않은 상태임.
    Fix방법>
    1. cost manager가 Active상태인지 확인
    Navigation path: Inventory > Setup > Interface manager
    2. transaction이 Costed되었느지 확인
    Navigation Path: Cost > View Transactions > Material Transactions
    the reason and reference tab 확인
    3. Run the following sql script:
    select costed_flag, transaction_group_id
    from mtl_material_transactions
    where costed_flag IN ('E','N');
    Return되는 data는 아직 Costing되지 않은 data임.
    4. Error가 발생한 Data는 다음과 같이 data를 초기화한다.
    update mtl_material_transactions
    set costed_flag = 'N',
    transaction_group_id = NULL,
    transaction_set_id = NULL
    where costed_flag = 'E' or costed_flag = 'N'
    Reference Documents
    Note:257408.1

  • COST MANAGER 가 ITEM TRANSACTION 에 대하여 COSTING을 수행하지 않는 경우의 처리.

    제품 : MFG_INV
    작성날짜 : 2004-05-25
    COST MANAGER 가 ITEM TRANSACTION 에 대하여 COSTING을 수행하지 않는 경우의 처리.
    ==============================================================
    PURPOSE
    COST MANAGER 가 ITEM TRANSACTION 에 대하여 COSTING을 수행하지 않는 경우의 처리.
    적용 : Oracle Inventory 11
    Oracle Inventory 11.5
    CMCTCM Cost Manager
    Problem Description
    COST MANAGER 가 ITEM TRANSACTION 에 대하여 COSTING을 수행하지 않아 분계
    가 생성되지 않은 데이터가 존재함.
    데이터의 상태는 MTL_MATERIAL_TRANSACTIONS의 COSTED_FLAG, ERROR_CODE, ERROR_EXPLANATION 이 Null 임.
    MTL_MATERIAL_TRANSACTION_TEMP 의 ERROR_CODE = Null 이고,
    ERROR_EXPLANATION = "Transaction Processor Error" 임.
    원인: MTL_MATERIAL_TRANSACTIONS 의 COSTED_FLAG 값이 NULL
    이고, TRANSACTION_GROUP_ID 에 값이 존재함. 그러므로 CMCMCW (Material
    Cost Transaction Processor) 가 이 데이터를 처리하지 않음.
    CMCMCW: 이 프로그램은 INV 와 WIP의 material transactions 의 costing 을
    진행시킨다. 이 프로그램은 mtl_material_transactions 에서 uncosted
    transactions 찾는다. 예) where costed_flag='N'& transaction_group_id=NULL.
    검색된 데이터에 대하여 INLTCP 이 호출되어 처리된다.
    Workaround
    N/A
    Solution Description
    1. SQL*PLUS 를 이용하여 해당 데이터를 아래와 같이 update 한다.
    SQL>
    UPDATE mtl_material_transactions
    SET
    costed_flag = 'N',
    error_code = NULL,
    error_explanation = NULL,
    transaction_group_id = NULL
    WHERE
    costed_flag = 'N'
    AND transaction_group_id is NOT NULL;
    2. Cost Manager 는 schedule 되어 수행된다.
    Reference Documents
    Note:156954.1 - The Cost Manager Is Not Costing An Item Transaction

  • Slowness in Cost Manager costing the Inventory Transactions : performance

    Hi All,
    We have just upgraded to R12.0.6 and we are facing performance issues with the Cost Manager ..it is costing the Inventory/Material transactions very very slowly..about 1-2 Inventory transactions are getting costed within a minute.
    The Actual Cost workers are taking a lot of time to process the transactions as well..
    Could someone please suggest or help us troubleshoot this issue , as this very critical as we are facing this performance issue in 12.0.6 production enviornment.
    Thanks
    Sachin

    Hi,
    Can you find any errors in the CM/DB log files? Do you run Gather Schema Statistics and Purge Concurrent Manager/Programs on regular basis?
    Please see if these documents help.
    Note: 387669.1 - Cost Manager Performance Issues
    Note: 304313.1 - Understanding Cost Manager
    Could someone please suggest or help us troubleshoot this issue , as this very critical as we are facing this performance issue in 12.0.6 production enviornment.If the issue with your production instance, I would suggest you log a SR.
    Regards,
    Hussein

  • Error in mtl_material_transactions  Cost Manager

    Hi,
    I am using EBS-R12 I want to find per unit costl.But I find in mtl_material_transactions Costed_flag=E
    and ERROR_EXPLANATION='The transaction date is not within the accounting period specified.' & inventory costing methods
    is average.
    I have update apply update
    update mtl_material_transactions
    set costed_flag = 'N',
    transaction_group_id = NULL,
    transaction_set_id = NULL
    where costed_flag = 'E' or costed_flag = 'N' ;
    and apply relaunch cost manager but Coted_flag remain unchanged.
    Please help me about this issue.
    Regards
    Omar

    Dear Hassan,
    My problem is resolved now. I have apply update on mtl_material_transactions with period_id.
    So thanks for cordial co-operations & positive approach.
    Thanks
    Omar
    Edited by: user13140975 on Mar 10, 2012 11:59 AM

  • Material Transaction Open Interface Error

    Hi,
    I'm getting following Error in Cost Manager after running the Transaction Open Interface,
    Interface work well to update the stocks, but it returns error Layer Cost Worker Concurrent.
    Error1
    Bills of Material: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    CMCLCW module: Layer Cost Worker
    Current system time is 10-OCT-2012 14:16:32
    debug_level = 0
    CM_EXTENDED_DEBUG = 2
    CSTPLCIN.COST_INV_TXN:CSTPLVCP.interorg (160): ORA-00001: unique constraint (INV.MTL_CST_TXN_COST_DETAILS_U1) violated
    Failing Transaction ID is 28227
    Start of log messages from FND_FILE
    Standard costing org : -1
    Interorg transfer send org: (consume layers) ...
    84:5
    28227:1
    Entering get_layers_consumed for transaction 28227 and a required quantity of 2 with a consumption mode of NORMAL
    Trying custom layers
    There are 0 custom layers
    General consumption
    Using SQL SELECT inv_layer_id,layer_quantity FROM cst_inv_layers WHERE layer_id = :i AND inv_layer_id <> :j AND NVL(transaction_source_id,-2) <> :k AND layer_quantity > 0 ORDER BY creation_date, inv_layer_id with 1,-1,-1
    End of log messages from FND_FILE
    No completion options were requested.
    Output is not being printed because:
    The print option has been disabled for this report.
    Deleting output file.
    Concurrent request completed
    Current system time is 10-OCT-2012 14:16:32
    Error2
    Bills of Material: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    CMCLCW module: Layer Cost Worker
    Current system time is 10-OCT-2012 14:16:32
    debug_level = 0
    CM_EXTENDED_DEBUG = 2
    CSTPLCIN.COST_INV_TXN:CSTPACDP.insert_account (10) ORA-01400: cannot insert NULL into ("INV"."MTL_TRANSACTION_ACCOUNTS"."BASE_TRANSACTION_VALUE")
    Failing Transaction ID is 28228
    Start of log messages from FND_FILE
    Standard costing org : -1
    ----------l_to_method---------
    =5
    Interorg transfer receiving org: (create layers) ...
    90:5
    28228:2
    i_txn_id 28228
    1 records updated in mclacd for 15005
    1 records copied from mclacd for 15005
    interorg_cost_txn(..)
    transaction_id:28228
    org_id:90
    i_txn_org_id:90
    i_txf_org_id:84
    i_txf_txn_id:28227
    i_exp_item:0
    i_fob_point:0
    l_snd_rcv:2
    l_from_org:84
    l_to_org:90
    Sending org distributions
    Receiving org distributions
    l_intransit:0
    Calling Inventory acct
    In Inventory_accounts
    In insert accounts
    l_ussgl_tc :
    Payable amount(l_value): acct: 414240
    In insert accounts
    l_ussgl_tc :
    DS - others Exception, sqlcode = -1400
    End of log messages from FND_FILE
    No completion options were requested.
    Output is not being printed because:
    The print option has been disabled for this report.
    Deleting output file.
    Concurrent request completed
    Current system time is 10-OCT-2012 14:16:32
    My Coding
    insert into mtl_transactions_interface
    (transaction_type_id, --------------1
    transaction_uom, --------------2
    transaction_date, --------------3
    organization_id, --------------4
    transaction_quantity, --------------5
    last_update_date, --------------6
    last_updated_by, --------------7
    creation_date, --------------8
    created_by, --------------9
    transaction_mode, --------------10
    process_flag, --------------11
    source_header_id, --------------12
    source_line_id, --------------13
    source_code, --------------14
    transaction_header_id, --------------15
    inventory_item_id, --------------16
    transaction_interface_id, --------------17
    subinventory_code, --------------18
    distribution_account_id, --------------19
    transaction_cost, --------------20
    transaction_reference, --------------21
    transfer_organization, --------------22
    transfer_subinventory, --------------23
    -- transfer_cost, --------------24
    primary_quantity, --------------25
    lock_flag,
    transaction_action_id,
    transaction_source_type_id,
    dst_segment1,
    dst_segment2,
    dst_segment3,
    dst_segment4,
    dst_segment5,
    dst_segment6)
    values
    (v_trx_type_id, --------------1 ------transaction type id
    i.uom_code, --------------2 ------transaction_UoM
    sysdate, i.creation_date, ------------3 ------trasnsaction date
    i.from_organization_id, --------------4 ------org id
    nvl(i.quantity_delivered, i.quantity), --------------5 ------quantity
    sysdate, --------------6 ------Last update date
    -1, --------------7 ------last updated by
    sysdate, --------------8 ------creation date
    -1, --------------9 ------creation by
    3, --------------10 ------transactio mode
    1, --------------11 ------process flag
    1, --------------12 ------source_header_id
    1, --------------13 ------source_line_id
    i.mrn_trx_number, --'MRN Interface', --------------14 ------source code
    '999999', --------------15 ------transaction header id
    v_item_id, --------------16 ------inventory item id
    xx_mrn_mtl_trx_int_seq.nextval, --------------17 ------transaction_interface_id
    i.from_subinventory_code, --------------18 ------sub inventory
    v_code_id, --------------19 ------code compbination
    v_item_cost, --------------20 ------cost
    'MRN Interface', --------------21 ------reference
    i.organization_id, --------------22
    i.to_subinventory_code, --------------23
    -- (nvl(i.quantity_delivered, i.quantity) * v_item_cost) --------------24
    nvl(i.quantity_delivered, i.quantity),
    2,
    v_trx_action_id,
    v_trx_source_type_id,
                   '01',
                   '00',
                   '000',
                   '141013',
                   '000000',
                   '00000');
    Thanks

    Can you get the following for the errored transaction?
    SELECT   transaction_id txnid, transfer_transaction_id txfrtxnid
           , organization_id orgid, transfer_organization_id txfrorgid, subinventory_code subinv
           , transfer_subinventory txfrsubinv, cost_group_id cgid
           , transfer_cost_group_id txfrcgid       , prior_costed_quantity
           , transfer_prior_costed_quantity       , rcv_transaction_id rcvtxnid
           , transaction_action_id txnactid       , transaction_source_type_id txnsrctypid
           , transaction_type_id txntypid       , costed_flag cstdflg
           , transaction_group_id       , inventory_item_id invitmid
           , transaction_source_id wip_entity_id       , transaction_cost txncst
           , shipment_number shipnum       , new_cost       , prior_cost
           , actual_cost       , project_id       , transaction_uom txnuom
           , transaction_quantity txnqty       , primary_quantity priqty       , prior_costed_quantity priorqty
           , currency_code altcurr       , currency_conversion_rate currconvrt       , currency_conversion_date currconvdt
           , TO_CHAR (mmt.creation_date, 'dd-mm-yyyy hh24:mi:ss') creation_date
           , TO_CHAR (mmt.last_update_date, 'dd-mm-yyyy hh24:mi:ss')last_upd_date
           , ERROR_CODE errcode
           , error_explanation errexpl
        FROM mtl_material_transactions mmt
       WHERE transaction_id IN (&Trx_Id)   -- Error transaction_id
    ORDER BY transaction_id DESC

  • Mass sales order costing(ck55) error

    hi
    If i do individual sales order costing , no error.But same sales order has done in ck55,error"item is not relevant for billing" ,but in single sales order costing is ok, .what is reason.
    system message
      Item is not relevant for billing
        Message no. CK_MCSO029
    Note
        You can remove this message from the log with the customizing
        transaction User-Defined Error Management for Mass Costing of Sales
        Documents. The item will still not be costed, however.
    Diagnosis
    System Response                   
    reg
    nagesh
    Edited by: nageshrr on Jul 5, 2011 2:01 PM
    Edited by: nageshrr on Jul 5, 2011 2:04 PM

    no replies and my thread was dead.

  • ESYU: Cost Manager(CMCTCM)을 cancel 하고 다시 실행하는 방법

    Purpose
    Oracle Cost Management - Version: 11.5.9 to 11.5.10
    Information in this document applies to any platform.
    MTL_MATERIAL_TRANSACTIONS(MMT) table에 costed_flag = E 인 error transaction이
    존재하는 경우 debug를 위해 cost manager를 다시 실행해야 될 경우가 있다.
    보통 Cost Manager는 일정 주기로 running 되고 있기 때문에 이를 cancel 하는
    작업이 필요하다.
    여기서는 실행중인 Cost Manager를 cancel 하는 방법을 알아본다.
    아래 사항을 방지하면서 Cost Manager를 cancel 하는 방법:
    - 동시에 여러개의 Cost Manager가 launch 되는 것
    - CMCTCM log에서 아래와 같은 warning message가 발생 되는것
    " A Cost Manager is already launched.
    Action: If you want to launch a new manager, cancel earlier manager first."
    Solution
    1. Cost Manager를 cancel: 아래 방법 중 하나를 선택한다.
    a) Use Sysadmin responsability
    Navigate to /Request/view
    Set : specific Request=on
    Name=Cost Manager.
    Find request 화면의 아래쪽에 있는 "Select the Number of Days to view"
    field에 9999를 입력한다.
    조회된 Request 중 Pending Scheduled 상태의 Cost Manager request를
    찾아 request를 cancel 한다.
    b) Run
    SELECT request_id RequestId,
    request_date RequestDt,
    concurrent_program_name,
    phase_code Phase,
    status_code Status
    FROM fnd_concurrent_requests fcr,
    fnd_concurrent_programs fcp
    WHERE fcp.application_id = 702
    AND fcp.concurrent_program_name in ('CMCTCM', 'CMCMCW', 'CMCACW')
    AND fcr.concurrent_program_id = fcp.concurrent_program_id
    AND fcr.program_application_id = 702 AND fcr.phase_code <> 'C';
    위 script 결과로 나오는 모든 requests를 /Sysadmin / Concurrent / Request
    화면에서 query 하고 모든 request를 cancel 한다.
    이 request id를 query 시에도 역시 "Select the Number of Days to view" 값은
    '9999'로 입력한다.
    2. cmclean.sql script를 실행한다.(Note 134007.1 참조)
    3. Cost Manager를 restart 한다.
    Inventory / Setup / Transactions / Interface Managers
    on line 'cost manager' - do Tools > Launch
    Reference
    Note 373207.1

  • Set batch management  for reasons of cost management item cannot be deleted

    Discovery was made that a material should have had batch management MARC-XCHPF selected.  Within that time sales orders were created as well as sales order stock.  411E movements were done to get rid of the sales order stock, and it can not be seen in MMBE.  MD04 is also clear.  New attempt to add batch management in the plant displayed errors - SD Documents exist (orders or deliveries) that have not yet been
    processed or that have been processed only in part.            
       Document   Item                                             
       206365     000020
    Attempt to remove item 20 from sales order and receive error
    Message no. V1128
    For reasons of cost management, item 000020 cannot be deleted.
    Diagnosis
    You tried to delete a sales document item for which cost management is carried out. Cost management can exist at item level for
       - make-to-order production
       - make-to-order stock
       - service contract item
    Procedure
    Enter a reason for rejection at item level.
    I found a similar problem on the forum but not really a solution other than throwing in the towel and making new materials.

    Hi
    What I understand from your thread is:
    You have chekced batchmanagement in
    material master & after working some time you want to remove that tick mark.
    First of all one should understand that for what ever reason batch management is ON, you can not reverse it .
    Either activation or deactivation of batchmanagement is irreversible.
    Oflat SAP had come with a note telling that how to proceed with reversal batch management.
    I have gone through that note .Finally SAP wants to take consultancy with some fees to make reversal.
    It is all pain ful job.
    If you can do it abandom thta material & create new material.
    This is the solution I can give.
    Hope it is celar to you.
    Regards
    YMREDDY

  • MQSeries as a Transactional Resource Manager with Weblogic Server

              I am trying to setup the example given in the BEA white paper:
              Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              Version 1.
              October 25, 2001.
              I followed the instructions given in the documents, but when i run client program
              >java MQClient t3://localhost:7001 "MQSeries test"
              I received the following exception below. Does anyone how what is the reason for
              this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
              6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
              for java and the MQSeries classes for Java Message Service on the weblogic
              server machine.
              sending: "MQSEries test"
              Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
              sted exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              ; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              --------------- nested within: ------------------
              weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              [java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              ; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              at $Proxy1.bridgeWLS2MQS(Unknown Source)
              at MQClient.main(MQClient.java:54)
              

    The point is that over TCPIP the MQ XA connection factory is not available.
              The MQ shared memory/JNI driver is required to access it, which limits
              access to those processes that are on the same box as the MQ q manager.
              This is an MQ series limitation.
              Douglas WF Acheson wrote:
              > Hello,
              >
              > If memory server me correct, default connection to MQ Series is through
              > JNI calls and shared memory. You have to change the protocol to TCPIP when
              > connection to the queue manager on another box (do not know much about XA
              > with MQ Series); that is when you connect to MQ Series vi JMS on another
              > box you must do something like the following:
              >
              > qcf = new MQQueueConnectionFactory() ;
              > qcf.setHostName(hostName) ;
              > qcf.setPort(port) ;
              > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
              > qcf.setQueueManager(qManagerName) ;
              >
              > Then when you create you queues, sesions etc. you are point at the correct Q
              > manager.
              >
              > Hope this helps ...
              >
              > Douglas WF Acheson
              >
              > "Raja Mukherjee" <[email protected]> wrote in message
              > news:[email protected]...
              > > On a closer look at the original post (sorry for missing that, it was
              > early
              > > in the morning), you would not be able to use XA if your QM and WLS are in
              > > different boxes. Check on this newsgroup, there are several posts on this
              > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
              > on
              > > the sames box. This is a MQSeries limitation not WLS.
              > >
              > > .raja
              > >
              > >
              > > "ibrahim Nehme" <[email protected]> wrote in message
              > > news:[email protected]...
              > > >
              > > > I am trying to setup the example given in the BEA white paper:
              > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              > > > Version 1.
              > > > October 25, 2001.
              > > > I followed the instructions given in the documents, but when i run
              > client
              > > program
              > > >
              > > > >java MQClient t3://localhost:7001 "MQSeries test"
              > > > I received the following exception below. Does anyone how what is the
              > > reason for
              > > >
              > > > this exception(s) and how i can solve the problem? My MQSeries Server
              > and
              > > Weblogic
              > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
              > > classes
              > > > for java and the MQSeries classes for Java Message Service on the
              > weblogic
              > > > server machine.
              > > > ---------------------------------------
              > > > sending: "MQSEries test"
              > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
              > > server; ne
              > > > sted exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > > ; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > <<no stack trace available>>
              > > > --------------- nested within: ------------------
              > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ]
              > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
              > > > at MQClient.main(MQClient.java:54)
              > >
              > >
              

  • Cost Managment - CSTPPACQ.acq_cost_processor(30):ORA-01436: CONNECT BY loop

    Hi,
    We have run the program Periodic Aquisition Cost but it error out. the Error is
    CSTPPACQ.acq_cost_processor(30):ORA-01436: CONNECT BY loop in user data.
    Plz guide me.

    Hello,
    For this error, I think you should open an SR. It looks like patch 5378145 that is references in Metalink note 405966.1.
    It could be useful to run the Cost manager in Trace mode, in order to get the statement that fails.

  • Landed Cost manager Program is scheduled to run everyday but it did not run

    Hi All,
    Landed Cost manager Program is scheduled to run everyday but it did not run for 2 days and there was no error; it did not start even though it is a scheduled prog to run every 30 mins.
    Please let me know if anyone has experienced similar cases before; also let me know if you have any clue for above? I am also researching on if there is any way to send notifications when a scheduled prog did not run even.
    Any suggestions are welcome and also would like to get your thoughts on notification part if this is possible to track.
    Thanks
    De

    1006390 wrote:
    Hi All,
    Landed Cost manager Program is scheduled to run everyday but it did not run for 2 days and there was no error; it did not start even though it is a scheduled prog to run every 30 mins.
    Please let me know if anyone has experienced similar cases before; also let me know if you have any clue for above? I am also researching on if there is any way to send notifications when a scheduled prog did not run even.What if you submit the request manually, does it work?
    Assuming no error can be found in the DB/CM log files, have you verified the scheduled settings for this program? Try to schedule it again and see if this helps.
    Any suggestions are welcome and also would like to get your thoughts on notification part if this is possible to track.
    http://docs.oracle.com/cd/E18727_01/doc.121/e12951/toc.htm
    https://forums.oracle.com/forums/search.jspa?threadID=&q=Notify+AND+Concurrent&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001

  • Change sales order - for reasons of cost management item cannot be deleted

    Hello Friends,
      When I try to delete a line item from sales order below error is fired and it doesnot allows to delete the items which has a WBS element.
      The function name is :BAPI_SALESORDER_CHANGE
      The error message is as below:
        ORDER_HEADER_IN has been processed successfully
        For reasons of cost management, item 001001 cannot be deleted
        Error in ITEM_IN 001001
        KONVKOM has been processed successfully
        KONVKOM has been processed successfully
        KONVKOM has been processed successfully
        KONVKOM has been processed successfully
        KONVKOM has been processed successfully
        The sales document is not yet complete: Edit data
        Sales document 0002012766 was not changed
      Information
        Sales order: 0002012766
        Item       : 001001
        WBS element: 2012766-001 The wbs status is "REL"  
      I found a similar problem on the forum but not really a solution other than giving a suggestion as "Enter a reason for rejection at item level.".
    but when I put the field ORDER_ITEM_IN-REASON_REJ = 'Z1' and ORDER_ITEM_INX-REASON_REJ = 'X',the error is still occurring.
      'Z1'-WBS has been cancelled
      How can I remove this item from the sales order?
      Please help me.....
    Best Regards,
    bluebaby

    Hello Lakshmipathi,
      thank you very much for answering my question..
      But how I get the file SAP note 14097,I was search this file in SDN and google but cannot find this file,if you know pls give me a hyperlink to view the content,thanks a lot.
    Best regards,
    Sophia

  • Cost Planning Error

    Hi to All,
    My name is Samad Farooq, currently using SAP Version 4.6C
    When creating a cost plan using the transaction code KP06, error is encountered when we try to save the planned data. Error that is displayed is as follow “Ledger 4A has fiscal year variant V6 instead of K4”.
    This specific case is happening only when using the controlling area JVCS and company code MAZ. Company code MAZ uses a calendar year.
    Thanking You,
    Samad Farooq

    Samad.. chech out the process...
    The fiscal year variant contains the number of posting periods in the fiscal year and the number of special periods.
    You can define a maximum of 16 posting periods for each fiscal year in the Controlling component (CO). To define the fiscal year variant, go to Customizing for Financial Accounting (FI), Financial Accounting Global Settings--->® Fiscal Year -
    Maintain Fiscal Year Variant.
    Integration
    You need to specify the fiscal year variant for each company code.
    When you create a controlling area, you also need to specify the fiscal year variant. The fiscal year variants of the company code and controlling area may only differ in the number of special periods used. You need to ensure that the fiscal year variants match, in other words, they may not have a time conflict.
    You can assign a company code using a fiscal year variant with 12 posting periods and four special periods to a controlling area that has a fiscal year variant with 12 posting periods and one special period. The time frame, for example, from April 1 to March 31 in the following year, must be identical in each fiscal year variant.
    However, it cannot be assigned to a controlling area with 52 posting periods for example.
    For more information on fiscal year variants, see the SAP Library under AC Financials -
    FI Financial Accounting -
    FI General Ledger Accounting(FI GL) -
    FI - Closing and Reporting in Posting Periods and  Fiscal Years.
    Thank you

Maybe you are looking for

  • StarWalk no longer supports iPad wifi or iPod Touch

    On April 30 an update to StarWalk for iPad was released that disabled the applications use of the internal compass for wifi only iPads. On May 1 an update to StarWalk for iPhone was released that disabled the internal compass for iPod touches. There

  • Speaker system for MacPro

    Hi All, Sorry if this is a basic question but I have not been able to find an answer... I just purchased a new MacPro and want to get some speakers for it so I can listen to music and watch DVD's. I was thinking 5.1 surround but read that Apple does

  • Derivation rule CO-PA, number of target fields

    Hi all, is there a possibility to have more than 6 target fields in a CO-PA derivation rule or is the only way to handle more fields with a separate rule based on the same source field? thanks for your help kind regards Adrian

  • Firefox Services don't work

    None of 4 social services add their buttons or appear in Services tab of Addons. 'Restart with disabled addons' doesn't help. New FF profile works fine.

  • Dynamic JNLP causes exception on 1st run after java install

    I have a dynamic JNLP file (php) which runs my software. It works just fine, except for the 1st time it is run after a user has installed Java. I get the exception; "The following field was missing from the jnlp file: <jnlp>". When I look at the jnlp