Scenario:file to idoc

dear experts
here my scenario is file to idoc
message is sent successfully from sender but which is not received in receiver i.e,in r/3.
the error which i found id
error category:idoc_adopter
error code:attribute_inv_rcv_serv.
plz any one can help me?????????
regards
somesh

hi
Receiver service cannot be converted into an ALE logical system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
In Business System(R/3) 'Adapter specific identifiers' chooset 'Compare System Landscap Directory' refersh cache and activate objetcs
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Similar Messages

Error in executing scenario File to Idoc

Hi,
I did File to Idoc scenario.
In that I got error in status record at r/3 system...
status record code is 51....Error is Application document not posted
regards,
pavani

Hi Ravi,
i mapped some of the data fields. Control fields i disabled them....
Can you giv me wat are the importent fields for Cremas04...
I did all the field that are indicated in red color..
still i m getting error
Message was edited by:
Pavani Kumari Kokkiragedda

Scenario: File To Idoc & Idoc To File

Hi,
Can any body explain file to idoc and idoc to file scenario's with screen shots which incluses setting at R/3 side and XI side. Starting from SLD to ID.
Thanks in advance.
Regards,
Prems.S

Also u can follow the settings on Xi and R/3 side
SAP XI
1) RFC Destination (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.
2) Create Port (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 (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Problem in scenario : file to idoc through bpm

hi,
 iam working on a scenario ,which splits invoice packets and sends it various receivers.
 i encounter an error when sending the split message to the receiver.the error is,
 [i]"cannot convert the sending service into an ale logical system".
 can u help me solving this.
 thanks in advance,
 john p.

Hi,
Refer to this thread... Same problem cannot convert the sending service into an ale logical system solved..
Re: Unable to convert the sender service to an ALE logical System
Cheers,
Siva Maranani.

Testing File to Idoc scenario

Hi,
I have created a scenario, file to IDOC..and Idoc i am using is CREMAS 04.
in SXMB_moni, message status shows Scheduled
And when I go to R/3 system tried we05, and Idx5 transactions and I didn't find the IDOC.
Can anybody tell me how to trace this issue?
Thanks
Balaji

Hi,
Have you done ALE config steps for inbound interface to SAP?
If not, then do it first.
They are:
1)Creating Logical systems(BASIS team creates it)
2)Assigning Clients to Logical systems(BASIS team creates it)
3)Create RFC destinations
4)Maintain distribution model for Idoc(Cremas)
5)Create partner profiles
How to relate whether I have the required partner profile in R/3 system?
Double click on the R/3 system, check if there is an entry for Inbound parameters
on the right hand side ,if so then see for the IDoc Cremas.
If you don't see an entry for IDOC CREMAS then create one as I mentioned above.
Regards,
JE

Duubt in File -XI-IDOC Scenario

hi
In my Scenario FILE-XI-IDOC Everything is fine.But IDOC can't display in R/3 when i checked with we05.
Please provide solution.
Thanks

Check the trasnaction SM 58 in XI. Make the user id as *.
Regards
Bhavesh

Without using ID file to idoc scenario

Hi People
I am trying one scenario(file to IDoc) that is without using configuration only using IR only is it possible to create? and how
Thanks & regards
shekar

Hi,
some scenarios could be done without IR:
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
But I guess it's not possible to realize a scenario without ID.
For example where do you want to configure you File Adapter?
Regards
Patrick
Edited by: Patrick Koehnen on May 21, 2008 1:31 PM

File to Idoc Mapping Problem

Hi all,
i'm getting an error from SXMB_MONI in a scenario File to Idoc.
I have done the mapping from source file and Idoc CREMAS03, when i try to test from Integration Repository it's all ok, but when the scenario is executed i find this error in Idoc Adapter :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
The field BEGIN in idoc structure is filled with constant value 1, than i dont understand the error.
This is the xml source file :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Vendor xmlns:ns0="urn:tbit40:workshop:group01:legacy">
- <Address>
<Country>IT</Country>
<Zip>001</Zip>
<City>ROMA</City>
<Street>SATTA</Street>
</Address>
<Currency>USD</Currency>
<SearchTerm>TEST</SearchTerm>
<LastName>GUIDA</LastName>
<VendorNumber>44332</VendorNumber>
</ns0:Vendor>
Any help is really appreciated.
Thanks.

