ALE SETTING

Hi ALL,
I have doubt in ALE SETTINGS
what is the difference between IDOC to FILE and FILE to IDOC ale setting. Can any one help me in this regard.
thanks
saranya

hi saranya,
ALE settings for IDOC to file scenario. Pls refer my article:
http://www.architectsap.com/expertise-Publications.htm(Custom IDOC creation and integration with xi)
i think this will give you good info aboutidoc to file ale settings.
ALE settings for File to IDOC scenario. Pls refer foll articles:
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Regards,
Mandeep Virk
*reward points if helpful*

Similar Messages

Urgent: ALE setting for BAPI_PROFITCENTER_CREATE used in LSMW

Hi Experts
I have previously posted this qurey but wasnt able to get it solve .
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number like creation of logical system and assigning the message type to that system.
Do we require to create distribution model aslos for this case?
What are the specific setting required to be done in case of any BAPI method for LSMW?
Please help me to solve this error.
Message was edited by:
Mitesh Parekh
Message was edited by:
Mitesh Parekh

Hi,
Once When you get message like 'Profit Center 000010' created it means You have not missed any mandatory data and it is successfully created. So don't think that you have missed some data.
Please Check in CEPC table again. Only enter PRCTR as 10 (no leading zeros required).
Still if you have problem refresh(F8) the table and check.
Hope you will get your data

ALE setting DEV / PROD

Hello all,
I have a question about what is the best way to setting ALE. Our scenario is as follows: we have ALE in DEV to distribute master data from PA to E-recruiting, but we also need distribute data in PRO system, so what is the way to do this:
1.- Settint ALE in DEV with the respective partner profile and then distribute the model view.
or
2.- Setting ALE in PRO.
Regards
Emilio Ciotta

Hi Emilio,
as every system in the ALE has an unique Id you will need a separate distribution model set up for DEV and PROD and perhaps QS/TEST anyways. I know some companies setting up all scenarios in DEV, transport everything and then only activate the PROD version in PROD but I for my own prefer setting it up per system. When configuring e-recruiting you have to make some settings directly on the PROD server anyways (ICF activation, Service user setting, http / https conect, some T77S0 switches ....) so it should not be a big deal to open the servers that someone can do the ALE settings, too. So far this approach has not been a problem in any of my projects.
Best regards
Roman

In ALE setting how to distribute GL account to severals company codes ?

Hi all ,
I use ALE to distribute G/L account data from one company code to one another company ( different host ) .
It's work fine now.
Now I want to distribute G/L account data from one company code to severals company codes.
But in cross-company code setting ( Tx: OBB5 ), one global company can only be assing to local company code in receiving host.
I have no idea how to set up the ALE configuration.
Can anyone give me some suggestion . Tks.
Regards,
Eric.

Dear Sharvari,
All the master data can be created in a central system and then distributed to the local systems through distribution models. I think no copy of GLs is possible. In your case you can create the GL Accounts in your central system and it'll flow to other systems automatically through ALE. To achieve this please consult your BASIS consultant who'll design the distribution model as per your requirement.
Regards
Edited by: drames on Aug 17, 2010 2:33 PM

ALE Set Up : BD64 Error

Hi All ABAP Gurus,
i am trasnfering material master data from Dev to QA using ALE.Fot that i have done the folloeing things.
1) First i Created and Assigned Logical system for respective clients using SALE Transaction.
2) Made RFC Connetion in Dev and QA using SM59 Transaction
3) Created Model View Distribution using BD64 Transaction.
In this step when i am going for Distribute ( Menu Path Edit--->Model View --> Distribute ), i am getting the following error
Target system QUALITY : Model view MM-MODEL has not been updated
Rreason: Distribution model is currently being processed
Please sugget how to correct this error.
Rewards will be given.
Regards.
ulhas

Hi,
Creating Customer Distribution Model
o     Go to T. Code BD64
o     Click on change and Create model view button
o     Enter the short text and Technical name as ZXXXXX
o     Select the model and click on Add Message Type Button
o     Give the Sender as STUD_S,
o                    Receiver as STUD_R,
o                    Message Type as ZMES_TYPE
o     Select the model view & click on Environment -> Generate Partner Profiles
o     Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o     Click on Execute
o     You should get a list in green color which means it executed successfully.
o     Back to main screen, select the model view
o     Click Edit->Model view->Distribute
o     Click on continue
o     You should get a list saying model view is distributed successfully.
Reward if useful
Thanks
Jagadeesh.G

ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot set up identical definitions.
I suppose I should 'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
Thank you in advance!

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

ALE/ IDoc: Error while checking in and storing

