Idoc and status (68)

Hello all,
My customer gets sometimes inbound messages with status 51 that can't be processed automatically (with BD87 or other). For a few kinds of messages, my customer corrects the problem manually in the target business document => The relevant idoc won't have to be processed in the future.
We would like to change the status of this idoc in order to identify it as an idoc that :
- has never been processed => status <> 53
- are never should never be be processed => status <> 51
Status 68 seems to be defined for such a request.
Is it the case ?
How can I turn my Idoc status from 51 to 68 with a business transaction (without using RC1_IDOC_SET_STATUS). (I want an User action)
Thanks a lot
J.C.

Hi JC,
Yes, with status 68 the Idoc cannot be send to application again.
If you need the user change the status manually, maybe you could generate a new transaction for this pourpose associated to a abap program that performs first a selection of Idocs with status 51, and later performs an user action that simply call IDOC_STATUS_WRITE_TO_DATABASE function module to change them to 68 .
Regards,
Roger

Similar Messages

Request iDoc and status iDoc correlation

Hello,
I have a strange problem.
In my XI 3.0, I have an iDoc2iDoc interface which used to work fine, until I installed patch level 14.
Now, when the acknowledgement (ALEAUD) comes back into my R/3 system, the iDoc system does not recognize it as a response for a specific request iDoc I've sent, but as an ordinary inbound iDoc.
After a short investigation, I found out that the iDoc number is not correlated, it seems like a problem in the iDoc adapter in the XI, that does not translate the iDoc number of the target system back into the iDoc number of the original system.
Has anyone met with this kind of problem ? any solutions ?
Thank you,
Elad.

Hi Anand.
All of the partner profile and iDocs configuration are complete and correct.
I'll try to be a bit more specific:
Local R/3 sends iDoc MATMAS through XI 3.0 and receives ALEAUD iDoc as an applicational acknowledgement.
For the R/3 to be able to correlate between the inbound ALEAUD and the outbound MATMAS the iDoc system uses a field containing the iDoc number.
The problem is that ALEAUD has the number generated by the remote system and the MATMAS has the number of my local system, the XI is suposed to translate the remote iDoc number back to the local iDoc number.
I hope it's clearer now, and that someone can help.
Thank you,
Elad.

IDOC number and status

Hi All,
i am using Function Module IDOC_INBOUND_ASYNCHRONOUS to post inventory records.
its posting the data sucsessfully but it does not return IDOC number and status.
i can see the status and number in WE02 but please tell me how can i get that in my program.
Thakns and regards
Pankaj

Hi friend,
       U can get the status and number of IDOC in WE05 and WE07.
       Once u get the number of IDOC got to table EDIDC(Control Rec table),
       EDID4(Data Rec table) and EDIDS(status Rec table) to get the information
       related to status and content of idoc.
       Directly, u can specify it in ur program as Tables:EDIDC,EDID4,EDIDS
       and get the info according to ur idoc number.
Thanks N Regards,
        Manian.

IDOC confirmation and status change ???

SAP friends,
I have a question about IDOCS. We are implementing. In AP after processing payments, our bank will send us a text file which will have idocs number. and status number ( accept and reject).
We have to update that status number for our idoc in the system and if the number that was rejected we have to send an email to everyone. How can we change the status of idoc using the file the bank sends us.
Thanks,
Kavita Reddy

Hi,
Please explain the process detaily. question is not clear.
IDOCs are the intermediate documents, which carry information from SAP to Legacy or vise versa.
IDOCs will be distingwished by message type. These will generate by Program. In program please check about the status.
Thanks
Kalyan

IDoc Control Record and Status Record Code, where is it!!!

Hi,
Where can i see the code for generation of control record and status record of IDoc.
   Thanks in advance for your answers

hi ,
1.first create an segment with the fields u want tcode we31 relase it .
2. create an idoc and assign segment to it tcode we30.
3.crate a message type tcode we81
4.assign that message to idoc tcode we 82.
do the ale configarations .
now u can write the code in our sender system
*1.     Create parameters/select-options for input data. i.e., message type, logical system.
parameters : p_mestyp like edmsg-msgtyp default 'ZKKUMSG',
             p_logsys like tbdlst-logsys obligatory.
*2.     Create Data objects for control record, data record and database table.
data : c_segment like edidd-segnam value 'ZKKUSEG',        "Data record (IDoc)-Segment type
       c_idoctp like edidc-idoctp value 'ZKKUIDOC'.            "Control record (IDoc)-Basic type
