‎2008 Feb 27 9:57 AM
hi frds plz give to tr.codes
various TCODE's involved in ALE?
to my mail id
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 4:44 PM
‎2008 Feb 27 10:01 AM
hi,
Following is a list of ALE/EDI transactions.
Transaction code Short text
SALE ALE Customizing
BALE Distribution Administration (ALE)
WEDI IDoc type & EDI Basis
WE02 IDoc display
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 EDI: File Processing Status (EDFI2)
WE09 IDoc lists enhanced
WE10 IDoc lists enhanced
WE12 IDoc test: Inb. Procg of Outb. File
WE14 IDoc test: Outb. from IDoc
WE15 IDoc test: Outbound from MC
WE16 IDoc test: Inbound File
WE17 IDoc test: Inbound status report
WE19 Test tool
WE20 Partner profiles
WE21 Port definition
WE30 IDoc type editor
WE31 Segment editor
WE32 View editor
WE33 Value tables for IDoc documentation
WE40 System process codes
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and selection reports
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 IDoc administration
WE47 Status Maintenance
WE48 Inbound process codes: Texts
WE49 Inbound process codes: Change texts
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE52 Outbound process codes: Texts
WE53 Outbound process codes: Change texts
WE54 FMs for changing file names
WE55 FMs for path names
WE56 Status process codes
WE57 Messages and application objects
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Parser for IDoc types and rec.types
hope this helps u,
Regards,
Arunsri
‎2008 Feb 27 10:01 AM
hi,
Following is a list of ALE/EDI transactions.
Transaction code Short text
SALE ALE Customizing
BALE Distribution Administration (ALE)
WEDI IDoc type & EDI Basis
WE02 IDoc display
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 EDI: File Processing Status (EDFI2)
WE09 IDoc lists enhanced
WE10 IDoc lists enhanced
WE12 IDoc test: Inb. Procg of Outb. File
WE14 IDoc test: Outb. from IDoc
WE15 IDoc test: Outbound from MC
WE16 IDoc test: Inbound File
WE17 IDoc test: Inbound status report
WE19 Test tool
WE20 Partner profiles
WE21 Port definition
WE30 IDoc type editor
WE31 Segment editor
WE32 View editor
WE33 Value tables for IDoc documentation
WE40 System process codes
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and selection reports
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 IDoc administration
WE47 Status Maintenance
WE48 Inbound process codes: Texts
WE49 Inbound process codes: Change texts
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE52 Outbound process codes: Texts
WE53 Outbound process codes: Change texts
WE54 FMs for changing file names
WE55 FMs for path names
WE56 Status process codes
WE57 Messages and application objects
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Parser for IDoc types and rec.types
hope this helps u,
Regards,
Arunsri
‎2008 Feb 27 10:03 AM
This is the order of Tcode used for ALE config
BD54
SCC4
SM59
WE21
WE20
BD64
after this, depending on the message type
u can use
BD10/11
BD12/13
BD14/15
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 4:44 PM
‎2008 Feb 27 10:04 AM
hi
TSTC - Tcodes
- TSTCT - Tcode Texts
SE93 shows transactions (can add transactions here as well)
I also use SM01 to view transactions (Be careful with this one as it's used to lock transactions. To browse the transactions start typing the transaction and hit enter. The cursor goes to the entry starting with what you typed. Hit enter to page down from there.
Use transaction SEARCH_SAP_MENU to find the menu path of a transaction
regards
sreelatha gullapalli
‎2008 Feb 27 10:25 AM
I wll exaplin in steps :
MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS
For this scenario Client 800 is the Sender and 810 is the receiving system
1. Creating Logical Systems
o Login using 800 client
o Go to T. Code SALE
o Expand Sending and Receiving Systems
o Expand Logical Systems
o Click on Define Logical System
o Click on New Entries
o Create STUD_S, STUD_R Logical Systems
o Save and come back
o Assign the STUD_S Logical System to client 800
o Assign the STUD_R Logical System to client 810
2. Creating the RFCs
o Go to T. Code SM59
o Expand R/3 Connections
o Enter RFC Name as STUD_S
o Connection Type as 3
o Language as EN
o Client as 800
o User as SAPUSER
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
o Enter RFC Name as STUD_R
o Connection Type as 3
o Language as EN
o Client as 800
o User as SATISH
o PWD as abap
o Target host as sap
o Click on Remote logon button to test the RFC
3. Creating the Message Type
o Go to T. Code WE81
o Click on change, continue
o Click on New Entries button
o Give message type as ZBAPI_STUD_MAS and description
o Save and back
4. Creating the Segment
o Go to T. Code WE31
o Give segment name as ZBAPI_STUD_SEG
o Enter Short Text
o Enter the Field Name and Data Element in the text boxes
o Save, continue,
o Click on Edit -> Set Release.
5. Creating the Basic IDOC Object
o Go to T. code WE30
o Give obj. name as ZBAPI_STUD_IDOC
o Click on create
o Select create new radio button, give description and continue
o Select the IDOC obj name and click on create button
o Enter the segment name which is create earlier
o Select the check box if you want to make the segment mandatory
o Enter 1 in minimum number 99999 in maximum number, continue
o Save and back
o Click on Edit -> Set Release
6. 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 ZSTUDENT
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 ZBAPI_STUD_MAS
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.
7. Checking the Port
o Go to T. Code WE21
o Expand Transactional RFC
o Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.
8. Checking the Partner Profiles.
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner profile STUD_R
o Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.
o Check Receiver Port is assigned correctly
o Check the Basic type as your Basic IDOC object.
9. Assigning the Message Type to Basic IDOC Object
o Go to T. Code WE82
o Click on Change & continue, New Entries button
o Give the Message type as ZBAPI_STUD_MAS
o Give Basic Type as ZBAPI_STUD_IDOC
o Release as 46C
o Save and back
10. Creating Inbound Function Module (Posting Program)
o Go to T. Code SE37
o Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS
Thx
Jagadeesh.G