ALE Idoc Change Pointers Question

Though I selected Transfer Immediately on Partner Profile screen, why Idoc hasn't been generated and transmitted?. Why do I have run RBDMIDOC explicitely to pickup change pointers?. Appreciate your responses.

Hi Appana,
Thank you for your time. I did checked all these steps still no luck.
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
DONE
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
DONE
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
DONE
2.BD50 -Activate change pointers for ur message type
DONE
3.BD52 - add the triggering fields and corresponding tables and change document object.
DONE
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
DONE
Any places I missed ? Please note usual ALE config has been done like SM59,WE,20,WE21 etc. Iam basically sending this Idoc to XI and then to 3rd party system.

Similar Messages

ALE IDOC change pointers - Msgtype CLFMAS

When making a change to a material class of a material a change pointer is created (as expected) for message class CLFMAS.
In the IDOc segment E1OCLFM of CLFMAS, OBTAB = ESTVA (instead of MARA as expected).
Where does this config take place?

Hi Appana,
Thank you for your time. I did checked all these steps still no luck.
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
DONE
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
DONE
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
DONE
2.BD50 -Activate change pointers for ur message type
DONE
3.BD52 - add the triggering fields and corresponding tables and change document object.
DONE
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
DONE
Any places I missed ? Please note usual ALE config has been done like SM59,WE,20,WE21 etc. Iam basically sending this Idoc to XI and then to 3rd party system.

ALE Idoc Change Pointer Question

Though I selected Transfer Immediately on Partner Profile screen, why Idoc hasn't been generated and transmitted?. Why do I have run RBDMIDOC explicitely to pickup change pointers?. Appreciate your responses.

Hi Appana,
Thank you for your time. I did checked all these steps still no luck.
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
DONE
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
DONE
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
DONE
2.BD50 -Activate change pointers for ur message type
DONE
3.BD52 - add the triggering fields and corresponding tables and change document object.
DONE
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
DONE
Any places I missed ? Please note usual ALE config has been done like SM59,WE,20,WE21 etc. Iam basically sending this Idoc to XI and then to 3rd party system.

ALE/IDOC Change Pointers for Custom Table

Hello all,
There is a requirement for my client, to trigger IDOC based on the Custom Table changes. The custom table has a maintenance view and will be updated/modified/deleted randomly by user. Now, i need to track the changes in that table and should trigger IDOC for the changes. The Message type i am using for this is MATMAS, as I need to incorporate changes to the same IDOC.
Is it ok to modify BDCP/BDCPS tables to update the changes from custom table? The Custom Table changes can be tracked through DBTABLOG......and i have my logic to trigger the IDOC
The question is: If i do modifications to BDCP and BDCPS, how this will impact? In future SAP upgrade/enhancements will this affect anyway? Can any one of you share your experience regarding this. Thanks.

Hi Raja,
You can send IDOC based on table maintenance event
I think you can code in event 02, to generate IDOC.
Check below link:
http://help.sap.com/saphelp_nw04/helpdata/en/91/ca9f0ea9d111d1a5690000e82deaaa/frameset.htm
Regards,
Nisha Vengal.

In ALE/IDOC Change Pointer using Maintenance order for message Type

Hi All Expert,
I am using Maintenace order to send via ALE/IDOC(Change ponters), i need standard message Name for Maintenance Order,

Hello,
I'm not sure you're taking the best approch.
Usually when you need to migrate ISU contracts into an ISU-CRM integrated system, you first migrate everything you need in ISU through the VERY powerful migration workbench available (transaction code EMIGALL), and then you replicate your data to CRM via INITIAL download.
That's definitely the strategy that will give you the best performance, and less work.
Kind regards,
Nicolas Busson.

Idoc and change pointers question.

Hi everybody,
How can I create a change pointer automatically for a change document on table JCDS? Becuase I can create change pointers for the change documents on table CDHDR, but I need to catch a technical object status change and create an idoc for the object that changed its status.
Thanks,

Hi Fernando,
I'm trying to accomplish the same thing that you were... trying to get a change pointer to be created based off the status change of a technical object (functional location or equipment).
Can you give me any detail on what you did?
Thanks,
John

ALE configuration - change pointers

Hello,
Iam trying to create idocs whenever there is a change in the customer master i need to trigger an idoc.Iam trying to use change pointer for that.
I checked in bd61,bd52,bd50 all the settings are ok.
but still idocs are not created when i change the customer master...
Do i need to run BD12(RBDMIDOC)...?or am i misssing any other settings...(When i tried to use bd12 to send customers iam able to generate idocs so my model is working...).
Second question I need to send DUNS number in the idoc which Iam not able to find in DEBMAS/DEBMAS04 how can i send that...?Even if i extend how can i populate it ...I dont find any user exits for MASTERIDOC_CREATE_SMD_DEBMAS which holds the control record....?
can anyone help....
Thanks
Larry

