IDocs for a Object

Hello,
If i know the Purchase order Number can i find out the IDOCS going out this Object.
In general for any object (can be a Delivery note or Sales order etc) if we want to know the outgoing and incoming Idocs , except by digging in to segmenst and reading teh contents is theer any other way . say FM?
Regds,
Ö
Mandar : It want it in Report , we can even go through relations in forground , that is not the issue.
We need get details in a report.

Hi,
If you have done the message settings for PO while creating PO in Header -> Message, then once PO get created goto ME22 or ME23 and in Header -> Messages. Select the output which you process with TYPE as EDI or ALE and select Processing Log in that you will get the IDOC number.
OR if you are youing ENJOY Transactions then goto ME22N or ME23N and click on Service For Object and then click the Where Used Icon
Message was edited by: Mandar Shete

Similar Messages

Business Object (BAPI/IDOC) for production Order

Hi All
I have requirement where data is coming from legacy system to R/3 via XI to generate a production order. I am not able to get right BAPI/ IDOC for inbound Production Order. Can anyone has done similar scenario. Can u suggest me BAPI or IDOC for same. I am using IS-Mills 4.7 version for R/3
Thanx in advance
Regards
Vinod

HI Vinod,
I think U can use IDOC LOIPRO01 for Production Order...
Regards,
Sridhar Reddy

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc TYPE edidc-docnum.
DATA i_edidd TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
 CLEAR i_msgs[].
 CALL FUNCTION 'WFMC_PROTOCOL_GET'
 EXPORTING
 cps_nast = wa_nast
 tables
 messages = i_msgs
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
 IF wa_msgs-msgv1 IS INITIAL.
 CONTINUE.
 ENDIF.
 v_idoc = wa_msgs-msgv1.
 CLEAR i_edidd[].
 CLEAR wa_idoc_ctrl.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 document_number = v_idoc
 IMPORTING
 IDOC_CONTROL = wa_idoc_ctrl
* NUMBER_OF_DATA_RECORDS =
* NUMBER_OF_STATUS_RECORDS =
 TABLES
* INT_EDIDS =
 INT_EDIDD = i_edidd
 EXCEPTIONS
* DOCUMENT_NOT_EXIST = 1
* DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
 CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
 EXPORTING
 object = wa_nast
 control_record_in = wa_idoc_ctrl
* IMPORTING
* OBJECT_TYPE =
* CONTROL_RECORD_OUT =
 tables
 int_edidd = i_edidd
* EXCEPTIONS
* ERROR_MESSAGE_RECEIVED = 1
* DATA_NOT_RELEVANT_FOR_SENDING = 2
* OTHERS = 3
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 COMMIT WORK.
 ENDLOOP.
ENDLOOP.

General questions on IDOCs and IDOCs for 2 Accounting Interface BAPIs

This post involves several questions pertaining to the topic of IDOC creation. I downloaded a couple of PDFs and tried googling for material on that, but things are far from being clear in my mind.
I tried to put my questions in some order, so we can follow a line of reasoning. Here we go, then:
I have one code where I there are calls to 2 BAPIs:
- BAPI_ACC_ACT_POSTINGS_REVERSE and
- BAPI_ACC_GL_POSTING_REV_POST
I am supposed to prepare/create an IDOC to perform the activities these BAPIs are responsible for, for the sole purpose of providing us much more details on the activities being executed in the system - this is one of the IDOC's features, if I got it right, its highly detailed logging of everything that is going on behind.
Now, the 1st question arises:
From the material I read, I understood that IDOCs are nothing more than data containers, whose sole purpose is to provide a means of communication between two different systems/parties - one of them would usually be SAP. If this is right, than what sort of IDOC would be this one I am supposed to build - if there's not going to be any inter-system communication ? Doesn't it sound strange that pure "data containers" can work as "logging functions" ? Please share some light here.
The 2nd question - after I understand what an IDOC really is - is
then connected to the job I have to do. I found 2 IDOCs which I think have the proper/correspondent basic types for the 2 aforementioned BAPIs. They are, respectively:
- ACC_DOCUMENT_REVERSE01 and
- ACC_GL_POSTING_REVERSE01
Getting back to my understanding of IDOCs, I got that every IDOC is generally made of one control record, data record(s), and status record(s). 3rd question: Where do the segments fit in ? Are the segments definitions of the Data Records ? And why is it that some IDOC types have header segments only and others doesn't have one ? (header segments are not the same as control records, right ?)
Finally, what is the general process flow for creating/preparing an IDOC ? I looked over a couple of forum posts about this but some of them differ one from another in the order of the steps, some don't mention this or that step, so I am still confused.
4th and last question: what comes first ? The definition of a partner, the bonding of a message type with an IDOC basic type, definitions of the inbound/outbound interfaces ?
Any help here would be highly appreciated.
Thanks in advance,
Avraham

