ALE interface

Hi, Can anybody suggest me... regarding
while creation of partner profile in to R3 system
or one r3 second one is legacy...
we have to maintain the partner profile explicitly ????
in both the system....
2> for using the model view distribute ? is there any need to transport the modelview... while replicating between development and quality server ???
thanks in advance
Manish

Hey Manish,
You will have to generate and configure Partner profiles in the sending & receiving systems. Follow the flow given below
ALE CONFIGURATION:
SALE - Define Logical System
     - Assign Client to Logical System
     - Define Target Systems for RFC Calls
     - Maintain Distribution Model and Distribute Views
     - Maintain Partner Profile Manually
     - Generate Partner Profiles
     - Check Technical Consistency
IDOC ADMINISTRATION
WE05 - IDoc Lists
WE02 - Display IDoc
DISPLAY STATUS
WE20 - Partner Profile
WE21 - Port Definition
SM59 - RFC Destination
BD71 - Distribute Model
DEVELOPMENT
WE31 - IDoc Segments
WE30 - IDoc Types
WE81 - Message Types
WE82 - IDoc Type / Message
WE57 - Message/Application Object
WE34 - IDoc Styles
WE32 - IDoc Views
CONTROL:
WE41 - Outbound Process Code
WE42 - Inbound Process Code
WE43 - Display Status Record
WE64 - Process Codes
outbound & inbound operations
BD10     Send Material
BD11     Get Material
BD12     Send customer
BD13     Get customer
BD16     Send Cost Center
BD17     Get Cost Center
BD18     Send General Ledger Account
BD19     Get General Ledger Account
If you find this answer useful, please reward me for the same.
Good luck
Karthik Potharaju

Similar Messages

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

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

Testing ALE Interface

Hi Friends,
How do we test ALE Interface.
Please provide me with stpes for configuring the ALE Interface for SAP-SAP,SAP-Non SAP scenarios on Outbound & Inbound Systems.
After configuring,How do we send the data.
<REMOVED BY MODERATOR>
Thanks
Edited by: Alvaro Tejada Galindo on Feb 14, 2008 11:01 AM

Hi Annapurna,
you can try these links as well .
IDOCS:
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE/IDOCS:
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://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
or have a look at this thread..
https://forums.sdn.sap.com/click.jspa?searchID=8882009&messageID=4770944
Regards,
Ramesh.

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

ALE interface generation from BAPI_POEC_CREATE