HI Gurus,
i need to send Documents from one system to an other System. I use BDA5
Both system are using different File Systems and the DMS Archive is also different.
I can send the DOCMAS without errors. When i Try to process the Documents i can not process IDocs which have a file (Segment E1DRAWFILES) included. i get the Error messages Error while checking in and storing
I also sent some IDocs which have no files (no segment E1DRAWFILES) and these can be processed. Has anybody an idea whats wrong? If i use normal transaction CV0xN i can upload and checkin documents.
How can i convince SAP to successfully process the IDocs with files from the source system?
Thanks in Advance
Udo

HI,
Udo,
1. Are you taking about business document?
or
2. SAP dms Document?
If DMS doc then send details regarding document type, and business object used in definine document type for object linking.
In DC10 U check flag in define object linking, Object chek from ALE[Set flag]
for business document i think differen procdure while defining your document type. i guess.
Benakaraja

Need of ALE settings to connect 4.7 to 5.0 to send IDOc

Hi
I have two servers 4.7 and 5.0 .
Now I want to send Idoc from 4.7 client 800 to 5.0 client 800.
Can anybody provide me the steps to create ALE settings and to send IDOC.
creating logical systems in source and destination and creating RFC and partner profile and port.
Thanks in Advance

Hi,
For ALE senerion for sending the material from one system there are three methods are there
1) Executable program only for Master Data
2) Message type Master As well as Transcation Data
2) Change Pointers Master As well as Transcation Data
1) SCC4 Create the Logical systems.
ALG800 for 800
ALG810 for 810
2) Assign the Logical systems to the Client using SCC4> selecting the Client and Double click> maintain the logical system name which you had created in the step 1
3) Main RFC destination SM59---> use the same Logical system name as the Logical system name
log on to 800 and goto SM59 --> create
ALG810 --> provide the 810 logon details and save
test with remote logon...it will open the client 810..
logon to client 810 goto--> sm59 --> create
   ALG800 --> provide the 800 logon details and save
test with remote logon...it will open the client 800..
logon to 800 goto BD64 maintain CDM-->change
create CDM
ZCDM01 CDM
ALG800 sender
ALG810 Reciever
MATMAS Message type
ZCDM01 CDM
ALG810 sender
ALG800 Reciever
MATMAS Message type
save
Environment ---> Generate partner porfile.
edit --> distribute CDM
Logon to 810
goto BD64---> select CDM ZCDM01 ---> Environment ---> Generate Pratner Profile.
Edit --> distribute.
ALE Setting are compleated.
Logon to sender system 800.
create material in MM01
Material   10001
Industry sector mechanical engee
Material Type finished
enter
Base Unit of Measure KG
Weight unit         KG
Gross Weight         100
Net Weight           100
save
Execute BD10 in client 800
Check the Idoc in WE05.
Log on to Client 810
Execute BD11
check the IDOC status in WE05
goto MM03 provide the material numer enter...
Thansk,
Nelson

How to remove the complete ALE configuration for a given system

Hello everybody,
Through ALE ,data is transferred between a number of SAP systems and the necessary ALE setups are in place.
Now,a particular SAP system,which used to be a receivor to the central SAP system,is to be retired.
Hence,the associated ALE set up is to be completely removed from the central SAP system.
Is the following sequence correct?If not and I have missed something,please enlighten me with the correct sequence.
1.Removal of the receivor logical system and its assignment to client ,through transaction SALE.
2.Removal of partner profile, through transaction WE20.
3.Removal of RFC destinations,through transaction SM59.
4.Removal of transactional ports for the logical system,through transaction code WE21.
5.Removal of Distribution model between the retiring system and the central SAP system.
(a)Regarding distribution model,I have a question-if the distribution model is maintained such that it contains the linking relationships between the central system and several receivor systems(in addition to the one I wish to remove),then is it possible to remove only the desired linkage and not touch the rest?
(b)Through BD64,I have tried but I am able to delete only the entire distribution model as a whole,while I would like to keep the distribution model and delete just one of the nodes,so as to cut the connection between only central system and the retiring system.
This is so because the other receivor systems are working fine,involving a lot of batchjobs and I am afraid that deleting the distribution model wholly will create unnecessary trouble.
Any help will be appreciated.Thanks
Papri

HI Nicolas,
I chatted with Rev-Trac support earlier today and here is what they have come back to me with.
Assuming the change in question was carried out in the development system. Changes to fields in tables should in most cases be captured in transports. Assuming it was a transportable change then go to the development system and execute transaction SE16 and query Rev-Trac table /RSC/T_MFM_4T filtering by TABLENAME.
On executing the query you should see a list of transports involved with changes to the transport. You can then check to see if there is a recent transport associated with the change - if so then you can find out who created the transport by using standard SAP functionality."
If you find this doesn't help, then please contact your Rev-Trac Administrator who can then log a support request on our support portal at www.xrsc.com
Hope this helps, Rick

How to - E-Recruiting ALE-integration step-by-step (EhP4)

