Reg: IDOC

Moderator message: please use a meaningful subject in future.
Hi,
I created an IDOC to transfer data between clients, same server.
Here I defined the port , partner functions , in both clients. but still i am getting that 'ALE LINK ERROR'.
If anybody knows guide me.
-Thanks .
Balajee Jeyaraj
Edited by: Matt on Nov 19, 2008 11:30 AM

Please check ALE configuration.huge number of threads available on this topic please search

Similar Messages

Reg: IDOC Purchase Order

Hi All,
I have a requirement to trigger a Purchase Order from Stock Transport Order (STO).
So whenever the STO is created, IDOC needs to be triggered & create a auto PO in the same client.
I tried with some examples from forum thread, but all goes in vain.
Could you please advice, what are all the steps needed to achieve this with in a same client. I have created a dummy logical system for Inbound processing with tRFC. Could you please advice this step is really needed.
Thanks & Regards,
Uswin
Edited by: Uswin B on Nov 21, 2011 11:40 AM

1. You need to setup output determination on the STO (transaction NACE, Application EF). You can create output type similar to NEU and assign it to o/p determination procedure linked to your STO document type. You can't use NEU though as it is configured to create ORDERS message type IDoc. To create PO you need message type PORDCR1.
2. You have to write your own function module to output IDoc of message type PORDCR1 and call MASTER_IDOC_DISTRIBUTE to trigger it. It is easy if you only map the minimum required fields so that the IDoc doesn't fail in syntax and take it from there. There are no standard functions that I know that created PORDCR1 message type IDoc (others chip in if you know). You need to create your own outbound process code with ALE processing as medium in the output type.
3. You can set the IDoc from the output type with direct 2 (as inbound) and set up partner profile in the output condition record to point to your inbound LS partner profile
4. You need to assign inbound message type:PORDCR1, IDOC type PORDCR101 and Process code: BAPI to your receiving LS partner profile
Those are the settings you need to do. I can't elaborate as there are many things specific to your implementation

Reg idoc for purchase order

Dear Friends,
I am trying to transfer data of purhcase order (ME21) (with header and item details) from one client to another client.
I am using idoc ORDERS05 for updating the data.
But i am unable to map the fields of the ME21 to the fields of segments of the idoc ORDERS05.
Note: I am using these fields of me21.
*header details
    ekko-ebeln.                             "Purchasing document
    ekko-bukrs.                             "company code
    ekko-bsart.                             " Purchasing Document Type
    ekko-ekgrp.                             " Purchasing Group
    ekko-ekorg .                             " Purchasing Organization
    ekko-lifnr.                              " Vendor Account Number
    ekko-aedat.                            "date on Which Record Was Created
    ekko-pincr.                            "Item Number Interval
    ekko-spras.                            "language
    ekko-zterm.                             "Terms of Payment Key
    ekko-waers.                              "Currency Key
*item fields
    ekpo-ebelp.                             "Item Number of Purchasing Document
    ekpo-ematn.                            " Material Number
    ekpo-txz01.                            " Long Material Number for MATERIAL Field
    ekpo-werks.                          "Plant
    ekpo-lgort.                           " Storage Location
    ekpo-matkl.                          " Material Group
    ekpo-menge.                         " Purchase Order Quantity
    ekpo-meins.                           " Purchase Order Unit of Measure
    ekpo-netpr.                         "Currency amount
pls help.
Regards,
Vinod Kumar.

Hi
chek with currect version of Message type,if it's not in message type do customise segement's.
cheers
venu

Reg : Idoc Transfer From SAP R/3 to Gentran

Hi Floks /
Any body can transfer SAP R/3 idoc to external Sterling Gentran intgration suite . what are process steps required to sending and what are the transaction codes are available in Gentran and Sap .
can u please help me out.
thanks
suresh

HI,
See the below links
In Gentran
XI with Gentran
XI vs Gentran for EDI
SAP ECC 5.0 Upgrade questions with Gentran, BDC, screens
Gentran EDI ?
Interuppting/debugging response from Gentran
Gentran and XI 3.0 question
Interuppting/debugging response from Gentran
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
In R3 IDocs
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
File-XI-IDoc Scenario - File to Idoc
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
see the below links to get more details about IDocs
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
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
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
Process codes in IDOC
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
http://edi.stylusstudio.com/msg04418.htm
Check this link to find out the difference b/w ALE,IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
---Split messages :
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
Regards
Chilla

