ALE interface with BAPI

Hi,
Am trying to create generate ALE interface for a BAPI(BDBG). After the creation an error comes
There is no entry in the object directory (TADIR) for R3TR TABL Z1BUSINESSPARTNERERM_CREATE. (representative error mess)
Can anyone help in resolving the same?
Thanks and regards

Hi Saurabh,
This type of error occurs when you have to do some changes in standard table. Can you check whether you have to maintain this perticular entry
"Z1BUSINESSPARTNERERM_CREATE" in a perticular table ?
Allot proint if my post helps!!
Best regards,
Vikash.

Similar Messages

Making BDBG Easy (Generate ALE Interface for BAPI)

Making BDBG Easy
Transaction BDBG is used to generate an ALE interface for SAP standard or custom developed BAPIs. Once a BAPI is given an ALE interface, it can be used in LSMW for migrating data or just as another IDoc. Quite a few SAP standard BAPIs cannot be used in LSMW as they do not come with an ALE interface. OSS note Documentation on Transaction BDBG (note number 125776) details the necessary steps to use transaction BDBG but it does not comprehensively cover the technical issues that one may encounter in order to create an ALE interface.
BAPI_ACTIVITYCRM_CREATEMULTI, which is used to create Activities in CRM, will be used to illustrate a step-by-step approach to using transaction BDBG.
Go to Object Navigator (transaction SE80) and create a bespoke function group, we will call ours Z_CRM_ACTIVITY. Activate it.
Then go to Function Builder (transaction SE37), and copy the BAPI to a bespoke function module. Thus, BAPI_ACTIVITYCRM_CREATEMULTI is copied to Z_BAPI_ACTIVITYCRM_CREATEMULTI and assigned to the function group that we created in the previous step Z_CRM_ACTIVITY. Edit the bespoke function module, go to the Attributes tab, and release the function module (Menu Path Function Module >> Release >> Release). Now activate the function module.
IDoc segment types have a maximum length of 27 characters. Each associated type for the Parameters (tabs Import, Export, Changing, and Tables) in a BAPI becomes a segment in the IDoc. Thus, an associated type in a BAPI cannot exceed 27 characters. During the ALE generation process anything beyond the 27th character gets truncated. This leads to more than 1 segment being called the same, and as a result an error occurs when the ALE interface is generated in the final step as an IDoc cannot have the same segment twice.
Eg: Table parameters DATE and DATEX correspond to types BAPIBUS20001_APPOINTMENT_INS (28 characters long) and BAPIBUS20001_APPOINTMENT_INSX (29 characters) respectively.
Also, a developer does not have the option to reduce the segment name during the ALE generation process. So in order to have an error free ALE generation happening in the end, bespoke associated types need to be created and assigned to our bespoke BAPI.
Go to ABAP Dictionary (transaction SE11), and create ZXXXXXXXXXXXXXXXX data types for the structures in the BAPI that are greater than 27 characters. Activate all these bespoke structures.
Bespoke structures ZBAPIBUS20001_APP_INS and ZBAPIBUS20001_APP_INSX can be used in lieu of the standard SAP ones for parameters DATE and DATEX. The same correction method needs to take place for other excessively long types, like the types being referenced by LOCATION and LOCATIONX.
Go to Business Object Builder (transaction SWO1). A search for Activity as the short description produces a few hits. After examining all the objects returned in the hit, we see that BAPI_ACTIVITYCRM_CREATEMULTI belongs to 2 Business Objects - BUS2000110 (CRM Activity) and BUS2000126 (CRM Business Activity).
Copy either of these objects to a bespoke object ZXXXXXXXXX, we will copy BUS2000110 and rename it to ZBUS200010, program RBUS2000110 should also be copied to a Z version (ZRBUS2000110), and the object name can be changed to Company Name (eg: XXX) followed by ActivityCRM (XXXActivityCRM).
Now we edit our bespoke object, and create a method for it by placing the mouse cursor on methods in the object type tree and clicking the create button on the menu bar.
A pop-up appears on the screen with the following text
Create with function module
as template? 
After clicking on Yes, another pop-up asks for a function module to be entered, enter the bespoke function module Z_BAPI_ACTIVITYCRM_CREATEMULTI here and click the tick button.
Accept all the default values in the next pop-up Create Method: Method Properties, and do the same for the next pop-up Create Method: Create Parameters. In the next pop-up click Yes to the question
Method ZBAPIACTIVITYCRMCREATEMULTI not
yet implemented
Do you want to generate a template
automatically for the missing section?
Double-click on the newly created method and go to the ABAP tab, the Function Module option will be selected as the default, make the API function as the default and click OK. Generate the business object.
Now, click on the method of the object and release the method (Menu Path Edit >> Change Release Status >> Object Type Component >> To Released). Double-click on the method to confirm that the Status is released.
Save all the changes made, and Back out of the Edit mode and go the main Business Object Builder screen. Re-generate the business object. First implement, then release the main object ZBUS200010 (Menu Path Object Type >> Change Release Status To >> Implemented, then follow the same menu path and click on Released).
Go to the BAPI Explorer (transaction BAPI), click on the filter icon on the menu bar, and select radiobutton All. Click on the alphabetical tab. Look for XXXActivityCRM in the list. Release status should be Released for this object.
Now we should be able to generate the ALE interface for the BAPI. Execute transaction BDBG, enter the bespoke object (ZBUS200010), do a drop down on the method field and select the bespoke method from the list. Click on the create button on the menu bar. In the first pop-up accept Message Type ZBAPIACTIVITYCRM and click OK. In the next pop-up the following values should be there by default
IDoc type ZBAPIACTIVITYCRM01,
ALE Outbound Processing
Function Module ZZ_ALE_ACTIVITYCRM_CREATEMULTI,
Function Group Z_CRM_ACTIVITY, and
ALE Inbound Processing
Function Module ZIDOC_INPUT_ZBAPIACTIVITYCRM,
Function Group Z_CRM_ACTIVITY.
The option Call in update task should be ticked.
Now our BAPI has an ALE Interface to it and can be used in conjunction with either the BAPI or IDoc option in LSMW. The default values for an IDoc Inbound Processing should be maintained in order to use the bespoke BAPI / IDoc.

