Normal File to IDOC

Hi Gurus ...
here i am working on a normal file to IDOC scenario. i am working on PI 7.0. here i am facing a problem .... i created a message type for the coming file. i created the message type and message interface even .... later i imported the idoc from the R/3 system.... after that as my file is having multiple records i gone for IDOC packaging.... for this i downloaded the IDOC and did the occurance change it to unbounded and imported into XI through External definitions ...later i went through the mapping program between the sender message and the receiver IDOC interface which we imported through External Definitions......later i went to interface mapping and did it between the sender message interface and the originally downloaded idoc type ....
i activated all the objects coming to Integration directory ... i created the service with my own name for the sender file system ...later for the receiver system i created the PARTY and SERVICE..and i configured the communication channels ...later i went through tthe creation of receiver determination ,,,..interface determination....sender agreement and receiver agreement ...
regarding the configuration i created the rfc destinations and parner profile and port ..... but finally when i try to test the scenario i am getting the error as ..
Receiver service XXXXXXXXXX cannot be converted into an ALE logical system.
for this i even check the business system in SLD also. the logical sysem name is there assingned to business system ....what else i can do to complete this scenario ....please help me out in this. \

Hey,
yo need to create two logical system.
1 for SAP R3
2 for SAP XI.
Create them in SALE transaction of SAP R3.
The logical system that you have created for R3 assign a client to it.
Now use this logical system name in your technical system(WEB AS ABAP) in SLD.
Create a business system for the technical system.
Import the business system in ID.
open the business system.
In the service tab check the adapter specific Identifier.
the logical system name should be the same as mentioned in SLD.
Now if you have a Business service for your file sender.
Open the business service.
Goto the service tab
there wont be any logical system name in the adapter specific identifiers.
Assign the logical system that you have created for XI to this service.
Now your scenario should run properly.
regards,
Milan
Edited by: Milan Thaker on May 16, 2008 12:11 PM

Similar Messages

With out using IDX2.....in file to idoc scenario

Hi Masters,
                   i have one doubt .. Can i send normal file from sender system to sap system in the form of idoc.. with out using IDX2...
if it is possible then plz explain me about the steps .. and also explain me wht is the actual use of IDX2 .. as wel as IDX1,,
if u say in IDX2 we have to load the metadata of the idoc .. then we already uploaded the structure of the idoc in XI system ... then why we are using again IDX2 to load the metadata. i have full confusion now .. plz explain me in details ..
          hoping for quick response ..
               Thanks in advance ,
                   jp.

Hi,
You can send an idoc to SAP system through XI without using IDX2. When u send an Idoc through XI, the metadata will be automatically loaded in Idx2.
IDX1 is used for creating a port in XI for Idoc. This port will be responsible for loading the metadata.
Also have a look at this:
Importance of IDX1
Regards,
Divija.

File to IDoc Scenario: Idoc Status 50

Hello,
I have a problem in doing a File to IDoc Scenario with a simple XML file mapped to IDoc "CREMAS.CREMAS03". In the beginning, I got a status 56:"IDoc with errors added". Then I added a logical system (LS name of my sender)manually in "Display IMG";however, it didn't work. So I simply changed the logical system name of my sender to XI_00_800 which already exists in R/3. I tried the scenario again, then I got the status 50:"IDoc added". Looked like the IDoc still hadn't been correctly inserted as a record. May I ask what other steps or configurations do I need to do to get this scenario to work? Thank you.

Steve,
<i>Moreover, I didn't create any partner profile. The "XI_00_800" partner profile is in the system all along. Should I create a whole new partner profile and point that to my sender business system?</i>
You need not create it once again as it already exists. Normally , ALE configurations on an R3 system are the responsibiltis of the Functional Team. For instance , on our projects we are never given access to the End r3 systems and the Partner profile are created by the F'nal team itself.
Like I mentioned, ask your F'nal team why you are getting this issue. From XI side , there is nothing more you need to do.
Regards,
Bhavesh

