New to SAP...Doubts regarding ALE.

Hi all,
I am new to SAP.
Can any one please explain me the following.!
What is the difference between EDI and ALE?
What is Logical system, Port, RFC destination, Customer Distribution Model, Partner Profile, Message type, Message control and if any of the important terminology that I have missed in the ALE concept?
Please help to explain me clearly in detail as I have no knowledge reg these and tried searching for info in various links, but still found difficult to understand?
Many thanks in advance....
Regards
Nani Ancha

ALE/EDI
Purpose
Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example, Structure linkRFC or as a file).
Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
· ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
· By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.

Similar Messages

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

Regarding Add New Non-SAP Software Unit in SLD

Hi Experts,
While We r Creating the Product in SLD, It is Asking for "Add New Non-SAP Software Unit" .
What is This ????? Why Do We Use this ????
I saw this Option in Only PI7.0......
Regards
Khanna

HI Khanna
Those are none other than Software Components that are not existing in the list and you are creating it new.
For example if you are selecting the Product that is existing say "SAP ECC". Now when you go for creating Software Component versions you can select from the list or you can creat your own. When you are creating of your own Software Component it is called Non-SAP Sotware Unit.
Cheers..
Vasu
** Reward points if found useful **

Doubts regarding XML Form Builder

Hi All,
I am having some doubts regarding XML Forms (Projects) that is created using XML Form Builder. Where are exactly these projects stored. Can I edit these projects and add my own Java Functionality in these. And also the data which I fill using these project where is it stored. Suppose New Project I ve created using XML Form Builder, now I want to feed in the news. Where exactly are these news stored.
Thanks in Advance
Anish

Hi Anish
You can make the standard settings and modify the XML forms builder in line with your requirements in the options. You can set the standard paths for your project on the Paths tab page.
To get a clear understanding, please go through this link.
http://help.sap.com/saphelp_erp2004/helpdata/en/62/ca6f365a6df84e87ba085f9b5fb350/content.htm
Hope that was helpful
Warm Regards
Priya

Some doubts regarding sorcing cockpit in EBP

Hi all,
This is sankar bhatta , working in IBM . I am new to the EBP module. I got few doubts regarding the sourcing cockpit.
When a shopping cart comes to the sourcing cockpit of the purchaser. I mean in what cases??
i am listing some of the cases where i have doubts.
1) A user creates a SC , but he doesn't assign any vendors. in that case it comes to the sourcing cockpit of the Purchase . is it right??
2)A user created a shopping cart ( with more than one item) without vendor and it has gone to SOCO of purchaser . he has assigned the vendor and orders it. the PO is created in the Backend. now because of some reason ( for example the vendor is not able to supply the item ) the purchase deletes one item from the PO in EB. In this case is the SC comes again to SOCO of the Purchaser???
3) the user created the SC without vendor.The SC goes to the SOCO of the purchaser. The SC is in approval process. Now the user deletes one item and orders it again. In this case whether the SC goes to the SOCO again???
4) User created a SC ( with more than one item) and approval is over. PO is created in the backend. Now, if the user or somebody who has the authorisation deletes the item in SC , does the SC goes to the SOCO of the purchaser??
5)According to SAp standard functionallity, PO can be deleted only by one in purcasing organisation. Is this person person csn be a purchaser (or) some other person in the Purchasing organisation??
Please answer these questions and if you know any other case where a SC comes to the SOCO of the Purcher please include that also.
Thanks and regards
Sankar Rao Bhatta.

