About Idocs in HR

Dear All,
     I just want to do IDoc's in HR moudle can any one please tell me , how to do.
     I am very much new to IDOC's and I am aware of HR stuff.
    So, any kind of help will be rewarded.
    Thanks in Advance,
Regards,
Satya.

Hi Satya,
please have a look at following thread
Re: IDoc to IDoc through ALE
You could also search in SDN for a lot of other links about idocs.
Regards
Bernd

Similar Messages

Issue about IDoc Adapter Receiver Channel's Performance

Hi Everyone,
Currently, I am working on a scenario of File -Integration Process - IDoc in XI 3.0 with patch level 16. The scenario works fine when it process one/two/three files in parallel, and the IDocs arrive R/3 system quite fast. But when I try four files in parallel, the whole XI server blocks, I can not do anything even logon Integration Builder, and the IDocs arrive R/3 brokenly, sometime with the invterval to 10 minutes. When the XI comes back, I found all the four integration processes finish successfully and each transaction works fine and fast. What's more, after I change the IDoc Adapter receiver channel to a File Adapter receiver channel, it works fine for even 20 files in parallel. So I think it is some issue about IDoc Adapter receiver channel. Does anyone have the same experience as me? Any comments will be appreciate.
Regards,
Nick

Hi Nick,
Can you check this Blog-
/people/sreekanth.babu2/blog/2005/01/05/delayed-xi-message-processing
May be useful.
How are you picking the files .. You can try with EOIO options while picking the file.
But if you use BPM, it is not applicable. It will act as a EO only.
Check this SAP Note- 833740
Thanks,
Moorthy

Questions about IDoc

Hi ABAPers,
I´m new on IDoc, so I need somebody to help me.
I wish know how can I find where an IDoc is "generated". That is, where the MASTER_IDOC_DISTRIBUTE function is called.
My issue is an IDoc generated during the purchase order process (I guess that in the MIRO), I´ve already tried debug and stop in the above function without sucess.
Any help is welcomed.
Thanks,
Charles

>
Charles Oliveira wrote:
> Hi Krishnendu,
>
> The debug didn't stop in these functions too.
>
> I don't understand so well about IDoc, but what I've, corrects me if something is wrong, is an IDoc (outbound) that is generated in a BADI or an USEREXIT, during the MIRO.
>
> I need know what's this EXIT or BADI, to make some modifications in the information that is passed to IDoc.
>
> Thank you and if you know anything more to help me, I would appreciate.
>
>
> Regards,
> Charles
There is a Concept called Message Control , Here Output type is attached to the IDoc message type and IDoc type. You will maintain this In WE20 partner profile part , in the outbound section.
and at the same time you will maitain the Output type in NACE ,
In NACE you will Configure the output type with medium as ALE/IDOC or EDI
and Program RSNASTED , i am not sure what is used in your case ? , it may be same or it may be Different and custom one.
you go to program RSNAST00 ,
in this you can go to line # 1327 ,
perform (tnapr-ronam) in program (tnapr-pgnam) using returncode
us_screen
if found.
here you keep a break point. and Go to MIRO tigger the output type. if it stops well and good.
if not start Debugging using /H in the messages screen , and Trigger the output by saving it.and then activate the Update Debugging from Menu Debugging->Update Debugging
then F8. it will stop exactly the above perform , and there you check.
and also if you know the output type you can check the Medium and Program used for processing the output.

Details about IDOC

Dear all,
           please give me detail about IDOC i IDES . I dont know about the IDOC.
Thanks& regards
                                                                  sourabh

Hi Sourabh,
IDoc refers to Intermediary Document.
I is primarely a Intermediary Document that is being used for data flow between SAP and other Third Party Tools.
When the user is using a Third Party tool to enter data instead of SAP, and this data has to be moved into SAP, then a I DOC is being created, where in we specify the matching fields between SAP and the fields in the Third Party.
This is used noth ways i.e for receiving data and also sending data to Third Party Tool.
Once the I DOc is being created, we provide the information to EDI consultant who would provide the required link between SAP and the Outside Tool.
Further we use T code WE19 for creating a I DOC and WE02 for viewing it
Hope I have provided enough information to you regarding I DOC.
Regards
Phani

A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
recipient port the port created in step (2)
recipient partner number the logical system name of the dotnet application created in (2)
recipient partner type'LS'
sender port SAP<SID>, where SID is the SAP system id
sender partner number the logical system name the SAP client maintained in step step (4)
sender partner type'LS'
message type the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy

About idoc in xi

