Missing Process Step - File to IDOC scenario

Hi gurus!
I'd like to help me with this topic. I have an interface that takes a File, its get converted with the CC File Sender (File Content Conversion) to XML, a mapping in the middle to the iDoc, and then it makes the ammount of "N" ACC.DOCUMENT.
The problem that we're facing is that when we get a very high load of messages entering to XI (e.g. the end of months) the users puts file with an average size of 1.5 MB. We inmediately see the checkered flag in sxmb_moni transaction on XI (Succesful status), but we sometimes wait for many days to see the IDOCS...
I'd like to know where can i find the status of these messages, because i don't know where's the step after the flag in the moni AND before the creation of iDocs.
Regards.
Juan

Like I said, the checkered flag status in SXMB_MONI means the process was successfully completed on the Integration Engine.  Processes are passed to the Adapter Engine once they're completed on the IE.  There can still be a problem at the Adapter Engine level, for which case SXMB_MONI is useless as a tool for problem determination.  You need to go into the Runtime Workbench and access the Message Monitoring tool and check the status for the Adapter Engine when your problem occurs.  If your messages are stuck on the Adapter Engine you can drill into the specifics of each message for problem determination.  In our case when this occurs it is generally either a problem with the java stack, user lock issue, or  SXI / CPA cache problem.