Hi Jaya,
Answer 1. Class is a template for creating objects. Object can also be called as instance.
Interfaces allow you to use different classes in a uniform way (polymorphism).
Answer 2. Normal abap is a procedural programming where as by using abap objects we can achieve object oriented programing.
Answer 6. Source code:
In below code i have created a interface and a class which is implementing the interface. I have declared a reference variable of type interface and created a object. Then i have called a method.
REPORT ZABAPOBJECTS_INTERF.
      INTERFACE I1
INTERFACE I1.
METHODS METH1.
ENDINTERFACE.                    "I1
      CLASS C1 DEFINITION
CLASS C1 DEFINITION.
PUBLIC SECTION.
    METHODS: METH2.
    INTERFACES: I1.
ENDCLASS.                    "C1 DEFINITION
      CLASS C1 IMPLEMENTATION
CLASS C1 IMPLEMENTATION.
METHOD I1~METH1.
    WRITE: / 'This is a method one'.
ENDMETHOD.                                                "I1~METH1
METHOD METH2.
    WRITE: / 'This is a method two'.
ENDMETHOD.                                                "METH2
ENDCLASS.                    "C1 IMPLEMENTATION
START-OF-SELECTION.
DATA : REF1 TYPE REF TO I1.
CREATE OBJECT REF1 TYPE C1.
CALL METHOD REF1->METH1.
Question 7: Yes we need to create a class but most probably we use the existing classes.
Regarding BAPi's go through the below links,
http://www.sapgenie.com/abap/bapi/example.htm
http://www.sapdevelopment.co.uk/bapirfc/bapirfchome.htm
Regards,
Azaz Ali.

Text ID for text object BUT000 does not exist

Hi Experts.
I am doing data migration using LSMW with IDoc. I have this error message "Text ID for text object BUT000 does not exist" when processing the IDoc.
Can anyone tell me what is this error about and how could i fix it. A step by step guide would be nice. Really need advice urgently.
I'll definitely rewards points.
Regards,
Julianna

for this u need to maintain the text object and its related text id using the TC: SM31 in rel. view of ur tcode( like MM01, Va01 etc).
first get the view names(1 for text object and 2 for text id) from fun. people.
then go to sm31 with 1 view, create BUT000 .
then go to sm31 with 2 view, maintain text id for the text object:BUT000.

How i need to write a logic to generate idoc for some of infotypes, when i change the single infotype

Hi experts,
I have an requirement , when I change any infotype record from pa30 or pa40, i.e
suppose I am changing the infotype 0002 in pa30 , the idoc only generated for that changed infotype only,
but I need it to generate the idoc for some other infotypes also I.e(0000,0002,t528t, 0016).
So please give me some help to generate idoc when I run a rbdmidoc(bd21).
Thanks in advance.
Venkat

yes, visible bounds is reading the non-visible masked objects too.
you're going to have to do it the hard way, loop through all your objects to get your bounds manually, and while you're at it, test for clipping masks and use the masking path instead.