Hi,
I want to generate an ALE interface from BAPI_POEC_CREATE (object type BUS2201).
FUNCTION BAPI_POEC_CREATE.
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_PO_HEADER) LIKE BAPI_PO_HEADER_C STRUCTURE
*" BAPI_PO_HEADER_C
*" VALUE(I_PO_HEADER_CUST) LIKE BAPI_PO_HEADER_CUST_C STRUCTURE
*" BAPI_PO_HEADER_CUST_C OPTIONAL
*" VALUE(I_TESTRUN) TYPE BBPS_BAPI2091-TESTRUN DEFAULT SPACE
*" EXPORTING
*" VALUE(E_PO_HEADER) TYPE BAPI_PO_HEADER_D
*" VALUE(E_PO_HEADER_CUST) TYPE BAPI_PO_HEADER_CUST_D
*" TABLES
*" I_PO_ITEMS STRUCTURE BAPI_PO_ITEM_C OPTIONAL
*" I_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_C OPTIONAL
*" I_PO_ACCASS STRUCTURE BAPI_ACC_C OPTIONAL
*" I_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_C OPTIONAL
*" I_PO_PARTNER STRUCTURE BAPI_BUP_C OPTIONAL
*" I_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*" I_PO_ATTACH STRUCTURE BAPI_ATT_C OPTIONAL
*" I_PO_ORGDATA STRUCTURE BAPI_ORG_C OPTIONAL
*" I_PO_LIMIT STRUCTURE BAPI_LIMIT_C OPTIONAL
*" I_PO_SDLN STRUCTURE BAPI_SDLN_C OPTIONAL
*" E_PO_ITEMS STRUCTURE BAPI_PO_ITEM_D OPTIONAL
*" E_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_D OPTIONAL
*" E_PO_ACCASS STRUCTURE BAPI_ACC_D OPTIONAL
*" E_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_D OPTIONAL
*" E_PO_PARTNER STRUCTURE BAPI_BUP_D OPTIONAL
*" E_PO_ORGDATA STRUCTURE BAPI_ORG_D OPTIONAL
*" E_PO_LIMIT STRUCTURE BAPI_LIMIT_D OPTIONAL
*" E_PO_SDLN STRUCTURE BAPI_SDLN_D OPTIONAL
*" E_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*" E_PO_STATUS STRUCTURE BAPI_BBP_STATUS OPTIONAL
*" E_PO_ATTACH STRUCTURE BAPI_ATT_D OPTIONAL
*" RETURN STRUCTURE BAPIRET2 OPTIONAL
1) I encoutered a first problem : as you can see, these are two parameters with the same type BAPI_TEXT_I. So it gives an error message during generation in BDBG. I can bypass this error by deleting the second parameter (E_PO_TEXT) in debug. But I don't like this method of course...
2) I have a second problem : the three parameters I_PO_HEADER_CUST, I_PO_ITEMS_CUST, I_PO_ACCASS_CUST are not taken in account in the generated FM (ZIDOC_INPUT_ZPURCHASEORDEREC_C), even if corresponding EDI segments are generated. I needed to add them manually (at the end of the following code) :
FUNCTION zidoc_input_zpurchaseorderec_c.
*"*"Interface locale :
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*" VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*" WRONG_FUNCTION_CALLED
* this function module is generated *
* never change it manually, please! 10.06.2008 *
DATA:
 z1zpurchaseorderec_create LIKE z1zpurchaseorderec_create,
 z1bp_po_header_c LIKE z1bp_po_header_c,
 z1bp_po_item_c LIKE z1bp_po_item_c,
 z1bp_acc_c LIKE z1bp_acc_c,
 z1bp_bup_c LIKE z1bp_bup_c,
 z1bp_bup_c1 LIKE z1bp_bup_c1,
 z1bp_bup_c2 LIKE z1bp_bup_c2,
 z1bp_text_i LIKE z1bp_text_i,
 z1bp_att_c LIKE z1bp_att_c,
 z1bp_org_c LIKE z1bp_org_c,
 z1bp_limit_c LIKE z1bp_limit_c,
 z1bp_po_item_d LIKE z1bp_po_item_d,
 z1bp_po_item_d1 LIKE z1bp_po_item_d1,
 z1bp_acc_d LIKE z1bp_acc_d,
 z1bp_bup_d LIKE z1bp_bup_d,
 z1bp_bup_d1 LIKE z1bp_bup_d1,
 z1bp_bup_d2 LIKE z1bp_bup_d2,
 z1bp_org_d LIKE z1bp_org_d,
 z1bp_limit_d LIKE z1bp_limit_d,
 z1bp_bbp_status LIKE z1bp_bbp_status,
 z1bp_att_d LIKE z1bp_att_d,
* go through all IDocs *
LOOP AT idoc_contrl.
* select segments belonging to one IDoc *
 REFRESH t_edidd.
 LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
 APPEND idoc_data TO t_edidd.
 ENDLOOP.
