Diff between EDI and ALE

Cand any one of you tell me exact difference between EDI and ALE

hi praneeth,
ALE: Application link enabling is a methodology used to transfer data between two applications
EDI (Electronic Data Interchange) is the standards to integrate data between those applications who support these standards
IDOC s are converted into a standard text format by EDI and send it to receiver application which is able to interpret that message means which support edi standards.
PLS refer existing threads, articles,blogs b4 posting
Regards,
Mandeep Virk

Similar Messages

Diff Btn EDI and ALE

Hi Experts,
What is the diff btn EDI and ALE.
Straight answers will be rewarded.
Regards,
SAI

Hi,
In simple words ...
ALE is technology for SAP mainly use to transfer data between SAP systems.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
Regards,
Padmam.

Difference between EDI and ALE.

Hi gurus,
     Let clarify my confusion in difference between EDI and ALE.please give a proper example for the same.
     please have a look my confusions as mentioned below:
    Case 1--In same company,suppose we r using two clients 417 and 416 and want to transfer sap data between these two clients.Then which process (EDI or ALE) has to be follow?
     Case2--Suppose want to transfer data from SAP system to non SAP system then which process(EDI or ALE) has to be follow.
Regards
Ashish K

Hi,
Follow the links on ALE and EDI
http://help.sap.com/erp2005_ehp_02/helpdata/en/a5/63240543a211d189410000e829fbbd/frameset.htm
http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
http://www.wb.nic.in/internet/edi.html
In both cases you can use any one either ALE or EDI.
Rgds,
Suman

Configuration of EDI and ALE

Hi,
I am new to Idocs i would like to know the cofiguration settings for EDI and ALE from starting.I know abt creating partner profiles and the other stuff. I would like to know in detail. Please let me know.
Thanks in Advance,
Srikanth.N

Hi
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)
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
RSEOUT00 Process all selected IDocs (EDI)
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.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
<b>Reward points for useful Answers</b>
Regards
Anji

What is diff bet EDI and XI?

Hi Friends
What is diff bet EDI and XI?
Regards
Vinny Novice

"EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
The business data is saved in IDoc format in the IDoc Interface and is forwarded as IDocs. If an error occurs, exception handling is triggered using SAP tasks. The agents who are responsible for these tasks and have the relevant authorizations are defined in the IDoc Interface.
Features
The IDoc Interface supports three types of data flow with the external system:
·        Outbound processing
IDocs are transferred to a receiving system from your SAP System.
·        Inbound processing
IDocs are transferred to your SAP System from an upstream system.
·        Status processing
XI
SAP XI is based on general standards so as to enable external systems to be integrated. At the center of the infrastructure is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in user-defined XML (eXtensible Markup Language) schema from the sender to the receiver using the Integration Server.
●     Modeling and design of messages, transformations, and cross-component integration processes
●     Configuration options for managing collaborative processes and message flow
●     Runtime for message and process management
●     Adapter Engine for integrating heterogeneous system components
●     Central monitoring for monitoring message flow and processes
Thanks

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

EDI and ALE

hi,
can anyone tell what are the table get affected while using EDI and ALE , and also with their explanation.
thanks
Ganesh

ALE tables.
EDMSG - logical message type
TBD05 - distribution model for message type
TBDLS - logical system
TBD00 - view of customer model
TBD10 - idoc field in ALE objects
BDCP - change pointer
CDHDR - chnage document header
CDPOS - change document item
TBD21 - ale idoc reduction
TBD30 - ale conversion rule
TBD11 - ale object type
EDI Tables
EDI_DC40 - Idoc control record structure
EDI_DC - Control record structur
EDIDC - Idoc control record
EDI_DD40 - Idoc data record structure
EDI_DD - data record structure
EDID4 - Idoc data record from v4
EDID2 - Idoc data record from v3
EDIDS - status record idoc
EDIDD - data record idoc
EDID3 - Idoc data record from v3

Diff between Serialization and Synchronization

Hi I am new to java.
Pl. give me the difference between Serialization and Synchronization.
Thankq
Sridhar

Don't you look at the timestamps of posts? They could
have been typing at the same time.
/KajPlease stop! I'll die laughing. LOL
Re: Diff between Serialization and Synchronization
Author: Annie. Apr 11, 2005 10:30 AM (reply 1 of 4)
Re: Diff between Serialization and Synchronization
Author: glrao Apr 12, 2005 8:31 AM (reply 2 of 4) I really like your sense of humor.
xH4x0r

Types of DTP , Diff between Standard and Error DTP

Hi experts,
What is DTP , are the Types of DTP , Diff between Standard and Error DTP , how it works in BI 7.0.
I will assign points for your valuable answers.