1)IF we are sending idoc sap apo to sap crm how can we send multiple records?
2)Can you tell me in what transaction can we see the imported idocs in
xi(i.e idoc metadata)?
3)after compilation of the execution part where can we check the processesd
idoc ?
4)if you see hold status in xml msgs processing what that means?
5) how much file send though xi?

Hi,
1)IF we are sending idoc sap apo to sap crm how can we send multiple records?
> If its IDOC then you could have multiple segments that could be trated as records. Even you could imply the IDOC packaging concept.
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
XI: IDOC to IDOC tunneling - how fast (and easy) can you get?
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Example Program for Mass Processing IDocs
http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
2)Can you tell me in what transaction can we see the imported idocs in
xi(i.e idoc metadata)?
--->In IDX2 you will be able to see the Metadata if the imported IDOC have processed at least once or the Metadata have uploaded in IDX2.
3)after compilation of the execution part where can we check the processesd idoc ?
-->In IDX5 you can check about it. even in SXMB_MONI you could monitor. SM58 will also give you the status if incase it failed
4)if you see hold status in xml msgs processing what that means?
-->It means the message is stuck up in queue go for SMQ1 or SMQ2 and can process manually.
5) how much file send though xi?
--> It depends upon the records available in fiel as well as vloume of data.
upt 2-5 MBs the processing will be fast with XI. But later you need to maintain the better configueration of Integration server.
Even you could process the single fiel in chunks of certain records or size.
Thanks
Swarup

About Idoc sender

Why we don't give CC and adapter for sender Idoc and HTTPs ?
I know that two are in ABAP stack, then how to communicate that and where the XML conversion done at ABAP sys or XI server or conversion not required ?

Hi Venkat
Plain HTTP adapter is part of the Integration Engine so when your message reaches integration engine this adapter changes it in XML data.Refer following link for more details about HTTP adapter:
[http://help.sap.com/saphelp_nw70/helpdata/EN/0d/5ab43b274a960de10000000a114084/frameset.htm]
In case of Idoc XI uses tRFC to post Idoc to integration server.Refer following link for more details:
[http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/content.htm]
PS: Reward points if find helpful.
Regards
Sami

I want to know about Idocs

Hi,
I am very new to SAP - XI. I want to work with idocs. So please help me how to develop a scenario which is having sender as file adapter and receiver as idoc adapter or vice versa.
thank you.

Hi
Complete walkthrough for IDOC - file scenario u can try this ./people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Configuration steps required for posting idoc's(XI)
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
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
to add more....
ALE settings.
SAP XI1) 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 XI 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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name

Questions about IDoc to file scenario

I 'm confused, and have a few questions:
1, we need to define a product for it at least , assign it to either of the systems?
2, we don't have to configure an IDoc communication channel, do we?
3, does the receiver system (file/ftp) need a logical system? and define it by t-code BD54, in XI or R/3?
4, at least define techinical system and business system for R/3?
Can you explain the sld configuration to me ?
thanks a lot.

Hi,
,1) we need to define a product for it at least , assign it to either of the systems?
    Ans: Yes we need to define a product.
2, we don't have to configure an IDoc communication channel, do we?
Ans: Sender agreement and Sender IDOC communication channel is not required as IDOC adapter
        resides on ABAP stack.
3, does the receiver system (file/ftp) need a logical system? and define it by t-code BD54, in XI or R/3?
Ans: For third party system from ID create the business system and use that Business system for File or
        FTP system.
Business System.
1.Goto Business Landscape->New Business System->Name the business system.
2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.
Business System have an entry in the SLD and Buiness Service do not.
Business Systems are used when you are sending data to and from an R3 system and can be of ABAP, JAVA and Third Party Types.
Business System is a logical representation of a Technical System.
Business Service is a abstract representation of a System. For instance, www.google.com have a several system working together and IPs of this machines change eventually. When we use a Business Services like google we reference a computer that we don't know the phisical implementation.
4, at least define techinical system and business system for R/3?
Technical System
In SLD, click on technical landscape->New Technical System->WebAS ABAP.
Ans: Yes : Technical system is a phisical machine, it have a IP. Can be a BBDD, ERP, J2EE ......... a Business System is a logical term that we use into the Business Scenarios and represent these Technical System that we had created.
Can you explain the sld configuration to me ?
SLD is the place where u can define systems that are existing in ur landscape. using these systems u can transfer data from one system to another using PI.
TBIT40:
https://websmp109.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT40
/people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak - SLD preview
SLD - http://help.sap.com/saphelp_nw04/helpdata/en/6e/fba1c735e0b44496072595092d924c/frameset.htm
Error while reading ID of own business system from the SLD
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30f8bd90-0201-0010-dd9a-c8a7f52c47aa
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55414
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c00e7efc-0f27-2a10-d9a2-c46fc3863c20
Check this out
http://help.sap.com/saphelp_nw04/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm
Log into SLD and click the Help Link
You will get the detailed documentation for SLD for your version
Thanks,
Satya Kumar
Reward if it is useful
Edited by: SATYA KUMAR AKKARABOYANA on Apr 24, 2008 12:30 PM