* through all segments of this IDoc *
 CLEAR error_flag.
 REFRESH bapi_retn_info.
 CATCH SYSTEM-EXCEPTIONS conversion_errors = 1.
 LOOP AT t_edidd INTO idoc_data.
 CASE idoc_data-segnam.
 WHEN 'Z1ZPURCHASEORDEREC_CREATE'.
 z1zpurchaseorderec_create = idoc_data-sdata.
 MOVE z1zpurchaseorderec_create-i_testrun
 TO i_testrun.
 WHEN 'Z1BP_PO_HEADER_C'.
 z1bp_po_header_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_header_c
 TO i_po_header. "#EC ENHOK
 IF z1bp_po_header_c-doc_date
 IS INITIAL.
 CLEAR i_po_header-doc_date.
 ENDIF.
 IF z1bp_po_header_c-pcdat_to
 IS INITIAL.
 CLEAR i_po_header-pcdat_to.
 ENDIF.
 IF z1bp_po_header_c-vper_start
 IS INITIAL.
 CLEAR i_po_header-vper_start.
 ENDIF.
 IF z1bp_po_header_c-vper_end
 IS INITIAL.
 CLEAR i_po_header-vper_end.
 ENDIF.
 WHEN 'Z1BP_PO_ITEM_C'.
 z1bp_po_item_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_item_c
 TO i_po_items. "#EC ENHOK
 IF z1bp_po_item_c-deliv_date
 IS INITIAL.
 CLEAR i_po_items-deliv_date.
 ENDIF.
 APPEND i_po_items.
 WHEN 'Z1BP_ACC_C'.
 z1bp_acc_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_acc_c
 TO i_po_accass. "#EC ENHOK
 APPEND i_po_accass.
 WHEN 'Z1BP_BUP_C'.
 z1bp_bup_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_c
 TO i_po_partner. "#EC ENHOK
 READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
 segnam = 'Z1BP_BUP_C1'.
 IF sy-subrc <> 0.
 APPEND i_po_partner.
 ENDIF.
 WHEN 'Z1BP_BUP_C1'.
 z1bp_bup_c1 = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_c1
 TO i_po_partner. "#EC ENHOK
 READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
 segnam = 'Z1BP_BUP_C2'.
 IF sy-subrc <> 0.
 APPEND i_po_partner.
 ENDIF.
 WHEN 'Z1BP_BUP_C2'.
 z1bp_bup_c2 = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_c2
 TO i_po_partner. "#EC ENHOK
 APPEND i_po_partner.
 WHEN 'Z1BP_TEXT_I'.
 z1bp_text_i = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_text_i
 TO e_po_text. "#EC ENHOK
 APPEND e_po_text.
 WHEN 'Z1BP_ATT_C'.
 z1bp_att_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_att_c
 TO i_po_attach. "#EC ENHOK
 APPEND i_po_attach.
 WHEN 'Z1BP_ORG_C'.
 z1bp_org_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_org_c
 TO i_po_orgdata. "#EC ENHOK
 APPEND i_po_orgdata.
 WHEN 'Z1BP_LIMIT_C'.
 z1bp_limit_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_limit_c
 TO i_po_limit. "#EC ENHOK
 APPEND i_po_limit.
 WHEN 'Z1BP_PO_ITEM_D'.
 z1bp_po_item_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_item_d
 TO e_po_items. "#EC ENHOK
 IF z1bp_po_item_d-deliv_date
 IS INITIAL.
 CLEAR e_po_items-deliv_date.
 ENDIF.
 READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
 segnam = 'Z1BP_PO_ITEM_D1'.
 IF sy-subrc <> 0.
 APPEND e_po_items.
 ENDIF.
 WHEN 'Z1BP_PO_ITEM_D1'.
 z1bp_po_item_d1 = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_item_d1
 TO e_po_items. "#EC ENHOK
 APPEND e_po_items.
 WHEN 'Z1BP_ACC_D'.
 z1bp_acc_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_acc_d
 TO e_po_accass. "#EC ENHOK
 APPEND e_po_accass.
 WHEN 'Z1BP_BUP_D'.
 z1bp_bup_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_d
 TO e_po_partner. "#EC ENHOK
 READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
 segnam = 'Z1BP_BUP_D1'.
 IF sy-subrc <> 0.
 APPEND e_po_partner.
 ENDIF.
 WHEN 'Z1BP_BUP_D1'.
 z1bp_bup_d1 = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_d1
 TO e_po_partner. "#EC ENHOK
 READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
 segnam = 'Z1BP_BUP_D2'.
 IF sy-subrc <> 0.
 APPEND e_po_partner.
 ENDIF.
 WHEN 'Z1BP_BUP_D2'.
 z1bp_bup_d2 = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bup_d2
 TO e_po_partner. "#EC ENHOK
 APPEND e_po_partner.
 WHEN 'Z1BP_ORG_D'.
 z1bp_org_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_org_d
 TO e_po_orgdata. "#EC ENHOK
 APPEND e_po_orgdata.
 WHEN 'Z1BP_LIMIT_D'.
 z1bp_limit_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_limit_d
 TO e_po_limit. "#EC ENHOK
 APPEND e_po_limit.
 WHEN 'Z1BP_BBP_STATUS'.
 z1bp_bbp_status = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_bbp_status
 TO e_po_status. "#EC ENHOK
 APPEND e_po_status.
 WHEN 'Z1BP_ATT_D'.
 z1bp_att_d = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_att_d
 TO e_po_attach. "#EC ENHOK
 APPEND e_po_attach.
