Need of Process code in ALE Inbound Processing?

Hi All,
What is the need of process code in ALE Inbound Processing? Why do we need to reach the function module through process code? we can as well directly point to function module.

Hi Ravi,
Please chcek this link perhaps it may help.
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

Similar Messages

Wrong processing code used in inbound processing

Hi
We are on 4.6C and have configured a dist. model for material distribution using message type MATMAS. On receiving end IDOC is properly received but processed with code 51 which is "IDOC Interface not complete for message type".
While testing it in we19 with standard inbound option we found that its using process code AFSA though in the inbound partner profile its set to MATM. (In the table tbd52 AFSA is not even defiend for MATMAS but for ARTMAS) While using INBOUND FM option there with FM specified as IDOC_INPUT_MATMAS_MDM we were able to process the IDOC properly in receiving end. We are not sure which code is being defaulted to during automatic inbound processing but we guess its same as AFSA as shown during standard inbound option. It will be of great help if someone can explain what might have gone wrong.

Dear Renjith
I got it. Actually the process code was correctly attached in sending system but in receiving system it was unfortunately set to AFSA which I ignored. Thanks a lot for the response.
regards
saurav

Interface for function module is incorrect in ALE inbound processing

I have created a custom function module and i assign this FM
to the custom process code for ALE INBOUND process and i already assigned this Fm to message type and basictype in Tcode we57.i have assigned this process code to the msgtype in WE20 also.
But while trying to execute the inbound function module through WE19, I get an error message: "interface for the function module is incorrect". What could be wrong?

Hi
if you ibserve clearly all the FM's will be having same parameters. Your function module also should contain same interface. Ensure that your FM does contain the same.
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED

ALE INBOUND Process Code

Hi,
In ALE INBOUND Process Code Apart from the Function Module name, what are the important things to be filled up while creating that InBound process code in WE42. What is the importance of those? what is the importance of Object Attributes in that?

Hi Mahesh check this may be useful to you
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
Link Message Type to Function Module (WE57) Client independent
u2022 Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Define FM settings (BD51) Client independent
u2022 Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
u2022 Click on New entries
u2022 Enter 0 for mass processing in the output column
u2022
Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
u2022 Log on to the appropriate receiving system client
u2022 Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
u2022 Choose Inbound with ALE service
u2022 Choose Processing with function module
u2022 Click on Processing with function module and choose create icon
u2022 Click on New Entries
u2022 Type in process code XXXXXXX and give it a description and save
u2022 Now you are asked to Please maintain codes added in ALE entry methods, enter and choose XXXXXX and copy it. You should choose a FM similar to your one.
u2022 Enter your process code XXXX
u2022 Enter your function module XXXXXX
NOTE: The next 6 steps are used in workflow error handling.
u2022 Enter IDPKFIDCMT in object type
u2022 Enter MASSINPUTFINISHED in End event
u2022 Enter IDOCINVOIC in IDoc object type
u2022 Enter INPUTERROROCCURREDFI in IDoc start event
u2022 Enter INPUTFINISHEDFI in IDoc End event
u2022 Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object XXXXXXXX, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
u2022 Add the message type XXXXX with process code XXXX.
u2022 Enter the output mode (background, immediately) for inbound processing and NO message code.
Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
You can find all the inbound and outbound processcodes in we64.
Regards,
SMS.

What is a process code in ale idoc

what is a process code in ale idoc,what is the purpose of Process code.

Hi,
     Let me tell some scenario then u would be able to understand what a process code is-------
In ALE ie, the data requested system is receiver and the data already presented system is sender ie, from where we are having the data,
here in sender side----
       we need a program to tranfer required data into idoc--( idoc is just a data container )    in sender side this program logic is in a function module it is configured in we41.
         ie this will transfer the data from database to idoc----in sender side it is a process code
and in receiver side after receiving the data we have to post it in database again program needed it is also ie the required code is also in function module it is configured in we42
it is about receiver side f.m or simply process code
okkkkkkkkkkkk

How to write processing code for the Inbound IDOC to the R/3 ??

i m having a file -> XI-->R/3 scenario,
IDOC is being sent from XI to R/3,
can u guide to me to write a processing code for the Inbound IDOC to the R/3,
since i m new to ABAP and ALE technology, can we provide me any blog for doing that.......or guide me....

