PI: File to IDOC port is empty in R/3 system

Hi,
We send an IDOC from PI. We can see the IDOC in R/3 (WE20) but the "port" is missing under "recipient infromation", there is no character in there. The other fields are all set. Where we have to set our port? In the communication channel is nothing to set.
Thanks
Ronny
Edited by: Ronny Pol on Feb 12, 2010 4:22 PM

No, we are not populating control record data in PI. We deactivated these fields...
Then I guess its unable to pick all the information(regarding sender/receiver port) from standard configuration.
Check the configuration once again that you have done(Abhijit's post above states the steps).
or
If you have time try the approach to populate EDIDC40 node in mapping and checking the option(Apply control record data from payload) in receiver IDOC channel.
Regards
Soumen...

Similar Messages

Flat file to Idoc : Last line empty in payload

Hello everyone,
I'm trying to import Flat File from an external partner, and insert it in our SAP System as Idoc.
It works fine, after a small change in the flat file.
In the normal version, I have a last record with value 'OK'.
I have add the close record.lastFielsOptional in the FCC.
But after checking the payload, I have seen that I have at the end the following thing :
<ns:File xlmns:ns="http://world.com/file">
<record>
</record>
<record>
</record>
<record />
</ns:File>
Can someone explain me how to avoid to have this last <record/>, or checking it in mapping ?
Thanks a lot

Hello Greg,
The problem is that the key in the flat file is 3 digit numeric field, and OK is 2 char.
If I try to use the key, I have an error on the last record because we have only 2 char for the key, and when I put the parameter record.lastFiledsOptional : yes, i have no more error on the FCC, but the last record of the payload is empty.
Have you a possibility to avoid this error.
Thanks and regards
JC

Port Concept in File to Idoc Scenario

Hi All,
i have some doubts in File to Idoc scenarion.......... for sending file i m using Business Service. In adapter specific Identifier i have "FILE".
1. So i hv to configure partner profile with this name.......... M I Right????
2. At my receiver side (R3) i have many ports configured for XI. so which one will be used to post idoc???
Thanks,
Maheshwari.

> 1. So i hv to configure partner profile with this
> name.......... M I Right????
U are correct. You need to create a Logical System Name on R3 for this in BD54 and then add the inbound partner profile entry in We20.
> 2. At my receiver side (R3) i have many ports
> configured for XI. so which one will be used to post
> idoc???
As it is a File to Idoc, ports on R3 do not matter. You need to create a port in IDX1 in XI.
Regards
Bhavesh

IDoc Error status 51 in R/3 System

Hi All,
I created the Custom Idoc to post the HR master data into the SAP R/3 system.
We developed the scenario to create single idoc for each record in the file.
If one record contains in the file then Idoc is processing successfully in R/3 System.
If the file is having more than one record, first record is processing remaining are giving the error status 51.
Where the problem in this case?
Regards
Sridhar Goli

thanks for your replys
I checked the payload of records it is valide data.
When I run the bd73 for reprocessing error Idocs, the same error record is processed and changed the status to 53.
I developed the custiom function module and called the Call Transaction in this FM.
After processing the first reocrd, I think it is not processing second record.
When I run the WE19 the error record is processing.
How can I solve this problem?
Regards
Sridhar Goli

File-XI-IDOC : error in sxmb_moni because of empty idoc

Hi !
I'm converting a CSV file to IDOC segments (CREMAS04).
XI uses a lookup table to convert CSV records to IDOC segments. It is normal that some records could not be converted. When I process a CSV file that has ALL non-convertable records, I get an error in sxmb_moni :
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 99889D40A4D811DBAD4A0017A4510466: Tag found instead of tag IDOC BEGIN=</SAP:P1>
And the final payload is:
<?xml version="1.0" encoding="UTF-8" ?>
<CREMAS04 />
In the integration repository, the occurance of the complex type CREMAS04 is "1..1", I modified the xsd to minOccurs=0 , maxOccurs=1 , and imported it, but it keeps showing me "1..1"...
How do I deal with these case ?? I don't want error red flags in monitor because of empty idocs...
Thanks.

Hi Bhavesh !
Thanks !
The problem is that because of mapping rules, the value of my target fields is SUPPRESS, not "empty".
For example, I have a file with this records:
A
A
B
A
"B" records should fill an IDOC segment, "A" not.
If I receive a file with only "A" records, for example 48 "A" records...then the IDOC segment, now, is receiving 48 SUPPRESS values...then the mapWithDefault doesn't work because they are SUPPRESS and not EMPTY.
Any ideas?
Thanks,
Matias.

Need Information for transporting a file as IDOC through File Port!!!

Hi,
All configurations are present in the system to transfer a file as IDOC using File Port.
Now we are creating a custom program to transfer the same. Now i have all the data in an internal table which has to be send to Non SAP system. So can i know the process how to send the same.
I have a SAP Directory where i need to place the system. I also have all ports required.
So please let me know how to code the same ASAP.
Thanks and Regards,
sagar..

You may want to try using the IDOC Test tool WE19 in order to test out your ports and partner profiles.
Also sending from SAP to XI / PI you might be better configuring RFC Destination / SM59.
See this Wiki for more info...
http://wiki.sdn.sap.com/wiki/display/XI/ALE+Configuration

Strange Problem.. File to Idoc... RCVPOR is missing in control Records.

Hi All,
File to Idoc:
Sender :
Party : PT_ABC
Business Service : BS_ABC
Note : I provided the LS name(PARTABC) for BS_ABC Under Adapter Specific identifiers.
Receiver :
Business system (Without party) : BS_DEV_R/3
In the IDOC receiver communication channel, I enabled the options
-Apply COntrol records from Payload
-Take sender from Payload
-Take Receiver from Payload.
Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
File is picked and message processed and when i checked in SXMB_MONI,Idoc control records are showing clearly like below.
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<CIMTYP>ORDERS05</CIMTYP>
<MESTYP>ORDERS</MESTYP>
<STDMES />
<SNDPOR>SAPDPI</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>PARTABC</SNDPRN>
<RCVPOR>SAPDL1</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>DEVSAP</RCVPRN>
</EDI_DC40>
But the Idoc is reached to R/3 with status '56' .And in the control records.. the receiver port (SAPDPI) is missing.
I dunno what happened.When i cross checked, the remaining interfaces are working perfectly.
Any idea whats going wrong?
Regards
Deepthi.

As a matter of fact it is not strange at all:)
It means you need to check the partner profile in the receiving r/3 system. This type of problem occurs because you need to define the partner profile PARTABC to the IDOC ORDERS05. If this association is missing you would always see the RCVPOR missing in the destination system.
Also you have mentioned that "Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
This is because for the BS_ABC sender service you must have a logical system associated; you can check the same by looking at the adapter specific identifiers. In your case I believe it is empty so the system can't find the logical system for it.
Thanks
Abinash

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

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