*** JSE 12/06/08 segments "forgotten" by BDBG
 WHEN 'Z1BP_PO_HEADER_CUST_C'.
 z1bp_po_header_cust_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_header_cust_c
 TO i_po_header_cust_c.
 WHEN 'Z1BP_PO_ITEM_CUST_C'.
 z1bp_po_item_cust_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_po_item_cust_c
 TO s_po_items_cust. "#EC ENHOK
 APPEND s_po_items_cust TO i_po_items_cust.
 WHEN 'Z1BP_ACC_CUST_C'.
 z1bp_acc_cust_c = idoc_data-sdata.
 MOVE-CORRESPONDING z1bp_acc_cust_c
 TO s_po_accass_cust. "#EC ENHOK
 APPEND s_po_accass_cust TO i_po_accass_cust.
*** JSE 12/06/08
 ENDCASE.
 ENDLOOP.
 ENDCATCH.
As for first point, I don't like this method, because it modifies a generated FM. Is there a way to force generation of this 3 parameters by BDBG ?
3) Considering the risk of overwriting modications in the generated FM, I have these questions : when are regenerated interfaces created by BDBG ? Are they regenerated always manually ? Or are they regenerated during transport for example ?
Thanks a lot for your help.
Julien.

Hi,
Pls see this very useful thread:
Re: 'BAPI_POEC_CREATE' function doesn't work with extended classic scenario
BR,
Disha.
Do reward points for useful answers.

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

ALE Interface Error

Experts
Im trying to generate an ALE interface for BUS0050. The process errors with "Segment ZIBP_0050_ITEM is used multiple times in IDOC types".
I have also tried this using a copy of the Object and get the same result
thanks for your help
Andy

hi, I think segment ZIBP_0050_ITEM is a customize segment which be added by EEWB, right?
Sometime, the problem in EEWB enhance field will impact our idoc generation.
in my opinion, you'd better delete all the customziing idoc type for BUS0050.
Then go to EEWB, delete the custimizing field related to ZIBP_0050_ITEM, and create them again.

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.

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

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

ALE-Interface and batch file

Hi,
So far we have transferred Data from one system to main system through ALE-Interface and Batch file. Now we are thinking to harmonize and optimize this process and run all data transfers though ALE-Interface and eliminate Batch File process.
Can anybody tell me, why the ALE-Interface is better than Batch file for data transfers?
Thanks

Batch file is carried out at offline and at certain time intervals
where as ALE is online transfer and while triggering a particular tcode it can be made to trigger
This is why ALE is best
cheers
S.Janagar

ALE interface to same client - different machines.

Is it possible to create an ALE Interface to the same client(200 to 200) for sample testing or customizing ??
Thanks in advance.

I think this depends on the logical system name of the clients. you can check in scc4.
regards,
martin

OUTBOUND IDOCS PROCESSING ON ALE INTERFACE

Hi experts...
I am working on ALE IDOCS
I have a requirement where i have to convert my outgoing idocs into flat files on my local system
1) How do i create a file port and specify the location(directory)
2) How do i assign this file port to the sending system
3) Where will the idocs be stored ... can i check the location using AL11.
Can anyone send the procedure for the above ..
Also can anyone send me documents on "SAP to LEGACY system Interfacing"
to my mail id [email protected]
Thanks and Regards

Hi Ashok,
Please check this link.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2a1dd5d3-0801-0010-ed8d-bd797ed922cb
open it as PDF.
I think it will answer all your queries....
Dont forget to award points if you get the answer:-)
Regards,
Vinay

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 for Sposnored Class in grants management

Hi All,
Is there any standard interface (ALE/IDOC/PROXY) provided by SAP for sponsored class in Grants Management module.
Thanks,
Swapnil Pawar

Swapnil,
Please see the Function Module GM_SPONSORED_CLASS_CREATE and determine if it works for you.
Thanks
Shyam

ALE interface

Similar Messages

Maybe you are looking for