data : begin of i_tab occurs 0,
          ZKSNO   like ZKSTD-ZKSNO,
          ZKSNAME like ZKSTD-ZKSNAME,
       end of i_tab.
data : w_itab like i_tab.
data : s_segment like ZKKUSEG.
data : i_edidd like edidd occurs 0 with header line.
data : i_control_record like edidc.
data : i_comm_idoc like edidc occurs 0 with header line.
*3.     Select the data from responding tables into internal table for a defined condition.
here you have take ur internal table
*select single zsno zsname from zkiran into corresponding fields of itab where zsno = p_sno.
*4.     create control record into internal table.
i_control_record-mestyp = p_mestyp.         "Message Type
i_control_record-idoctp = c_idoctp.         "Basic type
i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
*5.     create data record into internal table.
*i_edidd-segnam =   c_segment.
loop at i_tab into w_itab.
s_segment-zksno    = w_itab-ZKSNO.                     "Application Data
s_segment-zksname = w_itab-ZKSNAME.
i_edidd-sdata     = s_segment.
i_edidd-segnam    = c_segment.
clear w_itab.
append i_edidd.
endloop.
*6.     Process ALE Service Layer using the function module MASTER_IDOC_DISTRIBUTE. It returns the corresponding IDoc No.s.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control            = i_control_record
tables
    communication_idoc_control     = i_comm_idoc
    master_idoc_data               = i_edidd
exceptions
    error_in_idoc_control          = 1
    error_writing_idoc_status      = 2
    error_in_idoc_data             = 3
    sending_logical_system_unknown = 4
    others                         = 5.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*7.     Display Communication IDocs.
loop at i_comm_idoc.
write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
endloop.
*8.     Commit Work.
commit work.
i hope this sample code help u .
thanks

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.

IP Job in BW finished, but how can I check the IDoc receive status in BW ?

Hi,experts
After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
and how can I do now ? or how can I check the IDoc receive status in BW side?

Hi,
I too had the same problem, i executed the following to solve the proble, may be this will help you:
1) Go to T-code SM58 and select TRFC and press F6,
2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
Thanks,

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

IDOC in status 03

Hello,
I am trying to send IDOC to a target system but the IDOC is struck in status 03.'IDoc sent to SAP system or external program'.
How to push it further?
Thanks,
Rakesh.

Hello Rakesh More,
You can use the transaction BD87 to re-process those IDOC's.
Enter your IDOC Number and then execute. You will find the Execute-"Process" button in the application tool bar at the top of the next screen. Select your Outbound IDOC and Process.
Let me know if you have any questions.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Jul 28, 2011 1:51 AM

SAP IDOC shows status 03, but no file is written

We have SAP configured to generate delivery IDOCs when the SAP Delivery document is posted/saved. The IDOC is initially created with status 30. There is batch job RSEOUT00 every 30 mins that collects the IDOCs in status 30 and converts to status 03. When we review the IDOC processing screen, even though they are in status 03 and successfully written outside of SAP to a folder, there is no file in the folder. We are missing IDOCs. There is no real time external system integration. We are simply trying to write IDOC files to a folder.
Can you some please share your insights on how to resolve this issue?
Thanks in advance
Satish

RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model in sender system.
Partner profiles maintained in both the systems, soure Outbound properties
Target Inbound properties.
if you have two clients in system it will be easily you can check.

InfoPackage loading giving IDOC Error: Status 51

Hello Experts,
1) I created a DB view (ZZVIEW05) in the SD area on R3
   and it extracts data OK in RSA3.
2) I replicated the DataSource in BW, Created InfoSOurce
   activated and created an InfoPackage.
3) Scheduling the InfoPackage is failing with an Error:
      Transfer(IDocs and TRFC):Errors Occurred
         Request IDOc: APplication document not posted
For the Error, I right Clicked and looked at the IDoc status in the Source System (R3 where we are getting the data from).
The Idoc with Error has a status of 51 and has the following message:
Any suggestions ?
Thanks, BB
Function module not allowed: ABI_IDOC_DISPATCH
Message no. B1252
Diagnosis
     The function module ABI_IDOC_DISPATCH and the
     application object type which were determined
     are not valid for this IDoc.
Procedure
     1. Please check that the process code in the
         inbound partner profile is correct.
     2. If this is the case, you should check the ALE
         inbound methods ALE inbound methods for the
         process code and see whether the specified
         function module and application object type are
         correct.
     3. If this is also the case, then the function
         module and the application object type are not
         permitted for the logical message type, message
         variant, message function and basis type that
         are contained in the IDoc control record. You
         should check whether the correct values have
         been assigned to these fields in the control
         record. If they do have the correct values,
         then the assignment to the function module and
         the application object type needs to be
         maintained.

