Trouble shooting File to Idoc scenario: wrong Idoc structure in target

Hi All,
I am working in an file to idoc scenario. Now the scenario is running but the idoc I am sending from SAP XI is not matching with one received in SAP R/3 system. This is not a new scenario. The scenario was already existing. I have done structural changes in Idoc structure and re-imported it in SAP XI. When the iodoc reaches SAP R/3 system I check its structure and data content. 4 of its fields are missing all 4 were newly added fields. Data from some fields are getting merged into one field within Idoc. data from one field is moving onto other fields in target. I have refreshed the metadata using IDX2 transcation within SAP XI but still getting same result.

Hi All,
I am able to see the changed idoc structure in IR. I have also tried cache refresh. I am trying to explain my problem once again with example.
Source Idoc in XI
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f3                                       d33
       f4                                       d4
       f5                                       d5
Idoc structure received in SAP R/3 system. I am seeing through we02 transcation, inbound idoc
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f4                                       d33d4
I have tried cache refresh, IDx2 metadata refresh, but no improvement of the situation.

Similar Messages

File to Idoc Scenario and Idoc to File Scenario's

Hi Friends ,
This is Shalini Shah,
Please give me the details of how many busines sytems required in File to Idoc Scenario and Idoc to File sceanrio's.
In business system , what is the name of Integration server(this name is related to XI ot Third Party)
Please give me the full details of these two scenarios from Scratch.
Thanks in Advance.
Regards,
Shalini Shah.

Hi
These r few links which gives u complete scenarios...
for idoc to file:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
for file to idoc:
part1
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
part2
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
part 3
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
This link is also good:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
kindly rewards points if helpful.

Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2

Firefox recently updated and Face Book looks wrong. I've gone through all of the trouble shooting in "Web sites look wrong"

I cannot get Face Book to display properly in Firefox. I've done lots of trouble shooting. All of the "Web sites look wrong" troubleshooting. Very frustrating. Other web sites display properly. Not Face Book. Help! I love Firefox!

Woo-Hoo! Started Firefox in Safe Mode and disabled everything. Went through the Preferences check list of potential problems and double checked all of the settings, restarted Firefox, in plain default mode and wah-la, everything looks right again in Face Book! YAY! Then tried re-installing my theme, and checked FB again and it's all good! Thank You Firefox Support Pages! :)

SOAP- PI- IDoc scenario - getting IDoc acknowledgment

Hi guys,
is there any way how to propagate acknowledgment of an received IDoc in ECC back to the SOAP caller?
If I'm not wrong, sending IDoc to ECC is an asynchronous step. Is there any way how to let the caller know that the IDoc was received successfully?
Thanks, Peter

Hi Peter,
If your scenario is async, then you can receive by standard the acknowledgment. You can as well configure the acknowledgment in PI as seperate message (e.g. for mapping) with report idx_alerequest.
If your scenario is synchr you need to setup a Business Process with a sync - async bridge: The BP receives the SOAP msg, sends an IDoc requesting an ackn (or receives it as separate msg) and finally send the response back to the SOAP sender.
Regards,
Udo

Logic Pro trouble shoot files provided by apple

I apologize in advance if someone has already posted this link but it is well worth taking a look at.
http://search.info.apple.com/?q=logicpro+&search=Search&lr=lang_en&search=Go&type=ktech+ORklearn

You may need to rebuild the loops index.
Open up Logic and display the Loops Browser
Open up FInder and locate the folder containing the loops as you describe
Drag the loops folders onto the Loops Browser
That will rebuild the index and all should be well.
Pete

How can I include the Header Information....for a File to IDOC Scenario

Hi,
I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that "HEADER Information Missing: Message should Start with EDI_DC40" i.e the Header Information.
My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
Kindly Inform me some Solutions.
Thanks & Regards
Somnath

Hi Suraj,
Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
Thanks and Regards
Somnath

File to idoc scenario (split message)

hello everybody
i have a file (xml) -> XI -> Idoc scenario
sometimes idoc message is so much big and i have problem to process it.
so i would like split message in more idoc but i need decide a cut-point
example in file i have 200 row and i don't want create 200 idocs but example 4.
So i need cut file every 50 rows.
It's possible?
thanks
Alex

