ALE- BD97

Hi,
In ALE, Transaction code BD97 gets populated when we generate the Model or do we need to configure manually?
Thanks in advance,
Raja T

Hi Raja,
The logical system in QA, is it local logical system?
If it is then it will not bd shown in BD97.
Please check this from online help ... perhaps it may help.
Determine RFC Destinations for Method Calls:
In this section you assign the RFC destinations used for synchronous BAPI calls and for calling dialog methods in other systems.
For further information select "Help -> Application help" from within the transaction.
RFC destinations are assigned to logical systems using a tree graphic that can display all the logical systems of the whole system. The RFC destinations assigned to each logical system can be displayed.
RFC destinations cannot be assigned for your own logical system because your own logical system is always called locally. For this reason your own system does not appear in the list.
Requirements
The RFC destinations must be assigned in advance. To call specific methods, the client system must be specified as the "trusted system" on the server system.
Activities
- Select a logical system
- Assign a standard destination to the logical system for BAPIs and dialogs or a destination for special methods. If you want to call function modules in a target system (trusted system), you have to enter the object type remote user and the method logon with an appropriate RFC destination. The RFC destination should use the current user of the calling system (trusted system) and should have the suffix USR (e.g. BIECLNT000USR).
- Save your entries
Notes for Transport
These settings are not transported in the Change and Transport System. You must make the settings in each system.
Regards,
Ferry Lianto

Similar Messages

Homogeneous System Copy - Export Import of RFC's, ALE, Content Repositories

Good Morning,
I have a landscape with a Development and Production Systems with SAP R3 Enterprise 4.70 Ext 110, MaxDB 7.5, HP-UX 11.23. A Homogeneous System Copy is going to be done from Production to Development.
I have a idea to be able to recover the RFC's, ALE and Content Repositories Information after the Copy, which is to create a transport order with the structures which contain data for the RFC's definition, the ALE configurations and definitions and the Content Repositories configurations and definitions in Development and after the copy, transport the orders back to Development. The problem is that i don't know which structures should i use, and if my idea is viable?
For example, if i go to transaction oac0 and look at the content repositories and if i look at the Technical Information, i can see that the fileds with data are from Structure SCMS_SCREP, but my question is, inserting thsi structure in a transport order to import after the copy willbe enough? Aren't there more structures i need to insert in a transport order? And for RFCs and ALE?
Can anyone help me on this matter please?
Kind Regards,
Pedro Gaspar

Hi,
If the target system is being refreshed then first secure any information that you may require.
1) Backup user master and authorization data from each client where this data needs to be retained.
Use transaction SCC8 to export this data. Select profile SAP_USER and specify target system = TARGET_SID.
2) Backup RFC tables to restore destinations afterwards.
the only below tables required to take backup.
Call SE01 and create a new request of type = ""Transport of Copies"" with description = ""Export RFC destination tables prior to system refresh"".Make sure to specify a Target for the request or no data file will be created.
RFCATTRIB
RFCCHECK
RFCDES
RFCDESSECU
RFCDOC
3) ALE / Partner profiles.
Call WE20 and select each partner profile.
Follow menu path ""Partners --> Check"" and obtain a list of tables used.
The only tables listed were the ones listed below.
These tables are client-dependant therefore you will have to logon to each client and call SE01 and create a new request of type = ""Transport of Copies"
EDPP1
EDP13
EDP21
Also document the WE21 --> Ports --> Transactional RFC" section.
Run transaction BD64 and document each configured distribution model. This information is client-dependent so make sure to record values for each required client. and also record RFC destinations for synchronous method calls in BD97.
I hope it will help you.
Regards,
Kiran .V

Data Fir IDOC ALE and EDI