File sender adapter:FILE to IDOC without BPM, can't see in SXMB_MONI.

Hi all
I have a FILE - XI - IDOC Async scenario without BPM.
I configured FILE sender adapter and IDOC receiver adapter. I made a mapping to transfer file data to the structure of IDOC.
Now when i am trying to load the file using command prompt, i cud see nothing in the monitoring. Whereas if i go to the communication channel monitoring of runtime workbench, i saw that CC is polling correctly and was reading the file also.
And also wen i saw in the processed folder which i mentioned in the CC configuration for the ARCHIVE DIRECTORY, i saw that file got transferred to the folder also.
I don't understand why i cant see anything in the monitoring.
Could anybody help me to rectify the problem. Is there anything i m missing ?
Regards
Naina

Rajesh/Amar
TCode:: SXMB_ADM->Integration engine configuration->specific configuration->runtime
Trace_Level = 3 then you can get all MONI PIPELINE Steps also
I did this change but cudn't see anything in SXMB_MONI.
This is how i have configured my process:
http://wiki.sdn.sap.com/wiki/display/XI/FiletoMultipleIDOCSplittingwithoutBPM
But instead of IDOC splitting i have simple FILE - XI -IDOC scenario.
I have configured everything exaclty the same way it is mentioned here. But for me the process is not visible at all.
I can't even see the first request message in the monitoring.
This is the message i can see in the communication channel monitoring:
2010-05-24 09:07:41 Success Channel CC_*: Entire file content converted to XML format
2010-05-24 09:07:41 Warning Channel CC_*: Empty document found. Proceed without sending message
2010-05-24 09:07:41 Success File "/xyz/ABC.txt" archived after processing
Is there any problem with the file and that could be the reason it cant convert the file to the request message MT_REQUEST and thus am not able to see anything in monitoring.
help me guys....this is a simple process and i m stuck...its frustrating
Regards
Naina

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.