Great

Tcode BDBG - Generate ALE Interface for BAPI

Hi All,
I'm trying to generate an ALE interface for the BAPI - BAPI_BUSPROCESSND_CREATEMULTI for my LSMW project, for which I have created a bespoke object in SWO1 (ZBUS), but each time I try to generate the ALE interface for the BAPI I get the error as follows -
Segment Z1BPBUS20001_HEADER_INS is used multiple times in IDoc types
Message no. EA799
Diagnosis
Segment type Z1BPBUS20001_HEADER_INS is used multiple times in the IDoc type. A segment type may only be used once in each IDoc type.
I agree, segment BAPIBUS20001_HEADER_INS is used more than once in BAPI_BUSPROCESSND_CREATEMULTI for the HEADER and CREATED_PROCESS tables, so is there any alternate solution to it?
I have also tried running BDBG for BAPI_ACTIVITYCRM_CREATEMULTI, and I get athe same error message as above for the segment - BAPIBUS20001_APPOINTMENT_INS - but I cannot see this segment being used anywhere else except for tables DATE.
Kind regards,
Arijit Das

Hi Suresh,
thanks for your reply.
Method of BAPI has not been deleted,
but message type, idoc type and FM for Outbound processing.
These objects are within SAP namespace, so recreation will not work.
Regards
rea

Generate ALE-Interface for BAPI

Hi community,
in transaction BDBG i deleted the interface for object BUS2012 Method CreateFromData by mistake.
Can anybody provide solution on how to reset the interface?
IDOC interface:
message type: PORDCR
IDOC-Type: PORDCR05
package: MEW
ALE Outbound Processing:
FM: ALE_PO_CREATE
FG: MEWP
ALE Inbound Processing:
FM: IDOC_INPUT_PORDCR
FG: MEWP
Regards
rea

