ALE/IDoc: About changed and new funcitons in Release 6.40

Hi,
I'm not good at ALE/IDoc, but I have one question about the Release Notes for Basis component(Release 6.40).
(cf: http://help.sap.com/erp2005_ehp_03/helpdata/EN/ec/f23442d692ad04e10000000a1550b0/frameset.htm)
In the above document, in the category of "Effects on System Administration", on 3rd line,
"Newly created segments cannot generally be enhanced, and are classified as such"
I cannnot understand 2 points about this sentence.
The 1st is that "Newly created segments" means the segments I created by myself ? or the ones that were created after release 6.40? Which is correct?
The 2nd is what's the meaning of "cannot generally be enhanced, and are classified as such" ?
Once I created some segments, it is prohibited from customizing or changing them?
If you have some ideas or answers, please help me.
Best Regards,
Dai

Hi,
What I understand from the document is the segments created after release 6.40 by SAP cannot be enhanced because the segments are already released.
The custom segments can be enhanced before release.
Regards
Manasa

Similar Messages

  • Warn About Changes and page flow

    Hi, in dev guide, it is said:
    For any single page, or first page in a navigation flow where the retainAM URL parameter value is set to Y (and the pages share the same root UI application module) as you navigate between each page, set the Warn About Changes property to True on the pageLayout region.
    in other word, if pages in page flow are in the same AM, after changing am in the first page, anytime leave the following page to click the home link(oracle branding), the WarnAboutChanges msg should be alerted?
    But,
    Now I have two pages, using the same AM, set the two pages' property "Warn About Changes" to true.
    And I want to implement this: after inputing some words, and click a sunmitButton forward to pageB(add retainAM = Y in setForwardURL in code), then in pageB don't do anything, but click home link, WarnAboutChanges message does not alert.
    Could anyone help to explain this?
    And how to implement the page flow warnAboutChanges?
    And how root application module to set if different pages in different AMs?
    PreThanks to you very much!

    But,
    Now I have two pages, using the same AM, set the two pages' property "Warn About Changes" to true.
    And I want to implement this: after inputing some words, and click a sunmitButton forward to pageB(add retainAM = Y in setForwardURL in code), then in pageB don't do anything, but click home link, WarnAboutChanges message does not alert.
    Could anyone help to explain this?
    I asked u previously also read dev guide properly, here it what dev guide say:
    "By default, the Warn About Changes property is set to True for each of the items in this list except for the
    OASubmitButtonBean whose default value is False (a ccording to the UI guidelines, the "Warn About
    Changes" check should be performed for all submit button instances except for Cancel, Apply and Submit
    buttons). If you want to explicitly enable the check for a submit button, set this property to True. Note that can
    also set it programmatically by calling OASubmitButtonBean.setWarnAboutChanges(pageContext,
    Boolean.TRUE) in processRequest()."
    I hope this answers ur question.
    And how to implement the page flow warnAboutChanges?
    Read "Save Model ('Warn About Changes')" in dev guide :).And how root application module to set if different pages in different AMs?
    You can nest differnt AMs in on AM in AM wizard.--Mukul                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • SSIS DataFlow - copy only changed and new records

    I am copying a few tables each night from one SQL server to another. At the moment I delete every record from the destination table, and then copy all records from the source table with a SSIS Data Flow Task. 
    That works fine so far, but I would like to copy only changed or new rows. What would be the best way with SSIS to achieve this? I am quite new to SSIS, I have no idea if my goal is possible and how...

    I am copying a few tables each night from one SQL server to another. At the moment I delete every record from the destination table, and then copy all records from the source table with a SSIS Data Flow Task. 
    That works fine so far, but I would like to copy only changed or new rows. What would be the best way with SSIS to achieve this? I am quite new to SSIS, I have no idea if my goal is possible and how...
    Many ways:
    1st way
    1.use Merge function from source to destination table where you can have this conditions like load when not matched and don't load when matched.
    2. follow this ssis steps:
    execute sql task where you can write merge function from source to destination 
    http://blog.sqlauthority.com/2008/08/28/sql-server-2008-introduction-to-merge-statement-one-statement-for-insert-update-delete/
    2nd way:
    oledb source 2.lookup outputlookup 3. oledb destination table 
    and you can mention in lookup as no match output.
    3rd way:
    you can use scd transformation task in ssis...
    4th way:
    you can use if exists update  if not exists insert.. see below
     http://blogs.msdn.com/b/miah/archive/2008/02/17/sql-if-exists-update-else-insert.aspx
    http://sequelserver.blogspot.com/2011/02/alternate-to-if-exists-update-else.html
    - please mark correct answers

  • Why does an Inbound IDoc no change and differs from an Outbound IDoc no?

    Hi Experts,
    This seems to be a basic question..! But can someone kindly clarify why an IDoc number gets changed when sent from one R/3 system to another R/3 system and how does this happen???
    i.e., whenever an IDoc was triggered from R/3 system A to R/3 system B through XI/PI, the Inbound IDoc number (in system B) differs from the Outbound IDoc number (in system A)... Why does this happen and how???
    Thanks in advance!
    Br,
    G@nesh

    Hi Ganesh,
    The IDOC numbers are always Unique,
    IDOC can be generated in SAP system as a result of internal testing (WE19), or
    can be posted from a non sap system (say PI).
    So every time a new IDOC comes, it is assigned a new number to avoid confusion and also this plays a
    critical role in the  end to end testing and validation.
    If you look at the control record of the IDOC you can see a element called DOCNUM. this stores to actual IDOC number.
    from PI side you can  use IDX5 and in ECC  We02/05 to notice the idoc numbers.
    Regards,
    Srinivas

  • Questions about Contracts and New Phones

    I've had some questions about how upgrading and adding new lines to a contract works and I haven't been able to find the answers through Google. First some background information: We started this most recent contract in September of 2011 and as such the current contract will end September of 2013. According to the phone information portal, all three of the devices on my account will be eligible for an upgrade this Saturday (May 4th, 2013). My daughters birthday just so happens to coincide with that date and as such we were planning on surprising her by taking her to buy a new phone and we are going to allow our son to upgrade his phone as he has been asking to for a while.
    Is there any way of locking/limiting the amount of data allowed for each phone on a shared plan? I'm worried that my daughter will go way over our limit and not pay attention to the point where she will end up costing us a very large amount of money
    Does adding a new line require the start of a new contract?
    My son was interested in purchasing the "Samsung Galaxy S4" and has noticed that pre-orders for that phone are currently available. Is it possible to pre-order the phone on that date using the upgrade so that the price will be reduced?
    If the answer to number 2 is a no, does adding the new line take away the upgrades from other phones or would he be able to go to the store past the release date and upgrade then?
    Thanks for taking the time to read through all of this. Any help that I receive will be extremely appreciated.

    1. Yes. There is an additional fee per line you wish to do this for. When you add the line you can choose this option and set the data amount it is allowed to use.
    2. Yes. Each line is a separate contract with its own expiration date.
    3. The contract starts when you sign up for the contract. The amount will be pro-rated on the plan if it is not started until part-way through your billing cycle that is what you are asking. Doing the pre-order just guarantees you the phone in case they sell out.
    4. No it will not take any upgrades away as each line has its own termination date. You can move upgrades around between lines though.

  • SCD TYPE 2 in ODI 11g-error in INSERT CHANGING AND NEW DIMENSIONS

    Hi Guys,
    Im using IKM:Oracle Slowly Changing Dimension to achieve SCD TYPE 2.
    It is working fine for Overwrite on change.
    But whenever there a new insert upon change(Add Row on Change) in source, throwing below error:
    ODI-1228: Task INT_EMP_SCD_TYPE (Integration) fails on the target ORACLE connection ORA_DEV_EDW.
    Caused By: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_EDW.EMP_KEY) violated.
    I have unique key in target table column SAPID.
    How to overcome this issue.
    quick help would be highly appreciated.
    Thanks,
    Sreedhar S,
    <telephone number removed by moderator. this is a publicly viewable forum, not Oracle technical support>

    Hi Sreedhar,
    As said in the error message, you have an unique or primary key on one column and you try to insert a value already existing. This is a design issue.
    You have to ensure that you don't try to re-insert existing value for the column(s) with the key.
    Regards,
    Jerome

  • Transport ESS MSS changes and new web dynpros

    Hi ,
    How do we transport the changes that we  make to ESS/MSS web dynpro screens and how do we transport the new web dynpro applications that we develop?
    Appreciate any suggestions.
    regards
    Sam

    Hi Sejoon,
    Why do you want to copy the DC's to a custom SC. It gives you a lot of problems with references in the WebDynpro's and in the backend customizing.
    The ESS/MSS applications are in a separate business package which you don't need to upgrade whenever you apply a patch to your portal, so there is no administrative effort.
    Also, if you copy the DC's to a custom SC, and you do want to upgrade the package, then you still have to copy the DC again, and redo all your changes.
    Anyway, SAP's recommended approach is described in the NWDI cookbook; it says not to copy the DC's, but change directly in the original.
    Johan

  • Report Changes and New Reports in R12 - A useful document

    Hi All,
    I found this document.
    I hope it will be useful for everyone
    EBS R12: Financial Reports impacted by the R12 (12.0 and 12.1) Upgrade [ID 1110684.1]
    Pleaselet me know if there are any addional reports or completely new reports available in R12.
    Thanks and Regards,
    MPH

    997361 wrote:
    Hi,
    What are the new reporting in R12? I am not clear on this.
    Thanks
    KNhttps://blogs.oracle.com/stevenChan/entry/ebs_data_model_1213
    https://blogs.oracle.com/stevenChan/entry/ebs_seed_data_comparison_reports
    http://docs.oracle.com/cd/E18727_01/index.htm
    https://forums.oracle.com/forums/search.jspa?threadID=&q=RCD&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
    Thanks,
    Hussein

  • Replicate only changed and new data

    Dear,
    Is there a possibility to SQL Server 2012, to all the changes that happen in the DB x record in DB y?
    DB x would have all the data, and DB y would contain only the data from the time of recording.
    If the DB x insert data, the DB y are only visible data by the insert.
    If the DB x update data, the DB y are only visible data by the update, which can be seen that the data update.
    If the DB x delete data, the DB y are visible data are deleted.
    DB y be recorded only certain information, for example a specific table and certain procedures.
    Monitoring changes must be in real time.
    The structure must remain the same.
    Something like this would be like:
    Thank you

    You should do a no-sync subscription and then ensure that the data and schema necessary are on the subscription and use the continue on data consistency error profile.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Alerts for item master change and new item creation

    hai experts
                       my manager has to get an alert when any update has been done in item master or when a new item master is created .

    Hi.........
    Check this query for alert.........
    Quaery for New Item Creation:
    SELECT T0.[ItemCode], T0.[ItemName], T0.[CreateDate] FROM OITM T0
    Where DateDiff(DD,T0.[CreateDate],GetDate())<2
    Query For Updation of Item:
    SELECT T0.[ItemCode], T0.[ItemName], T0.[UpdateDate] FROM OITM T0
    Where DateDiff(DD,T0.[UpdateDate],GetDate())<2
    Above two alerts will be coming for two days........
    Regards,
    Rahul

  • Significance of "Change"- "unchanged" and "New" - "Old" statuses during maintain authorization?

    Hi all, I am new in SAP Security/GRC and I need help: What does it mean to see the statuses "changed" and "New" on the 'maintain Authorization' page ? I learnt there are actions one must perform to change the 'Change' status into "unchanged' and also integrate the "New" transactions with the "old". Could anyone explain please?
    Thanks

    Hi Divyanshu  the reference was helpful in explaining what will happen if new transactions are added or old ones removed without following appropriate maintenance procedures.
    What I learnt from the discussions in that reference is that if for example, we delete a transaction and fail to carryout the maintenance tasks as required, the transaction really doesn't get deleted as it still shows up the next time we log in. Or that the new transactions added may not pass the authority checks of S_T CODE, This is because any changes made to the menu transactions takes off the S_T CODE object from its 'standard' and 'unchanged' statuses to the 'changed' status. 
    Once the S_T CODE object gets into CHANGED status, transaction deletions made in the menu path DO NOT overwrite the transaction values in S_T CODE.  The transaction doesn't exist in the menu, but can be called because it still exists in S_T CODE (a possible risk source!!).
    So to fix the problem, always check to see that S_T CODE is in STANDARD status when deleting existing or adding new transactions by performing the actions I listed in my second comment.
     Once again, Thanks for your time. 

  • ALE / IDOC / RFC / EDI

    hi all ,
    i m very new for ALE / IDOC / RFC / EDI and i have to do these things , can anybody send me some material
    to read these things from starting? and please do clear what shud i read first or plz. tell me the sequence??
    my E-mail : [email protected]
    regards saurabh.

    Hai.
    check this.
    Application Linking and Enabling (ALE)
    In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
    For our purpose we have two clients
    namely Client 100 and Client 200.
    System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
    Distribution of Material Master Data Between two Systems
    1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
    To do this follow the following steps
    Execute SALE Transaction Code
    On The Screen Click on Sending and Receiving Systems.
    Then Click on Logical Systems.
    Then Click Defining Logical Systems.
    Click New Entries Button
    (E.g. (LG100 sending system)
    (LG200 receiving system))
    Enter two logical system names and their description.
    Save
    Comeback to SALE Transaction Code screen.
    2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
    LG100 assign to client 100
    LG200 assign to client 200
    To do this, do the following.
    Click Assigning Client to Logical System.
    Ignore the message that comes up on the screen.
    Select client 100
    Click details button on the toolbar icon or press F2.
    In the logical system box, enter LG100.
    Click on the save Icon
    Click the back button.
    Now select client 200.
    Click details icon or press f2.
    In logical Systems box, enter LG200.
    Save
    Back.
    Comeback to SALE Transaction Code screen.
    3) Maintain RFC Destination: (TR.CODE:SM59)
    (Note: Do Not Create This Step)
    Click Create Button on the Screen
    On the Screen Maintain RFC Destination i.e LG200.
    Enter LG200 in RFC destination box.
    Connection type is 3
    Give a description for the RFC destination.
    Maintain Technical Settings on Details on Technical Settings tab
    Target Host as : SAPKDC (NOTE: Save it as a Host Name)
    Maintain Logon Details on Logon/Security tab.
    Language: EN.
    User: MMUSER200 (This is the logon for dist.)
    Client : 200
    Password: MM1234.
    Save.
    Click on create to do the above process for Client 200 in
    The client 200 system.
    4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
    Execute Maintain distribution model directly for
    creating the model.
    Click on change mode button on App tool bar of the Screen.
    Create Model View pushbutton on App tool bar of the Screen.
    A pop screen will appear in which you specify
    Short text as Distribution for MM Data.
    Enter Technical Name as LGMODEL.
    Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as LGMODEL.
    Sender as LG100.
    Receiver as LG200.
    Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as LGMODEL.
    Sender as LG200.
    Receiver as LG100.
    SAVE.
    On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Logical System as LG200.
    Then execute the screen.
    Click back.
    Again On the same screen goto Menubar and select EDIT.
    Again select Model View and then select Distribute.
    ****LOGIN to client 200.
    Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Model View as LGMODEL
    And Specify the Logical System as LG100.
    Then execute the screen.
    Click back.
    *******Switch back to client 100 Session.
    5) Create Material using MM03 Tr.Code.
    Enter the material name as LGMATERIAL
    Industry sector as Mechanical Engineering
    Material Type as Finished Products.
    And then Click on Data Pushbutton on the App tool bar.
    Select views.
    In the select views box for materials check basic data 1 AND 2.
    Click enter icon.
    In the next screen that you get
    Give the text of the material as NEW MATERIAL.
    Base unit of measure as KG.
    Gross Weight as 200.
    Net Weight as 100.
    Weight Unit as KG.
    In the description area language (E) and material description.
    Click Save.
    Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
    6) Execute BD10 to transfer the material in which you specify
    the material as LGMATERIAL and
    message type as MATMAS (client100).
    Then a Screen will be displayed in which it shows that
    1 Master Idoc Generated .. Enter
    1 Communication Idoc Generated..Enter.
    *******LOGIN to Client 200.
    7) Execute BD11 to get the material in which you specify
    the material as LGMATERIAL and
    message type as MATMAS (client200).
    8) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    If not follow these steps.
    9) Execute Tr.code WE19( for rectification of errors in client200).
    Specify the Existing Idoc Number and Executes it .
    A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
    10) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    Now the Material is correctly displayed in Client 200.
    11) Monitoring of IDOCS.
    Transaction Codes:
    IDOC Display of Status: WE 05.
    IDOC Date and Time: WE07.
    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
    idoc:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    EDI:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    http://www.erpgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    rfc:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    http://www.erpgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    regards.
    sowjanya.b

  • Position data not getting ALEd correctly through change pointers

    Hi All,
    When Posiiton is updated in One system, it gets transfers to another systems through ALE/IDOCs using change pointer method.
    when a new holder is assigned to the position in system A,  the updated data is not getting tranfered to system B.
    All the ALE settings are correct, background jobs are scheduled correctly for the change pointers.
    How ever the updated position data is not getting transfered to system B.
    The IDOCs are faling with message " Relationship starting from 01O XXXXX impossible - 01S XXXX does not exist/is not active".
    Please let me know how to over come this error and tranfer the posoition data when ever it is changed.
    Thanks & Regards,
    Preethi G

    hello Sagar,
    u r dynamically generating dropdowns in ur view say VIEW1.U must be generating ur UI dropdowns on click of the button under a trnsparent container with a particular DROP DOWN INDEX ID .
    in ur onActionAdd method if u r generating drop downs with ID say DD101, DD102, DD103 and so on ...
    thn in ur close button , u need to use the method REMOVE_CHILD_NODE and try to remove the dropdowns with same index .
    u cn take reference of this code :
    DATA :
        DATA:
                lr_node_info     TYPE REF TO if_wd_context_node_info ,
                lr_node          TYPE REF TO if_wd_context_node,
                dd_indx_id       TYPE string .
    CONCATENATE lv_node wd_this->count_sysdel INTO lv_node.
            dd_indx_id = 'DD_1'.
            wd_this->count_sysdel = wd_this->count_sysdel + 1.
            wd_this->count_dd_sys = wd_this->count_dd_sys + 1.
            CONCATENATE dd_indx_id wd_this->count_dd_sys INTO dd_indx_id.
            lr_node = wd_context->get_child_node( name = lv_node ).
            lr_node->invalidate( ).
            CALL METHOD lr_node_info->remove_child_node
              EXPORTING
                name = lv_node.
            lo_drdwn = lo_container->remove_child( id = dd_indx_id ).
    here lv_node is the name of ur node , I am using count_sysdel of type NUM and concatenate statement
    to provide unique names to the generated node.
    u cn declare it under the attributes tab .
    u can have dd_indx_id = 'DD_1' and increment count each time using
    wd_this->count_dd_sys  which is another counter .
    do revert back if u need any assitance ,it shud help .
    rgds,
    amit

  • ALE/IDOC interview q's with answers(urgent)

    Hi folks,
    I want ALE/IDOC q's and answers .I have gathered some ,but still i want more...Please send as soon as possible.
    Regards,
    nagaraj

    Hi,
    Remember all the following TCodes:
    WE02      Display IDoc              
    WE05      IDoc Lists                
    WE06      Active IDoc monitoring    
    WE07      IDoc statistics           
    WE08      Status File Interface     
    WE09      Search for IDoc in Database
    WE10          Search for IDoc in Archive        
    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          Default values outbound parameter 
    WE27          Default value inbound parameter   
    WE30        Development IDoc Type              
    WE31        Development IDoc Segment           
    WE32        Development IDoc View              
    WE33        Value tables for IDoc documentation
    WE34        Object for Display of XML IDocs    
    WE40        System process codes               
    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        IDoc administration                
    WE47        Status Maintenance                 
    WE48      Inbound process codes: Texts       
    WE49      Inbound process codes: Change texts
    WE50      System process codes: Texts        
    WE51      System process codes: Change texts 
    WE52      Outbound process codes: Texts      
    WE53      Outbound process codes: Change texts
    WE54      FMs for changing file names        
    WE55      Function Module for Path Names     
    WE56      Status process codes               
    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     Parser for IDoc types and rec.types
    WE64     Documentation message types        
    WE70     Conversion: Basic types            
    WE71      Conversion: Extensions            
    WE72      Conversion: IDoc types            
    WE73      Conversion: Logical messages      
    WE81      Logical message types             
    WE82      Assignment Messages for IDoc Type 
    WE84      Assignment of IDoc and appl. fields
    OYSN     Number Ranges for IDOC
    sm59     Set up the RFC Destination
    If you want You can further Refer the Text Book By: Aravind & Nagapal.
    It is very useful.
    Regards,
    Anji

  • ALE IDOC's VS XI

    Hi,
    I have a scenario where I have to convince a client to move to XI instead of using ALE IDOCS which he is currently using.
    Can anybody please tell me what are the advantages of using XI instead of just ALE IDOCs between SAP and Non SAP systems??
    Regards,
    Puneet

    hi,
    have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    it described XI adavantages in IDOC scenarios
    (many protocols, idoc packages, acknowledgments - generic)
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Maybe you are looking for