IDOC and its types

sir,
can anybody explain about IDOC how it creeats and use in SAP and what are the types of IDOC. plz, explain with proper example.

hi,
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
types of idoc:
There are some standard idocs available in SAP like MATMAS,CREMAS etc..If the IDoc types (basic types) supplied with the standard SAP System do not meet our requirements then we can define our own IDoc types.
Before you define a new IDoc type, you should first check whether the basic types can be made to meet your requirements. You can display a list of the basic types and their meaning using the documentation tools in the IDoc Interface.

Similar Messages

  • Diff bet IDOC and Message Types.

    What are the difference between IDOC and Message types.
    Diff between MATMAS01 ,MATMAS02 and MATMAS03

    IDOCs:
    - IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes  that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
    Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between  two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment  is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
    -Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type. 
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
    <u><b>IDOC TYPE IS AN INSTANCE OF IDOC</b></u>
    Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not   a   local object type , it is transportable.
    For different applicatons we have different MESSAGETYPE.
    example:
    <u>APPLICATION</u>                <u>  MESSAGETYPE</u>
    MATERIAL MASTER                       MATMAS
    VENDOR MASTER                          CREMAS
    CUSTOMER MASTER                      DEBMAS
    MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES  ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
    REWARD ME IF THIS IS HELPFUL

  • ISU Billing/Invoicing IDOCS and Message Type

    Hi,
    Could any body provide me the list of IDOCS and Message types for Billing and Invocing Module. I was unable find the list across web.

    To get the idoc list , u should go to the transaction WE02, and give the search parameter as the  basic type of the above said message types..

  • Idoc and message type not getting replicated in the receiver system

    Hi
    i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
    However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

    Hi Tarang,
    at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
    Just look at standard IDocs and do as they do.
    Regards,
    Clemens

  • Can I know abt tickets and its types?

    Can I knwo abt tickets and different types of tickets , how much time will need to rectify a bug?>

    Hi Krishan,
          Normally Tickets are classified into 3
        1) CRITICAL or HIGH - U need to solve this within 8 hrs or may be less than that
        2) MEDIUM- U need to solve this within a couple of days
        3) LOW- U will get time of min 4 days for this
      Reward Points if Useful
      regards
      Avi....

  • Proforma Invoice - IDoc and message type

    Hi,
    The requirement is to send proforma invoice to legacy system upon creation. We use PI as middleware.
    Is it possible to send to proforma invoice data using IDoc?
    If IDoc then we have to use message control? Am i right?
    What is the process code and what is the basic IDoc type/message type to be used for this?
    Thanks for any help.
    Cheers,
    Srini

    Hi Srinivasan
    Basic type           INVOIC01  Invoice/Billing document
    Message type                   INVOIC     Invoice / Billing document
    Process code         SD09
    Description          INVOIC: Invoice
    Function module      IDOC_OUTPUT_INVOIC
    best of lucks and Happy Diwali
    Nandu

  • IDOC and Basic Type

    Hi Experts,
    I have a basic type that I will use in my IDOC with no process codes(attached FM) that will create a document (e.g. orders, deliveries)... and I have found out a BAPI that I can use in creating the document.. the question is.. do I still need to  CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND' after calling the BAPI to create the document?
    Thanks!
    Nosaj

    Hi,
    Thanks. To clarify.. first I will receive an IDOC coming from XI this IDOC containes the planned orderse that I will create in SAP.
    Question: Can one IDOC contains a lot of planned orders to be created? Meaning that I have created a copy of segment E1PLAFL because this segment can only acquire a maximum of 1 data record... so i copy it and customize it to acquire more than 1 data records.....?
    Then the Basic Type:  LOIPLO01 does not have a functionaly of creating planned orders.. so I will use a BAPI in creating the planned orders....
    Question: Since I will be using a BAPI to create the IDOC.. do I still need to call the function module ive said (WRITEIDOC)?

  • How to know a table's column name and its types

    if there has one table called "myEmp" stored in my database, it uses to hold employees' information. when a newcomer is hired, the HR will use a register page to register his/her information. for the flexible purpose, i couldn't know how many columns in this table, since it may be added two columns or deleted one column in one day, all i should do is show all fields in the register page and get all data to insert into this table.
    so, how can i know one table's structure in java? i know there has a method in DatabaseMetadata class: getTables(catalog, schema, tablename, tabletype), it's return is resultset . i wrote a code below:
    DatabaseMetaData md = conn.getMetaData();
    ResultSet md.getTables(null, null, tablename, types);
    i set catalog and schema both are null since i don't know what else can i set?
    the ResultSet doesn't contain the information i want.
    is there anyone can tell me where i am wrong and the right method? thanx a lot!
    sincerely
    Jasmine

    use ResultSetMetaData to get Column names

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

  • Reg. checkbox by group and simple types

    Hi,
    I have checkbox by group UI elemnet.
    I have binded the text property of the checkbox by group to a context attribute and its type property is selected from a simple type.
    In the view layout on NWDS its showing the label names which i hav given in the simple type. but when i deploy it and run it in browser its just showing only one check box. its not showing the label names.
    how to get the label names, using simple types. i,m able to get it using code.
    how to get it by simpletype???
    thanks, suresh

    hi,
    in case of check boxes, it will not work with
    a simple type
    write code similar to this according to your requirement
    in wdDoModifyVIew();
    if(firstTime){
    String[] names = {"one","two","three"};
    for(int i=0;i<names.length;i++){
    IPrivateCheckView.IXElement nelem =wdContext.nodeX().createXElement();
    wdContext.nodeX().addElement(nelem);
    nelem.setName(names);
    where X is a node ,
    Name is attribute under node X
    of type string
    bind the texts property of the check box group to the Node X
    Regards,
    Satya.
    Edited by: Satya on Nov 7, 2008 8:34 AM

  • Automatic configuration of NEU output types for PO Vendor and its partners

    Hi All,
    I have requirement where I need need to send IDOC to PO Vendor and its partners at the same time when PO is created and changed. I need to get NEU output types for Vendor and Partners in messages automatically. Can any one guide me how to get this functionality. Please help me with step by step process. I am new to MM.
    Thanks,
    Ravi

    To attach output type to purchase order :
    Go to NACE , Select Application EF ( Purchase Order)  and Click on Condition Records button.
    In a POP UP window double click NEU  and then select the right Key Combination and maintain right transmission medium and output devide details.

  • IDOC question on Message type and Basic Type - Partner Profile

    Hi all,
    I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
    My question is about the setup of Partner Profile creation (WE20).
    When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
    Questions:
    1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables.  I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
    2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
    Thanks.
    tuff

    Tuff,
    Below are my thoughts,
    There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
    OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
    Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order -  ORDRSP.
    And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
    Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
    In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
    2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
    Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
    Regards,
    Chen

  • Creating Idoc and sending it to its own...

    Hello All,
    The functional design specified that an inbound function module needs to be created to process a custom IDOC, let's say ZMMDLRTL, and using the data from the segments from this basic type ZMMDLRTL, I need to create another IDOC of basic type PORDCR101 to create a PO. This PO IDOC would then have to be posted to the same system where the inbound function module that would process the ZMMDLRTL IDOC. So this is just like creating an IDOC and sending it to yourself right?
    I used the function module MASTER_IDOC_DISTRIBUTE to create the PORDCR101 Idoc and sends it to itself. But now I am getting an error status 20, which is "Receive of IDOC is its own logical system". I just need some inputs on this.
    Thanks,
    Kristine

    Hi!
    In two words - to avoid this error you have to send PORDCR101 to another logical system pointing to the same client and make corresponding settings in distribution model (as you use MASTER_IDOC_DISTRIBUTE).
    Proceed as follows:
    1. Create a "dummy" logical system name, say LOGSYSD. This dummy logical system will serve as the receiver system in the distribution model.
    2. Using SM59 create RFC-destination LOGSYSD for the dummy logical system. The RFC-destination addresses the same client.
    3. Create a distribution view in BD64 with your "real" logical system for client as the sender and LOGSYSD as the receiver for your message type.
    4. Generate partner profiles for distribution model using BD82.
    5. Using WE20 create inbound parameters for your message type for <b>"real"</b> logical system.
    Hope it helps.
    Regards,
    Maxim.

  • How to link idoc with its corresponding documents and vice versa...

    Hello Experts,
    What are the tables, transactions, etc that can link a certain document(e.g. PO, GR, invoice) to its IDoc and
    vice versa.
    Thank you guys and take care!

    Hi,
    The Message Control parameters from the partner profiles must also match the corresponding
    fields in the output type. These parameters include:
    u2212 Application
    u2212 Partner
    u2212 Partner function
    u2212 Output type
    Tcode  - NACE  (Output Control)
    Tables - SRRELROLES  (Object Relationship Service: Roles)
    Message Control is a mechanism by which documents are output based on certain conditions.
    1) The application id, communication structure and o/p determination procedure are responsible for triggering IDocs corresponding to a particular application document. For this to happen message control settings have to be done.
    2) Message Control u2013 also referred to as output control or conditioning technique u2013 is a cross-application component used as a service program in several areas. The basic concept behind Message control is to generate and manage outputs from an application and control their timings and medium of exchange.
    3) Message control settings can be done via transaction NACE or via transaction NACO.
    4) Starting point in message control in the u201COutput Determination Procedureu201D (Procedure within NACE txn.). Depending upon the configuration setting in SPRO this procedure is determined.
    A procedure defines a set of possible outputs for an application. We can define several procedures for an application, but only one can be configured as
    active (i.e. for a particular transaction document within an application only one procedure will be determined based on configuration settings).
    Eg->
    a) For Delivery (txn. VL01NO) the document type setting in configuration (SPRO -> Logistics Execution -> Shipping -> Deliveries -> Define Delivery types) determines the procedure.
    So whenever we save a document of particular application (of particular application id) and of particular document type, the particular o/p determination procedure is triggered.
    b) For sales, SPRO -> Sales and Distribution -> Basic Functions -> Output Control -> Output Determination -> Output Determination Using the Condition Technique.
    5) In the transaction NACE we can see that corresponding to application id (say u2018V2u2019 (shipping)) various procedures are defined:
    6) Before making the entry of the output type corresponding to a particular procedure, we have to define it with its attributes.
    The output type defines the characteristics and attributes of the output itself. We can access the output types on transaction NACE by selecting an application and clicking the Output type button.
    7) Access sequence defines a sequence in which business rules are checked for proposing an output type. It has following attributes:
    - A set of business rules or conditions.
    - A sequence in which the rules or conditions are checked.
    - A requirement that checks for business rules using ABAP programs.
    - An exclusive or inclusive strategy.
    We can access the access sequences on transaction NACE by selecting an application and clicking the Access Sequences button.
    Business rule 1 is based on SOrg./Distrib.Ch/Division/Customer. Business rule 2 is based on Sales Organization/Customer Number. Each business rule is, effectively, a set of fields defined in a condition table.
    8) Condition table specifies the key fields for a business rule. Hence for Business rule 1 the key is Sales Org., Distribution Channel, Division and Customer.
    9) Condition records are inserted in the condition table. The transaction is evaluated with the key (of the condition table based on business rule) and if the transactional data matches with the condition record the output is proposed.
    Condition records are defined at last.
    10) Several programs and tables are part of Message Control. For EDI, the following tables and programs will frequently be dealt with:
    *NAST - This table has an entry for the processing program used for an output type.
    *TNAPR - This table has an entry for the processing program used for an output type.
    *RSNAST00 - This program is used to process entries in the NAST table.
    *RSNASTED - This processing program exists for each output medium. ALE_PROCESSING is the routine in the RSNASTED program to process ALE outputs.
    11) Final overview of the components used in Message control to propose outputs.
    12) After doing all the settings for message control, the partner profile setting for this ALE scenario needs to be accomplished. We need to add the following entry to the outbound parameters of the partner profile:
    13) One important question that arises at this juncture is, how is the partner profile determined from the output type is case of ALE?
    This is information is stored in table EDP12 (Partner Profile: Outbound with Message Control). Based on the Partner type of receiver (RCVPRT), output type (KSCHL) and Application for message conditions - without value table (KAPPL), the Partner number of receiver (RCVPRN), Outbound process code(EVCODA), Message type (MESTYP) and other related values are determined.
    Regards
    Pugazhenthi.P

  • Hello sir        i have mac os x lion and A fter upgrading to Lion  i can't instal the face time app its type ( FaceTime can't be installed on "Mac" because the version of Mac OS X is too new. )   can anyone help me please .   notes : on snow leopard the

    hello sir
           i have mac os x lion and A
    fter upgrading to Lion  i can't instal the face time app its type ( FaceTime can’t be installed on “Mac” because the version of Mac OS X is too new. )   can anyone help me please .
    notes : on snow leopard the face time was work normally but i delete it the app i thought it will work after i reinstall it

    Lion comes with FaceTime. Look in your dock or in the Applications folder.