Reg : IDOC data mapping

Hi All,
Which is the function module which Extracts the data from the application document ( Sales order or quotes ) and populates to the SAP message type Idoc segments.
what are the SAP table involved in doing this mapping.
Thanks & Regards.
vijay

Unfortunately the mapping is not in any table but in the source code as extracted here:
e1cuins-class_type        cuins-class_type
e1cuins-inst_id           cuins-inst_id
e1cuins-obj_key           cuins-obj_key
e1cuins-obj_txt           cuins-obj_txt
e1cuins-obj_type          cuins-obj_type
e1cuins-quantity          cuins-quantity
e1cuprt-class_type        cuprt-class_type
e1cuprt-inst_id           cuprt-inst_id
e1cuprt-obj_key           cuprt-obj_key
e1cuprt-obj_type          cuprt-obj_type
e1cuprt-parent_id         cuprt-parent_id
e1cuprt-part_of_no        cuprt-part_of_no
e1cuval-author            cuval-author
e1cuval-charc             cuval-charc
e1cuval-charc_txt         cuval-charc_txt
e1cuval-inst_id           cuval-inst_id
e1cuval-value             cuval-value
e1cuval-value_txt         cuval-value_txt
e1edk01-autlf             xvbak-autlf
e1edk01-belnr             ekko-ebeln
e1edk01-bsart             ekko-bsart
e1edk01-curcy             iso_waers
e1edk01-kzabs             pekko-kzabs
e1edk01-kzazu             xvbkd-kzazu
e1edk01-lifsk             xvbak-lifsk
e1edk01-recipnt_no        ekko-lifnr
e1edk01-vsart             xvbak-vsbed
e1edk01-zterm             ekko-zterm
e1edk02-belnr             ekko-angnr
e1edk02-belnr             ekko-ebeln
e1edk02-belnr             ekko-konnr
e1edk02-belnr             ekko-submi
e1edk02-belnr             pekko-labnr
e1edk02-datum             ekko-bedat
e1edk02-uzeit             sy-uzeit
e1edk03-datum             ekko-angdt
e1edk03-datum             ekko-bedat
e1edk03-datum             ekko-bnddt
e1edk03-datum             ekko-bwbdt
e1edk03-datum             ekko-ihran
e1edk03-datum             ekko-kdatb
e1edk03-datum             ekko-kdate
e1edk03-datum             pekko-eindt
e1edk03-datum             sy-datlo
e1edk14-orgid             ekko-bsart
e1edk14-orgid             ekko-bukrs
e1edk14-orgid             ekko-ekgrp
e1edk14-orgid             ekko-ekorg
e1edk17-lkond             ekko-inco1
e1edk17-lkond             xvbkd-inco1
e1edk17-lktext            ekko-inco2
e1edk17-lktext            xvbkd-inco2
e1edk18-prznt             ekko-zbd1p
e1edk18-prznt             ekko-zbd2p
e1edk18-tage              ekko-zbd1t
e1edk18-tage              ekko-zbd2t
e1edk18-tage              ekko-zbd3t
e1edka1-bname             ekko-verkf
e1edka1-bname             t024-eknam
e1edka1-ihrez             ekko-ihrez
e1edka1-ihrez             ekko-unsez
e1edka1-ilnnr             h_iln_vendor
e1edka1-lifnr             h_pekko_werks
e1edka1-lifnr             pekko-werks
e1edka1-orgtx             t024e-ekotx
e1edka1-pagru             ekko-ekgrp
e1edka1-paorg             ekko-ekorg
e1edka1-partn             ekko-lifnr
e1edka1-partn             ekko-logsy
e1edka1-partn             lfa1-lifnr
e1edka1-partn             lfb1-eikto
e1edka1-partn             pekko-kunnr
e1edka1-partn             t000-logsys
e1edka1-partn             xvbpa_we-kunnr
e1edka1-parvw             'EZ'
e1edka1-parvw             h_parvw
e1edka1-parvw             'LF'
e1edka1-parvw             'WE'
e1edka1-spras             ekko-spras
e1edka1-telf1             ekko-telf1
e1edka1-telf1             t024-ektel
e1edka1-telfx             t024-telfx
e1edkd1-ekgrp             ekko-ekgrp
e1edkd1-ekorg             ekko-ekorg
e1edkp1-defpa             xekpa-defpa
e1edkp1-ekorg             xekpa-ekorg
e1edkp1-lifn2             xekpa-lifn2
e1edkp1-ltsnr             xekpa-ltsnr
e1edkp1-parvw             xekpa-parvw
e1edkp1-werks             xekpa-werks
e1edkt1-tdid              xt166a_del-tdid
e1edkt1-tdid              xt166k_del-tdid
e1edkt1-tsspras           ekko-spras
e1edp01-abftz             ekpo-abftz
e1edp01-antlf             xvbap-antlf
e1edp01-bmng2             ekpo-ktmng
e1edp01-bmng2             ekpo-menge
e1edp01-bpumn             ekpo-bpumn
e1edp01-bpumz             ekpo-bpumz
e1edp01-brgew             e1edp01-menge*ekpo-brgew
e1edp01-evers             ekpo-evers
e1edp01-gewei             ekpo-gewei
e1edp01-kzabs             ekpo-kzabs
e1edp01-lgort             ekpo-lgort
e1edp01-matkl             ekpo-matkl
e1edp01-matnr             ekpo-matnr
e1edp01-menee             ekpo-meins
e1edp01-menge             ekpo-ktmng
e1edp01-menge             ekpo-menge
e1edp01-netwr             ekpo-netwr*cur_factor
e1edp01-ntgew             e1edp01-menge*ekpo-ntgew
e1edp01-peinh             ekpo-peinh
e1edp01-pmene             ekpo-bprme
e1edp01-posex             ekpo-ebelp
e1edp01-posguid           xvbap-posguid
e1edp01-pstyp             ekpo-pstyp
e1edp01-uepos             ekpo-uebpo
e1edp01-vprei             ekpo-netpr*cur_factor
e1edp01-werks             ekpo-werks
e1edp02-belnr             ekpo-aktnr
e1edp02-belnr             ekpo-konnr
e1edp02-belnr             ekpo-labnr
e1edp02-belnr             h_xvbkd-bstkd_e
e1edp02-belnr             xvbap-werks_ext
e1edp02-belnr             xvbkd-bstkd_e
e1edp02-bsark             h_xvbkd-bsark_e
e1edp02-bsark             xvbkd-bsark_e
e1edp02-ihrez             h_xvbkd-ihrez_e
e1edp02-ihrez             xvbkd-ihrez_e
e1edp02-zeile             ekpo-ktpnr
e1edp02-zeile             h_xvbkd-posex_e
e1edp02-zeile             xvbkd-posex_e
e1edp03-datum             ekpo-abdat
e1edp03-datum             ekpo-agdat
e1edp17-lkond             ekpo-inco1
e1edp17-lkond             xvbkd-inco1
e1edp17-lktext            ekpo-inco2
e1edp17-lktext            xvbkd-inco2
e1edp19-idtnr             ekpo-ematn
e1edp19-idtnr             ekpo-idnlf
e1edp19-idtnr             ekpo-matnr
e1edp19-ktext             ekpo-txz01
e1edp20-ameng             xeket-ameng
e1edp20-ameng             xeket-wemng
e1edp20-edatu             xeket-eindt
e1edp20-ezeit             xeket-uzeit
e1edp20-wmeng             xeket-menge
e1edpa1-partn             ekpo-kunnr
e1edpa1-partn             xvbpa_we-kunnr
e1edpd1-bednr             xekpo-bednr
e1edpd1-bstae             xekpo-bstae
e1edpd1-insmk             xekpo-insmk
e1edpd1-knttp             xekpo-knttp
e1edpd1-kzabs             xekpo-kzabs
e1edpd1-labnr             xekpo-labnr
e1edpd1-lgort             xekpo-lgort
e1edpd1-mahn1             xekpo-mahn1
e1edpd1-mahn2             xekpo-mahn2
e1edpd1-mahn3             xekpo-mahn3
e1edpd1-mwskz             xekpo-mwskz
e1edpd1-prsdr             xekpo-prsdr
e1edpd1-schpr             xekpo-schpr
e1edpd1-spinf             xekpo-spinf
e1edpd1-uebtk             xekpo-uebtk
e1edpd1-uebto             xekpo-uebto
e1edpd1-untto             xekpo-untto
e1edpd1-webre             xekpo-webre
e1edpd1-werks             xekpo-werks
e1edpt1-tdid              xt166p_del-tdid
e1edpt1-tsspras           ekko-spras
e1eds01-summe             ekko-ktwrt*cur_factor
e1eds01-summe             pekko-netwr*cur_factor
e1eds01-sunit             iso_waers
Whenever you have qualifiers, the segments appear multiple with diefferent fields.
Regards,
Clemens

