Idoc to File scenario using Party

Hi All,
I have to configure Idoc to File scenario .This file needs to be posted in EDI Subsystem .My receiver partner type is LI.That means i need to use Party here.So please let me know the step by step solution to do this.Specially i want to know the configuration in Party Identifier and Receiver Communication channel Identifiers.
How the control record values from idoc are transferred to EDI File structure and how will XI identify one of the many customers to post the file.
All valuable suggestions will be rewarded the points.
Please send me the documents for such scenario with screen shots.

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

Similar Messages

Problem : Idoc to File scneario using Party ..!!

Hi ,
lam doing Idoc to file scenario by using party.
Partner type for receiving system is "LS".
1. when I use Party for my sending system , the message is not processing showing error as " No receiver could be determined"
2. When I use the sending system as Without Party and the receiving system as Party,the message is processing.
Questions:
1. We should not use Party for the sender system when the partner type is "LS"??
2. Can we use the Party for my sending system when the partner type is "LI" or "KU".?
If yes, Do i need to do any Identifier settings in communication channels or at Party side like ALE#KU or ALE#LI??
Please clarify the main question whether can i use party for my SAP system when the partner type is "LS" for outbound scenario(Idoc to file).
Waiting for your answers.
Regards
Krupakar.

Hi,''
a SLD registration of DUMMY system for every Party
1. We should not use Party for the sender system when the partner type is "LS"??
The only way I know is to make a Dummy system in the SLD with a LS, which I can use in the headermapping of the receiver agreement.
You could use pratner type as LS enven for party, but there no need as such because you could do this as per below steps also
it is not possible to have a logical system within a service, that belongs to a party. Any entries you are doing here, are ignored.
2. Can we use the Party for my sending system when the partner type is "LI" or "KU".?
If yes, Do i need to do any Identifier settings in communication channels or at Party side like ALE#KU or ALE#LI??
Yes you can use the Party for sending system for LI or KU, You difinately need to setup the identifiers for it.
Usually an IDOC which is received from a customer should have a sender type LI or KU.
A workaround for your problem: For each service that belongs to a party create a party-less service with the logical system and do a header mapping. You need not maintain this service in the SLD. Just create a business service.
If the field SNDPRT contains LS, the service is a logical system and the sender party remains blank.
If it is not a logical system, a party is determined by means of the alternative identifiers (for the party). The following are used as identifiers:
·        Agency is the sender service found
·        Scheme is ALE# + SNDPRT. If the field SNDPFC contains a value, the following is added: # + SNDPFC
·        Name is SNDPRN
These values are used to search across all parties. The party that is found is used as the sender party.
For Identifiers go through below link
http://help.sap.com/saphelp_nw04/helpdata/en/42/f3d027074e1bcae10000000a11466f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e1/63e03fc2269615e10000000a155106/frameset.htm
Let me know if you need anymore info.
Thanks
Swarup

Issues in IDOC to File scenario using bussiness service

Hi Team
I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent). The setting which have done on SAP side are as below
SAP SIDE CONFIGURATIONS
1. Created RFC destination : RFC_XI_SYSTEM
2. Created port : PORT_TEST
3. created logical system: IDOC2FILE
4. created partner profiles: IDOC2FILE
XI side configurations
1. Created RFC destination: RFC_SAP_SYSTEM
2. Created port : by using IDX1 t-code
DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
3. metadata: by using idx2.
DOUBT: here it is asking for IDOC type and source port, i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know, please find the SAP and XI system details below and suggest accordingly.
SAP system details
Client: 800
User name: sapuser
system id: DEV
system number:10
XI system details
Client:100
username:xisuper
system id: SXI
system numebr: 00
I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
Thanks in advance.
Raju

To complete your scenario successfully with better understanding of Idoc adapter
read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Alerts-Idoc to File Scenario using BPM

