No message in sxmb_moni for idoc to file

Hi all,
In the idoc to file scenario i want to store the file on the XI server.i have done all the settings.When i trigger the program an idoc gets generated and it is posted to the port(XI port in my case)I get a green status(we02 status 03)but when i monitor my messages i am unable to see it in sxmb_moni.need help.
Regards,
Shrita.

Hi Shrita,
Take a look at these links..
Messages stuck with a "Green Flag" status in SXMB_MONI !!
Missing Messages - in RWB but not sxmb_moni
No Messages in integration server
cheers,
Prashanth
P.S : Please mark helpful answers

Similar Messages

Error in SXMB_MONI for Idoc to File Scenario (missing of field plant

Hi SapAll.
here i have got a tricky situation where in a Idoc(Matmas.Matmas05) to file Interface thorugh XI there is an error message raising in sxmb_moni.
to get the conclusion for this error i just copied the message from Sxmb_moni and tried with Message mapping in Design by just pasting there,after all this process iam getting the error message as below
Cannot produce target element /MT_FCI_MATERIAL/fcidataimport/objects/object/extensions/collection[3]/row/fields/PLANTEXT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
When i go the mapping program it is defined as
if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
and the important thing is the here the occurance of field plant text is 1.1.
so iam not sure on why the error was raised in message mapping as every thing is fine.
can any body help in slolving this.
regards.
Varma

if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
When WERKS's is absent the IF doesn't have a value and hence the whole context gets suppressed which returns the error. What you have configured would work fine if WERKS is there but with no value. Here the case is a bit different. WERKS itself is not coming. Your logic doesn't handle that. Hope you got what I intend to convey.
Correct me if I am wrong but the logic is you need to pass WERKS value to PLANTTEXT if value comes else map a blank constant...right??
If so, why not just use mapWithDefault
WERKS -> mapWithDefault(blank contant) -> PLANTTEXT
This way if WERKS comes teh value would be passed, if comes with blank value blank value would eb passed if doesn't come atall, even then a blank value would be passed.
Regards
Soumen...

Step-by-step configuration from XI to R/3 for Idoc to File Scenarious

Hi Gurus,
Am the Beginner in Xi, I tried to connect the Xi to R/3 for Idoc to File Scenario but the connection fails, (error in Rfc showing ), could any one send me the step-by-step sm59 configuration. R/3 version 4.6c and Xi version 3.0
rewards sure
advance thanks
with regards
Thambee

hi,
I connected my 800 r/3 client to 100(xi) client, R/3 client is version 4.6d in it rfc test connection is sucessful but remote logon is not responding in my R/3 model view distributed and it's reflected in xi client, when I push the Idoc from R/3(bd10), Idoc created sucessfuly but not despatched
Idoc message type is 10 and 30.
Second thing am confused with Ip address bcoz 2 ip address in both system one is loopback and anoter one is tcpip adapter which one i have to give is sm59, help me plz
with regards,
Thambe

Connection to be done for IDOC to File

Hi All,
I am doing IDOC to file ,i need to know what all connection need to be done (ALE) connection , please help me
Thanking you
Sridhar

Hi,
For IDoc to File sceanrio first you have to do ALE settings on R# and XI system.
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.
Affter ALE setting you have to do development in IR and ID as per standard XI procedure.
Regards,
Sami.

RFC Destination type for IDOC to FILE

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

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

Mapping for IDoc to File

Hi,
I am doing mapping for IDoc to file scenario.
Idoc is INVOIC02.
Source field is KRATE from segment E1EDP05
Target field is Rate.
Mapping rule is as follows.
zero when Condiditon type (E1EDP05-KSCHL ) = YCSE ( enter total 15 digits without any decimal in it. The last 2 digits will be treated as digits after decimal )
Can someone explain the mapping?
I have to map KRATE and Rate but where does KSCHL comes into this?
Please explain

TAKE HELP FROM THESE LINKS : These links can be helpful for you.
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/db0e83e8e74202a5bff527055ab7e5/content.htm
Regards,
Sandeep Kaushik

Setup for IDoc-XI-File scenario

Hi All,
Please provide info where can I find, step by step documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
Thank you,
Sree

Hi,
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.)
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Error in TRFC for IDoc to File scenario while sending IDoc

Hi,
Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
Can anybody help me out in resoving the error?
Regards,
Suraj Kumar

Hi,
Thanks for your reply.
It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
Hope I am clear.
Please let me know, if you need any further information.
Regards,
Suraj

Questions to a Mapping for IDOC-to-File Scenario

Hi all,
I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
<xdoc>
 <Invoice>
 @purno
 <HeaderInfo>
 <invno/>
 <shipdate/>
 <extvalue/>
 </HeaderInfo>
 <DetailInfo>
 <LineItem>
 @lineno
 <vpartno/>
 <descrip/>
 <qtyord/>
 <cost/>
 <vendmemo/>
 </LineItem>
 </DetailInfo>
 </Invoice>
