File to IDOC .. Look up Problem.

Hi Experts,
Iam doing file to Idoc scenario .. In which iam sending PO Response (ORDERS) from fie to idoc.
Source
File
Target(LSname)
R/3 (LS356)
R/3 (LS357)
R/3 (LS358)
Code
A    ( For LS356 )
B    ( For LS357 )
C    ( for LS358 )
Delivery ID
2536
2537
2538
GLN Code : 58899653
I have 4 fields in my look up table ..
CODE
GLN CODE
Delivery ID & Logical system
Using CODE and GLN Code as lookup key ---> I need to get the value of Delivery ID and Logical System.
So taking Delivery ID and LS name as key .. My source file will go to the corresponding R/3 system.
Its urgent .. Please respond asap.
Thanks
krupa.

Hi,
The problem is i cant write as static condition in receiver determination.
My Scenario is File to Idoc -- ( One legacy system to any of the 3 R/3 systems).
According to my requirement i need to write some 2 look ups
Delivery Look up table
CODE,    GLN Code,        Delivery ID,    LogicalSystem
A,           58899653,      021085,      LS356
B,           558899653,     021083,      LS357
C,           58899653,      021082,      LS358
Using Code and GLN Code as lookup key ---> get the value of Delivery ID and Logical System
IdocCtrlLookup
Purpose: To read the IdocCtrlLookup file to populate the Idoc control segment
valid control record has to found in IdocCtrlLookup file for Delivery ID
Delivery ID     Sender Port    Sender partnernumber        RX Port    RX partner num
021085      SAPGD2        GD2DVRC103                A000000046     GTEHHLD01
021083      SAPGD4        GD2DVRC122                A000000048    GTEHHLE01
021082     SAPGD4        GD2DVRC122                A000000047   GSEHHLE01
Please help how i can write the lookups and also how can i determine the Rx system dynamically with the above scenario.

Similar Messages

File-to-Idoc - field population problem.

Hi All,
Im getting the following problem.
My scenario is Filetoidoc.
Problem:
In the interface mapping Im able to see all the values are populated correctly for Idoc.but when I see in IDX5 or SXMB_MONI one value instead of populating correctly replacing , in that field.
Im using Java mapping program also to convert the file in to desired structure.
Thanks in advance.
Venu.

Hi All,
The out put from the above java program is.
<?xml version='1.0' encoding='UTF-8'?><ns0:MT_MeterReading_IntermediateForm xmlns:ns0="urn://MVP_SR3_01/MVP/MeterReading"><Recordset><H1><Recordid>H1</Recordid><RouteNumber>10151G</RouteNumber><MetReaderId>002</MetReaderId><TotRead>000015</TotRead><TotDevUploaded>000016</TotDevUploaded></H1></Recordset><Recordset><H1><Recordid>H1</Recordid><RouteNumber>10151G</RouteNumber><MetReaderId>SYSADMIN</MetReaderId><TotRead>000000</TotRead><TotDevUploaded>000000</TotDevUploaded></H1><Item><D1><HMetReaderId>SYSADMIN</HMetReaderId><HTotDevicesUploaded>000000</HTotDevicesUploaded><AccountNumber>6205</AccountNumber><MeterReadCode>0000001495</MeterReadCode><ReadDate>20060819</ReadDate><TroubleCode></TroubleCode></D1><D2><ChgdSplInstr>IN FOOTPATH DOG BITES information for service order</ChgdSplInstr></D2><U2><Data>33333300100451</Data></U2><UC><Data><u>SKIP TEST COMMENTS FROM METER READER FOR 4000734 MRo with RR '09'</u> </Data></UC></Item></Recordset></ns0:MT_MeterReading_IntermediateForm>
In abobe result last Data field value is populated correctly . the above result is from interface mapping.
but when the idoc is generated in XI. I'm unable to see the value.
Thanks,
venu.

File to IDoc - Partner No. problem

Hi,
I am trying to sent an IDoc to ERP system from PI. I made all configurations but I get an error in ERP in we02. It says that the Partner No. is incorrect. When I look at the Partner No. I see that it has the entry "TODO". But it must be the system name, like xxxclnt400
Why is PI sending the Partner No. as TODO??

Hi Chris,
Ensure that there are no changes done in SLD.
please check the receiver agreement object and field - header mapping - sender service
is it the same as with other flows ? you can put there the business system which has the correct
logical system name in SLD - so it will go correctly to ERP
Check whether the control record data is taking from the Payload.
Thanks,
Edited by: Hareenkumar on Nov 25, 2010 1:25 PM

Multi mapping.. is it possible File to Idoc & FIle .. its urgent?????

Hi All,
File to Idoc & File.
I need to pick the file and i need to do multi mapping, so that from the file we can generate
one idoc which has to go to SAP and
one acknowledgment's file and sent back to partner.
Based on the below blog, looks like we can't use Idoc adapter when the target message is Idoc using Multi mapping.
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Can anyone suggest me how i can achieve this scenario without using BPM.??
Regards
Seema.

