Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. 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.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

Similar Messages

  • Error while sending Material Master IDOC to Auto ID 2.1

    Hello All,
    I am using Auto ID 2.1 with SP1 on NW04.
    Integration server is XI 3.0 with corresponding XI Content for Auto ID.
    The backend is ERP2004.
    I am using the config guide for Auto ID 2.1.
    After completing the configuration, I tried sending the Material Master IDOC to Auto ID.
    IDOC gets created successfully. XI says the message transfer is successfully.
    In the log of Auto ID. I am getting the following error while importing the Material Master product:
    Product ID AUTOIDAII_MAT has an invalid format
    Internal error in /AIN/DM_PROD_COMMIT
    Message no. COM_PRODUCT897
    The description says that it may be a program error.
    Or the program expects some variable to be filled which has not occured.
    Any idea what could be the error. Or where should I try looking for to get more detail info.
    Do some one knows what should be the patch levels for the different components in all three servers for Auto ID 2.1 SP1.
    Thanks for any kind of input.
    Regards,
    Arundeep Singh

    HI Arundeep,
    use the following
    1) XI 3.0 SP level 12
    2) AII 2.1 SP2
    3) check in rfid outbound configuration guide for any customising for product to be done in AII
    regards,
    ashit singh

  • Error while sending Material Master IDOC to Auto ID

    Hello All,
    I am using Auto ID 4.0 on NW04s.
    The backend is ERP2005.
    I am trying scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0)
    After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID.
    I get a message that IDOC is just being created. I could not find it in the transaction WE02.
    Also, they are not appearing in the AII system.
    Thanks for any kind of input.
    Regards,
    Message was edited by:
            Rahul Gavande

    Hi Rahul,
    I have not worked on these version of products. And I don't know what changes have been done in the new versions.
    But still, can you let me know, what is the exact configuration that you have done and also
    which partner are you trying to send the IDOC. And if you are trying to send the IDOC then I will suggest to debug the transaction and see till what level it proceeds.
    Best of luck,
    Arundeep

  • Do we need a sender channel for IDOC to file scenario.

    Hi,
    Do we need a sender channel in IDOC to FILE scenario.
    Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
    What is the reason for this?
    Regards,
    Younus

    Younus,
    to add more...
    From <b>WAS(Web Application Server) 6.20</b> and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
    And it has got ABAP and JAVA engine in it.
    It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.
    <b>
    The SAP Web AS 6.10 did not have a Java engine.</b>
    and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
    and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
    Hope i cleared ur point...
    Cheers,
    Raghavesh
    Message was edited by:
            Raghavesh Reddy

  • Sending Acknowledgements for IDOCs

    I have reviewed the document "How To... Handle Acknowledgements for IDOC" and "Configuration Tips for a Business Service/Integration Process to Send Back ALE Audit IDOC".  These don't seem to work for the situation I have.
    We have two R3 systems sending IDOCs to XI, one located in the US and one in Germany.  The above documentation (from what I can tell) expects you to only have one R3 system.  For example, when setting up the Adapter-Specific Identifiers, there is only one spot to enter in the Logical System or R3 System ID.
    Is there a way to set up IDOC Acknowledgements if you have more than one R3 system that can be sending IDOCs?

    Hi Larry,
    for each R/3 create one business system service. Depending of the control data in your idoc (you can examine the sender R/3 system in the IDOc header data) create different receiving systems.
    Regards Mario

  • Multiple customers in Sender Party for IDOC type KU

    Hi All,
    My scenario is IDOC to HTTP with sender IDOC Type KU.
    We are using PO 7.4 and IDOC_AAE.
    I have done the following settings.
    Created a Sender Party and assigned a customer under party identifiers. (Also I can't add multiple values with same Agency and scheme it throws eror in PI)
    For a single customer the end to end scenario is working fine.
    But if I try to send the IDOC with other customer Number it fails as the entry is not maintained for that customer in Sender Party identifiers.
    Also I can't afford to create a different party for each customer as there are hundreds of customers in the ECC Application system.
    I also tried with value mapping but it won't worked.
    Please suggest on this.
    Regards,
    Nitin...

    Dear Nitin,
    did you solve this problem? A am faced to it right now... ...
    Regards,
    Markus

  • Monitoring and sending alerts for IDocs

    Hi ,
    I have Idoc scenarios both outbound and inbound.
    My requirement is that whenever an Idoc goes into error state an alert should be sent to a specified person automatically.
    Please also let me know ways to reprocess Inbound and outbound Idocs.
    Thanks

    Hi,
    Your question is mainly for ECC, than for PI...
    but you can acheive it, for instance, by creating an abap program which checks the IDoc status, and send an email to a list of persons you determined for instance in a Ztable for each idoc (message type + idoc type + idoc extension). You can scheduled this program by creating a SAP job (tcode SM36).
    Another way could be to add an abap enhancement in each idoc process (inbound / outbound) to check the status of this idoc and send an email. But...
    Personally, I prefer the 1st solution, as the program is scheduled, you can group several idoc errors and send only one email (!). Keep in mind this case: among 1000 inbound idocs, 750 are in error, because of a bad or a missing data in the source system... What 's the result with the 2nd solution?... it's a spam of 750 emails to the emailbox of your employees (!!!. Not sure they will appreciate...
    To retreat Idoc, you can use tcode BD87. Do not give this tcode to all employees, but only to some key users, to avoid that an employee retreat several idocs which are not in its scope (because he/she did not a godd selection in the selection screen) and which should be not be retreat now (exm due to a fiscel year).
    regards
    Mickael

  • Unable to convert sender service for IDoc to SOAP Scenario

    Hi,
    I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
    SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
    When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
    "Unable to convert the sender service receiver_service to an ALE logical system"
    I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
    Next is a Cache refresh i tried a full one but no impact
    Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
    I have no idea
    Thanks for help, be sure that helpful answers will be awarded
    regards
    Matthias
    P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

    Hi Matthias
    >>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
    Party information is generally not required to be maintained in SLD
    >>Adapter Specific Identifies
    What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
    Regards
    Suraj

  • Send Changes for IDOC ORDRSP

    Hi Gurus
      Can anyone help me in sending the changes for the IDOC for transactional data.
    For Sales Order IDOC -- ORDRSP.
    When newly sales order is created, all the sales order information should be sent. --This is not a problem.
    When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP. 
    but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
    Is there anything that i am missing???
    Any help is really appreciated.
    Thanks
    Saritha

    Hi Linda,
    I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
    Instead i  can help u out if u r facing any issue.
    In our case: wen ever sales order is created /changed an idoc shud be genrated.
    This can be done thru Message control.
    Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
    do let me know where ever u r not clear.
    regards,
    Naveen

  • Sending Material for Final packaging.

    Dear Experts,
    Greetings of the day!
    Scenario:
    At times we have some finished products, which we need to send to a vendor for making promotion packs- In simple terms, suppose we have finished material - A, B and C, and we want to get all together shrink wrapped. (3 in 1).
    No. of Promotional Packs: 100, each containing (materials A,B &C in the ratio of 1:1:1)
    Material
    Quantity
    Batch
    A
    100
    100001
    B
    100
    100002
    C
    100
    100003
    Batch management is active.
    Process AS-IS:
    1.Create Purchase request (MB51N); with item category -L
    2.Create Purchase order (ME21N);
    3.Issue material against purchase order by 541 Movement;
    4.Create inbound delivery against Purchase order;
    5.Receive material By MIGO, with movement type 107;
    6.Release GR Blocked Stock by MIGO with movement type 109;
    7.Create TO against material document generated from 109 Movement.
    8.Confirmation of TO for final put-away to respective storage bins.
    Problems:
    1. When we receive partial quantities from the vendor, we can make GRN (107) against the inbound delivery for the partial quantity by changing the quantity in the inbound delivery number; but we are not able to release GRN (109) as it is showing an error , which asks for complete receipt needs to be done.
    2. I have reversed 107, by doing 108, and then if I am trying to make GRN against the same inbound delivery by movement type 107, the system reflects an error  as " Delivery note data already Exits".
    Scenerio II: Promotion Packs : 100, each containing materials (A,A & A in the ratios of 1:1:1)-Pack of Three (Same Material)
    Material
    Quantity
    Batch
    A
    100
    100004
    A
    100
    100005
    A
    100
    100006
    Purchase request looks like : (B'coz at the time of making purchase request we don't know which batch will be picked by the system)
    Material
    Quantity
    A
    300
    Similarly Purchase order will look same, as it has been created from the PR, and inbound delivery number also same (Only one line item).
    Problems:
    1. At the time of GRN (107), how can we split the material into different batches, since we want to receive with the same batch.
    Hope the scenario's are clear!
    Regards,
    Malik Abrar Altaf.

    Hi,
       So many issues are identified when using two step procedure with inbound delivery. The notes 1373027 - Problems w/ 2-step goods receipts using inbound deliveries and  1225077 - GR with inbound deliveries in (valuated) GR blocked stock  explains the same.
       If you have different batch numbers for GR, then you have to split to different line items with respect to batch.
    Regards,
    AKPT

  • Sending material for Packaging to Vendor & receiving while GR

    Dear All,
    Kindly help in resolving below issue.
    I have to procure material from vendor in the container sent by me to him. However I dont want to use item Category L / Subcontracting for the same. We wll not maintain BOM as well. Please tell is there any other way round for the same. The stock of the container in my plant is non valuated.
    Regards,

    RTP is a material master of material type LEER or LEIH.
    more can be read here:
    http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b921143ad11d189410000e829fbbd/frameset.htm
    Regards
    MK
    Edited by: Manmeet Mohan Karandikar on Mar 9, 2010 9:49 AM

  • Sending material for subcontract vendor two times

    Hi,
      I have a requirement, we create the subcontract PO as per BOM 10 different types of raw materials are required now initilaly at the time of MB1B only 8 items are ther in the system so we do the trasnfer posting for 8 items then subcontract challan create ref. to MB1B document number now later we recd the remaining two items in our system now how to issue that two material aganist the challan.
    regards,
    zafar

    Hi All,
       Thanks for your reply, I per above reply I try one in development server,
    Subcontract Po created for one FG material Qty : 1, the Finish good BOM contain 2 raw materials
    Finish Material : FG1
    BOM Comp.     : RM1
    BOM Comp.     : RM2,
    when I have done the transfer posting posting first time I have transfer only RM1 to vendor with 541 movement type, then ref. to that document number I have created Subcontract challan with J1IF01 so as per Transfer posting doc. in challan only RM1 come, then without transfering the the RM2  when I am making GR for FG material system is posting both RM1 and RM2 to consumption even for this challan i have not transfer the RM2 to vendor,  so withotu saving the GR then I have trabsfer the RM2 to vendor against the same PO with MB1B movt. 541  now both the RM1 and RM2 are transfer to vendor but with different document now when I made the GR both the RM1 and RM2 are posted to conusmption but when I ma doing reconcilliation for the challan and GR system is giVING ERROR MESSAGE
    Material 229 is not assigned fully, short by 1.000 NO
    Message no. 8I574
    as this material I have transfer in secodn document and this is not there in the challlan so is there any other method so this.
    regards,
    zafar

  • Material for ale,idoc programming

    Hi folks,
    i need urgently the material for IDOC programming.i am mentioning the process below.
      1)i have created one program. i need to send some fields to a folder through IDOCS.
      when i will press a push button on my program, this idoc program should execute so that some of the fields will transfer through IDOCS.
    Thanks

    hi,
    Intermediate Documents (IDOCs)
    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.
    The two available process for IDOCs are 1) Outbound Process 2) Inbound Process.
    There are basically two types of IDOCs.:
    1.  Basic IDOC type defines the structure and format of the business document that is to be     
         exchanged between two systems.
    2. Extension Idoc: Extending the functionality by adding more segments to existing Basic IDOCs.
    -&#61664;To Create Idoc we need to follow these steps:
    1. Create Segment      ( WE31)
    2. Create Idoc Type      ( WE30)
    3. Create Message Type  ( WE81)
    4. Assign Idoc Type to Message Type ( WE82)
    1. Creating a Segment:
    nGo to transaction code WE31
    nEnter the name for your segment type and click on the Create icon
    nType the short text
    nEnter the variable names and data elements
    nSave it and go back
    nGo to Edit -> Set Release
    nFollow steps to create more number of segments
    2. Create Idoc Type      (WE30)
    nGo to transaction code WE30
    nEnter the Object Name, select Basic type and click Create icon
    nSelect the create new option and enter a description for your basic IDOC type and press enter
    nSelect the IDOC Name and click Create icon
    nThe system prompts us to enter a segment type and its attributes
    nChoose the appropriate values and press Enter
    nThe system transfers the name of the segment type to the IDOC editor.
    nFollow these steps to add more number of segments to Parent or as Parent-child relation
    nnSave it and go back
    nnGo to Edit -> Set release
    3. Create Message Type  (WE81)
    nGo to transaction code WE81
    nChange the details from Display mode to Change modenAfter selection, the system will give this message “The table is cross-client (see Help for further info)”. Press EnternClick New Entries to create new Message Type
    nFill details
    nSave it and go back
    4. Assign Idoc Type to Message Type (WE82)
    nGo to transaction code WE82
    nChange the details from Display mode to Change moden After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    nClick New Entries to create new Message Type.
    nFill details
    nSave it and go back
    There are three types of records :
    nControl Record                          nData Record                                     nStatus Record
    Control Record - contains the key information like destination, IDoc type, message type, port and sender information. Control records are of EDIDC type of structure.
    Data Records - This contains two parts.
    nAdministrative Section and Data Section
    nAdministrative Section consists of Idoc number, Segment Name, Segment number, Version, Segment Hierarchy etc.
    nData Section contains the data of respective segment
    nData records are of EDIDD type of structure
    nStatus Record - whenever a process is taken place, system will generate status records.
    nWe can identify the process with the number of status record.
    n01 - 49  for Outbound Process
    n50 - 75  for Inbound Process
    nwhen IDoc is processed the messages are:
    n01 - IDoc is created 
    n30 - IDoc is ready for dispatch
    n03 - IDoc is processed
    check all the below links u will find lot of info
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    For ALE -- IDoc's
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    ALE/ IDOC/EDI
    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.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
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    http://www.angeli.biz/www5/books/IDocBook/IDocBook.pdf
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    ~~Guduri

  • Reading material for ALE IDOC

    Hi Friends,
    Can anybody provide me any reading material for IDOC process so taht I can learn and use the IDOC functionality. I want to process few SAP transactions in the background through IDOC.
    Thanks & Regards
    Satya

    Hi Friends,
    Can anybody provide me any reading material for IDOC process so taht I can learn and use the IDOC functionality. I want to process few SAP transactions in the background through IDOC.
    Thanks & Regards
    Satya

  • Materials for idoc

    Hi am interested to learn about idocs can you provide me some useful links

    Hi saranya srithar  ,
    IDoc is an Intermediate document that holds application data.
    A container used to exchange data
    It is independent of the complex SAP structure to store data.
    It serves as the vehicle for data transfer.
    IDoc Type defines the structure and format in which the data is exchanged.
    It is similar to a structure in SAP
    IDoc data is an instance of IDoc Type
    IDoc  acts as a standard SAP interface to exchange business data through ALE.
    From an SAP system, an IDoc can be sent to and received from
    An SAP R/3 system
    An SAP R/2 system
    An EDI subsystem
    Any third-party application software
    Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
    These r all the t/codes which we will come across in IDocs:
    TCODE     TTEXT
    BD10     Send Material
    BD100     IDoc display object channel view
    BD101     Consistency check
    BD102     Outbound registry
    BD103     Inbound registry
    BD104     maintain tbd53
    BD105     Maintain Supported Business Objects
    BD11     Get Material
    BD12     Send customer
    BD13     Get customer
    BD14     Send vendor
    BD15     Open vendor
    BD16     Send Cost Center
    BD17     Get Cost Center
    BD18     Send General Ledger Account
    BD19     Get General Ledger Account
    BD20     IDoc passed to application
    BD21     Select change pointer
    BD22     Delete change pointers
    BD23     Delete serialization data
    BD24     Send Cost Elements
    BD25     Send Activity Type
    BD26     Get Activity Type
    BD27     Send cost center activity prices
    BD28     Send obj/cost element control data
    BD30     Distribute material object list
    BD31     Distribute document object list
    BD32     Distribute plant allocations(matBOM)
    BD33     Distribute material variants (ALE)
    BD34     Distribute order BOM
    BD35     Send Business Process Groups
    BD36     Send Business Processes
    BD37     Send Business Process Price
    BD40     Read change pointer for group
    BD41     Dispatch IDocs for group
    BD42     Check IDocs for group
    BD43     Post IDocs for group
    BD44     Assign Message Types to Serlz. Group
    BD47     Dependencies between methods
    BD48     Dependency method - message
    BD50     Activate Change Ptrs for Mess. Type
    BD51     Maintain function modules (inbound)
    BD52     Activ.change pointer per chng.doc.it
    BD53     Reduction of Message Types
    BD54     Maintaining Logical Systems
    BD55     Maintain IDoc Conversion
    BD55OLD     Maintain IDoc Conversion
    BD56     Maintain IDoc Segment Filters
    BD57     Maintain link and serialization ty.
    BD58     Convert organizational units
    BD59     Allocation object type -> IDoc type
    BD60     Additional data for message type
    BD61     Activate Change Pointers - Generally
    BD62     Define Segment Conversion Rule
    BD62OLD     Define Segment Conversion Rule
    BD63     Transport ALE Tables of Message Type
    BD64     Maintenance of Distribution Model
    BD65     Maintain IDoc type required fields
    BD66     IDoc type field -> change doc.field
    BD67     Maintain methods (inbound)
    BD68     Maintain Lists
    BD68OLD     Maintain Lists
    BD69     Assignment of Message Type to IDoc
    BD70     Synchronize Number Ranges
    BD71     Define FM for dependent bus. object
    BD72     Activate Events
    BD73     Reposting of IDocs (ALE)
    BD75     Convert IDoc Status
    BD77     Distribution of control data
    BD78     Monitoring control data distribution
    BD79     Maintain IDoc Conversion Rules
    BD79OLD     Maintain IDoc Conversion Rules
    BD81     Filter objects parameter filtering
    BD82     Generate Partner Profiles
    BD83     Send IDocs after an ALE error
    BD84     Post IDocs after ALE error
    BD85     Consistency check for transfer
    BD86     Consistency check for sales
    BD87     Status Monitor for ALE Messages
    BD89     Control data model. - initial screen
    BD91     Send Characteristic
    BD92     Send Class
    BD93     Send Classification
    BD95     Specify ALE object types
    BD96     filter objects of receiver determin.
    BD97     Assign RFC dest. to Logical Systems
    BD98     Consistency Check Workflow Connectn.
    BD99     Message type dependencies
    WE02     Display IDoc
    WE05     IDoc Lists
    WE06     Active IDoc monitoring
    WE07     IDoc statistics
    WE08     Status File Interface
    WE09     Search for IDocs by Content
    WE10     Search for IDoc in Archive
    WE11     Delete IDocs
    WE12     Test Modified Inbound File
    WE14     Test Outbound Processing
    WE15     Test Outbound Processing from MC
    WE16     Test Inbound File
    WE17     Test Status File
    WE18     Generate Status File
    WE19     Test tool
    WE20     Partner Profiles
    WE21     Port definition
    WE23     Verification of IDoc processing
    WE24     DefaultValuesForOutboundParameters
    WE27     DefaultValues for Inbound Parameters
    WE30     IDoc Type Development
    WE31     Development IDoc Segment
    WE32     Development IDoc View
    WE34     Object for Display of XML IDocs
    WE40     IDoc Administration
    WE41     Process codes, outbound
    WE42     Process codes, inbound
    WE43     Funct.module: Status record display
    WE44     Partner Types and Checks
    WE45     Forward (inbound) (V3, EDILOGADR)
    WE46     Error and Status Processing
    WE47     Status Maintenance
    WE50     System process codes: Texts
    WE51     System process codes: Change texts
    WE54     FMs for changing file names
    WE55     Function Module for Path Names
    WE56     IDoc Administration
    WE57     Assignment Messages for Appl. Objs
    WE58     Status process codes: Texts
    WE59     Change status process codes
    WE60     Documentation for IDoc types
    WE61     Documentation for IDoc record types
    WE62     Documentation for segments
    WE63     Documentation
    WE64     Documentation message types
    WE70     Conversion: Basic types
    WE71     Conversion: Extensions
    WE72     Conversion: IDoc types
    WE73     Conversion: Logical messages
    WE81     Logical message types
    WE82     Assign Messages for IDoc Type
    WE84     Assignment of IDoc and appl. fields
    WE85     Create Rule Names
    WEBU     Printing Labels via Assortment List
    WEDI     EDI Basis
    WEINBQUEUE     IDoc Inbound Queue
    WEKF     Purchase order SAP Retail
    WEL0     Forward (inbound) (EDILOGADR)
    WEL1     EDI: Interface Invoice for EDILOGADR
    WELI     Maintain Status Groups
    cheers!
    gyanaraj

