Executing RBDSTATE for ALE-Audit Processing

Hi Experts,
when I execute RBDSTATE into my Z_Function for BOMMAT Inbound Processing, it doesn't find any IDoc for the ALE-Audit Processing :
"No data relevant to audit were selected."
Any idea ?
Regards,
David

Hi Gordon,
I've decided to create another Distribution Model, only for ALEAUD (why ? I don't know...).
Now the IDoc ALEAUD is created into the Target System, but with Status is 02 "Could not find code page for receiving system".
Regards,
David

Similar Messages

Maintaining distribution model for ALE audit.

hi,
I have to create a bcakground job in the receiver system to periodically send back the audit data to the sender system. To do the same i need to maintain a distribution model for ALe audit. For doing so i don't have the modal view XIDEMO in BD64. How to implement. Also in SM59 while maintaing RFC destination it says U6D_700 no longer exists. Please suggest how to get it resolved.
Regards
Akash SInha
Edited by: Akash Sinha on Dec 16, 2009 9:59 AM

Hello,
You can create your own model view in BD64. In the model view add message type ALEAUD with sender as your system name and logical system of your reciever.
Also configure the Partner profile in WE20, with outbound parameter ALEAUD and IDoc Type ALEAUD01.
Schedule the program RBDSTATE with the required parameters.
BR/Yogesh

Performance improvement for ALE/IDOC processing

Dear experts,
Could you let me know any information to tune performance?
In our system (SAP R/3 Enterprise 6.20), material master data is distributed from one client to other clients in the same instance. It is because material master is maintained centrally, and is distributed to other clients for member companies.
During the night batch, distributing master data takes more than 2 hours. Although the distribution usually finishes without errors, we would like to explore ways to improve processing performance. Especially, program RBDMIDOC runs long time to create IDOC for MATMAS, even 0 master IDOC is set eventually.
OSS notes of the list for OS/DB/SAP parameters related to ALE/IDOC, tips in organizing batch jobs, etc, will be very appreciated.
Many Thanks,
Nori