Hi Dinesh & Sat,
I tried following:
Using WE19.....I was able to manually pump the IDOC that got stuck in ALE inbox on R3 side...then R3 was able service the request and send data to BW.
It seems the correct function module (R3 side) to process an incoming BW data request is RSAP_IDOC_DISPATCHER.
Instead ABI_IDOC_DISPATCHER is being invoked, by default, which is giving the problem (seems to be some kind of authorization issue!).
In WE20, I changed the partner profile to process using RSAP_IDOC_DISPATCHER. BUT somehow it is not being invoked.
I suppose some other setup (table entry) is conflicting with my setup ....
Any clues ?
Thanks, BB

Idoc- can we sent already sended idoc if status is showing error message

hi
Idoc- can we sent already sended idoc if status is showing error message
without making any changes.
Thanks in advance.

Hi raja,
IN BD87.
give the idoc number,its status,messagetype and partner system and resend it.
Regards,
nagaraj

Query on IDOC Ack (STATUS) config in XI for a specific partner comm.

Hi Experts,
Is it possible to configure the IDOC Ack (STATUS.SYSTAT01 message) in XI for a specific partner communication? We want to configure our system like ALEAUD but the message type should be STATUS.SYSTAT01 and the acknowledgment should be send to sender system for a specific partner only if XI receives any IDOC like (Orders) from that specific partner. For other partners (same sender system) we donu2019t want this acknowledgment settings and configuration. If possible please provide the configuration filters steps etc. Thanks for your valuable inputs in advance.
Thanks,
Satish
Edited by: Satish Jaiswal on Jan 8, 2009 2:55 AM

Hi Husain,
I have the document you have mentioned. Please note my requirement is to filter the Ack while creating and sending to R/3 based on Partner and Message type. The document provides info only on Message type filter but not parner specific for same sender system!!! Any help appreciated. Also note: BPM and Alert is out of scope.
Looking for some ALE configuration tricks to achieve this.
Thanks
satish
Edited by: Satish Jaiswal on Jan 9, 2009 2:40 AM

Basic of IDOC and ALE

Hi All,
I am beginner of ALE IDOC.
Please tell me in details whats is Control Records, Data Records and Status Records in details.
Thnks in Advance,
awards will be given.
Ulhas

Hi,
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. 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 u201CThe table is cross-client (see Help for further info)u201D. 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)
u2022 Create a Customer Distribution Model (CDM);
u2022 Add appropriate message types and filters to the CDM;
u2022 Generate outbound partner profiles;
u2022 Distribute the CDM to the receiving systems; and
u2022 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 u2013 Creating IDoc Type from Change Pointers
RSEOUT00 u2013 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.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva Kumar

What are IDOC and ALE?

We are getting a new system that will be interfacing to SAP via IDOC and or ALE
I am required to quickly reply back as far as what will be required from a BASIS side if they will interface using IDOCS and ALEs
Thank YOU and kind Regards!
M.

Hi Maria,
Application Link Enabling (ALE) is a mechanism or u can say that it's a tool for the exchange of business data between loosely-coupled R/3 applications built by customers of SAP, the enterprise resource management program. ALE provides SAP customers with a program distribution model and technology that enables them to interconnect programs across various platforms and systems.That means that ALE can integrate business processes between R/3 Systems and non-R/3 systems as well as between R/3 Systems.
There are three layers in the ALE system:
a)     application services,
b)     distribution services, and
c)     communication services.
The vehicle for data transfer is called an IDoc (intermediate document), which is a container for the application data to be transmitted.
After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system. If the data is distributed from a master system, the same transaction performed by the sender will be performed by the receiving system, using the information contained in the IDoc.
Changes made to fields in master data tables can be set to trigger distribution of the changes to slave systems, so that multiple database servers can update the same information simultaneously. IDocs carry information directly between SAP systems. In order to communicate with a non-SAP system, an IDoc is first transmitted to an intermediary system that translates the data to a format that will be understood by the receiver. Return data also passes through the translating system, where it is again encapsulated into an IDoc.
Now comes to ur 2nd query basis guys duties over IDOCS & ALE
a)Creating the RFC
b)monitoring different layers over ALE
c)Archiving IDOCS (when required)
d)use the Idoc display tool(we02)
e)use the Idoc Search tool (we09)
f)use the Status Monitor Tool(bd87)
g)Troubleshooting the Inbound Idocsu2026.
Regards,

Idoc and status (68)

Similar Messages

Maybe you are looking for