Maybe you are looking for

  • IOS 8 voice dialing, "Just to confirm..."

    What a huge step backward in the usability of my iPhone.  Instead of telling Siri, "call Mom mobile" and getting the response "calling Mom mobile" followed by the call going through, Siri now responds with, "Just to confirm, would you like to call Mo

  • ClearType makes fonts in Dreamweaver code view hard to read

    I'm using Dreamweaver 8.0.2 with Windows Vista Business. As you know, Vista has a feature called "ClearType," which is supposed to help smooth out the on-screen fonts. It normally does do this, but for some reason, in Dreamweaver code view, some of t

  • Query about the Cache in browser Netscape

    The Page you are trying to view contains POSTDATA that has expired from cache. If you resend the data, any action the form carried out (such as a search or online purchase) will be repeated. To resend the data, click OK, Otherwise, click Cancel.

  • Layout with Pages

    Hello, I would like to create a document of many sides (perhaps 300 to 500) and would like to be sure, Pages can do this and give out a document for printing and in the layout fix I did. Is that possible and sure – or should I use iCalamus or somethi

  • Smart Album based on metadata

    How do I create a smart album based on metadata content. I want to have one that has all my geo-tagged (latitude/longitude not blank) photos in it. Dual G5/Dual G4/MacBook Pro   Mac OS X (10.4.10)   Extreme N/Apple TV/iPhone