IDOCS and Tablestructure

Hi Experts
Is it possible to receive IDOCS and tables  at a time in a program using sapidoc3 and sapjco3 ?.
If possible how to handle those pls explain clearly.
Regards
Sridevi

Hi Sridevi,
Since your requirements are not clear, it's hard to answer your question. In general I'd say though the answer is no, because the simplified API the SAP JCo IDoc library provides (especially for sending or receiving IDocs) does not account for getting/sending other data at the same time.
The part that's unclear to me is whether you're talking about a JCo client (data is pulled from SAP by the external Java client) or a server (data is pushed out from SAP to the external JCo server). In either way the IDoc sent from SAP is (unless you use XML) most likely already in the form of tables (i.e. EDIDC and EDIDD or the more specific structures depending on SAP version). E.g. you can take a look at function module IDOC_INBOUND_ASYNCHRONOUS and there you can see that the IDoc basically is specified as data in internal tables. The JCo IDoc library provides a layer around that though, which hides this, but also restricts you in what you can do.
If you have to combine the data in one RFC call (not sure if this really is a requirement for you), then probably your only chance for using JCo IDoc library is to encode the table data in your IDoc (i.e. add custom segments like Z1VBAK, Z1VBEP, etc. and store the data within the IDoc).
Best wishes, harald

