IDOC Interface Error
Hi Experts,
I am getting the same error: and from the forums I came to know that we need to use the IDOC name in the Interface mapping.
I used the modified IDOC structure(External Definition) in mapping, but when I select the original interface in Interface mapping I am not able to get the message mapping name.
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>MI_IDOC_IA</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_IDOC_IA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please provide me some hint.
regards,
sri.
Hi Sri,
I used the modified IDOC structure(External Definition) in mapping,
but when I select the original interface in Interface mapping I am not able
to get the message mapping name
Are you following the steps as mentioned in the blog /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change or SAP note 814393
Are you creating any separate Message interface after creating the External Definition?Pls don't create any separate interface.
just export the XSD of the IDOC and change the occurrence (dont save ED with any other name ,keep the same IDOC name)
now in message mapping import the XSD you save earlier. and do the mapping.
In Interface mapping and in the ID configuration use the imported IDOC name only
Regards,
Srinivas
Edited by: Srinivas on May 15, 2010 10:15 PM
Similar Messages
-
File-IDOC, idoc interface error
Hi,
Scenario: File-IDOC (Multiple records in source file to be mapped to multiple CREMAS IDOCs) without BPM.
Modified the occurance(maxOccurs = 'unbounded') in XSD structure of IDOC(CREMAS) and saved it as external definition.
I have <b>used this external definition in message mapping and interface mapping</b>.
In configuration, i have used the same message interface (corresponding to external definition) as inbound interface.
Now, I get the following error.
- <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_WRONG_INTF</SAP:Code>
<SAP:P1><b>MI_Cremas04_multi_external</b></SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>Unable to interpret IDoc interface MI_Cremas04_multi_external</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.Hi,
>>I have used this external definition in message mapping and interface mapping.
In interface mapping you need to use <b>Imported IDOC</b> not <b>External definition</b>
This solves your problem.
let me know if you have any issues still.
Cheers,
Jag -
Unable to interpret IDoc interface Error
Hi All,
We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
Has anyone faced a similar problem ? If so please let me know how you fixed it.
Appreciate your help
Regards,
Madhuhave you seend below threads:
[link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
[link2|IDOC Error; -
Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit -
Idoc interface not found..
I'm attempting to pull in an XML file to Idoc and I'm getting an error stating "Unable to interpret IDoc interface ZINCOMINGINVOICE_CREATEFROMD01" in the monitor.
I have imported the Idoc into XI and mapped to it and the translation is working fine. I have also gone into IDX1 and IDX2 on the target R/3 system and on the XI system and setup the port and Idoc in the inbound list. I have also managed the port and setup the inbound document in WE20 and WE21 on the target R/3 system.
I have a couple questions.
1. Have I done all the setup?
2. With the Idoc of ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 and the setup above for WE20 inbound set to ZINCOMINGINVOICE_CREATEFROMDAT is that sufficient?
3. Likewise with the ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 idoc and IDX2 set to ZINCOMINGINVOICE_CREATEFROMD01 is that sufficient?
My inbound xml document is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <ZINCOMINGINVOICE_CREATEFROMD01>
- <IDOC BEGIN="1">
- <Z1BP_INCINV_CREATE_HEADER SEGMENT="1">
<INVOICE_IND>X</INVOICE_IND>
<DOC_TYPE>ZA</DOC_TYPE>
<DOC_DATE>2001-04-20T23:59:20-07:00</DOC_DATE>
<PSTNG_DATE>2005/05/02</PSTNG_DATE>
<REF_DOC_NO>123456</REF_DOC_NO>
<CURRENCY>USD</CURRENCY>
<GROSS_AMOUNT>4900</GROSS_AMOUNT>
<HEADER_TXT>[email protected]</HEADER_TXT>
</Z1BP_INCINV_CREATE_HEADER>
- <Z1BP_INCINV_CREATE_ITEM SEGMENT="1">
<INVOICE_DOC_ITEM>1</INVOICE_DOC_ITEM>
<PO_NUMBER />
<PO_ITEM>2</PO_ITEM>
<ITEM_AMOUNT>130</ITEM_AMOUNT>
<QUANTITY>30</QUANTITY>
<PO_UNIT>EA</PO_UNIT>
</Z1BP_INCINV_CREATE_ITEM>
</IDOC>
</ZINCOMINGINVOICE_CREATEFROMD01>Hello,
I encountered the same problem. If you are sure to have configure correctly your IDX2 transaction, be sure you have import the idoc in the repository under the good composant.
For example if IDOC is for R/3 4.6, import your idoc under SAP APPL 4.6C or SAP BASIS 4.6C to use it in the directory with a component that you defined before in your SLD as a SAP R/3 product.
Regards,
Chris -
Unable to interpret IDoc interface ReplenishmentOrderNotification_In
Hi All,
I am trsfering orders03 idoc from r/3 4.5 B system to XI and from XI to SNC system using idoc adapter.
In sxmb_moni, When I double click on particular XML message with errors
I am getting error in call adapter
details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>ReplenishmentOrderNotification_In</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Hi
I am creating JDBC to IDOC scenario but experiencing the same issue.
Can you advise how you solved this?
Thanks. -
Regarding AS2 seeburger to idoc interface
Hi Team,
I hope you are doing well.
I am working on as2 seeburger to idoc interface.
what are the steps required for this in IR and ID ?
where can we monitor if we get the error in as2 adapter side?
Regards
ANJANHi,
>>>what are the steps required for this in IR and ID ?
In ESR:
1.First you need to get the xsd of EDI document and import it into ESR under External definitions and import the IDoc also into ESR.
2. Create a service interface for the EDI document structure.
3.create message mapping between the ED(xsd of EDI doc) and Idoc.
4.Create operation mapping.
In ID:
1.Configure the parties using the AS2 IDs.
2.Create an AS2 sender communication channel(refer the configuration guide that you receive from seeburger).
3.Create an IDOC receiver communication channel.
All the remaining steps are same what we do for normal scenarios like receiver determination,interface determination and agreements.
>>>where can we monitor if we get the error in as2 adapter side?
In Seeburger workbench
Regards,
Priyanka -
Hi,
We have the following set up:
A JMS sender channel sends IDocs in a non XML format (some kind of flat file IDoc). I created a ABAP mapping that converts this flat IDoc to an XML IDoc. The problem is, that the sender sends diffrent kind of IDocs through the same channel.
1.try: I imported all possible IDoc types and tryed to do a content based routing. The problem is the input message. Due the fact, that this is no XML on input side, I cannot check the input data. Is there a possibility to do content based routing AFTER the mapping?
2.try: I created a dummy IDoc interface. The message type is just one tag (I created the complete IDoc XML in the ABAP mapping). So I send all data from the JMS to an IDoc receiver with the same dummy interface. The content of the receiver message contains all IDoc control data (EDI_DC40). The idea is, to use this interface as an generic IDoc interface but I get the error "ATTRIBUTE_WRONG_INTF" - "Unable to interpret IDoc interface MI_IDoc_any_IB_Async". Is there a way to set the IDoc attributes generic in the ABAP mapping or do I have to use the IDoc interface, that I imported?
Thanks for your help
JP1. The use of BPM may ease the routing part after mapping wherein u may use transform step folowed by send step
2. While doing idoc communication, even if u change the structure, u ll have to use the interface name as the original imported idoc name only. Otherwise u ll get the same error.
Regards,
Prateek -
Unable to interpret IDoc interface ZSHIPDEL_packageRD
Hi,
I am doing a file-xi-idoc scenerio.
I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.
However I get the following error message at runtime (Call Adapter):
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ZSHIPDEL_packageRD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Has anyone else experienced this error?
Regards
leenorI have a scenario exactly like the above one.
My file structure is like
TransactionDetailList
TransactionDetail (1:N)
Transaction_Type (0:1)
Transaction_Date (0:1)
Add_Revise_Cancel_USER_ID (0:1)
Add_Revise_Cancel_Date_Time (0:1)
My IDOC has the below structure,
ZIDOC_BDS_DIVERSION
IDOC
ZSEGL_DIVERSION_HEADER
SEGMENT
NOMNR
NOMIT
EVENT_DATE
ZSEGL_ DIVERSION_ITEM
SEGMENT
WHO_PAYS_DIVERSI
LOCID
DEST_CITY
so i have to generate multiple idocs in the target side.
I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.
In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.
I am getting the following errors like,
"Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="
Please let me know if I am missing some steps while configuring or I have to do something else.
Thanks & Regards,
Mukesh -
IDOC Adapter error / ATTRIBUTE_WRONG_INTF
Hi at all,
I have a problem regarding a interface sending IDOCs ( messagetype HRMD_A ) from one R/3 to another R/3 system via XI.
I have created a new Message Interface which has the Message Type of the imported IDOC typ ( HRMD_A06 ).
When the system tries to process the inbound IDOC I get the following message :
<!-- Call Adapter
-->
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>MI_HR_A_Cas</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_HR_A_Cas</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Where can the problem be located ??
Why can't the IDOC interface be interpreted ?
I hope somebody can give me an advise.
Thanks
FlorianHi Florian,
my solution:
Create a simple BPM which will handle your situation
BPM:
reveicer step -> check step -> (transformation one or two ) -> send step
in bpm you can use as many message interfaces (abstract idoc ) as you want
Regards,
michal
Message was edited by: Michal Krawczyk -
Unable to interpret IDoc interface
Hi,
I have a File to multiple IDOC scenario. I have change the IDOC occurance by creating ED.
I have developed everything but the following error is coming during my end to end testing.
Unable to interpret IDoc interface
Thanks,
RajRaj Says..
I have change the IDOC occurance by creating ED.
Hi Raj,
Since you have changed the IDOC occurrences by creating an ED so you have to make sure that IDOC and ED has been used properly in your scenario.
1. MM = use ED
2. IM = use original IDOC
3. ID = use original IDOC
Regards,
Madan Agrawal -
Hello all,
Can somebody send me documentation over Idoc interfaces? I need for Inbound now...but Outbound will be helpful though for future use )
And I have a question related to middleware too. A flat file will be the input to middleware (XI or webmethods). What is the output? Is it an IDOC format file or IDOCS with status 64 in SAP?
Thanks,
Message was edited by: SomenHi,
For inbound idoc in partner profiles if you set trigger immediately for a message type , whenever idoc comes from middleware , it will be processed automatically . for process success idoc status will become 53, if it is failed idoc status becomes 51.
at partner profiles if idoc process selected as process through background program , whenever idoc comes from middleware it goes to 64 status. for these idoc's we need to schedule RBDAPP01 program to process 64 status idoc's or we can process these idoc's from BD87 transaction
Check these links:
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm
http://www.sappoint.com/ppt/ale.ppt
below details might help you.
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
WEDI - main transaction for all ALE settings
Regards
Appana
*Award Points for helpful answers -
Hi Experts,
I am working on ALE IDoCS Interfaces... Can anyone send me the step by step procedure for creating a sample ALE,IDOC scenario where i can send a message from client1(800) to client(810).
I need the following
1.complete ALE configuration setting between two clients.
2.Creation of Idoc , segment, filling the idoc from scratch.
3.Dispatching the Idoc on the ALE Interface
4.Handling any exceptions
Is it possible to create an ALE Interface to the same client(800 to 800) for sample testing
Thanks and Regards
AKHai Ashok
Go through the following Steps
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
Thanks & regards
Sreenivasulu P -
GL Balance Inbound Idoc Interface
Hi Experts,
We are evaluating the option of G/L Balances upload using Idoc (Interface) from Legacy System.
Basically I am looking for the Error handling Conditions in Idoc.
If anybody has experience on working on Idoc for GL balance upload from Legacy system, please share your experiences with me.
Appreciate your help on this.
Thanks
SJYou can use IDOC type ACC_GL_POSTING01 for GL Postings and can use LSMW or any custom program for this IDOC.
-
Issues in IDoc Sender Scenario:IDoc with errors added
Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
ChilankaHi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
Maybe you are looking for
-
Aperture 3.0 not importing RAW files from Canon T1i
I have recently upgraded to Aperture 3.0. I shoot with Canon T1i in RAW+JPG file size. When importing files from Canon T1i for the first time to Aperture 3.0, I found that all files imported as jpg not RAW. How do I get the RAW files? Help!!! Anjali
-
i am executing the following pl/sql block an getting error DECLARE ERROR at line 1: ORA-01405: fetched column value is NULL DECLARE l_bfile BFILE; l_clob CLOB; l_parser dbms_xmlparser.Parser; l_doc dbms_xmldom.DOMDocument; l_nl dbms_xmldom.DOMNodeLis
-
SQL History - returning wrong statement if history is sorted
I have searched the forum and not seen anything on this, but I have been getting the wrong SQL statement returned when I select Append/Replace. I have statements going back to 12-Jan-06 (using 804 since 13-Jan-06, 796 since 12-Jan-06 and 715 last yea
-
How to get HFMUtilities for 11.1.2.1?
Hi Does anyone know where to find HFMUtilities for 11.1.2.1 version? I don't see anything as part of installation. Thanks in advance! PM
-
Hi Guys, I want to export a long list of selected tables, i can retrive table names from database dictionary, how can i copy my script in sqlldr instead of typing each table name, there might be any easy option, i might not know, any help would be gr