Sub: How to send idoc for IW31.

Dear All,
Content: My requirement is to send the idoc for maintanance order- IW31. I found the message type as IORDER. I am not able to use change pointer IORDER is not matching, as i am not able to find the message type, when executing BD21 (for change pointer).
Please let me know the procedure for sending idoc for IW31.

This is what it worked for me, to create an INBOUND IDOC to transaction IW31:
I converted BAPI_ALM_ORDER_MAINTAIN to an IDOC
1) In transaction SWO1 copy model BUS2007A to ZBUS2007A (make sure set the status to implemented Edit->Change Release Status->Object type -> to implemented.
2)In transaction BDBG, check Object type, Object ZBUS2007A, Method ORDERMAINTAIN
you can check
http://help.sap.com/saphelp_nw04/helpdata/en/78/21740f51ce11d189570000e829fbbd/content.htm
I Put in Message type ZORDERMAIN
IDoc Type ZORDERMAIN01
the function name will be: ZIDOC_INPUT_ZORDERMAIN
3) configure transaction BD51
4) Configure transaction WE57
5) Configure transaction WE42
6) and Finally Transaction WE20
In my case it worked, still I modified function ZIDOC_INPUT_ZORDERMAIN, and in the call function to BAPI_ALM_ORDER_MAINTAIN I commented the releationship tables.(They were giving me some errors)
Hope this info will help someone.
Regards

Residence Times for Archiving Object

Hi SAP Archiving Experts,
I am working on an analysis Project.I have finalised the List of Archiving Objects and need the residence times fro each archiving object.
Can any one let me know the source from which i can get the Standard SAP Recommended / the BEST PRACTICE for taking the Residence Time for the Archiving Objects...
Mainly : FI, CO , HR Transaction Area Archiving Objects....
Thanks.Kumar

Hello Kumar,
Residence times for archive objects usually differ from company to company as it depends on the needs of the business (and what they will agree to). Some companies will use a standard residence time across all archive objects to make it easy for everyone to remember. For example, some companies will use Current Year plus 2 as a base for all of the transactional data. The technical archive objects (such as idoc's, application logs, etc.), will have a shorter residence time.
Some of the HR objects will have a 2 year residence time hardcoded into the archive programs which you cannot change.
The book Archiving Your SAP Data from SAP Press gives some examples of common residence times. The second edition of this book is now available but I have not seen that yet and do not know if this version provides additional information.
Hope this helps.
Regards,
Karin Tillotson

ALE/iDoc for Work Center data transfer

Hello, community.
I am working on several interfaces for the PP and PM modules using iDocs/ALE.
One of the requirements is that only created and modified data must be distributed from R/3.
For Work Centers, we are using basic type LOIWCS02 and message type LOIWCS. We are generating iDocs through transaction POIM, which has two transfer modes: Complete (data for all Work Centers etc.) and Change (only new and updated data).
The Change Transfer Mode assumes you have set both Change Pointers and Change Documents for the objects to be transfered. Otherwise, it'll work just like the Complete Transfer Mode.
Our PP consultant told me there is no configuration to generate Change Documents for Work Center data modifications.
Can anybody give me other opinions? I'll resort to Z-table solutions only if I have no other options.

Hi Danilo,
Do you know what the process codes are for
LOIWCS and LOIROU ?
Appreciate your help.
Thanks,
Gopi.

Inbound IDoc for WBS data

Hi,
WBS Master Data is stored on an external system (called PRISM).
I need an Inbound IDoc for update in SAP of WBS data sent by external system.
Thank you in advance.
Kieron Kelly

Hi,
Please check the IDOC type : if that doesnt suffice, go with a custom IDOC.
/ISDFPS/PS01
BUS2054001 is a business object that has many BAPI's for processing the WBS data. Check the method and click on ABAP tab for the BAPI/FM names.
Regards
Shiva

How do I execute IDOC for message type LOIPRO

How is it possible to execute IDOC using message type LOIPRO which I have configured with change pointers? Change pointers are using object ORDER.
I am looking to only generate IDOC for production order changes / updates that meets the criteria set by the change pointers. If something in the order changes, but that field is not being looked at by change pointers, I don't need IDOC to pick up that order.
I don't want to have to run RCCLTRAN or RCCLORD on a scheduled job. Only need to have activity if change pointers are activated. Am I going down the wrong road using LOIPRO ?

Hi Bob,
Could you please guide me through the process of creating/triggering a change pointer based LOIPRO? Your help much appreciated.
Tabraiz

Inbound idoc and business object

Hi
1)please provide the code for inbound idoc function module.
my idoc tye contains one segment(s) contains three fields (for ex x , y, z.)
compare segment (s) fields x.y data with databasetable fields (x,y)data.
if sy-sbub rc =0 idoc is posted other wise it is not posted.
please provide code for this (with perfom staments.)
here x is vendor no and y is invoice no
2)for businees object
the records are found after comparing the data of idoc and database table
the vendor invoice(y) file atached to the fb60 transaction code for this i need business object?