Hi Sankara,
The Sourcing cockpit is much more simple than that. Your questions show you'rre very confused in this.
There is only one customizing point used : SAP Reference IMG -> SAP Implementation Guide -> Supplier Relationship Management -> SRM Server -> Sourcing -> Define Sourcing for Product Categories
If Sourcing for Product Categories is not configured, the system creates purchase orders in the local scenario for all requirements; these are incomplete if the source of supply is missing. If you require additional control options, for example, the facility to control processing at product level, you can use the following BAdI: Define Execution of Sourcing.
The diferent options you have in the customizing point are:
-Sourcing is never carried out: This is the default setting. Enterprise Buyer does not transfer any items to the purchaser's sourcing application ¨C independent of the status of the shopping cart.
-Sourcing is always carried out: Enterprise Buyer transfers each item to Sourcing ¨C independent of the status of the shopping cart.
-Sourcing is carried out for items without a source of supply: Enterprise Buyer transfers all requirements that have multiple sources of supply of which none is assigned, or if there is no source of supply for the requirement, to Sourcing.
-Automatic requirement grouping; sourcing for items without assigned source of supply:
If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO. If the requirement does not have a source of supply, it appears in the work list of the sourcing application for manual assignment. Once you have assigned a source of supply, you can submit the requirement to the report.
-Automatic grouping; sourcing is never carried out: If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO. If the requirement does not have a source of supply, an incomplete PO is created.
-Automatic bid invitation for items without a source of supply: Enterprise Buyer creates a bid invitation for all requirements that do not have any source of supply.
So for your questions:
1)depending on your customizing, this SC will lead to:
-Backend PR (classic scenario)
-Local incomplete PO (standalone or extended classic without soircing)
-Requirement in the Sourcing cockpit (if customized)
2)The modification of a PO will never change the initial document (SC and/or requirement), nothing 'comes back' into the sourcing cockpit
3)If you customized the sourcink cockpit, the SC line goes into it only after the approval process
4)This has nothing to do with the sourcing cockpit
5)The POs can be deleted by people who have correct authorizations (that is purchasers of the document purch. org. in standard). Be careful the POs cannot be deleted as soon as they have been edited (as of R/3).
Regards.
Vadim
PS: Please don't forget to reward points for helpful answers on your threads.

Am new to SAP.

Hi all,
Am new to SAP, I chosen to be a BASIS, am studying only through Google, SAP help. Recently i came to know about SDN. It will be very helpful, if you get me some links to have basic knowledge in R/3 and Netweaver.
Thanks,
Sri.

Hi Sri,
I think it will be so useful to you.
The R/3 Basis System: Overview
http://help.sap.com/saphelp_470/helpdata/en/54/57fe09786a11d194c90000e8353423/frameset.htm
Configurations Overview
http://help.sap.com/saphelp_470/helpdata/en/bb/9f12104b9b11d189750000e8322d00/frameset.htm
Installation
http://help.sap.com/saphelp_470/helpdata/en/33/7c863c593a8767e10000000a114084/frameset.htm
Monitoring Multiple SAP R/3 Systems
http://help.sap.com/saphelp_470/helpdata/en/42/a1cfb0fc4111d194bf00a0c93033f7/frameset.htm
Just all links are of help.sap.com, but this is not enough, read it and if you have any doubt, let me know.
Regards,
Dinesh.

Regarding ale & ioc

hi gurus ,
how can i communicate with SAP to Non SAP using ALE and IDOCS.
with regards
aru.

Hi
SAP Integration using ALE
(Application Linking and Enabling)
- Introduction -
Page 1 of 7
1.0 Introduction
Enterprises are increasingly looking to deliver real business benefits by integrating their systems and processes both within their organizations and between organizations. ng processes in this way, which requires tight integration, frequent communication and data exchange.
Highly integrated and inter-dependent SAP and non-SAP systems require frequent communication, tight integration and (usually) high levels of data exchange. In order to achieve this interoperability, SAP has come up with the concept of ALE (Application Linking and Enabling).
The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com
ge of business information across SAP and non-SAP systems. Applications are integrated by using synchronous and asynchronous communication without implementing a central database.
In this 7 article tutorial we will cover subjects such as:
Data Distribution Model
ALE process
IDOCS
Converters
Configuring ALE
Other concepts
RFC
Purpose
Communication 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.
Synchronous RFC
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC)
Transactional RFC (tRFC, also originally known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue until a later time. The calling dialog program can proceed without waiting to see whether or not the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
· executed in the order in which they are called
· executed in the same program context in the target system
· run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved.
Disadvantages of tRFC
· tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
· In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
Queued RFC (qRFC)
To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).
qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (in reference to the sequence defined in different application programs) in the participating queues.
Implementation of qRFC is recommended if you want to guarantee that several transactions are processed in a predefined order.
RFC: Data Transfer
All RFC types are transferred by means of CPI-C or TCP/IP. They constitute a form of gateway communication.
Additional Information
· RFC Basics (BC-MID-RFC)
· The RFC API
· RFC Programming in ABAP
· Queued Remote Function Call (qRFC)
· SAP Gateway
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
is a set of interfaces to object-oriented programming methods that enable a programmer to integrate third-party software into the proprietary R/3 product from SAP. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules.
A good place to get started is this Introduction to BAPIs presented by sappoint.com.
SAP also provides this in-depth BAPI User Guide to help you master the basics. Terminology, rules for usage and prerequisites are included.
Also, SAP provides this BAPI Programming Guide
For ALE
http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
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
For RFC
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/content.htm
http://www.planetsap.com/RFC.htm
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..
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
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/
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Reward all helpfull answers
Regards
Pavan