Reg: IDOC Schema

Hi Guys,
My Basis team imported the MATMAS03 IDOC.
When trying to access that IDOC in my mapping, it is showing that IDOC schema doesnot exist.
my R/3 version is 4.5.
Can any one guess what should be the problem.
Thanks,
M.S

Were the changes activated after importing the idoc....
Please check your Change List......
BR,
Sushil.

Reg:IDOC Sender side settings

Dear All,
My scenario is IDOCPIMDM
I have created all the basic ALE settings and they are,
SAP R/3:
1)RFC Destination (SM59)
2)Logical system
2)Port (We21)
3)Partner Profile (WE20) name same as logical system
SAP XI:
1) RFC Destination (SM59)
2) Create Port (IDX1)
3) Load Meta Data for IDOC (IDX2)
In Integration Directory,Adapter-Specific identifiers,its shows the logical system that was created in R/3 server.
Could anyone suggest me on the following queries,
1)Whether I have to create anymore steps other than this.
2)Should I need to create Logical system in PI
3)Should I need to create a distribution model.
4)What are the details ,I should enter in sender/receiver details ,while we use WE19 transaction code for triggering the idoc.
Thanks in Advance,
Lavanya.B

Hi Lavanya,
The steps are the standard steps.
I hope it should work.
In PI, you need to create on LS (Business Service) or Business System.
If you are creating Business Service, it would be mapped via SLD otherwise the Business service needs to be mapped to the indoc(Go to Business Service--> Edit to add Outbound interface as Idoc name)
Regarding Triggering Idoc,
You need to provide the sender and receiver details
Receiver Port
Receiver Partner no
Partner Type
Sender Port
Sender Partner no
Part type
Hope this helps you.
Regards,
Sushama

