Creating SDATA value of IDOC

Hi
        I am trying to create an IDOC in MII 12.1. IDOC is having a tag known as SDATA where we put all the values. For each field in SAP there is a column length. If our value for the field is less than the maximum length of the column we put a space for rest of the length. I am adding this space in MII using some string method which takes more time. Does anyone have any idea of adding this space more smartly. Please let me know
Thanks in advance
Shaji

I have used xsl to do this.
[Lazy Fixed Width Using xsl|Lazy Fixed Width Using xsl]

Similar Messages

  • Create material number in Idoc

    Hi experts,
                   I am new to create Idoc and ale.so please help me with basic steps.
                   I have two servers ECC6.0 and 4.7.    I want to send the details like (mbrsh,mtart.maktx,meins) from 4.7 then i want to create the material number in ECC6.0 and i want to get the material number in sap4.7..for this what are all the steps i need to follow....from creation of function module to idoc....everything i need.....what parameters can i use in function module......help me please..

    Hi,
    Basic Type:
    Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
    Segments:
    Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
    Steps in creating Segments:
    T.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 and Go back.
    Go to Edit -> Set Release.
    Repeat the steps to create more segments.
    IDOC TYPE:
    Business data is exchanged with an external system using the IDoc Interface.
    IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
    Steps in creating IDoc Type:
    T.Code WE30 to create IDoc Type.
    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.
    Message Type:
    Steps in Creating Message Type:
    T.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:
    T.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.
    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://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • Create subordinate values for Characteristics

    Hi ,
    I am using  BAPI to create the characteristic
        CALL FUNCTION 'BAPI_CHARACT_CREATE'
        EXPORTING
        charactdetail = gs_charactdetail
        keydate = gv_keydate
        TABLES
        charactdescr = gt_charactdescr
        charactvaluesnum = gt_charactvaluesnum
        charactvalueschar = gt_charactvalueschar
        charactvaluescurr = gt_charactvaluescurr
        charactvaluesdescr = gt_charactvaluesdescr
        charactreferences = gt_charactreferences
        charactrestrictions = gt_charactrestrictions
        return = gt_return .
    But  there is no way which i can create suboridinate values  for (charactvalueschar) . Please let me know how can i create soubordinate values for char values
    Reagrds
    Ramesh

    describe your problem.
    It does not really matter if you use standard batch input or IDOC, both will lead to the same result.
    However, object 0150 and CLFMAS are 2 different things.
    0150 is characteristics while CLFMAS is classification
    if you want classify with standard batch input then you should use 0130 instead of 0150.

  • Short Dump While creating a Value Driver Tree

    Hi all,
    I am trying to create a value driver tree in CPM. i am on SEM verion 3.1b. I am able to create the value driver tree but when i goto the graphical view it generates a ABAP short dump. does anybody have any idea on this

    hi srini,
           Elaborate it clearly .
    Regards ,
    Muneeh Gitta.

  • Problems in creating a Value Contract

    Hi,
    I'm trying to create a value contract using VA41.
    The process succeeds for one sales organization, but for another sales organization, I am getting a line in the document incompletion log, saying G/L account data is missing. This is despite the fact that a G/L account IS assigned to this sales organization in VKOA. Even when doubleclicking the error message, and getting to the Analysis Account Determination, it is clearly seen that the system did find a G/L account!
    After getting deeper into this, I found that the problem is caused by the item category of the contract line item, which has Revenue Recognition category B (Service-related revenue recognition). If I change this value to blank or a different value in the item category definition (VOV7), then I am able to add the line and save the contract.
    The question is whether there is a place where this sales organization (or the company code above it) is defined not to be able to accept lines with Revenue Recognition B? Or maybe I am misunderstanding this whole thing, and the problem is of a different kind?
    Thanks in advance for your help,
    Amit

    Hi Sri,
    Thanks for the quick response.
    The item category group is not NORM but our company's own item category group - YNOR.
    This is not the issue, as this item category group is assigned to the material also in the sales organization that works...

  • ERROR IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

    I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
    IF I proceess the Idoc in background each time error message comes
    FIELD kuwev-kunnr(ship to party)is not an input field.
    but if i run in foreground in debugging mode,sales order is getting created..
    please suggest something.

    If thats not working..
    try BAPI_SALESORDER_CREATEFROMDAT2
    If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

  • Throw Information message for sale order created with value less that 5$

    Hi all,
            I am basically an abaper, I have got a requirement in SD. The requirement is any sales order created with value less that 5$, should be prompted with an error message saying the minimum order value should be more than 5$. Could any one help me on this.
    Thanks in advance,
    shiv

    userexit_save_document_prepare,main program - sapmv45a, issue an error message if your document value is less than 5$ (VBAK-NETWR) but check if your order has any non-rejected item, I would not issue this message if all items are rejected:
    loop at xvbap where updkz ne 'D' and abgru = ' '.
      exit.
    endloop.
    if sy-subrc = 0.  "-you have at least one non-rejected, non-deleted item.
    NOTE: sapmv45a works NOT only for orders, so please check document types in your logic which are relevant to your messge only (VBAK-VBTYP and/or VBAK-AUART).

  • How to create FI Document in Idoc.....

    Hi Abapers,
    I hve small doubt that
    how to create FI Document in Idoc.....?????s
    I was new to the Idoc creation .......
    can u give me step by step process..............
    Thanks & Regard
    Ravi Sarma

    Hi Rahul,
    As per my understanding you are loking for creating the IDOC per FI document.
    So if in case the multiple rows have retrived from Oracle Join query then Multiple IDOCs to be created. Per row one IDOC.
    You can do this just by changing the Occurance of IDOC
    Export the XSD structure of imported IDOC from IR and modify the occurance of IDOC field as below example
    <xsd:element name="IDOC" type="ZTEST_IDOC.ZIDOC" maxOccurs="unbounded" />
    Then Import the xsd file as external defination and use it directly in mapping.
    It will create the multiple idocs  with mapping Row field of Oracle structure to IDOC field
    Thanks
    Swarup

  • How to create a value only  article and process it

    pls tell me how to create a value only article,  group article and
    hierarchy article and process the same in Is-retail

    Hi,
    Pl use the following link:
    http://help.sap.com/saphelp_ides/helpdata/en/fa/6a376542ef11d2a64b00104b57eaa3/frameset.htm
    Regards,
    S.V.ManiKumaar

  • Create huge number of IDOC

    Hi All,
    I am asked to create a file to IDOC scenario in PI. The problem is, the file will have around 200,000 records, 96MB. That means I have to get the 200,000 records from the file and create 200,000 PO IDOC at once. I know this is not possible. Does any one have this experience? How did you solve the problem?
    Thanks a lot!
    Charles

    Few ways to implement this.
    Though the file has huge number of records, you can tweak  or control the number of idocs creating at the reciever side.
    Refer michal blog for edit the occurence of target idoc structure to sent the number of idocs as per the need.
    The specified item was not found.
    https://wiki.sdn.sap.com/wiki/display/XI/File%20to%20Multiple%20IDOC%20Splitting%20without%20BPM
    if your sender side is flat file then in the content conversion you set the parameter Recordsets per message like 100 or so.. so that you create 100 idocs each time from the sender message structure. Refer SDN forum for fcc parameters and sender fcc adapter scenario.
    Refer this thread
    Recordsets per Message in File adapter

  • Prevent the Output Message when creating PO from inbound IDOC

    Hi SAP Gurus,
    In my project, I have to create PO from inbound IDOC (PORDCR) with a specific Document Type ('099').
    Requirement: These PO should not generate the output message while the others (Doc Type # '099') do.
    I have the Z fuction module which call BAPI_PO_CREATE for posting IDOC and it works fine.
    In the existing system, there are some set up that trigger the output message type for PO (output NEU) when using ME21 or ME22, as a result my PO created with output message.
    Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
    I'm new in MM and really need help!
    Thanks,
    Elaine.

    Hi Vinod,
    I really appreciate your anwer. I'm going to explore this with my functional consultant.
    Just like to have more questions:
    1. Is it easier if we change the existing condition table instead of creating a new routine?
    2. There are two forms for routine 101 (FORM KOBEV_101 and FORM KOBED_101). Can you explain to me why we need 2 here for what purpose of each form.
    3. In the debug mode by using WE19 to post inbound IDOC, I change the SY-SUBRC = 4 and PO created without output message. Is it the right direction? Anything else I need to pay attention to?
    Thanks again.
    Regards,
    Elaine.

  • How to create charasteristic value variable step by step please?

    How to create charasteristic value variable step by step please?
    I searched the previous threads it is not listed.
    I will assing points to only valuable information.
    York

    Hi Les,
    http://help.sap.com/saphelp_nw04/helpdata/en/ac/789b3c4d4d8d15e10000000a114084/content.htm
    In the left hand side of the query designer, find your char and under than there will be a button with text called Characteristic Value Variables. Right click this and choose New Variable. This will open the variable wizard. You need to follow the screen to define a technical name and description, the processing type, the user entry options and if the variable will accept single or multiple values, and also if you want to set a default value.
    Hope this helps...

  • I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

    I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
    What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
    My system is ECC5.0. Thanks.

    Hi, nagaraj
    this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
    In WE82, there are 5 records about Messagetype MATMAS:
         Message type   Basic type     Release
          MATMAS         MATMAS01        30A
          MATMAS         MATMAS02        30D
          MATMAS         MATMAS03        40A
          MATMAS         MATMAS04        46C
          MATMAS         MATMAS05        470
       I think it should be ok.
    In WE57, there 2 records are exist:
       FM_name                 BasicType       MessageType
      IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
      IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
    so I think all configurations should be ok.
    Message was edited by:
            liu bin

  • Do we need to create message interfaces for idocs and rfcs thatare imported

    do we need to create message interfaces for idocs and rfcs thatare imported
    from sap server
    in scenarios from sap system to file or vice versa
    i knew that we need not create message types
    do we also skip creating message interfaces

    hi,
    you create an abstract message interface for IDOC only if you want to use
    them in a BPM (integration process)
    for more about IDOCs 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>
    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>

  • Create order production from IDOC

    Hi!!! how create production order from IDOC INBOUND??... function... BAPI?? thanks...

    Hi
    welcome to SDN forum
    check this BAPi
    COXT_BAPI_ORDER_CREATE
    Regards
    Anji

Maybe you are looking for