Hi Sudeep
Simple File to Idoc scenarion blog
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
Also see the blog
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar.
Configuration of IDOC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
Regards
Santhosh
*Reward points if useful*

. What is a process code in ALE

. What is a process code in ALE
could u plz explain clearly

hi,
a process code represent function mod.,
Process code will come in to picture when you deal with IDOCS .. you need to assign a code which internally will have a Function module or a Include, that will have entire code to run your bussiness for an IDOC or EDI or ALE.
reward useful points,
siva
Message was edited by:
Shan

[HELP] ALE inbound process and Workflow handling problem

Hello,
first of all, i have to apologize about my english level. I will try to explain my problem (thanks for your patience ).
Well, I'm implementing an ALE inbound interface. My development at this point are:
- Customer Idoc Inbound function (with correct interface).
- Customer Basic Type
- Customer Message Type and correct assignment to the Basic Type (Tx WE81 and WE82)
- Customer Object Type (Subtype of IDOCAPPL)
- On BD51 I put "1" for my function.
- On WE57 I put this:
Processing by --> My function and type "F"
IDOC type --> My Basic type (without any extension)
Message --> My message type (without any message code or msg. function)
Object --> My object type (subtype of IDOCAPPL)
Direction --> "2" (Inbound)
- I created a process code for this interface (on WE42):
It is processed with ALE service and by a function module (my function).
On "Module(Inboud)" part I put my function and maximun number of repeats "0". On IDOC part I put my Object type with start event "INPUTERROROCURRED" and end event "INPUTFINISHED".
On application objet I put my Object type.
Rests of fields are blank.
- I defined a partner (WE20) with this new message type and process code.
- Also I created a Task (PFTC) for handle exceptions in inbound process. It has a rule for agent determinate.
I think it is all.
My problem is: when I process an IDOC (from WE19 for example) and it gets 51 status (error), it has to launch an event that trigger my task, is this way? Well I'm not getting any event.
I have all Workflow customizations OK (in this systems are running some Workflows).
In my function code, when I detect any error I put an error in the status table and put in WORKFLOW_RESULT the number '99999'.
Why I'm not getting any event? What I'm doing wrong?
Thanks in advance. Regards.

Hello again,
finally I've solved the problem. The solution for me, was a config on tx. WE42 and some missing code in the function, I only fill WORKFLOW_RESULT with '9999', but I didn't add any register to RETURN_VARIABLES table.
Regards.

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

DELV process code triggers unwanted inbound idoc!

Hi,
I am creating a delvry03 idoc with message type shpord.The process code is DELV.I am sending the idoc from LS to KU.I maintained the outbound parameters in both receiving and sender systems.The outbound is creating perfect.However, there is an unwanted inbound idoc that is being created.All the inbound idocs getting created in this way is in error.I am not able to understand why the inbound idoc is getting created.
I see DELV as both outbound and inbound process codes, but then i am not able to understnad why shpord message type is getting processed.I have not done the distribution model as the receiving system is customer.
Could someone help me out in this weird scenario.Thanks

Duplicate in ABAP General deleted. Post in ONE forum only, please.
matt

Re: ale inbound processing

Hi,
Hi,
I succesfully done configuration and customized all the inbound and outbound fms. When i send material text , it is successfully transported to external system.
But it is showing success status in the sender system status and it is showing warning status i.e 64 means that idoc is ready to transfer to application in inboudn processing.
this is my outbound fmcode:
DATA: XTHEAD LIKE THEAD.
DATA: TLINES LIKE TLINE OCCURS 0 WITH HEADER LINE.
CLEAR: XTHEAD,TLINES[],TLINES.
LOOP AT IDOC_DATA.
CASE IDOC_DATA-SEGNAM.
WHEN 'YTEXT_HEAD'.
MOVE IDOC_DATA-SDATA TO XTHEAD.
WHEN 'YTEXT_LINE'.
MOVE IDOC_DATA-SDATA TO TLINES.
APPEND TLINES.
CLEAR TLINES.
ENDCASE.
ENDLOOP.
call function 'SAVE_TEXT'
exporting
CLIENT = SY-MANDT
header = XTHEAD
INSERT = ' '
SAVEMODE_DIRECT = 'X'
OWNER_SPECIFIED = ' '
LOCAL_CAT = ' '
IMPORTING
FUNCTION =
NEWHEADER =
tables
lines = tlines[]
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
OBJECT = 4
OTHERS = 5
if sy-subrc <> 0.
idoc_status-status = '51'.
idoc_status-msgty = 'E'.
else.
idoc_status-status = '53'.
idoc_status-msgty = 'S'.
call_transaction_done = 'X'.
endif.
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-msgv1 = idoc_contrl-idoctp.
idoc_status-msgv2 = xthead.
idoc_status-msgid = '00'.
commit work.
can anyboyd tell what is the problem.
rgds
p. krishna prasad