Hi all and thanks for your answer.
My problem is that for what i can see all Idoc attribute (like the attribute BEGIN) are mapped with constant value.
In taget source i can see : BEGIN = Constant([value=1])
What i dont understand is why when i execute the scenario it ends with this message :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
It seem to me that the tag BEGIN is not filled with value, i also tried to copy the source xml file directly from SXMB_MONI (from payload) and test it in Integration Repository mapping section, but here is all ok and the test end succesfully.

FILE TO IDOC MAPPING Query

Hi Experts
I have facing some confusion when i am doing mapping for my scenario FILE to IDOC.
The IDOC Structure is as follows
HeaderRecord 0-1
DataRecord1   0-unbounded
     (Subnode)DataRecord2 0-unbounded
      (Subnode)DataRecord4   0-unbounded
DataRecord5 0-unbounded
      (subnode) DataRecord6 0-unbounded
TrailerRecord 0-1
when the DataRecord1 is executed, an idoc is generated and all the DataRecord2,DataRecord4,DataRecord6 shld come under that particular Idoc. And when another Idoc is generated,all the DataRecord2,DataRecord5,DataRecord6 shld come under that particular Idoc.
How to achieve mapping for this??
please help me out.
Edited by: vemuganti naga phalguna on Oct 27, 2010 7:56 AM
Edited by: vemuganti naga phalguna on Oct 27, 2010 7:59 AM

Hi
1) Source file is Text File.
sample source data.
A|20101006142345|SAPQMP|40|
B|5999|R00003D||N|20072008|Unknown|
C|T0014|M1556||colourless Pale yellow||Receipt-Bulk|1|Yes|Y|Text||
C|T0001|M1556||Limpid liquid ||Receipt-Bulk|1|Yes|Y|Text||
C|T1379|M1398|18||23|Receipt-Bulk|1|Yes|Y|Number|mm²/s|
B|5998|R00014A||N|20072008|Unknown|
C|T0014|M0211||2.0||CoA|1|No|Y|Text||
C|T0014|M0211||2.0||Receipt-Bulk|1|No|Y|Text||
C|T0014|M0211||2.0||Transfer|1|No|Y|Text||
C|T0051|M0271|97|||CoA|1|No|Y|Number|None|
C|T0073|M1356|Pass|||Receipt-Bulk|1|No|Y|||
C|T0073|M1356|Pass|||Transfer|1|No|Y|||
C|T0025|M0331||0.880||CoA|1|No|Y||g/ml|
C|T0025|M0331||0.880||Receipt-Bulk|1|No|Y||g/ml|
C|T0025|M0331||0.880||Transfer|1|No|Y||g/ml|
C|T0001|M1556||Clear & Bright ||CoA|1|No|Y|Text||
C|T0049|M0341|28.0||32.0|CoA|1|No|Y|Number|mm²/s|
C|T0049|M0341|28.0||32.0|Receipt-Bulk|1|No|Y|Number|mm²/s|
C|T0049|M0341|28.0||32.0|Transfer|1|No|Y|Number|mm²/s|
C|T0042|M0422|||-15|CoA|1|No|Y||°C|
C|T0092|M0578|||16|CoA|1|No|Y|Number|% Loss|
C|T0021|M0199||||CoA|1|No|Y||minutes|
C|T0039|M1453|Mktble|||CoA|1|No|Y|||
C|T0050|M0341||5.1||CoA|1|No|Y|Number|mm²/s|
C|T0050|M0341||5.1||Receipt-Bulk|1|No|Y|Number|mm²/s|
C|T0050|M0341||5.1||Transfer|1|No|Y|Number|mm²/s|
C|T0026|M0412|210|||CoA|1|No|Y|Number|°C|
Z|20101006142355|SAPQMP|40|
where Records A indicate File Header, Z indicates File Trailer
Recodrs B indicateds Material header and Would be repeating multiple times
No. of B Records = No. of Idocs generated with corresponding C records data which indicates Component Rows (multiple)
i.e as many B records file contains, that many Idoc will be created
For Mapping I require B and C Records. Field Separator is Pipe | symbol
I need to Ignore A B C Z
How to define the source structure and the respective FCC Parameters
please help me out

How to serialize File- XI- IDoc

Hi,
we have a scenario FILE->XI->IDoc.
The IDocs (one special idoc type) have to be send to ERP 2005 in serial order (not parallel).
I know, that I can solve this problem with queues (one queue for this interface) - but how can I manage it?
All other interfaces should still work parallel.
Regards
Wolfgang

