Serialization field in control record

Hi Experts,
I have one requirement like this.While generating idocs in control record we get serialization number by combining system date and time.
But now my requirement is i have to change that serialisation field with required timestamp.Can we do this? If so can anyone explain me how to do that?
Wiating for your valuable replies.
Points will be rewarded.
Regards,
Swetha.

Hi Swetha,
check out the following links if they can be of any use for your requirement.
[http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm]
[http://help.sap.com/saphelp_45b/helpdata/en/b5/9c487cfc6f11d1bf5a0000e8a7386f/content.htm]
Regards,
Sekhar kalluru

Similar Messages

  • Serialisation field in control record in idocs

    Hi Experts,
    I have one requirement like this.While generating idocs in control record we get serialization number by combining system date and time.
    But now my requirement is i have to change that serialisation field with required timestamp.Can we do this? If so can anyone explain me how to do that?
    Wiating for your valuable replies.
    Points will be rewarded.
    Regards,
    Swetha.

    hi,
    Firstly check the open periods for the compnay code in OMSY...
    If its not open then try in the MMPV to open it...
    You can also open it in OB52..which is FI trasaction...it open/close the two periods consicutively...
    You can reopen the periods but its not recomended...you can use MMRV..for back posting allowed...
    or else check this
    goto SU3
    select user profile
    in parameter ID give MMPI_READ_NOTE , and in parameterr value enter todays yyyymmdd and save.
    and goto MMPI intialise the periods to present one at a strech.

  • 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

  • Port field is blank in Control record

    Hi Experts,
    I am sending the idoc from R3 to XI to R3, the idoc successfully came to R3 to XI and XI to R3, but in reciever r3 system when i check idoc control reocrd, the port field is blank.
    Can you please help me why it is blank.
    Kind Regards,
    Praveen.

    Hi,
       If you have chosen the "Apply control records from Payload" check box in Receiver IDOC adapter configuration, then you have to look at what value did you map the RCVPRT field in your message mapping.
    If "Apply Control recrds from payload" is not checked, then you have to re-check if your port configuration is properly done in IDX1 transaction in your XI box.
    Regards,
    Ravi

  • How to put data in MESCOD field of in IDOC Control Record ?

    We have a File->XI->IDOC scenario.
    Two different types of files have to been mapped to the  same IDOC (WMMBXY).
    We want to use the field MESCOD in order to differ idocs from one type file or the other.
    In the Message Mapping, I have the EDI_DC40 record dissabled, to permit that it is fulfilled by XI.
    How can I put information in MESCOD field?. Is the only solution to enable EDI_DC40 record ? (I don't like this solution because automatic fulfilled is lost ).
    I've seen that a Header Mapping exists in Receiver Agreement, but this is only available to Sender&Receiver.
    Thank you.
    Francisco.

    hi Francisco,
    take a look at this:
    http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
    section:
    The following table provides information about
    how the fields of the control record are filled by the
    receiver IDoc adapter.
    now you see which fileds are supplied by receiver idoc adapter
    then:
    If you have not set the Apply Control Record Values from
    Payload indicator in the receiver IDoc adapter, the
    fields are filled as follows:
    now you see which fields are taken from ID
    so enable EDI_DC40 and just fill MESCOD
    this will be much easier than any other routing
    (if such exists if you disable it)
    Regards,
    michal
    Regards,
    michal

  • Idoc control record DIRECT field mapping

    Hello,
    I have a file to idoc scenario where the receiver system is an external one.
    I have the necessity to set in the outbound idoc control record DIRECT = 1.
    The XI system is XI 3.0 SP 19 and I've set up the mapping of the idoc control record in the message mapping and selected Apply Control Record Values from Payload and Take receiver from Payload in the Receiver Communication Channel but the idoc is still generated with DIRECT = 2.
    In the documentation the field DIRECT is listed as one that will be filled using the message mapping if Apply Control Record Values from Payload is selected.
    How can I generate an idoc with DIRECT = 1?
    Regards,
    Elisa

    Hello Punit,
    I know that logically the right value should be 2 but the request of the receiver system is to have it as 1.
    They only elaborate the idoc they receive with DIRECT = 1 (outbound).
    In SAP documentation the field is listed as one that can be mapping with the message mapping but the idoc adapter is ignoring the mapping even when the Apply Control Record Values from Payload is selected.
    Regards,
    Elisa

  • Populating MESFCT and MESCOD in IDOC control record through XI.

    Hi Experts,
    I want to map only MESFCT and MESCOD fields to IDOC control record as i see help.sap.com and all forums this part in XI is very confusing, as mentioned in the below thread i disabled all the mandatory fields(which are in red color)  in the EDI_DC40 and mapped MEDCOD and MESFCT with constants and in IDOC receiver adapter (Communication channel) i have checked the option (Apply Control Record values from Payload) , now i can see both the values MEDCOD and MESFCT  in XI payload, however I'm unable to see them in the target (ECC 6.0) system
    Threads Used:
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    SAP Note : 728792
    Target System
    WE09
    IDOC control record structure.
    Under Typinfo tab:
    Message Varient : <Still Empty>
    Message Function : <Still Empty> not populated from XI payload.
    Any guess ??? will there be any configurations required from ECC point of view to populate these values from XI payload.
    Thanks in advance
    Kelli.

    You mentioned that the payload values are visible post mapping during runtime so ,
    Try to edit the IDoc adapter once again and ensure that
    you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter
    Activate the adapter and try again.

  • Mapping of Control records in file to idoc scenario

    Hi,
    In the mapping part of file to idoc scenario is it necessary to provide the exact control record details
    or will it pick what ever is mentioned ? Can any one please explain regarding the same?
    Many Thanks,
    Sharath

    hi,
    in case of apply control records from payload
    It is indeed very simple to do it and the feature is available from SP10. I have seen lot of posts on the forum for the same and that is the reason for this blog. We can manipulate the control record in the mapping editor and map the EDI_DC40 segment of Idoc as required. Most of the times we need to map only SNDPRN, RCVPRN, SNDPRT, RCVPRT for posting Idocs with appropriate partner profiles in SAP R/3 destination systems. We can disable the rest of the fields as shown below. We need to manually change the control record of idoc for populating partner profiles in the control records while dealing with non-sap sender system, which will be used by receiver SAP system for posting idocs with appropriate ALE configurations.
    check this blog
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    regards
    chandra

  • Message type is not populating in the Inbound idoc control record

    Hi,
    I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
    The settings which I have done in WEDI as follows:
    1. Created Idoc segments with necessary fields and released
    2. Created Idoc type for the segment type
    3. Created message type
    4. Assigned message type to basic type
    5. In the inbound processing settings,
       filled the ALE attributes with the Idoc function module name and input value '0'
    6. Assigned FM to basic type and message type
    7. Created process code and assigned the process code to message type
    Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
    Best Regards,
    Mallika

    Hi,     
    Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
    Thanks
    Rahul

  • File name in control record of Idoc

    Hello All,
    I have come across a requirement for File to IDOC scenario where File name picked from dynamic configuration is to be stored in control record of IDOC. As file name is more than 45 chars long, I need to use a long field.
    Can you I use ARCKEY, SNDLAD or RCVLAD fields or there is some restriction to use these fields, means will it impact something?
    Regards
    Prashant

    Hi Prashant,
    I understand that your requirement is to store name of picked up file in SAP system.
    Can you I use ARCKEY, SNDLAD or RCVLAD fields or there is some restriction to use these fields, means will it impact something?
    You can use them if you are sure that it would not affect routing routines and message processing in SAP ECC.
    Regards,
    Radek

  • How to fill plant in control record of an I-Doc , message type - INVOIC

    Hi All,
    Can any one tell me, how i can fill Plant in control record of an I-Doc, when i generate I-Doc through billing with message type INVOIC. The field (EDIDC-REFGRP) should be fillied with Plant.
    Regards,
    Suresh Patiapti.

    Hi,
    Which type of processing you are referring to (outbound/inbound) ? Which standard process code is used for idoc processing?
    Regards
    Vinod

  • Include segment in Control record of  idoc type PEXR2002 and PAYEXT

    Gurus
    This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
    The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
    We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
    Is it possible to add segement in control record for each payment method?.
    Thanks for your time and consideration
    Auroar

    It may depend on how the IDoc is created.
    From a file.
    Sent via a Remote Call.
    You would then need to code it for this Message type only.
    I would take a copy of the standard Function and change that. You would have greater control then.
    Why is the partner number wrong anyway. Can you not just create another partner profile(s).
    Message was edited by:
            Martin Shinks

  • "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

  • 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.  

  • EDI: Receiver port in control record is invalid

    Yesterday, we got refreshed out quality system with the production SAP system.
    I am trying to process IDoc # QXXXXXXX  in quality but I am getting the following error message:
    EDI: Receiver port in control record is invalid.
    To create this IDoc, I copied IDoc # PXXXXXXX using WE19 and modified certain fields so that it would change the clearance status. The IDoc I used to copy from was from production server and a part of the recent refresh of Production serveru2026
    could that be the reason that the EDI Receiver port is invalid or is there another reason?
    THANKS IN ADVANCE.

    Hi sam kumar 
    Ports and Partner Profile  may be Same or Different in Quality and Production  systems.- it is Client dependent
    U can cross check Ports using WE21 with Quality system and production systems
    U can cross check Partner Profile using WE20  with Quality system and production systems
    if both are not same u need maintain port and partner profiel before creating idoc using we19...
    Note: Keep a note on Logical system also..
    I hope this help for all when system refreshs,.
    Ramesh

Maybe you are looking for