ALE Configuration Needed
Hi every one,
I want steps involved in ale configuration.
Lets take example two systems are Sysa and sysb
Thank you
hi
CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS
For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver
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 CATSSENDER, ECC Logical Systems
o Save and come back
o Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE
2. Creating the RFCs
o Go to T. Code SM59
o Expand R/3 Connections
o Enter RFC Name as CATSSENDER
o Connection Type as 3
o Language as EN
o Client as 800
o User as SAPUSER
o Password as YESV13
o Target host as SAPADM
o Click on Remote logon button to test the RFC
o Enter RFC Name as ECC
o Connection Type as 3
o Language as EN
o Client as 800
o User as SAPUSER
o Password as YESV123
o Target host as SAPADM
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 ZCATSTIME and description
o Save and back
4. Creating the Segment
o Go to T. Code WE31
o Give segment name as ZSEGMENTTIME
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 ZTIMEIDOC
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 backo 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 CATSSENDER
o Select the model and click on Add Message Type Button
o Give the Sender as CATSSENDER,
o Receiver as ECC,
o Message Type as ZCATSTIME
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 continueo
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 ECC (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 ECC
o Double click on Message Type ZCATSTIME in Outbound parmtrs.
o Check Receiver Port is assigned correctlyo
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 ZCATSTIME
o Give Basic Type as ZTIMEIDOC
o Release as 4.6C
o Save and back10. Creating Inbound Function Module (Posting Program)
o Go to T. Code SE37
o Create a function Module ZCATSDB_TIMESHEET_SURESH
o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o Import Parameters
P_WORKDATE LIKE CATSDB-WORKDATE
P_COUNTER LIKE CATSDB-COUNTER
P_LSTAR LIKE CATSDB-LSTAR
o Export Parameters
o Tables
S_PERNR LIKE ZCATSPERNR
[PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as
Ø SIGN
Ø OPTION
Ø LOW
Ø HIGH]
o Exceptions
o Source Code
FUNCTION zcatsdb_timesheet_suresh.
""Local interface:
*" IMPORTING
*" VALUE(P_WORKDATE) LIKE CATSDB-WORKDATE
*" VALUE(P_COUNTER) LIKE CATSDB-COUNTER
*" VALUE(P_LSTAR) LIKE CATSDB-LSTAR
*" TABLES
*" S_PERNR STRUCTURE ZCATSPERNR
TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd
CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC', " idoc type
c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME', "segment type
c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'. " message type
*001 comment begin
creating internal tables with out header lines for catsdb, edidc, edidd and also
- work areas
*001 comment end
DATA: it_edidc TYPE edidc OCCURS 0, " control internal table with out header line
it_edidd TYPE edidd OCCURS 0, " data internal table with out header line
wa_catsdb TYPE it_catsdb1, " work area for it_catsdb internal table
wa_edidc TYPE edidc, " work area for it_edidc internal table
wa_edidd TYPE edidd, " work area for it_edidd internal table
wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table
v_occmax TYPE idocsyn-occmax,
v_nbseg TYPE i.
CLEAR wa_catsdb. " clears work area of catsdb
CLEAR wa_edidc. " clears edidc work area
*002 comment begin
Save the message type and the basic IDoc type in the control segment.
*002 comment end
MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea
MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea
*003 comment begin
Retrieve the maximum number of segments in the basic IDoc type.
*003 comment end
SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.
*004 comment begin
Save the whole CATSDB table content in the IT_ZCATSDB internal table.
*004 comment end
SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.
*005 comment begin
Create a data segment for each line of IT_ZCATSDB.
*005 comment end
IF sy-subrc EQ 0.
LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.
MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.
CLEAR wa_edidd.
MOVE c_segnam TO wa_edidd-segnam.
MOVE wa_zsegmenttime TO wa_edidd-sdata.
APPEND wa_edidd TO it_edidd.
CLEAR wa_catsdb.
CLEAR wa_zsegmenttime.
ENDLOOP.
ELSE.
MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.
ENDIF.
*006 comment begin
Count the number of data segments.
*006 comment end
DESCRIBE TABLE it_edidd LINES v_nbseg.
*007 comment begin
If the number of data segments exceeds the maximum allowed number,then display an error message.
*007 comment end
IF v_nbseg GT v_occmax.
MESSAGE 'IDOC ERROR Message' TYPE 'E000'.
ENDIF.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc
EXPORTING
master_idoc_control = wa_edidc
OBJ_TYPE = ''
CHNUM = ''
TABLES
communication_idoc_control = it_edidc
master_idoc_data = it_edidd
EXCEPTIONS
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFUNCTION.
Save, check and activate
111. Assigning the Inbound Function Module to Basic Type & Message Type
o Go to T. Code WE57
o Click on change, continue, continue and New Entries Button
o Enter the Module as ZCATSDB_TIMESHEET_SURESH Type as "F"
o Basic Type as ZTIMEIDOC
o Message Type as ZCATSTIME
o Direction as 2
o Save and back
Now Login in 800 client of Application Server SAP-REMOTE
12. Assigning the Inbound Function Module in ALE Table
o Go to T. Code BD51
o Click on continue, New Entries button
o Give the Inbound Function Module ZCATSDB_TIMESHEET_SURESH
o Give Input t. as 0 (zero)
o Save and back13. Creating Process Code
o Go to T. Code WE42
o Click on Change, New Entries Button
o Give Process Code name as ZCATSDB, give Description & Save
o Select Processing with ALE Services Radio button
o Select Processing by Function Module Radio button
o Click the ALE Table (arrow Icon) in Identification
o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
o Give maximum number of repeats 0
o Save and back, back
o Select the process code from the list & click on Logical Messages Icon
o Give the Message Type as ZCATSTIME
o Save & Back, Save & Back, Save & Back
14. Changing the Customer Distribution model in receiving system
o Go to T. Code BD64
o Click on change and Create model view button
o Enter the short text and Technical name as CATSECC
o Select the model view & click on Environment -> Generate Partner Profiles
o Select Transfer IDOC Immediately and Trigger Immediately radio buttonso Click on Execute You should get a list in green color which means it executed successfully.15. Assigning the Process Code to Message Type in Receiving System
o Go to T. Code WE20
o Expand Partner Type LS
o Select the Partner Profile CATSSENDER
o Double click on Message Type ZCATSTIME in Inbound parmtrs.
o Give the Process Code as ZCATSDB
o Click on Trigger Immediately Radio button
o Save & Back
Save & Back
16. Creating the Selection Program (Outbound Program)
- Login in client 800.
- Go to T. Code SE38
- Create a Report Program as ZCUSTOMIDOC with the following code
REPORT ZCUSTOMIDOC
NO STANDARD PAGE HEADING.
TABLES:catsdb. " using structure of cats db table
*000 comment begin
this selection screen contains one select option and one parameter
*000 comment end
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS pernr FOR catsdb-pernr.
PARAMETER: workdate LIKE catsdb-workdate,
LSTAR like catsdb-LSTAR,
COUNTER like catsdb-counter.
SELECTION-SCREEN: END OF BLOCK b1 .
DATA: wa_val TYPE i.
wa_val = pernr-high - pernr-low.
*001 comment begin
calling custom function module
*001 comment end
CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'
EXPORTING
p_workdate = workdate " passing workdate parameter
p_LSTAR = LSTAR
p_counter = counter
TABLES
s_pernr = pernr. " passing pernr select option
IF sy-subrc EQ 0.
MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .
MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
gives information message if idocs are created for given employees
ELSE.
MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low 'TO' pernr-high. " gives error message
" if idoc is not created
17. Transferring the CATSDB records from sender Application Server SAPADM to receiver Application Server SAP-REMOTE
- Execute Report Program ZCUSTOMIDOC
- Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer
- Give Message Type as ZCATSTIME
- Give Receiver Logical system as ECC
- Execute
- You should get the IDOC Number
- Take the IDOC Number and go to T. Code WE05 & Execute
- In Outbox you can see the IDOC Status
- Select the status record in left side window
- Double click on the Status record in right side window- You can see the Control Record, Data Record and Status Records for that IDOC
If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully
18. SENDING IDOCS FROM APPLICATION SERVER SAPADM
TO APPLICATION SERVER SAP-REMOTE USING WEDI
- Go to T. Code WEDI & execute or T. Code WE19
- Give idoc number it is generated recently
- Continue & double click on segment to view data in segment
- Click on EDIDC to give port, partner no, message type, partner
type of receiver. [For sender no need to give any port no leave it as
blank]
- Click on Standard Outbound Processing button and click continue
- You will get a message as idocs successfully transferred
Now Login in Receiver 800 client
- Go to T. Code WE05 & Execute
- You can see the status record in left side window
- If the status no is 53 and color is green, it means the IDOC is posted to Application successfully.
- You can see the Log Information by double clicking on the status record in right side window.
- Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
- Now go to T. Code SE16
- Give the table name CATSDB & press F7
- See the contents of the table
- The table is updated with the catsdb records transferred from 800 client with our selection program.
reward if u find useful
regards
Nagesh.Paruchuri
Similar Messages
-
Ale configurations for IDoc?
hi..
What are the ALE configurations need for an IDOC?
bye.Hi,
Perform the following ALE configurations
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Also gothru this Blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points -
Hi All,
Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system. As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
I've done the following ALE configurations at R/3 side.
1. Created a logical system and RFC destination for TIBCO.
2. created a TRFC port.
3. Create a Partner profile and linked the TRFC port.
4. posted an IDOC from WE19.
but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
regards
FaisalHI
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Refer the below links for further assistance
4.create partner profile using idx2
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
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)
cheers -
ALE Configuration issues..
Hi,
I am trying to set up ALE configuration between two SAP systems. I have defined partner profile(WE20) in sender system, there is a tab 'Post processing : Permmitted Agent', I have chosen type as User and agent as system user Id. I would like to know on what basis value of type and agent should be chosen?
I have another query....I am sending Idocs from one system to other. I am defining control records in a program in sender system. In control record I have mentioned sender port name(sndpor), sender partner number(sndprn) and sender partner type(sndprt). I would like to know whether i need to mention receiver port number(rcvpro), receiver partner number(rcvprn) and receiver partner type(rcvprt) ?? Please note that I am not receiving any data to my system but only sending Idocs to other system.
Thanks.Hi,
in the sender system you will have to define the sending options
In the receiver system you will have to define the receiving options
that is the partner profile.
if you are not useful with this, you could play with BD64
In WE20, you specify with this partner (the system receiver) I will send this kind of data.
In the receiver system, in WE20, you will specify with this partner (the sender) I will received this kind of data
so if you send other things, the receiver system will refused it
You could also specify the system in some transaction, for example BD10 for material, but if the WE20 customizing is missing, the system will don't do anything
regards
Fred -
ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI
Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
UmeshUmesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave -
hi
what are the ALE configurations required to be done in R/3 and XI for Outbound and inboundHi
for IDOC TO FILE,
ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
AND
FOR FILE TO IDOC
ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
PLZ REWARDS POINTS
VIKAS -
Hi,
I am creating a ALE Scenario with Material Master. I am doing this for the first time. Please tell me whether it is possible to trasfer data from a sandbox(UPG) system to a development system. If this is possible, what are the configuration steps i need to do in bothe the system to trasfer data from sandbox to Development system. thse two systems are physically independent systems.
Thanks
JitenHi Jitendra,
Before you Configure go through this, If you need any clarification contact me.
<b>
ALE Scenario Development Guide
To develop a new custom ALE scenario, comprises 5 steps:
1. Design and develop the custom IDoc with its segments and a new message type
2. Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3. Develop the outbound process which does the following:
Populates the custom IDoc with control info and functional data
Sends the IDoc to the ALE layer for distribution
Updates status and handles errors
4. Configure the ALE inbound side (partner profiles with inbound process code)
5. Develop the inbound process which does the following:
Reads the IDoc into a BDC table; selects other data that is required
Runs transaction using call transaction or BDC session
Updates status and handles errors
Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
Figure 1: ALE Scenario model
1.1. ALE Example
For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service providers system.
Figure 2: Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
*--- Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*--- Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
*--- Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
*--- Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
*--- Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
*--- Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
*--- Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
* Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
*--- Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
*--- Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
*--- Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
*--- OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
*--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
*--- Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
*--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
*--- Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
</b>
Thanks.
Manju.
Reward Points. -
Dear Experts,
I have ECC PO and as of now user creates manual sales order in other R/3 4.7 which is time consuming, less accurate and erroneous process. I got to know something on ALE configuration where user creates PO in ECC, automatically SO created in R/3. Basically, i have two separate server ECC and R/3. pl share ALE configuration steps of to create SO in other R/3 system from PO of ECC system. Pl also share any other processes to be followed to achieve automation of SO creation into other SAP system from PO.Hi,
Check the transaction code VOE2 which suits your requirement to create the SO from PO with ALE
In that transaction code you have to maintain the combination of Customer , vendor and sales area details
After that set up the partner profiles in the transaction code WE20 with the Partner type LS from ECC to R/3 with relevant message types and IDOC types
Please let the Developer know these details and he would be able to create the Partner profile
revert back if you need further details
regards,
santosh -
ALE configuration automatic SO creation
ABAP Experts,
I have ECC PO and as of now user creates manual sales order in other R/3 4.7 which is time consuming, less accurate and erroneous process. I got to know something on ALE configuration where user creates PO in ECC, automatically SO created in R/3. Basically, i have two separate server ECC and R/3. pl share ALE configuration steps of to create SO in other R/3 system from PO of ECC system. Pl also share any other process to be followed to achieve automation of SO creation from PO.
Thks
Moderator message: please search for available information/documentation before asking.
Edited by: Thomas Zloch on Jan 4, 2011 2:35 PMHi,
Check the transaction code VOE2 which suits your requirement to create the SO from PO with ALE
In that transaction code you have to maintain the combination of Customer , vendor and sales area details
After that set up the partner profiles in the transaction code WE20 with the Partner type LS from ECC to R/3 with relevant message types and IDOC types
Please let the Developer know these details and he would be able to create the Partner profile
revert back if you need further details
regards,
santosh -
ALE configuration Between HR and FI system
Dear All,
We have HR system on ECC6 and FI system on 4.x version,
i have to do ALE configuration between these two systems , please guide me what bapi's , idocs and what background jobs i need to run on FI system or HR system
please advise at the earliest.
Regards,
Najeeb ..http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAIS/CABFAIS.pdf -
ALE CONFIGURATION WHAT ARE CHANGES REQUIRED WHILE MIGRATING TO UNIX
HELLO GUYS,
PLEASE LET ME KNOW WHAT ARE THE CHANGES REQURIED IN ALE CONFIGURATION WHILE WE ARE MIGRATING FROM WINDOW NT TO UNIX?
REGARDS
RAJESHHi Rajesh,
Could you briefly explain me the scenario in which you want to transfer the data ?
Upto my understanding:
If you want to transfer the data from SAP to legacy system, through ALE u need to have translation programs, u can use BAPI's for this.
Regards,
Kannaiah Kavuri -
Hello Experts,
I have a few questions regarding ALE Configuration, help appreciated
1) Is it necessary to create user for ALE transfer in both sender and receiver system ?
2) Is it necessary to create logical system for both sender and receiver in both the systems ?
3) Can tRFC created in sender system have a different port name than the logical system name ?
Is it ok, if only configuration is done in the sender system, if I am looking for one way transfer of Idocs from sender to receiver ? The receiver will receive the Idocs and process internally, sender is responsible only for sending in my case.
I have referred the below link,
7 Steps For ALE Configuration - ABAP Development - SCN Wiki
Best Regards,
Ameya B.Hi Mili,
You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful. -
ALE Configuration HCM - Program read table idoc_structure error
Hello SCN community,
I have small problem with ALE Configuration of HRMD_A message type. I created extension named 'ZRMD_A06'.
When I'm trying to run t-code: bd21 (report RBDMIDOC)
I'm getting following error message:
At the beginning I thought there is problem with segment structure of Z1P2006 of extension 'ZRMD_A06'
I compared segment Z1P2006 with structure 'P2006' in se11 - and it is the same.
Next I checked the bd21 transaction in debug mode.
I figured out that there is error in FM 'RH_MASTER_IDOC_DISTRIBUTE_HRMD' in include 'LRHALF10'.
Could you please help me?Hello,
Thank you all for your help.
I'm writing this post to provide solution for others like me.
To solve this problem you need to apply this sap note:
HR-CA-ALE: Segment Z1Pnnnn prevents distribution
for me:
As of Release 4.6: In the customer enhancement RHALE001, fill the function exit EXIT_SAPLRHA0_004 with the line
F_idoc_control-cimtyp = 'ZRMD_AXX'.
steps:
1. Go to SE37
2. Enter EXIT_SAPLRHA0_004
3. Double click on INCLUDE ZXHALU08 . (in my case)
4. Add to the code this line: F_idoc_control-cimtyp = 'ZRMD_A06'. (ZRMD_A06 - because I called so my custom extension)
5. and have a nice day because you solved this problem! -
i also need documentation of ALE configuration procedure
hi
check the below links
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
For ALE -- IDoc's
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
ALE/ IDOC/EDI
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/ale/why_ale.htm
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
if u need more info shoot me a test mail to [email protected]
If u find it useful mark the points
Regards,
GNK -
Hi,
I did the ALE configuration in sending and recieving system like creating LS,Assigning LS to Client,Model View For Message type,ports and partner profiles.
When i was trying to distribute the model view it is giving error:
RFC Destination not configured or partner profiles not generated.
I can remote logon from sender system to reciever system and vice versa.
The partner profiles are created for the LS Sender and reciever.
So can any one help me on this issue.
Thank you.Hi Mili,
You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.
Maybe you are looking for
-
How do i delete a video or playlist from apple tv without removing those items from itunes
I don't know how to control content on apple tv. The only way i know to remove a playlist or a certain video from apple tv is to remove the corrisponding playlist or video. how do i manage files on apple tv
-
During the restore from iTunes I get, almost at the end of the restore, the message that iTunes could not restore my iPhone due to an unknown error (1). Can someone help?
-
RE; Adobe flash player problem
I just up graded my adobe flash player to 10.1 and now I cannot get any movie that requires the flash player to play. Anyone else with this issue? HOw do I go back to the earlier version? Thanks for your help.
-
Cover Flow bug in Simplified Chinese version
in both OS 3.1.2 and 3.1.3 Simplified Chinese version. If I use the English/Traditional Chinese version, the bug doesn't exist. Thanks. Message was edited by: cavaus
-
My built-in camera on my MacBook Air has not worked since I bought it.
I did not get the warranty so they would not cover the camera. The techs at the Apple Store couldn't figure it out and I do not have the money for a new one. Do any of you have advice?