I'd recommend to profile the program at least once to see where there's possible room for improvements. I.e. an ABAP runtime analysis and SQL trace would be good for a start. You can check out the links in thread Please Read before Posting in the Performance and Tuning Forum, which will give you some references if you need them. Once you have more details, you either know what you need to do or you can provide them and ask a more specific question (and thus you will receive much better answers).
As a general remark though I've seen often poor performance initially on the changer pointer selection, because there are too many entries in the table (due to system generating unnecessary change pointers, which should be disabled or/and lack of proper reorganization, i.e. deletion of old/processed change pointers via BD22). Sounds like this is most likely also the cause of your problem, because otherwise it's hard to explain long run times without generating any master IDocs. You can check the number of change pointers easily via view BDCPV or BDCP2 - it depends how you store your change pointers (most likely you find them via view BDCPV in a 6.20 system, unless somebody switched it to the newer BDCP2).
If you still have them in BDCPV (or the underlying tables to be more precise), check out [OSS note 305462 - MOD: Migration change pointer to table BDCP2|https://service.sap.com/sap/support/notes/305462], which will provide you a general hint how to do that (and thus also improve the performance). However, if you're currently not deleting any old change pointers, you should ensure that a regular job runs for transaction BD22 (program RBDCPCLR). You'll easily find other (possibly relevant) OSS notes by doing a search yourself...

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 audit in IDOC

In respect of ALE Audit in IDOC
1. All IDOC receivers send Acknowledgement.
2. All IDOC senders expect an Acknowledgement
3. Receiver communication channel is required for ALE Audit
4. Sender communication channel is required for ALE Audit
I believe 1 and 3 correct. Please confirm me.
thanks
kumar

Kumar,
I think 3 is correct , 1 & 2 also correct but based on condition, please see below.
 3 -sure
2 - Please refer the below doc ,Page 1
fyr :In general, acknowledgments have to be requested explicitly by the sender. However, this does not apply to IDocs. The following acknowledgments are sent back by default, unless the corresponding message type is maintained in an exception table.
1 - Please refer the below doc Page 1
fyr :IDocs only return acknowledgments if the receiver is configured for using ALE audit.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Please correct me if i 'm wrong!!!
Best regards,
raj.

Fault policies not getting executed for called BPEL process

Hi,
I am facing one issue in execution of fault policy for a called BPEL Process.
I have two BPEL Processes - BPELProcess1 and BPELProcess2.
We have fault-policies and fault-bindings file.
Case1 - BPELProcess2 is synchronous :-
BPELProcess2 throws a fault of selectionFailure.
Now this fault is defined in fault-policies and fault policy is bound to BPELProcess2 component in fault-bindings.xml file.
But this fault policy is NOT getting executed.
This selectionFailure fault from BPELProcess2 goes unhandled and in BPELProcess1, invoke activity gets this unhandled fault and raises a fault "remoteFault".
This remotefault is also defined in fault-bindings and bound to BPELProcess1 component. Here fault policy bound to BPELProcess1 is working fine.
So problem is that for called process, fault policies are not getting executed while for calling process, they are getting executed.
Case1 - BPELProcess2 is Asynchronous
BPELProcess2 is asynchronous. So same situation happening here. Fault policy for BPELProcess2 is not getting executed on throwing selectionFailure.
But now here, since BPELProcess2 is async in nature, BPELProcess1 is not getting response and it is always waiting for response which is wrong.
So how can we use fault policies in this case?
Please suggest.
Thanks & Regards,
Parshant

So that means - only fault originating from invoke activity in BPEL can be associated with a fault policy. No other fault can be associated. Even if I throw a selectionFault from throw activity, that will not be captured. Only fault from invoke activity can be associated with a fault policy.
Please confirm.
Thanks,
Edited by: 833944 on Feb 24, 2011 9:36 PM

Error when executing statement for table/stored proc

Hi All,
 I am getting this error when executing IDOC to JDBC (Stored Procedure) Scenario.
 In my stored procedure I have three insert statements to insert rows in to 3 tables.
 This stored procedure is working fine for two insert statements i.e,
 For this I have created data type for stored procedure with 10 elements and executed the scenario and was successfully running.
 when I added 3rd insert statement to stored procedure ie., when i added 5 more elements to the datatype (totally 15 elements) it starts giving the bellow error in Message Monitoring.
Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
 Note:- I have run the stored procedure with three insert statements in Sql Server, and also by calling an external program also, and was working fine.
 Note : Is there any structure needs to be follow when working with IDOC to Stored procedure.
I am struck up with the error, can any body resolve this issue.
Thanks in Advance,
Murthy

Hi narasimha,
 This seems to be any error due to incorrect query formation.In your receiver jdbc channel set the parameter logSQLstatement = true.you can find this parameter in the advanced mode. Using this parameter you will be able to see the sql query which is generated at runtime in the audit log in RWB.
Regards,
Pragati

Setup of ALE Audit in SAP Receiver System

Hello,
for a scenario JDBC -> XI -> IDoc, I have to setup ALE Audit in the receiver SAP sytem.
I have followed the steps in the How-To-Guide (Handle acknowledgements for IDocs):
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
However I just want to have acknowledgements sent back to SAP XI for a specific type of IDoc (source coming from the database) and not all received IDocs as there are different sender systems sending IDocs (some of them via XI some of them directly).
Is there a way to configure ALE Audit in a way ALEAUDITs are sent just for specific sender systems / IDoc types. I want to avoid that the SAP XI system receives ALEAUDIT for all inbound IDocs.

Hey,
This document describe how the handle audit the the sender and the receiver systems are SAP system, when one of the sides (sender/receiver) is not SAP system,
than the configuration become much more complex.
As of XI SP18, there are ways to control ALEAUD,
for more information, read:
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393634373435%7d
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

Logical systems for ALE

HI all,
I'm configuring for an IDoc to be generated and downloaded to a file via a file port.
This IDoc is of message type PAYEXT.
The file is to be sent ot the bank via the meansa of third party software.
Do I have to create logical systems for these? Or only the outbound logical system?
Do I also need to set up the distribution model , and if so, how far do i need to set it up?
Points wil be awarded. Thanks!

Hi
Use BD64 Tcode to setup distribution Model
Define the 2 logical systems.
see the flow:
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
Reward points if useful
Regards
Anji

Sequential Instantiation of BPEL instances for a BPEL process

Hi,
We are using Oracle SOA 10.1.3.4 & AIA2.5. We have a situation where the instances of a particular bpel process have to be executed in sequence. Also, the new instance should NOT be instantiated unless the previous instance is completed.
For example.. Lets say a SyncBPELReqABCS is invoking SyncBPELProvABCS via ESB. SyncBPELReqABCS is looping and spawning multiple instances of SyncBPELProvABCS in a certain sequential order in Asynchronous Fire-and-Forget model. Lets say bpel-instance#1, bpel-instance#2 and bpel-instance#3 are instances of SyncBPELProvABCS process. Even though SyncBPELReqABCS invokes (spawns) SyncBPELProvABCS in a fire and forget model, the bpel-instance#2 should not begin unless bpel-instance#1 is completed and bpel-instance#3 shuld not begin unless bpel-instance#2 is completed. This is because there is a dependancy between instacnes of SyncBPELProvABCS process.
Can this be achieved in Oracle SOA?? Can we restrict the instacnes of SyncBPELProvABCS to be created in this manner?
This is similar to "incompatability" of concurrent programs in ORACLE EBusiness Suite where one concurrent program waits till another concurrent program completes.
Please let me know if I am not clear. Appreciate an immediate help!
Thanks,

Hello,
Now that I look back at this tread, I can see that the questions I was asking and those of the original poster were somewhat different.
But they both fall under the heading of "Sequential Instantiation of BPEL instances for a BPEL process", and so I thought I would post some findings we've come across regarding that topic here.
There were a couple steps that helped us achieve the behavior we were looking for, and the were...
1) Change the BPEL oneWayDeliveryPolicy from "async.persist" to "sync"
This can be done in a couple locations. The first is within the EM application that comes bundled with SOA 11g, and the place to go is:EM > [farm name] > SOA > soa-infra (right click) > SOA Administration > BPEL Properties > More BPEL Configuration Properties > OneWayDeliveryPolicyOnce that value has been changed to "sync" (without the quotes), you'll need to stop and start the managed servers that run your SOA instance(s).
As you might expect, making a change at the "server level" like this impacts the default behavior of all composites deployed within your SOA instance. The second place to make this change - within the deployment descriptors for your BPEL process - impacts only the BPEL process that is being modified. To make the change at this level, you would edit your project's composite.xml file and, for each BPEL component, specify: <component name="BPELProcess1" version="2.0">
 <implementation.bpel src="BPELProcess1.bpel"/>
 <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
 <property name="bpel.config.transaction">required</property>
