File to idoc bypass scenario

hi all
I am doing file to idoc bypass scenario....i have to send file containing
EDIDC segment to respective idoc.I have used the idoc name as interface and its also successfully picking the file but while receiving the idoc receiver is showing some error.in sxmb_moni its showing error as obligatory field eiedk01 is missing while its persent in the pay roll of the messege...........please guide me in bypaas
can i check my message expect sxmb_moni .
my receiver adapter is IDOC
sender adapter is XI........
regards
saurabh sharma

Look into the replies by Bhavesh in this thread.
https://forums.sdn.sap.com/click.jspa?searchID=3098859&messageID=3484218
Regards,
Jai Shankar

Similar Messages

Doubt about RFC Destination in FILE to IDOC Async scenario

hi
In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
Any specific reason.
Thanks in advance.

First you need to have a clear understading of how the idoc adapters works.
In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
Hope this answers your ques.
cheers
*Raj*
*POINTS IF SATISFIED WITH ANSWER.

Big Doubt.. Help pls.. Urgent.. File to IDoc (Bypass)

File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.
Hi Bhavesh and all,
I done file to idoc scenario (Bypass)
From the above thread i have hardcoded my XML file by inserting BEGIN
and Segment = "1" in each of the new segment.
Since it is a bypass scenario.. when it reach to production , the idoc -xml will come from one of the tool without having these BEGIN and SEGMENT = "1".
Still XI will receive it??
Because my doubt is i harcoded the XML file and finished my developement.
Now iam getting the doubt that once they do testing in QA server..the XI will process it and not ?
Can we able to achieve this even without BEGIN and SEGMENT = "1" ?
or
those fileds are mandatory?
Pls suggest me .. its urgent.
Regards
Seema..

Hi Seema,
>> Can we able to achieve this even without BEGIN and SEGMENT = "1" ?
or
those fileds are mandatory?
To post an idoc to R/3 system this fields are mandatory.
>>From the above thread i have hardcoded my XML file by inserting BEGIN
and Segment = "1" in each of the new segment.
Since it is a bypass scenario.. when it reach to production , the idoc -xml will come from one of the tool without having these BEGIN and SEGMENT = "1".
Still XI will receive it??
As you are just routing it...just XI will poll the file and sends data to the idoc ( as the source and target structure are same).
Regards,
Prasanthi.

Generating partner profile for File to Idoc(CREMAS) scenario.

Dear friend,
Completed all the steps in SLD, IR and ID.
I do not know how to create Partner profile and I skipped this step.
While testing I got the error "Unable to convert sender service to an ALE logical system".
I think i got this error because I have not created partner profile.
Could anybody tell step by step process of creating partner profile including logical system names( Sender and Receiver)?
I have seen many blogs and i couldn't get clear picture on how to generate partner profile.
My sender system is XI server and receiver is R/3.
I have created RFC destination, Port also.
Thanks in Advance
Chiru

generally u create partner profiles using transaction WE20.
SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Partner Agreement (WE20).
go through this link for step by steps
http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b808e43d711d1893e0000e8323c4f/content.htm
http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp

File to Idoc Scenario using third party systems

hi,
Working with a File to Idoc Scenario. Been able to successfully define everything in IR / ID. However when I go to BD87 (reciever system) and see the status of Idoc processed - getting the error code 51 "Function Module Not Allowed: <Function Name>" . What could be the reason for this???
Have defined partner profiles in WE20 of type LS and also specified an inbound paramter in the post processing tab for partner profile. Are there any other settings I need to take care of to avoid getting that error.

Hi
I am giving u all the steps whioch are required for
File to IDoc Scenario
SM59- Create RFC destination
IDX1- Create a IDXPORT in idx1
IDX2-3. Import metadata of IDocs in idx2
Bus. service adapter specific Identifiers-->Logical sys name
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
SE16-Table name->LFA1 to check vendor has been created
Check have u followed all the steps.
Regards
Arpit Seth

IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

Hi All,
IDOC (Invoice) to EDI file scenario without Seeburger
Pls let me know if anybody have blogs for the same
EDI file to IDOC (Orders) scenario without Seeburger
Pls let me know if anybody have blogs for the same
Regards

Hi Rachit,
>>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
Also java code for IDoc to EDI have some problems:
1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
All the best
Regards
Suraj

File sender adapter:FILE to IDOC without BPM, can't see in SXMB_MONI.