Similar Messages

  • Steps required in File to Idoc Scenario

    Hey guys i m doin a file to Idoc scenario and just wanna make sure my steps r correct.
    steps done on the XI server
    1.Create RFC destination(test the destination by giving the target host as the R/3 server).
    2.Create port for the RFC destination.
    steps on the R/3 side
    1.Create/verify logical system name.
    and finally create business system for this logical system in SLD.
    now do i need to do partner profile as well or not? and if i have to do it how is it accomplished.
    thanx
    ahmad

    Hi,
    The following are needed for idoc to file scenario...
    In R3...
    RFC dest to XI (sm59)
    Logical system (bd54)
    Port to XI (we21)
    Partner profile for the logical system (we20)
    In XI...
    RFC dest to R3 (sm59)
    Port to R3 (idx1)
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3.
    Regards,
    Uma

  • File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

    Hi All,
    I am doing File to IDoc scenario( Bypass) for Orders05.
    File is picking succesfully and not posting the idoc in the SAP..
    My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
    but the error it is showing is <b>" Obligatory node 'E1EDK01' missing in the structure ORDERS05 "</b>
    Please suggest me ASAP what is going wrong .
    Thanks in Advance.
    Regards
    Seema.

    The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
    This is how it should look, ( check the parts in bold),
    <?xml version="1.0"?>
    <ORDERS05>
    <IDOC <b>BEGIN ="1"</b>>
    <EDI_DC40 SEGMENT="EDI_DC40">
    <DOCNUM>1</DOCNUM>
    <DIRECT>2</DIRECT>
    <IDOCTYP>ORDERS05</IDOCTYP>
    <CIMTYP></CIMTYP>
    <MESTYP>ORDERS</MESTYP>
    <SNDPOR>XXXXXXXXX</SNDPOR>
    <SNDPRT>LS</SNDPRT>
    <SNDPFC></SNDPFC>
    <SNDPRN>XXXXXXXX</SNDPRN>
    <RCVPOR>XXXXXX</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPFC></RCVPFC>
    <RCVPRN>XXXXXXXX</RCVPRN>
    <CREDAT>20070511</CREDAT>
    <CRETIM>152803</CRETIM>
    </EDI_DC40>
    <E1EDK01 <b>SEGMENT = "1"</b>><BELNR>AAAAAAAAA123</BELNR>
    </E1EDK01<b>SEGMENT = "1"</b>>
    <E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
    </E1EDKA1>
    <E1EDKA1 <b>SEGMENT = "1"</b>><PARVW>LF</PARVW>
    <NAME1>international</NAME1>
    <NAME2>Delhi</NAME2>
    <ILNNR>2121211545</ILNNR>
    </E1EDKA1><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>002</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDP01><POSEX>45</POSEX>
    <E1EDP19 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <IDTNR>00000000002150059</IDTNR>
    <KTEXT>Reddy</KTEXT>
    </E1EDP19><E1EDP19>
    <QUALF>003</QUALF>
    <IDTNR>5484218521214</IDTNR>
    </E1EDP19></E1EDP01>
    </IDOC></ORDERS05>
    Regards
    Bhavesh
    PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

  • ALE Configurations in File to IDOC Scenario

    Hi All,
    We are doing File to IDOC Scenario.
    ALE Configurations done:
    R/3 Side:
    1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
    2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
    3. Created partner profile and assigned the ports to the message types.
    4. Created Logical system
    XI side:
    1.  Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
    2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
    <b>3. Unable to load metadata in XI.</b>
    Now we are unable to test the scenario as it provides an error message in MONI as "<b>Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors</b>".
    Also Let me know whether the steps mentioned above are correct for the scenario.
    Regards,
    Nithiyanandam

    Hello,
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP XI towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is #####+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    With Regards,
    Vidya.
    *******Reward with Points if found useful

  • How can I include the Header Information....for a File to IDOC Scenario

    Hi,
    I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that <b>"HEADER Information Missing: Message should Start with EDI_DC40"</b> i.e the Header Information.
      My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
    Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
      Kindly Inform me some Solutions.
    Thanks & Regards
    Somnath

    Hi Suraj,
      Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
      Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
      Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
    Thanks and Regards
    Somnath

  • Problem in executing File to IDoc Scenario in XI

    Hello,
    I am Working in HR Payroll module and new to XI.We are implementing File to IDoc Scenario in XI.When I place the flat file in the application server the file is read but the contents of the flat file is not getting posted to the IDoc.The constant values defined for IDoc in Mapping program is getting posted .I am not able to trace the error.
    kindly help me out in resolving this problem.IF there is any way of debugging the entire process please let me know.
    Thanks & Regards,
    Malathi V.

    hi,
    check this blog to test your mapping,
    /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
    Next, check your INBOUND MESSAGE in SXMB_MONI and check if the content conversion has been perfromed as expected.
    these steps will help you reason out the cause of your problem.
    Regards,
    Bhavesh

  • Idocs with errors added status-56 in file to idoc scenario- how to rectify

    hi ,
    in file to idoc scenario when i m sending the file from ftp server to IS Retail,  file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

    Hi,
    Have you configured the partner profile details? check these steps..
    1. In the receiver system you must configure the partner profile for your sender system in WE20.
    2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
    2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
    <a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
    Regards
    San

  • File to idoc scenario in pi 7.1

    Hi All,
    I am testing file to Idoc scenario.
    I have few queries. I am using PI 7.1
    1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
    So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
    2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
    Please advice how to overcome
    3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
    "EDI: Partner profile inbound not available"
    I checked all the relevent partner prfile configuration is already there"
    I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
    Ram

    Hi Ram,
    There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
    >>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
    If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
    >>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
    No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
    >>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
    Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
    Regards
    Suraj

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • Error values in Idoc Control Records in File to Idoc Scenarios

    Hi All,
       I am posting 2 different types of Idocs in 2 different File-to-Idoc Scenarios. In many cases both these files may get picked at the same time. One is an Orders Idoc and the other one is Shipment Idoc. The Orders Idoc has a control record value in the Sender Partner Fn as 'ZC' while as for Shipment Idoc that value is not passed. The other Sender parameters are passed and are different for both these idocs. But when the files are processed, the value 'ZC' get populated for the Shipment Idoc also. When 100 files are sent with 90 orders and 10 shipments, the shipments get created with 'ZC' partner fn. This is visible in the Call Adapter Pipeline Step under the node IDocOutbound. . I have 2 different Idoc receiver adapters.Can anybody help me out here?
    Thanks,
    Geetha

    Hey,
    >'ZC' while as for Shipment Idoc that value is not passed
    Check whether the Source/ Mapping  populates the 'ZC' , Did you checked Apply Control record in Receiver Adapter for Shipment, What is the name  you have mentioned for the in the SLD -Logical system  for Sender system
    Cheers
    Agasthuri

  • File to Idoc Scenario using third party systems

    hi,
    Working with a File to Idoc Scenario. Been able to successfully define everything in IR / ID. However when I go to BD87 (reciever system) and see the status of Idoc processed - getting the error code 51 "Function Module Not Allowed: <Function Name>" . What could be the reason for this???
    Have defined partner profiles in WE20 of type LS and also specified an inbound paramter in the post processing tab for partner profile. Are there any other settings I need to take care of to avoid getting that error.

    Hi
    I am giving u all the steps whioch are required for
    <b>File to IDoc</b> Scenario
    SM59-  Create RFC destination
    IDX1-  Create a IDXPORT in idx1
    IDX2-3.     Import metadata of IDoc’s in idx2
    Bus. service adapter specific Identifiers-->Logical sys name
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    SE16-Table name->LFA1 to check vendor has been created
    Check have u followed all the steps.
    Regards
    Arpit Seth

  • File to IDoc Scenario exception handling

    I have configured Time bound File to IDoc scenario with processing mode in Sender adapter as 'Delete'. And it is running perfectly. I am trying to add additional functionality to the scenario, i.e.,if a file does not exist on the ftp server, a mail should be sent to a recipient.
    May be using Java proxy is not appropriate, as poll interval does not be accounted in Java Proxy and file server should be having Java runtime.
    Please can any one suggest, how this can be acheived?
    Regards,
    Suraj Kumar

    Hi Bhavesh,
    What you have understood is correct?
    Any way, I will come out in more detail.
    My Ftp server: //yhsap/xi
    File: xi_for_upload.txt
    Sender Adapter: File Adapter using content conversion with processing mode as 'Delete' and poll interval is 600sec.
    Simple Mapping is achieved.
    Receiver Adapter: IDoc Adapter.
    So, if file is not available in Source system, send mail to [email protected]
    Can you suggest a suitable solution?
    VasanthaKumar: After adding wait step in BPM, can you please illustrate me how to ping the ftp server and how to read whether file is there? Can you please explain in more detail.
    Thanks & Regards,
    Suraj Kumar

  • Problem with File to IDOC scenario

    Hello,
    I try to implement our first scenario to IDOC.
    In TOC SXMB_MONI I have to errors
    1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
    2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
    Any idea how I can solve this problems?
    Elad

    HI,
    I think u have not done the configuration at the R3 end....
    Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • Needed urgent clarification on FILE TO IDOC scenario

    Hi Experts,
                      I need urgent clarification on FILE TO IDOC scenario plz clarify it
    1.In FILE TO IDOC scenario after creation of RFC dest ,performing steps in IDX1&IDX2
    what configurations to be done on target system?
    2.In some blogs it is given that steps should be done in RFC dest,we21,we20  .
    But is it mandatory to do so RFC dest and WE21 steps [OR] directly can we configure partner profile in WE20?
    3.on integ server IDX2 has to be done (or) is it optional for FILE TO IDOC scenario?
    Too many to answer plz clarify good explanations will be rewarded.
                                                                                    Regards,
                                                                                    Vinod.

    Hi,
    Please follow the below process for configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Pre-requisites for Outbound IDoc from R/3 to PI:
    Configurations required in R/3:
    Maintain Logical System (SALE)
    Define RFC Destination (SM59) which points to PI system
    Maintain Port (WE21)
    Maintain partner profile. (WE20):
    Maintain Distribution Model (BD64):
    DO let me know if you need more information
    Thanks and Regards,
    Chirag Gohil.

  • Error while doing a File to IDOC scenario

    Hi Experts,
    I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
    I have checked with all the configurations and couldnt find where it went wrong.
    Kindly help me in this regard.
    Thanks.

    Hi
    Check the inbound parameter and the process code.
    To find Process code for IDoc use Tcode WE42.
    ALE idoc trouble shooting use
    Troubleshooting of ALE Process
    look also this configuration
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Maybe you are looking for

  • HT4968 How can I take a shared calendar and recreate it using my personal ical rather than having to share?

    Here's the deal.  I stepped into an administrative position last fall and began building an entire calender schedule for our summer 2014 program.  I put a lot of work into building two months, however I have only just realized that the apple ID is fo

  • Deployment of class file in oracle 10g Application Server

    Hi, I have a class file import java.io.*; import javax.servlet.*; import javax.servlet.http.*; public class HelloWorld extends HttpServlet { public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { res

  • Can't create a file, Can't Publish to iWeb

    When I try to publish some changes to my site, I get a Publish Error that says: Can't create the file "droppedImage.png." The disk may be damaged or full, or you may not have sufficient access privileges. My iDisk doesn't seem otherwise to be damaged

  • OIF with external IdP (Shibboleth) - certificate issue

    Hi, We are in the process of setting up Oracle Identify Federation(as SP) with an external IdP (shibboleth) for SSO, We got the meta data from the IdP and setup the Identify Provider in OIF with IdP meta data, The IdP got self sign certificate, When

  • Programming assistance

    Hi all, I need some help hopefully before Sun evening... I have to modify my Inventory program to have an Add, Delete and a search button simple enough.. Well Im new to Java programming and have been limping my way along from day one I have a C+ and