Idoc Output Control Problem, Want to prevent IDoc creation

I want to prevent an IDoc from being simply created if a certain condition is not met. However if I set the sy-subrc = 4 and exit from the routine it still goes ahead and creates an outbound IDoc. Here is the code from the routine. I have debugged into the code and it DOES get executed when i change order info header from VA02. I have already debugged to make sure that the following piece of code does get executed and the SY-SUBRC does get set to 4 before the execution exits the Form given below. Please suggest what I m doing wrong?
FORM KOBED_601.
If the document is incomplete (Price not on list)then no o/p is created
IF KOMKBV1-UVPRS NE c_c.
SY-SUBRC = 4.
EXIT. "(also tried using RETURN)
endif.
*} INSERT
ENDFORM.
FORM KOBEV_601.
*{ INSERT ECDK903987 1
Falls Verkaufsbeleg vollständig ist, soll Nachricht erzeugt werden
If the sales document is complete, then the output should be created.
*} INSERT
ENDFORM.

Wait. I think I have figured out part of the problem. The problem is that both the VOFM routine that I have written 603 is executed followed by standard SAP VOFM routine 002. Though I checked that the configuration for the output type that I m using ZBAO has the right VOFM routine number 603 set, it still does execute the Standard SAP VOFM routine 002 after executing my routine, which seems to override the SY-SUBRC = 4 that I have set. If I set the SY-SUBRC = 4 in debug mode in routine 002 then the IDoc doesnt get created.
Is there a way I can prevent it from executing the standard SAP VOFM routine 002?

