Import certificate from trading partner

Hi
I got a certificate from my trading partner. (Communication is AS2)
Now I have to import it to my B2B and use it while communicating with him
Can someone tell me how to import this so that I can select the certificate in the Security tab?
Thanks
Vijay Sai.S

Hi,
In Case of 10g using oracle wallet manager import trusted trading partner certificate.
In case of AS11G use the below command to import the trading partner certificate into jks,
keytool -importcert -file -keypass
Please also look into the below link for more details,
http://blogs.oracle.com/oracleb2bgurus/2009/08/certificate_management_in_11g.html
Regards
Nandagopal

Similar Messages

  • 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>

  • Trading partner agreement lookup failed as From trading partner cannot be i

    Hi,
    I am sending 850 EDI XML to our Penske trading partner, Its throwing below error. Could anyone helpme how to resolve this issue. Please do the needful.
    our sender id is EMR and receiver id is Penske( I am also attaching a file which i am processing)
    Machine Info: (essapt020-u009.emrsn.com)
    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:199)
         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:1061)
         at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
         at oracle.tip.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:903)
         at oracle.tip.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:317)
    File which i processed
    <?xml version="1.0" ?>
    - <Transaction-850 xmlns="urn:oracle:integration:b2b:BD5A9C92A91F474292233E610E5258F9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="X12" Version="V4010" CreatedDate="2009-09-14T06:20:48" CreatedBy="ECXEngine_837" GUID="{3A6795B0-F6A0-DE11-B354-00144F86C7D4}">
    - <Internal-Properties>
    - <Data-Structure Name="Interchange">
    <Lookup Name="InterchangeSenderQual">ZZ</Lookup>
    <Lookup Name="InterchangeSenderID">EMR</Lookup>
    <Lookup Name="InterchangeReceiverQual">ZZ</Lookup>
    <Lookup Name="InterchangeReceiverID">Penske</Lookup>
    <Lookup Name="InterchangeControlVersion">00401</Lookup>
    <Lookup Name="Standard">X12</Lookup>
    <Property Name="InterchangeAuthorizationInfoQual">00</Property>
    <Property Name="InterchangeAuthorizationInfo" />
    <Property Name="InterchangeSecurityInfoQual">00</Property>
    <Property Name="InterchangeSecurityInfo" />
    <Property Name="InterchangeSenderQual">ZZ</Property>
    <Property Name="InterchangeSenderID">EMR</Property>
    <Property Name="InterchangeReceiverQual">ZZ</Property>
    <Property Name="InterchangeReceiverID">Penske</Property>
    <Property Name="InterchangeDate">090909</Property>
    <Property Name="InterchangeTime">1419</Property>
    <Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property>
    <Property Name="InterchangeControlVersion">00401</Property>
    <Property Name="InterchangeControlNumber">000085390</Property>
    <Property Name="InterchangeAckRequested">0</Property>
    <Property Name="InterchangeUsageIndicator">P</Property>
    <Property Name="InterchangeComponentElementSep">0x3e</Property>
    <Property Name="DecimalSeparator" />
    <Property Name="ElementDelimiter">0x2a</Property>
    <Property Name="ReleaseCharacter" />
    <Property Name="RepeatingSeparator" />
    <Property Name="SegmentDelimiter">0x7e</Property>
    <Property Name="SubelementDelimiter">0x3e</Property>
    <Property Name="InterchangeChildCount">1</Property>
    <Property Name="InterchangeTrailerControlNumber">000085390</Property>
    - <Data-Structure Name="Group">
    <Lookup Name="GroupSenderID">EMR</Lookup>
    <Lookup Name="GroupReceiverID">Penske</Lookup>
    <Lookup Name="GroupVersionNumber">004010</Lookup>
    <Property Name="GroupID">PO</Property>
    <Property Name="GroupSenderID">EMR</Property>
    <Property Name="GroupReceiverID">Penske</Property>
    <Property Name="GroupDate">20090909</Property>
    <Property Name="GroupTime">1419</Property>
    <Property Name="GroupControlNumber">85364</Property>
    <Property Name="GroupAgencyCode">X</Property>
    <Property Name="GroupVersionNumber">004010</Property>
    <Property Name="GroupChildCount">1</Property>
    <Property Name="GroupTrailerControlNumber">85364</Property>
    - <Data-Structure Name="Transaction">
    <Lookup Name="TransactionID">850</Lookup>
    <Property Name="TransactionID">850</Property>
    <Property Name="TransactionControlNumber">0001</Property>
    <Property Name="TransactionImplementationReference" />
    <Property Name="TransactionChildCount">24</Property>
    <Property Name="TransactionTrailerControlNumber">0001</Property>
    </Data-Structure>
    </Data-Structure>
    </Data-Structure>
    </Internal-Properties>
    - <Segment-ST>
    <Element-143>850</Element-143>
    <Element-329>0001</Element-329>
    </Segment-ST>
    - <Segment-BEG>
    <Element-353>00</Element-353>
    <Element-92>SA</Element-92>
    <Element-324>16010055985</Element-324>
    <Element-328 xsi:nil="true" />
    <Element-373>20090909</Element-373>
    <Element-367 xsi:nil="true" />
    <Element-587>AC</Element-587>
    <Element-1019 xsi:nil="true" />
    <Element-1166 xsi:nil="true" />
    <Element-1232 xsi:nil="true" />
    <Element-786>03</Element-786>
    </Segment-BEG>
    - <Segment-CUR>
    <Element-98>2L</Element-98>
    <Element-100>USD</Element-100>
    </Segment-CUR>
    - <Segment-REF>
    <Element-128>06</Element-128>
    <Element-127 xsi:nil="true" />
    <Element-352>ALICE.EMRSN.COM:oracle.apps.po.event.xmlpo:458153-325924</Element-352>
    </Segment-REF>
    - <Segment-FOB>
    <Element-146>CC</Element-146>
    <Element-309>ZZ</Element-309>
    <Element-352>UCC FOB DEST COL</Element-352>
    <Element-334 xsi:nil="true" />
    <Element-335 xsi:nil="true" />
    <Element-309_1>ZZ</Element-309_1>
    <Element-352_1>FOB Shipping Point</Element-352_1>
    </Segment-FOB>
    - <Segment-ITD>
    <Element-336 xsi:nil="true" />
    <Element-333 xsi:nil="true" />
    <Element-338 xsi:nil="true" />
    <Element-370 xsi:nil="true" />
    <Element-351 xsi:nil="true" />
    <Element-446 xsi:nil="true" />
    <Element-386 xsi:nil="true" />
    <Element-362 xsi:nil="true" />
    <Element-388 xsi:nil="true" />
    <Element-389 xsi:nil="true" />
    <Element-342 xsi:nil="true" />
    <Element-352>NET75 EOM</Element-352>
    </Segment-ITD>
    - <Loop-N1>
    - <Segment-N1>
    <Element-98>VN</Element-98>
    <Element-93>XPEDX</Element-93>
    <Element-66>US</Element-66>
    <Element-67>160000511</Element-67>
    </Segment-N1>
    - <Segment-N3>
    <Element-166>2099 CORPORATE 44 DRIVE</Element-166>
    </Segment-N3>
    - <Segment-N4>
    <Element-19>FENTON</Element-19>
    <Element-156>MO</Element-156>
    <Element-116>63026</Element-116>
    <Element-26>US</Element-26>
    </Segment-N4>
    </Loop-N1>
    - <Loop-N1>
    - <Segment-N1>
    <Element-98>BT</Element-98>
    <Element-93>EMC OU CIM</Element-93>
    </Segment-N1>
    - <Segment-N3>
    <Element-166>Emerson Motor Company,</Element-166>
    <Element-166_1>a Division of Emerson Electric Co. PO BOX 4147</Element-166_1>
    </Segment-N3>
    - <Segment-N4>
    <Element-19>Saint Louis</Element-19>
    <Element-156>MO</Element-156>
    <Element-116>63136</Element-116>
    <Element-26>US</Element-26>
    </Segment-N4>
    </Loop-N1>
    - <Loop-N1>
    - <Segment-N1>
    <Element-98>SO</Element-98>
    <Element-93>EMC OU CIM</Element-93>
    </Segment-N1>
    - <Segment-N3>
    <Element-166>8100 West Florissant Ave</Element-166>
    <Element-166_1>PO Box 3946</Element-166_1>
    </Segment-N3>
    - <Segment-N4>
    <Element-19>Saint Louis</Element-19>
    <Element-156>MO</Element-156>
    <Element-116>63136</Element-116>
    <Element-26>US</Element-26>
    </Segment-N4>
    </Loop-N1>
    - <Loop-N1>
    - <Segment-N1>
    <Element-98>CA</Element-98>
    <Element-93>SEE EMERSON ROUTING</Element-93>
    </Segment-N1>
    </Loop-N1>
    - <Loop-PO1>
    - <Segment-PO1>
    <Element-350>1</Element-350>
    <Element-330>4800</Element-330>
    <Element-355_1>EA</Element-355_1>
    <Element-212>116</Element-212>
    <Element-639 xsi:nil="true" />
    <Element-235_1 xsi:nil="true" />
    <Element-234_1 xsi:nil="true" />
    <Element-235_2>SW</Element-235_2>
    <Element-234_2>P062155530000</Element-234_2>
    </Segment-PO1>
    - <Loop-PID>
    - <Segment-PID>
    <Element-349>F</Element-349>
    <Element-750 xsi:nil="true" />
    <Element-559 xsi:nil="true" />
    <Element-751 xsi:nil="true" />
    <Element-352>PAD (BOX)</Element-352>
    </Segment-PID>
    </Loop-PID>
    - <Loop-N1_2>
    - <Segment-N1>
    <Element-98>ST</Element-98>
    <Element-93>CIM IO Plant CMD</Element-93>
    <Element-66>FA</Element-66>
    <Element-67>INTERNALC01</Element-67>
    </Segment-N1>
    - <Segment-N3>
    <Element-166>Boul Carlos Salinas de Gortari</Element-166>
    <Element-166_1>Kilometro 9.7</Element-166_1>
    </Segment-N3>
    - <Segment-N4>
    <Element-19>Apodaca</Element-19>
    <Element-156>NL</Element-156>
    <Element-116>66600</Element-116>
    <Element-26>MX</Element-26>
    </Segment-N4>
    - <Segment-SCH>
    <Element-380_2>4800</Element-380_2>
    <Element-355>EA</Element-355>
    <Element-98_1 xsi:nil="true" />
    <Element-93 xsi:nil="true" />
    <Element-374_5>112</Element-374_5>
    <Element-373>20090910</Element-373>
    <Element-337 xsi:nil="true" />
    <Element-374 xsi:nil="true" />
    <Element-373_1 xsi:nil="true" />
    <Element-337_1 xsi:nil="true" />
    <Element-326 xsi:nil="true" />
    <Element-350>1</Element-350>
    </Segment-SCH>
    </Loop-N1_2>
    </Loop-PO1>
    - <Loop-CTT>
    - <Segment-CTT>
    <Element-354>1</Element-354>
    </Segment-CTT>
    </Loop-CTT>
    - <Segment-SE>
    <Element-96>24</Element-96>
    <Element-329>0001</Element-329>
    </Segment-SE>
    </Transaction-850>

    Hi Srinivas,
    I am in dilemaaa whether i need to take a EDI x12 over internet and EDI x12 over genric exchange.I think this is something which you should discuss with your TP and as per the availability and requirement a decision should be made.
    If you are using FTP protocol in internal delivery channel, then you need to follow the file naming convention to provide B2B required information to identify the TP and transaction. For this please refer -
    http://www.b2bgurus.com/search/label/Generic%20File
    To know more about TP identification in EDI, please refer -
    http://www.b2bgurus.com/2007/08/trading-partner-identification-in-edi.html
    Regards,
    Anuj

  • Trading partner agreement lookup failed as From trading partner cannotbeide

    Machine Info: (essapt020-u009.emrsn.com)
    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:199)
         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:1061)
         at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
         at oracle.tip.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:903)
         at oracle.tip.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:317)
    I am getting an above error, while procssing data to our trading partner
    regards
    srinivas

    Hi Srinivas,
    I think you have one more thread opened for the same -
    Trading partner agreement lookup failed as From trading partner cannot be i
    Anyways, as I mentioned earlier in above thread, please follow proper file naming convention to allow B2B to identify the Trading Partner.
    Regards,
    Anuj

  • 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

  • Importing photos from 2 different cameras

    I have been importing photos from my partner's and my own Sony Cybershot cameras for months now but only discovered by browsing iPhoto Library that I has created doubles from day one.
    I have 2 DSC0250.JPG and 2 DSC0250.jpg for example.
    I am a bit worried that one set will be crushed. Am I going to lose all those photos? Can I rename one set? How can I register an other camera on iPhoto to stop it from creating doubles all the time?
    Many thanks in advance for your help
    Steph

    Where are you seeing these "doubles" - in the iPhoto window or using the finder?
    you can not change the file names - never make any changes of any sort to the content or structure of the iPhoto library - it will corrupt it and you will lose data
    iPhoto is fine with duplicate file names - it knows that cameras do that
    you can set both cameras to different starting points so they are not the same until later
    LN

  • While defining the Inter company rules unable to select Trading partner lov

    n case implementing new company
    While defining the Inter company rules user unable to select Trading partner Legal entities from Trading partner LOV
    Note:1
    I have checked the DOC ID 1113834.1, bur also there are no any Inter company Exception defined the Inter company Exception does not have any Exceptions
    Please advice

    in search lov write the first words+% and enter

  • Smartcard - importing certificates

    I have BlackBerry 8900 and Smartcard reader v1 and I am trying to get it working together.
    I am able to pair the devices together, BlackBerry sees the SmartCard reader. I can import certificates from it, but after that I cannot see any new certificates on my certificate list. The card is ok, the certificate is there  - I have checked it on my PC
    What am I doing wrong? Are there any additional steps required to get the certificates from my card? One more think I am wondering about is that I am also never asked about the smartcard PIN.
    Solved!
    Go to Solution.

    Ok, I solved it myself.
    Apparently BlackBerry requires that every certificate contains user email. I tried with a different card that has a certificate with email information and it worked. It's a pity though that I didn't receive any warning/information that a certificate is wrong and buggy "Certificates imported" message misleading me that everything went just fine.

  • Trading Partner Import

    Does anybody has dealt with Trading Partner conversion from Legacy systems?
    I want to know what are the Pros and cons of the process.

    Hi,
    In Case of 10g using oracle wallet manager import trusted trading partner certificate.
    In case of AS11G use the below command to import the trading partner certificate into jks,
    keytool -importcert -file -keypass
    Please also look into the below link for more details,
    http://blogs.oracle.com/oracleb2bgurus/2009/08/certificate_management_in_11g.html
    Regards
    Nandagopal

  • B2B SelfService Error creating Trading Partner .zip import file using ant

    SOA 11g 11.1.1.5 B2B - We are trying to create an import file for out trading partners into SOA B2B 11g but are getting errors when we run the ant script to build the import zip file.
    We ran the ant-b2b-util to get the b2bselfservice.xsd file, loaded that into jDev to show the selfservice.xml structure.
    We have built a trading partner xml file and at this point have stripped it down to one TP just to see if we could get it to work and we keep getting the same error messages.
    From the $SOA_ORACLE_HOME/bin directory (where we have placed our TP xml file: TPD_NA.xml) here is the command and results from running the ant script:
    [oracle@nalinoap05 bin]$ ant -f ant-b2b-util.xml b2bselfservice -Dinput=$ORACLE_HOME/bin/TPD_NA.xml -Doutput=$ORACLE_HOME/bin/TP_Docs.zip
    Buildfile: ant-b2b-util.xml
    b2bselfservice:
    weblogic_dependencies:
    [echo]
    [echo] Weblogic server location: /oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/wlserver_10.3
    [echo] JNDI properties folder location: /oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin
    [echo]
    verifyargs:
    utility:
    [echo]
    [echo] java.naming.provider.url=${java.naming.provider.url}
    [echo] java.naming.factory.initial=${java.naming.factory.initial}
    [echo] java.naming.security.principal=${java.naming.security.principal}
    [echo] java.naming.security.credentials=*****
    [echo]
    [echo]
    [echo] args=selfservice
    [echo]
    [java] Commandline arguments 1: [selfservice]
    [java] 2012.04.10 at 13:27:35:559: main: (INFO) Input file location(s) :[oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin/TPD_NA.xml]
    [java] 2012.04.10 at 13:27:35:559: main: (INFO) Output file location :/oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin/TP_Docs.zip
    [java] 2012.04.10 at 13:27:35:596: main: (INFO) TradingPartner created :/soa/b2b/tp_id1AC191488133.xml
    [java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010VICS docType=852 docDef=852Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010 docType=997 docDef=997Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=850 docDef=850Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=860 docDef=860Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010VICS docType=864 docDef=864Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=864 docDef=864Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=997 docDef=997Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:602: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=856 docDef=856Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:602: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=810 docDef=810Def not found in doc_*.xml file
    [java] 2012.04.10 at 13:27:35:691: main: (SEVERE) TPD_NA.xml: Error in Validation:
    [java] [org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
                   org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef']
    [java] Java Result: 255
    BUILD SUCCESSFUL
    Total time: 1 second
    Here is the contents of TPD_NA.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <SelfService xmlns="http://xmlns.oracle.com/integration/b2b/selfservice/profile">
    <TradingPartners>
    <TradingPartner hosted="false" name="OvvvvvvvX" >
    <Identification name="EDI Interchange ID" value="18xxxxxxxxxX" />
    <Identification name="EDI Interchange ID Qualifier" value="14" />
    <Identification name="DUNS" value="18xxxxxxxxxX" />
    <Identification name="Generic Identifier" value="18xxxxxxxxxX" />
    <Identification name="AS2 Identifier" value="18xxxxxxxxxX" />
    <SupportedDocumentDefinition initiator="true" docTypeName="852" docProtocolVersion="4010VICS" docProtocolName="EDI_X12" docDefName="852Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="997" docProtocolVersion="4010" docProtocolName="EDI_X12" docDefName="997Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="850" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="850Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="860" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="860Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="864" docProtocolVersion="4010VICS" docProtocolName="EDI_X12" docDefName="864Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="864" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="864Def" />
    <SupportedDocumentDefinition initiator="true" docTypeName="997" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="997Def" />
    <SupportedDocumentDefinition initiator="false" docTypeName="856" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="856Def" />
    <SupportedDocumentDefinition initiator="false" docTypeName="810" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="810Def" />
    </TradingPartner>
    </TradingPartners>
    </SelfService>
    We have exported our metadata and looked at the doc_EDI_X12.xml file and ALL of these referenced documents exist in that file and can be seen by going to Administration --> Document and under the Document Protocols navigation --> EDI_X12 --> 5010 --> 810 --> 810Def (as an example).
    If we strip out all of the SupportedDocumentDefiinition lines then the ant script will build an import file with just the trading partners and Identifications.
    What are we doing incorrectly or what is not working properly to get the ant script to build the import zip file??
    Thanks for any assistance,
    Ken

    Does that mean we have to create all of the document type definitions in the selfservice file?
    We have created (installed) all of the document types by installing them from the B2B Administration --> Document page.
    The definitions in the Trading Partner xml file exactly match the definitions of the installed documents.
    In the selfservice.xsd the <element> SelfService shows the profile:DocumentProtocols as minOccurs as 0 :
         <element name="SelfService">
              <complexType>
                   <sequence>
                        <element minOccurs="0" maxOccurs="1"
                             ref="profile:DocumentProtocols" />
                        <element minOccurs="0" maxOccurs="1"
                             ref="profile:TradingPartners" />
                        <element minOccurs="0" maxOccurs="1"
                             ref="profile:Agreements" />
                   </sequence>
                   <attribute name="version" type="profile:non-empty-string"
                        use="optional" />
              </complexType>
         </element>
    so we thought that since the documents had already been defined (created/installed) to B2B they would not have to be redefined in the selfservice xml.
    If we have to define all of the document types in the selfservice xml file that we are using for the trading partners what are the minimum values that we need to include?
    Could we use minimal definitions such as this:
    <DocumentProtocols>
    <DocumentProtocol name="EDI_X12">
    <DocumentProtocolVersion name="4010">
    <DocumentType name="850">
    <DocumentDefinition name="850def" />
    </DocumentType>
    <DocumentType name="997">
    <DocumentDefinition name="997def" />
    </DocumentType>
    </DocumentProtocolVersion>
    </DocumentProtocol>
    </DocumentProtocols>
    before the <TradingPartners> section of the seflxervice xml file?
    Thanks for your assistance!

  • 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,
    Karthick

    Hello 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

  • Reg: Importing Trading partner details

    This is wrt importing trading partner details thro' Demand Management System Administrator > Collection > Legacy Systems >Legacy Collection - Flat File.
    I just got this input from the bug id      6871484. Could anyone help me with the following details?
    I want to know the exact functionality of this option.
    And if at all it allows me to import the TP details, let me know the format of the file or some sample.
    What should be ideal values for the parameters against ...
    Flat File Loader
    and against
    Pre-Process Monitor.

    I was able to get the details as shown in below code...
    CalloutMessage cmIn = (CalloutMessage) input.get(0);
    String fromParty = cmIn.getParameter("FROM_PARTY");
    String toParty = cmIn.getParameter("TO_PARTY");
    String documentType = cmIn.getParameter("DOCUMENT_NAME");
    String action = cmIn.getParameter("ACTION_NAME");

  • Copy Trading Partner to Asset line items from Vendor line items in F-90

    Dear Friends,
    I want to copy trading partner field from Vendor line item to other line items like Asset and Tax in T.code - F-90
    Client want to use Transaction type - 100
    Is it feasible?
    Thanks in advance

    try:
    1) substitution - tcode OBBH
    or
    2) open FI - menu FIBF tcode BF44
        - event 1120 or 1130
    A.

  • Unable to update Partner Unit in Eccs with Trading Partner from FI

    Hi,
    I had removed the Breakdown category from the FS item Master (CX14) for a reco Acct by mistake .Now when i update the master table in CX14 with the same Break down Category(0110 - Partner Unit (break down Type-4) + Translation Currency (break down type -2)) the sytem than gives a pop up window showing the "Report for Transaction Check" where it asks for the Default Value of Partner Unit to be entered.Once i maintain the default value of partner unit all the document for the reco account gets updated with default Partner unit.However in FI module each of the documents posted for this account have diffrent Trading Partner due to which im unable to do the Interunit Elimination.
    Kindly let me know how do i update Partner unit in all the documents in Consolidation with the trading Partner from FI module.
    thanks
    Karan

    Once i maintain the default value of partner unit all the document for the reco account gets updated
    this system behavior makes sense as you are trying to change configuration after loading transaction data. what happens if you go back to the underlying accounts and change TP back to what FI is showing? if u have to deal with a lot of documents u may want to set up a BDC session to do the mass update.

  • 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
    VK

    Thanks 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

Maybe you are looking for

  • Can't send mail after updating to 10.5.5

    I don't know if it could be coincidence, but I had been receiving and sending email all day long until I installed the latest update (10.5.5). Since the installation completed, I have not been able to send mails (receiving is okay). The program keeps

  • IPad screen goes black

    I have a 3g 32gb 1st gen iPad and this has happened to me a couple times. I will be using an app or on the web in safari and then out of no where the screen will go black and the only way to get it to come back on again is to hold power and home for

  • Recent Booting up Problems

    Hey guys, I've been using a windows XP partition on my Macbook Pro for a few years now occasionally for gaming, otherwise I just use the standard Mac OS. I've run into a new problem. I was using it today, and went to the washroom. As I was returning,

  • IProcurement is not a valid responsibility for the current user. Please contact your System Administrator.

    Hi All, When I am trying to click on the 'iprocurement Home page' menu in the iprocurement responsibility getting the below error message in R12; "iProcurement is not a valid responsibility for the current user. Please contact your System Administrat

  • Shared services services  cannot see in services

    hi i was tring to change the password for shared servies and i was able to do it then i deplyoed it succesfully but then after i cant see the shared services in services console strange thing is i can open in my local host but cant open in user machi