Reg: IDOC Status Info Report

Hi Experts
I am trying to posting the products/internal orders data via IDOC/ALE.
After the Data loaded into the target system,I required to display the below info:
Initial Data Load Results Report Layout:
Totals
Total number of records read:
Total number of records processed:
Total number of internal orders created
Total number of records in error
Records Created
Material XXXXXX created
Extended to Plant 9999
Extended to sales organization 9999
Characteristic xxxxxxxxxxxxxx created
Records in error
Line 12 Plant 9999 does not exist
Line 13 Sales organization 9999 does not exist
My concern here is as we were loading the data from source to target here via IDOC/ALE.So once the Idoc processed , control won't comes to the developer's view .Then how I can able to publish the above info?
As I am new to ALE/IDOCS can someone throw some light on this.
Thanks for your cooperation in advance.
Regards,
Sreeram Kumar.Madisetty

Hi
So finally you want log of updated records rite ?
Are you Using FM or stand alone program to process the IDOC ?
Standard IDOC or Custom ?
Inbound or outbound ?
For inbound if you are using standard Fm find exit for that Fm and in that u can develope the code like in report .
Finally count the number of records updated .
You are getting some errors records so pass the all error recors into internal table and count the records in that internal table ..
or
IF you are using custom fm u can directly code the requiremtn in Fm like validations .
if you are not clear please revert back and mention ur IDOC and processing Fm so that i can help you more ..

Reg idoc interface

hi all,
its regarding idoc interface,try to help me.
i have a programRHALEINI and defined in Work Item WA00012 - "IDOC Extract for HR Master Data"
This IDoc will be created in SAP but not delivered to any external system.
The interface created in this work item will then read these IDOCs and the required fields will be identified and reformatted so that it can be processed by the FMS system.
Program RHALEINI is executed to create the IDocs for all employees. Refer to Work Item WA00012 - "IDOC Extract for HR Master Data
WI WA00012 will also provide Function Module Z_TP_INI_IDOCS to pull all the IDOCs needed to extract all of the employee data (latest employee extract).
The purpose of this interface program is to read all IDOCs created by program in WA00012 and map the required data into a flat file structure.
here to map i have header trailor and body data how to do this.
provide me solution asap with an example
thanking u

Hi,
Once you get the idocs then you have to read the info from these idocs and then you have to populate it into your file.
It depends on the data format that they want to create it.
cretae a file of type l_v_filename TYPE draw-filep,
then start creating header structure item structure and footer structure.
keep passing data to these structures and transfer it to file
TRANSFER l_wa_header TO l_v_filename_temp
same thing you cna do for ur item data,
loop on this and pass line by line to the file.
same way populate the footer data also.
It entirely depends ont he way they want to populate in the final file.
Reward points if you find useful.
Regards,
Sasi