Hi Suresh,
thanks for your reply.
Method of BAPI has not been deleted,
but message type, idoc type and FM for Outbound processing.
These objects are within SAP namespace, so recreation will not work.
Regards
rea

ALE INTERFACE BOR KNA1 error generetion in transaction BDGD

Moderator message: Do not use the word "urgently" in your posts. It is generally considered quite rude to do so. I have edited the subject.
Hello! i would like to implement ALE interface of the BAPI BAPI_CUSTOMER_CREATEFROMDATA1 (business object KNA1) to use it in transaction LSMW but until i generate the interface using transaction BDGD the program block the generation and give me the follow error:
Segment Z1BPKNA105 is used multiple times in IDoc types
Message no. EA799
Diagnosis
Segment type Z1BPKNA105 is used multiple times in the IDoc type. A segment type may only be used once in each IDoc type.
What i have to do for resolve the error and generate ALE interface of BAPI BAPI_CUSTOMER_CREATEFROMDATA1???
HELP ME THANKS!!
Edited by: Matt on Nov 7, 2008 5:25 PM
Edited by: Matt on Nov 7, 2008 5:25 PM

>
Matt wrote:
> What would you like me to change it to?
I was going to add a "Too late ;-)" but it probably doesn't matter now
Rob

BAPI to ALE interface

Hi All,
I'm trying to generate an ALE interface for the BAPI -
BAPI_CASE_CREATE for my LSMW project, for object SCASE , but each time I try to generate the ALE interface for the BAPI I get the error as follows -
Segment 'SAGMENT NAME' is used multiple times in IDoc types
Message no. EA799
'Segment type is used multiple times in the IDoc type. A segment type may only be used once in each IDoc type'.
Please Reply ASAP

Hi,
You can use any middle ware(webmethods/EAI etc) which can invoke an RFC enable FM/BAPI...
You need to do an ALE here..
Since most of the BAPI have the return tables which stores the error or sucess messages you can use the after invoking the FM that will response the middleware(Synchronous method)..
Hence the return tables store the errors which can be used, But if you want to store those errors in SAP then better create a custom table and update the same whenever the error occurs..(for this u can create a wrapper of the std Fm that you use and implement the logic for updation of errors/custom table)
Hope this helps you
regards
shiva

Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify

Hi All
    I am learning XI and the difference between " ALE, IDOC, RFC, BAPI, BADI "
    Not clear and when to use what and how in point of XI ?
   Pl..clarify me
Adv..thanks and points
--- Rakesh Behera

Hi
This will expalin you every thing ...pl..go through
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.
I hope this will help you to understand the difference bet..those
regards
--- prasad

Different between ALE, IDOC and BAPI?

Hi Folks,
What is the different between ALE, IDOC and BAPI? and send me the following steps?
Thanks in advance.
Siva

Hi,
please read the below lines.
ALE
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
BAPI
BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.
Pros and Cons for both BAPI and Call Transaction
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others.
You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
This is just from my experience working with both BAPI and Call Transaction. I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed.
Regards,
Anki Reddy.

Ale,idocs,edi,bapi,badi

Hi Guru,
Can u give me the detail idea and configuration steps in a sequence of the following -ALE,IDOCS,EDI,BAPI,BADI
your perfect answer would be very helpful and i will cosider u as a real hiro in sap abap in my mind and heart

Hi Manas,
EDI
EDI stands for Electronic Data Interchange.It is mainly an interface which acts as a moderator between SAP and non SAP system.EDI is used to transfer Datas to R/3 from NonSAP system or Other SAP system.
EDI uses IDOC as its interface component.Which mean EDI is a concept and IDOC is like protocol.
EDI is configured in the R/3. It has Outbound folder and indboud folder.
Outbound folder:This contains the data to be send to the nonSAP system
Inbound folder:
This contains the data from the nonSAP to R/3 or SAP system.
status processing
This holds the status of message from SAP to NonSAP and from Non-SAP to SAP. So that if any error occurs in transfereing Message it is easily traced out.
You can refer from this sites
Check the following links
See the below links
SAP XI supports EDIFACT
How to get started using Conversion Agent from Itemfield
More on the SAP Conversion Agent by Itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
SAP XI supports EDIFACT
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Hope this will help you...
Regards,
Nitin.

