Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Similar Messages

Error while executing a JDBC to Idoc scenario : No standard agreement found

Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
Ravi

Hi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka

Runtime Error: How to Reprocess File-XI-IDoc scenario

Hi All,
I'm working a file adapter to XI to IDoc scenario. My XI message has about 2,000 records in it and one of those records contains an error (due to an invalid character in a description). My question is in a production environment would it be somehow possible for me to reprocess this erred message and post the remaining 1,999 records that do not have an invalid character? What are my options to progress?

Thanks Bhavesh,
Not sure what additional details you need but I'll give it a go. I've got an input file that contains lets say 100,000 rows of data and each row is a separate record. I use sender file adapter using file content conversion with fixed length definition. I send that through a simple mapping program that will generate 100,000 IDocs. I'll get 50 XI messages each containing 2,000 records (recordsets per message)
Because of an invalid character in the source file (an "escape" character) in SXMB_MONI I get a red flag. The error message is essentially "com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x1b".
Since the XI message errors none of the IDocs for the 2,000 records in that message gets created even though 1,999 of them are OK.
So my question is basically is there a way for me to restart this message via SXMB_MONI (or another way) so the other 1,999 records will process OK leaving me with the error to deal with later?
Thanks again!

Error while doing file to mail scenario

Hai All,
I am getting the following errors while doing the file to mail scenario.
Error:Exception caught by adapter framework: Failed to call the endpoint
Error:Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
Can anyone please give me solution...

Try this:
Re: "Could not determine code page" inbound side error
and this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

Error in File-PI-Idoc scenario

Dear All,
While working on File-PI-Idoc scenario, I am getting the error as
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have checked various other posts on the same error but still I am not able to resolve this.
Please help me in resolving this error.
reg,
nj

Nishu,
Please check whether you have assigned the following roles to the particular user you are using for data communication.
Roles:
SAP_XI_IS_SERV_USER,
SAP_XI_APPL_SERV_USER
Regards,
Sugata

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

How can I include the Header Information....for a File to IDOC Scenario

Hi,
I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that <b>"HEADER Information Missing: Message should Start with EDI_DC40"</b> i.e the Header Information.
My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
Kindly Inform me some Solutions.
Thanks & Regards
Somnath

Hi Suraj,
Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
Thanks and Regards
Somnath

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: Idoc Status 50

Hello,
I have a problem in doing a File to IDoc Scenario with a simple XML file mapped to IDoc "CREMAS.CREMAS03". In the beginning, I got a status 56:"IDoc with errors added". Then I added a logical system (LS name of my sender)manually in "Display IMG";however, it didn't work. So I simply changed the logical system name of my sender to XI_00_800 which already exists in R/3. I tried the scenario again, then I got the status 50:"IDoc added". Looked like the IDoc still hadn't been correctly inserted as a record. May I ask what other steps or configurations do I need to do to get this scenario to work? Thank you.

Steve,
<i>Moreover, I didn't create any partner profile. The "XI_00_800" partner profile is in the system all along. Should I create a whole new partner profile and point that to my sender business system?</i>
You need not create it once again as it already exists. Normally , ALE configurations on an R3 system are the responsibiltis of the Functional Team. For instance , on our projects we are never given access to the End r3 systems and the Partner profile are created by the F'nal team itself.
Like I mentioned, ask your F'nal team why you are getting this issue. From XI side , there is nothing more you need to do.
Regards,
Bhavesh

Error while doing F-90 Asset Acquisation

Hi,
I am getting the below error while doing F-90 Asset Acquisation scenario. Please help me to fix this issue.
Tax code V1 country IN does not exist in procedure TAXINN
Message no. FF713
Diagnosis
You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system settings.
To do this, choose Maintain entries (F5).
Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
Create a new tax code if necessary.
Caution:
Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
Thanks
KB

Hi,
you need to maintain Tax Code A0 & V0 in t.code OBCL t.code.
and also ensure to check whether you have created tax code V1 or not in FTXP t.code. If not, create V1 tax code and assign GL on that in the right Transaction event keys in OB40.
Try.... if not working let me know....
Regards,
MOhan.

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

Error while doing File to File Scenario

All,
I am trying a simple file to file scenario - where xi picks up the file from a location and maps the message and dumps it in another location.
I am Getting the below error while doing the same .........
Time Stamp Status Description
2009-03-30 14:30:24 Success Channel Test_send_cc: Send binary file "d:\input\input.xml". Size 203 with QoS EO
2009-03-30 14:30:24 Success Application attempting to send an XI message asynchronously using connection AFW.
2009-03-30 14:30:24 Success Trying to put the message into the send queue.
2009-03-30 14:30:24 Success Message successfully put into the queue.
2009-03-30 14:30:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
2009-03-30 14:30:24 Error Attempt to delete file "d:\input\input.xml" after processing failed. Retry
2009-03-30 14:30:24 Success The message was successfully retrieved from the send queue.
2009-03-30 14:30:24 Success The message status set to DLNG.
*+2009-03-30 14:30:24 Error Transmitting the message to endpoint http://filip:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.*
2009-03-30 14:30:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Mar 30 14:35:24 GMT+05:30 2009.
And i cant see the meesages using the SXMB_MONI trasaction
please help me resolve ths issue
Regards,
Mahesh.
Edited by: mahesh uma on May 3, 2008 2:12 PM

Hi Uma,
Go through this links::
Hope these links are useful to you..
Urgent: Message not transmitted from AFW to Integration server
Error with huge file
File to JDBC error
Thanks,
Satya Kumar..

Regarding error in XI File to IDoc scenario

Hi,
when i was doing file 2 idoc scenario i got this error "Unable to convert sender service to an ALE logical system". please resolve my issue as early as possible.

Uday,
Please go through these threads:
Unable to convert the sender service to an ALE logical system
How to convert Sender Party/Service to a Logical System?
Unable to convert the sender service to an ALE logical system
BR,
Alok
Edited by: Alok Sharma on Jan 31, 2008 12:39 PM

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
Babu

Please 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

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

Error while doing a File to IDOC scenario

Similar Messages

Maybe you are looking for