Explain about Idoc to soap scenario

Hi All,
I am beginner to sap pi can anybody help me out, How to perform Idoc to soap scenario...

Dear Gaffar,
Please use the search functionality to learn.
Redirecting...
http://www.google.com/cse?cx=013447253335410278659%3Ak8ob9ipscwg&ie=UTF-8&q=idoc+to+soap+scenario&siteurl=www.google.com…
try out the scenario,create the thread if you face any issues.

Question About IDOC ADAPTER

I test a scenario as file->xi->IDOC->R/3
and another scenario as R/3->IDOC->XI-file
i think, it should be two Communication channel
to R/3,one is Receiver another is Sender
But when i create the channel ,after select the adapter
tyep as IDOC, i can not select the Channel as a Sender
Can only set it as a Receiver
why?
and when i test the first scenario , the flowing error
appers(my test idoc message is 'CREMAS03':
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>I:IDOC_ADAPTER:209 66609E10320A11D9ABCB000F1F6BBAD1 E1LFA1M</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I:IDOC_ADAPTER:209 66609E10320A11D9ABCB000F1F6BBAD1 E1LFA1M</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
all of setting seems fine.

The IDOC adapter does not need a sender channel, as all information the XI needs are stored in the message itself. Sender channels are requested mostly for polling adapters like file of jdbc. HTTP-, RFC-, IDOC- and XI-adapter do not need a sender channel (see manual for further details).
The error message seem not to be translated in your system. Here is the message text:
"MSGGUID &1: Control record must start with tag EDI_DC40, not &2"
So in the payload there is no control record for the IDOC.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

About idoc to file scenario

hi experts,
i am getting error while doing RFc connections(R/3 side) in idoc to file scenario, timed out error (cpi_c),
could anybody solve this problem?

Hi friends,
here is new document for IDOC TO FILE scenario..
http://jskcomput.blogspot.com/2013/08/idoc-to-file-scenario.html

Doubt about IDOC Adapter

Hi all,
i'm using idoc adapter for generating IDOCS from R/3, and my scenario is: IDOC->XI->File. this is working fine, in R/3 i've got partner profiles for diferent vendors(suppliers) and they are configured for create idoc message in R/3 and all this message are caught by XI from my scenario and generate the corresponding text file.
but now suppose that I need another scenario because i need to send purchase orders by mail instead file to some of my vendors in R/3. the scenario would be IDOC->XI->Mail.
for both cases i would use ORDERS05.
i can't undertand how XI knows wich scenario have to use, if there's nothing from R/3 that tells XI which scenario should be used.
thanks, Fabian.

Thanks for responses, I know what should i use to do what i wanted. but i've tried to make a condition in the receiver determination and it's giving me an error saying that 'No receiver could be determined'.
i've searched in other threads and i have seen that utilizes xpath to make conditions
what i have done is add a condition in Configured Receivers as '/p1:ZORDERS2/IDOC/EDI_DC40/RCVPRN = 0000010598'
because depending on the partner, i want to use either one or other adapter (file or mail)
do i have misedd something?

Query about IDOC XML Port

Hi,
I'm trying out the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4443. [original link is broken] [original link is broken] [original link is broken] But, I don't see any advantage of using this as it's like appending the file (because each IDoc xml will have it's own start and end tag). Please clarify.
Thanks in advance.
Regards,
Joe.

Hi Joe,
In that case, the root node's occurances should be changes from 1:1 to 1: unbounded.
In general, the idoc's minimum and maximum occurances will be 1.
You have to download the XSD of the standard IDOC and edit the root node occurances to:
xsd:element name="IDOC" type="ORDERS.ORDERS05" minOccurs="1" maxOccurs="unbounded"
then upload the new XSD as external definition.
Then use this external definition as the source structure in the mapping.
Regards,
Ravi

About idocs

hi to all
pls tell me ,for one idoc scenario ,sender side and reciever side what configurations would be configured.
thinks & regards

Hi
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough 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.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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
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.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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
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
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji

About Idocs in HR

Similar Messages

Maybe you are looking for