Hello All,
    I am newly join in IT company (Name don't want to specify) . They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
Regards
Swati Namdev

Some use full Tcodes:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

Homogeneous System Copy - Remaining ALE Configuration

We made a system copy of an R/3 HR productive system to a new server for testing purpose. The system copy was made with a backup / restore procedure. Now, the new server in online and is working fine. The problem starts when we want to make the accounting payroll. This process needs financial data from R/3 Finance system via ALE to make the accounting. So we decided to connect this new test system with our R/3 Finance QAS system, via ALE, to make possible the extraction of the data needed.
When running the accounting payroll process, we get the following error: "RFC Destination is not maintained for object BUS6004 and method check" and the accounting is canceled. We noticed that the system is trying to use a RFC which its destination is R/3 HR Productive system. Obviously, we deleted the RFC connection pointing to the real productive system to prevent any damages. Also, we checked the ALE configuration and everything is OK (Transactions: BD97, WE20, WE21). But, when we checked the consistency of the ALE configuration, in transaction BDM5, we noticed that there is another ALE configuration defined, which is pointing to the R/3 HR Productive system. It seems that the system copy brings all the definitions of the ALE configurations that were defined in the original R/3 HR productive system. However, this new system is using these settings for connecting via ALE. There is a way to delete or disable these old settings defined in this new system? When making a system copy, there is a way to avoid copying the ALE configurations defined in the source system?

You have some options here ie after system copy
- Before starting the background process (ie #rdisp/wp_no_btc)
- Start SAP system, execute sm59 and append to all the <destination/target> with <destinaion/target>_no connect for each RFC. This way the connections won't happen
- Save
- Stop SAP
- remove # frm rdisp/wp_no_btc
- Restart SAP
whenever you want to try a connection then will remove the _NOCONNECT and it connect
or
you have a table RFCDES, which can be disabled (i haven't tried this).
Cheers

Error in ALE customization.

Hi,
when I use PRRW transaction to transfer all data from HR system to FI.
I am getting error :
"In your system an error occurred that can probably be corrected by making changes in ALE customizing. "
I have checked RFC connection from HR to FI is in place.

Have you checked RFC destinations defined to your logical system?
Use transaction BD97,check the assignment to RFC destination for your logical system, also insue that you are using correct(standard BAPI Destination or Special method destination)as per your system customization.
Hope this will help you.

Error in ALE Service While Creation of Vendor Master

hi,
I am using a scenario where a third party system is sending vendor master data to a R/3 system The file is picked up by the file adapter(sender) and mapped to IDOC format, using Idoc adapter (receiver). A Vendor is then created by posting the CREMAS03 IDOC into the R/3 system.
Everything goes fine till the Idoc comes into the R/3 system. There in BD87(Idoc Status Monitor), getting the "Error in ALE Service" error. When expanded further the specific error is that of "Cross-system company code xxxx does not exist". What is generally the cause of this error and how would I resolve it?
For those of you who have attended TBIT 40, this scenario is Example 1 - Creation of Vendor Master Data.
Any help would be appreciated?
regards,
SK

one more thing
if you want to be sure that you're using the right data
try to set your system to send the vendor data out
first - send it from BD14
and then you'll know which fields do you need
if you do that take a look at segment E1LFB1M
and check for BURKS
Regards,
michal

Issue in Data transfers using ALE for E-Recruiting standalone system

Dear Experts,
We have an issue in data transfers using ALE. We are having standalone system where E-Recruiting is maintaind seperately and the version is EHP5.
When we configured iDoc in Sandbox and its working fine. But when it comes to Dev and Quality servers this is not working fine.
we have created iDocs using the following filters.
For Object P: Infotypes 0000, 0001, 0002, 0003, 0006, 0024, 0105.
For Objects O,S: 1032, Subtype: 0010
For Object: 1001, Subtype: A003, A008, A012, B007
For Object O: 1001, Subtype: A002, B002, B003, B012, Tyoe of related object: O,S
For Objects: C, O, S, Subtype: 1000, 1002, 1028
For Object:C, Subtype: 1001, Subtype: A007
When we do the data transfers in Sandbox using PFAL it is transferring the data properly.
But when we do the same iin Dev and Quality servers we are not able to do it and gettign 52, 51 errors.
Here we are facing a strange issue. For some Users when we transfer data it is transferring data but with 52 error messgae.
For some users I am getting 51 error where i could not transfer any data.
For some users, when we tranfer O, S, and P related data is moving but getting mostly 52 error and all the relationships are not moving here for O,S and properly. But P related CP, BP and NA are getting created successfully.
It is happening only in Dev and Quality server and that too some users are able to get transferred but not all.
Where will be the issue? How can we resolve this?
Any help will be appreciable.
Thank you in advance.

Hi Sekhar,
Have a look over these threads.
Errors in ALE data transfer to E-Recruiting.
http://scn.sap.com/thread/1535402
BR,
RAM.

ALE logical systems for business service or process

Hi,
I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
"Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
How can I handle this problem?
Should I hard code values somewhere?
Which ones?
I have read the other posts for the error above, but my situation seems to be different.
Help!
Chris

Hi,
To solve your problem, here my solution:
1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
2/ Create this Logical System on your target system (R/3).
WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
Mickael.

Why do we create logical systems in ALE?

Hi All,
i got this question in interview.
Why do we create logical systems in ALE?
Thanks & Regards
suresh

Hi
In addition to above .
A logical system is used to identify an individual client in a system, for ALE communication between SAP systems. That's why you see a field for 'logical system' in the client master data in SCC4 (table T000).
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
http://help.sap.com/saphelp_nw04/helpdata/en/b5/1d733b73a8f706e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24ca94ba111d189750000e8322d00/content.htm
http://72.14.203.104/search?q=cache:J-uDLyT0w54J:www.topxml.com/biztalkutilities/walkthroughs/SAP%2520Configuration.pdfwhatislogicalsystems+(SAP)&hl=en&gl=in&ct=clnk&cd=5
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d7/9c73631d6c11d2a56e0060087832f8/content.htm
This guide is really good shows step by step procedure.
http://72.14.203.104/search?q=cache:Xyl0zxpyEXsJ:www.sappoint.com/abap/ale.pdfLogicalsystem(ALE)&hl=en&gl=in&ct=clnk&cd=9
for one client config
http://www.sappro.com/downloads/OneClientDistribution.pdf#search=%22Logical%20system(ALE)%22
Please reward for the same.

Logical systems in ALE iDoc

Hi,
For exchanging data between two systems(not between two clients of the same system) using ALE iDoc , logical systems should be maintained in both the systems?
For eg: there are two systems, system A and system B.
i have maintained the logical systems as SYSA (for system A) and SYSB ( for system B) in the system A using the transaction 'SALE'. Should this need to be maintained in system B also?
Thanks & Regards,
Soumya.

Hi,
In both the systems you have to Define the Logical systems,
but in you assign only one to the client,
i.e. in system A you assign the Logical Sytem of of A to the Client in SALE
transaction the same goes for B.
and you don't need to create a distribution model for both the systems,
you can create it in one system and send it to the other system.
Regards,
Samson Rodrigues.

Can We send data from SAP to non SAP using ALE !

In this case what will be the receiver side configuaration !
What will be our receiver client !

Hi,
We can send SAP to Non-SAP system using ALE technology.
Ex:-
Business Connector, VB.NET system can be integrated using ALE technology over TCP/IP connection.
Regards
Vijayanand Poreddy

Using ale u can send from sap to sap and sap to non sap systems

hi,
using ale u can send from sap to sap and sap to non sap systems,
then what is diff b/w ALE and EDI

Hello KALYAN KUMAR,
Application Link Enabling (ALE)
1.You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems.
2.ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
3.ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
1.You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor).
2. 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).
3. This enables communication with non-SAP systems.
By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message
I hope u understands the difference:)