Hello ,
Data transfer process (DTP) to transfer data within BI from one persistent object to another object, in accordance with certain transformations and filters. In this respect, it replaces the data mart interface and the InfoPackage. As of SAP NetWeaver 7.0, the InfoPackage only loads data to the entry layer of BI (PSA).
The data transfer process makes the transfer processes in the data warehousing layer more transparent. Optimized parallel processing improves the performance of the transfer process (the data transfer process determines the processing mode). You can use the data transfer process to separate delta processes for different targets and you can use filter options between the persistent objects on various levels. For example, you can use filters between a DataStore object and an InfoCube.
Data transfer processes are used for standard data transfer, for real-time data acquisition, and for accessing data directly.
1.Benefit: Data Distributionwithin BI Capabilities (from PSA or InfoProviders to InfoProviders)
2.Improved transparency of staging processes across data warehouselayers (PSA, DWH layer, ODS layer, Architected Data Marts)
3.Improved performance and high scalability
4.Separation of delta mechanism for different data targets: delta capability is controlledby the DTP
5.Enhanced filtering in dataflow
6.Repair modus based on temporary buffers (buffers keep complete set of data)
See these docs for more info
[Data Transfer Process |http://help.sap.com/saphelp_nw04s/helpdata/en/42/f98e07cc483255e10000000a1553f7/content.htm]
[Enterprise Data Warehouse (EDW)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a]
[What's New with SAP NetWeaver 2004s - Detailed|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3]
[SAP NetWeaver 7.0 ETL and EII|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b24053-654e-2a10-4180-b0e7c7b4c9f2]
[How to Create Monitor Entries from a Transformation Routine (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50fda171-e36e-2910-9290-e3dab26c50b5]
FAQ on SAP NetWeaver 2004s
[Modeling the Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7c2a7c65-0901-0010-5e8c-be0ad9c05a31]
[Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c9f5fb91-0c01-0010-67a8-fd35946e9403]
Thanks
Chandran

Diff between dbms_profiler and dbms_trace

Hi,
what would be the major diff between dbms_profiler and dbms_trace? which is more useful.
Thanks,
Mathew

DBMS_PROFILER is one way to analyse where the time is being spent

Whats the diff between express and pro??

Just wondering what the main diff between the two are. I've used pro at school, but cant afford to get it at home. Will i still be able to use the same audio instruments like the same synths and plug ins??? Also, would i be able to run the program on a mac mini (top of the line)?

Matt Mac 63, "Whats the diff between express and pro??" #5, 10:33pm Oct 18, 2005 CDT
All I was saying is that if a person can afford to get Pro, they definitely should. The difference in features adds up to at least the difference in price, if not very much more.
Having said that, Express is good value compared to most other DAW software at that pricepoint, but it is only intended as a 'Lite' version.
Some examples, off the top of my head, of differences not made really clear in the comparison list.
Input Objects:
In Pro you can use Input Objects to monitor incoming signal without rec-enabling a track. That doesn't sound much, on the face of it, but what it means is you can use external FX units (hardware) as inserts in tracks (or busses) just like plugins, and bounce them with the mix. it also means you acn monitor what you are playing into Logic Pro with plugin FX applied, but record dry so you can hear your guitar with the reverb, or whatever, but still have the recorded dry signal so you can change the FX settings later.
Pro has some very handy environment objects. The main one being the Trabsformer object. But also another extremely useful object is TouchTracks.
If you've ever played with Ableton Live you would have noticed you can triger clips with the keyboard in all different ways (loop, gate loop, one shot etc.) Well TouchTracks does that with MIDI regions.(I have a feeling that feature in Live was modeled after Logic's TouchTracks' as it is incredibly similar.)
They are only a few examples of a whole range of differences. If all the differences were itemized in the 'comparison chart' it would be about 3 pages long.
All I am saying is, don't take the comparison chart as the definitive list of differences.
yes, Express is a good basic tool and you can do a lot with it, with some imagination.
The SOS author's claim that:
you're paying less than a third of the price of Logic Pro and getting over 90 percent of the functionality."
is not true in totality.
It may be true to someone who has never dabbled in audio software before, because it takes literally years to become fully conversant with every function in Logic Pro, and no-one uses absolutely everything.
But for serious users, who have big demands, in my opinion, Express is less than 30% of Pro's functionality.

Diff between issession and issystem

All,
Wanted to understand ..When we need to restart he DB servers in case if we change some parameters ...?
What is the diff between issession and issystem modifiable clauses ...?
Thanks

Got the answer

Diff Between PCC and PC by Order

Dear Team,
Why PCC does not support Actual Cost Method and Why PC by Order does't not support Target Cost Method?
Please give your views and comments.
Best Regards,
Satish

hi
=========================
what is diff between billing and invoice?
From the help for cash order, it says that the invoice will print immediately after order created, the billing will be done seperately by transaction after delivery. Can anyone explain more detail.
=================
based on ur query.. Billing and Invoice are one and the same.. the difference is that in general business terminology Billing means the process of crediting the customer to the certain sum of money either by cash or credit, for the goods or services purchased by him... this process consists of many other documents like credit note, debit note, invoice, etc.
Invoice is the Printed format of the Bill ie, the sum of amount the customer is credited is made available in the printiable format....
dont get confused by the Billing and Invoice words.. in simple way invoice is one of the documents generated during the billing process.. Billing is a process which consists of various different documents which are generated depending on the business requirements...
Reward if USeful
Thanx & regards.
Naren..

Diff Between Interfaces and API

Hi to all.
Can anybody tell me , What is the basic diff between API and Interfaces ?
Thanks in advance

Hi Lalit,
Both place validation will happen. In Interface table as well as in API.
The difference you can say..for interface you have to load the data in and invoke the import program by which it will populate data in oracle apps base table. So you have to write some DML.
While in API you can simply use PLSQL record type and using that invoke API by which it will populate record in oracle apps base table.
Keep in mind both ways the validation happens. It is just the approach and some part is just for legacy data conversion.
Regards
Prashant Pathak

Relation between EDI and SAP MM

Hello Gurus,
Is there any relation between SAP MM and EDI...?
Omkar--

Hello Omkar,
There is no specific relation between EDI and SAP MM. SAP MM module is for your internal data while Industry EDI is communication media.
E.g.
If you create a PO in your system , it is related to your MM part while information with regards to craeted PO is supplied to vendor by EDI _ Electronic data interchange.
Hope this will help you.
Amit C kulkarni.

Diff between EDI and ALE

Similar Messages

Maybe you are looking for