ALE interface programing

hi experts,
whtat is ALE and why we r using ALE.please give the
steps with example.
regards,
cnu

Check this questions u may get ur answers.
1. What is ALE?
Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.
In a single SAP system different applications are integrated via a single database (e.g. finance, sales, production, human resources). However, many companies do not have just one integrated system but a distributed environment with different applications running on different systems. To run the whole business in such an environment the distributed applications have to be linked. This can be done through Application Link Enabling (ALE).
ALE provides distributed business processes that can be used to link the applications on different platforms. There are some ALE business processes delivered in the standard SAP system. Furthermore, there are tools that can be used to change the existing ALE business processes or to implement new distributed business processes.
Besides the business processes there are special ALE services that are required to set up and control a distributed environment. These services include a distribution model, business object synchronization and tools for monitoring or error handling.
ALE is a major part of SAP's Business Framework Architecture. Besides the basis middleware, that provides the communication between components, and the interfaces (BAPIs), ALE business processes and ALE services enable the cooperation of the single components within the framework. That makes ALE the glue of the Business Framework.
2. What are the benefits of ALE?
With ALE companies get the opportunity to improve business performance and to solve organizational or technical issues.
Through distribution you can decentralize your business, enabling local units to operate independently from each other. This flexibility enables the local units to return better business results than in a centralized environment. They have the necessary flexibility to optimize business processes in different organizational units and can ensure that information systems can handle the speed of change in rapidly expanding markets. Distribution allows a high level of freedom, provided that this level of freedom has been clearly defined.
On the other hand, some companies, that already have a distributed organization with different computer systems in the local units, have the opportunity to link their units through ALE business processes. This enables them for example to provide a 'one face to the customer' approach. Another area that can benefit through ALE are virtual organizations (partnerships between independent companies, joint ventures and mergers and acquisitions).
Of course, in many cases an integrated solution based on a single system is not possible at all. Some applications used by a company can not run on the same computer system. This includes legacy systems or complementary software. It may also be possible that a company uses different SAP industry solutions or specific country solutions, which do not run on the same SAP System. If these applications run on different systems they can not be linked by a central database but have to use a special integration mechanism like ALE. In this way ALE also links SAP Core Systems to other SAP components like CRM, Business Information Warehouse or APO.
Besides the benefits of having an improved flexibility in setting up the whole business processes, ALE may also reduce costs, in particular costs of upgrading. If the whole business is run on one integrated system you have to upgrade the whole system, even if only one part of your company (e.g. human resources) requires an update. So the entire company is affected by the upgrade project and all users have to be trained for the new release. Within a distributed environment with release independent interfaces, like those provided by ALE, you can focus the upgrade project on that part of the company that has to be upgraded. The other parts of the company are not involved and need no training. This can save a lot of money. Furthermore, existing investments are protected.
Another cost factor for distribution might be communication costs. For an overseas connection it can be more expensive to provide online access to one central system (T1) than to connect distributed systems to each other (64K line).
There might also be some technical reasons for distributed systems. If some parts of the business have special requirements for security of data access (e.g. human resources), this can be set up much safer on a standalone system, which is, however, linked to other parts of the company through distributed business processes. A similar example is high availability. High availability is usually required by the operations part of the company (production, logistics) but not by other areas (e.g. financials, human resources). In a distributed environment high availability can be set up for specific parts of the environment instead of for the whole business. This can also reduce costs.
In a distributed environment you can not decrease the overall workload of the systems but you can separate the user workloads on different systems. Through this scalability you can improve performance. Another benefit of distributed systems is that if a technical failure occurs on one system, all other systems continue to operate. Only a small part of the business is disrupted by the error. On one central system such an error would disrupt the entire business.
3. When should ALE be used?
Besides the benefits of ALE there are also reasons not to distribute:
The functional scope in a distributed environment is restricted. Not all functionality that is available in an integrated SAP system can be used with distributed systems in the standard yet. Although ALE provides tools to create new ALE business processes or to enhance existing business processes, this does involve additional expenditure.
Each company needs some organizational standards and data harmonization. In a distributed environment less standards are required than on a single integrated system. However, in a distributed environment the maintenance of the standards and the data harmonization is more difficult than on a single system.
The administration of decentralized systems is more expensive. Support and service costs for hardware and software in decentralized systems are higher than these costs in a single centralized system.
ALE should be used in a company if the benefits of ALE for this company outweigh the reasons against distribution. For this you always need to carry out a company specific investigation, in which you also should consider the culture of the company. ALE is good for some companies but not for all.
4. What is the relationship between ALE and Middleware?
Electronic Data Interchange (EDI) is a term for the transfer of business messages between two systems. There are many such messages, the most common of these include a customer sending a purchase order message to a vendor, or a vendor sending an invoice message to a customer. Classic EDI is mainly restricted on the exchange of transactional data, no master data or configuration data. In most cases, EDI replaces the transfer of paper copies of these documents. Via the messages ALE business processes can be implemented between business partners. The EDI messages also use the ALE services.
For the communication between different types of systems special EDI messages are defined as standards for inter company communication. There are many standards for these messages - in the United States, the ANSI X.12 standard is the most prevalent, in Europe, the UN/EDIFACT standard is used. For sending EDI messages the information has to be converted into an EDI standard. With SAP systems this is done by EDI subsystems. This conversion is the only difference between EDI messages and other messages used in ALE business processes. The processing of these messages on the SAP System is the same as the processing of other ALE messages.
5. Which ALE business processes are available?
IDoc Types - Message Types
ALE business processes are integrated business processes that run across distributed systems. This can be two different SAP systems, links between SAP and non-SAP systems, SAP and Web-servers (Internet Application Components) or SAP and desktop applications. The links between the systems may be loosely (asynchronous) or tightly (synchronous) coupled. These business processes are release independent and can run between different release levels of the systems.
Many SAP applications offer ALE distribution processes. The following list gives some examples:
Master data replication (IDoc Types - Message Types - Master Data)
- Material
- Customer
- Vendor
- General Ledger accounts
- Bill of materials
Accounting (IDoc Types - Message Types -Accounting Business Processes)
- Links to logistic systems
- Distributed financial accounting
- Distributed cost center accounting
- Distributed special ledger
- Profitability analysis
- Distributed profit center accounting
- Consolidation
- Treasury
Logistics(IDoc Types - Message Types - Logistics Business Processes)
- Reallocation of materials
- Distribution of sales and shipping
- Product data management
- Purchasing contracts
- Sales and operations planning
- Warehouse management
- Links to warehouse control systems
- Links to production optimization systems
- Links to transport planning systems
Information systems (IDoc Types - Message Types - Logistics Business Processes)
- SAP Business Information Warehouse (BW)
- Exchange of data between information systems
- Web reporting
Human resources (IDoc Types - Message Types - HR Business Processes)
- Human resources as a single component
- Payroll results
- Travel expense accounting
- Links to time collecting systems
However, these standard solutions may not fit 100% for a company. There may be differentiation in the business process or a required distributed business process is not supported in the standard. If this happens, ALE provides tools that can be used to adapt a standard ALE business process or to create a new distributed business process.
6. Which ALE services are available and what do they do?
To integrate distributed systems you need more than a communication infrastructure and interfaces. Some additional services are required that are provided by ALE:
Business process harmonization:
Within system overlapping business processes multiple functions running on multiple systems are involved and connected through multiple interfaces. The processes are combinations of functions (sub-processes) running on the single systems.
(Example: A business process for customer order management involves functions in sales, manufacturing, warehouse management, finance, and so on. It is possible that the sales functions are carried out on another system than the manufacturing, the warehouse management or the accounting. Furthermore, some information exchange with the customer, a supplier or a bank may be involved in the process.)
ALE helps to coordinate the whole business process by defining it within a global model. In this model the business rules for the distribution are defined. Via the model the sub-processes get to know which part of the overall process they have to do themselves and when they have to pass the process over to another system. Through this the whole business process gets harmonized.
Receiver determination:
For distributed business processes a sub-process on one application (client) has to start another sub-process on another application (server). It is important that the new sub-process is started on the right server. Which server is the right one can not be defined by technical values, it depends on the business content of the process.
(Example: A sales system forwards customer orders to two different production systems. To which system a special sales order is forwarded depends on the entries in the sales order (this may depend, for instance, on the ordered material or on the customer). One sales order may also be split into two or more different orders that may be forwarded to different production systems.)
To notify the client which system is the receiver of the communication (server), ALE uses a distribution model. From this model the applications get the information about the right server. There are special ALE BAPIs and function modules available for this. The receiver determination makes sure that the information is sent to the right places.
Business object synchronization (semantic synchronization):
If business processes run across distributed systems, they have to share some data to be harmonized. This is data like business information data, master data or customizing data. If this data is changed in any of the distributed systems, other systems have to be informed about the change. There has to be some kind of subscription of the data.
ALE provides a special service for this data synchronization. This service can detect data changes and distribute the information to those systems that need to know about the change. This service also defines which data is shared. You can determine which fields of a data object shall be common and which fields may vary locally.
Consistency checks:
For a business process running across two distributed applications there has to be some harmonization of the sub-processes in the single applications. For making sure that the sub processes are harmonized there are special ALE consistency check tools. These tools help to find and repair inconsistencies. By this it can be ensured that the whole ALE business process works in the right way.
Monitoring:
For the monitoring of distributed processes it is not enough to monitor all activities on the single systems. The overall business process has to be monitored. The ALE monitoring services provide detailed information about the communication process, the sub-process on the other systems and its results. Database links are created between the business objects in question on the client and the server. This is especially important for loosely coupled applications with asynchronous links. In this case the server can not give return values back to the client directly so that the ALE monitoring is the only channel for feedback.
Error handling:
Another problem with asynchronous communication is error handling. If an error occurs on the server the calling process on the client may have finished already. So the server can not return the error message to the client. A special error handling process required. This process is one of the ALE services. It uses workflow functionality to identify the error and to start the required error handling.
7. Synchronous vs. asynchronous links?
When distributed applications are linked by ALE business processes, the question often arises as to how tight the link should be. Synchronous and asynchronous links have both advantages and disadvantages.
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link. Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client can not be finished (otherwise there would be data inconsistencies).
(Example: There is a logistics system and a financial system. Every stock movement in logistics has to be posted in the general ledger of the financial system. If the link between logistics and finance is synchronous, no stock movement can be recorded in the logistics system if the communication line to the financial system is down.)
Because of this, synchronous links are usually used if the client only wants to get some data from the server and the sub-processes on the server do not have to write any data to the database.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later. The disadvantage of asynchronous links is that the sub-process on the server can not return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
Asynchronous links are used if a synchronous link is not applicable. For the problems with sending return information to the client and with error handling there is some support from the ALE services.
8. Which kind of interfaces do ALE business processes use?
ALE business processes are integrated processes across distributed systems, requiring interfaces between the systems. These interfaces have to be stable to enable the communication between different releases and to reduce the impact of release changes within the distributed environment.
In SAP R/3 release 3.0 and 3.1 ALE uses IDocs as interfaces. An IDocs is a data container for transferring messages asynchronously. They are release independent. Since SAP Release 3.1G BAPIs are a new type of object oriented, stable interfaces that can be called synchronously or asynchronously. Asynchronous BAPIs use IDocs as data containers. ALE business processes can use BAPIs as well. In the future new ALE business processes will use BAPIs as interfaces. But the existing IDocs will still be supported. In time, BAPIs will be created with similar functionality to existing IDoc interfaces.
9. Why does SAP uses ALE instead of database replication or distributed databases?
Database replication is another possibility for doing business object synchronization. However, there are some major disadvantages with database replication. At the moment database replication is database dependent and release dependent within one database. This makes database replication impossible for the use with non-SAP systems and even for the replication between SAP Systems you have to make sure that all systems are running on the same SAP release and the same database release of a single database vendor. Furthermore, with database replication you cannot do things like field conversions or version changes. ALE does not have these shortcomings because it offers application driven data replication independent of the underlying database.
Another technology, distributed databases, is no alternative for ALE at the moment, either. There are some good results of distributed databases available, but the performance is far from sufficient for using it with larger applications like SAP.
10. What is the relationship between ALE and middleware?
For distributed business processes many different services are required. Most of these services are offered by SAP. For some of these services you can also use products that are provided by SAP's complementary software partners or by other companies:
The communication service for doing the pure communication is usually done via Remote Function Call (RFC). RFC is provided by SAP for most platforms both for synchronous and asynchronous communication. There are other messaging systems for the communication service available as well, like IBM's MQSeries. However, the communication between SAP and the messaging system is still done via RFC.
For the serialization of asynchronous communication the RFC provides little functionality at the moment. The serialization has to be checked by the application. ALE offers some support to do these checks. The serialization of the RFC communication will be improved in the future. Serialization services are provided by some of the existing messaging systems, but even they can not guaranty a 100% serialization of the communication, since they use RFC for the connection to SAP.
The monitoring and error handling of the communication is done via services provided by the RFC and ALE. If messaging systems are used for the communication they also offer some monitoring and error handling functionality.
If a non-SAP system is involved in the ALE business scenario and this system does not understand SAP's BAPI or IDoc interfaces, the data has to be mapped to any interface structure that this system offers. For this mapping SAP does not provide a service but it certifies mapping tools from software partners. These tools are called ALE translator. The most known product in this area is probably Mercator from TSI International Software. The same kind of mapping can also be done by 'EDI converters'.
Another type of middleware products offer process ware. This is mainly a combination of the communication service, the mapping service and a set of rules for the mapping. Some ALE translator can be used for this as well.
Receiver determination is one of the ALE services (see above). Parts of this service can also be provided by some of the messaging systems, but you cannot use these systems without using ALE receiver determination.
For the other ALE services like application monitoring, application error handling, semantic synchronization and business process harmonization, there are no middleware products available as a replacement of ALE.
ALE is open for the use of middleware products for the distribution, but in most cases the additional middleware is not necessary. In a communication between different SAP systems usually the use of additional middleware makes no sense at all. For the communication between SAP and non-SAP systems there might be some benefits, especially if the middleware is used at the company already. The only middleware tool that is really required if the non-SAP system does not understand BAPIs or IDocs is an ALE translator.
Regards