Report for Purchase Orders didnt reach target through ALE

Hi Experts,
we are sending Purchase Orders to Third party system using XI.
But some of the orders when we save its automatically system generating output medium is PRINT so these orders not going through ALE.
1)Can anyone please tell me why the system is generating PRINT instead of ALE distribution.
2) is there any report for how many purchase orders created for the day and how many of them gone through successfull using ALE distribution.
Answer will be rewarded.
Kiran

Hi
Have you configured the PO Output type/messages with the Medium as 'A'(ALE)
otherwise the system willd efualt take 1(print) as default medium.
Check the NAST table entries for that date created Output type of PO's
for all of them the Medium(NACHA) field should be A
then all will go through ALE
check them.
Regards
Anji

Sales Order from one SAP to another SAP system thru ALE

I am trying to send a Sales order IDOC from one SAP system to another SAP system (basically from DEV to QAS). Will i be able to do this using ALE ? If so, how ? I don't want this Sales order to be posted as PO in QAS. I want it to stay as a sales order.

hi,
use BAPI SALESORDERCREATE
~linganna

Upload data from legacy system to SAP through ALE IDOC

Hello All,
I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
Could you please provide a sample program for retrieving data for IDOC.
Thanks

Hi,
You can find the sample code in the following link.
Re: calling idoc_input_creditor
Regards
Sajid

ALE- BD97

Similar Messages

Maybe you are looking for