Hi all
I have a FILE - XI - IDOC Async scenario without BPM.
I configured FILE sender adapter and IDOC receiver adapter. I made a mapping to transfer file data to the structure of IDOC.
Now when i am trying to load the file using command prompt, i cud see nothing in the monitoring. Whereas if i go to the communication channel monitoring of runtime workbench, i saw that CC is polling correctly and was reading the file also.
And also wen i saw in the processed folder which i mentioned in the CC configuration for the ARCHIVE DIRECTORY, i saw that file got transferred to the folder also.
I don't understand why i cant see anything in the monitoring.
Could anybody help me to rectify the problem. Is there anything i m missing ?
Regards
Naina

Rajesh/Amar
TCode:: SXMB_ADM->Integration engine configuration->specific configuration->runtime
Trace_Level = 3 then you can get all MONI PIPELINE Steps also
I did this change but cudn't see anything in SXMB_MONI.
This is how i have configured my process:
http://wiki.sdn.sap.com/wiki/display/XI/FiletoMultipleIDOCSplittingwithoutBPM
But instead of IDOC splitting i have simple FILE - XI -IDOC scenario.
I have configured everything exaclty the same way it is mentioned here. But for me the process is not visible at all.
I can't even see the first request message in the monitoring.
This is the message i can see in the communication channel monitoring:
2010-05-24 09:07:41 Success Channel CC_*: Entire file content converted to XML format
2010-05-24 09:07:41 Warning Channel CC_*: Empty document found. Proceed without sending message
2010-05-24 09:07:41 Success File "/xyz/ABC.txt" archived after processing
Is there any problem with the file and that could be the reason it cant convert the file to the request message MT_REQUEST and thus am not able to see anything in monitoring.
help me guys....this is a simple process and i m stuck...its frustrating
Regards
Naina

File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

Hi All,
I am doing File to IDoc scenario( Bypass) for Orders05.
File is picking succesfully and not posting the idoc in the SAP..
My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
but the error it is showing is " Obligatory node 'E1EDK01' missing in the structure ORDERS05 "
Please suggest me ASAP what is going wrong .
Thanks in Advance.
Regards
Seema.

The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
This is how it should look, ( check the parts in bold),
<?xml version="1.0"?>
<ORDERS05>
<IDOC BEGIN ="1">
<EDI_DC40 SEGMENT="EDI_DC40">
<DOCNUM>1</DOCNUM>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<CIMTYP></CIMTYP>
<MESTYP>ORDERS</MESTYP>
<SNDPOR>XXXXXXXXX</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC></SNDPFC>
<SNDPRN>XXXXXXXX</SNDPRN>
<RCVPOR>XXXXXX</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPFC></RCVPFC>
<RCVPRN>XXXXXXXX</RCVPRN>
<CREDAT>20070511</CREDAT>
<CRETIM>152803</CRETIM>
</EDI_DC40>
<E1EDK01 SEGMENT = "1"><BELNR>AAAAAAAAA123</BELNR>
</E1EDK01SEGMENT = "1">
<E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
</E1EDKA1>
<E1EDKA1 SEGMENT = "1"><PARVW>LF</PARVW>
<NAME1>international</NAME1>
<NAME2>Delhi</NAME2>
<ILNNR>2121211545</ILNNR>
</E1EDKA1><E1EDK02 SEGMENT = "1"><QUALF>001</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDK02 SEGMENT = "1"><QUALF>002</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDP01><POSEX>45</POSEX>
<E1EDP19 SEGMENT = "1"><QUALF>001</QUALF>
<IDTNR>00000000002150059</IDTNR>
<KTEXT>Reddy</KTEXT>
</E1EDP19><E1EDP19>
<QUALF>003</QUALF>
<IDTNR>5484218521214</IDTNR>
</E1EDP19></E1EDP01>
</IDOC></ORDERS05>
Regards
Bhavesh
PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

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

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

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.

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

Help needed in a file to idoc scenario

Hi all,
The scenario is file to Idoc via XI. The problem here is the input file might contain both the PO create and PO change in the same file.
Assume the first record is PO create and When we post this via XI there could be a delay for creating the PO in the SAP.
Meanwhile even if the second record (say that's the PO change for the first PO create record) gets processed parallely there could be a possibility of error saying that PO is not created.
How do we handle this in XI??.. If we use Queue Processing in IDoc adapter it'll guarantee only the delivery order and not the processing order if I'm right?.
Please guide.

Saravanan - IDoc preocessing can be handled by serialization. This will guarantee also the order of processing.
 
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm" target="n">SAP Help - IDoc serialization in XI</a>
 
 
Peter

File to idoc bypass scenario

Similar Messages

Maybe you are looking for