Hi,
The Multi mapping is possible without BPM but not for IDOC as its not part of Java Stack. IDOC adapter is on ABAP stack.
As Raj have suggested,
You could create two different Mappings one for file to IDOC and another for file to file as an acknowledgment.
In Receiver determination you need to use multiple receivers as IDOC --R/3 receiver and the File receiver system.
It will create the IDOC as well as push the acknowledgment to file also.
But incase if you get any problem with sending the IDOC then also you will get successful acknowledgment via file. So directly there will not be any relation between these IDOC and File receivers as an delivery recipt of IDOC.
Here either you have to use the IDOC acknowledgment feature or BPM or Alert notification to get the exact notification about the IDOC posting to receiver system.
Please refer below links
1. IDOC acknowledgment
This Feature is Available under SP 18 and we are on SP16
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
Check this document on handling IDOC acknowledgements. This might give you some pointers.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
This Feature is Available under SP 18 and we are on SP16
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
Check this document on handling IDOC acknowledgements. This might give you some pointers.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
How to Handle Acknowledgments for IDoc (NW7.0)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
IDOC acknowledgements
2. BPM
File to IDOC with BPM
File to idoc with BPM
Problem in BPM implementation
Use Aleaud in BPM
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
3. Alert Notification
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
Thanks
Swarup

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.

Strange Problem.. File to Idoc... RCVPOR is missing in control Records.

Hi All,
File to Idoc:
Sender :
Party : PT_ABC
Business Service : BS_ABC
Note : I provided the LS name(PARTABC) for BS_ABC Under Adapter Specific identifiers.
Receiver :
Business system (Without party) : BS_DEV_R/3
In the IDOC receiver communication channel, I enabled the options
-Apply COntrol records from Payload
-Take sender from Payload
-Take Receiver from Payload.
Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
File is picked and message processed and when i checked in SXMB_MONI,Idoc control records are showing clearly like below.
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<CIMTYP>ORDERS05</CIMTYP>
<MESTYP>ORDERS</MESTYP>
<STDMES />
<SNDPOR>SAPDPI</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>PARTABC</SNDPRN>
<RCVPOR>SAPDL1</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>DEVSAP</RCVPRN>
</EDI_DC40>
But the Idoc is reached to R/3 with status '56' .And in the control records.. the receiver port (SAPDPI) is missing.
I dunno what happened.When i cross checked, the remaining interfaces are working perfectly.
Any idea whats going wrong?
Regards
Deepthi.

As a matter of fact it is not strange at all:)
It means you need to check the partner profile in the receiving r/3 system. This type of problem occurs because you need to define the partner profile PARTABC to the IDOC ORDERS05. If this association is missing you would always see the RCVPOR missing in the destination system.
Also you have mentioned that "Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
This is because for the BS_ABC sender service you must have a logical system associated; you can check the same by looking at the adapter specific identifiers. In your case I believe it is empty so the system can't find the logical system for it.
Thanks
Abinash

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

Problem in : File to IDoc

Hi,
   I am working on a file to IDoc scenario.The logical name for the sender system is maintained in the SLD.I am not populating the control record in the mapping.
   When am executing the scenario, the status message in SXMB_MONI is showing request processed but in the outbound status it is showing error and the message displayed is " EDI Partner Profile not found ".
   Can anyone help me out with this.
Thanks and regards,
Pravesh Puria.

