How to transfer the transactional dat a using ale

Question

hi to all abap gurus
i heard that we can transfer the transactional data ( like so data , po data ) using message control technique by ale technology . . can u please give  all steps  in message control technique with one exapmle . i searched in the forum but i did not get answer . pls points will be rewrared for good answers.  if u want to give links pls give exact links .

Answer 1

Hi ,
       here is the configuration.
MESSAGE CONTROL (USING EDI / ALE)
For Purchase order (Message control using EDI and message type ORDERS) – STEPS
Settings to be done in the Sending system
From NACE
Choose Application – EF ( Purchase order), press on condition record
Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – 6 (EDI), time – 4(send immediately), language – EN).
Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – EDI, Partner function –VN)
Create RFC destination from SM59 (ZNARA_ALE_EDI).
Create a port from ZNARA_ALE.
Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE  SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
Basic type –ORDERS05, Message type – ORDERS ) Go to the message control and key in the data (Application – EF, Message type – NEU, Process code –ME10, Transfer immediately )
Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
To transfer the idoc from Client 555 to 500
Settings do be done in 555.
From NACE
Choose Application – EF – Purchase order, press on condition record
Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – A (ALE), time – 4(send immediately), language – EN).
Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – ALE, Partner function –VN)
From SALE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
From SM59 create RFC destination with the same name as that of the receiving logical system  (ZALERECV_N).
From BD 64(distribution model),  create a model view with Technical name ZNARA_PO (message type – ORDERS, Sender – ZALESEND_N, Receiver – ZALERECV_N). Generate partner profiles. Distribute.
Note that partner profile will be generated under LS.
Settings do be done in 500.
From NACE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
IMP data for message control in  Sales order creation.
Partner profile to be created under KU.
Outbond parameters in the partner profile (Message type – ORDRSP, Basic type – ORDERS02, partner profile - SP) In Message control (Application – V1, Message type – BA00, Process code – SD10)
Notes:
Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
Table EDP13 - Partner Profile: Outbound (technical parameters)
Table EDP21 - Partner Profile: Inbond (technical parameters)
Please reward if useful.