Similar Messages

  • What is the diffrence btween IDOC and BDOC?

    what is the diffrence btween IDOC and BDOC?

    Hi,
    In short Idoc is an Intermediate Document and Bdoc is an Business Document.
    Data can Be Transferd from Sap to Non Sap using Idoc where as we can transfer
    data between sap to sap in Bdoc.
    IDoc
    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions
    BDOC
    BDoc is a business document which is technically similar to an IDoc. BDocs are used to communicate data between two systems.
    BDocs come in two types. One is the message BDoc (MBDoc) and the second is the Synchronizing BDoc (SBDoc).
    MBDoc is used for replicating the data between SAP CRM and SAP R/3
    SBDoc is used for replication and realignment between SAP CRM and mobile clients
    som times SAP will be integrated with som other third party systems
    ex SAP with BAAN here we should comunicate one to other systems
    here we can integrate using EDI technology in this the formate of data will be in I DOCS EX :EDI is a bridge between 2 systems .I doc is a container to transfer data from one sys to other
    this Idocs we can use in ALE technology also
    BDoc is called Business Document,
    BDoc represents data in a structural format. This sturctural architecture is use to either input data to system or send data to other system.
    BDocs are data carrier that can either collected in system(Inbound) or can be send out of system(Outbound)
    Please refer following link:
    http://help.sap.com/saphelp_crm40sr1/helpdata/en/ec/8d7e3a7e760b55e10000000a114084/content.htm
    Thanks,
    Medha.

  • 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

  • DIFFERENCE B/W  IDOC  AND RFC   ADAPTERS

    HI FRIENDS,
    WHAT IS THE  DIFFERENCE B/W   IDOC  AND  RFC   ADAPTERS..? AND WHICH ONE IS
    PREFERABLE  TO USE    IN TRANSFERING DATA FROM THIRD-PARTY SYSTEM TO  SAP.?
    REGARDS,
    RAMAKRISHNA.

    Hi
    These links will help you to understand :
    http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
    Please dont forget to reward with points.
    Edited by: Dheeraj Kumar on Mar 3, 2008 2:59 PM

  • How to trigger automatically an IDOC and RFC from SAP R/3 system?

    Hi ,
    lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger  on timely basis(schedules)
    1)standard IDOCs and BAPIs?
    2)customized Idocs and Customized Bapis?
    3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
    please explain ,
    thank you very much for your help.
    regards,
    Babu

    sorryfor the late reply, I was busy with my work.thank you for your posts.
    so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
    And I think we use RSNASTED if we have on recieving side right?
    <b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
    REPORT Z_SEND_DATA_TO_XI.
    parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
    <<your other variable declaration and ABAP Code here>>
    call function 'ZXI_SEND_DATA'
    in background task
    destination dest
    exporting
    Name = John
    City = Smith. (The values to pass to XI)
    commit work.
    <<Any Write statements or sy-subrc statements here>>
    6) Save and Activate your ABAP program.
    6) After all these steps, execute your ABAP Program to send the data to file via XI.

  • IDoc and creation of sales order!!

    Hi,
    I need to create sales order using IDoc and the file will have multiple line items for sales order and it has to be dynamic, so whats the best way to do this?
    Regards
    Gunjan

    Hi
    Check for the related IDOC types in EDBAS table and for related Message Types
    in table EDMSG. take relavent one for your requirement and use.
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    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
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    Reward points if useful
    Regards
    Anji

  • Tax with the help of idoc and EDI

    Dear gurus,
    how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

    Hi Amit,
         I do not understand how a non-sap system having an idoc adapte?
    Do you mean the non-sap system has the ability to understand the IDOC files?
    If yes, then your scenario is typically a IDOC-to File scenario.
    Read this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
    Regards,
    Ravi

  • PI 7.1 scenario -- File to File , File to IDOC  and IDoc to File Scenario

    Hi All,
    *I have PI 7.0 . I have in that File to File , File to IDOC  and IDoc to File Scenarios*
    File to File -- This scenario is working fine.
    File to IDOC   --  Setting done in PI 7.0 like SM59,  IDXI, IDX2  and in R/3 like SALE (logical system)---  This scenario is working fine.
    IDoc to File  --  Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
    Now I need to move to PI 7.1  -- for File to File , File to IDOC  and IDoc to File Scenarios.
    Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
    If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
    Regards

    >
    Rickkk wrote:
    > Hi,
    >
    > Idoc metadeta is updated through idx2?
    >
    > Regards
    If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
    You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

  • ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

    Hi,
    we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
    Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
    My question is:
    We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
    It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
    Best regards,
    Steven

    Hi Abhishek,
      This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna  maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
    Thanks in advance.
    Regards,
    Arunmozhi.

  • Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

    Hi Experts,
    Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
    What objects i can skip.
    My PI system is 7.3 dual stack.
    I have seen below blogs, still its confusing to me.
    When and how to create an scenario in SAP PI without mapping objects.
    Pass Through Scenario with no Mapping in PI 7.1
    Appreciate your help on this.
    Regards,
    Mohan.

    Hi Mohan
    In pass thru interface you don't need to create any ESR objects, only ID objects are required.
    Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
    Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
    Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
    Regards
    Osman

  • Difference between idoc and rfc

    what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. 
    IDocs are used for asynchronous transactions:  Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. 
    Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions. 
    A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another. 
    IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands. 
    An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
    layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. 
    The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
    RFC
    Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • How to encode XML to Idoc and decode Idoc to XML in business connector?

    Hi all,
    first of all: thanks for all, who are reading and perhaps responding this question!
    Here some facts and my question(s):
    The facts:
    - I have the business connector version 4.6!
    - I'm not working with any SAP Netviewer!
    - I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
    What am i doing and what is working properly:
    - Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
    - gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
    - puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
    !!!So far only getting and putting of the file works!!!
    What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
    CONVERSION FROM XML INTO IDOC AND VICE VERSA
    My question:
    - which services i have to use between getting and putting the files?
    Thanks to all,
    Tamer

    Hi,
    I have the same problem. I do fix it?
    Thanks
    Wilson Xavier
    Brazil

  • Idoc and http adapter

    Idoc and http adapter resides in ABAP stack. So how do we monitor these two adapters ? It wont be visible in RWB ?

    Hi,
    To know the difference i suggest u try to do it by ur self only.
    Login in to Runtime Work bench- component monitoring-Adapter engine-communication channel monitoring- Filter the communication channel with name.
    and click on message id of that channel, it will show u the steps by step log for that channel.
    MONI is used for message monitoring.
    chirag

  • How to convert XML into idocs and post in ECC using PI

    Hello All,
    I want to configure the scenario like this MDM->PI->ECC. Using FTP I am getting able to fetch the xml file from MDM Server Ready folder. Now, I need to convert this XML file into Idocs and post it in ECC. Can anyone provide me step by step configuration in PI to achieve this. I have configured communication channel with adapter type Idoc in Itegration Builder. But, I am not sure where it will do the conversion of XML into Idoc and how do post it to ECC. I am working first time on PI 7.1. I have worked on XI 3.0 in 2006-2007. Any help to configure this step by step shall be appreciated.
    Thanks & Regards,
    Hemal

    In you have the XML from MDM you have to use the mapping provided by the funtionals in the Funtional specification documents. once you did it you must configure the Receiver IDoc Adapter. and later dont fonget to configure properly the ReceiverAgreement.
    as you receive the docuement from MDM via FTP, thats not a SAP System that means that you have to define PI as the sender of the IDoc,otherwise you will have the Error "Unable to convert the sender service to an ALE logical system"
    to do that in the receiver Agreement>Header Mapping>Sender System-->Select PI server.
    Take in mind to send IDocs to any SAP System, the system that send it must be a SAP system too. thats why you configure it
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
    Another thing is you have configure the ALE distribution Model.
    se this:
    http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Let us know
    Rodrigo P-.

  • IDOC --BPM--IDOC AND FILE

    Hi Experts,
    My scenario is idoc to idoc and file through BPM.
    so I hve one integration process and 2 receiver.The prob is frm IP it is pointing to only file not to IDOC
    1) 1 sender agreement
    2) 3 receiver determination
    3) 3 interface determination
    please help me out..

    Why are you using BPM for this?it is not good design.
    If you want to still use bpm then
    1)1 receive step,
    2)2 transformations steps(if or are executing Operation mapping in IP).
    3)2 send steps.
    check your BPM design and monitor Integration process work flow.
    Regards,
    Raj

Maybe you are looking for

  • Creation of service notifcation

    Hi All, We are using repair order process. The main process is: - Creation of notification (S3) - In action box, creation of repair order (RAS) - Delivery (LR) - Service order (SM03) - Delivery to customer (LF) - Billing My issue is when create servi

  • How do I fix the audio on facetime since I updated itunes

    I updated to the lastest version of itunes and now the audio on facetime will not work.  This is the same problem on my imac, my macair and my ipad2. any solutions?

  • Using multiply effect on illustrator file with 2 color job?

    Hi, Encountering a tricky problem and not sure if its an InDesign fix or an Illustrator fix. I am working on a 2 color job—pms color + black on a book cover. The cover needs to seperate into these 2 colors. Also, I need to make a high res and lowres

  • Help on drag and drop function

    Hi guys, I have a problem creating a drag and drop function for a certain task. The task is as stated below: 1. Create a VI that enables a user to drag and drop multiple image files into it. 2. I was thinking of storing all the file names into an arr

  • Time Machine Can Be Made to work with a Network Share

    FYI I am just posting this here for the benefit of the community. The source of this info is: http://forums.macrumors.com/showthread.php?t=375047 As I write this, I am doing a Time Machine backup to a ReadyNAS NV+ afp mounted share. Here is a summary