Hi,
Change the partner profile settings in target system to process idoc's immediately
when they reached to the system.
or else process 64 status idoc's using BD87 transaction.
Regards
L Appana

Purpose of Process code

Hi what is purpose of Process Code
I know there we add Msg type and Function module what is its function that function module will helps in getting the data
and *what abt Msg type* and Process code there

Hi,
R/3 uses the method of logical process codes to detach the IDoc processing and the processing function module. They assign a logical name to the function instead of specifying the physical function name.
Logical pointer to a processing method
The IDoc functions are often used for a series of message type/IDoc type combination. It is necessary to replace the processing function by a different one. E.g. when you make a copy of a standard function to avoid modifying the standard.
Easily replacing the processing method
The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.
For inbound processing codes you have to specify the method to use for the determination of the inbound function.
After defining the processing code you have to assign it to one or several logical message types. This declaration is used to validate, if a message can be handled by the receiving system.
The inbound processing code is assigned analogously. The processing code is a pointer to a function module which can handle the inbound request for the specified IDoc and message type.
The definition of the processing code is identifying the handler routine and assigning a serious of processing options.
Processing with ALE
You need to click "Processing with ALE", if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios.
Associate a function module with a process code
Table TBD51 to define if visible BTCI is allowed
For inbound processing you need to indicate whether the function will be capable of dialog processing. This is meant for those functions which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.
WE41 Process code outbound creation
WE42 Process code inbound
Regds
Sivaparvathi
Please reward points if helpful............

Process code in idocs

WHat is the purpose of the process code in the inbound processing od IDOCS(WE42)

you need the process code to determine which Function is used for creating/processing the IDoc.
Go to WE20 (Partner) and choose you inbound processing messages.
In the first tab you´´ll find the processing code.
Transaction: WE42 to define the processing code
Tcode: WE57 and BD51 to map the Function to this processing Code.

Problem in ALE inbound With process code

i want to give a function module to the in bound process code in transaction WE42 but i am not able to give the function module name .after giving the function module name if i say save system giving message "The ALE table is not yet maintained for process code ZTEST".

Hi,
This are the steps which involoves the Idoc processing .
For ur query, check the bold letters .. do that part . it will solve ur problem
Create Idoc type Transaction WE30.
Idoc type Idoc segments
Z_idoc
Create Message Type Transaction WE81.
Message type
z_msg
Assign Message Type to Idoc type Transaction WE82.
Idoc type Message type
z_idoc z_msg
<b>Create a function module through SE37
z_idoc_input
Assign characteristic of function module BD51
Assign fn module to Idoc type and Message Type WE57
Idoc type Message type Fn Module
z_idoc z_msg z_idoc_input
Create Inbound process code and assign inbound function module Transaction WE42.
Process code Inbound function module
zcode z_idoc_input</b>
Create a distribution Model - Transaction BD64
Create distribution model for distribution of messages
with the message type of z_msg
Update inbound parameters of the Partner profile Transaction WE20
For the Logical system A for the above message type update the partner profile
inbound parameter and specify the process code of zcode.
For Outbound ALE Configurations: (Example)
IDoc definitions and necessary ALE configurations settings for the outbound .
Create Idoc segments Transaction WE31.
Create Idoc type Transaction WE30.
Create Message Type Transaction WE81.
Assign Message Type to Idoc type Transaction WE82.
Create a distribution Model - Transaction BD64.
Reward points if it is Useful.
Thanks,
Manjunath MS

Steps in Inbound Processing in ALE IDOC

Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
Thanx

Hi
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
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
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

Need of Process code in ALE Inbound Processing?

Similar Messages

Maybe you are looking for