Similar Messages

  • IDoc output type not getting configured in IDoc-File scenario

    Hello
    I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
    1] Created output type
    2] Created partner function as EDI LS for this output type
    3] Configured RSNASTED as Processing Routines for output type
    4] Included this output type in the Header output procedure
    5] Configured XI system as the partner in partner profile with appropriate Message control
    Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
    I checked in SPRO but could not find such flag.
    Does anyone had came across such output type configuration.
    Thanks in advance.
    I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
    Regards
    Rajeev

    Hi,
    Please check the following
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    Copy NEU to ZNEU or YNEU
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
    G.Ganesh Kumar

  • Restrict IDOC processing through output control

    Hi,
    We want to send one idoc (ORDERS) only to a particular logical system while creating purchase order through output control
    Can anybody explain how we can restrict sending idoc to only one logical system?
    Thanks in advance

    You can control output processing for shipments(VT01n docs) based on overall status by maintaining Activity profiles for shipment types.
    SPRO: Logistics execution->Transportation->Shipments->Define and assign activity profiles.
    Type a variant name in the status field you want to process edi for the shipment type and click on maintain.
    Select shipment checkbox in the 'Print after save' box and enter the EDI output type.
    Regards
    Sridhar

  • Purchase Order IDoc Output Error

    I'm having a problem creating IDoc output for a vender PO.  I have the vender setup in WE20 with outbound parameters:
    Partn.funct. VN
    Message Type: ORDERS
    Basic Type: ORDERS05
    Application: EF
    Message Type: NEU
    Process Code: ME10
    In the PO Output conditions I'm using the Doc.type/Purch.Org/CoCode/Vender key. 
    When I create a PO and go in to the message screen Output type NEU appears, Medium: EDI, PartFunc: VN, Partner: vend#, Lang: EN  <b>When I try and save I receive an error message indicating that I can not enter a partner function for output NEU.</b> 
    I think I have everything configured correctly.  Any suggestions on how to resolve would be appreciated.
    Thanks!

    Check the configuration of Message Control using transaction NACE.
    Also check the Condition Records you have created for the output type.
    For details refer to
    http://help.sap.com/saphelp_erp2005/helpdata/en/c8/19887b43b111d1896f0000e8322d00/frameset.htm
    Also, try to create a test idoc using the transaction WE19.
    Hope this helps.

  • Problem with non-updated idocs

    Hi,
    we have a problem after upgrading from 3.5 to 7.0. Lots of extractors end
    in an error-message concerning non-updated idocs. Every day several
    extractors have this problem. This are not always the same extractors. As
    a result we must repair many extractions manually.
    I know the procedure of how to repair, but I want te know how I can prevent
    extractors from running into this problem in the first place.
    Any suggestions?
    This is the problem-message that we get...
    Non-updated Idocs found in Source System
    Diagnosis
    IDocs were found in the ALE inbox for Source System that are not updated.
    Processing is overdue.
    Error correction:
    Attempt to process the IDocs manually. You can process the IDocs
    manually using the Wizard or by selecting the IDocs with incorrect
    status and processing them manually.

    It has been happening on our env as well (BI 7.0 SP 12), time to time one load or the other gets into this problem and it waits yellow for few hrs before turning red.
    I can correct the IDOC and move on or run the load again it works fine.. but the process chain gets held up not going to the next stage for hrs..
    any resolution on your problem..
    thanks
    Mayil

  • R/3 to XI manually IDOC sending and problem:

    <u><b>R/3 to XI manually IDOC sending and problem:</b></u>
    I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    I check XI (sxmb_moni) but there is nomessage there.
    <b>Problem 1:</b> I don't want R/3 ask me UID and password for XI access
    <b>Problem 2:</b> I want to see message in XI (sxmb_moni)
    Thanks

    Hi Cemil,
    >>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    check the RFC destination from R3 to XI (SM59)
    you will find the right one from your port (We21)
    you can also check step by step procedures
    for IDOC - XI in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • JDBC to IDOC scenario - Mapping problem with E1FIBSEG

    Hi friends,
    I have problem when generate multiple Idocs (FIDCC1) an multiple positions based on an External Definition for a SQL Server table. I have selected all fields from this table from a SELECT into the JDBC configuration.
    My mapping is like this:
    DWCAJA.ResultSet  1..1
         IDOC.
    Thats ok and generate n IDOCs by every change of PK.
    The problem is when i want to map positions because i dont have any field in source message to identify the number of positions to map with E1FISEG.
    If I have two differents Pks and n rows, the result of testing is as folow:
    FIDCC1
      IDOC
         E1FIKPF
             E1FISEG
             E1FISEG
      IDOC
            E1FIKPF
    I cant obtain n BSEG segments according PK. I've mapped and all fields of row segment but those are created in the first IDOC node only,
    Any suggestions?
    Regards,
    Pablo.-

    Important: Primary key : DWSucCod + DWCajSec
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100001</DWCtaConCo>
      <DWRecImp>100</DWRecImp>
      </row>
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 100
         E1FISEG
              hkont :1100002
             dmbtr : 200
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    - <row>
      <DWSucCod>12</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100003</DWCtaConCo>
      <DWRecImp>300</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100002
             dmbtr : 200
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 300
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100001</DWCtaConCo>
      <DWRecImp>100</DWRecImp>
      </row>
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    - <row>
      <DWSucCod>12</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100003</DWCtaConCo>
      <DWRecImp>300</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 100
         E1FISEG
             hkont :1100002
             dmbtr : 200
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100003
             dmbtr : 300

  • Idoc to file problem.......... IDOC lost

    i have a idoc to file problem,
    the idoc is sent from R/3 to XI,
    the problem is IDOC is sent from R/3,
    it didnt reach to XI.....
    i have checked.......we05 in R/3, it gives a status 3,
    then i checked SM58 in R/3, it shows nothing,
    when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
    pls help, where can i trace the idoc.....
    pls help

    Hi sudeer,
    Did You Check It In WE19.(Test Tool For Idoc Processing)
    If Not Do The Following Steps:
    <u><b>Step1:</b></u>
      >>      Give Your Existing Idoc Number.
    <u><b>Step 2:</b></u>
      >>      Basic Type is Your Message type.
            Ex: MATMAS05 or CREMAS05.
    <u><b>Step 3:</b></u>
      >>      In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
      >>      You Should Fill  Your Mapped Entries In Data Structure of EDIDC.
      >>      So that Those Fields Gets Framed as Segments.
    <u><b>Step 4:</b></u>
      >>      After Doing It goto  Menu Bar and Click Idoc And Goto  Edit Control Record.
    <u><b>Step 5:</b></u>
      >>      Now You Give Your Sender And Receiver Port Number Along With Your 
            Logical System And Message Type again its Your MATMAS05  or
           CREMAS05 .
    <u><b>Step 6:</b></u>
      >>      After Doing It Click Standard Outbound Processing.
    <u><b>Step 7:</b></u>
      >>      It Will Say what Happened To your Idoc.
    <u><b>Step 8:</b></u>
      >>     It Is For Sure That if This Processing Fails It Wont Go To XI..
    Regards,
    Dhayanandh .S
    Dont forget To Provide Points If Found Helpful...
    Message was edited by:
            DHAYANANDH SIVASANKARAN

  • IDX2 Communication Error - Problem with only 1 IDoc Type

    Trying to import metadata via IDX2.  All IDoc types have imported succesfully, except DELVRY03. 
    I get a message saying "Communication Error" Message #: IDOC_METADATA407.
    I have tried DELVRY01 and it imports fine.  But, DELVRY02 and DELVRY03 both give the "Communication Error" messages.
    Any ideas why this one particular type will not import?  Settings/logon have not changed.
    Thanks

    FYI, Update... I think I may be on to something here...
    All checks in WE30 return okay.
    I debugged the IDX2 program, error is occuring in the 'IDOCTYPE_READ_COMPLETE' function call.  It is returning with message: 'Structure of segment E1EDD10 is unknown'.  Did search on this in OSS and found note #491264 -- Output of IDoc DELVRY02/DELVRY03 does not work
    Symptom
    You want to display IDoc DELVRYnn (nn = 02,03), SHPMNTnn (nn = 03,04,05), or PLNSHPnn (nn = 01) via the IDoc documentation transactions. The sys
    Comment: This relates only to the display of the IDOC structure. The IDocs work for the data exchange.
    Still working through the note to see if this will fix the issue, but I just tried to import in SHPMNT03 and I get the same error.
    Thanks.

  • Want to triggered IDOC, when PO saved.

    Hello,
           Want to triggered IDOC, when PO get created.
           All configuration has been done, IDOC triggered when PO is released. But, I want to triggered IDOC when PO get create.
           Can any one please tell me the proper steps to configured output type??
       Thanks in advance.

    We can use standard output type 'NEU'  If you want to create new one. Simply copy the standard one 'NEU'  as 'ZNEU' (example) and modify if you need any changes. This is the easiest method creating custom output type. (Generally functional consultanats do create Output types ).
    To do this , Goto tcode 'NACE' , select  Application -'EF' and click on 'Output types' button. Then you can see different Output types for Application 'EF'.   in chnage mode - select 'NEU' and from menu bar - Edit -> Copy As.  new you change the NEU to 'ZNEU'  and on the same screen select a tab 'Default Values'.  
    here you can set
    Dispatch time   -->    '4-Send immediately (When saving the application)  
    Transmission Medium  --> 6 (EDI ) or A (ALE ).
    partner function  - choose from F4.
    and save it.
    (Note: we generally set dispatch to  '4 ', then Idoc will be generated immediately.  If you set '1 ' , you need to run RSNAST00 program after you create PO,then only Idoc will be created status 30.)
    Testing Manually using output type.
    Now test this by creating PO. Goto ME21n , after giving all the inputs b4 saving it, from menubar - GOTO->Messages
    Here you can give  outputtype  either NEU or the custom one 'ZNEU' ,  medium 6 (EDI), patner function, and partner no ,
    and click on  further data select transission medium 4 . go back to main screen and save it.  After creating PO again goto in display mode goto-messages check whether the any green light icon shown on the output. is yes, double click on it , you can see IDOC no also.
    Now do settings in WE20 assign this oytput type . I think this you know it..

  • IDOC-XI scenario problem

    I have a IDOC - XI scenario,
    where IDOC is generating from a R/3,
    the problem is, an IDOC was sent from R/3, but has not reached XI,
    in R/3, i have seen in WE05, there i see this IDOC having status '03',
    and, also in SM58, there i no error corresponding to this IDOC,
    but in XI, in IDX5, i cant see that IDOC,
    where the problem lies?

    Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
    ) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
    2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
    Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
    So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
    Please see the below links ,
    /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • XI 2.0 problem: scenario xml - xi - idoc

    Hi!
    my scenario is xml -> xi -> idoc1, idoc2.
    when the interface start, if I call SXMB_MONI I see that idoc1 is correct; for idoc2 the system generate an error: idoc.adapter.generic, "MSGGUID 587E007DA385D54697B3F02220A78987: Tag ORDERHEADER found instead of tag IDOC BEGIN=.</"
    Can you help me to undestand the problem?
    10 points for you!
    Thanks,
    Gianluca

    Bruer,
    I use an interface mapping between xml (imported from SAP BBPCRM 4.0, data type OrderCreateOrChangeVendorOut) and Idoc custom. My mapping is graphical mapping without java class or xsl.
    My scenario work with one xml and two different idocs. Today I have added a second idoc. The problem is that the first one work correctly, for the new idoc generate an error for idoc_adapter.generic.
    The jar file for the mapping is mandatory for my new idoc?
    Thans you very mutch,
    Gianluca

  • Hi In ALE ,IDOC  HOW  CONTROL DATA IS TRANSFERRED

    Hi Experts,
                          Hi In ALE ,IDOC  HOW  CONTROL DATA IS TRANSFERRED .
    Thanks & Regards
    Bhaskar Rao.M

    Hi Bhaskar Rao,
    Good Check out the following documentation.
    /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1230385,00.html
    Some good links on ALE/IDOC
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    Please check this online document for ALE and IDoc.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Also check this links for additional information.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    Good Luck and thanks
    AK

  • Problem in processing incoming IDOC

    Hi All,
    I have a problem while processing Incoming IDOC in the system.
    While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
    When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
    (Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
    Expecting your help in this regard.
    Regards
    Nagarajan N

    Hi
    You can use WE19 to debug the Idoc FM.
    Check this link if it is helpful:
    Debugging Idocs
    Regards
    Neha

  • 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

Maybe you are looking for

  • How can i sort a list ?

    Hallo! Some days ago, i made a small programm, which is able to read *.txt files and list it out! Now i am trying to sort this list ( by age or name). I think it�s possible with the "compareTo" Methode. But i don�t no how? Please give me some tips! T

  • How to clear import queue?

    Hi All, we are using WebAS 6.20 and we have a huge number of transports in our landscape. The import queue of our systems therefore is quite big (several thousand transports) and slow. I found an option "Delete Imported Requests". But most of the tra

  • Whats the Maximum Ram my macbook can take?

    Hi I have A macbook pro 1.83 GHZ (yonah) Can it go further than the 2GB specified by apple? Many thanks If not what causes it not to?

  • Editing referenced images

    Is it possible to edit images that are referenced and not online at the time of the editing? Is there a selection somewhere that will allow this to happen? Currently, if my image is offline, I do not get a histogram and I don't think I can edit in an

  • I downloaded the new iOS6 and now I can not connect with the iTune or App stores. My wi-fi works.

    I downloaded the new iOS6 update to my 4s and now I can not connect with the iTune or App store. How do I fix it? My Wi-Fi works fine.