Sound technologies

Hi, although not connected directly to java. I am looking for some information about the latest techniques and technologies used in the games and animation industry, for example interactive audio. Also some history of how sound has changed in gaming over the last 20 years or so. anyone know of any good sites. thanks.

the site www.google.com has a lot on that subject

Similar Messages

  • Re: New sound technology for MSI, called Nahimic ?!

    i totally agree. nahimic is inferior compared to creative sound blaster cinema 2. the difference is just way too obvious. Nahimic employs heavy volume leveling processing that suppressed the sound entirely, and the volume at same level is far lower tha...

    So my temps were at 74 max running extreme.  100% power.  Support just told me my coil whine could be from a faulty or underpowered PSU.  I could go grab a gold rated 1000, probably need it if I SLI. 
    Still no answer from support to why my boost clock...

  • Problem Getting 3D Sound With AWE64 Gold Card in DOS

    Hi,
    I cannot get 3D Sound to work with my AWE64 Gold Card in MS-DOS.
    In the C:>SB16 directory, I type CT3DSE to enable 3D Enhancement Technology but I receive the message, your card does not support 3D Sound Technology. I was able to activate it in the past and now I can't.
    I installed the DOS drivers from the AWE64 Gold CD - so incorrect drivers are not the issue here.
    Could it be that there's not enough free Conventional Memory to activate this feature? I have 510KB free.
    Can anyone help?
    Thanks.

    Mystery solved.
    There are at least two models of the AWE 64 Gold: The CT4540 and the CT4390. The 4540 does NOT support 3D Creative Enhancement Technology. The 4930 does. This may seem odd as one would expect the higher model to be more advanced.

  • Sound bars...good idea or bad idea?

    I am looking at purchasing a new HT system, but the Sony sound bars caught my eye. I know they can't fully sound as good as a true 5.1 or 7.1, but I like the idea of not having to run wires. Do they sound good with movies or just TV? Any help is welcomed. 

    The sound bars produced today are actually amazing. While they might not give you the range of a more expensive set, they are perfect for average home theater use. They use 3D sound technology to bounce off walls, creating artificial surround sound that actually impressive - the sort of technology you would of paid thousands of dollars for a few years ago.
    I would not recommend sound bars for mainly music use - they are not designed for that. They are designed for home theaters - and if that is your purpose, and you don't wish to run a more extensive and expensive system, sound bars are great. They are arranged so that the speaking voice is louder and the music softer, which is a major failing of a big theater system which isn't properly set up.
    Quick, easy, and simple the use is the advantage of a soundbar.
    Limited options for more intense audiophiles is the disadvantage.
    I am a Bestbuy employee who volunteers on these boards on my own time. I am not paid for posting here, and you should understand that my opinions are exactly that - opinions. I do not represent Bestbuy in any way.
    : Open Mailbox

  • Website utilizing Soundstorm technology

    Hi all,
    Here is a website I came across.  Unfortunately it is a pay site but down in the sound effects section they claim to have to used Soundstorm technology to record.  Maybe someone with a few extra bucks might be adventurous enough to try it.
    http://www.audiolicense.net/

    nothing to do with nvidia.
    Quote
    Here you can explore and purchase from a selection of sound effects from Soundstorm, the award winning sound editorial house. A team is currently in the process of categorising the remaining 200,000 effects for upload to the web site shortly.
    From that quote, i gather that a mucis/sample company is called Soundstorm.
    This does NOT relate to the nvidia sound technology on the nforce1/2.

  • Nahimic Sound Enhancer: Tutorial

    Some of you may have heard about Nahimic previously, and its use in MSI Gaming systems. With Computex, we’ve decided to announce our partnership on a grand scale, and in short, Nahimic Audio Enhancer is a nifty software tool to enhance your gaming experience.
    Nahimic itself has a background as an army supplier in sound technology – more specifically delivering software to combat flight simulators in France. Therefore, Nahimic is the first dedicated audio solution of its type with roots solely in gaming, unlike other solutions that stem from the world of movies.
    Regardless of whether you’re interested in improving sound playback or recording, the easy to use control panel helps you on your way. See Nahimic’s video below for a comprehensive explanation:

    Could you clarify the advantages or disadvantages of this as compared to the SoundBlaster software bundled with my GS70 2QE? Also weather or not I should be able to a upgrade my BIOS, and ensure my audio drivers are up to date, to run it on a machine that didn't ship with it? The updated BIOS description would seem to indicate this is possible (GS70 2QE Haswell), but the application wont launch to the GUI for me. Like others all I see is the startup icon in the task bar.

  • MSI All In One 2400 - sound quality

    I have read your review on the net about the MSI AIO WindTop 2400 and I bought it.
    I'm disappointed with the sound quality, as I checked it`s very poor. 
    The sound seems to be good, but the quality is poor for the machine's prize.
    HIFI speaker o SRS Premium Sound, don't add more quality.
    To make a comparison a notebook have more sound quality.
    By the way, the speakers can't be set as 2.1 (by default 2.0) to use full the subwoofer.
    I tried changing drivers, without any change.
    Thxs for your attention

    You're right. The marketing information for this model implies better than average sound. At least better than what I got, since I don't have the sub-woofer. Still,  2 x 5W Speakers with a 10W Subwoofer is still pretty low-end for any PC sound system. If you can stomach your disappointment, you might want to consider something like a Logitech Z313 2.1 speaker system.
    Bye.     
    Quote from: marcelom on 20-August-10, 06:37:30
    As is advertised "Premium Sound Technology with 2 x 5W Speaker,10W Subwoofer"
    Hi-Fi Speakers SRS, etc. etc.
    I expect more sound quality.
    My litte Asus Eee Pc has better sound 
    I'm disappointed because I just want a multimedia center for a little room (tv, dvd player, pc).
    Also if I wanna connect a Home Theater, I must get some one with digital optical connection (toslink).
    By the way toslink connectors aren't present in a lot of HT.

  • Using Skype Mobile while traveling in Europe

    I have a Verizon Samsung Fascinate with Skype installed.   I have bought credits.
    I will soon be traveling to Belgium and France.  I have been told by Verizon that my phone will not work in Europe.  However, when my husband talked to a representative from Skype, he was told that, with the Skype credits, we would be able to use our phone in Europe....   Please explain the discrepancy in what we were told by the two representatives from the 2 companies.
    If there is something special we have to do in order to use our phone in Europe, please let us know what it is.
    Thank you

    --- At the risk of sounding  technologically uninformed I don't understand the acronyms you used for phone compatibility in Europe. I have an unused iPhone 4 I had AT&T "unlock" for me (I understand there's no real way to check stateside whether the unlock process was actually successful, but I'll go with the assumption it worked for now) BTW AT&T website provides a form you submit and they'll reply within 48 hrs. Took 3 hrs for me, I assume because I have another phone under contract with them, so no harm no foul for them.
    ---  Anyway ... I visited various blogs trying to find out the best process to acquire a SIM card for France. It's complicated as the saying goes. So I googled the question what about Skype?
    --- I use Skype-to-Go from US to call Europe. Very cool, they provide a local # I dial and it connects me for little cost. Calling cell phones is pricyer than landlines. I can use Skype-to-Go from ANYWHERE in the US on one of three authorized phones.
    --- My question is: Is there a similar process FROM Europe to US?
    --- Can I use the Skype App to dial a phone in the US from the existing AT&T US iPhone without incurring roaming charges- and if YES, HOW?
    OR Can I use my old unlocked iPhone with a SIM card from France to call US and Euro #s? if yes which provider do you recommend? Preferrable one purchased in US so it is pre-authorized and ready to go upon arrival.
    OR do I need to use the iPad camera-driven Skype function that requires previous arrangments to ensure that the recipient is at her computer also?
    --- The subtle differences have never been clear to me ...
    Thank you!

  • MSI GE70 Apache Pro unboxing

    Here we have the awesome MSI GE70 Apache Pro (GE70 2PE-051UK) for our unboxing! As you can see it has all the trademark MSI logo, slogan and some of the other world class brands which feature on this notebook such as the Killer network who provide the fastest possible network speeds for lightening quick connection when gaming! The sound is by Danish specialists Dynaudio for unbeatable clarity. Dynaudio is only used on the best quality products, they also provide there sound systems to top cars such as Bugatti; showing they provide only top quality sound. The keyboard is by Steelseries; pioneers in the gaming peripheral department. They provide the top quality keyboard produced for the ease of use for gamers therefore improving you’re gaming skills! On the side of the box is the model and spec of the notebook inside.
    First thing you see when the box is open is the power lead and unit, as shown the power unit is very thin and light; like the notebook itself so therefore great for portability!
    Also we have the sleeve with a driver CD, warranty booklet/form, quick start guide, hot key F3 recovery function booklet, CE Compliance booklet and finally a competition entry to win a free notebook!
    Now for the main event; the notebook itself! Inside the box we have supports to hold the notebook to make sure it’s safe when being delivered. Once it’s out of the box we have the notebook in a protective sleeve and under this is the screen sleeve to protect further! Here is the GE70 out of the protective sleeves, the lid of the notebook is brushed aluminium and has simple and effective MSI branding; the dragon in Asian legends means the king of the world, this represents MSI commitment to provide only the highest standard of gaming notebooks to gamers worldwide. As well as this, the dragon on the logo is backlit and adds to the already awesome look of the notebook.
    On the front of the notebook there are the LED indicator’s, we have the disc indicator, Bluetooth, WLAN, battery, caps lock, num lock and finally the sleep.
    On the left side of the notebook we have an SD card slot, gold flash headphone jacks with MSI audio boost which enhances sound clarity and fidelity by 30%; just another feature which can make your gaming and multimedia experience much better! There are 2 USB 3.0 slots, HDMI port, ventilation, power plug and the security lock.
    On the right side of the notebook we have the gigabyte Ethernet port, VGA port, high power USB 2.0 for when you need to charge your mobile fast (or any other device), BD Combo / DVD Super multi and another USB 2.0!
    Here’s the back of the laptop, as you can see it has a sleek design like the rest of the notebook.
    The screen itself is a 17.3” Full HD (1920x1080) anti-glare LCD panel in LED backlight, the anti-glare itself is very use full for gaming and other tasks as you can use the notebook in any conditions and still have maximum use at all time!
    Here we have the full keyboard layout by Steelseries, it features a fully backlit keyboard with over 1000 different colour combinations and five different scenario modes for the keyboard! So weather you’re at home gaming in the dark or at a LAN party, you can have the coolest looking keyboard with high visibility for every key; enabling you to maximize your gaming skills in every situation. This keyboard also supports multi keys; therefore allowing users to rapidly respond to games with precision and issue commands rapidly. You can learn more about the Steelseries keyboard and engine here:
    Featured on the steel series keyboard is a change to the usual keyboard layout, the left Ctrl button has been made larger than usual as it is an important key for gamers and is now more accessible when gaming.
    The windows button on this keyboard has also moved from the left of the keyboard to the right side, this has been done in favour of gamers so the button doesn’t get in the way when you are gaming. All these little details maximize your gaming experience way more than your normal keyboard!
    On the GE70 we have world class sound provided by Danish sound specialists Dynaudio! The notebook has speakers located above the keyboard and also has 2 other speakers on the underside of the notebook closest to the front. The speakers support 7.1 channel SPDIF output, features exclusive audio boost technology which enhances sound clarity and fidelity by 30%! All together increasing the gaming and multimedia experience with the great sound provided. You can learn more about the Dynaudio sound here:
    [video=youtube;tE8FBiuGsBo]
    The back of the notebook has 5 rubber studs to keep the notebook secure when stationary; therefore no movement when using the notebook. The battery is a 6-Cell Li-Ion, there are several ventilation spots to keep the notebook running cool at all time.
    Here is the spec of the notebook
    Operating System   Windows 8.1
    Processor / chipset
    CPU   Intel Core i7 (4th Gen) 4700HQ / 2.4 GHz
    Max Turbo Speed   3.4 GHz
    Number of Cores   Quad-Core
    64-bit Computing   Yes
    Chipset   Mobile Intel HM87 Express
    Features   Intel Turbo Boost Technology 2.0
    Memory
    RAM   16 GB ( 2 x 8 GB )
    Technology   DDR3L SDRAM
    Storage
    Hard Drive   256 GB SSD - MSI Super RAID
    SSD Form Factor   mSATA
    Hard Drive (2nd)   1 TB HDD / 7200 rpm - Serial ATA-600
    Optical Drive   DVD±RW (±R DL) / DVD-RAM
    Display
    Type   17.3"
    LCD Backlight Technology   LED backlight
    Resolution   1920 x 1080 ( Full HD )
    Widescreen   Yes
    Image Aspect Ratio   16:9
    Features   Anti-glare, MSI Matrix Display
    Audio & video
    Graphics Processor   NVIDIA GeForce GTX 860M - 2 GB GDDR5 SDRAM
    Camera   Integrated webcam
    Capture Resolutions   1280 x 720
    Sound   Speakers, subwoofer , microphone
    Audio Features   Dynaudio Premium Sound Technology, MSI Audio Boost
    Input
    Type   Touchpad, backlit keyboard
    Communications
    Wireless   802.11n, Bluetooth 4.0
    Network Interface   Gigabit Ethernet
    Ethernet Controller   Killer E2200 Intelligent Networking
    Battery
    Technology   6-cell Lithium Ion
    Capacity   49 Wh
    Run Time   Up to 4 hours
    Ac adapter
    Output   120 Watt
    Connections & expansion
    Interfaces   2 x USB 2.0 ¦ 2 x USB 3.0 ¦ LAN ¦ VGA ¦ HDMI ¦ Headphone output ¦ Microphone input
    Memory Card Reader   Yes ( SD Card, SDHC Card, SDXC Card )
    Miscellaneous
    Features   Cooler Boost technology, SteelSeries gaming keyboard
    Dimensions & weight
    Width   41.8 cm
    Depth   26.9 cm
    Height   3.9 cm
    Weight   3 kg
    This is the MSI boot configure, it’s the first software that opens on start of your MSI notebook. It’s a thoughtful program which is designed to let you choose how you want your notebook to boot up, the 2 screenshots show the options available; you can choose between the windows 8.1 metro or the normal desktop screen on log in. As well you have the option to choose whether the start button goes to the start screen or the app screen. This simple program allows you to customize your notebook to your needs!
    The GE70 has a Killer E2200 Intelligent networking LAN chip. It automatically detects and accelerates game traffic for smoother, faster gameplay by recognizing and prioritising online game data packs. Therefore in any game you’re playing weather a FPS or MMO you will always have the fastest response time possible in every situation! You can also manually decide the priority of each application to maximize network performance on the programs you need the most! You can see more on the killer network on our youtube -
    [video=youtube;bc4Y4VxOA-g]
    Now to test the system with the latest high demand games! We tested the system with crysis 3, metro last light, assassin's creed IV and battlefield 4. All these games require very high spec systems and are great for testing; we tested them on max settings and also on Nvidia’s optimized settings for each game. Nvidia has made it easy to optimize the settings to get the best performance possible out of the notebook with the GeForce experience! You can auto-optimize game settings for best performance and tweak them if you want better graphics or better frame rate.
    The result are as follows:
    Crysis 3 maxed out ran at an average of 20-30 FPS and with Nvidia’s optimized settings it ran at an average of 55-65 FPS.
    Metro last light maxed out ran at an average of 30-40 FPS and with Nvidia’s optimized settings it ran at an average of 50-60 FPS.
    Assassin’s creed IV maxed out ran at an average of 30-40 FPS and with Nvidias optimized settings it ran at an average of 35-45 FPS.
    Battlefield 4 maxed out ran at an average of 35-45 FPS and with Nvidia’s optimized settings it ran at an average of 50-60 FPS.
    All round great results from some of the highest demanding games on the market, it shows that the GE70 is capable of keeping up with your gaming needs while still being a portable, slim and light notebook.

    It is extra ventilation for cooling! Quote from: RepoSnow;104046
    I actually just bought one of these- 012 US model and it hasnt got here yet but do you know what these two rows of dots are on the back? (Picture #15) http://i60.tinypic.com/34h9xfb.jpg

  • Poor Audio Quality in my new HP 15 R203TX

    Hi I have just purchased HP pavillion 15 R2037TX laptop. It comes with 5th gen 5200U processor with 4gb ram, 2gb nvidia 820M graphics 1tb of hdd with DOS with realtek hd sound technology.  I installed win 8.1 and accordingly installed all the drivers from the official hp website. After installing audio driver I found that DTS audio control panel was installed. My laptop is working fine except one thing  I am not getting proper sound quality which i used to enjoy in my previous e038tx laptop that  too came with DTS audio. The sound is not sweet or crisp rather very hazy when playing through external subwoofer and speaker. I enjoyed clear and crisp audio quality in the same speaker and sub woofer  previously. Plus I can not understand why after realtek hd audio I get dts audio control panel. Because the audio vendor says its hardware is Realtek HD audio. Realtek has its own audio control panel which I do not find here. Whatever kindly help me how can i enjoy beautiful sound >? thanx in advance

    swarup_s wrote:
    Hello friend   @lbrou87 I'm not hear to debate about the issue unless you are a Hp Support people (Which I think you are not).  And  I have explained everything  in my previous replies  then why are you asking absurd questions. This was my 2nd laptop after 7 years and I'm using 1st time a HP laptop. I could have gone with my previous brand laptop of DELL . I chossed Hp to try a new brand. I could have gone with purchasing DELL. If I pay a premium price for this hp model then why I'm getting a great featured laptop which gives me a low audio output. What you said in your reply  HP don't want to update the technology in the drivers which make Hp customers to buy external speakers. Then what more I can say!!!...  I'm really unsatisfied. The Hp support if they can't say anything then who should I go and ask. (sorry  friend  @lbrou87  if I'm being rude to you in this reply)   
    I was just trying to help.  I've been through this with HP Support before with a similar issue.  I though the premise of a forum was not only for HP's representatives to help, but other forum members as well.  But, since you want to be rude and obnoxious to someone that only wants to help, I'm done with this thread.  Wait for HP's representatives for help.  Good day sir.

  • What is IDOC and ALE?

    Hi anybody,
             Please tell me what is IDOC and ALE? What pupose using IDOC and ALE?
              Give me  Example sample code  of using IDOC and ALE.
    Thanks
    S.Muthu.

    Dear,
    Here is some facts which will be helpful to clear yr concepts for ALE/IDOCs.
    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.
    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.
    *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.
    ALE (Application Linking and Enabling)
    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.
    Distributed Process:
    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
    Need for Distributed Process:
    • Business in Different Geographical Locations.
    • Non availability of dedicated network.
    • Cultural and language differences in Geographical locations.
    • Running of Mission-critical Applications (Like Maintenance downtime etc.).
    • Separate up gradation of Modules.
    Distributed SAP SYSTEM – CHALLENGES
    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
    • Receiving systems that can handle their own problems and not tie up the sending system.
    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
    • A sound technology and methodology that can be used in all distribution scenarios.
    SAP Distributed environment:
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the
    application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).
    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    • Basic integrity check: A basic integrity check is performed on the control record.
    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application 
    How to create idoc?
    *WE30 - you can create a IDOC type
    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
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type.
    The receiving systems for the specified message type are determined from the customer distribution model.
    Output:-The report outputs information about the number of master IDocs and communication IDocs created.
    RSEOUT00 – Process all selected IDocs (EDI)  Report for generation of files for EDI outbound processing.The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.  
    It is important that you make sure that only test messages or productive messages are selected.
    The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    For testing you can use WE19.
    Hope This will be helpful,
    Best Regards ,
    P Singh

  • Difference btw idoc ale and edi

    Hi all,
    I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
    Also do send some materials for the same.

    Hi,
    ALE (Application Linking and Enabling)
    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.
    Distributed Process:
    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
    Need for Distributed Process:
    • Business in Different Geographical Locations.
    • Non availability of dedicated network.
    • Cultural and language differences in Geographical locations.
    • Running of Mission-critical Applications (Like Maintenance downtime etc.).
    • Separate up gradation of Modules.
    Distributed SAP SYSTEM – CHALLENGES
    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
    • Receiving systems that can handle their own problems and not tie up the sending system.
    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
    • A sound technology and methodology that can be used in all distribution scenarios.
    SAP Distributed environment:
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).
    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    • Basic integrity check: A basic integrity check is performed on the control record.
    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
    IDOC:
    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]
    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.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    RFC:
    RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
    and you will be passing an Import parameter DESTINATION to it.
    Other code and usage will be similar to any fun module;
    Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
    Refer this link:
    [http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
    check out the following link it might help you
    [http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
    EDI:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    [ALE / IDOC / RFC / EDI]
    [SAP ABAP and EDI/ALE/IDOC]
    [Re: IDOC/BAPI/ALE/EDI]
    Regards,
    Dhruv Shah

  • Walkman update required

    Hi sony,
    Last week bought a z3. Switched from galaxy s4 to z3 mainly for the sound technology I saw in Sony website. Guess what am totally amazed with sound quality in headphones. I used a Sony headset even on s4. But some features on z3 really disappointed me. Here are some, pls give a fix ASAP.
    Couldn't successfully complete post on sony support due to unknown reason. Hence posting here. Pls help this reach to Xperia developers
    1. Walkman widget does not have shuffle repeat icon. We need to everytime open app.
    2. When used a app to control headset button the walkman widget gets vanished from lock screen. Coz of this I have disabled swipe lock screen which I liked a lot.
    3. Calendar widget does not reflect facebook birthday days.
    4. Cannot move to home screen pages directly by touching the circle icons. We need to swipe multiple times to move to home screen pages.
    Well these are main which I regularly use.

    1. true
    2. which headphones are you using?
    3. I prefer google calendar
    4. press the home button 
    "I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

  • Victim of hitech

    Hi there, I think that I´m a victim of the image and sound technology. Why? I own a Sony MicroMv camcorder IP 210 that use the editing software Movie shaker, based on Quick Time 5, only. Now I both an Ipod photo, that´s based in Itunes with QuickTime 6 or superior only. There´s a conflict here. I need to choose one or another to use. I need help to the solution of this. tks. robson

    Hello,
    Your acount has been hacked. You should change both your Skype account and e-mail passwords immediately and that of your PayPal account. The ONLY way in which an account can be hacked is by the hacker either knowing (or "cracking") your password. For this reason Skype doesn't reimburse any assets lost due to an account being hacked.  You could also contact Paypal
    TIME ZONE - US EASTERN. LOCATION - PHILADELPHIA, PA, USA.
    I recommend that you always run the latest Skype version: Windows & Mac
    If my advice helped to fix your issue please mark it as a solution to help others.
    Please note that I generally don't respond to unsolicited Private Messages. Thank you.

  • Realtek HD Audio Issue

    Hello fellows,
    Unfortunately I've been having problems with my Realtek HD Audio (includes THX TruStudio Pro and Dynaudio Premium Sound Technology) with my Windows 8 x64 MSI GT70 whenever I open up a game file and start playing for 1-2 minutes (WoW, Diablo III, SCII). I've tried all the different settings in the Audio Manager but it didn't help.
    For WoW, I seem to have resolved most of the problem (an issue with the sound where makes clicking and buzzing noises) when I opened up the loading screen and chose to open it in 32-bit instead. Unfortunately, SCII or Diablo III don't have that option in the loading screen. For WoW, the problem is mostly gone but an occasional click here or there comes, a lot softer than before. Before, it was unbearable so I had to turn the sound off completely.
    Anyone have suggestions to stop it for good? I'd appreciate the help. I've already reinstalled everything concerning the audio system, it says it is working properly, and I have the latest driver (also tried disabling THX) and the problem still arose after that. I've also tried to run the programs in compatability mode but that didn't work either. Everything else aside from games sound just fine. In any case, changing to the 32-bit helped with WoW. How can I do that for the others?
    Cheers,
    A
    System specs:
    MSI GT70 0ND-490NE
    Operating system Microsoft Windows 8
    CPU
    Intel Core i7 (3rd gen.) 3630QM / 2.4 GHz
    Quad core
    64-bit Computing
    Chipset Mobile Intel HM77 Express
    Memory
    RAM 8 GB
    Maximum. RAM supported 32 GB
    Technology DDR3 SDRAM
    Speed ​​1600 MHz
    Number of Outlets 4
    Storage
    Hard Drive 750 GB HDD / 7200 rpm
    Interface Serial ATA-300
    Optical drive DVD ± RW (± R DL) / DVD-RAM
    Display
    Type 17.3 "
    LCD Backlight Technology LED backlight
    Resolution 1920 x 1080 (Full HD)
    Widescreen Yes
    Features Anti-glare
    Audio & Video
    Graphics Processor NVIDIA GeForce GTX 675M - 2 GB GDDR5 SDRAM
    Camera Integrated webcam
    Audio speakers, subwoofer, microphone
    Standards THX TruStudio Pro
    Audio Features Dynaudio Premium Sound Technology, MSI Audio Boost
    Communications
    Wireless 802.11n, Bluetooth 4.0
    Network Interface Gigabit Ethernet
    Ethernet controller Killer E2200 Intelligent Networking

    Thanks for the suggestions. Even with the default sound driver, I still experience the problem. I contacted MSI and they think it may be a hardware issue. That was the only thing they said. I have my doubts, however. If it was a hardware problem then why don't I have any audio problems when playing music or watching videos?
    Anyone have any other ideas? I really don't want to send the computer away, going through that effort and then to find out that it wasn't a hardware problem after all

Maybe you are looking for

  • To draw in the pdf using pen tool in acrobat reader x

    hi im using the app.execMenuItem("Annots:Tool:InkMenuItem"); in the javascript of textbox in acrobat pro 9. When i click the text box pen tool is activated and im able to sign in that textbox. But in acrobat reader 10.1.2 when i click the textbox its

  • Trouble Connecting Wirelessly

    Hi. I received my WRT54G3G-ST router today and went through the setup without any problems. The problem I have is that I can't seem to connect wirelessly. A couple of times I received an error message that the router was out of range, but I was in th

  • External "Superdrive" not working with macbook?

    My macbook has a broken disk drive but I have a superdrive, how do i get it to work?  Computers with internal disk drives don't seem to like working with external ones.

  • IMessage stopped working on iMac

    i message stopped working on imac

  • Reset the state of one switch when another switch is pressed in a VI

    I have a START/STOP latching button and a PAUSE/RUN latching button. I would like to be able to reset the PAUSE button when the START/STOP button is pressed. Sometimes the user leaves the PAUSE button latched and then presses the START/STOP button. T