FILE to IDOC settings
Hi all,
I am doing the scenario of file to idoc in which is it necessary to create RFC destination on both XI side and R/3 side. Clarify the settings required from XI to R/3 ..
regards,
kumar
This is expalined both the scenarios:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
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
Similar Messages
-
IDOC is posting with Errors in File to IDOC scenario
Hi,
I did the File to IDOC scenario for CREMAS . IDOC is posting with Errors .. i.e. in the status record it was showing 56- EDI: Partner profile inbound not available ..
If I manually process that IDOC in WE19 , then it was processing successfully.. and in the we19 it was showing Inbound Processing : Port Not Maintained but even though manually it was posting fine...
any ideas regarding this will be appriciated.....
Regards
BabuPlease check whether you had done the following assuming your doing File to Idoc
Settings in your Business service for the receiving system
Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
Settings in R/3
WE20 - Add the partner profile for the particular message type cremas and process code.
Your statement
" and that same logical system name had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
Please do mention R/3 Details in the receiver business service or system.
Thnz -
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,
muraliHI
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 -
PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario
Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of. -
ALE Configurations in File to IDOC Scenario
Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
<b>3. Unable to load metadata in XI.</b>
Now we are unable to test the scenario as it provides an error message in MONI as "<b>Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors</b>".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
NithiyanandamHello,
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 XI 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 #####+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 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.
With Regards,
Vidya.
*******Reward with Points if found useful -
File 2 IDoc ----- Process Codes
Hi Frnds,
I done one scenario between File 2 IDOC.
I am updating file system data in MATMAS IDOC.
Scenario working prperly, But i am unable to se the results in MATAMAS IDOC.
File adapater picking up tha data it sent IDOC.
how to see the Up dated data in to MATMAS,
Which process codes i need to execute
can any one help me out...
Regards,
Rajhi,
these are the process codes.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 6)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
Step 7)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
Thanks,
Vijaya -
** File to IDoc scenario - IDoc not created in target system
Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
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.
Thanks,
Satya -
No suitable sender agreement error (File -- XI -- IDOC R/3)
Hi All,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.
Have manged to complete teh IR and ID config as per the various threads in SDN.
I am using FCC in the Sender File adapter (which I assume will read the file data and convert to XML data). When this channel is activated, it gives me the error 'No suitable sender agreement found'.
As per various posts in sdn, this scenaruio may not need sender agreement as XI is finally using IDOC adapter to send data to R/3.
Am I correct in assuming that ??
Could you help point any potential missing config.
For your reference:
The comm Channel used to read file data is using File adapter (marked as SENDER/NFS/FCC/Integration server)
Appreciate your feedback.
Thanks
ShirinHi,
chk for ALE settings....
Steps for ALE settings:-
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
Step 6)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 7)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
Prashant -
How to get Idoc acknowledgment in File to Idoc scenario
Hi All,
Please give suggestions about the below mentioned scenario:
Scenario: FileXI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
Regards,
XIerPls go thruough these links also
Please see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
unable to import from SLD
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
<b>IDOC Acknowledgements</b>
R/3 IDOC ->XI-> ORACLE Error Handling
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
Regards
Abhishek Agrahari -
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
<b>File to IDoc</b> 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 -
Hi all
I dont know much about idocs. I am creating a file to idoc scenario. i have done with(hope so) all the other settings, design and configuration. BUt dont know how to do the mapping.how the control segment fields have to be mapped. what are the mandatory fields in idoc?Hi Aarthi,
You can leave the control records of the Idoc blank since XI fills them up. This is because XI would be the sender for the idoc. If you select "Header mapping" then you have to map control records else not.
Also in the idoc data segments all fields with a red dot are mandatory. If you do not have a field from the file to map with the mandatory idoc field then either you can suppress it or map it to a constant.
Hope this helps.
Regards. -
Hello Guru's
Can any one send methe link where i can find the Idoc settings related material or screenshots.
regards
aryanHi,
check the following links:-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
http://help.sap.com/saphelp_nw2004s/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
/people/sriram.vasudevan3/blog/2005/09/01/mdm-55-data-distribution-using-sap-xi
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/2a65ec507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards,
Archit -
Scenario: File To Idoc & Idoc To File
Hi,
Can any body explain file to idoc and idoc to file scenario's with screen shots which incluses setting at R/3 side and XI side. Starting from SLD to ID.
Thanks in advance.
Regards,
Prems.SAlso u can follow the settings on Xi and R/3 side
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 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 name. -
can SDN provide me guidance to make a file to IDOC scenario, specially the settings at the XI and at the receiver SAP R/3 side.....
i m new to XI so, setting details are important,HI
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 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 name.
cehck out these blogs
/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/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
-- /people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i - here check the part 1 and 2 examples with all screen shots.
-- File-XI-IDoc Scenario
Message was edited by:
Anu Ram -
Hi Experts,
I am working on the scenario like File-Bapi-Idoc
1) Getting the file from external system, in the file
If the Sonumber is populated then need trigger an Bapi_change
and after getting the response flag as 1 from Bapi then have to send all those file fields through IDOC-.
Else
2)If the Sonumber is not populated from the file then need to trigger a Bapi_Createfromdat to create the sales order and receive the salesorder number as response from Bapi then
have to send all those file fields and Bapi response sales ordernumber through the same IDOC which is mentioned in the point 1.
Please provide the solution for this.
Is BPM required for this,if so provide the steps.
Thanks in advance,
PraveenHey,
you will require a BPM for this.
Steps.
1) recieve step(abstract async) for the file
2) Switch case: condition based on the Sonumber i.e . whether it is populated or not.
Branch 1(of switch if Sonumber is populated): send step(abstract synchronous) recieves flag as 1.
Branch 1 will also have a transformation step that will consist of the mapping between bapi_change and Idoc
Branch 2(of switch if Sonumber is not populated):send step (abstract synchronous) recieves sales order number. the creation logic will be written in the BAPI.
Branch 2 will also have a transformation step that will consists of mapping between Bapi_create and the Idoc.
3) After the switch there will be an abstract asynchronous send step for the Idoc.
In Inegration directory:
Channel: File, RFC and Idoc.
receiver determination
File-> BPM
BPM->RFC
BPM-> IDOC
Now for Idoc you require ALE settings both on XI as well as R3
Steps for ALE settings:-
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 6)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
Step 7)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
reward points if useful
regards,
Milan
Maybe you are looking for
-
How do I telll if a art is a rectangle/ellipse/polygon/star etc.?
When iterate through arts in document, I can tell if a art is kPathArt or not by call GetArtType(). Is there anyway that I can even tell if a kPathArt is a rectangle/ellipse/polygon/star etc., something like IsEllipse()?
-
How can I get rid of a email that I put in when I got-my. iPad I cannot remember the password and it pops up when I try to get my iCloud app
-
Been asked for passwords at start up constantly
Been asked for passwords at start up constantly, i only changed my password once and now i can not even get into my keychains to see previous passwords. anyone have this problem, pelase let me know what to do about it.
-
Is Developer Release 6.0 shipping yet?
Is Developer 6.0 shipping yet in the UK? Release date was given as end March, and yet I can find NO mention at all on any Oracle Website announcing it. Is it released yet or not? Simon Hedges Gloucester UK null
-
MBP unexpectedly shuts down for no reason- help!
MBP unexpectedly shuts down for no reason. My MBP has been working fine, until I updated to 10.5. Originally this problem started in Bootcamp running XP, but has now done this once in OS X, just a while ago. There seems to be no difference- even when