CProject 4. 0 Document Approval Document Error

Hi All,
We have the configuration that was working fine for Phase Approval in cProjects 4.0.
I am having a look at it as we are getting ‘<b>You can not begin approval without an approval document’</b> error message on click of ‘Begin Approval’ button.
Though I have not checked ADS (Note - 944221), this does not seem to be  ADS problem as the ‘Document’ with decision as ‘Granted’ gets displayed properly.
I create New Approval by adding approver, after click of ‘Begin Approval’, then the error message gets displayed.
Configuration seems OK as it was working fine few days ago.
Also looking at note – 874054 (Is it only for cProjects 3.1 ?)
The only thing which I am doubtful about is, in configuration ‘Activate Forms Per Project Type’ where I need to deactivate the smartform ‘DPR_APPROVAL_HIER’, which is set to ‘Active’ (i will deactivate and test again). Also the PDF Print form ‘DPR_APPROVAL_HIER’ is set active.
Thanks in advance....

Hi Bushan,
try this ,
In c project configuration --> Activate From per Project Type
--->you ACTIVATE the PDF FORM
---> DEACTIVATE the smart form
for DPR_APRROVAL_HIRE FORM
thanks
sunil

Similar Messages

  • CProjects - Approval Document for a Task

    Hi,
    Is it possible to create some approval scenario for a task in cProject.
    There are some tasks which need cost approval. Can anyone recommend an easy to implement solution using the standard by either reusing approval document or attaching a BW report with a task.
    kind regds
    Vishal

    Hi Thomas,
    I do understand and agree with your opinion. The issue is that we need to get an object approved that is not a phase in the main project definition. So just wondering if we can create this object as a phase under a subproject definition - This is just to avoid these huge modifications. So if we can treat a task as a phase of the subproject and trigger the approval of this, do you see any issues technically ? (Though there are issues in functional design, but they would outnumber the benefits if it can be realised ?)
    Cheers
    Vishal

  • Approval document in cProjects 4.0 through Smartforms

    Hi all,
    Is there any way to manage approval documents in cProjects through smart forms instead of Adobe Server (AIF)?
    If so, is there any documentation for configuring it that way?
    Thank you very much in advance!
    Kind regards,
    Isabel

    J,
    Sorry, I don't leave my email address up except for brief periods when I'm looking for someone to use it. Since Peter has your email, I'm sure he will sort that issue out for you. Meanwhile, I'll give you some additional information on posting screen shots.
    Any of the photo hosting sites will work. I'm currently using Photobucket as I've found it to be more reliable than others that I've tried. The site will guide you through the upload process. Then it will offer you several options for sharing your "photo". Choose the HTML option. Copy that HTML code and paste it here. That's all there is to it.
    Jerry

  • CProjects Phase Approval : Approval Document does not exist

    Hello,
    I am trying to approve a phase in cProjects 4.0 (WD ABAP Based).
    When I goto Approval Tab --> Approval Document, it displays:
    Approval Document does not exist
    I have checked the configuration and everything looks correct.
    For Project Type I have activated the Form DPR_APPROVAL_HIER
    The ADS is configured properly.
    I also checked Note 874054 - You cannot start approval w/o approval document, and the config is as per this note.
    What else can be likely reasons for this problem.
    Any help is appreciated.
    Regards,
    Shubham

    Hi Shubham,
    As per SAP, ADS is supported by the following servers only:
    Windows server 2003 on IA32 32 bit
    Linux Suse SLES 9 on x86_64 64 bit
    Linux Red Hat EL 4 on x86_64 64 bit
    AIX 5.2, 5.3 64 bit
    HP-UX 11.11 on PA-RISC 64 bit
    HP-UX 11.23 on PA-RISC 64 bit
    Solaris 9 on SPARC 64 bit
    Solaris 10 on SPARC 64 bit
    Refer http://service.sap.com/pam - Netweaver 2004s - Additional Components.
    Check the Server on which your cProjects has been installed.
    Regards,
    Reema.

  • Regarding phase approval document

    Hi,
       Error occuring when try to begin the approval of phases in cProject. A error message occurs as
    ''You cannot begin approval approval test without an approval document''
    But already I have assigned and activated the approval document DPR_APPROVAL_HIER in Customising---->Activate forms per project type. I have assigned the same in Customising -
    >define Phase types . Still I face the problem.
    Pls help me to solve this issue.
    Thanking you.
    Regards,
    Sarvodaya

    Hi,
    Check with following Tests:
    I ABAP:
    1.  Use transaction SA38 to execute the program FP_TEST_00.
               Detailed information about this test program and about how you should then proceed is given in the Adobe Document Services Configuration Guide in the Help Portal under:
               http://help.sap. com/saphelp_nw2004s/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm -> Adobe Document Services Configuration Guide -> Configuring the Web Service -> Securing Access to the Web Service ->Configuration Check -> Configuration Check for PDF-Based Forms in ABAP
              o If the FP_TEST_00 form is displayed in the print preview, the ADS configuration is correct.
                        -> Check your application program that contains the call for the form, and the form itself, for possible errors See point 5 for further information.
              o If the system displays an error message instead of a form, the configuration of ADS is incorrect.
                        -> Carry out the additional tests from point 2 onwards.
    2.  Use transaction SA38 to execute the program FP_PDF_TEST_00.
                  This enables you to check the RFC connection to ADS (see the reference to the documentation given above).
              o If the system displays the version number of ADS, the configuration of the RFC connection is correct.
                        -> Proceed to point 4.
              o You receive one of the following error messages:
                        1. If the system displays dialog fields for user and password instead of the version number, the entries for user and password in the RFC connection do not match the entries in user management.
                        -> Check the user and the password. Continue with point 3.
                        2. The system displays a "SYSTEM ERROR" with the following text:
                        "ERROR CODE    :    100.101
                        ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code"
                        -> Contact your system administrator and ask them to check or correct the details for target device, service number and path prefix in the RFC connection (transaction SM59).
                        3. If the system displays an error message stating that there is no valid HTTP connection, then there is no RFC connection to ADS.
                        -> Contact your system administrator and ask them to correct or create the RFC connection (transaction SM59).
    3.  Check the user and password of ADS
                  Requirement: In order to carry out this test, you must know the user and password for ADS. If you do not know this information, contact your system administrator and ask them to carry out the test.
                  A detailed description about the procedure is contained in the documentation for the Adobe Configuration Guide at:
                  http://help.sap. com/saphelp_nw2004s/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm -> Adobe Document Services Configuration Guide -> Configuring the Web Service -> Securing Access to the Web Service ->Configuration Check -> Configuration Check for PDF-Based Forms in ABAP -> Checking the User and Password
              o If the system displays the version number of ADS, the configuration of the user and password is correct.
                        -> Proceed to the next point (4).
              o If the system does not display a version number (the page in the Web browser does not change, and submit continues to be displayed), the configuration of ADS is incorrect.
                        -> Contact your system administrator and ask them to correct the configuration for the user and password.
    4.  Check the settings for the destination service
                  To use the destination service on AS Java, settings are required on AS ABAP and AS Java. Therefore, this test contains several steps.
                  4. 1 In your ABAP system (transaction SA38), call the FP_CHECK_DESTINATION_SERVICE program (available as of NW2004s SPS 08).
                           a) First of all, execute the program without selecting the option "With Destination Service".
                           The system processes a test form in the background and displays the size of the generated PDF. It does not use the destination service in the process.
                           b) Now select the option "With Destination Service" and execute the program again. The system processes the test form, using the destination service.
              o If the system displays the same message (file size of generated PDF) as it does in a), the configuration of the destination service is correct.
                        -> Proceed to the next point (5).
              o If the system issues an error message, the configuration of the destination service is incorrect.
                        -> Carry out tests 4.2 to 4.4.
                  4. 2 Check whether the /default_host/sap/bc/fp and /default_host/sap/bc/fpads ICF services are active. (transaction SICF). If this service is not active, activate it. Note: As of NW2004s Support Package Stack 12, when you bundle in distributed systems (in other words, for "non-double-stack installations"), it is optional to use the fpads ICF service
                  4.3 Check the settings for the ICF service.
                           a) Enter the following URL in your Web browser:
                        http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp
                        < server> is the AS ABAP, <port> is the HTTP port of the AS ABAP. (you can determine this information using transaction SICF).
                           b) In the dialog box for the user, enter ADS_AGENT and the relevant password.
              o If the ICF service settings are correct, the browser displays the layout information of the FP_TEST_00 form in XML format.
                        -> Proceed with point 4.4.
              o If the browser displays an error message instead of the XML file, a configuration error occurred.
                        -> Check whether the user ADS_AGENT exists on the AS ABAP, and if the user has the required authorizations and roles (SAP_BC_FP_ICF).
                  4.4. Check the settings for the destination service on AS Java
                           a) Call Visual Administrator and navigate to Services -> Destinations
                           (detailed instructions are available on the Help Portal at: http://help.sap.com/saphelp_nw2004s/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm ->Adobe Document Services Configuration Guide -> Configuring the Web Service -> Securing Access to the Web Service -> Creating or Changing the Destination Service)
                           b) Extend the setting in field URLunder Connection Settings to:
                           http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp
                           (The <server> and <port> that are already available refer to the AS ABAP.)
                           c) Choose 'Save and Test'
                           d) The system calls the ABAP system that stores the form templates.
              o If the settings are correct, the system issues the message: "HTTP GET response code 200 Content Type/xml."
                        -> Proceed with point 5.
              o If the system issues an error message, the configuration of the destination service is incorrect.
                        -> Contact your system administrator and ask them to correct the settings for the destination service.
                           e) Do not forget to change the URL back to http://<server>:<port>.
    5. Generated PDF with additional information
                  Call your form and save the generated PDF with additional information locally. You receive a PDF with attachments, which enable you to analyze the problem in detail.
                  Information about the PDF with additional information is available in the problem analysis guide (PAG) for SAP NetWeaver (TM) at:
                        http://help.sap.com/saphelp_nw70/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm ->Usage Type Application Server Java -> Problem Analysis Scenario for Adobe Document Services -> Adobe Rendering Error
                  Setting using transaction SFP
                  For more information about how to proceed if you use the dialog box in transaction SFP to set this function, see the documentation for SAP Interactive Forms by Adobe in the SAP Help Portal at:
                        http://help.sap.com/saphelp_nw70/helpdata/en/37/47a2be350c4ac8afe36b691203971f/frameset.htm
                        (You can display the document in German at: http://help.sap.com/saphelp_nw70/helpdata/de/37/47a2be350c4ac8afe36b691203971f/frameset.htm)
                        -> SAP Interactive Forms by Adobe -> PDF-Based Print Forms -> Calling Forms in an Application Program -> Saving Runtime Information and a Generated PDF Locally
                  Setting using user settings
                  You can also use the user settings to activate the function "PDF with Additional Information".  Proceed as follows:
                        1. Call transaction SU3 ('Maintain User Profile') or SU01 ('User Maintenance').
                        Note that you require the relevant authorization for the user maintenance of other users.
                        2. Choose the tab page 'Parameters', and enter the required parameters and values:
                        FPTRACELEVEL = 04
    Setting the trace to the value required for the local saving of runtime information and for the generation of the PDF that contains additional information.
                        FPTRACEFILE = <directory>\<file name>
    File for the local saving of runtime information This specification is optional.
                        FPSAVEERRORPDF = X
    The system generates a PDF that contains additional information.
                        FPERRORPDFFILE = <directory>\<file name>
    File for locally saving the PDF that contains additional information
                         Caution: Local saving is possible only for applications that have a GUI connection, and therefore, this is not supported for Web Dynpro ABAP.
                        3. These values then have a fixed assignment to the user.
                         Reset these values after troubleshooting is completed.
                  -> Attach these files (PDF with attachment) to a message with the component BC-SRV-FP, including a precise description of the problem.
    Niranjan
    Let me know if it helps !!!

  • 11I - PO DOCUMENT APPROVAL MANAGER FAIL 시의 기능 개선 사항.

    제품 : MFG_PO
    작성날짜 : 2004-11-29
    11I - PO DOCUMENT APPROVAL MANAGER FAIL 시의 기능 개선 사항.
    ====================================================
    PURPOSE
    PO Document Approval Manager Fail 시의 기능 개선 사항에 대한 검토.
    Explanation
    PO 를 승인하였으나 Status 가 In-Processs 인 경우가 발생할 수있다. 이런
    경우는 보통 PO Document Approval Manager 가 정지되었거나, Workflow 에서
    Error 가 발생한 경우가 일반적이다.
    이런 경우의 처리 방법은 Workflow Sysadmin 권한으로 Login 하여 Retry 하거
    나, wfretry.sql 을 수행하여 문제가 발생한 workflow 의 진행을 재시도 하
    게 된다.
    Procurement Family Pack F 에서는 이같은 재시도를 자동으로 수행하는 기능
    이 추가되었으며 아래의 방법으로 설정할 수있다.
    1) How to Implement This New Feature:
    - Apply 11i.PRC_PF.F (Procurement Family Pack F) AND one-off
    patch 1942091
    - Procurement Family Packs G and higher
    2) Technical Details:
    a) Dodument manager 에 관련된 Error 를 처리하기 위하여 새로운
    Purchasing Item Type 인 "POERROR" 이 추가되었다.
    POERROR item type 에 대하여 아래의 workflow attribute 가 define 되었
    으며 이 값들을 설정하여야 한다.
    관련 Attribute 들은 아래와 같으며 Business 환경에 맞게 적절한 값으로
    설정한다.
    DOC_MGR_WAIT_RELATIVE_TIME Length of time, in minutes, processes
    will have to wait before getting picked
    again.
    Default = 0
    RETRY_COUNT Number of attempts to get document
    manager for approval.
    Default = 0
    TIMEOUT_VALUE Length of time, in minutes, for
    notification automatically close itself.
    Default = 0
    SYSADMIN_USER_NAME Application user (typically the System
    Administrator) who can receive
    notifications for document manager-
    related errors in status 1 and 2.
    YOU MUST DEFINE THIS MANUALLY TO A VALID
    USERNAME.
    b) POERROR item type 에 대하여 Workflow Background Processor 가 주기적으
    로 수행되어야 한다.
    document manager 에 대한 재시도 횟수는 아래의 요소에 의해 결정된다.
    - Attribute DOC_MGR_WAIT_RELATIVE_TIME
    - WorkFlow Background engine wait period
    c) Approval mode 와 관계없이 POERROR 를 처리할 Workflow Background
    process 가 수행되어야 하며, wait time 후에 해당 process를 재시도하게
    된다. Background engine 이 start 되면 document approve 를 다시 시도하
    게된다. User 는 status 1 와 2 errors 에 대해서는 Notification 을 받
    지 않으며, status 3 error 는 User 에게 Notification 을 보내게 된다.
    (Sysadmin 에게 발송되지 않음.)
    Example
    Reference Documents
    Note 160713.1 - Improved Document Error Handling Provided in
    Procurement Family Pack F Quick Reference

  • FICA Document Approval - CA_DOC, Workflow 21000088

    Hi All,
    I am using the standard Workflow 21000088 for FICA document approval for Posting using the Business Object CA_DOC.
    I had maintained Event 5500 as well as Rule for Agent assignment using Rule - 21000056.
    Now whenever any posting happens, An approval work Item is sent to Supervisor. But Nothing triggered after it is approved or Rejected.
    Supervisor Double clicks on the Work Item and as per SAP documentation, if it approved, it should remove the Check reason from Document, if it is rejected, it must display Reverse transaction to reverse document. But these actions are not happening.
    Anybody has any idea?
    Thanks
    Manas

    Hello,
    We have a similar workflow for approving doc postings (we made a copy of the SAP standard one) and it works fine.
    Have you had a look at the workflow log? Try transaction SWI1 (for the relevant dates), find the workitem, and click on the 'scroll' icon.
    Then you will be able to see where the workflow stopped and what the error is. Please tell me what it says.
    cheers
    Paul Bakker

  • 'Approval document'  in Phase Type

    Hi,
    Can somebody let me know how do we configure 'Approval document' while setting a Phase relevant for Approval? I have done relevant settings in the Phase Type. Waiting for your reply @ earliest.
    Thanks & Regards,
    Gaurav

    Hi Gaurav,
    I have sent you one mail on your yahoo id regarding the flow and make sure that as the decision maker you have assigned the resource not the role.
    if you still face the same problem then try out these steps:-
    1.  Call transaction SFP, enter the DPR_APPROVAL_HIER form and choose          
        'Change'.                                                                               
    2.  Go to the following node in the context view: DPR_APPROVAL_HIER ->         
        MAIN -> DECISION_MAKER -> DATA -> LINE_TERMS_DECIDER ->                    
        DECISION_MAKER_L                                                                               
    a) Remove the conditions from the elements in the folder                   
           DECISION_MAKER_L. To do so, double-click the relevant elements,         
           choose 'Conditions' and remove the conditions                           
           (C_ROLE_DESCRIPTION, C_DECIDER_AFTER, C_DECIDER_BEFORE,                 
           T_DECIDER_ON, C_DECIDER_ON, T_DECIDER_AT and C_DECIDER_AT).                                                                               
    b) Then use drag-and-drop to move these elements from the                  
           DECISION_MAKER_L folder to the superior folder                          
           LINE_TERMS_DECIDER.                                                                               
    c) Delete the empty folder DECISION_MAKER_L using the context menu         
           (right-click to open the context menu).                                                                               
    Page 2                                                                               
    3.  Choose 'Layout'. In the designer, select 'Palettes' from the menu          
        bar and select the palettes 'Hierarchy' and 'Object'.                                                                               
    CAUTION: Double-clicking in hierarchy view may change the layout.          
        Therefore, make sure you only click once on a object to select it.                                                                               
    a) In the hierarchy view, open the subtree MAIN -> DECISION_MAKER ->       
           DATA -> LINE_TERMS_DECIDER.                                                                               
    b) Remove the subform LINE1 below the node COL3. To do this, select        
      c) Check or change the data binding of the following elements (go to          
       the palette 'Object', choose the 'Binding' tab:                                                                               
    COL1: Default binding: None                                                                               
    T_DECISION_MAKER: Default Binding: T_DECISION_MAKER                                                                               
    COL2: Default binding: None                                                                               
    C_PROJECT_ROLE: Default Binding: C_PROJECT_ROLE                                                                               
    C_ROLE_DESCRIPTION: Default Binding: C_ROLE_DESCRIPTION                                                                               
    COL3: Default binding: None                                                                               
    LayoutDummy: Default binding: None                                                                               
    LINE2: Default Binding: None. Set the indicator 'Repeat Subform            
       for Each Data Item', do not set the 'Min Count' and the 'Max'              
       indicators.                                                                               
    C_DECIDER_AFTER: Default Bindung: C_DECIDER_AFTER                                                                               
    C_DECIDER_BEFORE: Default Bindung: C_DEFCIDER_BEFORE                                                                               
    LINE3: Default Binding: None. Set the indicator 'Repeat Subform            
       for Each Data Item', do not set the 'Min Count' and the 'Max'              
       indicators.                                                                               
    T_DECIDER_ON: Default Bindung: T_DECIDER_ON                                                                               
    C_DECIDER_ON: Default Bindung: C_DECIDER_ON                                                                               
    T_DECIDER_AT: Default Bindung: T_DECIDER_AT                                                                               
    C_DECIDER_AT: Default Bindung: C_DECIDER_AT                                                                               
    d) For element LINE3, enter the following FormCalc script for the             
       event "form::ready":                                                                               
    if  (  $.C_DECIDER_ON.isNull  )  then                                      
           $.presence = "hidden"                                                  
       endif                                                                      
    4.  Save and activate the form. If the system issues the error message 
        "Unknown Layout Type" when you save, go to the properties view and 
        change the layout type to 'Standard Layout'.                       
    Best regards,
    Jatin

  • Web Analysis 9.3.1: Error occured while opening document. Document ID = {0}

    Hi Experts,
    I am having an issue while opening a web analysis dashboard report. When I try opening it, web analysis runs for about 15 mins & then throws following error:
    Error occured while opening document. Document ID = {0}
    The report opens with its header having company log & two buttons, but data grid remains empty.
    The source of Grid is Essbase. The tunning parameters in Essbase.cfg file are in place.
    Could anyone please through more observation on this issue. Let me know if any further information is needed!.
    Kindly suggest me any way to resolve it.
    Thanks,
    Krishan

    The isapi (if you use one) timeout setting might be smaller than the time essbase needs to retrieve te information.
    but most probably the analysis applicationserver jre heapsize is either to small or needs to much time to allocate it. Be sure to increase heapsize and set max equal to min (try 800mb, if your hardware has that resource)

  • WebAnalysis Error: Error occured while opening document. Document ID = {0}

    Hi Experts,
    I am having an issue while opening a web analysis dashboard report. When I try opening it, web analysis runs for about 15 mins & then throws following error:
    Error occured while opening document. Document ID = {0}
    The report opens with its header having company log & two buttons, but data grid remains empty.
    Kindly suggest me any way to resolve it.
    Thanks,
    Krishan

    Hi Natesh,
    Thanks for your reply to my query posted in this forum. Please find my inline answers between asterisk to your questions:
    Whatz the source of your Grid? Relational SQL Query (OR) A spreadsheet with Essbase database connection file?
    * Yes, the source is Essbase.*
    If source is Essbase, it seems- Outline might've got altered when you're trying to refresh the report.
    * The outline was in tandem when we tried running this report in WebAnalysis. This outline & WebAnalysis report which is in Dev Server is a replica of the one in Test Server where it runs fine. *
    If source is based on a Relational SQL query, chances are that- Query is no longer valid.
    * NA as this statement is NOT applicable to our source.*
    If it's Essbase, it's also likely that- It ran out of time while fetching the data from Essbase. You may try playing around with the parameters in Essbase.cfg file.
    * This might be one of the causes, but I double checked the all the tunning parameters in Essbase.cfg file in place.*
    Could you please through more observation on this issue. Let me know if any further information is needed!.
    Thanks for your time.
    Regards,
    Krishan
    Edited by: user10475612 on Nov 8, 2009 1:07 PM
    Edited by: user10475612 on Nov 8, 2009 1:09 PM
    Edited by: user10475612 on Nov 8, 2009 1:12 PM

  • Document protocol identification error

    Hi While receving Shipment from our trading partner, it showing below error in b2b, Please help me in resolving this? We are suing Custom document over internet.
    Machine Info: (essaps000-u008.emrsn.com)
    Description: Unable to identify the document protocol of the message
    StackTrace:
    Error -: AIP-50083: Document protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) MimePackaging:unpack:Exit
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Enter
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Number of Components = 1
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage compInfoList[k].getValue().toLowerCase()==>text/plain
    2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Components List= [Loracle.tip.adapter.b2b.packaging.ComponentInfo;@4fa23a
    2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
    2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage File Name=>null
    2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: AS2 Identifier Value: EMRSNS
    2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
    2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage:Payload <?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ApplicationArea>
    <Sender>
    <LogicalID>SCN024538</LogicalID>
    <ComponentID>SHIPMENT</ComponentID>
    <TaskID>SHOW</TaskID>
    <ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
    <ConfirmationCode>Never</ConfirmationCode>
    <AuthorizationID>160</AuthorizationID>
    </Sender>
    <CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
    </ApplicationArea>
    <DataArea>
    <Show>
    <OriginalApplicationArea>
    <Sender>
    <LogicalID>EMR1601000</LogicalID>
    </Sender>
    <CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
    </OriginalApplicationArea>
    </Show>
    <Shipment>
    <ShipmentHeader>
    <DocumentID xsi:type="ItemIDType">
    <ID>TSI543897</ID>
    </DocumentID>
    <DocumentDateTime>20090914</DocumentDateTime>
    <DocumentReference type="WayBillAirBill">
    <DocumentID>TTSA021720000001</DocumentID>
    </DocumentReference>
    <DocumentReference type="BillOfLading">
    <DocumentID>BTSA02172000002</DocumentID>
    </DocumentReference>
    <DocumentReference type="PackingSlip">
    <DocumentID>TSI543897</DocumentID>
    </DocumentReference>
    <Attachment inline="false">
    </Attachment>
    <ActualShipDateTime>20090914</ActualShipDateTime>
    <ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
    <ShipFromParty>
    <PartyIDs>
    <ID>501V00041757</ID>
    </PartyIDs>
    <Name>BENCHMARK ELECTRONICS THAILAND</Name>
    <Location>
    <ID>160234567</ID>
    </Location>
    </ShipFromParty>
    </ShipmentHeader>
    <ShipmentItem>
    <ItemID>
    <ID>166806G1</ID>
    <RevisionID>
    </RevisionID>
    </ItemID>
    <SupplierItemID>
    <ID> EML166806G1</ID>
    </SupplierItemID>
    <Description>ASSY GROUND CURRENT DETECTOR</Description>
    <ShippedQuantity unitCode="EA">20</ShippedQuantity>
    <PurchaseOrderReference>
    <DocumentID xsi:type="DocumentIDType">
    <ID>501LBR295816</ID>
    </DocumentID>
    <ReleaseNumber>
    </ReleaseNumber>
    <LineNumber>001</LineNumber>
    <ScheduleLineNumber>1 </ScheduleLineNumber>
    </PurchaseOrderReference>
    </ShipmentItem>
    </Shipment>
    </DataArea>
    </ShowShipment>
    2009.09.15 at 10:31:07:506: Thread-30: B2B - (DEBUG) calling setMode() changing from -1 to 2
    2009.09.15 at 10:31:07:511: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Exit
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP EMRSNS
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
    2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
    2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
    2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
    2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
    2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
    2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
    2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
    2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
    2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
    2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@23ce9f
    2009.09.15 at 10:31:07:597: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons:  A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
    2009.09.15 at 10:31:07:598: Thread-30: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons:  A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
         at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
         at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:370)
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.09.15 at 10:31:07:598: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
    2009.09.15 at 10:31:07:657: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
    2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
    2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
    2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
    2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
    2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
    2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
    2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
    2009.09.15 at 10:31:07:661: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
    2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
    2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
    2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
    2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
    2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {CONTENT-TRANSFER-ENCODING=binary, CONNECTION=Keep-Alive, AS2-FROM=BENCHQA, CONTENT-TYPE=application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m", MIME-VERSION=1.0, RECEIPT-DELIVERY-OPTION=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll, AS2-VERSION=1.1, EXPECT=100-continue, USER-AGENT=Microsoft(R) BizTalk(R) Server 2006 R2 3.0.1.0, AS2-TO=EMRSNS, CONTENT-LENGTH=5137, ORACLE-ECID=1253032264:10.236.2.145:16396:0:3376,0, MESSAGE-ID=<ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>, HOST=emersonb2b-s.emrsn.com, B2B_SERVLET_URI_PATTERN=/b2b/transportServlet, DISPOSITION-NOTIFICATION-TO=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll}
    2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
    2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
    2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
    2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
    2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
    2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
    2009.09.15 at 10:31:07:671: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
    2009.09.15 at 10:31:07:684: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
    2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
    2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
    2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 IdentifierEMRSNS
    2009.09.15 at 10:31:07:769: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
    2009.09.15 at 10:31:07:815: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2009.09.15 at 10:31:07:827: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
    2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>
    2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
    2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
    2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) Engine:notifyApp Enter
    2009.09.15 at 10:31:07:848: Thread-30: 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>0AEC0291123BE8B0DB800000B91B0200</b2bMessageId>
    <errorCode>AIP-50083</errorCode>
    <errorText>Document protocol identification error</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (essaps000-u008.emrsn.com)
    Description: Unable to identify the document protocol of the message
    StackTrace:
    Error -:  AIP-50083:  Document protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
      ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) Engine:notifyApp Exit
    2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
    2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
    2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
    2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
    2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
    2009.09.15 at 10:31:07:860: Thread-30: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
    2009.09.15 at 10:31:07:861: Thread-30: B2B - (DEBUG) DBContext commit: Enter
    2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Leave
    2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
    Edited by: user8653471 on Sep 15, 2009 10:55 PM

    Hi Anuj,
    Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
    Do above statement is related to EDI? I am using Custom document over internet
    I did not find any unreadable/non-xml characters in the xml file, here i am attaching the xml fille.
    <?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ApplicationArea>
    <Sender>
    <LogicalID>SCN024538</LogicalID>
    <ComponentID>SHIPMENT</ComponentID>
    <TaskID>SHOW</TaskID>
    <ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
    <ConfirmationCode>Never</ConfirmationCode>
    <AuthorizationID>160</AuthorizationID>
    </Sender>
    <CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
    </ApplicationArea>
    <DataArea>
    <Show>
    <OriginalApplicationArea>
    <Sender>
    <LogicalID>EMR1601000</LogicalID>
    </Sender>
    <CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
    </OriginalApplicationArea>
    </Show>
    <Shipment>
    <ShipmentHeader>
    <DocumentID xsi:type="ItemIDType">
    <ID>TSI543897</ID>
    </DocumentID>
    <DocumentDateTime>20090914</DocumentDateTime>
    <DocumentReference type="WayBillAirBill">
    <DocumentID>TTSA021720000001</DocumentID>
    </DocumentReference>
    <DocumentReference type="BillOfLading">
    <DocumentID>BTSA02172000002</DocumentID>
    </DocumentReference>
    <DocumentReference type="PackingSlip">
    <DocumentID>TSI543897</DocumentID>
    </DocumentReference>
    <Attachment inline="false">
    </Attachment>
    <ActualShipDateTime>20090914</ActualShipDateTime>
    <ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
    <ShipFromParty>
    <PartyIDs>
    <ID>501V00041757</ID>
    </PartyIDs>
    <Name>BENCHMARK ELECTRONICS THAILAND</Name>
    <Location>
    <ID>160234567</ID>
    </Location>
    </ShipFromParty>
    </ShipmentHeader>
    <ShipmentItem>
    <ItemID>
    <ID>166806G1</ID>
    <RevisionID>
    </RevisionID>
    </ItemID>
    <SupplierItemID>
    <ID> EML166806G1</ID>
    </SupplierItemID>
    <Description>ASSY GROUND CURRENT DETECTOR</Description>
    <ShippedQuantity unitCode="EA">20</ShippedQuantity>
    <PurchaseOrderReference>
    <DocumentID xsi:type="DocumentIDType">
    <ID>501LBR295816</ID>
    </DocumentID>
    <ReleaseNumber>
    </ReleaseNumber>
    <LineNumber>001</LineNumber>
    <ScheduleLineNumber>1 </ScheduleLineNumber>
    </PurchaseOrderReference>
    </ShipmentItem>
    </Shipment>
    </DataArea>
    </ShowShipment>

  • Error message when opening a document "this document is being used by another user

    error message when opening a document "this document is being used by another user, do you want to make a copy?
    I select yes, then new message - word can not open this document.the document might be in use or it may not be an invalid document.
    Any suggestions?

    Hello MrNeuf,
    I would recommend releasing and renewing the IP lease on the affected computer. The following article provides further information and details the process of doing so.
    Mac OS: How to release and renew a DHCP lease
    http://support.apple.com/kb/TS1920
    Cheers,
    Allen

  • Error loading BASIC document. General Error. General input/output error".

    Error loading BASIC document. General Error. General input/output error".

    I guess your problem is related to StarOffice8, right?
    I had the same issue after upgrading StarOffice7 to StarOffice8:
    http://forum.java.sun.com/thread.jspa?threadID=5287604&tstart=0
    Apparently the .StarOffice8 directory in your export/home directory was created based on .StarOffice7
    directory. Probably here something went wrong. Maybe a bug.
    So the solution is very simple:
    rm -r .StarOffice8 in your export/home directory and restart StarOffice8.
    Or you can also rename the directory.

  • Document protocol identification error for custom protocol

    Hi,
    Working for B2B inbound transaction. By using B2B need to transfer file from remote TP location to Host TP location. The file type is non EDI file (FLAT file of type fixed length) .
    I am doing given below steps but B2B giving document identification protocol error after file picked for processing.
    Document Defination at administration level:
    Protocol : Custom
    Version : 1.0
    DocType : CustomerDoc
    DocDef : CustomerDocDef( In these mentioned values as
    Identification Type = "Flat"
    Identification Start Position = 1,
    Identification End Position = 1 ,
    Identification Value = 1)
    Host Tp set up:
    TP Name : Client
    EDI INTERCHANGE ID : ClientID
    EDI GroupID : ClientID
    EDI Interchange ID Qualifier : 01
    Listening channel : Client_Deliverychannel
    Remote TP setup :
    TP Name : Customer
    EDI INTERCHANGE ID : CustomerID
    EDI GroupID : CustomerID
    EDI Interchange ID Qualifier : 02
    Document IMPORTED : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
    Listening channel : Customer_Listeningchannel
    Agrement for the Remote TP 'customer:'
    Document using : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
    TP names using : Customer , Client
    Listening channels using : Customer_Listeningchannel, Client_Deliverychannel
    Sample Flat File Using:
    1 00123451107200600123456780021000021001500049870USD 0000000000
    Thanks&Regards,
    Sridhar.Rachumallu.
    Edited by: user1133742 on Jun 29, 2010 11:54 PM
    Edited by: user1133742 on Jun 30, 2010 12:00 AM

    Configuration is looking fine. however error says B2B is not able to identify incoming document.
    Please paste/send the log in trace:32 mode for further analysis.
    Rgds,
    Nitesh Jain
    [email protected]

  • Duplicating An Approved Document

    Hi Experts,
    I have a scenario which is described below.
    A PO was generated which has gone through the approval procedure and has been approved. The originator has added the approved document and saved it.
    Now, the originator has to release another PO which has same materials as in the Approved PO. When the originator is duplicating the document it gives duplicates the PO but then the Vendor Code and Vendor Name fields are both disabled. Which does not allow the Originator to select the new vendor for the duplicated document.
    Any thoughts on this.. Is this a bug or the functionality is right as per SAP?
    Regards
    Rohan S. Kamble

    Hi Gordan, Rahul,
    My SAP B1 Version is 8.8 PL 10.
    Rahul:
    Yes with normal PO there is no such issue. Thats why i specified Approved PO. There is certainly an issue with the Approved PO's.
    Could any one please reconfirm if the behavior is occurring for PL 10?
    Regards
    Rohan S. Kamble
    Edited by: Reno on Feb 18, 2011 2:39 PM

