Control record in File to Idoc

hi guys,
i am new to XI and now learning File to Idoc scenario.
after going thru some forums and blogs i found that while mapping the control record EDI_DC40 in the idoc should be disabled.
my question is will this control record be disabled forever or should the proper data be filled at the runtime.
help me in understanding this concept plz.
Points will be awarded
Regards
BHASKER

Hi Bhasker,
The control record acts as router. This control record has information like which is message type, Idoc type, sender port etc. [http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm ]
The control records need to filled since data in the Idoc has to be filled accurately. But again it is not necessary, XI has option to fill the control records by itself at runtime using receiver determination
This blog will help you understand more
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
regards
Ramesh P

Similar Messages

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

Error values in Idoc Control Records in File to Idoc Scenarios

Hi All,
I am posting 2 different types of Idocs in 2 different File-to-Idoc Scenarios. In many cases both these files may get picked at the same time. One is an Orders Idoc and the other one is Shipment Idoc. The Orders Idoc has a control record value in the Sender Partner Fn as 'ZC' while as for Shipment Idoc that value is not passed. The other Sender parameters are passed and are different for both these idocs. But when the files are processed, the value 'ZC' get populated for the Shipment Idoc also. When 100 files are sent with 90 orders and 10 shipments, the shipments get created with 'ZC' partner fn. This is visible in the Call Adapter Pipeline Step under the node IDocOutbound. . I have 2 different Idoc receiver adapters.Can anybody help me out here?
Thanks,
Geetha

Hey,
>'ZC' while as for Shipment Idoc that value is not passed
Check whether the Source/ Mapping populates the 'ZC' , Did you checked Apply Control record in Receiver Adapter for Shipment, What is the name you have mentioned for the in the SLD -Logical system for Sender system
Cheers
Agasthuri

Posting multiple records from file to idoc

Hi Exerts,
i have done scenario to post one record from file to IDOC, to post multiple records from file to idoc what are the options to be modified in the scenario.
thanks,
dhanush

Hi Dhanush,
You need to change the occurance of idoc to 0 to unbounded ie need to opt idoc packaging.
Just download the xsd of you idoc to the desktop and change the occurance tag as "<xsd:element name="IDOC" type="COND_A.COND_A02" maxOccurs="unbounded" />" and then reimport it into External definition and use it in your message mapping and then map it with you source structure.
Regards,
Prasanthi.

First record is not an IDoc control record (check file)

Hi Experts,
I try to build an interface between a non SAP system and a SAP system via IDOC.
I created an .xml test file that I would like to upload now in system with program RSEINB00, but i have error
First record is not an IDoc control record (please check file).
What do I need to do? This is example file I uploaded
?xml version="1.0" encoding="UTF-8"?>
<EXCHANGE_RATE01>
     <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
               <TABNAM>EDI_DC40</TABNAM>
               <IDOCTYP>EXCHANGE_RATE01</IDOCTYP>
               <MESTYP>EXCHANGE_RATE</MESTYP>
               <MESCOD>010</MESCOD>
               <SNDPOR>XML_2_IDOC</SNDPOR>
               <SNDPRT>LS</SNDPRT>
               <SNDPRN>INCENTAGE</SNDPRN>
               <RCVPOR>SAPQH3</RCVPOR>
               <RCVPRT>LS</RCVPRT>
               <RCVPRN>QH3CLNT100</RCVPRN>
               <CREDAT>20110526</CREDAT>
               <CRETIM>204404</CRETIM>
          </EDI_DC40>
          <E1ECXHANGE_RATE SEGMENT="1">
               <LOG_SYSTEM>QH3CLNT100</LOG_SYSTEM>
               <UPD_ALLOW>X</UPD_ALLOW>
               <DEV_ALLOW>000</DEV_ALLOW>
               <E1BP1093_0 SEGMENT="1">
                    <RATE_TYPE>RUFX</RATE_TYPE>
                    <FROM_CURR>USD</FROM_CURR>
                    <TO_CURRNCY>RUB</TO_CURRNCY>
                    <VALID_FROM>20120105</VALID_FROM>
                    <EXCH_RATE>5000</EXCH_RATE>
                    <FROM_FACTOR>100</FROM_FACTOR>
                    <TO_FACTOR>1</TO_FACTOR>
                    <EXCH_RATE_V>0.00000</EXCH_RATE_V>
                    <FROM_FACTOR_V>0</FROM_FACTOR_V>
                    <TO_FACTOR_V>0</TO_FACTOR_V>
               </E1BP1093_0>
               </E1ECXHANGE_RATE>
     </ IDOC>
</EXCHANGE_RATE01>
kr,
Stef

Hi Udo,
I thought I posted it in another forum, still not solved.....
kr,
Stef

Control Record - Data fetch in IDOC

Hi Folks,
Can you please tell me from where the Control Record data for ORDERS and ORDCHG gets populated. ? I have checked the FM - IDOC_OUTPUT_ORDERS which has one of the import parameters as control_record_in which is already populated when it reaches this FM. I am triggering the IDOC using - NACE settings.
Since there are many output types and message variants involved in my system i will have to find out from where the Partner profile are loaded. ?
Thanks
Balakumar

Hi Balakumar
Have you checked in NACE->Output Types->Processing routines, if the output type you are using is indeed configured to use RSNASTED?
If it is using RSNASTED, then in that program it will call a function to read the partner.
It basically checks table EDP12 based on your output type, partner number, etc, and then retrieves the IDoc Message Variant, Function, Process Code. This then gets populated into the IDoc Control Record.
Table EDP12 basically is populated when you configure partner profile in WE20 -> Outbound Parameters -> Message Control.
Rgds
Eng Swee