Hi,
Transaction :WE20
Choose partner Type : LS
Give partner Number ( give Logical System Name ( Sender System ..check with basis or Bd54 Transaction .if the sender is Business Service ..give XI Logical system)
and Inbound parameter add the Idoc and give the process code and save.
ur problem will solve..
let us know if U need any
regards
Ram

File 2 Idoc - Problem

HI,
my file 2 Idoc scenario looks fine and the file sender adapter is working (shown in adapter monitoring).
But there is no IDoc output.
q1: Are there any possibilitiy to monitor this ?
There are no messages in the message monitoring.
q2: my file content conversion looks like
KeyFieldName = ID
KeyFieldType = Integer
DTHEADER.fieldnames: ID(keyvalue),Header1,Header2,Header3
DTHEADER.fieldSeparator: ,
DTHEADER.endSeparator: 'nl'
DTHEADER.keyFieldValue:1
DTPOS.fieldnames: ID(keyvalue),Pos1,Pos2,Pos3
DTPOS.fieldSeparator: ,
DTPOS.endSeparator: 'nl'
DTPOS.keyFieldValue:2
DTSUM.fieldnames: ID(keyvalue),Sum1,Sum2
DTSUM.fieldSeparator: ,
DTSUM.endSeparator: 'nl'
DTSUM.keyFieldValue:3
Can you tell me how the flatfile looks like ?

Payload: Inbound File
<?xml version="1.0" encoding="utf-8" ?>
- <ns:FILEINPUT_MT xmlns:ns="http://......./BG_File2IDoc">
- <Record>
- <DTHEADER>
<Header1>123</Header1>
<Header2>456</Header2>
<Header3>789</Header3>
</DTHEADER>
- <DTPOS>
<Pos1>456</Pos1>
<Pos2>457</Pos2>
<Pos3>458</Pos3>
</DTPOS>
- <DTSUM>
<Sum1>444</Sum1>
<Sum2>555</Sum2>
</DTSUM>
</Record>
</ns:FILEINPUT_MT>
Payload: Outbound IDoc
<?xml version="1.0" encoding="UTF-8" ?>
- <ZSTCMP01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>/</TABNAM>
<DIRECT>/</DIRECT>
<IDOCTYP>/</IDOCTYP>
<MESTYP>/</MESTYP>
<SNDPOR>/</SNDPOR>
<SNDPRT>/</SNDPRT>
<SNDPRN>/</SNDPRN>
<RCVPOR>/</RCVPOR>
<RCVPRN>/</RCVPRN>
</EDI_DC40>
- <Z1STCMP_HEADER SEGMENT="1">
<UZEIT>0011</UZEIT>
- <Z1STCMP_ITEM SEGMENT="1">
<ROUNDING_VALUE>1</ROUNDING_VALUE>
</Z1STCMP_ITEM>
</Z1STCMP_HEADER>
</IDOC>
</ZSTCMP01>
File: <Header1>123</Header1> is mapped to
Idoc: <Z1STCMP_HEADER FIELD1> but this one is missing

Problem in executing File to IDoc Scenario in XI

Hello,
I am Working in HR Payroll module and new to XI.We are implementing File to IDoc Scenario in XI.When I place the flat file in the application server the file is read but the contents of the flat file is not getting posted to the IDoc.The constant values defined for IDoc in Mapping program is getting posted .I am not able to trace the error.
kindly help me out in resolving this problem.IF there is any way of debugging the entire process please let me know.
Thanks & Regards,
Malathi V.

hi,
check this blog to test your mapping,
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Next, check your INBOUND MESSAGE in SXMB_MONI and check if the content conversion has been perfromed as expected.
these steps will help you reason out the cause of your problem.
Regards,
Bhavesh

XI Problem: File to Idoc Scenario - IDOC_INBOUND_ASYNCHRONOUS

Hi,
I'm having problems with inbound IDOCS in R/3. The idocs from XI are sent as tRFC using the FM IDOC_INBOUND_ASYNCHRONOUS and this is a problem because i have like 200 or 300 idocs to be sent at the same time and each IDOC takes like 5 minutes to process, hence the system crash due the amount of simultaneous logins (error message ThISend: ThRollout ).
I need to fix this problem using some kind of serialization and the use of the function module IDOC_INBOUND_IN_QUEUE.
Does anyone know how to achieve this?.
The scenario configuration in XI and R/3 is as follows: (PI 7.0 SP15) - (R/3 SAP ECC 6.0)
File to Idoc.
Sender CC->
File content conversion
Exactly once in order
Receiver CC->
IDOC protocol
Queue Processing
R/3 Partner profile config.
Message type BOMMAT
Trigger immediately
Thanks.

Hi,
You have to split the messages in the sender file adapter, by using the parameter "Recordsets per Message".
I hope that it will solve your problem. Please see the below link, it might be useful to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
Rajesh

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

HI I have a file to IDOC scenario,
data from file is mapped to IDOC structure,
there is a field in the IDOC structure <name> size 50, and after that there is a field called <ID> size 4,
i populate the structure and send it to R/3, there when i see it in we05, the IDOC is seen as containing the values of both <name> and some parts of the field <ID>..in the field <name>..........
though in sxmb_moni, the IDOC structure produced is all correct

i have tried all the things u mentioned..but its not working...
i reimported everything.....refreshed everything........
somehow its taking the size as 25, and if i keep the field empty, even then it takes some values from the next field.......
is there any other places to look for............
what are the function module that i can debug to see the problem

Problem with File to IDOC scenario

Hello,
I try to implement our first scenario to IDOC.
In TOC SXMB_MONI I have to errors
1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
Any idea how I can solve this problems?
Elad

HI,
I think u have not done the configuration at the R3 end....
Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

File to idoc scenario problem

I am trying to do FILE TO IDOC scenario, i am getting error called, UNABLE TO CONVERT SENDER SERVICE TO AN ALE LOGICAL SYSTEM.?
could anybody solve this problem?

Murali,
You get this error when Adapter specific attributes are missing..
Maintain Adapter Specific Attributes for business system in Integration directory.
Select your business system...Then select Service-->Adpater Specific identifiers.
from right hand window..
Set Logical System ID(of R/3 system), R/3System ID and client.
Let us know if you need more details.
Nilesh

File to IDOC .. Look up Problem.

Similar Messages

Maybe you are looking for