ALE Process And regarding material

Hi,
I want learn about ALE's In ABAP . So pleasesend me the process of ALE and the regarding material.

Hello Nagaraju,
The following links will give you complete idea about ALE,
<a href="http://help.sap.com/saphelp_46c/helpdata/en/c9/d97749ae0311d1a5120060087832f8/frameset.htm">ALE in Business Process</a>
<a href="http://help.sap.com/saphelp_46c/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm">What is ALE and how it works?</a>
Hope this helps.
Regards
Arif Mansuri

Similar Messages

IDOC Process And regarding material

Hi,
I want learn about IDOC In ABAP . So please send me the process of IDOC and the regarding material.

Check out the following links:
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
http://www.erpgenie.com/sapedi/idoc_abap.htm#Updating%20IDoc%20data%20in%20segments
http://help.sap.com/saphelp_47x200/helpdata/en/78/21750b51ce11d189570000e829fbbd/frameset.htm
Please do assign points if useful
Regards
Aravind

Can any one Provide BW380 - (Analysis Processes and DataMining) Material

Hi friends
Can any one Provide <b>BW380 - (Analysis Processes and DataMining)</b>
Material (either pdf or ppt).
Thanks & Regards,
Suresh

Hi Suresh,
try this links.
http://help.sap.com/saphelp_nw04/helpdata/en/49/7e960481916448b20134d471d36a6b/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/31/555a421b5ec153e10000000a1550b0/content.htm
hope it helps,
regards,
Parth

Exact process flow for   Material management (MM) and UI Tcodes.

Hi Gurus,
Could any one tel me Exact process flow for   Material management (MM) and UI Tcodes.
ALL   BAPIs for   MM module.
Thanks in Advance.

hi,
Check the threads:
MM flow
MM-Process
For tcodes:
TCODES IN MM
TCODES IN MM
Hope it helps..
Regards
Priyanka.P

[HELP] ALE inbound process and Workflow handling problem

Hello,
first of all, i have to apologize about my english level. I will try to explain my problem (thanks for your patience ).
Well, I'm implementing an ALE inbound interface. My development at this point are:
- Customer Idoc Inbound function (with correct interface).
- Customer Basic Type
- Customer Message Type and correct assignment to the Basic Type (Tx WE81 and WE82)
- Customer Object Type (Subtype of IDOCAPPL)
- On BD51 I put "1" for my function.
- On WE57 I put this:
Processing by --> My function and type "F"
IDOC type --> My Basic type (without any extension)
Message --> My message type (without any message code or msg. function)
Object --> My object type (subtype of IDOCAPPL)
Direction --> "2" (Inbound)
- I created a process code for this interface (on WE42):
It is processed with ALE service and by a function module (my function).
On "Module(Inboud)" part I put my function and maximun number of repeats "0". On IDOC part I put my Object type with start event "INPUTERROROCURRED" and end event "INPUTFINISHED".
On application objet I put my Object type.
Rests of fields are blank.
- I defined a partner (WE20) with this new message type and process code.
- Also I created a Task (PFTC) for handle exceptions in inbound process. It has a rule for agent determinate.
I think it is all.
My problem is: when I process an IDOC (from WE19 for example) and it gets 51 status (error), it has to launch an event that trigger my task, is this way? Well I'm not getting any event.
I have all Workflow customizations OK (in this systems are running some Workflows).
In my function code, when I detect any error I put an error in the status table and put in WORKFLOW_RESULT the number '99999'.
Why I'm not getting any event? What I'm doing wrong?
Thanks in advance. Regards.

Hello again,
finally I've solved the problem. The solution for me, was a config on tx. WE42 and some missing code in the function, I only fill WORKFLOW_RESULT with '9999', but I didn't add any register to RETURN_VARIABLES table.
Regards.

PROCESS AND STEPS OF CONFIG FOR IMPORT MATERIAL RECEIVED AND SALE TO CUSTOM

Hi,
We have plan to develop new process is import the material at plant then repack the material in different size and sale
the material to customer.
I am not fully aware of entire process of MM/FI/SD integration part and process steps.
Can anybady help me to provide Entire process and steps of transaction and config process ?
Thanks in advance
Regards
Tarunkumar

You are asking almost the entire configuration of MM/SD/FI which is not possible. Please describe your process where you need to answer for the following:-
a) whether the import material would be sold to domestic customer
b) whether the import material would further be processed in a plant
c) whether the import material would be cleared at domestic customs
For each and every above question, you need to follow a different configuration in SAP. Also first search the forum based on your current scenario and wherever you are unable to proceed further, please post that issue only instead asking for entire configuration.
thanks
G. Lakshmipathi

