MESSAGE TYPE Transaction

Hello experts,
Iu2019m new to IDoc and trying to learn and understand different aspects of it. Iu2019m unable to find which transaction I can use to see u2018MESSAGE TYPEu2019. Can anybody point out to me please?
Thanks a lot in advance.

Hi,
Creating Message Type:
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign message type to idoc type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Regards,
SuryaD.

Similar Messages

  • Need to ALE only 2 fields through a reduced message type copied from MATMAS

    Hi,
    Only the Authorization group fields MARA-BEGRU and MARC-QMATA need to be transferred through ALE from one system to another one.  A new reduced message type has been created from MATMAS.
    The fields BEGRU and QMATA have been selected through the BD53 transaction to be part of the segments.
    Result: 3 segments are part of the new Message type: E1MARAM and its 2 children E1MAKTM and E1MARCM.
    Problem:  Even the BD53 (Reduced message type) transaction has been used, too many unnecessary fields are transferred through the ALE. 
    The following fields in the E1MARAM segment must not been updated (transferred) in the receiving system:
              -  PSTAT,
              -  LVORM
              -  MTART
              -  MBRSH,
              -  MATKL,
              -  MEINS,
              -  GROES,
              -  WRKST,
              -  SPART,
              -  VPSTA.
    They should disappear from the segment.
    The E1MAKTM segment must not been transferred to the receiving system because the user does not want to modifiy the Material description.  But the BD53 (reduce message type) seems to consider that segment as mandatory.
    Only few 1EMARCM segments with specific Plants (WERKS) should be sent on the receiving system.  Not all the Plants.  That segment should not include the PSTAT field.  I have no control on which Plants to transfer.
    <u>Revision</u>:
    Only 2 segments must be ALE'd with only the following fields:
              1-  <b>E1MARAM</b>:
                        a)  MATNR (Material number)
                        b)  BEGRU (Authorization group)
              2-  <b>E1MARCM:</b>
                        a)  WERKS (Plant)
                        b)  QMATA (Material Authorization Group for Activities in QM).
    What should I do to ALE only those 2 segments and only those specific fields?
    Thanks a lot.
    Diane.

    Thanks Ferry for the previous answer,
    I have a problem with the E1MARCM segment.
    My sending and receiving systems do not have always the same Plant numbers.
    If a Plant exists on the sending system and it does not on the receiving system, the Plant must not be created on the receiving system. But from the sending system, I do not know which Plants the receiving system has. This is why the IDoc contains all the Plants. But I added some logic in the  <b>inbound</b> customer-function, EXIT_SAPLMV02_002, to ignore the Plants that do not exist on the receiving system in doing a SELECT on the MARC table in the receiving system.
    But that customer-function is called from the IDOC_INPUT_MATMAS01 function module, in the " WHEN  E1MARCM " section:
              PERFORM CHECK_USER_EXIT TABLES T_EDIDD
                                                                            USER_SEGMENTS
                                                               USING CURRENT TABIX.
              LOOP AT USER_SEGMENTS.
                         CALL CUSTOMER-FUNCTION '002'
                                   EXPORTING
                                                MESSAGE_TYPE    = IDOC_CONTRL-MESTYP
                                                F_CUST_SEGMENT = USER_SEGMENTS
              ENDLOOP.
    In the perform check_user_exit, no record is created in the user_segments table because all the segments in my IDoc start with ' E1 ' :
              LOOP AT IDOC_DATA INTO USER_SEGMENTS FROM CURRENT_TABIX.
                        IF USER_SEGMENTS-SEGNAM(2) = ' E1 '.
                            EXIT.
                        ENDIF.
                        APPEND USER_SEGMENTS.
              ENDLOOP.
    The customer-function is called within the ' loop at user_segments '. This is why the customer-function is never executed and my code is ignored. So, all the IDocs in the receiving system are in the status 51 (red light).
    Do you have any idea how to resolve my problem.
    Thanks.
    Diane.

  • Idoc Message type and Process Cosde for CJ01 transaction

    Hi,
    What is the Idoc message type and inbound Process code for CJ01 transdaction?
    Is there Any standard procedure to find out Idoc Mesage type and process codes for particular application?
    Thanks.

    Hi,
    All the sending and receiving programs(transaction) start with BD. e.g. if you want to send the material you can use the BD10 transaction and IDOC is available for the same.
    Go to se93 and search for BD* and look for the description.
    Regards,
    Nilesh.

  • IDOC Message type for FB01 transaction.

    Hi,
    I am going to get a file which I will pass through PI (XI) and bring into IDOC and post into SAP ECC 6.0.
    I just wanted to know which IDOC message type / basic type I should use for posting an FI document i.e. FB01 transaction.
    Rgds

    Hi,
    please read SAP notes 892103 and 551035.
    The correct IDOC type should be FIDCC1 / FIDCC2.
    Best regards,
    Andreas

  • What message type used by ALE in transactional data

    Hello friends,,,
          I wish to know what msg types are used in transactional data like PO, PR, etc in Materail tables???
    thanking you

    hello babi,
        Message Type         Technical Name
        Product                    PRODUCT
        Location Group/Assortment  LOCGRP
        Assortment Product         ASRTPRD
        Assortment Version         ASRTPRDVRSM
    Assortment Version for Space Management ASRTPRDVRSO
       Allocation and PO           ALLOCPO
       Markdown Proposals          MDPROP
        Open-to-Buy                 OTB
    complete details of ALE:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    REgards
    Varun

  • Automatic trigger of message type WE01 in VL32N transaction

    Hello,
    My requirment is to populate the message type WE01 in VL32N transaction.
    Please let me know the steps
    Regards,
    HK

    Hi,
    You have to maintain the CONDITION RECORDS for the WE01 output type
    Goto the Transaction code  NACE and click on the APPLICATION ME and click on the OUTPUT types in the MENU BAR
    select the OUTPUT type WE01 and assign the SMARTFORMS & PRINT PROGRAMS to the output
    Now assign this outpt to the OUTPUT determination procedure and
    Maintain the condition records for the OUTPUT
    Once you maintain the CONDITION RECORDS , then automatically it will be triggered to the INBOUND DELIVERY, in VL032N
    Please check them and let us know if you need any frther details
    regards,
    santosh

  • Modification of message type 519 in transaction ORFA

    Message Number 519 says that there is an customizing inconsistency for Cost-of-Sales Accounting. Since cost-of-sales accounting is active but the functional areas is not set as an account assignment object. There is a need to keep cost-of-sales active and not maintain the functional area of our legal entity. In other words, this current scenario must be maintained.
    The current scenario, however, prevents user from running depreciation by raising the message number 519 as the error. The type of this message needs to be modified from error to be just a warning. The message itself says that this can be done but the steps specified do not work:
    Use transaction ORFA->Transactions->Maintain Message Types
    Use Message Class AAPO and add entry for message 519.
    The error message 'Message Number 519 is not allowed' is raised.
    How do we convert Message Number 519 from error to warning?

    Hi
    Have you activated operting concern?
    If yes let us know in detail... to help you..
    Also as this is subjective raising a message to SAP would provide you effective solution...
    And changing the error to warning type is not advisable...
    still if you want to go for it .. spot the call up point for the particular message in the respective program with the help of ur abap consultant and change it with the access key...
    Regds
    Karthick Gopi

  • Transaction/Program to create message type LIP076 Idocs

    Hi Idoc Experts,
    Can you please let me know the T-code/program to send MD61(weekly forecast) data thru the idocs.
    FYI- I am planning to use message type LIP076 with basic type SOPGEN01
    Example: BD14 T-code to send the Vendor master details thru idoc.
    I am looking for a similiar transaction/program, so that it will create LIP076 idocs with MD61 details.
    Thankyou,
    Ravi

    Hello Ravindran
    You can also check the documentation in the below path and when you execute it it takes you to transaction SXDA. I am not authorized in my system, may be you can check more detailed in your system about the transaction..
    SPRO -- > IMG --> Production --> Production planning --> Demand management --> tools --> Data transfer workbench: planned independent requirements.
    Regards,
    Thanga

  • Definition of Message Type and Transaction Type from the Implementation per

    My assumption is that both, Notification Type and Message Types are same.
    <b>Is the above assumption right?</b>
    In Sol Man 4.0, the notification types required are
    1)     ABSC  2) SLF1 3) TASK
    <b>Are there any other notification types required for Sol Man 4.0?</b>
    The main transaction types required in Sol Man 4.0 are
    SLFI, SLFT and SLFN
    <b>What is the significance of External Number range and Internal Number range used in the transaction type?</b>

    Hi
    1 > A data type</i> in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
    The characteristic of columns and variables that defines what types of data values they can store. Examples include character, floating point and integer
    Check out the details:
    http://en.wikipedia.org/wiki/Data_type
    A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
    details:
    http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
    2) Regarding the difference between XI 3.0 and PI 7.0, this threads will clear your doubts:
    difference between XI 3.0 and P.I 7.0
    Difference/ changes from XI 3.0 to PI 7.0
    Regard's
    Chetan Ahuja

  • Message type " " is unknown. Transaction J1IF13

    Dear all,
    When i am executing transaction J1IF13 for Subcontracting i am getting this error "Message type " " is unknown."
    i want to cancel the transaction
    Regards
    Amey

    Closed

  • Inutilização de NFe: Log de erro Message type 8 is not defined

    Olá Pessoal,
    Estamos com um erro aqui muito semelhante ao descrito na Thread: [Skip número da NF não autorizada|;.
    Solicitamos a inutilização de uma nota writer de saída que foi barrada no Monitor GRC por erro de validação e por isso estava com status 8 na J1BNFE (ECC). A inutilização foi feita com sucesso, o status no GRC está correto, mas no ECC a autorização ainda não constava. Executamos o report XNFE/UPDATE_ERP_STATUS_DIAL e ao fazermos a msg de "erro ao atuzalizar ECC". No monitor da J1BNFE a nota agora aparece com o seguinte log de erro:
    Message type 8 is not defined
    Message no. J1B_NFE018
    Diagnosis
    The messaging system passed a value for the message type to the back-end system (field I_MSGTYP) that is not defined in the back-end system.
    System Response
    The back-end system cannot interpret and process the inbound message.
    Procedure
    Configure the messaging system in a way that it transfers only allowed message types to the back-end system via the inbound interfaces J_1B_NFE_XML_IN or J_1B_NFE_XML_IN_TAB.
    Achei a thread mencionada acima com o mesmo erro e verifiquei a aplicação das notas, já que o problema foi solucionado com a aplicação das mesmas. Eis os status:
    Nota 1298283 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
    Nota 1376324 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
    Nota 1413636 (ECC) - Completely Implemented na SNOTE;
    Nota 1376901 (GRC) - Não relevante pois estamos no GRC SP13.
    Aparenmente alguma coisa ainda está faltando.. mas nao sei o que é.
    Desde já agradeço,
    Daniela Machado

    Verifique esses passos da nota 1298283 (no ECC)::
    Change Domain J_1BNFE_MESSAGE_TYPE
    Use transaction SE11
    Select Domain and insert name J_1BNFE_MESSAGE_TYPE
    Push Change.
    Select Tab "Value Range".
    Insert
    Fix value Short text
    8 Authorization to Skip a NF-e with Validation Error
    9 Rejection to Skip a NF-e with Validation Error
    Maintain table J_1BNFE_MAP_TYPE
    Use transaction SE16 and display the table entries.
    Push CREATE (F5)
    Insert records
    MSGTYP DOCSTA SCSSAT
    8 Space A
    9 Space B
    At.,
    Bernardo Braga
    Edited by: Bernardo Braga on Jul 1, 2010 10:06 PM

  • Message type BOMMAT (change BOM)

    Hello Guru,
    I have some question and need help, when i try a standard transaction CS02, try to change a BOM material existing for example, the base quantity of the BOM was 650, i enter new data as 655, but suddenly retain the original Qty as 650 and save the changes as SAP will accept the changes i've done (BOM for material 2456 changed) but eventual i have not change any value to the original BOM. SO it mean this is standard SAP funtionality for CS02.
    But when we use an interface using message type BOMMAT a standard SAP message tpye, we have created an IDOC using this message type and same data as the original was maintain to it, to be more exact we plan to change a BOM thru this IDOC but all the data we have is the same value of the original BOM, so we expect no error could be encounter of this IDOC since in standard CS02, changing of BOM even same value was inidicated did not had error message encountered when saving.
    But thru our process, when we try to process the IDOC with message type BOMMAT in program RBDAPP01 (BD20) the idoc did not pass it when into status 51(Error when saving BOM. Please see the application log.) and when we check the BOM it has duplicate value upon executing the program we able to fix it when we delete the duplicate line segment in the IDOC and reprocess it once again.
    my question is why in standard message type BOMMAT had encountered error when processing when we try to make change of BOM even the same value is carried out by the IDOC, and why in standard CS02 saving a change of BOm with same value as it is SAP accept the process? Please help and clear the process.
    Any inputs R.Brahamankar and Vivek
    Thanks
    Edited by: Ryan on Feb 9, 2009 9:23 AM

    BOMMAT  and process code BOMM

  • How to connect our outbound function module to the message type

    how to connect our outbound function module to the message type any transcation code exits to assign the message type with the function module .
    Thank in advance .
    A. Thiru

    Hi Thiru,
    Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
    For E.g for PO's
    Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
    In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process  codes with respective Function modules.
    Regards,
    Anbalagan

  • Wrong message type while sending response from TP

    Hi,
    We are simulating a scenario in which the host is sending a Rosetta over RNIF request to TP. The request is getting completed and acknowledgement is reaching the host properly.
    Now we are trying to send back a response from TP for the above request. But the following error is being observed:-
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Action Name: null
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Enter
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames tpitValue >>
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Exit
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage All TPs list for broadcasting[]
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsgold.get_MSG_ID()>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID() >G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID()>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
    2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage msgIdFrmBkEnd>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: BTGS Type: null Value: null
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP NameBTGS
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP NameCOMSTOR
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: Pip3A4PurchaseOrderConfirmation
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: V02.03.00
    2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdG20090303035936810.34565d:11fc706dc89:-7fbc@706519011
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 1
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) Engine AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage using appMsgId as b2bMsgId
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is G20090303035936810.34565d:11fc706dc89:-7fbc@706519011
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
    initial : null
    from : TPName: COMSTOR Type: null Value: null
    to : TPName: BTGS Type: null Value: null
    final : null
    initiating : TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() COMSTOR is hosted party
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() End..
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
    initial : null
    from : TPName: COMSTOR Type: null Value: null
    to : TPName: BTGS Type: null Value: null
    final : null
    initiating : TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: Pip3A4PurchaseOrderConfirmation docTypeRevision: V02.03.00
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: PurchaseOrderConfirmationAction actionRevision: V02.03.00
    2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : PurchaseOrderConfirmationAction Activity Version: V02.03.00
    2009.03.03 at 11:31:21:962: Thread-24: B2B - (DEBUG) calling setMode() changing from -1 to 2
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setMode() changing from 2 to 2
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setValidationEnabled() changing from null to false
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:addCollaborationDetails() End..
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<PurchaseOrderConfirmationAction>
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:1
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: COMSTOR Type: null Value: null to TPName: COMSTOR Type: null Value: null
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
    From Party -> null-null-COMSTOR-Buyer To Party -> null-null-BTGS-Seller Collaboration -> 3A4
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) RepoDataAccessor:getAgreementName(partyNAMES) Begin..
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
    2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
    2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) Engine:notifyApp Enter
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011</correlationId>
    <b2bMessageId>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011</b2bMessageId>
    <errorCode>AIP-50501</errorCode>
    <errorText>Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (punin1879150941)
    Description: Unable to identify the trading partner agreement from the given input values. Also verify agreement effectiveToDate
    StackTrace:
    Error -:  AIP-50501:  Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
    2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) Engine:notifyApp Exit
    2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
    2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) DBContext commit: Enter
    2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) DBContext commit: Leave
    2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
    As it can be seen from the logs, the message type is being set to 1. However it should be 2 in case of response.
    The following header properties are being used in the AQ stub:-
    msgID = G20090303035936810.34565d:11fc706dc89:-7fbc@706519011
    from = COMSTOR
    to = BTGS
    doctypeName = Pip3A4PurchaseOrderConfirmation
    doctypeRevision = V02.03.00
    payload = Pip3A4_Response_POA10170020309.xml
    attachment =
    Can you please let us know the reason for the wrong message type being set?
    Regards,
    Ravi Shah

    Dheeraj,
    We have included msgType=2 as a part of the AQ header.
    The logs show that message type is getting set to 2 but still COMSTOR is Buyer and BTGS is Seller.
    Because of this, agreement look-up is getting failed.
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Action Name: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Enter
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Exit
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage All TPs list for broadcasting[]
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsgold.get_MSG_ID()>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID() >G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID()>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage msgIdFrmBkEnd>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: COMSTOR Type: null Value: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: BTGS Type: null Value: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP NameBTGS
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP NameCOMSTOR
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: Pip3A4PurchaseOrderConfirmation
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: V02.00
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdG20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 2
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Engine AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage using appMsgId as b2bMsgId
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
    initial : null
    from : TPName: COMSTOR Type: null Value: null
    to : TPName: BTGS Type: null Value: null
    final : null
    initiating : TPName: null Type: null Value: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: COMSTOR Type: null Value: null
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() COMSTOR is hosted party
    2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() End..
    2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: COMSTOR Type: null Value: null
    2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
    initial : null
    from : TPName: COMSTOR Type: null Value: null
    to : TPName: BTGS Type: null Value: null
    final : null
    initiating : TPName: null Type: null Value: null
    2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: Pip3A4PurchaseOrderConfirmation docTypeRevision: V02.00
    2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: PurchaseOrderConfirmationAction actionRevision: V02.00
    2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : PurchaseOrderConfirmationAction Activity Version: V02.00
    2009.03.04 at 11:53:01:856: Thread-13: B2B - (DEBUG) calling setMode() changing from -1 to 2
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setMode() changing from 2 to 2
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setValidationEnabled() changing from null to false
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:addCollaborationDetails() End..
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<PurchaseOrderConfirmationAction>
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:2
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: COMSTOR Type: null Value: null
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() cpaID=null
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
    From Party -> null-null-COMSTOR-Buyer To Party -> null-null-BTGS-Seller Collaboration -> 3A4
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) RepoDataAccessor:getAgreementName(partyNAMES) Begin..
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
    2009.03.04 at 11:53:01:888: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
    2009.03.04 at 11:53:01:888: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name BTGS
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name PurchaseOrderConfirmationAction BusinessAction_9516
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
    2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) Engine:notifyApp Enter
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011</correlationId>
    <b2bMessageId>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011</b2bMessageId>
    <errorCode>AIP-50501</errorCode>
    <errorText>Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (punin1879150986)
    Description: Unable to identify the trading partner agreement from the given input values. Also verify agreement effectiveToDate
    StackTrace:
    Error -:  AIP-50501:  Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
         at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
         at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
         at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
         at java.lang.Thread.run(Thread.java:534)
    ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) Engine:notifyApp Exit
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Enter
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Leave
    2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
    Can you please look into this?
    Regards,
    Ravi Shah

  • IDOC message type for "Site" in SAP Retail module?

    Hi All,
    We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction:  WB01, WB02).  Does anyone know if there's an IDOC message/type already associated with this?  Thanks in advance for your help!
    Cheers,
    Matt

    Hi,
    please read SAP notes 892103 and 551035.
    The correct IDOC type should be FIDCC1 / FIDCC2.
    Best regards,
    Andreas

Maybe you are looking for