Hi everyone,
Can anyone tell me the step-by-step guideline to perform the ALE initial run from SAP HCM to E-Recruiting using transaction PFAL (RHALEINI)??
We are implementing E-Recruiting stand-alone constellation: separate ECC instance integrated with E-Rec via ALE/RFC, enhancement package 4.
We've done some try-outs in the new version, but we lack the certainty that we've done things right.
Please do not refer to note 997181 since it does not explain the details on how to run the initial load. It explains adequately how to set-up the config and very basically how to run PFAL on page 2 (scen. I2-A) and page 4 (up to rel. 6.03)... But it's not sufficient in my opinion... We've done exactly the same...
So what I'm interested in is the right sequence of runs and the selection screen values.
We also have quite a few SLG1 errors which are unclear. Some suggest as if the processing occurs simultaneously (parallel) and blocks the asynchronous processes... Is there a certain number we should enter in the field "number of objects per process"? It's defaulted on 200...
Can anyone shed some light on the best-practice how to run this transaction?
Many thanks in advance!
Miroslav.

Hi Medic,
hope u r doing good.
Can u pls chk dese links by Roman,They speak alot on HR_ALE_ER issues.
Re: E-Recruitment Technical Structure ( Attn: Roman Weise)
Re: ALE data transfer from E-recruitment to HCM
Re: E-Recruiting- ALE is working for OM data, but not for internal employees
Re: ALE setting DEV / PROD
Re: ALE Linkage error in E Recruitment
Re: E Recruit 603 - ALE
Re: ALE from HR to E-Recruiting on EhP4
Regards
Rohit.S

PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

Urgent :Getting error "No ALE scenario active in Profit Center Accounting"

Hi Experts
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number.
Please help me to solve this error.
Thanks
-Mitesh
Message was edited by:
 Mitesh Parekh

Hi,
Refer This SDN Blog, which gives you steps in detail....
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
 Most of the functions are within R/3, hence platform independence.
 Quality and data consistency due to standard import techniques.
 Data mapping and conversion rules are reusable across projects.
 A variety of technical possibilities of data conversion.
 Generation of the conversion program on the basis of defined rules
 Interface for data in spreadsheet format.
 Creation of data migration objects on the basis of recorded transactions.
 Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 Maintain attributes choose the import method.
 Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 Maintain relationship between source and target structures.
 Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 Assign Files to defined source structures
 Read data Can process all the data or part of data by specifying from / to transaction numbers.
 Display read data To verify the input data being read
 Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
 Presetting for Inbound IDOC processing not transportable.
One Last thing, Check in BD64 is the Distribution model is Active for Profit Center.
Cheers...
Santosh.D
Mark All the Usefull Answers.

BAPI calls via ALE

Hi,
I have a scenario where
source and target system are same.
send order data through BAPI via ALE as per [Unchecked Deliveries|http://help.sap.com/crmcg_en/6c/d321ef6e1111d4b554006094b9b9dd/content.htm]
I am first time sending data using BAPI via ALE, in customer distribution model I have created a model view, used 'Add BAPI' to add concerned BAPI. Now my question is how to triggert the process?
Is it through
Writing the BAPI fm in order processing/ saving user enhancement?
Configure Output type with medium A in nace?
Thanks,
Suraj

Hi,
Did I get you correct? You want to sent out sales order data and receive the input in the same SAP client?
In this case you don't need BAPI or ALE setting. Use or define an output message in nace for medium 6 or A in the sales order.. SAP will create an ORDERS Idoc, eg based on condition records. In the WE20/WE21 settings of the outbound configure it to send it to an rfc destination which is equivalant to the sender system. Of course you would need some changes in the inbound dependend on what do you want to do with the data.
Kind Regards
Michael

All ALE configuration are right, but why errors in idocs?

hi any anybody explains why error are occurs in IDOCs when all ALE setting are ok. please explain any scenario

Hi,
One of the commonly occuring error status - 26(Syntax error in Idoc) Outbound
The reason for the occurence of this error is mostly related to the structuring of the segments in the IDoc, the normal structure should have a parent segment followed by the sub segments but in cases when that fails to happen, the Idoc is in 26 status. For correction of this error goto WE30 and check if the mandatory segment is checked.
status 51(Application Document not posted) Inbound
This normally occurs due to the incorrect data being populated in the segments or it could also be related to serialization.
~Krithika

ALE idocs outbound process

ale setting i properly then i created zprogram to generate idocs , idocs are generated for out bond process . then i checked in other client the data is not received sending system showing the idoc status is 3 . other client i am not able to see the data? can any one tell me how check that idocs.

first check the RFC thru SM59, whether the ports are mainted properly, next check whether partner profiles(WE20) are mainted correctly with the respective ports and then check if the idocs are stagnated anywhere between the server thru the help of middleware team
if both are mainted properly debug the code with BD87 or WE19, where exactly u will know the issue which helps you to rectify the problem

ALE SETTING

Similar Messages

Maybe you are looking for