Doubts on ALE and EDI

Hi all!
Could anyone please let me know the meaning of the following points which I came across in few resumes. I am new to Interfaces and just want to know few examples in detail on how an EDI and IDOC work? If anyone can explain any/few/all of the points below, it would be really very nice and helpful for many of us.
1. Involved in Master Data distribution for Vendor Master from Central Partner system using ALE Distribution Model.
2. Involved in EDI Configuration using Message Control, setting up the Message type, Access Sequence and Output Determination Procedure for Sales order.
3. Involved in the ALE configuration for maintaining Material Master Data, Customer Master Data and Vendor Master Data between two clients.
4. Assisted with troubleshooting EDI outbound interfaces and error message handling.
5. Extended IDOC for ORDERS05 for outbound processing.
6. Created sales order using standard IDOC (orders 05).
7. Monitoring and re-processing of the IDOC's
8. Created Message types and assigned it to IDOC type.
9. Created Process code and assigned it to Inbound Function Module.
Points assured!
Thanks!!

Hi Sekhar, regarding ALE this is some material.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User: MMUSER200 (This is the logon for dist.)
Client : 200
Password: MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG100.
Receiver as LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG200.
Receiver as LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as Mechanical Engineering
Material Type as Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time: WE07.
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.
Regarding IDOC,
Create Message Type (WE81)
Create Segment type (WE31)
Create IDOC Type (WE30)
Assign Segment type to Idoc Type (WE30)
Assign Idoc Type to Message Type (WE82)
Assign Function Module Mtype Idoc Type (WE57)
Create a Process Code (WE41-outbound, WE42-Inbound)
Enable Customized FM to ALE (BD51)
Assign these to Partner Profile (WE20)
check the following thread:
/message/2222912#2222912 [original link is broken]
http://help.sap.com/saphelp_erp2005vp/helpdata/en/e6/04c03e7856b300e10000000a114084/frameset.htm
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
   release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
hope this helps,
kindly reward if found helpful.
cheers,
Hema.
http://www.sapgenie.com/ale/why_ale.htm

How to log in to the new installed SAP ABAP instance ?

Dear Experts,
In SAP ERP 2005 installation,
I have done central system installation, Now I need to perform postinstallation steps,
Could you please tell me, how to log in to the new installed SAP ABAP instance and do the post installation?
Regards,
Madhavan K