Hi Joseph,
The above process is for outbound.
the tool used behind for the process is SMD tool (Shared Master Data tool)
based on the configuraution steps as below they work
BD61 - activates the Change pointers tool (SMD)
BD50 - is for activating Change pointers specifically that message type
BD52 - is for activating Change pointers specifically for that message type and specifically to a field in belonging to that message type
and the CMD (Customer Distribution Model also need to be configured)
you can come up with furthere questions

Help With IDOC Change Pointers

Hi guys,
I'm trying an IDOC to file scenario. The scenario is working fine. I have activated change pointers for my IDOC. My understanding was that if there will be any change in my master tables, then because of the activated change pointers, the IDOC will be generated automatically. But in my case, for eg if i'm inserting any new record say Vendor data, no new IDOC is generated. For sending IDOC i have to use bd14 to send my IDOC explicitly.
Is my idea of change pointers wrong???Or am i missing some setting, so that the IDOC should be generated automatically???
Please help me on this guys...
Regards
Varun

Automatic generation of IDOC when we change the MASTER DATA:
Change Pointers:
Change documents are working based on change document technique which
tracks changes made to the key documents (Material Master, Customer Master,
Vendor Master.Etc) in SAP.
Changes made to the keydocuments are recorded in the change document Header
table i.e. CDHDR and Item table CDPOS, Additional change pointers are written
in the BDCP and BDCPS tables.
Change pointers technique is used to initiate the outbound process automatically
when master data is created or changed.
A standard program RBDMIDOC is sechuled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the Masterdata to the appropriate destination.
'Object' is collection of fields of different database tables. T.code for creating an object
is SCDO.
Configuration for Change Pointers:
1. BD61 Active change pointers generally
 - Check the checkbox "Change pointers activated -generally"
 - Save it
2. BD50 Active change pointers for Message Type
Message Type Active
MATMAS Check the check box
3. SCDO Change Document Objects
 - Check whether the "MATERIAL" is available in the object list.
