IDOC - Idoc_adapter.sender_bsi_incorrect (path //s)

Hi people, I get this error when I run the idoc_adapter :
<SAP:Code p1="The accessing object does not support the path //s" p2="DEV" p3="" p4="">
I have configured the ale name, for example, for BS dev I put SAPDEV for client 100, but this error is showed.
Do you know if there is one log, one way to debug and discover something? Something strange is the "path //s", it looks like an address.
Thank you for any help !
Regards,
Renato.

Hi people, I discovered !!!
I am going to tell the way that I did to discover the problem :
In the monitor (sxmb_moni) the process trace is showed, there are entries like CL_IDX_IDOC_SERVICE-ENTER_PLSRV that means one abap class method, so, I debug this method and I find the function SAI_LOGICAL_SYSTEM_GET which get the logical system names, and debuging this function I could see one comparation statement "hosts_in ne me->host" whose in my case was "SRLCPD13" <> "srlcpd13", bingo !
I used transaction SLDAPICUST to change the host name to low case, and voilá !
Bye,
Renato.

Similar Messages

IDOC_ADAPTER.SENDER_BSI_INCORRECT

Hi,
I get the following error message. Can anyone help on this? I have imported the metadata using transaction IDX2. Also the cache displays the logical system for the receiver system. My sender system is a third party and not an SAP System. Do I still need to specify the logical system for that?
Regards
Amit
SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in SLD client: AbapSLDRequestHandler.ext" p2="BS_Enfield_WS" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
</SAP:ErrorHeader>

problem resolved by Creating an entry in 'sailcrbsc' table for the sender system. Even though the sender system is not a SAP system I had to create an entry in the above table. Refresh the cache from SXI_CACHE. And resend the message.

Unable to convert partner to IDoc sender partner

In XI 2.0,we are facing a problem while trying to send idoc out of XI to SAP R3 system.We created Business Systems without specifying ALE logical system name,but later we corrected this.
Even then we are getting this error:
<SAP:Code p1="I::000" p2="SRMSUS_BUSS_SYS" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
We have created port in IDX1 in XI for R3 system.
Suggest us ?
regards
Vishal

Vishal,
Add your agency and schema values in both party and receiver idoc channel (tab identifiers),
it should be something like
BS_ (your R/3 system system), Schema ALE#KU# (KU if its customer)
Thanks,
Pavan

IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP Only asynchronous processing supported

Hello Expert,
Error while send IDOC
" IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP Only asynchronous processing
supported for IDOC Adapter" is returned.
Please suggest
Thulasi

Hi,
Make sure that you have mentioned the Recever message interface as Async mode
Here it is saying that IDOC suports only Async that means some where else u have mentioned as Sync interface
Regards
Seshagiri

Idoc error 56 in inbound

Hi Experts,
I did one idoc transfer from Server A (ecc 5)to server B(ecc 6) .when i took the transaction   we02 in server A its showing green light and outbound idoc was gone to server B .when i took we02 transaction in server B its showing error 56 with red light ,but idoc that i send from server A reached here with diff idoc number in the inbound side ,I had taken this idoc and put it in we19 transaction and i found that in the inboud side recever port in not populating .i tried to put port name manually by using the inbound function module at that time it works correctly ending with green light and same material is created in server B.
what should i do to make the inboud port to populate automatically .In partner profile of server B ,ports and maintained correctly . Is it because of any server difference?(ECC 5 --> ECC6) .Please help .
Regards
Sarath
Edited by: Sarath Madhusoodhanan on Feb 6, 2008 7:24 AM

Best Practices for mySAP Retail
Version 1.47
based on
SAP R/3 Enterprise with Retail Extension 1.10
and SAP BW 3.0b
Process Documentation Scenario
EDI in Purchasing
Copyright
© Copyright 2003 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Table of Contents
1     SCENARIO EDI IN PURCHASING     4
1.1     Introduction     4
1.2     Procedure     4
1.3     Preconditions     7
1.4     Scenario Menu and Basic Path     7
1.5     Overview of Required Master Data     8
2     EXECUTION     9
2.1     Purchase Order Processing in the Retail System     9
2.1.1     Create Purchase Order     9
2.2     Sales Order Processing in the Vendor System     10
2.2.1     Looking at IDoc ORDERS and ORDRSP     10
2.2.2     Display Sales Order     10
2.3     Control Order Confirmation in the Retail System     10
2.4     Process Delivery in the Vendor System     11
2.4.1     Posting Stock     11
2.4.2     Create Delivery     11
2.4.3     Picking and Goods Issue     12
2.4.4     Looking at IDoc DESADV     12
2.5     Post Goods Receipt with Reference to Shipping Notification in the Retail System     12
2.6     Create Billing Documents in the Vendor System     13
2.6.1     Creating Billing Documents     13
2.6.2     Looking at IDoc INVOIC     13
2.7     Display Incoming Invoice in the Retail System     13
1     Scenario EDI in Purchasing
1.1     Introduction
To increase the efficiency of communication between retailers and vendors, documents such as purchase orders, order confirmations, shipping notification documents and invoices are transferred electronically. In the SAP R/3 System, this communication is supported by the creation of IDocs. An IDoc is an electronic document with the standard SAP format. Communication between two SAP R/3 Systems takes place using a converter and standardized national (SEDAS) or international (UN/EDIFACT) standards to transfer messages across a network (Wide Area Network, Local Area Network).
In the following scenario, we at retail headquarters (Retail system) will be communicating with our vendor (Vendor system). As only one SAP R/3 System is available, while we are going through the handbook the two systems will be simulated using two company codes.
As the retailer, in purchasing organization E001 we place orders for our distribution center VZ01 in purchasing organization V001, distribution chain V2 for >Article 1 with our vendor >vendor. Company code PS01 will be used to designate our organization. The vendors organization will be represented by purchasing organization V00L, distribution chain V3, supplying site LZ01 and company code PS0L. At retail headquarters, processing on the purchasing side will involve purchase orders, order confirmations, goods receipts and invoice verification. On the vendor side, sales-side processing will be shown using sales orders, delivery documents and billing documents. To ensure adherence to the chronological procedure of the business process, we will continually be jumping between the retailer and the vendor. So that both sides are able to communicate with one another and so that subsequent functions in the business applications can be triggered, the vendor >vendor on the side of the retailer must be connected with the customer >customer on the side of the vendor. For more detailed information see the Customizing Guide for this process.
1.2     Procedure
The process flow is as follows:
1.     Process purchase order in the Retail system
2.     Process sales order in the Vendor system
3.     Control order confirmation in the Retail system
4.     Process delivery in the Vendor system
5.     Carry out goods receipt with reference to shipping notification in the Retail system
6.     Create billing documents in the Vendor system
7.     Carry out invoice verification in the Retail system
The following overview shows the individual steps again and the IDocs to be sent:
Retail system     IDoc           IDoc           Vendor system
Create purchase order     ORDERS
               Sales order is created, order confirmation is created
          ORDRSP     Process sales order
Order is entered into the purchase order
          DESADV     Create delivery
Shipping notification is created
Carry out goods receipt for the shipping notification
          INVOIC     Create billing document
Incoming invoice is created, invoice verification is carried out
1.3     Preconditions
1.4     Scenario Menu and Basic Path
The following path is the basis for all other paths in this process documentation. As an alternative to the SAP menu, you can use the process menu for navigational purposes. You can access this using the button in the SAP Easy Access menu.
BASIC PATH     SAP menu  Logistics  Retailing
PROCESS MENU     PCS_RT_LOC4_040
1.5     Overview of Required Master Data
To carry out the scenario, use the master data listed for your installation of the preconfigured system. You can find corresponding identifiers in the following table:
     FASHION     HARD GOODS     FOOD
MASTER DATA IN THE RETAIL SYSTEM
RETAIL ARTICLE     PCS-02-ART111     PCS-02-ART431     PCS-02-ART333
VENDOR     PCS-V112     PCS-V432     PCS-V332
DISTRIBUTION CENTER     VZ01     VZ01     VZ01
MASTER DATA IN THE VENDOR SYSTEM
VENDOR ARTICLE      EDI-02-ART111     EDI-02-ART431     EDI-02-ART333
CUSTOMER     PCS-C300     PCS-C320     PCS-C310
SUPPLYING SITE     LZ01     LZ01     LZ01
PURCHASE ORDER QUANTITY     500     500     500
BASE UNIT OF MEASURE     PC     PC     PC
2     Execution
2.1     Purchase Order Processing in the Retail System
2.1.1     Create Purchase Order
The retailer creates a purchase order for the vendor >vendor in their SAP R/3 System (the purchase order could also be the result of a complex procurement scenario). Following this, the SAP R/3 System automatically sends an IDoc in ORDERS format using the standard EDI outbound.
PATH     Purchasing  Purchase order  Purchase Order  Create  Vendor Known     ME21N
ENTER     Vendor
Order type
Document date     >VENDOR
'Standard purchase order'
TABSTRIP     Organizational data     In Header area (expand if necessary)
ENTER     Purchasing Org.
Purch. Group
Company Code     'E001'
'E01'
'PS01
BUTTON          In Item Overview area (expand if necessary)
ENTER     Site     VZ01
BUTTON
ENTER     Article
PO quantity
OUn     >Retail ARTICLE
>PURCHASE ORDER QUANTITY
>BASE UNIT OF MEASURE
BUTTON
Only when using a generic article:
MESSAGE     Enter variant quantities
ENTER     Distribute the total quantity among the variants
BUTTON
MESSAGE     Can delivery date be met?     Possible
BUTTON          Only with message
MESSAGE     The effective price is..., the article price is...     Possible
BUTTON          Only with message
BUTTON
MESSAGE     Standard PO created with number ... .     Note purchase order no.
BUTTON
When the purchase order is created, an IDoc ORDERS is created, using message control, which is sent to the vendor..
2.2     Sales Order Processing in the Vendor System
The IDocs sent in this process are always available twice, once in the senders EDI outbound and once in the recipients EDI inbound.   The IDoc ORDERS that is sent by the Retail system enters the vendors system, ensuring that a sales order (standard order) is automatically created. At the same time an order confirmation ORDRSP is created and sent back to the retailer. When the order confirmation arrives in the Retail system, the sales order number is entered into the purchase order.
2.2.1     Looking at IDoc ORDERS and ORDRSP
PATH     SAP menu  Tools  Business Communication  IDoc Basis  WE02 - Display IDoc      WE02
ENTER     Date of creation
BUTTON
SELECTION     Outbound IDocs and inbound IDocs ORDERS AND ORDRSP are displayed.
Double click on IDoc ORDERS in inbound
Double click on IDoc number
Expand the controlling tree status records
Expand the controlling tree application document posted
Note down the number of the message standard order number... saved.
BUTTON     2 x
2.2.2     Display Sales Order
PATH      Sales  Sales order  Order  VA03 - Display     VA03
ENTER     Order     Order number from 2.2.1
BUTTON
TABSTRIP
     Site
Confirmed quantity     LZ01
>Purchase order quantity
BUTTON     2 x
2.3     Control Order Confirmation in the Retail System
PATH      Purchasing  Purchase order  Purchase Order  ME23N - Display      ME23N
PATH     Purchase order  Other purch. order
ENTER     Purchase order
Purchase order (radio button)      from 2.1.1
x
BUTTON
PATH     In Item Overview area (expand if necessary)
TABSTRIP Confirmations
The number of the sales order is entered in the field, External document
BUTTON
2.4     Process Delivery in the Vendor System
The vendor creates a delivery with reference to the sales order, picks and posts the goods issue. When the goods issue is posted, a shipping notification (IDoc in DESADV format) is automatically sent.
2.4.1     Posting Stock
So that the delivery can take place, there has to sufficient stock available in the vendors distribution center (LZ01). To ensure this is the case, CATT ZRT_3_1_MB1C can be started:
PATH     SAP menu  Tools  ABAP Workbench  Test  Test Workbench  Test Tools  SECATT - Extended CATT      SECATT
ENTER     Test Configuration     /BPR3R/EDI_BESTAND
BUTTON
ENTER     Error behavior
Variant
(otherwise leave the default values)     S No termination, Continue with Next Script Command
According to the selected master data:
1 (Fashion),
2 (Food) or
3 (Hard goods)
BUTTON
BUTTON     2 x
2.4.2     Create Delivery
There is sufficient stock available for the delivery to be created.
PATH      Sales  Sales order  Order  Subsequent Functions  VL01N - Outbound Delivery      VL01N
ENTER     Shipping point
Selection date
Order     LS01
See
See 2.2.1
BUTTON
MESSAGE     Delivery ... saved
Note down the number of the delivery
BUTTON
2.4.3     Picking and Goods Issue
The pick quantity is entered and the goods issue posted. Only after this has been done, is the IDoc created.
PATH      Sales  Store order  Delivery  VL02N - Change     VL02N
ENTER     Outbound Delivery      from 2.4.2
BUTTON
TABSTRIP
ENTER     Pick quantity     >Purchase order quantity
BUTTON
MESSAGE     Outbound delivery ... saved
BUTTON
MESSAGE     Outbound delivery ... saved
BUTTON
2.4.4     Looking at IDoc DESADV
PATH     SAP menu  Tools  Business Communication  IDoc Basis       WE05
ENTER     Creation Date
Logical message
BUTTON
Outbound IDoc and inbound IDoc DESADV is displayed
Double click on IDoc DESADV in inbound
Expand the controlling tree Status records
Expand the controlling tree Application document posted
Note down the number of the message 0001 delivery (ies) of number ... to number ... created.
2 x
2.5     Post Goods Receipt with Reference to Shipping Notification in the Retail System
The retailer posts the goods receipt with reference to the shipping notification.
PATH      Merchandise logistics  Goods receipt  MB0A Goods Receipt for Other Reference     MB0A
ENTER     Movement Type
Site
Storage Location
Shipping Notif.     '101
VZ01
0001
See 2.4.4
BUTTON
BUTTON
MESSAGE     Document ... posted
BUTTON
2.6     Create Billing Documents in the Vendor System
2.6.1     Creating Billing Documents
The vendor creates a billing document that the retailer receives using EDI (IDoc in INVOIC format).
PATH      Sales  Billing  Billing Document  VF01 - Create     VF01
ENTER     Document      from 2.4.2
BUTTON
MESSAGE     Processing document ... .
Document ... saved
BUTTON
2.6.2     Looking at IDoc INVOIC
PATH     SAP menu  Tools  Business Communication  IDoc Basis       WE05
ENTER     Creation Date
Logical message
BUTTON
Outbound IDoc and inbound IDoc INVOIC is displayed
Double click on IDoc INVOIC in inbound
Expand the controlling tree Status records. Expand the controlling tree Application document posted
Note down the number of the message order number... saved.
2 x
2.7     Display Incoming Invoice in the Retail System
PATH     Retailing  Purchasing  Logistics invoice verification  Further processing  MIR4 - Display     MIR4
ENTER     Invoice doc. number     See 2.6.2
BUTTON
Thanks
Amit Shivhare
PS: Reward point

Are there any XI Development Guide ?

Hi Everybody,
I would like to know if there are any development guide to XI. I am using the Sap Infrastructure XI 2.0, but it is a compilation from de help. I need understand the comunication : Data_Base-XI-Sap using IDocs.
Thanks in advance.
Bye,
Renato.

Hi Lu,
Thank you very much ! It is a good documentation.
Now I am trying to send the Idoc to Sap but the error occurs :
<SAP:Code p1="The accessing object does not support the path //s" p2="MS1" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
Do you know any ideia ?
Thanks,
Renato.

How to Configure logical path and how to retrieve physical path for an IDOC

Hi ,
I want to configure logical path for an IDOC,
and then I need to retrieve Physical path from this logical path
using a FM (eg. FILE_GET_NAME).
How to configure the logical path for an idoc ?
Regards ,
Harshit Rungta

Using Logical Files in ABAP Programs
To create a physical file name from a logical file name in your ABAP programs, use the function module FILE_GET_NAME. To insert the function module call in your program, choose Edit ® Insert statement from the ABAP Editor screen. A dialog box appears. Select Call Function and enter FILE_GET_NAME. The parameters of this function module are listed below.
Import parameters
Parameters
Function
CLIENT
The maintenance tables for the logical files and paths are client-dependent. Therefore, the desired client can be imported. The current client is stored in the system field SY-MANDT.
LOGICAL_FILENAME
Enter the logical file name in upper case letters that you want to convert.
OPERATING_SYSTEM
You can import any operating system that is contained in the list in Transaction SF04 (see Assigning Operating Systems to Syntax Groups). The physical file name will be created according to the syntax group to which the operating system is linked. The default parameter is the value of the system field
SY-OPSYS.
PARAMETER_1
PARAMETER_2
If you specify these import parameters, the reserved words in the physical path names will be replaced by the imported values.
USE_PRESENTATION
_SERVER
With this flag you can decide whether to import the operating system of the presentation server instead of the operating system imported by the parameter OPERATING_SYSTEM.
WITH_FILE_EXTENSION
If you set this flag unequal to SPACE, the file format defined for the logical file name is appended to the physical file name.
Export Parameters
Parameters
Function
EMERGENCY_FLAG
If this parameter is unequal to SPACE, no physical name is defined in the logical path. An emergency physical name was created from table FILENAME and profile parameter DIR_GLOBAL.
FILE_FORMAT
This parameter is the file format defined for the logical file name. You can use this parameter, for example, to decide in which mode the file should be opened.
FILE_NAME
This parameter is the physical file name that you can use with the ABAP statements for working with files.
Exception Parameters
Parameters
Function
FILE_NOT_FOUND
This exception is raised if the logical file is not defined.
OTHERS
This exception is raised if other errors occur.
Suppose the logical file MYTEMP and the logical path TMP_SUB are defined as in the preceding topics and we have the following program:
DATA: FLAG,
      FORMAT(3),
      FNAME(60).
WRITE SY-OPSYS.
CALL FUNCTION 'FILE_GET_NAME'
     EXPORTING
          LOGICAL_FILENAME        = 'MYTEMP'
          OPERATING_SYSTEM        = SY-OPSYS
          PARAMETER_1             = '01'
     IMPORTING
          EMERGENCY_FLAG          = FLAG
          FILE_FORMAT             = FORMAT
          FILE_NAME               = FNAME
     EXCEPTIONS
          FILE_NOT_FOUND          = 1
          OTHERS                  = 2.
IF SY-SUBRC = 0.
WRITE: / 'Flag      :', FLAG,
         / 'Format    :', FORMAT,
         / 'Phys. Name:', FNAME.
ENDIF.
The output appears as follows:
HP-UX
FLAG :
FORMAT : BIN
Phys. Name: /tmp/TEST01
In this example, the R/3 System is running under the operating system HP-UX, which is member of the syntax group UNIX. The logical file name MYTEMP with the logical path TMP_SUB is converted into a physical file name /tmp/TEST01 as defined for the syntax group UNIX. The field FNAME can be used in the further flow of the program to work with file TEST01 in directory /tmp.
Suppose we have a logical file name EMPTY with the physical file name TEST, connected to a logical path that has no specification of a physical path. If you replace the EXPORTING parameter 'MYTEMP' with 'EMPTY' in the above example, the output appears as follows:
HP-UX
FLAG : X
FORMAT :
Phys. Name: /usr/sap/S11/SYS/global/TEST
The system created an emergency file name, whose path depends on the installation of the current R/3 System.

Error:IDOC_ADAPTER" ATTRIBUTE_INV_SND_PARTY : File to IDOC scenario .

Dear XI experts ,
Issue : Error to a new implementated SAP ERP SYSTEM . File to IDOC Scenario
Business Scenario : Exchange Rates from Thomas REuters (XML) - > XI-> SAP 1 , SAP 2 ERP Systems ( 2 diff SAP ERP systems)
SAP 2 is a new system set up for a new plant of our Organization.
The Excahnge rate is gettiong updated by IDOC: EXCHANGERATE.EXCHANGE_RATE01 in two SAP Systems
Each one is configured with diffrent IDOC receiver .
The Error is : for the SAP 2 system . The MEssage gets branched and one message is successfully sent to SAP1 , and turns an error : in SXMB_MONI for SAP2 system
I had been thropugh few blogs have performed the below steps:
-IDOC metadata : IDX2 have configured in XI
-checked the port of EGP , Partner Profile in SAP 2 ERP system
-Checked IDX1 , IDX2 of SAPEGP in XI .
-Refreshed business system .
-Tried to send the xml data from the start point through File Zilla(FTP)
Could somehow help as this is Production issue ans this is affecting the business.
Error from SXMB_MONI:
<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_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Reuters</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Reuters to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Reuters : is the Sender Party of Exchange Rates. I have seen in blogs to craete agency / schema , but since thsi scenario is 2 seperate SAP ERP systems , my question is do i need to create agency , schema for sender party .
Appreciate your Input
Thank you,
Vara
Edited by: Varalakshmi SB on Oct 26, 2011 12:14 PM
Edited by: Varalakshmi SB on Oct 26, 2011 12:16 PM

agency and scheme are used when your doing B2B scenarios.

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

Logiacal path deactivate in IDOC

Dear Sir,
We are doing the hardware migration project.
hence we have installed new SAP system in new H/W and completed the data migration from production system.
Now we are in the testing phase, so we would like to disable the entry temporarily in
Idoc new SAP system(Trns: File) to avoid the disturbance of production system.
We want to use the same logical path again for multiple testing
Could someone tell me how to inactive(Prodcution server IP address logical path) temporarily the entry in File transaction. ?
Thanks
Elumalai

I would just put a fake entry in your hosts file like
127.0.0.2 <hostname-of-production-system>
Since 127.* are lookback addresses the system will try to connect to itself (and fail) and hence your production will not be impacted.
Markus

Idoc archival Path

Hi Guys,
I want to know the path where idoc been archived? Is it somewhere in the sap database or at operating system level?. If it is at operating system level, can you let me know how to find the path where idocs are achived.
Thanks in advance,
Harikrishna.

Hi Hari,
archive files will not be stored in the database; it will be stored in the file system at operating system level (or on any of the mounted file systems). another possibility is that it can be stored in an external storage system if you are using one.
You can know the path as follows (if it is stored in the file system):
- go to transaction SARA
- enter object name as IDOC and enter
- click on management
- expand the tree of 'complete archive session'
- select any of the recent archive sessions and expand the tree to the maximum level
- then double click on any of the archive files, you will see the path where the file is archived and file name of the archive file
hope this helps,
Naveen

How do we find out the file path which the IDOC is stored.

Hi,
If we use T-code: AL11, we can see the file path of the Unix server. And some IDOC outbound file is also stored in some file path after generated.
If i generated an outbound IDOC, how do i know in which file path it stored??
Thanks

Hi,
Go to control record of the outbound IDOC.
go to partner tab, check the port under sender information.
the outbound file path will be configured with your port.
Use T-code WE21, the concerned port will be available under section 'File'
Directory under tab Outbound file will show the path under which file has been stored.

IDOC_ADAPTER.RECEIVER_BSI_INCORRECT

Hi,
I'm trying to send an IDOC to a SAP system (IQ1_100) from XI. I've defined a technical system (IQ1) and a business system (IQ1_100) in SLD. The corresponding logical system is also named IQ1_100. In Integration Builder configuration, the receiver of the IDOC is IQ1_100 - IDOC Adapter with port SAPIQ1, RFC-destination IQ1_100. (so maintained in SM59) In XML-monitor all messages send to this receiver fail in step 'call Adapter' with the following error:
Code: IDOC_ADAPTER.RECEIVER_BSI_INCORRECT
Unable to convert partner to IDoc receiver partner.
What did I miss???
Thank you for any help, regards, Kathrin!

Hello Kathrin,
Please make sure that the ALE name for your receiving (and sending) systems in SLD is in UPPER case only. Then you can try this:
1. In Integration Directory (Configuration).
   Follow menu path: Environment -> Clear SLD data cache.
2. In the transaction SXI_CACHE.
   - F6 (complete cache refresh)
   - Follow menu path: Goto -> Business System. Choose the busine
     system and press the button #Compare Data#.
Hope this will help.
Kind regards Johan

Problem with File to IDOC scenario

Hello,
I try to implement our first scenario to IDOC.
In TOC SXMB_MONI I have to errors
1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
Any idea how I can solve this problems?
Elad

HI,
I think u have not done the configuration at the R3 end....
Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

IDOC Adapter Error

Hi All,
My scenario is JDBC to IDOC, where I am fetching data from Database and posting an IDOC in SAP. My ALE Configuration is correct. I have done the following steps:
In XI:
1. Created RFC destination to connect to ECC system
2. Created Port in IDX1
3. Imported Meta-data in IDX2
In ECC:
1. Defined Logical system
2. Partner Profile settings.
Still, I am getting the below error, not sure why is this occuring...
<?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_RCV_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone help me out with what could be the cause of the error.
Thanks in advance.
Regards,
Amit

Hi Amit,
check this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
OR Check the receiver IDOC setting in my posting on Wiki
for File to IDOC scenario are u missing something
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
copy and paste complete link in URL or click here
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC& then Part3
Sachin
Message was edited by:
Sachin Dhingra

IDOC - Idoc_adapter.sender_bsi_incorrect (path //s)

Similar Messages

Maybe you are looking for