Hi,
Check the list of post installation steps:
http://www.saptechies.com/post-installation-steps-for-ecc-60/
From my point of view basic post installation steps are:
- Installing SAP License (from http://service.sap.com/licensekeys)
- Setup TMS (STMS)
- Import profiles (RZ10)
- Client Copy (SCC*)
- Create users (SU01)
However further many steps are required as per your requirements. Cehck the link for more detailed steps.
Regards,
Srikishan

I'm new in SAP . Would like to have some advice

Hi Friends ...
Hello all , perhaps I'm posting the thread into the correct thread category , I'm really new in SAP and currently starting to put my interest into SAP . I'm currently doing IT Support (Unix Support). Previously I have no ideas about SAP and from my knowledge , jumping into sap is too costly until I found about getting to SAP academy through E-Learning which cost half of the actual normal classroom method of getting SAP certification . And obviously it pulled my interest . A few opinion and advices I would like to gather :
1) Do you think that it worth for me to spend money for SAP certification ?
2) What is the career prospect of an SAP certified ?
3) What is normally the routine of the SAP consultant ? in term of the job dsecription .. I don have any ideas what is the scope of a SAP consultant .
4) Is the SAP job marketable ? internationally ?
5) What is the possibly of getting job for a newly certified SAP w/out experience
6) Which is the best module that I should enroll for the certification ?
7) What is normally market price for the SAP certified salary .
What is other tips/advice from you for me before i start investing on getting on the SAP certification . Many thanks in advance for the advices .
Thank you
Regards

Hi,
Well looking at your queries I can suggest you to spend some time looking for the kind of requirements in the markets ( this you can find from different job portals). This answers your query number 2) and 3)
1) Do you think that it worth for me to spend money for SAP certification ?
This is an investment and it is really worth it
2) What is the career prospect of an SAP certified ?
As mentioned earlier, please check this yourself
3) What is normally the routine of the SAP consultant ? in term of the job dsecription .. I don have any ideas what is the scope of a SAP consultant .
As mentioned earlier, please check this yourself
4) Is the SAP job marketable ? internationally ?
Yes
5) What is the possibly of getting job for a newly certified SAP w/out experience
Good depending on your previous work experience
6) Which is the best module that I should enroll for the certification ?
This is always dependent on 3 things:
1) Your academic qualifications
2) Your professionsal experience
3) Your interest
7) What is normally market price for the SAP certified salary .
Depends on your experience and as you are from IT market it varies a lot depending on your experience and the requirement of the company
Hope this helps you.
Do let me know in case of any specific queries.
Regards,
Rakesh

Very urgent: Doubts regarding CRM WORKFLOW OF BUSINESS PARTNER CREATION

HI ,
I HAVE DOUBTS REGARDING CRM WORKFLOW OF BUSINESS PARTNER CREATION, WHILE I AM CREATING BUSINESS PARTNER THROUGH R/3 , IT REFLECT IT INTO MYSAP CRM ALSO, AT THAT TIME IT SENDING THE MAIL TWICE TO THE RECEIPIENT. IS THERE ANY WAY THROUGH WHICH I CAN RESTRICT IT TO SEND THE MAIL ONLY ONCE,
PLZ SEND ME THE REPLY AS SOON AS POSSIBLE,
THANKS ADVANCED,

HI
WORKFLOW SEETING. SAP MAIL
MULTIPLE MAILS AND
ONLY ONCE CHOOSE
ONLY ONCE OPTION ON WHICH VERSION U R WORKING?
REWARD IF HELPFUL
VENKAT

New to SAP PI, I need more information on SAP PI Topics

