Transactions used in simple file-idoc scenario

hi all,
what are the transactions used in idoc scenario...(Ex: idx1 for creating new idco)
let me know what is the transaction code to find the clients available...
Is it 'SCC4'
Please provide me required info
Thanks
Narasimha
Edited by: Narasimha bommela on Jan 23, 2008 9:17 PM

Try this guide:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Covers everything from setting partner profiles to monitoring Idocs
I can also recommend this book: http://www.sap-press.com/product.cfm?account=&product=H1935

Similar Messages

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (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.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(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)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (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
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

XI is not able to archive file in file-idoc scenario

Hello friends,
I have an issue in my file->idoc scenario. When a file is placed to XI's filesystem using FTP, it is placed under xiftpuser user. Owner of all directories in this structure wher the file is placed is xiftpuser. XI is not able to archive the file because of the permissions on the archive directory. But the problem is, permissions on this directory are 775 and xiftpuser and xipadm user are in the same group. So this should work. But it doesn't. When I change permissions to 777 everything works fine.
Do you have any idea what could be wrong?
Does it matter, that xipadm user has been added to the common group with xiftpuser "later", when XI was up a long time before? Do we need to restart j2ee to take these new permissions into account?
Thank you,
Olian
Edited by: Olian Saludew on Sep 23, 2008 11:46 AM

Hi,
If archive directory Path is d:\archive
Put a '\' after it.
e.g. "D:\archive\"
It will work.
Regards,
Akshay.

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
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...
MenoN

Exceptions in file-idoc scenario

Hi Folks,
I am developing a file-idoc scenario. What are the different exceptions I would be needed to handle apart from the following two identified?
1. Mapping issue
2. Problem in posting the idoc (SAP system may be down and others)
Thank you

Hi Raja,
The errors an happen at following steps:
1. Error while picking the file:File adapter error
2. Error in mapping: error due to incorrect data, incorrect format, corrupt file etc.
3. While posting Idoc: due to Incorrect userId password, due to structure not matching, destination system being down.
Hope this helps.
Regards
Vijaya

File -- IDOC scenario using XI 3.0

Hi
I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
According to SAP documentation :
To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.
Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
Thank you in advance for your time.

Hi,
Pls look into following link about Acknowledgement.
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
Hope this helps..
Regards,
Moorthy

Acknowledgement - IDoc-File & File-IDoc scenario

Hi All,
   Acknowledgement is possible in case of asynchronous IDoc-XI-File scenario? If yes, how to setup?
   Same as above question for File-XI-IDoc scenario.
   In case of synchronous scenario, how to setup email with acknowledgement?
Thanks a lot in advance.
Sree

Hi Rama,
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:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

File-IDOC Scenario

Hi,
My scenrio is File -IDOC.
I had done Design & Configuration part.
I am getting following error
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
Kindly help me;.

Hello Srikant,
Refer the following weblog in section 5 Troubleshooting File-to-IDOC Scenario in XI.
You have to define logical system name for sender system.Do the steps which are specified in weblog you can able to overcome this error.
Cheers
Veera

Peculiar behaviour in picking file from FTP in File-IDoc scenario

Dear XI Expert,
I have successfully completed configuration of FTP --> XI --> IDoc scenario. I have noticed a peculiar behaviour in picking the file from FTP. I placed a file on FTP and activated File Adapter with poll interval '60' secs and processing mode as 'Archive'. For the first time it has picked the file with expected behaviour and IDoc got posted to SAP successfully. But when I placed file for the second time and when refreshed the FTP directory, immediately file got archived without waiting for 60 secs. But in sxi_monitor I could not see any activity of processing this scenario. Surprise is that, file got archived in target directory. This goes on and on... without registering any activity of processing the message in Message monitoring.
In adapter monitoring it shows the message as described below:
History:
2006-05-09 22:57:25 : Processing started
2006-05-09 22:57:25 : Error: Processing interrupted due to error: FTPEx: No such file
2006-05-09 22:57:24 : Processing started
2006-05-09 22:57:24 : Error: Processing interrupted due to error: FTPEx: No such file
For your information my SAP XI system is on SP16.
Please find below the parameters of sender adapter:
Quality of service: Exactly once
Poll interval: 60 secs
Processing mode: Archive
Connect Mode: Per File Transfer
Transfer Mode: Binary
Can anybody help me out in resolving such a problem in this scenario?

Hi Jayakrishnan,
Thanks for your reply.
Once again the same problem is noticed. i.e., for the first time when file adapter is activated the file got picked, activities were logged in monitoring and IDoc got posted to destination system. For the second time when file is placed, before 60 secs got completed the file is picked and archived in the target directory. No activities in monitoring are logged.
I have tried it checking the message at adapter level, but it is showing 'No results' (even in the case of successful pick of the file for the first time, not even it is showing other file adapters).
I was not able to understand where the problem could lie?
Regards,
Suraj Kumar

File-IDOC scenario in ALE

Hi,
I want to upload vendor master from a FTP file location to SAP using ALE IDOCs. We don't have XI middleware in our system. Could anybody suggest how to do it in detail?
I want to upload data from the file in FTP when a master file is placed in FTP location.How can I get that functionality?
Thanks in advance.
Edited by: Jaya on Jun 3, 2010 1:48 PM

Jaya,
You are using the right approach.
The idoc message type for vendors in CREMAS. You should use transaction wE19 and try to create a CREMAS idoc from the data in your file, manually.
Once you are able to create the idoc and process the idoc successfully to create the vendor, you can write a program and read your file from the server, do the conversion and call function "IDOC_CREATE_ON_DATABASE" and create your idocs.
Salai.

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Message Split -- File to Idoc Scenario - ( Without BPM )

I have multiple records coming to XI in a File and I have to create Multiple Idocs to R/3.
Due to Complexity of mapping I'm splitting Maaping step into 2 message Mappings.
A-->B
B-->C
In the 2nd Mapping step I'm doing message Split meaning for each Source record I'm creating multiple Idocs ( To be precise each record on the source becomes 4 idocs in the Target.
2nd Mapping step is as follows
Source 1..1
Sourcerecord 0.. Unbounded
 field1 0..1
 field2 0..1
 filed3 0..1
Target
Message 1
 Idoc 1.. Unbounded
 Idoc Structure..
Message 2
 Idoc 1.. Unbounded
Message 3
 Idoc 1.. Unbounded
Message 4
 Idoc 1.. Unbounded
So based on some criteria each record of Source will be mapped to 4 Messages ( 1 each under each Message )
Is it possible to do this without BPM?. Iam sending all these Idocs to same R/3 System.
Thanks for any help..RK

Hi,
See the blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Basicly we have 2 ways of handling such scenarios:
- we can use a block step and send multiple IDOCs from our BPM
- we can also do a little trick and send multiple IDOCs from the XI without a BPM
The first approach is a standard XI approach. It involves the use of a BPM
so the speed of this transfer many not be very good in case you'd like to send
hundreds or thousands of IDOCs in just one call.
The second approach uses a little trick that was mentioned several times
on the XI Froum by a number of XI developers but is still not very clear to the XI newbies.
It allows us to send multiple IDOCs without the use of a BPM. Most probably this will be your choice
if you'd like to use such 1:N (IDOCs) scenarios effectively.
Please see the bwlow threads also..
IDOC Splitting
File To IDOC Thru XI
Multi-Mappings in BPM (XI 3.0)
Please let me know , your prob..is solcev or not..
Regards
Chilla..

File to IDOC Scenario - Doubt in RFC Destination

Hi all,
I m working on a File - IDOC Scenario. I got a IDX1 error Also when I try to import IDOC in IDX2, I got I:000 error message(No more information was given) . When I checked the RFC destination, Test Connection works fine. But Remote Logon didnt work, since the target system is not a Trusted System
Is it necessary to make the Target System, a Trusted System ? (For enabling Remote Logon)

Hi ,
There might be some problem with the R3 user that u r using...
For some versions of R3 it is required that the password be in CAPS for making an RFC connection...
I knw this sounds weird but even i had this problem....
Also chk if the XI user has RFC priviliges..
reward points if helpful
PrashANt

How to fill controlrecord in File to Idoc scenario

Dear experts,
Currently I have a working file->Idoc scenario in which I fill Idoc-controlrecordvariables as follows:
- field SNDPOR: name of XI developmentsystem (via a constant)
- field RCVPOR: name of SAP developmentsystem (also via a constant)
- same for fields like SNDPRN and RCVPRN etc.
In Development this works fine. Then I transport the design objects to the next environment. But when I want to test the same in Acceptence or Production, it won't work because the fields are still filled with the settings for the Development system.
Can I fill these fields via some systemvariable in stead of a constant? Or is there another way?
Thanks,
William
Edited by: JWD on Aug 31, 2010 2:20 PM

Hi,
1)Uncheck option Apply contraol record values from Payload in IDoc receiver channel.
2)Disable EDI_DC40 control record in message mapping.
this two steps will solve your problem at configuration time it will take the values irresctive of environment.so you no need to maiantain constant values..
Regards,
Raj

FILE TO IDOC SCENARIO-Receiver Business system ECC showing Red

HI
     In File-idoc scenario Business system showing red status in RWB .And i have given the role for the business system as application server and configure related integrated server . But the error in a RWB for the ping and self-test is as follows
     Unable to log on to system buss_ecc_200 in language en with user PIRWBUSER .
I thing from XI side every thing is ok. But for bussiness system side ECC might miss some configuration .
       could any help in this issue:
regards..

Hi
Please try one of the followings:
1) In Configuration --> Business service --> Service --> Adapter specific identifiers. Give logical system name for the sender system (e.g XI_00_800)
2) In Design --> mapping objects. Give all information of sender n receiver in EDIDC40 segment and
   In configuration --> receiver communication channel in that enable the checkbox take sender from payload.
3) In configuration --> Receiver Agreement --> Header mapping --> Sender Service (Give XI1 i.e ur sender system).
Also check the RFC destination that is the major problem with idoc...

Transactions used in simple file-idoc scenario

Similar Messages

Maybe you are looking for