LSMW with BAPI for Person's Qualification Profile - BAPI_QUALIPROF_CHANGE

All,
I tried to use BAPI 'BAPI_QUALIPROF_CHANGE' to upload the qualification profile for an employee. The corresponding object type for the function module is BUS7017 (& the method is CHANGE). But in standard SAP, in the initial LSMW attributes screen, it supports only those objects with an ALE interface. But, BUS7017 does not have an ALE interface.
It is possible to create an ALE interface for a BAPI in the transaction 'BDBG'. After creating an interface, I get the business object in the F4 help for the Business object (LSMW attributes screen). But, I get an error in the step 'Maintain structure relations'. It is saying 'target structure could not be found'.
Can you please tell me what I am missing here. Also let me know how to generate a function module for the inbound/outbound processing of an ALE with BAPI?
Thanks in advance.
Regards,
Parvath.

Hi,
Did u get any solution to this . I am trying to upload cost centers and facing the same problem. If you have found any solution , please pass it.
Sutapa

Inbound IDOC FM with BAPI

Hi Everyone,
I need some information about posting an application using inbound IDOC with BAPI. I need to write a FM for
Inbound IDOC with BAPI to post it. Can some one give me direction as where to start as I am new to BAPI.
Thanks in advance.
Regards,
vicky

