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

Similar Messages

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

Error message "EDI: Field SEGNAM in data record is default"

Hi all,
I am facing issue in Idoc creation. I am getting error message saying 'EDI: Field SEGNAM in data record is default' and so Idoc is not getting created.
Can anybody tell me how to resolve this. I checked in debugging mode and found that this error message is coming from a standard program.
Waiting for some good replies.
Thanks,
Archana

Hi,
Yes, it is getting displayed from FM 'EDI_SEGMENTS_ADD_BLOCK'.
But not getting any clue how to resolve this as it is getting displayed from standard program.
Any clue on this?
Thanks,
Archana

EDI: Sender port in control record is invalid

HI
EDI: Sender port in control record is invalid, this message i am getting in WE02 what is this pls tell me ASAP
regards
shekar

Hi,
Check the ALE setting...
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani

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

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.

IDoc (Control Record) RCVPOR

Hi,
I'm posting an IDoc from XI to R/3 and field RCVPOR is coming out blank.
In the documentation, it says that it should be populated from the Port value in the receiver IDoc adapter.
Any Idea why it's blank? It is there in the receiver IDoc adapter settings.
Same problem with SNDPFC? (This one I don't know were the value would come from).
All the other fields in the Control Record are being populated correctly since I have the
(Apply Control record Value from Payload) checked in the IDoc adapter.
Other question, if (Apply Control record Value from Payload) is checked, is there a way to overwrite some of the values or it's all or nothing?
Rgds,
Yves

Hi Yves
> Any Idea why it's blank? It is there in the receiver
> IDoc adapter settings.
Check you have configured the port in IDX1 transaction. Should be something like SAP<SID>.
> Same problem with SNDPFC? (This one I don't know
> were the value would come from).
Do you really need this? It's rarely used. Usually just the partner type is used, not the partner function... (but read below).
> All the other fields in the Control Record are being
> populated correctly since I have the
> (Apply Control record Value from Payload) checked in
> the IDoc adapter.
> Other question, if (Apply Control record Value from
> Payload) is checked, is there a way to overwrite some
> of the values or it's all or nothing?
In my config I also have "Apply Control record Value from Payload" checked. In the mapping I do NOT disable the control rec, but put empty constants on mandatory fields. Then you can set whatever you want, including the SNDPFC.
Let me know.
Alex

Idoc Control record - Change to msg type not working

Hi,
We have a field in the control record that we are trying to update but it will not take. The FM is IDOC_OUTPUT_TPSDLS. Inside this FM is a call to function customer-function '020'. double click on the '020' and you go to the user exit EXIT_SAPLV56I_020.
I created the include ZXV56U30. It has one line of code - idoc_control-mescod = 'GLT'. We are trying to populate this field with 'GLT'. I activated the include and the user exit and the customer-function and finally the FM IDOC_OUTPUT_TPSDLS. The user tested and said while we are getting our custom segments populated we are not getting this idoc_control-mescod = 'GLT' to work.
What am I missing here? Do I need to do a commit after the field is populated? Is there some config that needs to be in place or what?
Any help would be apprciated since we need this by the EOD for go-live.
Thanks - many points awarded if someone can figure this out!

Hi,
Check if the user exit enhancment is added to a project in CMOD and make sure the project is activated.
Thanks,
Naren

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.

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

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.

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

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

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

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.

EDI: Field REFINT in control record

Similar Messages

Maybe you are looking for