Hi Michal,
wow - it work's ... but the idocs in ERP 2005 have now the state 75 (yellow) (in WE02; the message is: IDoc received via qRFC).
All messages a sent to ERP via exactly the same queue - called SAP_ALE....
Do you have an idea with state 75.
But you helped me a lot ... Thank you!
Before I wrote this thread, I checked your book, but you described the scenario IDOC -> XI -> ... and not opposite.
You see - I bought your book ... and now I should read it ))
Regards
Wolfgang

FCC File-XI-IDOC: Pl confirm the validity of parameters I have specified

Hi,
I have the scenario File-XI-IDOC. I have almost completed the IR and ID config minus the FCC part.
Need to do the FCC for reading the file which will enable me to map it to IDOC structure.
I have the following TextFile structure ( Note: each field in the file is fixed length )
Header( 1 record)
Data_header (1 record)
|_ Data_Item (Multiple records)
Trailer
As expected each node has multiple fields in it like:
Header = Source, Destination, Date
Data_header = Company, Country
Data_item = Office1 address, postcode1,
Data_item = Office2 address, postcode2,
Data_item = Office3 address, postcode3,
Trailer = Checksum, Carriage_return_value
I have keyed in the following values into the various FCC parameters.
Appreciate if you could confirm if they are correct. (pl provide correct values, if needed)
Recordset_name: (should I put any value heer???)
Recordset Structure: Header,1,Data_header,1,Data_item,*,Trailer,1
Key field: (should I put any value heer???)
Header.fieldfixedlengths = 10,10,8
Header.endseparator = 1310   ( Header record ends with a carriage return value 13 followed by line feed character 10)
Header.fieldnames = Source, Destination, Date
Header.Keyfieldvalue = 1 (Should I put anything here??)
Header.keyfieldinstructure = u2018ignoreu2019
Data_Header.fieldfixedlengths = 4,4
Data_Header.endseparator = 1310   ( Data Header record ends with a carriage return value 13 followed by line feed character 10)
Data_Header.fieldnames = Company, Country
Data_Header.Keyfieldvalue = 2 (Should I put anything here??)
Data_Header.keyfieldinstructure = u2018ignoreu2019
Data_Item.fieldfixedlengths = 40,7
Data_Item.endseparator = 1310   ( Data Item record ends with a carriage return value 13 followed by line feed character 10)
Data_Item.fieldnames = Company address, postcode
Data_Item.Keyfieldvalue = 3 (Should I put anything here??)
Data_Item.keyfieldinstructure = u2018ignoreu2019
Trailer.fieldfixedlengths = 2,2,1
Trailer.endseparator = T   ( Trailer record ends with a character T)
Trailer.fieldnames = Checksum, Carriage_return_value, End_value
Trailer.Keyfieldvalue = 4 (Should I put anything here??)
Trailer.keyfieldinstructure = u2018ignoreu2019
Appreciate if you could confirm if they are correct.
Thanks and Regards
Shirin

Hi,
I am still confused with what do I do with the CR/LF character pair in my incoming file.
If possible could you let me know the value you would put in the fieldFixedlengths, endSeparator fields in all the recordsets.
As you can see all my data lines end with a value 1310, so do I not need to put it in FCC to let it know that data line is ending.
Appreciate your response.
Regards
Shirin
Header Section
Field                             Length          Notes
Source                             [10]
Destination                    [10]
Message ID                  [10]
Created Timestamp      [8]
CR/LF character pair        [4]           (Carriage return character (13) followed be line feed character (10) )
Data_Header Section
Field                             Length          Notes
Company                         [4]
Country                           [4]
CR/LF character pair         [4]           (Carriage return character (13) followed be line feed character (10) )
Data_item Section
Field                             Length          Notes
Address                          [40]
Postcode                          [7]
CR/LF character pair          [4]           (Carriage return character (13) followed be line feed character (10) )
So my file's Header and Data_header and Data_item will look like
STARSYSTEMSAP       1234567890200812121310
GB03GB 1310
101chamberlayne drive, Preston,UK,      E149PL 1310

File to IDOC : Code page error

Hi
I am working on Scenario File to IDOC.
T90CLNT90 is the rfcdest for SAP R3 System from XI.
The file sender succesfully sends thefile to the XI Engine.From XI to R3 the adapter fails to send the idoc.
What could be the reason for code page error?
I am getting following eror.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>DB Tab RFCDES: Could not determine code page with T90CLNT90</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: DB Tab RFCDES: Could not determine code page with T90CLNT90</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Prashanta

Hi,
Check if T90CLNT90 exists in SM59 transcation I think it should be T90CLNT090.
Also check this link
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
Thanks,
Prakash

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Scenario:file to idoc

Similar Messages

Maybe you are looking for