Hi
1)please provide the code for inbound idoc function module.
my idoc tye contains one segment(s) contains three fields (for ex x , y, z.)
compare segment (s) fields x.y data with databasetable fields (x,y)data.
if sy-sbub rc =0 idoc is posted other wise it is not posted.
please provide code for this (with perfom staments.)
here x is vendor no and y is invoice no
2)for businees object
the records are found after comparing the data of idoc and database table
the vendor invoice(y) file atached to the fb60 transaction code for this i need business object?

IDOC - Problem booking CLFMAS idoc for kna1 (customers)

Hello,
currently im working on data migration using the lsmw transaction.
My project is to add the classifcation using the message type CLFMAS to customers in kna1.
Every time im trying to process the idocs it fails with error:
"Object 0000010035 (KNA1 ) not found", but the customer exists and is not deleted.
The contents of my idoc:
E1OCLFM
OBTAB KNA1
OBJEK 0000010035
KLART 011
E1AUSPM
ATNAM WST_CM_DEALERTYPE
ATWRT ESA
ATZIS 000
E1DATEM
KEY_DATE 00000000
Why it fails?
Regards,
Christian

HI,
I am also getting the same error while posting CLFMAS idocs for Customer Master Data. Did you resolve this issue? If yes, could you please let me know how to fix this?
Thanks
Dev

Idoc with recurring Object ids(CP) in E1PLOGI.

Hi,
When Idocs for object type 'CP' is getting created the E1PLOGI are getting created with recurring object ids.
In a single IDoc, if multiple E1PLOGI are there, the the 1st E1plogi contains one object id (CP), 2nd one contains 1st and 2nd both , 3rd E1PLOGI contains 1st,2nd and 3rd, all the object ids(CP).
Please explain what's the cause of this kind of recurring insertion of objects in the succeding E1plogis.
Thanks.

Hello,
In my case Inbound - IDOC was generated & process in one thread. there was bug in code which was creating another thread to proces same IDOC.
One thread was processing IDOC with correct status of 53, another was trying to process IDOC it was putting status of 51 on same idoc
Both statuses were on same IDOC.
The possibility of creating new idoc hapens when system try to create IDOC.
In your case, It's just processing of IDOC which happens two times. so new IDOC will not be created.
Regards,
Sameer Desai

Idocs for Purchase RFQ

Hi Friends,
Does anybody knows how to configure, an Outbound Idoc to non SAP application for Purchase Request For Quotation? And after inbound a similar Idocr for update Quotation into SAP using estandar Idocs messages?
Thanks for your help,
Andres.

Hi
Check these links for Idoc
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

IDocs for a Object

Similar Messages

Maybe you are looking for