</component>What does this change do? Well, I don't claim to have a complete understanding, but in theory it prevents a thread handoff from taking place between the service that is initiates your BPEL process (like a receive) and the actual BPEL engine thread that processes the request.
In our case, where calls between (and within) composites were all of the synchronous "fire and forget" variety, this change also caused the entire processing of a message (across three different composites) to happen in a single thread (each message handoff was one-way, and with the oneWayDeliveryPolicy set to "sync", each was handled in a synchronous manner).
This also seemed to have the effect of serializing our message processing. For example, in a test case where a BPEL process reads from a JMS queue and 250 messages are enqueued, with the oneWayDeliveryPolicy set to "async.persist", I'd typically go in to EM and, on each refresh, find 5-8 instances of the composite that processes those messages to be in a "Running" state. Once the change to "sync" was made, I'd only see at most only 2 (where one had actually already finished; the audit system just hadn't yet caught up to that fact yet).
This also means that, with a "sync" delivery policy, messages (at least in our environment) are processed more slowly, but that was ok with us as we were more concerned with the behavior than the speed.
For details on this and other BPEL deployment descriptor properties, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/bp_app_deploydesc.htm
Also, it's important to note that making the above change will alter the boundaries of your transactions as well as how faults are propagated. For more details, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/soa_transactions.htm
2) Front BPEL process with a Mediator object and enable message resequencing
While we're using the above change as a standard practice in our environment, this second change has only been nominally tested - but it could be of interest and so I'll mention it here.
Once you've updated your composite to include a mediator object in front of your BPEL process (if there isn't one there already), edit the .mplan for your mediator and change the "Resequence Level" from the default value of "operations" to "component". Then change the "Resequence Mode" from "off" to "FIFO" and specify an X-Path expression by which the mediator will be able to group your messages. This will help ensure that the messages are being processed in the order you expect.
More information about resequencing within the mediator component can be found:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/med_resequencer.htm
Hopefully the above information is useful - if not for the original poster, then for someone who comes along later with similar questions.
- Nathan