</xdoc>
The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
Is it possible to implement this process with a common message-mapping or have I to implement a business process?
Thanks
with best regards
Christopher

Hi Christopher,
Is it possible to implement this process with a common message-mapping or have I to implement a business process? - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
Thanks,
Rajeev Gupta

Route of the operator.... while creating mapping for idoc to file

Hi,
Scenario is IDOC to File but certain rules are there while creating a mapping in XI.
This is the description for my scenario :
Within XI this Idoc message needs to be translated into 2 text files:
1 file for the route of the operator
     - Read the idoc data.
     - When reading a new order first get the customer. This will be a new line in the file.
        The customer number will be set into the filed u2018CustomerIDu2019.
     - Then read the items. For every item create a new line in the file. The machine number will be mapped to the field CustomerID
     - The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
Could you please guide me how can i implement this above scenario.
Regards,
Y.Raj

Within XI this Idoc message needs to be translated into 2 text files:
this can be done using multimapping i.e. defining your target messages at mapping tabs in your message mapping.
When reading a new order first get the customer. This will be a new line in the file.
The customer number will be set into the filed u2018CustomerIDu2019.
If there is some condition for identifying new order then you should put condition based on input field.
if customer no doesnot exists in order then RFC lookup can fetch customerno
The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
for this declare varaible in global section and use the same or some builtin function can be used for the same.
Rajesh

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

No messages in SXMB_MONI for outbound proxy interface

Dear All,
i am executing Proxy-PI-File interface and I am not able to find any message in SXMB_MONI in the ECC side.
I have done all the required proxy configurations and also the ABAP report calling the proxy is working fine but still not able to view data.
Please guide where i am missing.
Warm Regards,
Nishant Jain

1. Debugg your report which is sending data to Proxy. Make sure data is present in the internal table.
2. Proxy configuration is client specific so make sure the client from where you are running the report has been cofigured for proxy. Check SLDAPICUST & SXMB_ADM settings once again.

Acknowledgement for Idoc To File Scenario

Hi Experts,
My scenario is idoc to file and if the file is successfully delivered at destination then i need an acknowledgement saying that the file was received successfully.
How to achieve this. Can any body send me the scenario with screen shots.
Your help will be greatly appreciated.
Thanks & Regards,
Venkat

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.

XI and R/3 System connection settings for IDOC to File scenerio.

Hi SAP champs,
I am working on a IDOC to File XI scenerio. But I am confused while configuring connection settings at XI system and R/3 system. I am finding problem in transaction IDX2 to maintain the IDOC metadata. Please let me know the complete step by step system cofigurations in XI and R/3 systems for the scenerio. Thanks in advance..
Regards
Sanjeev.

Hi Sanjeev,
We upload Medata in IDX2 to just reduce runtime effort and hence to improve the performance. However it is not a mandetory step to be performed for R/3 TO XI scenario.
You are confused just because here you dont find any F4 help to select the metadata and the PORT.
Thanks
Sunil Singh

Integration Directory configurations for IDOC - XI - File

Hi all,
I have a scenario as above: IDOC-XI-FILE
The IDOCs come from an R/3 system - NHGDDBS01.
I've configured 2 BS:
1) BS_NHGDDBS01
-> TS: NHGDDBS01, type: WebAS ABAP
-> SWCV: BASIS 6.20
2) BS_DEV1_NAUTICUS_OOTS
-> TS: TS_DEV1_NAUTICUS_OOTS, type:Third Party.
-> SWCV: SWCV_DEV1_NAUTICUS_OOTS, type: Third Party
-> PDT: PDT_NAUTICUS_OOTS
With this setup, can someone help me by showing me how to configure the Integration Directory in order to receive IDoc from R/3 (nhgddbs01)?
Please help.
Thanks.
Ron

> This is known issue.....Check the below
> steps.............
>
> Go to XI system ->and IDX1 transaction.. And check
> the port number + RFC destination is given correctly.
> this should point to SAP system ..
> Check thsi RFC destination is having all the entires
> and test connection success
>
> And the port should have the naming convention
> SAP<System Id>.
>
> ........................Check this SAP Note -940313
Hi,
I followed the SAP Note.
The SAP System ID is DV1.
I've configured IDX1 with the following port:
Port: SAPDV1
Client:108
Description: <blank>
RFC_Destination: PI_001 (This RFC destination points to DV1, despite the naming. Connection test is successful)
I recreated metadata on IDX2:
IDoc Types: ZPATINFO
Source Port: SAPDV1
IDoc Types: ZADMINFO
Source Port: SAPDV1
However, when I test the message from R/3 using WE17, SM58 on R/3 it's still showing the error:
Transaction IDX1: Port SAPDV1_108, client 108, RFC Destination error.
May I know where did this error occur and how to rectify this?
Please advise.
Thanks.
Ron

No message in sxmb_moni for idoc to file

Similar Messages

Maybe you are looking for