IDOC: HRSM_D01

I maked migration from non SAP system to the SAP R3 via XI (IDOC HRMD_A07).Export file from non SAP system in .csv file.
Now I need store Attendences/Absences data into IT2001 (IDOC HRSM_D01), but I dont know structure of the IDOC and
I need to fill the tables PTEX2000 & PTEXDIR via HRSM_D01 IDOC.I use HRSM_D01 only for Attendences/Absences data.
What is the process of migration via HRSM_D01?
can you help me anyone?

How fill I the tables PTEX2000 & PTEXDIR via HRSM_D01?
Need help.thx

Similar Messages

  • IDOC HRSM_D External System / Deletion of vacancies failed

    Hi,
    we are using IDOC HRSM_D01 Upload Time Data to send HR vacancy data from an external system to SAP HCM.
    It should update Infotype 2001 with vacancy type 0100.
    This works fine. Data are sent via PI / IDOC and inbound processing through code HRSM_D.
    After that, we can see it in tables PTEXDIR and PTEX2000. It is transferred to HR/PA30 with the report RPTEXPT.
    So far, so good.
    Now we want to delete it. We re-send the same record, same  AWTYPE, DOCNR etc and add the "X" for REVERSED.
    The IDOC WE02 shows green, BAPI POST successful, but nothing is in table PTEXDIR and PTEX2000.
    When I look at the function module IDOC_INPUT_HRSM_SCHEDULE, it only handles PA2002 (Time Attendance, not absences) for reversed data. Is this true?
    Can I only delete Attendancies?
    Thanks for deedback
    hs

    When I look at the function module IDOC_INPUT_HRSM_SCHEDULE, it only handles PA2002 (Time Attendance, not absences) for reversed data. Is this true?
    Can I only delete Attendancies?
    I copied the whole sender agreement etc. and created a zIDOC_INPUT_HRSM_SCHEDULE procedure.
    I found out, that Infotype 2002 was hardcoded and 2001 Deletion was not supported. Now it workes, when I deleted the hardcoded 2002-checkup.
    But is there any better way?
    thx
    Holger

  • Idoc Tests

    Hi,
    We have a TIBCO JMS -> SAP XI -> SAP HR scenario, but at this moment we don't have the TIBCO part configured.
    We want to send some test messages from XI to HR (Idoc HRSM_D01), in order to test the IDoc processing in HR.
    Do you guys know, how can we perform tests between XI and HR?
    Thanks in advance,
    Luis

    Hi,
      I am not sure about the HR part, but once i replied to a thread for PU12 in sap hr for pushing data but it was to and from 3rd party,
    see if it helps you.
    Error while opening sld page of server
    And,
    http://help.sap.com/saphelp_erp2004/helpdata/en/4f/d52a70575e11d189270000e8322f96/frameset.htm
    Just see if it can work to and from sap xi.
    All the best.
    Anirban.

  • Programming HR Infotype 2003 updates

    Hi
    I have a requirement to create infotype 2003 (Substitution) records from a bespoke infotype 9007 that I have just created.  I am wanting to avoid a BDC session (naturally) and was therefore leaning towards IDocs or BAPIs.  I have spotted the IDoc HRSM_D01 that I could possibly use and then execute the report RPTEXTPT to process the data from the staging tables.
    What I wanted to know, was whether this would be the correct way forward, or is there a cleaner/more future proof way.  We are currently on 46C and are starting an upgrade to ECC 6.0 in Jan '07.
    Thanks in advance.
    Ian
    It appears I should be using the HR_INFOTYPE_OPERATION FM. 
    Message was edited by: Ian Stubbings
    Message was edited by: Ian Stubbings

    Tamás Nyisztor wrote:
    > Unfortunately SAP lacks perfection, deal with it.
    Hi Tamás,
    Of late i've been dealing with HR_INFOTYPE_OPERATION frequently & if you dig deep into it you'll see that there is a BDC being done using CALL DIALOG on dialog module HR_MAINTAIN_MASTER_DATA !!! And you must be knowing CALL DIALOG is obsolete.
    Anyways there's always an excuse of downward compatibility though
    BR,
    Suhas

  • Add segment in an infotype

    Hi,
    I created an idoc based on idoc HRSM_D01, and I want to insert a new segment as a child segment type of the root (ZHRSMD01) but I can't do it. It only allows me to insert below the existing segments.
    Can you help me?
    Sónia

    HRSM_D01           
            E1BP7012_2  
            E1BP7011_2  
            E1BP7031_1  
            E1BP7031_2  
    Actually the above segments are parent segments under HRSM_D01. It wont allow u to enter another segment as same as parent segment.
    So u have to add it under the related parent segment.
    Thanks
    Eswar

  • Inbound Interface using HRSM_D01 Idoc

    Hi,
    We have an inbound Idoc using the HRSM_D01 idoc. This interface allows an external system to send data to our SAP HR system to update infotypes 2001 and 2002.
    We are planning on extending this interface by not only allowing new values to enter the system but also cancellations of old records. For example an employee has reported working time for one day but would like to change the record into absence. The employee should then be able to change the record in the source system and the cancellation of the old record (deduction from IT2002) for the attendance and a new record (IT2001) for the absence should be sent to SAP.
    There is a field in the Idoc that indicates if the record should be reversed. But it seems like the RBDAPP01 program that processes the inbound idocs does not update the interface table PTEX2000 with records that have X in the REVERSED field in the idoc.
    Does anyone have experiences from cancelling records in a source system and the passing the cancellation to SAP HR?
    Thank you
    /Björn

    Hi,
    We have an inbound Idoc using the HRSM_D01 idoc. This interface allows an external system to send data to our SAP HR system to update infotypes 2001 and 2002.
    We are planning on extending this interface by not only allowing new values to enter the system but also cancellations of old records. For example an employee has reported working time for one day but would like to change the record into absence. The employee should then be able to change the record in the source system and the cancellation of the old record (deduction from IT2002) for the attendance and a new record (IT2001) for the absence should be sent to SAP.
    There is a field in the Idoc that indicates if the record should be reversed. But it seems like the RBDAPP01 program that processes the inbound idocs does not update the interface table PTEX2000 with records that have X in the REVERSED field in the idoc.
    Does anyone have experiences from cancelling records in a source system and the passing the cancellation to SAP HR?
    Thank you
    /Björn

  • Logical System in IDOC-XI scenario

    Hi,
         I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
        we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No.  2) Logical System. 
    my questions are
    a) Are we use Logical System in B to B scenario ?
    b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
    Thanks and Regards
    Mahesh.

    Hay Kumar,
    Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
    a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
    b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
    Have a Good One,
    Uri Lifshitz.

  • IDoc not received in MII

    Hi All, 
    I am using SAP MII 12.1.5 Build 87. 
    I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII. 
    We are able to send iDoc from SAP but we are not able to receive same in MII. 
    Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83. 
    Following are the log details for SAP MII Logger as well as SAP NW Log. 
    SAP NW Log: 
    Error processing JRA IDOC message  
    SAP MII Log: 
    Error processing JRA IDOC message  
    Error processing JRA IDOC message [server=xxx, client=xxx]  
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
    at $Proxy943.onMessage(Unknown Source)
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
    at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
    at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
    at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Please help me out on this issue.                                         
    Regards,
    Manoj Bilthare
    Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

    Hi Manoj,
    Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
    If this doesn't help you,please try  restarting your server again.
    How about the credential editor have you configured this as well?
    Regards,
    Sudhir Kumar
    Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

  • Open Sales orders through IDOC

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

  • Scheduling Agreement with Delivery Schedule using Idoc messages

    Hi all,
    Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
    My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
    As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
    Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
    Thank you
    Regards
    Subha

    Hi ,
    The Field
    LABKY : Delivery schedule key
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 026, Offset : 0393. external length : 000001
    Regards
    Seegal

  • Invoice and delivery notes - idocs..

    Hello SD experts,
    I am new to SD.
    Can any one tell me what is the invoice. I mean
    what are the table AND transaction codes I have to go and check ?
    What are delivery notes ?
    My functional consultant is telling that
    there is a consolidated invoice and there are 2 delivery notes that are being combined for this invoice. The invoice # is 6016186004
    For DN#   6073107044 there is a VICS BOL that was passed back that is = 04000000000016146 
                   6073107045 there is a VICS BOL that was passed back that is = 04000000000016023
    and he wants to know how the program selects which VICS BOL fields in IDOC.  He gave me to use IDOC #77122253 in quality system for testing.
    In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
    If so then what are the I need to give
    Output application    (is it V1 or MR ?)       
    Output type    ??

    hi ..
    Please refer below..
    for invoice ,  tables: VBRK and VBRP
    AND transaction codes : VF01 to 03.
    What are delivery notes ?
    after goods issue, we need to issues delivery note to customer.
    In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
    you need to go to VL70 or you can process with RSNAST00.
    Output application type : V2
    Output type : LD00
    Regards
    Venkat.. Ananth Technologies

  • Error Posting IDOC: need help in understanding the following error

    Hi ALL
    Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
    where SAP_050 is the RFC destination created to post IDOCs
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Your help is greatly appreciated.............Thank you!

    Hi Patrick,
      Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
    Also Refer this Note 747322
    Regards,
    Prakash

  • Error while executing a JDBC to Idoc scenario : No standard agreement found

    Hello SAP PI Gurus, 
    I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration. 
    <SAP:AdditionalText>No standard agreement found for ,
    BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
    While i test the configuration...i get an error in reciever agreement as mentioned above.
    Can you pls help me in resolving this issue.
    Regards,
    Ravi

    Hi,
        I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
    Thanks
    Priyanka

  • Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

    Hi Friends,
        I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
    The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
    I have noticed that 2 things .
    1.  E1ADRE1 field is NOT being sent by the ECC system .
    2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
    Has anybody faced this problem before ?
    I look forward to replies.
    Detailed error is given below.
    Regards,
    Ranjini.
    Customer could not be determined
    Message no. /SAPAPO/EDI010
    Diagnosis
    The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
    The section was not available in the processed IDoc.
    System Response
    The system cancels processing.
    Procedure
    Configure the EDI convertor in such a way that the corresponding section has a value.

    Hi Ranjini,
    Please look into the following
    1) Customer master data is fully maintained
    2) Customer number ranges are fully defined in customisation
    3) Customer address details are maintained
    4) Is there any special characters used while defining customer data or customer
    number like $, #,[ etc.,?
    5) Customer int models are active in SCM side prior to IDOC processing (including
    customer, demand, stocks etc)
    Please confirm your findings
    Regards
    R. Senthil Mareeswaran.

  • Error in creation of  PurOrd IDoc

    Hi All,
    I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG  but  when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
    What could be the possible problem?
    Highly appreciate any kind of help.
    Thanks in advance,
    Shweta
    PS: <b><REMOVED BY MODERATOR></b>
    Message was edited by:
            Alvaro Tejada Galindo

    Hi
    Check the Partner Profile in WE20 correctly
    also see the steps for it as per the doc
    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.
    Regards
    Anji

Maybe you are looking for