ALE Audit

Hi All,
Please give me ur inputs on this scenario:
Scenario: FileXI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
Possible Solution 1: Along with the IDocs a proxy is also sent to the SAP from XI. Proxy has a wait time and collects following information:
No: of IDocs posted successfully,
No of IDocs Failed and there reason.
And then an email has to be sent using Alert Message to the process head with the above information.
Possible Solution 2: ALE AUDIT is used on the receiver SAP system and the error messages are sent to XI and the messages are collected in another interface in XI and subsequent Alert Management is used to shoot email.
Which solution is better and why?
Regards,
XIer

Hey
>>Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
For this you need to use BPM coz File can't handle sync calls.
As far as i know,in both the cases you need to use BPM.
Note:ALEAUDIT is mainly used in a IDOC to IDOC scenario or IDOC to File scenario
Thanx
Ahmad

ALE Audit - ALE logical system

Dear all,
we encounter an issue with an integration workflow that sends an ALE audit back to the R/3 system (Scenario:
R/3 -IDOC-> |XI-BPE| -HTTP->Partner)
Everything works fine except the ALE audit from the process to the R/3 System.
In the receiver agreement we use a header mapping to map the Sender.
Is there any difference between usual IDOC posting (for which our config works of course) and ALE Audit IDOCs?
Thanks in advance,
Helge

Hi Helge,
if you're using BPM in the XI
this is what you could to:
create a new processing code for inbound aleaudits
and change a little the standard function module
for inbound ale audits (the only change
would be a table in which you'd map
BPM names to just on partner profile)
this way if you'd be using a new BPM
you will only have to add one record to the table
and the processing will always be done correctly
with just one partner profile
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

ALE Audit System

Does ALE audit system work between a non-sap sending system and SAP as receiving system. If yes, then how is the "audit table" and "audit analysis program" step taken care of?

Hi Helge,
if you're using BPM in the XI
this is what you could to:
create a new processing code for inbound aleaudits
and change a little the standard function module
for inbound ale audits (the only change
would be a table in which you'd map
BPM names to just on partner profile)
this way if you'd be using a new BPM
you will only have to add one record to the table
and the processing will always be done correctly
with just one partner profile
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Learning Materials for ALE and Idocs

Hi Experts,
Kindly send me the documents/Links for ALE and IDocs.
Regards,
Ram.

Hi
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
check these...
http://www.onestopsap.com/interview-Question/ale/
http://sap.ittoolbox.com/groups/career/sap-career/aleidoc-interview-questions-688290
http://www.erpgenie.com/faq/ale.htm
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:
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
Reward points if useful
Regards
Anji

Are these steps correct for ALE configuaration ?

1.An ALE Configuration we have to do five steps
a)Define logical System (SALEsending and receiving system logical systemdefine logical system)
b)Assign client to the logical system( SALEsending and receiving systemlogical system Assign client to the logical system)
c)We have to define port at (WE21)
d)GENERATING PARTNER PROFILES(WE20)
e)Define target system for RFC calls (sm59)
f)Creating Distribution model (BD64)
g)WE42 for creating process code.
h)Send Data ( bd10)
i)Get Data(bd11)
j)BD51
k)WE57
We have to repeat the FIRST 6 steps for each of the sender and receiver and those are compulsory. I am not yet clear about the last 5 steps.
E.g. our sender is 200 and receiver is 400
So for each of them we have to do the 5 steps twice.

