Skip to Content
author's profile photo Former Member
Former Member

IDOC-FILE scenario

Hi all,

Can anybody send IDOC-File scenario for Purchase order(PO)numbers ...

from SAP SRM to XML file ...

can anybody have any document or any steps..

Please help me......

Thanks in advance

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 06, 2006 at 11:11 PM

    Create Data Types

    *****************

    Create your Sender Data type -- DT_SRM

    Create your Receiver Data Type -- DT_File

    Create Message Types

    *****************

    MT_SRM(DT_SRM)

    MT_File(DT_File)

    Create the Message Interface

    *****************************

    MI_SRM(MT_SRM) Outbound & Asynchronous

    MI_File(MT_File) Inbound & Asynchronous

    Create the Message Mapping

    **************************

    MM_SRM2File ---(MT_SRM to MT_File)

    -


    *********************

    Log on to SRM System

    *********************

    Transaction /nSPROXY

    Create your Proxy

    -


    XI Directory

    ************

    Create Sender Agreement

    Create Receiver Agreement (FILE Receiver)

    Create Interface Determination

    Create Receiver Determination (Refer your Receiver Agreement and Interface Determination)

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 07, 2006 at 12:43 AM

    HI ,

    As your scenario is Idoc->XI->File Scenario..

    It is not required to have source data type or message interface. Idoc itself acts an interface. And message type is nothing but idoc structure itself. You need to import the idoc into Repository.

    Check this blog as a reference -Idoc to FIle scenario

    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

    And in similar lines you need to develop an interface.

    Coming to your exact scenario-

    Also for SRM systems , there are already predelivered content availale from SAP .It includes all the Repository objects. So you need to just do the configuration. Just check is there any objects are delivered for your current scenario.If not you can develop, as mentioned in my first part of the reply

    Check this thread-SRM->XI

    SRM XI scenario

    XML PO Transfer To Vendor in SRM 5.0 via NW2004S/PI 7.0

    Hope this helps,

    Regards,

    Moorthy

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      <i>U told It is not required to have source data type or message interface..why??</i>

      >>> Yes, it is not required if you are using Idoc/RFCs/BAPIs. Because we are going to import the structure into Repository. so this it will act as a Message interface/message type.

      Is your source message format is other than above, then Data Type etc is required.

      Now coming to Mapping etc-

      If you are using Idoc etc , your source message type will be Idoc which you have imported from the SAP Application systems.And target depends on the requirement.

      And the mapping type is chosen based on the complexity and the requierement. So, if it is complex, then you can go with Java/XSLT mapping. But it is prefered to use Message Mapping(Graphical-Drag/drop) .

      Did you check, is there any standard delivered content exist in the SRM component ? If not you need to do mapping etc ..otherwise you can use existing one..

      Regards,

      Moorthy

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.