Hi experts- RFC look up in IDoc to File Senario

Hi,
I have req with Idoc to file (delivery Idoc).
But i need to get user name of sender(r/3) into file which is not available in idoc type.
I think we can do through RFC lookup functonality.
Can u tell me exact procedure and code for this?

Hi,
Check some links on Look ups.
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
Look ups.
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
/people/francesco.bersani/blog/2007/03/05/data-lookup-optimized
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
Use this crazy piece for any RFC Mapping Lookups!
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
SAP XI Lookup API
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
Lookups in XI made simpler
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
Lookup - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
DB lookup - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0
Lookup's in XI made simpler - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
How to check JDBC SQL Query Syntax and verify the query results inside a User Defined Function of the Lookup API -
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
/people/prasad.illapani/blog/2006/10/25/how-to-check-jdbc-sql-query-syntax-and-verify-the-query-results-inside-a-user-defined-function-of-the-lookup-api
Lookups - /people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
Lookups - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/content.htm
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
Lookups with XSLT - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72
/people/sravya.talanki2/blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
How we have to create the lookups?
Check this weblogs with some screenshots on how to achieve this:
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
/people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
Regards,
Phani
Rewar points if Helpful

Similar Messages

RFC Destination type for IDOC to FILE

Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeff

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

IDOC to File Senario - Mapin error

Hi,
   I am trying IDOC to File Senario using XI. I am stuck while message mapping.
I need to map IDOC : MATMAS.MATMAS01 (Material numbaer and Matrial description ) to File.
I have imported IDOC : MATMAS.MATMAS01 in IR.
Created target Data type/ message type/ message interface:
Target Data type structutre:
DT_Matdesc    Complex type (Node)
Matno             Element                     0...1
Matdesc          Element                     0...1
Using graphical message mapping I am trying to map the the Fields from Idoc structure to Target structure, But I am geting Internal error. Can anyone help me out.
Waiting for the reply.
Thanks in advance.
Shweta.

Hi,
    I am not able to activate Message Mapping. On activation it gives below error.
Error:
Internal error while checking object Message Mapping MM_Matdesc1 | urn:namespace:santosh (TRAINING, VERSION 1.1 of ssingh); see details
Details Error:
Internal error while checking object Message Mapping
MM_Matdesc1 | urn:namespace:santosh (TRAINING, VERSION
1.1 of ssingh); see details (CHECK_EXCEPTION)
Internal error while checking object Message Mapping
MM_Matdesc1 | urn:namespace:santosh (TRAINING, VERSION
1.1 of ssingh); see details (CHECK_EXCEPTION)
Compilation process error : CreateProcess: null\bin\javac
-J-Xmx512m @D:/usr/sap/RXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map544be4d0b04a11dbb43e005056b72d1d/O1170151922621.txt
@D:/usr/sap/RXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map544be4d0b04a11dbb43e005056b72d1d/S1170151922621.txt
error=2
I am not able to trace out the error.

Problem : Idoc to File Senario,overriding the segments in Idoc,on condition

Hello People,
Idoc to file senario.
There are fields in the Idoc which i want to populate, if that particular Idoc is going to XI. Can u tell me how can i check this condition .. ???

you dnt have control fro r/3 to check if the IDOC is reached to XI then XI creates the file then update few thing...
make sure the IDOC is reached to XI using the port if IDOC is using some port...but if the file is getting places in server using AL11 you can check that....in your condition you can check if file is exist in the target folder thn update .....insead of checking if IDOC sent to XI--XI creating a file...i doubt you have that flexibility...lets wait for other reply what they have to say?

IDoc to file senario

Hi,
This is an idoc to file senario and in this senario,
PI receives multiple IDocs in a day and at end of the day PI needs to build a file with one header record, one detailed record for each IDoc and one tril record at the end file.
Could you please suggest me how can I achive this.
For better understanding i am providing file structure.
HDR RECORD
DETAILED RECORD1
DETAILED RECORD2
DETAILED RECORD3
DETAILED RECORD4
TRIL RECORD with total idocs proccessed.
Thanks in advance...
Sreeni