File-XI-IDOC : error in sxmb_moni because of empty idoc

Hi !
I'm converting a CSV file to IDOC segments (CREMAS04).
XI uses a lookup table to convert CSV records to IDOC segments. It is normal that some records could not be converted. When I process a CSV file that has ALL non-convertable records, I get an error in sxmb_moni :
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 99889D40A4D811DBAD4A0017A4510466: Tag found instead of tag IDOC BEGIN=</SAP:P1>
And the final payload is:
<?xml version="1.0" encoding="UTF-8" ?>
<CREMAS04 />
In the integration repository, the occurance of the complex type CREMAS04 is "1..1", I modified the xsd to minOccurs=0 , maxOccurs=1 , and imported it, but it keeps showing me "1..1"...
How do I deal with these case ?? I don't want error red flags in monitor because of empty idocs...
Thanks.

Hi Bhavesh !
Thanks !
The problem is that because of mapping rules, the value of my target fields is SUPPRESS, not "empty".
For example, I have a file with this records:
A
A
B
A
"B" records should fill an IDOC segment, "A" not.
If I receive a file with only "A" records, for example 48 "A" records...then the IDOC segment, now, is receiving 48 SUPPRESS values...then the mapWithDefault doesn't work because they are SUPPRESS and not EMPTY.
Any ideas?
Thanks,
Matias.

Converting a flat file to IDOC

Greetings to All,
I have a requirement where i need to convert an IDOC (flat) file to IDOC.
the idoc is SHPMNT04.Presently i am trying to implement it using FCC at the sender side as the flat file is fixed length type.
Can any one suggest me a better method like using XSLT or Java mapping which could make my work smarter as i am Finding it very difficult to count and write the FCC for the IDOC which is have more than 60 segments.
Any help will be greatly admired.
Thnaks,
Anika.

Hi
I am still having a doubt if this method will work on real time scenario.I mean i have to pick files
from an 3rd party FTP location (polling and picking as and when i get a file starting with say
ABC*.txt).Added to this there will be issue related to the volume of file(1000 per day),will that create
any performance issues.
It is now that you are sharing the complete scenario/ problem , just have a glance from your first post at the top & the replies, because its the problem statement that steers the discussion.
Making the files available for the Report is a seperate task. You have to develop FTP-to-File XI scenario (or regular ftp process to send files across, which normally will not be allowed in XI server), I dont see any other way, if any, I 'assume' that it might complicate the situation.
Performance - it is not something to do with your scenario alone, but the overall system load, configuration etc. (b.t.w 1000 is normal)
Can we schedule a job for running the report periodically?
Yes, scehdule a batch job calling this Report (with necessary variants) with required frequency or exact time (if there is any agreement with sender)
I have started a POC
I appreciate that, best way at this moment. you can reverse engineer from the errors to configure your scenario. for any reason,if you think it does not work, you can always stop and/or look for different solution.
need your help
- Definitely I will share my thoughts, if time permits
how will i get the flat file xml(IDOC) in the source side
do you mean the source structure, you can use the same structure as your target.
once you are convinced with your solution approach, then it is better to close this thread & start a new one with new issues, for more views & suggestions and better readability.
@Rajesh - I appreciate your efforts to solve the issue , but the below is not correct & possible, w.r.t this issue
Here what you need is to do configure File Sender CC with NFS protocol.
Regards
Vishnu

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

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

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

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

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

My desktop files and folders no longer appear on the screen. I think this is a result of an iPhoto updating. It appears (from getting info) that now Desktop is being treated like a normal file for which an application to open it must be supplied. Help?

My desktop files and folders no longer appear on the screen. I think this is a result of an iPhoto updating. It appears (from getting info) that now Desktop is being treated like a normal file for which an application to open it must be supplied. Can anything be done? Incila

You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
You need to get a new computer or a refurbished one.

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

Normal File to IDOC

Similar Messages

Maybe you are looking for