Reg. Process cost and raw material cost added

Dear Friends
Please consider our below scenario
PO is created and stock is maintained in unrestricted (Raw material)
and then Production order is created for Cut pcs and Raw material is issued to production order through 261 mvt type
next Cut pcs is received against the production order through 101 Mvt type. Now operation cost is not added with the Raw material cost, only the Raw material cost is represents in MIGO-> FOOTER - QUANTITY->Quantity in LC field. What to do to calculate the process cost too.
When we receive the cut pcs what we attached as component to the cutpcs's cost is calculated, the charge for Cutting is not calculated. we want both cutpcs charge(10.00 per pc)+component cost(raw mat. 180.00 per 1 kg)
Cut pcs 10 pcs * 10 Rs = 100 Rs
Raw mat 10 kg * 180 Rs = 1800 Rs
the total cost is 1900 Rs should come in that field
Thanks
Rajakumar.K

Please give solution
Thanks
Rajakumar.K

CO and Process order without material using T. Code CORO

Hi
We need to use Process Order without material functionality for recording "changeover" time and cost (i.e. setting up process for production of other material in a production line).
For this purpose we have configured a separate process order type. We have created a separate activity for Changeover and planned rates using KP26.
Now we create Process Order without material using T. Code CORO and confirm it using COR6N. On confirmation system successfully credits Cost Center.
We need to know:
1) whether we should settle the process order as well or no need to assign settlement profile to Order Type
2) Or should we run Cost Estimate first.
Plz help, if any have idea

Thank you all for your valuable input.
Srinivasa, your suggestion is very good, especially when calculation of variances/WIP is required. But again as there is no cost relevant material where the WIP/Variances will be settled during settlement process?
1) PP need to create process order without material because changeover cost should not be charged to either material and capacity hours are consumed during changeover. 2) CO need to identify the cost of changeover which should be charged to cost center. So far we have achieved both of these two objectives by the following activities:
Creation of Process Order without material using CORO T.Code say 3 hours of changeover occurred we create order with quantity of 3 Hours. And confirmation of activities quantity 3 using COR6N so cost center is credited by 3 x rate per hour. As there is a separate Process Order type for Changeover we can identify changeover quantity and cost in a given period.
After contributors feedback in this thread I have come to conclusion that I don't need to assign Settlement Profile and PA Structure to Changeover Process Order type. So no need to run Process Order settlement. As there is no specific required for Changeover WIP/Variances as well.

Regarding scripting in adobe HCM process and forms

Hi Gurus,
I am working on adobe HCM process and forms. Configuration has been done for HCM process and forms and I am getting the scenario stage level in the forms based on which I will give the visibilty to differenct levels of approvals in the form.Scripting has been done for that.
When form is initially loaded, I am making invisible some of the fields. On choosing the drop down the value that I make invisible is visible again. I found that Scenario stage that I bound to the form attribute is getting cleared off, when drop down event is called. Drop down event calls the generic services to fill the drop down values. Drop down used is from ISR Controls from the library.
The scripting that I used in the drop down event is as belows
if (xfa.form.data.Page1.FORM_SCN.rawValue == "INIMGR_LVL1")
xfa.form.data.Page1.DE.DEContent.HR_VIEW.presence = "invisible";
xfa.form.data.Page1.FORM_SCN.rawValue this is getting cleared off. Form SCN is the field in the form where in which I bound the attribute scenario stage.
Pls help me on this.
Regards,
Krishnan Paramasivan

Solomon,
Thanks for the earliest response. can you explain me in detail. Where to check/select the form scenario stage field to be passed over. In scripting the coding written as below:
xfa.record.CONTROL_PARAM.ISR_EVENT.value = "DD_GET_POSITION";
ContainerFoundation_JS.SendMessageToContainer(event.target, "submit", "", "", "", "");
DD_GET_POSITION is the event created in generic services and used in the user events in the form scenario stage in HRASR_DT.
Any further guidance on this ?
Thanks in advance.
Regards,
Krishnan

Regarding HCM Process and forms Workflow

Hello all,
I am working in HCM process and forms workflow. In that workflow, there are three levels. First and second level is approved by the respective managers. I am using the Standard TASK TS17900100 in the 3rd level. In which the final level has Send, withdraw, "BACK TO AUTHOR" option. When I click on Send button the PROCSTATE (workflow container element) status getting changed to Processed and the workflow getting Completed.
But when I click on "BACK TO AUTHOR" button the PROCSTATE status is not getting changed from "APPROVED" to "BACK"?
Any clue on this what could be error ?
Thanks & Regards,
Krishnan