Reg:idoc to file scenario

q) In idoc to file scenario i used business service for sender R/3 system and maintained adapter-specific identifiers for it,can i use the business system or business service for receiver system and as it is a cross company environment?

Hi Srikanth,
you can use business system which is created for R3 system.There is no need to use the business service for R3.
can i use the business system or business service for receiver system and as it is a cross company environment?
As it is a cross company envirionment, might be you dont have created BS for u r receiver system in SLD. So it is better to use business service for receiver.
Hope it will gives the idea...
Cheers
Veera

Reg: IDOC to file for PEXR2002

Hi folks,
Here my scnario is once fund transfer happend idoc are generated. I have to pick the generated idocs and transfer to a file.
I have done the configuration and design. But after the idoc is generated it is not transfered to XI system how can i debug this to find the reason where it got struck,
Regards
Vijay.

Hi Vijay,
Are you using the Partner is LS or KU?
Go throgh the following thread
Party and Service not found
Go throgh the following blog
Wanna Party ?
Regards
Goli Sridhar

Doubts reg idocs

HI experts,
Where we implement te code for idoc(creation).?please tell me

Hi,
Are you using a custom idoc or standard idoc? If you are using standard sap idoc then SAP provides FM for this. If you want to check the FM name, you can check based on the process code in transaction WE41 ( process code for outbound idoc )
If you have created your own IDOC you write your own FM using transaction SE37.
Let me know if you need any other information.
Regards,
RS

REG: IDOCS

Hi All,
Is there any specific process to import an Idoc in the metadata because when i imported an Idoc directly by using the tab create, i am facing a error while testing the file to Idoc scenario.
Thanks in advance
Siva.

Metadata gets filled at runtime. If you have changed IDOC after running scenario, delete metadata for the message at XI ( T Code: IDX2) and run it. (at XI)
Make sure that Logical System has Outbound/Inbound message type assigned (WE20at R/3) & (IDX1 at XI)
If you have problem retrieving/getting
config at XI end:
SM59: RFC Destination - <SID>CLNT<INS> (target host, system number points to ABAP Server : Client: xxx, user abcd). Check that remote logon works without asking for username/pwd.
at R/3:
Create logical system names in SALE/BD54:
SM59: RFC Destination for XI (same pattern)
SM59: RFC destination to self
SXMB_ADM : Integration Engine configuration: Change Global definition:
Role: Application system
Corresponding Integration Server: http://<host>:<port>/sap/xi/engine?type=entry
nikhil

Reg: IDoc is u0091pushedu0092 into SAP from the external EDI system

Iam facing one issue in our system for message type DESADV (inbound). please read through .
"When an IDoc is pushed in from the external EDI system & even though the inbound Partner Profile is set to immediate processing mode:
The IDoc stays in status 64 - 'IDoc ready to be transferred to application'. This assumes that the IDoc has not been processed yet and still needs to be processed with program RBDAPP01 (or via the process button in BD87).
We don't want to again run this program "RBDAPP01". What was the problem.
I appreciate ur help.

Hi Krishna,
In some other scenarios if an IDocs remains in status 64, it means that the processing within the IDoc engines did not reach its end, where the new status could be set. There are two principal reasons:
1. In the matching partner profile the processing is not set to "Trigger immediately"
2. The application that processes the IDoc abnormally ends with a fatal error (crashes). If this happened you will see a trace in the system log (ST22). In this case have the satellite system write the file to disk but you trigger the EDI_DATA_INCOMING. Then start EDI_DATA_INCOMING from SE37 manually and debug yourself through the individual steps. A good start would be to set a break-point in the application handling function (in your case: IDOC_INPUT_DESADV ).
If useful do reward.
Regards,
Adarsh Srivastava

Azhar--azhar :) reg. idoc

Hi azhar,
I did ALE-IDOC with the help of ur document yaar. It beyond expression....thing is outbound process for message type MATMAS is fine...but when i go to other client....i m not able to see the data in MM03...
I shall be thankful to u yaar...i've give me ur gmail Id. pleas..
Regards,
[email protected]

http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
hi,
steps for ALE IDOC is ::
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC

Reg: IDOC

Similar Messages

Maybe you are looking for