Version of EDI standard in control record of an IDOC

Hello All,
  I want to know from where the Version of EDI(in details tab of control record) is being picked from.
Thanks,
Rakesh.

Hello Amit,
  I checkd in WE30.I think release version is different from EDI version because for a vendor in the system the release is 46C whereas EDI version is V11.
Thanks,
Rakesh.

Similar Messages

  • "Receiver port not valid in control record"...idoc error

    Hi,
    The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
    Recently we upgraded from SAP 4.6 C to ERP 5.0.
    After upgrading we are getting a message as Port(HPLED) invalid in control record.
    I get an error message as  "receiver port HPLED  not valid in control record"...
    It is not able to find  the receiver port & hence cannot create the MM.
    We checked all the config and compared with Test and production and we could not find any noticable change.
    Did anyone come across any infor on this?
    Your valubale reply is really very important for me.
    Pls reply.
    Regards,
    Pri

    Hey Ramesh,
    I've already done the WE57 setting.
    You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
    For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
    I've done all the config and have tried all the things in both the systems but somehow nothing is working.
    That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
    Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
    In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
    Regards
    Abhishek Sahi

  • Passing Control Record Data in IDOC to R/3 3.1i system

    Hi,
    We have PI 7.0.9 installed in-house and are currently attemptng to point to an R/3 3.1i system (we are in the process of upgrading to ECC5).
    When I enable the check-box to "Apply Control Record Values from Payload" in the receiver comm. channel for the IDOC adapter, it ignores the directive.
    If I look at the Payload in the XML Message in the call to the IDOC adapter, the fields are all filled - however the IDoc adapter simply builds its own values when sending to the back-end. The only difference to idocs for newer SAP systems is we use EDI_DC rather than EDI_DC40.
    Does anyone have any knowledge of this problem and a solution?
    Thanks
    Brian

    Hi Brian,
    About "Apply Control Record Values from Payload"
    If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
    If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
    If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values
    If in the receiver Communication Channel, you do NOT choose option "Apply Record control value from Payload", then EDI_DC40 will contain the values mapped during Mapping in Message Monitoring and SXMB_MONI - Response Payload, but when the IDOC is sent out , control record is filled with the value from the SLD
    If you are looking for, where to find the place where the logical system name for the XI system is defined, it can seen in 2 places....IN transaction SALE on XI, under "Basic Settings --> Logical Systems --> Assign Logical System to Client"...double click on the client no you want to check for...
    Also it can be seen in the SLD in the corresponding business system details.
    Do you want this value as the SNDPRN in the control record ? then you need not do anyhting
    Also take a look at these links,
    http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Also have a look at this thread...
    Re: SLD - Logical System Management
    I hope it helps....
    Regards,
    Abhy

  • Multiple control records in inbound idoc FM

    HI, 
         I have one basic doubt.
    when we write
    LOOP AT idoc_contrl
    LOOP AT idoc_data where docnum = idoc_contrl-docnum.
    endloop.
    endloop.
    does it mean there can be multiple idocs being processed with single inbound fm call.
    where do we controll whether inbound fm is called for every new idoc or there will be collective processing.
    Regards,

    Mass Processing of IDOC's is possible but not in all the cases. Refer to the given below Link:
    http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a670f507d11d18ee90000e8366fc2/content.htm
    http://help.sap.com/saphelp_me52/helpdata/EN/5f/45f93b4139b478e10000000a11402f/content.htm
    As far as Coding block you mentioned, I believe the same would be fired for each & every IDOC.

  • Control record mapping in IDOC

    Hi All,
    I am doing File to IDOC scenario. In this I am using MBGMCR03. In EDI_DC40 segment I have mapped constants to the sender n receiver port, partner frofile etc. And in IDOC receiver adaptor i have selected take sender from payload. It is working fine.
    However when i will transport my scenario to quality , How am i going to change all these constants with the new names?
    is there any better way of doing it? Like my sender details will be automatically determined by PI system.
    Thanks,
    Atul

    Hi Atul,
    1.if i use full export for transporting SLD from DEV to QA,can i use the same tecnical systems and business systems in QA?
    Can T.S and B.S also get transported from DEV to QA?
    You can use same technical systems and Business systems.
    1. Go to Dev SLD and Export all your SWCV, Products, Technical and Business Systems. This is nothing but saving of the SLD objects as a CIM file on your local machine. You would also need to export the Technical And Business System poitning to your XI integration server .
    2. Go to the QA SLD and then import these objects exported in Step 1 in QA SLD
    3. Now, create the QA Tech and Business Systems in the QA SLD
    4. Go to the Dev Business systems imported on the QS SLD and you will have an option Transport Targets. In this map the Source Business System to the Target Business Systems.
    Make sure that all Dev Business Systems have the correspodning Transport Targets for the QA Business SYstems
    5. Now if you import the ID objects in QA , the business systems name will be renamed automatically.
    2.In such case how to define business systems groups and transport targets?
    You need to create Transport Groups on your QA SLD. One for Dev and One for QA. You can create Transport Groups only for Integration Server Business Systems.
    And this is why you would need to export the Dev XI technical System and Business System from the SLD of Dev and Import it into the QA SLD.
    2. Create the transport groups and then assign all Dev Business Systems to Dev Group, all QA Business Systems to QA group and then create the transport targets.
    You use the Option related Integration server in the Business Systems to assign a Business System to a Group.
    Refer
    Problem regarding xi transport
    How to handle SLD for Tranporting Dev to Quality ser
    https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
    Overview of Transition from Dev to QA in XI
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
    Thanks,
    Satya Kumar
    Reward if it is useful..

  • Cannot map control record values from payload w/XSLT after SP13 upgrade

    Hi!
    Since we upgraded to SP13, the mapping of control record values form the XML payload to the IDOC control record (File->XI->IDOC scenario) no longer works if the mapping is done via XSLT. It works if the XI graphical mapper is used. The XSLT used is the same pre and post upgrade, but worked fine previously.
    [ Apply Control Record Values from Payload is checked in the IDOC adapter comm channel. ]
    Has anyone else experienced this? Am looking for any inspiration
    Cheers
    Duncan

    Are you sure the xslt file is still there?
    Maybe some non-compliance was corrected in later SP and your XSLT was using that non-compliance.
    If you post the XSLT we could try to point out any possible errors.
    Regards,
    Henrique.

  • Passing Idoc Control Record information  to JMS header

    Hi All,
    We have a requirement where we need to pass the 'MESCOD' and 'MESFCT" in the EDIDC_40 - Control record for the idoc to the Header of a JMS message.
    Basically we are trying to pass IDOC Control segment to the JMS header.
    I was looking at the options we have in the JMS adapter, and i am not sure how can this be achieved.
    Would appreciate any info on how this can be done.
    Thanks,
    Karthik

    Hi Karthik,
    As suggested by Ravi, you can hardcode this values in XI mapping before pushing data to JMS.
    Otherway round would be...check for User Exit where you can populate EDIDC_40 with MESCOD and MESFCT.
    Nilesh

  • Changing IDOC control record by XSL Mapping

    Hi,
    I am using scenario: legacy -> XI -> R/3.
    In the first step I am mapping XML -> IDOC. I have to map the field "SERIAL" in idoc control record in EDI_DC40 (idoc control record structure) with a constant. When I view the message in XI monitor. I cannot see the change and that field is not visible as before.
    Any suggestions would be highly appreciated !
    Regards,
    Faiq

    Hi,
    If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
    MESCOD
       MESCFT
       TEST
       EXPRSS
       STD
       STDVRS
       STDMES
       SNDSAD
       SNDLAD
       RCVSAD
       RCVLAD
       REFINT
       REFGRP
       REFMES
       STATUS
       DIRECT
       OUTMOD
       CREDAT
       CRETIM
    You can change the contents of only above  fields by using a mapping and getting it replected in the SAP System.
    Regards,
    Bhavesh

  • BADI to Change control record from idoc

    I’m trying to use the BADI IDOC_CREATION_CHECK to change the control record from the idoc but im not able to do it because the parameter IDOC_CONTROL is an importing parameter not a changing parameter, I’ve tried to use the BADI IDOC_DATA_MAPPER but I this case I’m just able to change the data record, should I use another BADI?
    Regards
    Luis Constantino.

    hi.
    have you tried ABI_IDOC_PROC_MODIF?
    i did not read much thru the documentation...
    i hope this helps.

  • Passing control records to Idoc

    Hi,
    how can we pass control record data to Idoc?can we do that in mapping(GUI) in XI ,lets say if I am doing <b>file to Idoc</b> scenario.I know we can disable the control record field and use apply from payload.my concern is if we don't use apply from payload.
    I have read in SDN XI takes from sender or reciever business systems as they are  related to Logical systems(ref link:XI IDoc  control record data source?) ,does it mean that we don't map these cotrol record fileds in the mapping(GUI)?
    and also please tell me how XI can pass data from flat file to a particular IDOC?
    thank you.

    hi,
    have a look at blog to see what is being filled and how:
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    you can also check my book in which I describe IDOC scenario configurations 
    <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>

  • BADI/Exit: Changing IDoc Control Record

    HI,
    do you know a way to modify the IDoc Control Record for MASTERDATA IDocs like CREMAS/DEBMAS/ etc ?
    there are a lot of IDOC Badis and Exit´s but without changing the EDIDC.
    any ideas ?
    Regards,
    Gordon

    Hi Gordon,
    Did you find an answer to your question? I have the same issue and am looking for a BADI or user-exit that will allow me to change the IDOC control record.
    Thanks,
    Uma

  • EA608 EDI: Sender partner number in control record is default

    We have created some KU partners in WE20 for sending billing documents to the SD bill-to partner but is running into an output error EA608 (EDI: Sender partner number in control record is default) on the billing document when trying to create IDOC's.
    Settings on partner:
    Partner: 12345
    Partner type: KU
    Partner function: BP
    Message type: INVOIC
    Application: V3 : Billing        
    Output type: ZEDI : US EDI Invoice
    Process code: SD09 : INVOIC: Invoic
    EDI Standard         X  
    Message type         810        
    Version              004010     
    Any idea to what the problem is?
    BR
    Joergen

    Hi Joergen,
    we also have similar problem to send out ordrsp. Could you tell me how to solve this problem as I saw tht this problem of yours has been answered.
    Thanks inadvance for your reply,
    Lily

  • EDI: Field REFINT in control record

    I am trying to send orders.orders05 idoc from ecc to xi
    the message that I get in we02 in ECC is
    EDI: Field REFINT in control record with value 'T080902134731A ' is invalid
    Does somebody knows where this field is configured ?
    when I edited this idoc in we02 and erased this value the process was sucessfuly
    but when I try using we19 it assigns this value automatically
    thx
    Shai

    hi
    it depends on use
    As a reference, this field contains the number of the interchange file, as entered in the EDI standards.
    An interchange file can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
    either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
    or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.
    cheers

  • Partner determination in control record for EDI

    Hi all,
        I have a custom EDI output which goes into the delivery.  However this EDI output is not picking the correct partner.
    The sales order with 2 plants would create 2 deliveries.   First delivery is created for plant A121 while second delivery is created for plant A710.   However, the vendor partner is not picked up correctly for plant A121 in the first delivery.  LIkewise the second delivery.  When the sales order has same plants, it create 1 delivery.  This comes out with correct partner.
      My question is:  How is the partner determined in EDI control record before the delivery is created ?
    In Partner Profile, WE20, there are 3 defined partners (100 LI, 200 LI, 300 LI).  For plant A121, the partner would be vendor 200.
    Thanks
    Joyce

    Hi Vinod,
       Thanks for your suggestion.  I have condiiton record for this EDI which is plant and it would list the partner.  Somehow, it seems the plant is not picked up correctly when there are a few plants in the sales order.   Becasue the partner is not picked up correctly, it seems to affect other output types that are plant-based.
        Initially the all output for EDI works fine.  There have been recent changes made to split delivery by plant which is fine  Output is one that are having issues.
       Have you any other suggestions ?  I will continue to look at the program  you suggested.
    thank you.\
    Joyce
    Edited by: Joyce Chan on Mar 17, 2010 8:31 PM

  • EDI: Sender partner number in control record is default

    Hello!
    Another problem... in SUS - MM, Plan Driven Procurement
    I try to send PO from MM to SUS. But in the messages I get following
    error: "EDI: Sender partner number in control record is default"
    Message no. EA608
    SAP Note Number: 111342 doesn't help
    the logical systems are maintained!
    Any idea about this problem?
    Kind regards,
    Barbara

    If this is in regards to an ASN:  Check to see if this customer buys several divisions or is relevant for one division only.  In our instance of SAP, we found that it didn’t go to the Customer Master division setup relevant  to the division on the ASN to get the ACCT AT CUST field, it went to the first in the sequence of divisions and got that ACCT AT CUST field information.  That information was not filled out as it was a new division and that is what kept the output from happening.    For example:   we had divison 02, 04, 06 and 08.   We added division 03 and extended all customers to division 03.     Those customers that only bought division 04 just stopped sending ASNS.    The ASN was for division 04, but SAP logic was retrieving the ACCT AT CUST information (SALES tab, not CORRESPONDENCE tab) for divison 03, but we didn’t have that filled out. 
    Hope that helps.  

Maybe you are looking for