Dear all,
At the sender side,I am sending 2 Idoc's orders03,orders04 Idocs I am Merging in to single at my mapping level and sending to the respective receivers.
When even some error occurs at system level or application level,an alert must be sent to the respective valid receipents.
My question is,when creating the Alert Rule how to use the interfaces(orders03,04) (here I have multiple senders).
Is Alert rule required in BPM scenario's?if not let me know how alerts would be triggered for bpm scenarios.
Thanks,
Srini

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

FCC in receiver side in idoc to file scenario

Hi all,
           I am doing an idoc to file scenario using FCC .I am using FCC in receiver side ,but i am getting my output file in only one line while i want structre to be seprated by new line.for more information i am giving muy file structre.
Record
    header(1to1)
    data    (0 to unbounded)
    footer (1to 1)          header, data, footer are three structre which contain various fields.I have to use fieldFixedLengths as filed separator. I am also using endseperator as 'nl' but its not coming in new line.Please share ur views on this issue.
Regards
Neha

hi neha,
In your scenario
Recordset Structure header,data,footer
header.fieldFixedLengths    = 1,2,3, whatever it is
data.fieldFixedLengths      = similar to header
footer.fieldFixedLengths    = similar to header
header.endSeparator = 'nl'
data.endSeparator = 'nl'
footer.endSeparator = 'nl'
I guess you dont have to do any thing else.
Regards
Pushkar
Message was edited by:
        Pushkar Anand

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

IDOC to XML file scenario with party

Hi All,
I am developing a IDOC to XML file scenario with party in which I have extended the MATMAS idoc and configured the receiver FILE communication channel.
But its giving me the error *"No receiver could be determined"* with party. If I run the same scenario without the sender party its working fine.
And sender is my R/3 system under party P_Party and receiver is my third party system under P_Party.
Thanks in advance.
Gaurang

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier classifier
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
classifier attID classifierAtt
classifier destSourceMsg MainDocument
classifier showInAuditLog true
bic classifierAttID classifierAtt
bic destEncoding UTF8
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName AUTO
bic newLine true
bic srcEncoding UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
 <D_I01>00</D_I01>
 <D_I02/>
 <D_I03>00</D_I03>
 <D_I04/>
 <D_I05>ZZ</D_I05>
 <D_I06>CELORGS01</D_I06>
 <D_I05_2>ZZ</D_I05_2>
 <D_I07>AVX</D_I07>
 <D_I08>032008</D_I08>
 <D_I09>1718</D_I09>
 <D_I10>X</D_I10>
 <D_I11>00401</D_I11>
 <D_I12>000000008</D_I12>
 <D_I13>0</D_I13>
 <D_I14>T</D_I14>
 <D_I15>^</D_I15>
 <S_GS>
 <D_479>PO</D_479>
 <D_142>CLS01</D_142>
 <D_124>058895921</D_124>
 <D_373>20080320</D_373>
 <D_337>1718</D_337>
 <D_28>8</D_28>
 <D_455>X</D_455>
 <D_480>004010</D_480>
 <S_ST>
 <D_143>850</D_143>
 <D_329>800001</D_329>
 <S_BEG>
 <D_353>00</D_353>
 <D_92>SA</D_92>
 <D_324>4500005037</D_324>
 <D_373>20051110</D_373>
 </S_BEG>
 <S_CUR>
 <D_98>BY</D_98>
 <D_100>USD</D_100>
 </S_CUR>
 <S_FOB>
 <D_146>CC</D_146>
 <D_309>OR</D_309>
 <D_352>FREE CARRIER</D_352>
 <D_334>02</D_334>
 <D_335>FOB</D_335>
 <D_309_2>DE</D_309_2>
 </S_FOB>
 <S_ITD>
 <D_336>01</D_336>
 <D_333>3</D_333>
 <D_351>45</D_351>
 </S_ITD>
 <G_SN9>
 <S_N9>
 <D_128>L1</D_128>
 <D_369>GEN</D_369>
 <S_MSG>
 <D_933>TEST</D_933>
 </S_MSG>
 <S_MSG>
 <D_933>MESSAGE</D_933>
 </S_MSG>
 </S_N9>
 </G_SN9>
 <G_SN1>
 <S_N1>
 <D_98>BY</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 <S_PER>
 <D_366>BD</D_366>
 <D_93>Graham Crawford</D_93>
 </S_PER>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>BT</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>SE</D_98>
 <D_93>3M COMPANY</D_93>
 <D_66>92</D_66>
 <D_67>0000019591</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>ST</D_98>
 <D_93>SAMPLE</D_93>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SPO1>
 <S_PO1>
 <D_350>00010</D_350>
 <D_330>10.000</D_330>
 <D_355>EA</D_355>
 <D_212>10</D_212>
 <D_639>PE</D_639>
 <D_235>BP</D_235>
 <D_234>230-1812-01JDS</D_234>
 <D_235_2>EC</D_235_2>
 <D_234_2>A00000000000002</D_234_2>
 <G_SPID>
 <S_PID>
 <D_349>F</D_349>
 <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
 </S_PID>
 </G_SPID>
 <S_REF>
 <D_128>CO</D_128>
 <D_127>4500005037-00010</D_127>
 </S_REF>
 <G_SSCH>
 <S_SCH>
 <D_380>10.000</D_380>
 <D_355>EA</D_355>
 <D_374>002</D_374>
 <D_373>20051208</D_373>
 </S_SCH>
 </G_SSCH>
 </S_PO1>
 </G_SPO1>
 <G_SCTT>
 <S_CTT>
 <D_354>1</D_354>
 </S_CTT>
 </G_SCTT>
 <S_SE>
 <D_96/>
 <D_329>800001</D_329>
 </S_SE>
 </S_ST>
 <S_GE>
 <D_97>1</D_97>
 <D_28>8</D_28>
 </S_GE>
 </S_GS>
 <S_IEA>
 <D_I16>1</D_I16>
 <D_I12>000000008</D_I12>
 </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