How can we configure or control records go into single idoc thru BODS?

Hi,
Our case is -
IDOC format has three segment. Each segments has child nodes -
1. CONTROL SEGMENT - This is required only once per idoc.
child1
child2
2. SEGMENT1 - sinlge source record to be broken into two segments.
child1
child2
3. SEGMENT2 - sinlge source record to be broken into two segments.
child1
child2
we have a single source (lest say having 100 records).
In the current design which does generates IDOCS but as many as the no of records in source. Currently we use a row generation transform as dummy (with row count as 1) to pass to the IDOC parent nodes's from clause to escape the error - invalid input to the parent nodes.
Child nodes are either mapped to the source table or are null.
Question - How can we configure this in a way that we control how many records go into single idoc. Ex - lets say 50 per idoc so only 2 idoc should be created if 100 records are there.

HI,
this sounds to me like Data Services. If so I would suggest to post this into the Data Service forum.
regards
Ingo HIlgefort

Why control records disable in mapping for idoc communication?

Hi, In the mapping we disable conrol records in file to idoc ...why is their any specific reason..>? plz respond me soon..accurate question reward more..thanq

Hey,
EDI_DC40 contains the data about control records.
Before the message leaves the Integration Server, the message header contains values that are exported and used later to complete the IDoc control record.
Adapter populates it runtime.
Correct me if i am wrong
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Loop in file to IDoc scenario PI 7.11 (Support Package 04)

In our scenario we use FileSenderCommunicationChannel to get files from FTP-Server. After processing the file should be saved in archive directory on our PI-Server (UNIX-System). Physically the archive directory is not in our PI-Server, it is a mapped windows server directory.
In case of non availability of the archive directory (e.g. windows server down), we have the following described problem.
1.
Start processing of file from FTP-Server (File with 2 lines, result 1 IDoc per line (2 IDocs))
2.
In AdapterEngine monitor we find 2 messages (successfully). Audit-Log of last message (second line) contains the following error.
File "TUM00001.TXT" - archiving file "/ext/windows_server/X/OLD/20100326-075807-897_TUM00001.TXT" after processing failed with java.io.FileNotFoundException: /ext/windows_server/X/OLD/20100326-075807-897_TUM00001.TXT (No such file or directory) - retry.
3.
In IntegrationEngine monitor we also find 2 messages for the IDocu2019s.
Error situation:
Now the loop startsu2026. (until directory is available (mapped)). Frequency of loop depends on u201CPoll Interval (secs)u201D of FileSenderCommunicationChannel.
1.
Create new message in AdapterEngine for last line of the file (with same entry in Audit-Log u201Cerror for archiving fileu201D)
2.
Create new message (IDoc) in IntegrationEngine
We doesnu2019t have this problem in our old environment (XI 3.0 Support Package 21).
Parameter of FileSenderCommunicationChannel:
Quality of Service: Exactly Once
Poll Interval (secs): 3600
Processing Mode: Archive
Archive Directory: /ext/windows_server/X/OLD
Directory for Archiving Files with Errors: /ext/windows_server/X/OLD/ERR
Recordset Structure: ROW, 1
Recordset Sequence: Ascending
Recordset per Message: 1
For me itu2019s an error, but Iu2019m not sure because itu2019s a mapped directory.....

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

File to idoc scenario in pi 7.1

Hi All,
I am testing file to Idoc scenario.
I have few queries. I am using PI 7.1
1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
Please advice how to overcome
3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
"EDI: Partner profile inbound not available"
I checked all the relevent partner prfile configuration is already there"
I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
Ram

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

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

File to idoc adapter :IDOC IS POSTED IN XI but showing error EDI partner

Hi ,
my interface is working fine but issue is that in Recver R3 system idoc is in errors status 56 (EDI partner profile not available.
I already define business system which is used to send data from XI.
My Business system name is testBsys1 for sender XI service.
In R3 i have created logical system testBsys1
and in we20 already created partner profile testBsys1
and also maintain in bound parameter.
please suggest me where is i am doing mistake.

Hi Mohit,
How is the control record of the posted Idoc made in PI? Check the Control Record of The IDoc that is posted in R3, it is not having correct information.
IF you are not making the control records in PI mapping, then in the receiver IDoc, keep apply control records from payload as checked.
Regards
Suraj

My scenario is file to Idoc and we are using multiple receivers.

Whenever we executes the scenario, getting the error u201CATTRIBUTE_IDOC_METADATA u201Cin sxmb_moni
Any suggestions on how to do solve this?

Hi,
>>>>Error: Copy Receiver from Payload: Receiver Is Missing in Payload
Have you checked "Apply control records from payload " in IDOc receiver communication channel?? If so please make sure that you've mapped RCVPRN accordingly in control record of IDOC.
Refer below discussions
Error in SXMB_MONI as"Copy Sender from Payload: Sender Is Missing in Payloa
IDOC Error - Copy Sender from Payload: Sender Is Missing in Payload
Regards,
Priyanka

How to handle the control records in case of file to idoc scenario.

Hi All,
can you please clarify me how to handle the control records in case of file to idoc scenario.

Hi,
In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
Regards
Seshagiri

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

Control record in File to Idoc

Similar Messages

Maybe you are looking for