Friends,
In the Workflow ,there is the binding for "Processor Role" between Workflow Container and Task Container. I removed this binding as it is not required. Now on click of "Back to Author" in the final stage the work item is moving to Inititor.
Thanks & Regards,
Krishnan

Regarding attachment handling in HCM process and forms

Hi Experts,
I have developed one process and forms for termination process in which i am using "SFREEATTM" as an attachment.
the process will flow like this.
1) HR Business Partner raise a Termination Form for an employee and submit the form which will route the form to HR Admin with the help of workflow.
2)HR Admin access the form and adds a text file attachment to the form and submits it to the manager.
3)Manager access his inbox and displays the form but HE IS NOT ABLE TO SEE THE ATTACHMENT MEANS ATTACHMENT IS NOT COMING HERE SOMEHOW MISSING .
Could you to please help me why the attachment is not coming to the manager though i already mention in my scenario step as DISPLAYED ONLY as an attachment attributes..
BR
Rajat.

Hello,
Please check the form scenario configuration, where the steps and attachments are configured. I think for the manager step, the attachment option is not configured.
As a result , the attachments are not visible at this stage.
Hope this helps.
Best Regards
Saujanya

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Relation of ALE , EDI and idoc

HI
     what is relation of these ALE, EDI, IDOC , i know the definition of these , i want know ( while the transfer of sap to sap ALE tool is used ,) where this idoc is used ,
regards
shivaji

Hi Shivaji,
What is EDI?
Electronic Data Interchange
     The computer-to-computer electronic exchange of machine processable business documents in a standard format
     An electronic alternative to paper, fax, and phone-based transactions used by companies to communicate with one another
Purpose:
     Allows for better time management and relieves the entering of duplicate information while cutting down on discrepancies and human intervention.
     The Electronic Data Interchange component in Sales and Distribution consists of an Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
     send messages (outbound processing) such as an order confirmation through Electronic Data Interchange (EDI)
     receive messages (inbound processing) such as a sales order through EDI
EDI:
     What?
     The technology of transmitting documents electronically
     Why?
     For Electronic Data Interchange between a company and trading partners
     How?
     By means of an electronic document - the IDoc
From the SAP side, the EDI interface is based on IDoc technology, which is independent of
EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem.
Synchronous Remote Function Call (RFC) is implemented to define the time of transfer for a
file between the two systems. The following data can be transferred using the EDI interface:
Outbound Idocs: IDocs are transferred from the R/3 System to the EDI subsystem.
Inbound Idocs: IDocs are transferred from the EDI subsystem to the R/3 System.
Status report: The EDI subsystem sends a status report to the R/3 System on the progress of
the processing of the outbound Idoc.
Contents of IDOC
The data in every IDoc is exchanged between the SAP system and a subsystem in the following three record types, irrespective of the IDoc type:
     Control record (Table: EDIDC): Contains information about Sender and Receiver. There is only one control record per IDoc. It consists of
IDoc Number
Sender and Receiver information
IDoc Message Type* / Port.
IDoc Type / Direction / Current status / Partner No / Partner Type (Vendor/customer)
     Data record (Table: EDIDD): Contains the message to be exchanged between Sender and Receiver. An IDoc can contain multiple data records, as defined by the IDoc structure. Data records store application data such as purchase order / sales order header information, sales order details like sales doc #, Material / Qty and other relevant information.
     Status record (Table: EDIDS): Contains Status of IDoc at various stages, during the transmission of IDoc between Sender and Receiver. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process like status code, date and time at every stage
