Suggestion on RSEINB00 ( file to idoc)

Hi,
    What is the use of port in program RSEINB00. How does the program identifies to which idoc it has to convert the flat file.
    Should we maintain any control record in the header of the flat file.If yes can anybody give me the format of the file which RSEINB00 identifies.
    Will I be maintain a remote location for flat file in program RSEINB00 through FTP connection or the file has to from application server itself.
Thanks & Regards,
Karthik.k

Hi Krishnan,
You need to pass the control record.
Std code checks whether the first record is a control record and then on tries to fetch the other details.
I suggest one debug of IDOC_INBOUND_FROM_FILE or the main program RSEINB00 would help a lot.
Rgds,
HR

Similar Messages

Suggestions for File to IDOC Scenario

Experts,
Here is the requirement A Legacy System will Produce the Customer data file and we have to transform certain data and post it to DEBMAS.
As Part of the information in the file there is a field Which could have a value Update,Amend or Delete.
My Question is How do it handle this.
Please give me your valuable thoughts.
Is it Possible to go for File2IDOC here?
Thanks
Vasu.

Hi Vasu,
If Customer data file is of type xml then file to IDOC scenario is preferable.
Else you have to convert Customer data file to xml first and then proceed for that you can use content converson feature of File Adapter.
The information for Update,Amend or Delete will be provided by customer or you have to decide it based of data in table?
if it is provided by customer then you can go for ABAP Proxy for that take help of ABAPers.
If you have to decide the Update,Amend or Delete logic.
Then fetch the data from table compare it with incoming data decide the Action and then perform the action this can also be handled in ABAP Proxy.
Reward Points if HElpful
Thanks
Sunil Singh

File to Idoc OR File to AbapProxy

Hello,
Let me expose my problem.
In fact, I need to integrate new Goods Movements sent by a non-Sap system to ECC system.
To do that, the non-sap system sends a file.
Then, I need to generate from this file an Idoc (MBGMCR), fill this Idoc with some extra data (from Ecc tables) and then to integrate it into ECC.
The question here is to find the best solution (according to performance and feasibility) to do that using PI (7.0).
We are hesitating between two scenarios:
1- File to Abap Proxy
We get the data sent by an abap proxy, and then we complete it with the necessary extra data from ECC tables in order to create complete the Idoc segments.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Even, using PI will be a waste of performance/time (due to mappingu2026)
2- File to IDOC
This alternative looks more interesting (at least in the PI way).
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
For example, the file contains Orders headers and I need to generate Goods Movements for the materials contained in the orders. So I need to access Orders posts, to retrieve the materials data.
Is there a way to retrieve simple information in PI using ECC data?
Any other suggestion/comment is welcome.
(Any other scenario is also welcome)
Thanks you in advance.
Saber L.
SAP PI consultant.
Edited by: LMS LMS on Nov 7, 2008 10:24 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM

ABAP proxy would improve performance in terms of providing adapterless communication.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Making a direct connection would increase point to point connectivity across the organization whose reduction is one of the reason why XI is used.
If ur communication is async and u have the idoc structure ready, then u may proceed with Idocs.
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
If you want to prevent the node from getting generated, simply disable it in mapping.
I hope u have seen this
Choose the Right Adapter to integrate with SAP systems
Regards,
Prateek

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 scenerio

hi
in file to idoc scenario
i got error in sxmb_moni
in status it is showing recording,
in Q.status it is showing stop symbol.
waiting for suggestions.

Hi Sandeep,
Have a look at queue problms here
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Some additional help
Q.Status is "Queue stopped"
queue status is stopped
Regards,
Prateek

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>> I am using a business service as my sender system.
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

Special character in File to IDoc

Hi,
am working on file to Idoc scenario.
The data is populated as expected in to the segments but when i see the idoc in the receiving system the special characters are replaced by #
For ex
how LII u201Cexceeds industry benchmarks and defeats stereotypesu201D
is cming as LII #exceeds industry benchmarks and defeats stereotypes#
Any suggestions to display the special characters.

In your File Sender channel you can set the File Encoding Scheme of your choice. We had a similar case where special characters were seen as # . Once we changed the Encoding scheme to ISO-8859-1 it worked fine.
Refer to the below link
http://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm
-Mala

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

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 in SRM

Hello All,
I am executing a scenario involving File to IDoc using an XSLT interface mapping.
I am getting an error with error text "Tag ORDERHEADER found instead of tag IDOC BEGIN"
Here is the error message:
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tested the XSLT mapping alone in Repository and it is working fine.
Please suggest on this issue.
Regards, Namadev

Hi Namdev,
//Tag ORDERHEADER found instead of tag IDOC BEGIN"
I think this error is due to a problem either in your source file or your mapping. When the IDOC is to be sent to the destination system, it expects the first tag to be <IDOC begin = > , but I dont think that is happening in your mapping.
As you are doing XSLT mapping, I would suggest you test your mapping and check if the destination Message that is created matches with the IDOC structure.
Regards,
bhavesh

File to idoc (Idoc is not getting posted in R/3 system)

Hi Experts,
I am having file to idoc scenario. In sxmb_moni i have seen success messages . The flag is checked on both sides.
So when clicked on the right hand side there are 443 idocs.but idoc is not posted on r/3 side. when i give the idoc number in r/3 system in we09 i couldnt find it? soi went for bd 87 transaction and gave the idoc number. it is saying that idoc is strucked in qrfc queue?
Kindly suggest.
Thanks in advance.
Regards
sai

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Complete file not displayed in File server(Idoc - XI File scenerio)

Hi,
Am working on Idoc-XI-File scenerio.
The target file is getting generated properly and complete xml n Adapter Monitoring in RWB.
But in the file server(in the directory)only part of the xml is displayed.The size of the file is 82KB.
Is there any configuration need to see the complete file in File Server.

Hi Amit,
This could be due to Network. How far is the file server from XI server?
I suggest putting the file in to local machine or in the same network and check whether it is OK.
- Pinkle

File to idoc with BPM

Hi All,
I have one File to IDoc Scenario. Now I want to throw posting error in a file.
i.e., if mapping goes not well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a file(Flat file) will be created at sending system side.
I am planning to design this scenario with BPM. Now end user requires a akwoledgement for this scenario eithere it may be succsess or failure in file format. If succsess the file will be created with succsess information(any format), either failure also file will be created with error information. The user requires only file format b'coz this file will be read by another java application (user didn't require to his mail).
Can anybody suggest the solution for this:
1. How to generate aknowledgement file for sucsess or failure.
2. How to use this file to idoc scenario in BPM with out using Alert configuration or Mail adapter.
Regards,
Konala.

Hi,
As you know Idocs are used for asynch communication, only was to get acknowledgemnet is using ALEAUDIT. For your scenario there can be one work around. When you post IDoc in the, in that function module after the posting is done call one more RFC with the the success/failure message which will trigger RFC to File sceanrio.
If you get any other solution, please post it back to same thread.
Thanks,
Prateek

How to catch Posting error in File to IDoc Scenario?

I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
Can anybody suggest the solution.
Regards,
Suraj Kumar

Hi Suraj,
this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
regards
jithesh

Suggestion on RSEINB00 ( file to idoc)

Similar Messages

Maybe you are looking for