Maybe you are looking for

  • I need BW 7.0 doc where can i find can u help

    what are the main differences between 3.5 and 7.0

  • I'm having problems with my Serial Number, can anyone help?

    Hey guys. Alright, so a few weeks ago I bought a Wacom Bamboo Capture tablet, and it comes with a copy of Adobe Photoshop Elements 8.0 Now, I installed it previously and it worked perfectly. Then, all of a sudden, I go to boot it up, and I'm asked fo

  • I NEED TO TALK WITH SOMEBODY OF SKYPE......!

    WHAT IS THIS.......I NEED TO TALK WITH SOMEBODY THAT WORKS IN SKYPE COMPANY......I AM TRYING AND TRYING TO CALL CHILE AND THE CALLS DONT GO THROUGH....????????  WHAT'S GOING ON???

  • Can't adjust Bass and Treble from windows Mixer (SB Audi

    Hello,?i have Sound Blaster Audigy (5.)i installed drivers for it, but i cannot adjust Bass and Treble from ordinary W?ndows Sound Mixer, because sliders are passi've (disabled)?what is the solution?tahnk you. my system is:windows xp prof. edition +

  • Registering Listener

    ===Oracle 10gR2 RAC - Nodes-4 - Redhat Linux AS4=== Hi All, $ crs_stat -t | grep LISTENER NAME=ora.rcorprod01.LISTENER_RCORPROD01.lsnr NAME=ora.rcorprod01.LISTENER_RCORPROD01_DB2.lsnr NAME=ora.rcorprod01.LISTENER_RCORPROD01_DB3.lsnr NAME=ora.rcorprod