Hi Vicky,
Please take a look at this link which will show step by step on how to setup inbound proscessing.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Also check this links for sample codes.
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
Hope this will help.
Regards,
Ferry Lianto
Message was edited by: Ferry Lianto

Transport of ALE Interfaces for Function Module

hi,
i have a Z function module, Z business object type and z message type identifying ALE interface.
i need to move all the objects from Dev R3 to QA R3. What are the steps involved?
Thanks,
Tirumal

Hi
While creating a Z function module it will ask you for a change request number. attach it to change request and migrate it to Production.
In case your function group to which you assigned this function module is open then the CTS number will by default come in CTS number field if any exists for the function group. You can now migrate your CTS to production.
Now after assinging function module to a CTS you can be sure that your program for function module and FM both will be migrated. For confirmation you can now check attribuutes section in your function module. it will list the SAP program associated with Func mod , function group to which function module is assigned , package and include programs which needs to be migrated. So you only need to attach a CTS and migrate your CTS.
You can create a Change erquest (CTS) in SE01 or SE10 transactions.
Regards,
Amit.
Please reward any help
Message was edited by: amit bhadauria
Message was edited by: amit bhadauria

Dcs interface with sap pm

Dear experts,
can anyone explain me the basic steps and information regarding dcs interface with sap .
i want to do this sap implementation for the thermal power station. i want to generate notifications and work orders when the parameteres of particular equipment crosses its range.
how the important parameters from the dcs is linked with sap server. how i can get the data from dcs and pass it to the sap system.
can anyone give the helping hand.