Hi Alessandro ,
We had the same problem in HR implementation where we used to get data for thousands of employees in a single file.
As Idoc was not able to hold this much of data,data used to be truncated.
Then we had taken a field (employee number) as a criteria to generate IDocs,and now we have an IDoc generated for each employee record.
This was helpful as for a single employee,there were a number of change records.
The logic used was:
Employeecode -> splitByValue(value changed) -> collapseContexts -> IDoc.
Does it suit your requirement as well?I mean,may be you can find such field for splitting IDocs.
Kindly let us know.
Thanks.
Regards,
Shweta

Http - iDoc scenario - ID

Hi,
HTTP - XI - iDOC is my scenario.....
i am facing problem in iDoc adapter...
the error category is idoc adapter and the error id is "ATTRIBUTE_INV_SND_SERV"
Which RFC destination and port should in mention in Communication Channel? Either the receiver or XI?
forward your suggestions....
Thanks,
RPN

hi rpn,
check this links
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Check the following blog.
The specified item was not found.
Unable to convert sender service to an ALE logical system
ATTRIBUTE_INV_SND_SERV
XI 3.0, Party and Service problems (IDoc inbound)
Trouble shooting file to IDOC and IDOC to file
Troubleshooting File-to-IDOC Scenario in XI.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
see the below links
ALE configuration for pushing idocs from SAP to XI
Introduction to IDoc-XI-File scenario and complete walk through for starters.
idoc settings Configuration steps required for posting idoc's(XI)
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - Generate Test Case for an IDOC Scenario
regards
srinivas

IDOC scenario Debugging

Hi,
I want to debug the IDOC senarios(Both File to Idoc and Idoc to file ).. for this.. from where can we start.. and what are the things we need to check.. how can we debug the scenarios...
i mean.. just give me the descriptive steps..
Thanks
BABU

HI,
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Thanks
Swarup
Edited by: Swarup Sawant on Feb 9, 2008 1:32 PM

Problem in Idoc scenario

Hi
Can anyone tell me how to determine the status of an iDoc in recieving system.
Please be specific

Hi,
enter WE05 transaction code in R/3 and hear u will c the status of IDOC wether it is posted succesfully.
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

Idoc Scenario Partner type not LS

Hi experts ,
we have gone through https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a&overridelayout=true for idoc scenario where idoc partner type is not a logical system .Now we are working on case2 scenario in above document.we have some confusion in the configurations at R/3 side.Can somebody explain the step by step configuration at R/3 side.
Thanks.

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type : INVOIC
Under Outbound Option u2013 Tab
Receiver Port : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size : 1
Transfer IDoc Immediately (Select)
Basic Type : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application : V3
Message Type : RD00
Process Code : SD09
Hope, your problem will get resolve.
Regards..
Imran

IDoc to IDoc Scenario - Correct Interface Mapping configuration

Hello All,
i have to configure an Interface Mapping for an IDoc to IDoc scenario.
IDoc Type for sending and receiving already imported and located under Imported Objectes\IDocs in respective Software Component Version.
Now, how is the correct configuration? Add the sending respectively receiving IDoc Type directly to Source Interface/Target Interface under Display Interface Mapping or create first a sending Message Interface and a receiving Message Interface and add the IDoc type under configuration Message Types. Then add the Message Interface to the Interface Mapping.
The selection for direct import of the IDoc structure under the Interface Mapping (Source Interface/Target Interface) is possible.
Many Thanks in advanced!
Jochen

hi,
for IDOCs (if you don't use a BPM)
you don't need any message interface
so if you have already created a message mapping
you can put the IDOCs directly to your interface mapping
then click on read interfaces
and select your message mapping program
if you want to learn more about IDOCs and XI
have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Alert Configuration for File to IDoc scenario

I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
and configured Alerts for file to IDoc scenario.
But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
Regards,
Suraj Kumar

hi Suraj,
WHich SP version are you on??
If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
Regards,
Bhavesh

Trouble shooting File to Idoc scenario: wrong Idoc structure in target

Similar Messages

Maybe you are looking for