IDOC - Field conversion

Hi All,
I have created IDOC conversion rules for customer master data under segment E1KNA1M in BD79.
One of the conversion rule is to add a "P" in front of the customer numbers in the target client. For example - source client: cust num = 1234567, target client: cust num = P1234567
How do I add this conversion rule? Which rule type should I use?
Appreciate any help!
Thanks,
Charlene

Hi Charlene,
You can create a new conversion routine and associate it to the field kunnr.
For example, to create conversion routine ZEDG, create the following functions:
FUNCTION conversion_exit_zedga_input.
*"*"Interface local:
*"  IMPORTING
*"     REFERENCE(INPUT) TYPE  KUNNR
*"  EXPORTING
*"     REFERENCE(OUTPUT) TYPE  KUNNR
  DATA: l_input TYPE kunnr.
  l_input = input.
  replace 'P' in l_input WITH '0'.
  CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input  = l_input
    IMPORTING
      output = output.
ENDFUNCTION.
FUNCTION conversion_exit_zedga_output.
*"*"Interface local:
*"  IMPORTING
*"     REFERENCE(INPUT) TYPE  KUNNR
*"  EXPORTING
*"     REFERENCE(OUTPUT) TYPE  KUNNR
  CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
    EXPORTING
      input  = input
    IMPORTING
      output = output.
  CONCATENATE 'P' output INTO output.
ENDFUNCTION.