Maybe you are looking for

  • Flash Player seems to install but when trying to play tv shows it doesn't register and asks me to install again.

    I have a Mac OS X Yosemite 10.10.3, i have no problem viewing videos on youtube but when i try and watch movies or tv shows streaming them off websites, it seems to come up with this message. 'Please install flash player HD to continue (required),' w

  • Windows will no longer detect iPhone camera

    I'm sorry to be the millionth person to post a thread about this problem, but I can't seem to find any solution to this problem. My computer simply will not recognize my iPhone 3GS as a camera anymore, so I can't import any of my photos. Yes, it is s

  • Extract the data from URL using XI

    Hi, Please let me know if  you have idea  about this: Scenario is: 1. We are extracting some raw data (strings) from one url(http) using java program ... 2. After extracting the data , some parsers making the XML files for that. Now my question is :

  • !!!! Scott Kelby's taken over my keyword list

    Hi. Coming home from a shooting session today, I imported my files as usual, but when I should start tagging them, I found that most of my keywords were missing from the keyword list (approx. 45 of 50 categories missing). Instead, I found keywords li

  • Changing namespace when calling OSB business service

    Hello All, I have a business service in OSB calling a BPEL process. The BPEL process returns values prefixing all the tags with name space "pidx". The name space definition is xmlns:pidx="http://www.api.org/pidXML/v1.2". When I test the business serv