Hi,
PI receives multiple IDocs in a day and at end of the day PI needs to build a file with one header record, one detailed record for each IDoc and one tril record at the end file.
Can u please give more details on this...
If the IDOC's are coming multiple times in a day say 100 times and each IDOC will have multiple IDOC's then what do u want...
I think u have to combile multiple IDOC's in source to a single IDOC and send at a time.. If not PI has to store these IDOC's and send them at the end of the day...
Please give exactly what u want to achieve...
Babu

Problem : IDoc to file Senario, multiple segments in the IDoc.Intresting !!

Hello People,
Just a very good problem, to put your brains work.
The senario is Idoc to File.
Now Suppose the structure of IDoc is in such a way.
segment1 - fields A, B, C, D --- >> Single
segment2 - fields E,F            --->> This segment can come multiple times.
segment3 - fields G, H          -
>> Single
segment4 - filds I, J, K          -
>> Multiple.
Now the format of the file is Fixed Length.
The record will be inserted Row wise.
Let us assume that the number of segments are.
segment1
segment2
segment2
segment3
segment4
segment4
All segments are at the same level.
Example of file :-
A B C D E1 F1 G H I1 J1 K1
A B C D E2 F2 G H I2 J2 K2
So please let me know, what kind of structure should i create in my repository for the Target and also let me know , the File content Conversion part ..
Thanks in Advance.
Harpreet.

hi,
Repeat the row for each segment and in the (i)th iteration of the map it to the (i)th segment from the input. Now in your FCC, it will be like writing a normal fixed length conversion.
For e.g. you target structure will look somewhat like this.
Document
Recordset
     Record(i)
       FieldA
       FieldB
       FieldC
       FieldD
       FieldE(i)
       FieldF(i)
and so on....
Cheers,
Sarath.
Award if helpful.

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

IDoc Flat File Needed

Hi Experts.
I need the Idoc flat file for Delfor01(delivery schedule).
Advance Thanks.

Hi Bala,
Follow the procedure
IDOC to XML Convertion using ALE Interface
1) Send an outbound IDOC data(MATMAS) to a flat file(XML) on client1(SENDER).
- Create File Port (WE21) of XML Type for outbound file.
- Specify the Physical directory and file under the Outbound File tab
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
A sample scenario for idoc generation
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
Now go to the physical directory and check your idoc converted as an XML File.
Note enter required message type
OR try this
Just pass the IDoc Document no in the FM - IDOC_XML_TRANSFORM.
IDOCS_OUTPUT_IN_XML_FORMAT
IDX_IDOC_TO_XML
it will transform the IDoc in XML format
Regards,
Sridhar

Error in IDoc to file scenario

Hi Experts,
I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please suggest me in this issue.
Thanks,
Bhuvan.

Check this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
You might want to refer to the SAP NOTE: 316877
Regards,
Ravi

Problem in idoc to file mapping

Hi Experts,
I am doing a idoc to file scenario...
There is a single idoc with multiple header and line items .
I am using multi mapping for header and lineitems.
The problem i am facing is regarding the occurences in target strucure...
at which level they should be specified so all the headers come in one strucure and line items in another...or should the occurences be o to unbounded at each field level.
Kindly help me regarding the same ...

hi
i have the same scenario : IDOC (orders) to Flat File. can you plz help in mapping. the input format to XI is in the given way
idoc
    a1---(0-1)
    a2---(0-1)
       b1--
    a3---(0-1)
       b1---(0-n)
         c1---
       b2---
         c1---
    a3---(0-n)
       b1---
       b2---
    a3---
      b1---
      b2---
    a3
      b1---
      b2---
i have created the same output DT in the same format (parent-child) for flat file. and my questions are
1. is that correct, do i need to create the same DT as the above idoc (like parent and child) or different?
2. how to map the idoc fields to my file DT..do i need to map parent to parent and child to child...or different.
plz help me out
Thanks
ram

IDoc to File interface

Hi Experts Team,
My scenario is IDoc to File interface. I need to create 12 different files based on the Plant code (WERKS). At the end of the day, i need to ftp the file to different locations. How can I do the design and is there any need for BPM here?
Please explain..
Thanks & Regards,
Kanda

Hi S.P ,
You may use the variable substitution functionality of receiver file adapter and can generate the file based on the xml payload content which contains your WERKS field.
You may refer the following blogs for the understanding of the concept.
An interesting usage of Variable Substitution in XI
Thanks & Regards
Prabhat

