Testing File to Idoc scenario

Hi,
I have created a scenario, file to IDOC..and Idoc i am using is CREMAS 04.
in SXMB_moni, message status shows Scheduled
And when I go to R/3 system tried we05, and Idx5 transactions and I didn't find the IDOC.
Can anybody tell me how to trace this issue?
Thanks
Balaji

Hi,
Have you done ALE config steps for inbound interface to SAP?
If not, then do it first.
They are:
1)Creating Logical systems(BASIS team creates it)
2)Assigning Clients to Logical systems(BASIS team creates it)
3)Create RFC destinations
4)Maintain distribution model for Idoc(Cremas)
5)Create partner profiles
How to relate whether I have the required partner profile in R/3 system?
Double click on the R/3 system, check if there is an entry for Inbound parameters
on the right hand side ,if so then see for the IDoc Cremas.
If you don't see an entry for IDOC CREMAS then create one as I mentioned above.
Regards,
JE

Similar Messages

How to test file to idoc scenario?

Sender side: flat file
Receiver side : IDOC
Using file content conversions for sender file.
my question when flat file is picked up sent to xi and idoc.
where do I check data received.
Im using creamas.creamas03 idoc.
What is ALE configuration for IDOC and how to do it?
thanks in advance.

Hi,
>my question when flat file is picked up sent to xi and idoc.where do I check data received.
1)RWB- CC montoring..Select the Sender adapter whether the message is sent to XI Sucessfully
2) Check in Sxmb_moni
3)Tcode-We02 look for the IDOC Posted
4)SM59 RFC Destination Test in XI & R3
5) Check the Port in XI - idx1 R3- we21
Regards
Agasthuri Doss

File to idoc scenario in pi 7.1

Hi All,
I am testing file to Idoc scenario.
I have few queries. I am using PI 7.1
1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
Please advice how to overcome
3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
"EDI: Partner profile inbound not available"
I checked all the relevent partner prfile configuration is already there"
I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
Ram

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

PI7.1 File to Idoc scenario issue.

Hi,
We recently had an upgrade from PI7 to PI7.1.
When testing File to Idoc scenario ,we had an issue as below
Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="1" type="T">Error during lookup - com.sap.aii.mapping.lookup.LookupException: Error when calling an adapter by using the communication channel GeneratedReceiverChannel_RFC (Party: , Service: ED2_200, Object ID: a8f14398a9993dccadbe983d401f693a) The channel with object ID a8f14398a9993dccadbe983d401f693a could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache.</Trace>
<Trace level="1" type="T">Error when parsing RFC Response - null</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
This was working fine before upggrade.
Any changes required to be done in scenario?
Pls let me know.
Thanks,
Srinivasa

do a CPA cache refresh
http://hostname:port/CPACache/refresh?mode=full
also check if the object is visible in tcode SXI_CACHE..
also refresh the SXI_CACHE

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
 I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

Alert Configuration for File to IDoc scenario

I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
and configured Alerts for file to IDoc scenario.
But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
Regards,
Suraj Kumar

hi Suraj,
WHich SP version are you on??
If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
Regards,
Bhavesh

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

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)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
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

Steps required in File to Idoc Scenario

Hey guys i m doin a file to Idoc scenario and just wanna make sure my steps r correct.
steps done on the XI server
1.Create RFC destination(test the destination by giving the target host as the R/3 server).
2.Create port for the RFC destination.
steps on the R/3 side
1.Create/verify logical system name.
and finally create business system for this logical system in SLD.
now do i need to do partner profile as well or not? and if i have to do it how is it accomplished.
thanx
ahmad

Hi,
The following are needed for idoc to file scenario...
In R3...
RFC dest to XI (sm59)
Logical system (bd54)
Port to XI (we21)
Partner profile for the logical system (we20)
In XI...
RFC dest to R3 (sm59)
Port to R3 (idx1)
create metadata for the idoc (idx2)
In sld...
create business system for R3.
Regards,
Uma

Problem in executing File to IDoc Scenario in XI

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

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

File to IDoc scenario-CREMAS not getting posted

Hi Experts,
i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
Can anyone please tell me what is the reason and the solution for this problem?
Is this a data error or XI error?
Thanks in advance,
Shweta.

Hi Shweta
Status 51, 52 means Posting error
Please check wheteher all the configuration has been done or not
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
After That check the solution it is due to Authorization
File to idoc - IDX5 Error
Regards
Abhishek Mahajan
*Please reward points if helpful**

File to Idoc Scenario. Pls advice

Hi All,
I have implemented File to Idoc Scenario and it worked fine.
I have 2 doubts:
My Scenario: File -- XI -- R/3 system named D01
1. In Configuration: In Receiver Aggrement why we put
    XI Business System name in Sender Service?
2. In Configuration when I open my R/3 Business system
    (D01CLNT100) and click on Adapter Specfic Identifiers I can
    see my Logical System Name as D01CLNT100.
    When I use SALE tx. in D01 R/3 system I can see
    D01CLNT100 as logical system
    Question: If I use SALE transaction and change my
    logical system name to "test" , do I need to change the
    name "test" in SLD and then for R/3 Business system
    (D01CLNT100) in Adapter Specfic Identifiers I will see new
     Logical System Name as test.
Regards

Hi,
Question: If I use SALE transaction and change my logical system name to "test" , do I need to change the name "test" in SLD and then for R/3 Business system (D01CLNT100) in Adapter Specfic Identifiers I will see new Logical System Name as test
Yes , you need to Update the name in SLD and just Do SLD Data Cache in ID-- Environment to reflect the same name in Identifiers place.
>>1. In Configuration: In Receiver Aggrement why we put XI Business System name in Sender Service?
You might have used XI as Sender and you might have placed the file in XI Server to pickup.
Thats why you are using Xi's Business System name as Sender Serveice.
Regards
Seshagiri

** 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

Not sure if IDoc was created or received in file to idoc scenario

Hi,
I configured a file to idoc scenario in my test client for idoc MATMAS.MATMAS02 , now after going thru all the phases of design and configuration and creating partner profile using we20 , when I m executing the scenario , I am not sure wht happened to the idoc becz i can't see in the R/3 system using we05/02 or BD87 in the XI system .
Pl help how to rectify the error and find out where the error has actually occured.
ans will be rewrded
rgds
mojib

Hi Mojib,
first check in SXMB_MONI whether you have a success chequered flag for the file messge.................if there is error here, then rectify your this error and re-run your scenario................if you cannnot see your file msg in SXMB_MONI, then go to RWB and in comm channel monitoring, see the error in sender file comm channel status and rectify the error in sender file comm channel in ID and save and activate it and then re-run your scenario............
then execute SM58 to see in there is anything in tRFC.........if there is not anything here, then it means your IDOC has reached R/3.................
then in R/3, execute WE05 for the relevant period, then you will see your IDOC there with some status..........
Regards,
Rajeev Gupta

XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

Hi All,
The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted. I did see successfully message for that particular messages but the IDOC's were not created in the ECC. If the messages is reprocessed then IDOC's are posted successfully to the ECC system. The message has checkered flag in the SXMB_MONI tcode.
This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
Thanks,
Sarvesh

Hi,
Interesting problem...since its intermittant..
You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
from the ecc system to check inbound queue monitoring.
from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
Hope that helps
Regards
Ravi Raman

Testing File to Idoc scenario

Similar Messages

Maybe you are looking for