Hi Guys,
I'm New to SAP PI, I need more information on SAP PI Topics which are related to Development and configuration.
i have gather some information please add more topics and major scenarios if i missed out.
SAP PI Topics:
1.     Mapping
u2022     Standard Functions
u2022     User-defined Functions
u2022     Message Mapping
u2022     Multi-Mapping
u2022     Java, XSLT mapping overview
2.     Business Process Management
u2022     BP Modeling
u2022     BP Engine
3.     Design and Configuration
u2022     System Landscape Directory
u2022     Enterprise Services Repository
u2022     Integration Directory
4.     Runtime
u2022     Integration Engine
u2022     Different installations of Adapter Engines
u2022     Runtime Workbench / Monitoring
u2022     Architecture
5.     PI as Component of SAP NetWeaver
u2022     Positioning
6.     Overview and Basic Concepts
u2022     Adapters & J2EE Adapter framework
u2022     Business Process Management
u2022     Mapping
7.     Adapters
8.     Technical Connectivity for communication with SAP and non-SAP systems
u2022     File/FTP(S) (File Systems / FTP Servers)
u2022     JDBC (RDBMS systems)
u2022     JMS (Messaging systems, e. g. MQSeries, SonicMQ)
u2022     SOAP (Web Services based on SOAP)
u2022     WS-RM (Web Services based on WS Reliable Messaging)
u2022     HTTP_AAE Adapter
u2022     Plain HTTP(S)
u2022     Mail (Mail Servers via SMTP, IMAP4, POP3)
u2022     SAP Business Connector (SAP BC)
u2022     Marketplace (SAP Marketplaces)
9.     Application Connectivity
u2022     RFC
u2022     IDOC_AAE Adapter
u2022     IDoc
u2022     Proxy (ABAP and Java)
10.     SAP Industry Business Packages (contain adapters and content)
u2022     RNIF 2.0 (RosettaNet)
u2022     RNIF 1.1 (RosettaNet)
u2022     CIDX (RNIF 1.1)
11.     Advanced Adapter Engine Extended u2013 AAE
u2022     PI as Infrastructure for Service Oriented Architecture (SOA)
SAP PI Scenarios:
u2022     SOAP to JDBC scenario
u2022     RFC to FILE scenario
u2022     Multiple IDOC's to File scenario
u2022     File to File scenario
u2022     File to RFC scenario using BPM
u2022     File to JDBC scenario
u2022     Idoc to File scenario
u2022     Abap Proxy to XI scenario
u2022     Idoc Flatfile to Idoc XML Scenario

You may search for all basic topics on SCN and you will get required information. Such basic questions should be searched before posting. Thread locked.
Regards,
Prateek Raj Srivastava

Reg: New to SAP

Dear All,
First, I introduce myself.
I am Navaneeth, from Mechanical Engineering background.
I shifted into IT industry and I have 7+ years of experience in Web development technologies like Microsoft and LAMP.
Now I am planning move my career with SAP. I am completely new to SAP.
I have few queries, please clarify it.
1. Is the right time to move SAP from my career background?
2. How is the future Market trend for SAP related jobs?
3. Which one will be the best area for me to enter in to the SAP? (Technical or Functional or both)
4. What are modules will have the more value and less population?
5. Will ABAP is suitable for me?
6. Should I need to do a training/certification?
7. Should I start my SAP career as a fresher or can I use my existing experience?
8. How can I plan my career with SAP?
Please help me to move on forward.
Thanks & regards,
Navaneeth.

Hi,
to 1 & 2: SAP is the best in the IT market for companies. It is a good idea to work with it, since the IT branch was not affected by with world crisis in 2009 and 2009; additionally, withing the IT, SAP consultants are the best paid.
to 3: you should start programming with ABAP considering that you´re technichal. It´ll be a good start for a newbie.
to 4: difficult to know. Some are not very used; therefore there are not many consultants.
to 5: like 3
to 6: traning yes, certification no. Read my answer to a similar [post here|;.
to 7: you´ll be a newbie and your experience will play a minimal role, if any. You´ll start a new life, professionally speaking, so companies will consider you in the first step as a trainee.

Regarding ale idocs

Hi....
Please send some FAQ'S regarding ale,idocs
thanks
k..swaminath

Hi,
plz go through the 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
Reward points if u find useful.
Regards,
Nagaraj

New to SAP XI BPM scenario File -- RFC -- File

Hi All,
I am new to SAP XI BPM,
My Scenario is : the input parameter for the RFC is sent through a file and the response from the RFC comes into XI which is then written into a file.
Here my dought is How many Container I have to create... and tell me what is use of Container...
Thanks & Regards
Siva

Well in short I would like to say is
A Conatiner is like a table whose structre is having two fields namely ELEMENT and VALUE so it is nearly similar to decalring variables in the general programming , but here in the workflow terms we call them as Container elements. and Conatiner is a place where all the defined variables are stored with Name/Value pair.
Now coming to the issue , the file which is imported from XI make sure that it has the structure as Name//Type/Value
Count the number of lines and create the conatiner dynamically by using the class CL_SWF_CNT_CONTAINER from the ABAP program it has lots of methods check it .

New to SAP...Doubts regarding ALE.

Similar Messages

Maybe you are looking for