Hi,
You can use XI as a connector instead of ALE to connect mySAP ERP to SAP Business One. The DI API is the connector for SAP Business One.
The DI API or Data Interface API is part of Business One and the Business One SDK. B1i exists to easily connect mySAP and SAP Business One without typical coding that would be required simply by using XI to connect with SAP Business One and mySAP. B1i contains all of the connections, pre-defined content, message handling and error correction for common business scenarios to connect these to systems. Without B1i, you have to hand code everything. If you are not connecting with SAP Business One, then you may not have a need or requirement to use B1i. There are more detailed whitepapers here from the SAP Business One main page on SDN. You should have a look at those.
You should have SAP Portal authorisation to access the following info. Go to sevicemarketplace -> smb -> SBO -> Install'n'Updates->Updates->Updates for SAP Business One->SAP Business One Releases prior to 2004->SBO-MYSAP INTEGRAT.TOOLKIT 1.5.
You can find there an presentation how to Integrate SBO with mySAP via XI (https://websmp203.sap-ag.de/~sapidb/011000358700002285912003E.ppt)
Thanks
Swarup

Inbound ALE interface for HR Master and OM data

Dear Experts,
I have a requirement for ALE interface to create and maintain HR master and OM data with the details coming from external HR system and I need to send back the pernrs,position or org. unit created back to external system.I am trying to use HRMD_A message type for this interface which will use FM IDOC_INPUT_HRMD to post the idocs which will update the DB tables of infotypes directly.But in my case i need to create the pernr or position with details coming from external system and send them back.how i can create and catch these details using this standard FM IDOC_INPUT_HRMD?
Thanks a lot in anticipation!!

Hi Ramnaresh,
Did you get the solution for this. we have the similar requirement from people soft to SAP but only one direction.
We are using the IDOC ( IDOC_INPUT_HRMD). It is working fine except for the fields KOSTL (Cost Center), ORGEH (Org Key), SETLL (Job key) in infotype 0001. the values are showing in generated IDOC but not updating the infotype table PA0001.
The functionality is working fine for other fields and other infotypes.
When I debug the program it is dealing with the config table T77S0 parameters: PLOGI , ORGA , Value 'X'.
If we maintain this value, I am getting the below error message.
The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field cannot be maintained in dialog, which means you cannot fill it with data at this point. It is calculated automatically by the system.
If the Config, table parameters are not maintained, then IDOC is in successful state but not updating the cost center in PA0001.
Can you please let me know if you get any solution on this.
Thanks,
Jitender

ALE interface with BAPI

Similar Messages

Maybe you are looking for