Get trading partner profile identifiers
Hi,
Can you advise which function/expression in BPEL Process Manager that can be call to get the B2B trading partner profile identifiers? Because I have a use case where by I'm evaluating trading partner to perform specific logic.
For example, I want to get the value of the identifier type "Name", the expected value would be "Acme".
Regards,
Scott.
Hi Anuj,
Your example is correct if the message receive from B2B partner link.
However, my scenario is the reverse. I am receiving the message from a File Adapter partner link, then I need to fetch properties in trading partner profile for decision logic.
Essentially, I'm looking for APIs that are used in the Oracle B2B partners tab. I want to call these APIs from BPEL to get trading partner profile details.
Regards,
Scott.
Similar Messages
-
Importing Trading Partner Profiles
Greetings,
Is there an XSD that captures our notion of Trading Partner Profile? If so, is there a back door way of importing XMLs of that type into an Oracle Integration B2B (I suspect there's no way of doing that from the console)?
To elaborate, IHAC who is trying to migrate from an existing B2B deployment to Oracle Integration. In the process, we will need to recreate the tons of TP profiles they've already configured in Oracle B2B. The good news is that those existing TP profiles TPs can be exported into an XML format. If we support that format ourselves, that I was thinking of running their XMLs' through an XSLT to align it with our format, and then importing those XMLs automatically.
On a related note, I'd be interested to know if we understand ebXML CPPs and CPPAs, because in general, that would be a good way of importing TP profiles and agreements, regardless of their origin.
Regards,
KarthickHello Karthik,
We have the notion of Self Service API which can be used to create Trading partner and Agreement in Bulk. Please refer
http://rameshnittursblog.blogspot.com/2007/09/creating-b2b-metadata-using-self.html
Please send a test mail to [email protected] for self service API samples.
Rgds,Ramesh -
Getting EDI:Partner profile not available.
Hi,
I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
<u><b>My Scenario details</b>:</u>
1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
7. Activated all Standard Change list items.
The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
I have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
can somebody suggest me solution please.
Thanks,
Vijay.Hi,
<i>6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.</i>
>>>Check this for Reciever Business System.. not for Sender system..
BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check all the data from XI is populated in the idoc structure in SAP R/3 in we05...by clicking each segment.. if so, then there is no problem from XI..
check WE20 ..partner profile configuration in R/3 also check inbound parameters are given
Regards,
Moorthy -
Partner profile not available.
Dear Folks,
i am doing the scenario JDBC to IDOC. For that i did all the necessary ALE settings and configured the systems. While executing that scenario. In we02, i am getting the error partner profile not available eventhough i configured it. From the error i found that, in technical info, partner number and port are different. And i am getting some Default parnter number and port.
From my observations, i checked the Sender business system and i found that, logical system which was mentioned for this business system is replicating as a default parnter number in the technical info.
please guys i need your valuable suggestions to eradicate this error.
Regards,
DileepHi Mark,
I checked the payload and i am not using header mapping.
I tested the same by doing some modification like, In sender business system, i replaced the default logical system name with which i am using.Then idoc status is changed to status 50. But i am getting the Default port as previously said.
one more thing is , whenever i am getting this partner profile error, it is hitting one of my Company portals. i.e., displaying this partner profile issue in MSS(managerial self service) of HR Portal.
I was little bit confused of why it is hitting the portal?
what would be the key point for their connection?
Please help.
Regards,
Dileep -
Trading Partner in Gain and Loss from valuation
Dear Friends,
My issue is with the valuation posted for account maintained on line item basis only (Not open item managment). Since the account is maintained on line item basis, only balance is valuated each month thru f.05.
The problem is that when account posted with Loss or Gain each month on valuation, the document will not have a Trading partner assigned which causes my inter-company elimination issue.
How to get Trading partner assigned to document posted on valuation (F.05) I have tried sustitution rule and OB32 to make Trading Partner as editable but SAP does not allow both.
Best Regards
VKThanks Venkata,
My problem is with the autmated posting result from forex gain or loss when carrying F.05. These documents autmatically created but donot update the Trading Partner. I can not manually input them even if enter Trading Partner is option in OBA7 is checked.
Best Regards
VK -
Trading partner' field (ANLA-VBUND) on asset master data
Dear experts,
I have informed field Trading partner' (ANLA-VBUND) on asset master data but we have notice that, in our system, it has not got any function on an accounting level.
Trading partner is not informed in documents like:
CR - Loss
DB - Asset account (with trading partner informed on asset's master data)
We only get trading partner informed in postings like:
CR - Vendor with trading partner informed in vendor's master data.
DB - Asset account
By the way, although trading partner is informed on asset's master data, trading partner is not informed on depreciation postings.
At the end, I think that my expectations around the functionality derived on field Trading partner' (ANLA-VBUND) on asset master data are not correct. I could not found any SapNote or SapHelp regarding this question.
Does any body knows what is the functionality of field Trading partner' (ANLA-VBUND) on asset master data?
Thanks in advanceDear Brigitte,
Thanks for your answer. Looking to the documentation you mentioned above I've found the following:
AA/Asset Accounting
* Asset transfers between company codes: If a fixed asset is transferred to another company code, two posting documents are required - one for each company code. The trading partner of each document must be set with the company ID of the other company code, respectively.
In my understanding there is no functionality regarding trading partner on asset master data level apart of transfers between company codes. Am I right?
I understand that my initial approach was not correct.
Regards -
Migrating Trading Partner from test to Production environment
Hi,
My Production environment has configuration for two trading partner.
I need to migrate one more trading partner from test environment to (the existing) production environment.
I see Agreement level export, TP level export, Config level export options in Oracle B2B.
Can you please suggests as to which is the fastest and most accurate way to migrate new trading partner configuration?
Regards,
Ravi ShahThere is nothing as preferred option. However you can keep few things in mind.
1. Agreement Export - Preferred option , if you would like to export only specific Trading Partner and Agreement details.
2. Repository Export - For full repository export.
3. Trading Partner Export - This option do not keep any TP in mind while taking the export, hence you may not information about Delivery channel and Agreement. This provides information about Trading partner profiles and Supported Document defition of the trading partner.
Let me know. -
Identify Trading Partner EDI X12 over File Protocol
Hi
I am working on EDI X12 (835) over File Protocol.
The EDI payloads I will be getting will hold same EDI InterchangeIds, Group, or Exchange.
oracle.tip.adapter.b2b.edi.identifyFromTP = ANY
and I have given oracle.tip.adapter.b2b.allTPInOneDirectory = false.
So that it identifies based on the directory name.
For this I changed my trading partner name same as directory name.
Could you please suggest me is there any other way of identifying From Trading partner than changing the Trading partner name to directory name?
Thanks & Regards,
Praveena.Hi Praveena,
Yes, TP name and directory name should be same.
Put oracle.tip.adapter.b2b.allTPInOneDirectory = true (Idetifies the Trading partner by the directory name) in your tip.properties file.
Check below thread for more information on TP identification -
Re: Internal Delievery channel AIP-51505: General Validation Error
Regards,
Anuj
Edited by: Anuj Dwivedi on May 5, 2009 4:31 PM -
AIP-52251: Error identifying remote trading partner at MLLP Exchange with
used HL7 over MLLP, one trading partner is EAI(B2B Localhost), another is EchoServer(a java application, the hostname is is4-nb4.corp.ha.org.hk). used a script to enqueue message. like below:
DECLARE
enqueue_options dbms_aq.enqueue_options_t;
message_properties dbms_aq.message_properties_t;
msg_handle RAW(16);
ipmsg b2b.IP_MESSAGE_TYPE;
xml_clob clob;
msg_id number(10);
subscribers dbms_aq.aq$_recipient_list_t;
BEGIN
select message_seq.nextval into msg_id from dual;
xml_clob := '<?xml version="1.0" ?><ADT_A01 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.3.1" CreatedDate="2005-08-16T16:52:26" CreatedBy="ECXEngine_826" GUID="{1A2726C6-B00E-DA11-8F7A-080020C8D296}"><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>EDI</HD.1></MSH.3><MSH.4><HD.1>PWH</HD.1></MSH.4><MSH.5><HD.1>EchoPac</HD.1></MSH.5><MSH.6><HD.1>PWH</HD.1></MSH.6><MSH.7><TS.1>20050804162010</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>ADT</MSG.1><MSG.2>A01</MSG.2></MSH.9><MSH.10>TEST007</MSH.10><MSH.11><PT.1>#Property(ProcessingID)#</PT.1></MSH.11><MSH.12><VID.1>2.3.1</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13><MSH.14 xsi:nil="true"></MSH.14><MSH.15>AL</MSH.15><MSH.16>ER</MSH.16><MSH.17>#Property(CountryCode)#</MSH.17><MSH.18>ASCII</MSH.18><MSH.19><CE.1>ENG</CE.1></MSH.19></MSH><PID><PID.1>1</PID.1><PID.2 xsi:nil="true"></PID.2><PID.3><CX.1>A0000010</CX.1></PID.3><PID.4 xsi:nil="true"></PID.4><PID.5><XPN.1><FN.1>TEST, Patient 01_10</FN.1></XPN.1></PID.5><PID.6 xsi:nil="true"></PID.6><PID.7><TS.1>20001001</TS.1></PID.7><PID.8>F</PID.8></PID><PV1><PV1.1>1</PV1.1><PV1.2 xsi:nil="true"></PV1.2><PV1.3 xsi:nil="true"></PV1.3><PV1.4 xsi:nil="true"></PV1.4><PV1.5 xsi:nil="true"></PV1.5><PV1.6 xsi:nil="true"></PV1.6><PV1.7 xsi:nil="true"></PV1.7><PV1.8 xsi:nil="true"></PV1.8><PV1.9 xsi:nil="true"></PV1.9><PV1.10 xsi:nil="true"></PV1.10><PV1.11 xsi:nil="true"></PV1.11><PV1.12 xsi:nil="true"></PV1.12><PV1.13 xsi:nil="true"></PV1.13><PV1.14 xsi:nil="true"></PV1.14><PV1.15 xsi:nil="true"></PV1.15><PV1.16 xsi:nil="true"></PV1.16><PV1.17 xsi:nil="true"></PV1.17><PV1.18 xsi:nil="true"></PV1.18><PV1.19><CX.1>10010</CX.1></PV1.19></PV1></ADT_A01>
subscribers(1) := SYS.AQ$_AGENT('b2buser', null, null);
message_properties.RECIPIENT_LIST := subscribers;
ipmsg := b2b.IP_MESSAGE_TYPE (msg_id, null,'EAI','EchoServer','Echo_ADTA01_Process', 'ADT_A01', '2.3.1', 1, xml_clob, null);
dbms_aq.enqueue(queue_name => 'b2b.IP_OUT_QUEUE',
enqueue_options => enqueue_options,
message_properties => message_properties,
payload => ipmsg,
msgid => msg_handle);
commit;
END;
show errors;
then go to the B2B Report tab, can see two message like below
EAI EchoServer MLLP - 1.0 HL7 - 2.3.1 Echo_ADTA01_Process WaitFA 2007年11月12日 星期一 下午05:51:37
Acknowledgement Invalid 2007年11月12日 星期一 下午
and in the log file, like this:
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage Could not find a Trading Partner with MLLP ID = is4-nb4. Please check the Trading Partner Identification section of your Trading Partner
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:247)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage identify trading partner by MLLP Id failed for is4-nb4 with ExceptionError -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:257)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {From=is4-nb4, FromIP=160.19.23.102, FARequired=true, protocolVersion=1.0, ToIP=160.19.55.114, Port=4911, Message-Id=1194861102002-1207274363, protocol=TCP, To=is4wingw02}
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning true
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error Set
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA processed by HL7
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Not creating an ACK for an incoming ACK Message
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA B2BMessage is null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Exit
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA Sent
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 1194861102002-1207274363
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2007.11.12 at 17:51:43:096: Thread-10: 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>null</correlationId>
<b2bMessageId>A0133772116334587C90000068CD8000</b2bMessageId>
<errorCode>AIP-52251</errorCode>
<errorText>Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4</errorText>
<errorDescription>
<![CDATA[Machine Info: (is4wingw02)
Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Enter
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Transaction.commit()
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Leave
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
here said not find the remote partner, but in B2B server, can ping Echoserver.
what is wrong?Hello again,
I have tried all different combinations with the IP addresses and host names, but to no avail. Then I changed the Trading Partner Identification Type from MLLP Id to Sending Application (one of the customer requirements is to be able to identify the Trading Partner by the combination of Sending App/Sending Facility, since they are running multiple HL7 applications on one host). However, I still see the same error in the log file - for some reason, B2B is still trying to identify the Trading Partner by the MLLP Id. Redeploying the configuration didn't help, the requested identification type is ignored.
Please help! If needed, I can send the B2B log file, but maybe I'm missing something obvious.
BTW, the customer has installed the patch for bug 6439217 on October 10th. The B2B version is 10.1.2.2.0.
Thanks in advance! -
Agreement lookup failed as From trading partner cannot be identified
Hi,
I am working on custom document over HTTPS.
I configured B2B to send custom document over Generic Exchange(transport - HTTPS).
I enqueue the XML document with AQ header to IP_OUT_QUEUE. B2B is able to read the data from IP_OUT_QUEUE and invokes the client Webapplication.
I changed the IP_OUT_QUEUE to custom AQ. B2B is able to read data from custom AQ, but B2B throws "Trading partner agreement lookup failed as From trading partner cannot be identified"
b2b.log:
2010.02.15 at 13:03:44:470: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2010.02.15 at 13:03:44:471: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2010.02.15 at 13:03:44:497: Thread-22: B2B - (DEBUG)
Protocol = AQ
Version = null
Transport Header
aq.receiver.expiration:-1
aq.receiver.delay:0
aq.receiver.priority:1
aq.receiver.correlation:b2buser
2010.02.15 at 13:03:44:881: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
2010.02.15 at 13:03:44:907: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned on, will listen on IP_OUT_QUEUE for messages
2010.02.15 at 13:03:44:921: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
2010.02.15 at 13:03:45:069: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppInterfaceListener:onMessage calling processOutgoingMessage
2010.02.15 at 13:03:45:069: Thread-22: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
2010.02.15 at 13:03:45:070: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.15 at 13:03:45:070: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.15 at 13:03:45:071: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.15 at 13:03:45:076: Thread-22: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP Namenull
2010.02.15 at 13:03:45:078: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP Namenull
2010.02.15 at 13:03:45:078: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdnull
2010.02.15 at 13:03:45:094: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 1
2010.02.15 at 13:03:45:095: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:095: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is 0A4DBD67126D1BA2FC700000136A1AD0
2010.02.15 at 13:03:45:099: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
initial : null
from : TPName: null Type: null Value: null
to : TPName: null Type: null Value: null
final : null
initiating : TPName: null Type: null Value: null
2010.02.15 at 13:03:45:101: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
2010.02.15 at 13:03:45:102: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: null Type: null Value: null
2010.02.15 at 13:03:45:102: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
2010.02.15 at 13:03:45:112: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:112: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
initial : null
from : TPName: Acme Type: null Value: null
to : TPName: null Type: null Value: null
final : null
initiating : TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:113: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: null docTypeRevision: null
2010.02.15 at 13:03:45:118: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: null actionRevision: null
2010.02.15 at 13:03:45:119: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() Set actionRevision in MessageInfo: null
2010.02.15 at 13:03:45:119: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() Obtain DocType using actionName and actionRevision.
2010.02.15 at 13:03:45:124: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : null Activity Version: null
2010.02.15 at 13:03:45:125: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<null>
2010.02.15 at 13:03:45:125: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:1
2010.02.15 at 13:03:45:126: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: Acme Type: null Value: null to TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:127: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() cpaID=null
2010.02.15 at 13:03:45:127: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2010.02.15 at 13:03:45:128: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2010.02.15 at 13:03:45:128: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
2010.02.15 at 13:03:45:129: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
From Party -> null-null-Acme-null To Party -> null-null-null-null Business Action name -> null
2010.02.15 at 13:03:45:130: Thread-22: B2B - (ERROR) Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
2010.02.15 at 13:03:45:131: Thread-22: B2B - (ERROR) Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
2010.02.15 at 13:03:45:131: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
2010.02.15 at 13:03:45:132: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
2010.02.15 at 13:03:45:132: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.02.15 at 13:03:45:209: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2010.02.15 at 13:03:45:211: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2010.02.15 at 13:03:45:212: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2010.02.15 at 13:03:45:353: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2010.02.15 at 13:03:45:354: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2010.02.15 at 13:03:45:367: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2010.02.15 at 13:03:45:397: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2010.02.15 at 13:03:45:398: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2010.02.15 at 13:03:45:471: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2010.02.15 at 13:03:45:472: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2010.02.15 at 13:03:45:472: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2010.02.15 at 13:03:45:476: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2010.02.15 at 13:03:45:477: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
2010.02.15 at 13:03:45:477: Thread-22: B2B - (DEBUG) Engine:notifyApp Enter
2010.02.15 at 13:03:45:485: Thread-22: 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>null</correlationId>
<b2bMessageId>0A4DBD67126D1BA2FC700000136A1AD0</b2bMessageId>
<errorCode>AIP-50548</errorCode>
<errorText>Trading partner agreement lookup failed as From trading partner cannot be identified</errorText>
<errorDescription>
<![CDATA[Machine Info: (dgda21a)
Description: Make sure the trading partner has name, type, and value information
StackTrace:
Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2010.02.15 at 13:03:45:512: Thread-22: B2B - (DEBUG) Engine:notifyApp Exit
2010.02.15 at 13:03:45:513: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
2010.02.15 at 13:03:45:513: Thread-22: B2B - (DEBUG) DBContext commit: Enter
2010.02.15 at 13:03:45:516: Thread-22: B2B - (DEBUG) DBContext commit: Transaction.commit()
2010.02.15 at 13:03:45:516: Thread-22: B2B - (DEBUG) DBContext commit: Leave
Kindly help me to resolve this issue.hi Anuj,
I am enqueuing from BPEL process. I have set the AQ header.
<b2bMsgHeader><Header xmlns="http://xmlns.oracle.com/pcbpel/adapter/aq/publishB2BMessage/">
<QueueHeader/>
<PayloadHeader>
<MSG_ID xmlns="">2SY16SY_TEST_FEB15_07E01null2010021513270041</MSG_ID>
<INREPLYTO_MSG_ID xmlns=""/>
<FROM_PARTY xmlns="">Acme</FROM_PARTY>
<TO_PARTY xmlns="">GlobalChips</TO_PARTY>
<ACTION_NAME xmlns="">ProcessBusiness</ACTION_NAME>
<DOCTYPE_NAME xmlns="">DocType</DOCTYPE_NAME>
<DOCTYPE_REVISION xmlns="">1.0</DOCTYPE_REVISION>
<MSG_TYPE xmlns="">1</MSG_TYPE>
<PAYLOAD xmlns="">XML payload</PAYLOAD>
<ATTACHMENT xmlns=""/>
</PayloadHeader>
</Header>
</b2bMsgHeader> -
EDI 810 transaction error: Cannot uniquely identify a trading partner
Hi,
I am facing following error on B2B 11g version 11.1.1.6.0. Please provide the solution if you are aware of the issue.
Error Description: Cannot uniquely identify a trading partner. The trading partners PARTNER-A, PARTNER-B have the same set of identifications.
Partner Identification parameter for PARTNER-A and PARTNER-B
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-A
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-B
Thank you
RamTwo TPs can not have same identification.
There are two ways to come out of this problem.
1. Change the identification criteria for the TP.
2. Use exchange level Identification for one TP. -
Trading Partner Summary Report not getting genrated in PDF
Hi all
We are running EBS r12 on solaris 5.10 machine.
Problem is there is a report called "Trading Partner Summary Report"
it is getting completed successfully but when i try to c the output it says
File does not begin with '%PDF-',
Please help
Regards
MusaddaqHi,
Please also see:
Note: 955203.1 - SEPA Payment Format Ends With FILE DOES NOT BEGIN WITH '%PDF-%'
Note: 905198.1 - Printing Error: File Does Not Begin with '%PDF-'
Regards,
Hussein -
IDOC is Getting Fail with - 56 Status EDI Partner profile not available
Hi,
I am trying to Post invoice Data into IDOC on ECC Side.
My Scenario is File u2013 XI u2013 ECC(IDOC).
But It is Getting Fail with 56 Status u201C EDI: Partner profile not available u201C
On Control record I am getting this
Port BLANKKKKKKKKKK
Partner Number CLNTDEC110 Logical system for Client
Partn.Type LS Logical system
Function BLANKKKKKKKKKK
Port SAPDPI
Partner number CLNTSAMPLE
Partn.Type LS Logical system
Partner Role BLANKKKKKKKKKK
My configurations are Like this :----
On ECC Side MY SID is DEC
On ECC side I have two logical system in CLNTDPI100 for PI
CLNTDEC110 for ECC.
I have Partner profile on ECC system on CLNTDPI100 logical system - we20
Added message type in inbound side of partner Profile (INVOIC-INVOIC02)
ON SAP PI/ XI System MY SID is DPI
IDX 1 has Port name SAPDEC
On Message mapping EDI_DC40 is mapping with constants with below given value
<INVOIC02>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<TABNAM> </TABNAM>
<DIRECT>2</DIRECT>
<IDOCTYP> </IDOCTYP>
<MESTYP>INVOIC</MESTYP>
<SNDPOR>SAPDPI</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>CLNTDPI100</SNDPRN>
<RCVPOR>SAPDEC</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>CLNTDEC110</RCVPRN>
</EDI_DC40>
Regards
PSCheck the following :
in We 02 which partner number is displayed just in the posted IDOC -> 2nd coloum in the IDOC list .and verify if the
same you have in Partner profile. Actually this details comes from ECC business system's logical system name which you give in SLD.
in we 19 - take the error iDOC numner and open the IDOC ->click on the first line -> check entries as you mentioned
above sender port should be PI port not empty.you need to check the partner profiles properly
follow these steps
1. create a RFC destination of tyoe H for Pi system- 2. create a Port and assigen the RFC destination to it
3 create logical system for PI BD54 PICLNT001 say , 4 with the same name create a partner profile in We20
in parter profile maintain the inbbound message parameters and add the PI port as receiver port in it .Give the basic type also .
now
for sender details in ur case PI : u have port (defined in PI IDX1),patner number (LS defined in ECC PICLNT001), parter type LS.
for receiver you have port defined (as above), partner number the logical system for ECC system.
in we 19 ,, edit the control record as above and go to the tab inbound processing and test the internal posting
it should work fine. in the adapte specific attribuet for receiver ECC system , maitain the same LS name , if any wrong entry is
there then change the LS in sld to poing to correct LS/
refer this
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/technology/sap/26/
Regards,
Srinivas -
No details getting populated in Log for Partner Profile Generation...
Hi,
When I create a distribution model in BD64 and then go to environment -> Generate Partner profiles, enter all the required parameters like model view, type, id, version, packet size and all necessary stuff, but when I execute I get a message in log for partner profile generaation saying, "No messages have been defined for the selection conditions in the model".
Can someone tell me as how can I eliminate this error ?
Thanks.
Regards,
Tushar.Hi,
When you create a model view, first you have to save the entries and then generate partner profiles.
This should help
Vamsi -
Business Area is value getting copied to Trading Partner Business Area
Respected Members,
In the Purchase Order i have maintain the business area and through this Purchase order i am making the good receipt and business area is visible at MIGO item level screen also.
BUt when accounting document is generated the business area value is not visible in the business are.
After keen observation i found that value of Business area is getting copied to Trading Partner Business Area and Business area value is getting clear off.
Why Sap Guys have hardcorded like that they clearing the business area value and putting in the trading partner businessa area. In coding they have not maintain any condition also.
Please anybody can clear my doubt at what scenario the business area value will be visible in the business area field and when it will get clear and transfer to trading partner business area.
Thanks a lot.
ManishHi,
1. In case of Business where payments are made centrally it is important to report
Bank A/c Business area wise.
2. However I have solved the problem by doing "Sustitution", and its working fine. The Business Area is getting updated against the Main Bank Account Line item.
3. I am however getting one error while doing the upload in FF_5. The error occurs
only if Business Area is a "required" field in Bank Account's "Field Status
Group".
Error: (00 298) Formatting error in the field COBL-GSBER ; see next message.
But if I make Business Area as an Optional Field I am not getting an error and
also the posting is done to Main Bank Account.
Is there anyother method by which this error can be corrected.
I have assigned 2 points for your inputs. Can you help me to solve this error as well.
Rgds
Prasad
Maybe you are looking for
-
Print issue: "Print on both sides..." checkbox not present in V10.1.2 under Win XP SP3
Since upgrading to Adobe Reader 10.1.2 (wish I never had), my "Print on both sides" option is evidently ON (by default), but I cannot turn it off because the check box to do so is not present in the Print dialog: The checkbox should be underneath the
-
I just want to create a discoverer workbook that allows the user to link to a Word document. How can I accomplish this?
-
How to create a folder in cocoa?
I Want to create a folder un the documents folder with objectif c. I want that the folder is called "App".
-
I believe I have a security issue with Firefox blocking a page that I need access to.
On my laptop ONLY, I can't get access to the page on my bank's website to pay bills. It will let me log in and view the page that shows the amount in my accounts. In order to get full access, I am required to type in the answer to my "Login Security"
-
TS4006 how can i find my ipod even though it's locked
Please i lost my ipod and it's i want to find can somebody please tell me how to find cause i have a lot of imortant things on it that i need and i need help quick tank you.