ALE/IDoc interface for Special Ledger Data

Anybody has experience with extracting Special Ledger data from ECC through ALE/IDoc interface?
Because Special Ledger is cutom to any client, I'm thinking we need to create a custom IDoc type. I didn't notice any standard IDoc type. Any documentation or any tips on this will be appreciated.
Thanks,
Srinivas

problem has been solved
thanks

Similar Messages

  • ALE, IDoC Interfaces

    Hi Experts,
                I am working on ALE IDoCS Interfaces... Can anyone send me the step by step procedure for creating a sample ALE,IDOC scenario where i can send a message from client1(800) to client(810).
    I need the following
    1.complete ALE configuration setting between two clients.
    2.Creation of Idoc , segment, filling the idoc from scratch.
    3.Dispatching the Idoc on the ALE Interface
    4.Handling any exceptions
    Is it possible to create an ALE Interface to the same client(800 to 800) for sample testing
    Thanks and Regards
    AK

    Hai Ashok
    Go through the following Steps
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode  BD64 ? Create Model View
    Tcode  BD82 ? Generate partner Profiles & Create Ports
    Tcode  BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
            save and goback.
    2) Tcode BD50--->  check the MATMAS check box save and comeback.
    3) Tcode BD51--->  goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52--->  give message type : matmas press ok button.
       select all  what ever you want and delete remaining fields.
       save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
       it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
       give Message type : MATMAS and Executte
    Thanks & regards
    Sreenivasulu P

  • Actual Line Items for Special Ledger

    Hello,
    I wrote an report to show FI-SL balances.
    In addition to that, now I need the actual line Items for them (table TRACTSLA)
    I've found a transaction called KE5Z, which is for PCA line items.
    Is there also such a transaction for special ledger line items, which I can reuse?
    Thanks in advance.

    Tty KE24, KE25.
    Regds,
    Anil

  • Interface for retrieving CVS data

    Hi
    I want to write an interface for retrieving cvs data,like the last person toupdate the file,the last date and everything visible in cvs log..
    Can anyone help me in designing the interface,and also is there any api's available for this
    Please reply soon..
    Thanks and regards
    Sumit

    For simple CSV files that you generate yourself, that should indeed be more than enough. The standard CSV files that most applications output have some more rules however, and Excel breaks those rules
    (sigh).
    Check this out:
    http://ostermiller.org/utils/CSV.html

  • How to change the safety interval for 0FG_DO01- Special ledger data source

    Gurus,
    Is there a way to change the safety interval for SAP Standard Data source 0FG_DO01(safety Inteval).
    I am only able to display it in RSA2 and not change.
    Appreciate your immediate assistance.
    Thanks,
    Ravi Aananthuni

    You can view it in RSA2. However you may need to  update table ROOSOURCE to change the value of safety interval upper and lower limits.
    Thanks,
    Ravi ananthuni

  • Integration directory : select IDOC interface for WAS business system

    Hi,
    While adding a receiver determination for an WAS business system, I do not get any IDOC based message interface from the design repository proposed for my business system in the popup dialog.
    The only interfaces that appear are for the non SAP standard SWCV that we added to the business system. But no interface for the APPL 5.0 SWCV ( or BASIS 7.0 ) appears.
    In the SLD this component is correctly listed for that WAS .
    If I remove all the default search criteria , eventually, the in terface appears but after selecting it I get a message saying :
    "Message Interface does not exist in any software components installed on this business system "
    Since everything looks ok in the SLD I'm puzzled. How does this look on other systems ?
    Any ideas
    ( The business system was updated from APPL 4.70 / BASIS 6.40 to APPL 5.0 / BASIS 7.00 some time ago but I don't know how it look before the upgrade of the business system )
    rgds
    Dirk

    Hi Bavesh,
    Yes, It's correctly listed.  I did not manually link these components to the technical/business system. This happened automatically by the SLD data collector service. I also cleared the SLD cache several times,
    rgds
    Dirk

  • Reg ALE-IDOC------- rush for points :)

    Hi all,
    I m trying ALE from client 800 to 810 of IDES. I completed the outbound process and i m seeing the IDOC with status 03 in WE02 with green signal.
    Now wht i need to do to see my iDOC....help me futher.
    Regards,
    [email protected]

    Hi
    See the tarnsaction WE05
    or in the tables EDIDS,EDIDC and EDID4
    see the other related tcodes of the IDOC's
    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
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Special Ledger Data Transfer GCU1 Splitting rule "Z12/SKIP/0001"

    Hello experts,
    when transfering documents from financial accounting into a special ledger (GCU1) I get the error message "Keine Aufteilungsregel definiert zu Z12/SKIP/0001" (No splitting rule defined for Z12/SKIP/0001).
    Under Financial Accounting (New) --> Special Purpose Ledger --> Actual Posting --> Settings for Accounting Integration --> Document Splitting --> Additional Activities --> Define Splitting rule the function "automatically split" is not checked for the named categories. Is my category missing or do I have to check the "automatically split"? Can anyone help me on this?
    Do I have to use a different transaction for transfering documents if new G/L is active?
    Best regards,
    Maria
    Edited by: Anna-Maria Noack on Dec 3, 2008 10:09 AM

    Hi,
    r u using Spl gl for first time.i would like to know if the entry is coming for the first time.
    r u getting error at that time.
    pl specify. if using for first time, new fields and new tables will get activated , so system at time of posting will check consistency with std and spl gl tables.
    we need to run consistency program REZZGLEX to get this consistency error to be resolved
    thanks
    g.bharathi

  • Reconcile Special ledger data

    Hi Guys,
    Could you tell me like how to reconcile data from BW with R/3 in case of special ledger?
    Regards

    create a report in R/3 in report writer and have one report on BI on the same lines and reconcile the data.

  • Usage of ALE - idocs generated for BAPIs

    Hi
      I need to use - the std idocs generated for BUS2032 object - CREATEFROMDAT2 method to store the BAPI call  ( BAPI_SALESORDER_CREATEFROMDAT2 )data for those sales orders that could not be created.
    If I want to use the SAP delivered BAPI ( BAPI_SALESORDER_CREATEFROMDAT2 ) to call as it within an ABAP program - and then if the call did not go through - then log the data for BAPI into the corresponding idoc with the message type SALESORDER_CREATEFROMDAT2 ( idoc type SALESORDER_CREATEFROMDAT202 )  do I need to move the values from the BAPI structures to the idoc segments programatically ?  Or since the idoc is linked to the BAPI - by definition, is there an implicit way to move data to the corresponding idoc segments and save the idoc .
    Can anyone out there give me a code sample to do - what I have asked above ?

    Hi,
    I guess you can use function module ALE_SALESORDER_CREATEFROMDAT2 to create idoc from bapi data. You can pass the entire data in internal tables that you are passing to BAPI into above mentioned function module and then it will create an Idoc for the same. Also populate the receivers in the internal table receiver.
    KR Jaideep,

  • Infrastructure for special stock data

    DeDear Experts,
    Is there any infrastructure for stock detail where special stock data is available like sales order stock and project stock.
    Free stock is available in S032 info structure, I want the same for special stock.
    Please suggest me in this regards as I need to develop the stock report in alternative unit of measure.
    Regards,
    vgl.

    As per OSS note 581240 only certain special stocks are updated in info structures S031-S039:
    The following special stocks are always updated:
    Special stock 'O': Stock of material provided to vendor
    Special stock 'W': Consignment stock at customer
    Special stock 'V': Returnable packaging stock at customer
    The following are never updated:
    Special Stock 'K': Vendor consignment stock
    Special stock 'M': Returnable transport packaging
    The following stocks are updated DEPENDING ON YOUR VALUATION TYPE (Special Stock Valuation indicator):
    Special stock 'E': Sales order stock
    Special stock 'Q': Project stock

  • IDoc programming for Requested Delivery Date - Inbound ORDERS

    Hi Folks,
    I want to manipulate Requested Delivery Date on the Sales Order.
    The Field for Req Del Date is RV45A-KETDAT.
    But this value is stored in VBAK-VDATU.
    When i am trying to modify this value using dxvbak structure, this value is getting populated correctly, but not updating in the table.
    Look at the code snippet below.
    if zedidc-sndprn = '0000902000'.
            IF ze1edk03-iddat = '002'.
              MOVE ze1edk03-datum TO zvbak-vdatu.             " Requested Delivery Date
               zvbak-vdatu = sy-datum + 7.
               BREAK-POINT.
               dxvbak = zvbak.
            ENDIF.
            endif.
    What's wrong here??
    Thanks,
    Matt

    Done

  • Need BAPI for upload the special ledger data (GB01)

    Hi Guys,
    I have to upload the GB01 data from excel to sap.
    Is there any BAPI for this app
    plez Help me
    thanks

    hi
    use function modules JV_GB01_DIRECT_INPUT and JV_GB01_DOCUMENT_POST
    hope this helps you
    Regards
    Aakash

  • ALE delta extract for HR master data

    We want to create some R/3 delta extracts based on the HR PA* tables using the ALE delta extract function of generic extractor. Has anyone done this before?  Are there any OSS notes or documents that I should look at?  Thanks!

    Hi Bill Faison,
    This is very old message. I think your problem must be solved. If it is not then: yes we can extract Data from R/3 with ALE Delta .
    You have to perform below steps.
    1.     In your Table you need to activate ALE change   pointer.
    2.     Create change documents for required table.
    3.     Created Generic Extractor with ALE Delta.
    Hope this will help.
    Let me know if you have any concern or issue in this regards
    Best Regards
    Sharad Verma

  • Additional User Exits For Special Ledger Extraction

    Hi,
    I have a requirement to append 2 additional fields to data extracted for a 3fi_sl_xx_tt datasource.
    I was planning on using the standard transactional data user exit. However a consultant we have on site has suggested there is another user exit available prior to the data being extracted. He suggests that this will allow me to retrieve the additional data at the same as all the other data and therefore prevent having to loop around what could be a large internal table in the standard exit.
    Does anybody know if this is possible/feasible or even how I might check if an exit is avaialable.
    Any help much appreciated.
    Simon Bailey

    Hi Simon,
    Is the consultant referring to the user exit for populating into the FI-SL table rather than populating the extractor during the data pull from SAP BW ?
    It is very likely he is talking about using the user exit for populating the FI-SL tables using the user exit RGGBS000 or ZRGGBS000(generally coped to a Z).

Maybe you are looking for