Similar Messages

  • Are idoc fields case sensitive?

    Hello, there has been an error during idoc processing. The trading partner field was filled in lowercase and this is bringing me error      Message no. FB279  ' Company dp0017 is not defined'. The other idocs had DP0017 filled in and were processed fine.
    Any input on this? thx.
    Edited by: Antish  Awootar on Jun 7, 2011 8:02 AM

    Hi Antish,
    It actually depends on the value that is stored in the IDOC, if the IDOC has company code in lower case then that is exactly how it will be used in the program for all purpose and no automatic conversion is applied. The below message is thrown in the FM - FI_COMPANY_CHECK This FM will look up the table T880 - If you check the entry in this table will be DP0017 and not dp0017. Hence it is throwing the error message.
    If your question is it works fine when i try in SE37 with the FM "FI_COMPANY_CHECK" or if i input "dp0017" in  WE19 or in SE11 against T880, then the reason for that is a conversion is applied automatically and it is changed to DP0017.
    To answer your question "Are idoc fields case sensitive?", it depends on the context, does it retain the case when it is filled in, yes it does.
    Regards,
    Chen
    Edited by: Chen K V on Jun 7, 2011 4:10 PM

  • IDOC inbound conversion Rules

    Hi to all,
    I'm Implementing an Inbound Interface for Cost Centers using idoc message COSMAS and IDOC type COSMAS01.
    I want to modify IDOC data changing the cost center code by another one stored locally in a param table (Z*). 
    I think the best way to do this is by creating a conversion rule in BD72 than maintain and assign to Message type. The problem is that i have to select data from the Z* Table i need two parameters from the IDOC(LogicalSystem and cost center). How can I create a custom conversion routine or something to get this data from the Z table into the IDOC field (KOSTL).
    The conversion exits only have one import parameter and one export parameter.
    Do anyone had one problem like this?
    Thanks in advance to all.

    Hi,
    Please check the documentation in WE60 tcode and see if the fields are required to be passed...
    Regards,
    Nagaraj

  • IDoc fields, when empty

    Hi all,
    I have a requirement to send IDoc to external system. When there is no corresponding data, IDoc fields are not filling.
    I need to fill blant value to the IDoc fields and send to external system.
    I don't have permissions to change the standard code.
    My doubt is: Can I fill the empty field in conversions or in any other place, other than coding? is BD64 useful to fill the IDoc field?
    Thanks in Adv,
    Moderator message - Duplicate post locked
    Edited by: Rob Burbank on Dec 9, 2009 9:51 AM

    Hi Kanagaraja,
    I am sending the IDoc to PI system using ALE. The IDoc is CLFMAS. when ever a Material Master IDoc generated, subsequent CLFMAS will be generated. The IDoc filling logic is actually in Master_IDoc_MATMAS FM. I think I don't have permissions to change the coding, since its a standard IDoc and some other systems also using the same IDoc generation logic.

  • How to map empty IDoc field

    Hi everybody!
    I want to map the value of a source field through a <b>FixValues</b> function to the target field. Unfortunately this is an IDoc field which sometimes doesn't even exist (i. e. it's not just empty - it's not even there). In this case the <b>FixValues</b> function suppresses the output, and there is <i>no</i> output - not even the <i>default</i> value of <b>FixValues</b>. However, the requirement is that I always have to generate a default output - even if the input field is empty/missing.
    Ony ideas how this could be done?
    Regards, Joerg

    Hi Himadri!
    Thanks for the quick response! I tried to create such a que. However, it doesn't remove the SUPPRESS from the queue. Here's the code:
    // Two input params: src[] and def[]
    // src contains the input queue (with SUPPRESS values)
    // dst contains (hopefully) only one value - the default value
    int n=src.length;
    result.clear();
    if (n==0) {
      result.addValue(def[0]);
    else {
      for (int i=0; i<n; i++) {
        if (src<i>.equals(ResultList.SUPPRESS)) {
          result.addValue(def[0]);
        else {
          result.addValue(src<i>);
    What am I doing wrong?
    Regards, Joerg

  • How to map Idoc fields with external file

    Hi All,
    How to map Idoc fields with external file.
    I want to check the settings where Idoc fields are mapped with external file.
    Thanks in advance.
    Regards,
    Govind.

    If you have configured a fileport where on trigger of IDOC you are creating the file, you can look at the message type documentation and get the offset values for each field in each segment

  • To Handle Special Characters(Guideu0099 ) in MATMAS IDOC fields

    Need to handle special characters like Guide™, as an attached  superscript in MATMAS02/05 IDOC field . The field name is TDLINE in E1MTXLM segment.
    As a trial run when these special characters are pasted in the TDLINE field, it throws an error that "the input field contains prohibited characters"
    Please let me know if there is any workaround for this.

    hi
    good
    go through these links, i hope these ll help you to solve your problem.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAGTFADMLO/CAGTFADMLO.pdf
    http://www.erphome.net/wdb/upload/forum14_f_2908.doc
    thanks
    mrutyun^

  • Mapping the IDOC fields for Inbound PO

    Hi,
    I am trying to map the fields for PO for IDOC type ORDER05, but unable to do so for the following IDOC fields in segments.
    Document Date
    Vendor
    Account Assignment Category
    Delivery Date
    Requirement No.
    Requisitioner
    Purchase Requisition
    Preq Item No.
    Outline Agreement
    Outline Agreement No.
    What fields in the IDOC match these in SAP R/3.
    Thanks,
    Randy.

    Hi Did you manage to get this IDoc working? I'm having the same problem with the mapping and the documentation is really bad.
    Thanks.

  • Missing IDOC field in XML after IDOC reimported in ESR

    Hi Guys,
    I have just reimported my IDOC in ESR wherein an additional field is added.
    However, when I test a message, the IDOC field is missing in the XML payload upon entering PI even though I have entered a value in the IDOC.
    Flow:
    SAP ECC > PI
    I have also already updated my message mapping. I'm not sure if I have missed any steps after importing the IDOC in ESR.
    Could you please help me on this issue?
    I'm using ICO by the way.
    Thanks and Regards,
    Neil

    Hi Neil,
    As Shanthi said you need to update metadata but since you are using ICO you need to do it in NWA.
    NWA->SOA->Monitoring->IDOC Adapter Monitoring
    Regards,
    Praveen.

  • ALE: mapping IDoc fields to change document fields - TBD22 for ADRMAS iDoc

    Hi,
    I am currently try to find a table or way to extract the information of the TBD22 table (ALE: mapping IDoc fields to change document fields) for the iDocs/ Message Types:
    ADRMAS
    INTERNAL_ORDER
    PROJECT
    I am looking for a table that shows me to which SAP R/3 tables and fields the segments and fields of the above mentioned messages will be mapped to.
    When I add one of the above mentioned message types to the table TBD22 selection criteria I always receive the notification: "No table entries found for specific key".
    Could anybody determine Which table I have to use or why I cannot extract this information?
    Thanks in advance!
    Best regards

    Hi,
       Since we can not map the target IDOC when any of the field changes using nodefunctions , you can write UDF and check the same i.e if field1 changes or field2 changes or field3 changes then trigger new IDoc. This is one of the options that you can try...please try it once.
    Regards
    Priyanka

  • Removing unused IDOC fields

    Hi All ,
    Removing unused IDOC fields using an XSLT editor is possible? If so, we can import them the IDOC as XSD correct? What will be the immediate benefit of such a tweak?
    Thanks
    XA

    Hi,
    When the Idoc definition itself is huge enough to cause the XI message mapping
    editor to consume a lot of memory and at times even end up giving an Out of Memory error, only while displaying
    the mapping. SAP recommends that a Reduced XSD feature provided by the Integration repository should be
    used in place of actual Idoc structure to avoid memory issues.
    If it is imported as an IDoc and used thereafter directly in mapping still results into an XSD of
    around more than 3 MB and causes trouble during opening of the mapping and also gives errors during mapping
    edit leaving the work in a vulnerable state.
    To overcome issues in the design editor to a considerable extent by using Reduced XSDs.
    you can find more details in Note # 709400.
    Regards,
    Harish

  • Quantity field conversion problem in SAP script

    Hi experts,
    I have problem with sap script quantity field conversion.
    In purchase order the actual value of field( MDPM-ERFMG) is 3,500.
    But in Print preview it is showing only 3.5
    Any one Please help me in this problem
    thanks in advance
    murali

    Hello,
    check this:
    Number of Decimal Places
    A program symbol of one of the data types DEC, QUAN, and FLTP can contain decimal place data. Use the option below to override the Dictionary definition for the number of decimal places for the formatting of this symbol value.
    Syntax
    &symbol(.N)&
    The EKPO-MENGE field contains the value 1234.56. The Dictionary definition specifies 3 decimal places and an output length of 17.
    &EKPO-MENGE& -> 1,234.560
    &EKPO-MENGE(.1) -> 1,234.6
    &EKPO-MENGE&(.4) -> 1,234.5600
    &EKPO-MENGE&(.0) -> 1,235
    REgards,
    Vasanth

  • IDOC field to SAP data base field

    Is there any way to find out the field names of SAP database table associated with the IDOC fields??
    I would appreciate for any types of help in this.
    Pranav

    Hi,
    To find inbound FM, you can go to transaction WE57. Go to selection -> by contents (menu), select basic type and enter the corresponding IDoc type. The system will display the corresponding FM(s).
    You can also go to transaction WE64 to find the inbound and outbound FM(s).
    Regards,
    Ferry Lianto

  • Item  Field  Conversion

    Hi,
       can any body  give me a brief introduction about Item  Field  Conversion.. When we need to go for this.. and  how can we do this.. please suggest me..
    Thanks
    babu

    Hi,
    Itemfield Conversion :
    Adds functions to SAP NetWeaver for converting data to and from XML. It can process unstructured, semi-structured, and structured data. The Conversion Agent can be called using an adapter module in the Adapter Framework of SAP Exchange Infrastructure.
    You can find SAP Conversion Agent by Itemfield in the SAP Software Distribution Center on SAP Service Marketplace at service.sap.com/swdc.
    A partnership with Itemfield aims to introduce complex data transformation capabilities to SAP's offering. But the partners will face significant integration and support challenges.
    On 5 December 2005, Itemfield, a provider of data transformation software, announced a partnership agreement with SAP. Under the terms of the agreement, SAP will embed the Itemfield Conversion Agent for SAP NetWeaver in its NetWeaver suite. This is an adaptation of Itemfield’s ContentMaster technology that is designed to plug into the latest release of NetWeaver Exchange Infrastructure (XI), SAP’s application integration platform.
    The addition of SAP to the list of Itemfield partners — which includes IBM, Informatica, Oracle, Microsoft, webMethods and Software AG — moves the company much closer to its goal of positioning ContentMaster as the de facto standard for independent data transformation technology. SAP's NetWeaver XI is achieving growing adoption, with 1,600 installed customers to date, but has somewhat limited transformation features. This combination of factors gives Itemfield an opportunity to substantially boost its own customer base. However, success will require a robust marketing effort, and the ability to scale up quickly to support a growing number of global customers.
    The partnership will also help SAP make up for the lack of complex data transformation capabilities in XI — a limitation that SAP customers have had to work around, either by developing custom code or by stretching the use of the XI business process management facility. The Itemfield Conversion Agent for SAP NetWeaver provides XI users with a proven and powerful option to address even the most complex unstructured, semistructured and structured data transformation issues. However, SAP will face a major challenge in effectively supporting, and keeping in a coherent state of integration, the growing number of third-party products in the XI platform (which include iWay and Seeburger adapters, IDS Scheer process-modeling tools, and now Itemfield's technology).
    XI customers with complex data transformation requirements: Evaluate whether the Itemfield Conversion Agent for SAP NetWeaver meets your technological and financial needs. Demand contractual guarantees of adequate long-term support from SAP (which offers full support for the product) before making a commitment.
    XI customers adopting XI in conjunction with other Itemfield partners' platforms: Consider using Itemfield as a "unified" transformation utility across multiple integration products (but remember that the Itemfield Conversion Agent for SAP NetWeaver is an additional-cost item, subject to the controversial XI volume-based pricing schema).
    I hope this will clarify you.
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Date field conversion

    hi gurus! can someone give me a  tip on a date field conversion.
    I have a field that comes YYYYMMDD but i want to convert to DD.MM.YYYY
    Can someone help me on this
    Thk, Regards

    REPORT  Z_82235_TEST4                           .
    data:  date1(8) type c,
           date2(10) type c.
           date1 = 'YYYYMMDD'.
    CONCATENATE date1+6(2) date1+4(2) date1(4) INTO date2 separated by '.'.
    you pass your date to date1 in place of 'yyyymmdd' and you will gate ur desired output on date2.

Maybe you are looking for