4. BD52 Maintain Table Views
- Enter the Message type "MATMAS" and press enter.
For example
OBJECT TABLE NAME FIELD NAME
MATERIAL MARA BISMT
5. BD60 Additional data for message types:
For example:
Message Type Function Module Table
MATMAS MASTERIDOC_CREATE_SMD_MATMAS MARA
6. WE21 Port
7. WE20 Partner Profile
8. BD64 Distribution Model
as michal said we have to use RBDMIDOC program.for executing this program we need to give message type like
MATMAS or
DEBMAS or
CREMAS
depending on your requirement.
go to SE38 tcode
--- copy RBDMIDOC to zprogram(i'e., ZRBDMIDOC)
---create variant
use this zprogram(ZRBDMIDOC) in BACKGROUND SCHEDULING SM36
STEPS IN BACKGROUND SCHEDULING:
Use tcode SM36
Click Job wizard in the button set
Click Continue
Enter Job name and press continue
Select ABAP program and press Continue
enter Program name and press continue
and again press Continue
set Schedule type immediately and continue
Select periodic job checkbox, press continue
Select none of the above and click on other periods give one-minute and then press create
Press continue and then press complete.
recently i did this requirement
if u have any doubts plz let me know
Best Regards,
Srikanth
Reward the useful answers and you will get one point yourself

IDOC Change pointers is table BDCPV still used nowadays

Hi,
I got a do something with idoc transfer. I got a document with described what to do.
One of the things to do was to get Change pointer data out of tale BDCPV. But in that
table hasn't been written anything last year.
i have activated changepointers with tx BD61
i have activated the change pointers for the right invidual meesage types tx BD50
i can create the idocs with tx BD21 or program RBDMIDOC.
i see another table BDCP2 is filled with data. Has there anything changed with Change Pointers last years?

Hello,
SAP recommends the usage of the change pointer table BDCP2 instead of BDCP/BDCPS.
You can get further details in SALE -> Modelling and Implementing Business Processes -> Master Data Distribution -> Replication of Modified Data.
BR,
Suhas

ALE IDOC related basic question

Hi Gurus,
I am new for SAP please clarify my quary.
In SAP R/3 we have the one data base server, every one have authorization for access data form data base,they can extract data from data base, that time what is the need to distribute the data form one client to another client using ALE throug IDOC and some other methods also.
Hi i have the doubt on this, Please dont feel cilly.. please clarify me clearly.
Thanks & Regards
Sri Sairam

Hi Sai.
Very good question, first think is data is client dependent. Dont think that all user will have access to all clients of the SAP system. In some projects we can see different clients in the same server (lets take development box), in one client we can develop the program and in another we can do the unit testing. In this case if you want to keep the data in both clients then we need to distribute them. You may have seperate clients based on the application also (like client for FI, seperate one for SD, like that - in dev to do testing).
But in most of the cases we can see data distribution scenarios in between 2 servers, since master data will be maintained seperately.
Thanks
Satya

Change pointers using ALE/IDOC configure

how configure CVhange Pointers using ALE/IDOC

Hi,
[Change pointers configuration|Change pointers]
For more info you can search in SCN, you will get more.
Thanks!!

Change pointers for the ZSEGMENT of IDOC Extension.

Hello Experts,
We are working on the SAP version ECC 5.0.
Our requirement is creating the ZZField and use this field to interface with legacy systems in the trnx FD02 and table KNB1.
We have created the ZZField in table KNB1 and also ZSEGMENT for the IDOC DEBMAS06.
We want to add the IDOC change pointers proramme for this ZSEGMENT that is being created.
I know there are two methods of doing this:
OLD METHOD:USER EXIT....
NEW METHOD:CALL CUSTOMER FUNCTION'...'
I tried the old method with the user EXIT_SAPLVV01_0001 for the Cutomer master.
But I am getting the error as
PROGRAMME NAMES zx....ARE PRESERVED FOR THE INCLUDES OF EXIT FUNCTION GROUPS.
Can any one tell me how do i need to write the programme for the IDOC CHANGE POINTERS for the ZSEGMENT?
Thank you.

Our requirement is creating the ZZField and use this field to interface with legacy systems in the trnx FD02 and table KNB1.
We have created the ZZField in table KNB1 and also ZSEGMENT for the IDOC DEBMAS06.
in the above question watr the fields ur going to populate in KNB1 TABLE or in ZSEGMENT FOR DEBMAS06.
CAN U PL GUIDE ME..
thanking u...
ajay

About ALE,Idoc, EDI

sir,
what is the purpose of ALE,Idoc and EDI, what is the difference and how they will useful for sap
suggest me

Hi
can anyone send me the good links for EDI concepts.explain me a bit about the creation process .
EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
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
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Links
IDOC
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
IDOCS
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE/ IDOC
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
Have a look at these good links-
EDI
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi2.jhtml
http://www.sapgenie.com/sapgenie/docs/i830v3020.xls
http://help.sap.com/saphelp_46c/helpdata/en/0b/2a655d507d11d18ee90000e8366fc2/frameset.htm
http://www.hud.gov/offices/hsg/comp/edi/0306sec1.cfm
http://www.sapgenie.com/sapedi/index.htm
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.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
http://www.sapgenie.com/ale/whitepaper.htm
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
ALE/ IDOC
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
EDI
EDI interface is used to link/communicate SAP system to some external system. like .NET application. IDOC's are used for communication purpose.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
ALE/IDOC
ALE interface is mostly used for communication within different R/3 SAP systems. like you have a distributed environment and you need to share data between two SAP systems then you will use ALE/IDOC technique.
http://www.sapgenie.com/whitepapers/ale.htm
http://www.sapgenie.com/ale/index.htm
http://www.sappoint.com/abap.html
http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
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
check these links.....
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.onestopsap.com/interview-Question/ale/
http://www.onestopsap.com/interview-Question/edi/
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htmhttp://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docPlease check this link for EDI/ALE/IDoc online documentation.

http://www.easymarketplace.de/online-pdfs.php
Thanks
Mohan
Award points if it adds information.

Hi friends need some help in ALE IDOC !

For training purpose I am trying to create an IDOC using ALE
where I am using the same client as server as well as receiver......So I am using as receiver "NONE" . this is already present in the SM59 under logical systems..
But i cant create a port for that...as its saying its not compatible with the TRFC "
Can any one tell me what is the way to create the port ?

Hi,
You are new to ALE and IDOCs so I am giving all step by step to do the ALE.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
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
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Thanks
Sarada

Status 51 Error in ALE IDOC

Hi,
Iam trying to send a MATMAS Idoc from one client to another client , which is in the same R/3. The outbound staus is 03 and the inbound is 51.
I just created a material (Material details are attached below for reference) and send tht material to the other client using BD10.
can you please tell me the Inbound function module name which i should use to post it again.
Material Name:KRMATERIAL
Industry sector : Mechanical Engineering
Material Type : Finished Products.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
Thanks
-Karthik

Hi Karthik,
Just follow the procedure, this is for MATMAS
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Reward Points if this helps,
Satish

ALE Idoc Change Pointers Question

Similar Messages

Maybe you are looking for