folow the link
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
which will givw u the steps for ale configuration
steps are
. ALE->Sending and Receiving Systems->Logical Systems->Define Logical System. a. Here you add the name of the logical system for the distributed system. To make them easy to find I like to name them based on instance/client so in the case of the system listed above I would call it DM7200. This naming convention makes it easy to follow in various systems.
2. ALE->Sending and Receiving Systems->Logical Systems->Assign Client to Logical System.
a. In this step you assign your logical system to a particular client. WARNING: DO NOT CHANGE THIS IF IT IS ALREADY CONFIGURED!!! That holds especially true on an FI system as it cannot be changed once it is set. Make sure to discuss this with the Basis team before entering the data.
3. ALE->Sending and Receiving Systems->Systems in Network->Synchronous Processing->Determine Target System for RFC Calls
a. This area allows you to tell SAP where to make RFC calls based on the logical system. That means that when I want to look up Vendor information in cases like infotype 194 and 195 where a function module is called that I can tell the system where to go to find that information. To configure this you should make sure that the system where the financial information will be kept is listed.
4. ALE->Modelling and Implementing Business Processes->Maintain Distribution Model and Distribute Views
a. In this step we will define where the FI data comes from and what data we expect to receive. We will also define the system that will be receiving the payroll posting and what data we will be sending that system.
b. SAP Recommends the following list of messages to be received from the financial system:
i. COACTV-IDoc for cost center/activity type
ii. COAMAS-Master activity type
iii. COELEM-Cost Element Master Data
iv. COGRP1-Cost Center Groups
v. COGRP2-Cost Element Groups
vi. COGRP5-Activity Type Groups
vii. COSMAS-Master Cost Centers
viii. CRECOR-Core Vendor master data distribution
ix. CREMAS-Vendor master data distribution
x. GLCORE-Master data G/L accounts (CORE IDoc)
xi. GLMAST-Master data G/L accounts (master IDoc)
xii. PRCMAS-Profit center master record
xiii. RCLROL-Reconciliation ledger rollup
c. To add these messages you can follow the steps listed here:
i. Go into change mode by clicking on the pencil/glasses button or Distribution model->Switch Processing Modes via the menu
ii. Click on the Create Model View Button
Fill in the data for your model. Below is my example.
iii. Now it is as simple as adding message types. Click on the Add message type button and enter the required data. The sender is the FI system and the receiver is the Payroll system. Tip: Once you add the first message type if you select it before adding the next message you will only need to fill out the message portion and not the sender and receiver
iv. Now we need to build the partner profiles so that the systems know where the distribution model needs to get or put things. To do this go to Environment->Generate Partner Profiles.
Enter the partner system you want to use and press execute or F8.
This screen shows the successful creation of the partner profiles. If you want to see them can go to transaction WE20.
v. Now we must send the model to the other system. To do this use menu path Edit->Model View->Distribute
Now I should be able to see this model in my FI system, in this case, DM3. I can take a look at this via transaction BD64 in the other system
You'll notice that the coloring on the messages and models is in gray. This indicates that the model is maintained in another system.
d. We also have to configure the model for posting to the other system. In this case we will be using BAPI's and not message types. SAP recommends the following BAPI's:
i. AcctngServices.DocumentDisplay, Accounting: Display Method for Follow-On Document Display
ii. AcctngEmplyeeExpnses.Post, Accounting: Post G/L Acct Assignment for HR Posting
iii. AcctngEmplyeeRcvbles.Post, Accounting: Post Cust. Acct Assignment for HR Posting
iv. AcctngEmplyeePaybles.Post, Accounting: Post Vendor Acct Assignement for HR Posting
e. For the most part the steps are the same as above but it is slightly different because you use the Add BAPI button instead of the Add Message Type. BAPI's are case sensitive so you'll need to be exact.
<REMOVED BY MODERATOR>
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 2:27 PM

Executing RBDSTATE for ALE-Audit Processing

Similar Messages

Maybe you are looking for