Issues in SAP(Idoc)-XI-File scenario

Dear All,
I am working on SAP(Idoc)-XI-File scenario. But in the Receiver agreement i am not able to see the idoc in order to specify some conditions there.
Please suggest if I have to do any settings in order to specify some conditions in the idoc.
Warm Regards,
N.Jain

Hi nishu jain ,
U can specify the conditions in Reciever Determination.
1.Go to Scenarios
2.Choose your business scenario
3.Click Service without party
4.Double click Reciever Determination
5.U wil get screen in which there is a option called Configured Recievers.
6.Click there.then u wil get the screen with
Left Operand Op Right Operand
7.There u can specify the condition.
Reward points if u find this useful.......
Regards,
gyanaraj

IDOC to File scenario Configuraton settings

hi,
   I am doing IDOC to FILE scenario.I am sending IDOC from R/3 to XI and then to XML file.That mean smy scenario is as Follows ( R/3XIfile ) These are my queries
-->I have created RFC Destination from R/3 to XI.should I need to create RFC destination from XI to R/3 ( i mean In XI )??
-->I have created one Port in R/3 and I have linked that port with RFC Destination that i have created.here i am sending IDOC from R?# to XI...SO we call this PORT as SENDER PORT or RECEIVER PORT??
-->and DO we need to create PORT in XI also??is it require for my scenario??
-->DO we need to create Partner Profiles in XI also??
-->DO we need to create LOgical system in XI to represent the XI system?? (as we created LS in R/3 to represent sender system)
--->Here is my big doubt..
               when we test IDOC ..by sing we19 TCODE,
   We need to fill the corresponding details as below,
Receipent                                  Sender
Port                                              Port
PartnerNo                                      PartnerNo
PartnerType                                   PartnerType
my Doubt is,
-->>In which field we need to specify the Port that we have created in R/3..Receipent side OR Sender Side..?? and Why??
-->>Same for ParnerNo..where we need to specify the Logical system which we have created in R/3 should specify??Why??
Please give reply ASAP..with detailedexplanation..
points will be rewarded..
regards,
murali

HI
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD u2013 System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system names
cheers
reward poins if found useful

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

In idoc to file scenario, if XI system is down where do idocs pile up?

In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?

Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

Idoc to File scenario using Party

Similar Messages

Maybe you are looking for