File to IDOC, with External Definition to hold multiple IDocs

Hello Experts,
I am configuring a sample File to IDOC scenario. Here are the steps I am following, can you please guide me what I am missing here.
I am having a flat file with 10 records to be transferred to my ECC system through IDOC adapter to create 10 different IDocs.
1. I am picking up my flat file using a 3rd party Business System with File Content Conversion
2. I uploaded CREMAS Idoc and exported as XSD file and modified Occurences paramter to unbounded and uploaded back as an External file definition into IR
3. I defined an SAP WEBAS ABAP type Business System with LS (representing my ECC system) and configured with IDOC Rcvr channel.
4. In the IDOC recvr Channel, I specified RFC destination pointing to my ECC system & Port, Release...etc
5. On the ECC side, I configurated a PARTNER PROFILE with the above mentioned LS(used in step 3) and added an Inbound Idoc paramter CREMAS with process code CRE1. Selected the option Trigger Immediately.
Testing:
1. When I checked my CC monitoring in RWB, my file on the sourced is getting picked up successfull with respect to the specified polling intervals.
2. I don;t see any messages in my SXMB_MONI. I verified SXMB_ADM configuration it looks fine to me
3. I used TCode:WE02 on ECC side, nothing is there
4. I used Tcode SM58 on ECC side, nothign is there
I have no idea what is happening after successfully picking up the file on the source side.
Is there a way to trace where exactly the error is or what is wrong with my scenario?
Just an observation, We don;t need to specifiy any LS on the Sender Business Sytem(3rd party in my case) which picks up my file on the source side. Rather I am specifiying LS on the Target Business Sytem(type WEBAS ABAP in my case) to send my IDOC to ECC system. I am using the same LS to define PP on ECC system.
Edited by: Chris Rock on Oct 21, 2008 5:03 PM

Aamir,
I tried full cache refresh, also cleared SLD Cache for both IR & ID. No luck.
I think either some thing wrong in connection parameters, but atleast if I see some error in Moni or RWB, it helps, but in my situation, nothing is showing up there.
Connections:
I specified PORT & RFC Dest in IDOC RCVR Adapter along with WEBAS Release version. These PORT & RFCs are created in XI using SM59 & IDX1 and both passed the connection test.
On the ECC side, I created a PP with inbound Idoc CREMAS and process code as CRE1. This PP uses the LS that was used in RCVR BS specified in XI side.
I also loaded Idoc meta data into XI with Tcode: IDX2
Please help me, any body. I will sincerely award the points.

Regarding RFC connection in File to IDOC Scenario

Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario
!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!
Regards,
Varun Reddy.K

Hi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh

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

Receive acknowledgement in file-to-idoc scenario

Hello!
I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
I have passed all steps:
In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
Also, I have logical system C2DCLNT100 - this is CRM system.
First, I go to BD64, create new model view XI_CRM. Then, add message type:
Sender system - C2DCLNT100
Receiver system - P1DFILE
Message type - ALEAUD.
Then I create RFC destination P1D_001 to my PI server.
Then I create port SAPP1D using WE21
Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
Confirmation to system: P1DFILE
Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
So, what should I do to see ack in sxmb_moni?

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.

PI: File to IDOC port is empty in R/3 system

Similar Messages

Maybe you are looking for