Know Me
Basic Type: The form of IDOC type that is originally created in the system. Like ORDERS01 is a basic type IDOC for order messages. It is using the basic types only you would be able to enhance them to suit new requirements within the same IDOC structure. Any enhancement to the basic type IDOC will produce an Extension IDOC that would be more or less similar to the basic type with some new additions (of segments or fields). Here, I would go on to say that IDOC type and Basic type is the same thing that would be referred to interchangeably.
Message type: Again, obvious from the name, its the message that is being conveyed. A message type is assigned to the Basic type. Here, logical messages are assigned to the basic type to reflect a business message being transacted. For example, ORDERS is the message type for a purchase order sent by buyer to vendor. The use of which Basic type in this message will differ from buyer to vendor. Basic types used for ORDERS are ORDERS01/02/ etc...Also, one may come up with a custom built IDOC type (or basic type as you can say)...But it is essential to associate a message type with a basic type IDOC. This feature will enable the same IDOC type to be used for a related message. For example : ORDERS01 can be used for message ORDERS for posting a order, the same IDOC can be associated with message ORDCHG to indicate that the message is an order change and so the processing of this IDOC will change accordingly.
IDoc Type:
     Defines the structure of data records
      IDoc Type is used to understand the message in string form available in the data records.
      IDoc type is version dependent i.e an Idoc type can be used only in versions in and above the version in which IDoc is released.
      Transaction WE30 is used to define and release IDoc Types
      Newly created Idoc is a BASIC IDoc and modifications
             (Additions of segments) to IDoc after it has been released can be done by creation of extension      of IDoc.
      IDoc type can be defined by structuring Segments
Function Module: The most important player in the IDOC processing. This is nothing but an ABAP program to process the IDOC. SAP has supplied function modules to process all standard basic IDOCs and messages. A function module is determined based on the Basic IDOC type and the message type (also message code). So from the above descriptions about basic and message type, the combination of two would primarily determine which IDOC will process this idoc. As an instance, ORDERS01 with message ORDERS is configured to be processed by FM IDOC_INPUT_ORDERS. Similarly, ORDERS01 + ORDCHG will be processed by IDOC_INPUT_ORDCHG. Likewise, you can see all associations in WE57 for inbound. For out bounds, you would refer to process codes (WE41).
Segments: The idenfiers in the IDOC structure which indicates the data, their level, state of occurrence....You can take them as records in the IDOC. Each individual segment will come to you as a record in the IDOC. (Go to EDID4, provide an IDOC # and it will list all included segments as records.) Segments are logically nested to indicate various levels of data (header, item etc).
Qualifiers: Inside the segments, there are fields that can carry actual data often signified by use of qualifiers. A qualifier for a segment field would provide the exact meaning of the data. For example, E1EDK03 segment is configured for dates related data. Segment field IDDAT qualifies the date type and the DATUM field gives out the actual date. So you may see a date qualified as 002, which can be interpreted as requested delivery date. Likewise you can see all qualifiers and their meanings in the associated segment fields in SE12. Give the segment name and go to the domain the ranges for the ID fields.
How EDI Works
Sending Data
     Computer system serves as a data repository.
     EDI extracts information from existing computer applications.
     Transmits paperless, computer-readable documents via telephone lines.
Receiving Data
     Fed directly into a computer system.
     Automatically processed and interfaced with internal applications.
Processing Time
     Accomplished in minutes.
     No re-keying.
     No paper shuffling.
     No attendant costs of manual document processing and delivery.
What is the difference between ALE, EDI, IDocs and BAPI?
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
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.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
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, RFC 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.
1.     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.
1.     By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.
IDoc Interface/ALE
Purpose
The IDoc interface exchanges business data with an external system.
The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.
The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.
You need the IDoc interface in the following scenarios:
Electronic data exchange (EDI)
Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc
Application Link Enabling (ALE).
Application Link Enabling (ALE) is a technology to create and run distributed applications
Hope this would help you.
Reward points if helpful.
Vamsi.

FB05 - trans to be processed and first line item PK for doc type

Hi all,
Me quite confused of the entry for the following document type in FB05
DG - cust credit memo
DR - cust invoice
SA- gl acc doc
SB - gl acc posting
KG - vdr credit memo
DZ - customer payment
Need the help to let me know for document type above, what radio button to choose in transaction to be processed and also what posting key use at first line item.
Also if i choose the wrong transaction to be processed radio button, any impact?
thanks
rgds

Document type is primarily used to distinguish different various types of transactions. Ultimately, there are only two effects in accouting - debit and credit. Thus, doc type helps distinguish btw various types of accounting entries. It also controls certain field status while document posting and also drives the number range for the accounting document.
Posting keys determine whether a transaction will be a credit or a debit. They also have an influence over the field status of the document entry screen. Posting keys are broadly divided into those belonging to
Customer                             - Acct type C
Vendors                               - Acct type V
GL                                       - Acct type G
Fixed Assets                        - Acct type A and
Material Mgmt. transactions   - Acct type M
For each account type there are both debit and credit posting keys. You can clik on F4 on the posting key field and see the various entries. You will understand.
Thus, which posting key to enter depends on the transaction you want to enter.
Regards,

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

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

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

ALE Process And regarding material

Similar Messages

Maybe you are looking for