IDoc to file- How to include conditions in Interface determinations

Hi,
In interface Determination i am trying to add the conditions based on IDoc structure field value. But when i clicked on Condition editor i don't find Idoc stucture in editor XPath.
Please suggest me how i can add the condtions in the Interface determination in IDoc to file Senario.
Thanks in Advance...
Regards
Sreeni

Hi Sudhir,
I have tried as you mentioned, but still its not working. Below i am providing my inbound payload.
Could please let me know how i have to mention in condition editor to refer the IDoc field
ZGHIER01/IDOC/Z1GLHIERH/SETNAME
<?xml version="1.0" encoding="UTF-8" ?>
- <ZGHIER01>
- <IDOC BEGIN="1">
 + <EDI_DC40 SEGMENT="1">
 - <Z1GLHIERH SEGMENT="1">
 <CATEGORY>GLHIER</CATEGORY>
 <SETNAME>PEGPL_AG</SETNAME>
 + <Z1GLHIERD SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 </Z1GLHIERH>
</IDOC>
</ZGHIER01>
Thanks & Regards
Sreeni
Edited by: Sreenivasulu Reddy jonnavarapu on Dec 12, 2008 10:39 PM

IDoc to File with different file name and data based on the IDoc header dat

Hi,
I got a requirement to implement IDOC to file senario. In this the Converted file should have the file name and file content based on IDoc Header data. Means If one of the IDoc header field value is
'A' - then the file name recieved by reciever system should be 'A.txt' and with the columns A B C D F.
'B' - then the file name recieved by reciever system should be 'B.txt' and with the columns C D F.
In both the case IDoc message type is same.
Please suggest me what i need to do to achieve this.
Thanks in Advance. ...
Regards
Sri

Hi,
As per my requirement, we need to create one file for each IDoc based on IDoc header data. SAP program generates 10 IDocs for each run. All 10 IDoc's message type is same. Each IDoc has one header record with the file name. Base on the name in the IDoc header record, file needs to be created with different columns and file name. Means..
IDoc 01- Header Description contains 'A' - than file will be generated should have name as 'A.txt' and columns 'parent' 'child' 'descripion'.
IDoc 02- Header Description contains 'B' - than file will be generated should have name as 'B.txt' and columns 'Name' 'Department' 'Description'.
IDoc 10- Header Description contains 'J' - than file will be generated should have name as 'J.txt' and columns 'Order No' 'Materail' 'Description'.
Hope this will give more clarity on my requirement. Please let me if you are still not clear on requirement.
Thanks for your all help..
Thanks & Regards
Sreeni

IDOC to IDOC....... RFC look up

Hi Friends,
Iam new to SAP XI and have some questions.Answers to this query will be my pleasure.
my scenario:
sender :idoc1 (delivery)
receiver: idoc2 if customer present
 else idoc3 to create "customer" and then idoc2 to create "sales order"
Message mappings:
1 for idoc1 to idoc2
1 for idoc1 to idoc3
and 2 interface mappings for the above message mappings.
Please explain me how can i use one mapping if condition is false and then mapping2
and how to use second mapping if condition is true.
Also given below is mapping for a field .Please check and explain:
source field:E1ADRM1-PARTNER_ID
Mapping/Transformation rule:E1ADRM1-PARTNER_Q = 'WE' Select KUNNR from KNB1where ALTKN = E1ADRM1-PARTNER_ID and BUKRS = 'GR11' Value = KNB1-KUNNR and check that KNA1-STCD2 = 999839383 with KNA1-KUNNR=KNB1-KUNNR if no entry found in KNB1customer must be created
Target field: PARTN_NUMB
Please explain.I got an answer previously that i have to use RFC look up, if so please explain where and how to write the RFC look up.
Thanks in advance,
Harish.

Hi Kinthali,
I think I am not getting your question correctly...
You need to map from Idoc1 to idoc2 or if idoc 2 is not the idoc1 to idoc3... right??
>>Please explain me how can i use one mapping if condition is false and then mapping2 and how to use second mapping if condition is true.
Which condition are you talking about here?? Check the condition in the interface determination and then choose the needed interface...
Regards
Suraj

Hi experts- RFC look up in IDoc to File Senario

Similar Messages

Maybe you are looking for