Message types?

hi am new to BI
pls help me to know about message types.
plese provide docs or pdfs if u have and that would be really helpful
thank u

Hi Ranjith,
Message Types:
A --> Termination Message
The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
E --> Error Message
Depending on the program context, an error dialog appears or the program terminates.
I --> Information
The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
S --> Status Message and Sucess message
The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
W --> Warning
Depending on the program context, an error dialog appears or the program terminates.
X --> Exit
No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
For more info:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Regards,
KK.

Similar Messages

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

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

Idoc message type for open orders & Open JIT lines

Hi,
I need to send Open Purchase Order data and Open JIT lines data to supplier daily via Idocs.
Is there any standard messege type available for this data.
Regards

Hi Rohita,
Instead of changing the standard domain, You have to make the changes in the User Exit.
Say Qualifier 001,002,003 were already there in the domain.
001--Purchase Date
002--Delivery Date
003--Ordered Date
In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
These Qualifiers are just like other variables and u can add whatever values to them that u want..
You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
If u analyse the FM closely u will realise that they have done coding for those values in the domain.
So instead of adding it to domain u just have to do the coding for this new qualifier.
Revert back if u need any help on it.
Thanks...
Message was edited by:
Utsah Garg

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

IDOC Message type for open sales orders

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any message type available for this in SAP R/3 4.7 version
Regards
Anandh

Try VA05 schedule lines standar variant...include status fields and both ordered qty and confirmed qty. In SAP standard system order status, status A means open orders fully (Nothing shipped, everything opened). Status B means in process orders (Partially processed - shipped). Status C means complete orders (Nothing opened). As there is no delivered qty in VA05, you need to download to excel the file and calculate the difference between both qty fields for each A and B status. That is a way to get the missing qty to be delivered or open qty as you stated.
Hope it helps.
Jorge Fernandez

Change sales orders using ORDCHG Message type

Hi,
I am trying to test the changing of quantity on sales order items using message type ORDCHG and process code ORDC. In segment E1EDP01 the action code is set to 002 - item changes. However when the IDoc is posted a new line is created in the order rather than the existing one being changed. The action code in the header is set to 003 - one or more items changed. Does anybody know how to control the change of quantity for an existing item?
Many Thanks
Caroline

Hi,
Try to populate Logical message code 'CHG' in the EDIDC-MESCOD while you are creating the IDoc.
If a message code has been entered in the (inbound) partner profiles, the external system must fill the field during IDoc inbound processing.
Regards,
Yogesh

Idoc Message type for Scheduling agreement

Dear Experts,
How to configure to create Idoc for Scheduling agreement (not the releaseed schedule lines) ?
I am trying to use message type ORDERS05 but it is not working.
Will any body guide me preferably step by step process for this ?
Thanks in Advance,
Best Regards,
Raju

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

How can we change the message type?

Hello all
We use SRM server 5.5 with classic scenario.
When we create shopping cart, we implemented the Change Badi to assign the purchasing group from R/3 material master.
We implemented the following logic.
If material master in R/3 has no purch. Group, SRM also has no purch. Group. So SRM display the error message You should select the purch. group to determine the purchasing group in basic view.
But, We have the standard error message, when we choose the material code this material code has no purch. Group in R/3 No purchasing groups were found.
Message number is BBP_ATTR050.
Because of this message, we can not progress the process to create shopping cart.
Can we change the message type from Error to Warning Message?
Or, Can we delete this message?
Thank you,
Best regards,
SH

Yes. You are right.
When user choose the material code, there is no purch. group in 1st Step, but
we want to choose the purch. group in 2nd Step on basic view.
But we have the error message at 1st step. so we can not progress to 2nd Step.
If we use dummy purch. group, user could make the human mistake.
So our customer want to remove purch. group and choose the purchasing group by user.
But i'm not sure if we remove this error message, we got solve this problem..
Pls give me an idea..
Message was edited by:
So Hee Lee

How can I put a filter to message type COND_A

I am creating message types: COND_A from Change Pointer.
I have an active filter on element: Condition type. (BD64). This is working OK.
I also want to set the filter on element: Material type.
This is not working, probably because this element is not an active field in any delivered IDoc Segments. (Ref. WE05). The result is that no messages (IDoc's) are delivered.
How can I get this filter to work for COND_A?
In other words: How can I select on Material type = 'XXXX' creating message type COND_A from Change Pointer?

No, however, you can have Favorites and Recents show on the App Switcher (Multitasking) screen, assuming you are running iOS 8: Settings App > Mail,Contacts,Calendars > Show in App Switcher [under CONTACTS]

Message type MBGMCR: posting of GR for a text po

Hi
Goods issues are posted by using this message type MBGMCR in R/3 system. Idocs are coming from SRM system.
We are getting an error message for an idoc of this message type MBGMCR : "No stock posting possible for this material, The material belongs to a material type whose stocks are not managed on a quantity basis".
I checked the data segment & found that this is a text PO (PO without material reference).
My question is that can we post GR of a text PO by using this message type MBGMCR.
Regards
sapmm

have you tried posting it manually with MIGO, just for testing purposes?
MIGO or MB11 usually allow to post a goods receipt even for text items, with some preconditions, like GR indicator is active.
Usually, when the receipt is based on the PO, such message should not come, because a text PO has an account assignment K, which means the costs are posted to cost center and no stock is created.
And IDocs for movements do in general the same as a manual posting, using the same program routines for posting.
This M7097 is usually coming if you have no account assignment in the PO, which means you want post to stock, but stock management is not active for the material type.

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

How to change P.O. duplication message type from warning to error for Order

Hi Experts,
I have a requirment to change P.O. duplication message type from warning to error for Order only not OrderTemplate. I can easily change message type in BAdI ISA_BASKET_MSGS, but I can't find the parameter to know if it's Order or OrderTemplate (DocType). If this BAdI is not good way, is there other way? and how to please?
Please advise / help..
Thanks, Jin

Thanks Easwer for your help.
The info for getting status from function is very clear and I followed you instruction and completed the coding in BAdI and tested it successfully .... Thank you very much. I need to learn where I can see the system status of the template, i.e. I1034 (Order Template) or Order or Quotation .....? if I need to filter out Quotation, I can easily do it in the BAdI. Could you please provide me more details?
Thanks again, Jin
Thanks again, Jin

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

Message types?

Similar Messages

Maybe you are looking for