Status Code 56; Idoc is added with errors

file 2 idoc :
i am getting error 56(idoc is added with errors).
data was picked successfully from legacy system and sent to xi.. sxmb_moni shows success but in target r/3 weo5 shows error 56......plz anyone give me answer//

answered

Similar Messages

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

How to update the status of Outbound IDOC in case of error

I want to know about how to update the status of Outbound IDOC in case of error.
I am using message control functionality here.

HI,
If u r using the standard message and basic type
u can do it in the FM attached to the basic and message type.There u need to write ur own message instead of standard SAP message..chek if there r any userexits available in the FM..where u can overwrite ur own message ..
If u r using the Zmessage and Zbasic type
then u need to declare an internal table of EDIDS structure and then append ur message to the internal table..
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-msgty = <message type>
idoc_status-msgid = message-id.
idoc_status-msgno = message-number.
idoc_status-msgv1 = message-message_v1.
idoc_status-repid = sy-repid.
idoc_status-status = <give the error status>.
APPEND idoc_status.
Reward if u find useful
Regards,
Nagaraj

Exit code: 6 Silent workflow completed with errors

I'm trying to create a silent install package for Dreamweaver
CS3. I followed the steps listed in previous listings and created a
application.xml.override file and run the setup.exe with the
--mode=silent and the --deploymentFile=deployment.xml. After the
install is ran, I get Exit code: 6 Silent workflow completed with
errors and notice that the Adobe add ons are installed but no the
actual Dreamweaver application. Anyone have ideas on resolving this
and getting the install to work properly?

Looks like the first two warnings are security level warnings meaning that your silent install will not grant the correct security level for what ever reason. I suspect it needs admin level maybe?
Here is a link. Read #8 as it has to do with silent installs. The log will give you more hints on what you did wrong.
http://kb2.adobe.com/cps/829/cpsid_82942.html

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

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.

SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

Hi,
This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
So far I have installed
http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
2012 release.
Here is the detail of error message:
TITLE: Package Validation Error
Package Validation Error
ADDITIONAL INFORMATION:
Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection
Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Task: There were errors during task validation.
Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
(Microsoft.DataTransformationServices.VsIntegration)
Here are my environment details:
SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
Services Project2\Integration Services Project2\Package.dtsx.
Does this kind of Shared drives have any impact to give this issue?
Thanks in advance!
Ketan
P.S.: I had look at this forum question -->
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

Hi Arthur,
Thanks for your response.
Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
1) Some times excel source files cannot be parsed by excel source connection manager.
2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage while destination mapping.
3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file. <-- For
this we tried IMEX setting also
4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
Do you think it is advisable to convert Excel into CSV or Flat file.
Thanks,
Ketan

Two status for one idoc while IDOC_STATUS_WRITE_TO_DATABASE, giving error

Hi
I am using a Z function module to process an incoming idoc (custom process code).
While using the test tool WE19, I am trying to process an idoc. When I am using Inbound Function Module tab, the idoc is processing normally. But when I am using Standard Inbound, it is giving me message Idoc saved but cannot or should be processed.
Idoc was in status 64.
I tried debugging and found that idoc (while processing from Standard Inbound) in FM IDOC_STATUS_WRITE_TO_DATABASE, it is giving an error message because two status are present for the same Idoc.
While processing from Inbound function module, there is only one status in FM IDOC_STATUS_WRITE_TO_DATABASE and idoc is processing successfully.
Please advice, if anyone know why it is happening and how it is happening. I have not searched for SAP notes.

Hi,
Check in your partner profile inbound parameters what options is selected. Trigger Immediately or Trigger by background program. Select Trigger immediately and try processing the idoc once again.
KR Jaideep,

Error while updating the status record of IDOC in SAP

Hi All,
I am facing this problem. I have done outbound processing and IDOC was sent successfully from SAP to EDI system and it was processed in EDI and now EDI system wants to send the status back to SAP with a status message and the status number that we are using is '24' and we have mapped all the fields in the status table EDIDS and made sure that EDI system sends all those and I think Counter field can not be determined by EDI system so EDI system used the counter '1' since it can not determine how many counters are already there in SAP and unless we pass the value to this counter field we were getting the error. After passing all the values the status of the IDOC is updated with the status '00' instead of '24' and we do not know why it is happened and I would like to know how SAP converts the status record that is received from the EDI system.
Please let me know how the status record will be translated into SAP from EDI system and I ahve followed basically EDIDS structure and the IDOC status is updating in SAP but with wrong status number and the alignemnt also missing in SAP fields like if I give some text in the EDI it is splitting and storing in 2 fields.
Please help me in this and I think I have explained the problem in a detail manner.
Thanks,
Ramesh.

Hi Naresh,
Thanks for the reply and my question is since EDI system is able to send the status back to SAP from EDI system and only problem is it is updatinf the status wrong and I have checked the EDIDS table also and the entry is creating with another counter and please confirm me that it is because of EDI does not support the status record update so that I can confirm to the client that there is nothing wrong in the way SAP functions and EDI system can not update the status code in the SAP.
Thanks,
Ramesh.

Ale Idocs Status code 64

Hi,
While processing inbound idocs, I am encountering status code 64 (IDoc ready to be transferred to application) . Can any one help in avoiding this status code.
Helpful answers will be rewarded.

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Although the partner profile is defined and the IDoc has been received, the IDoc cannot be transferred to the application.
You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report.
Check the processing mode for the IDoc in the partner profile:
Processing mode 1: The system transmits the IDoc immediately after receipt in the application.
Output mode 3: The system collects received IDocs.
IDocs are not intended to be transmitted directly to the application.
Status 64 in the IDoc can normally only occur in conjunction with processing mode 3 and output mode 2.

SCCM Client Instalaltion failed with error code 1624

Folks,
I am getting clients installation failed exit code 1624 and
CcmSetup failed with error code 0x80070658

- Check the access to the adminshare from the SCCM server
\\computer\admin$
- Run the wbemtest.exe to see if you can connect to the systems namespace
- Verify DNS records on your DNS server
- Renew dns
Ipconfig /flushdns
Ipconfig /registerdns
Kind regards,
Tim
MCITP, MCTS, MCSA
http://directoryadmin.blogspot.com
This posting is provided 'AS IS' with no warranties or guarantees and confers no rights.
"If this thread answered your question, please click on "Mark as Answer"

Need all transaction codes for idocs

need all transaction codes for idocs

Hi,
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
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
BAPI tcode --- BAPI.
Also:
IDOC:
IDOC ADMINISTRATION
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
WE60 IDoc type documentation tool
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.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
1.4 IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
WE19 EDI test tool. Use to test inbound Function module changes.
WE31 Segment create
WE30 Create IDoc extension type
WE82 Link Release detail to Extension IDoc Type
WE57 Assign function module to logical message and IDoc type
BAPI: BAPI, SWO1.
Transaction codes Related for IDOC Configurations
WEDI: Area Menu for IDOCs
WE02: Display IDoc
WE19: ALE Test tool
WE30: Development of IDOC Type
WE31: Development of IDOC Segment
WE41: Process Codes, Outbound
WE42: Process Codes, Inbound
WE47: Status Maintenance
WE81: Logical Message Types
WE57: Assignment Messages for Appl. Objs
SM59: RFC Destinations (Display/Maintain)
SALE: Display ALE Customizing
BD54: Maintaining Logical Systems
BD67: Maintain methods (inbound)
BD64: Maintenance of Distribution Model
BD87: Status Monitor for ALE Messages
Reward points if found helpful...
Cheers,
Chandra Sekhar.

OutputTask Status Code: -223026

I am using channel expansion to setup a number of input channels from a PXI chassis 4461 & 4498 as an InputTask. As well, I am also settting up the output channels on the 4461 as an OutputTask. The application is for a burst random where the Input & Output tasks are synchonized with one another.
Both the input & output tasks verify correctly. However, when I try to collect the input data - which is used as the trigger to start the OutputTask - get some errors.
The first is,
A first chance exception of type 'NationalInstruments.DAQmx.DaqException' occurred in NationalInstruments.DAQmx.dll
?ex
{Error=Expression expected. Message="Property must have the same value for all channels on this device.
Property: NationalInstruments.DAQmx.Timing.ReferenceClockSource
Task Name: InputTask
Status Code: -200106"}
_HResult: -2146233087
_message: "Property must have the same value for all channels on this device. Property: NationalInstruments.DAQmx.Timing.ReferenceClockSource Task Name: InputTask Status Code: -200106"
Data&colon; {System.Collections.ListDictionaryInternal}
Error: -200106
HelpLink: Nothing
HResult: -2146233087
InnerException: Nothing
IPForWatsonBuckets: 249626407
IsTransient: False
Message: "Property must have the same value for all channels on this device. Property: NationalInstruments.DAQmx.Timing.ReferenceClockSource Task Name: InputTask Status Code: -200106"
RemoteStackTrace: Nothing
Source: "NationalInstruments.DAQmx"
StackTrace: " at nNIMSSAIL100.StatusObserverT<nNIMSSAIL100::ApiTraits<nNIMSSAIL100:otNetApi> >.CheckWithName(StatusObserverT<nNIMSSAIL100::ApiTraits<nNIMSSAIL100:otNetApi> >* , tCaseInsensitiveBasicString<unsigned short\,_STL::char_traits<unsigned short>\,_STL::allocator<unsigned short>\,nNIDMXS100::tLocaleConsideringWideStringComparitor\,nNIDMXS100::tLocaleConsideringWideStringCaseForcer>* pName) at nNINETAI2005100.Read2D<class nNIMSSAIL100::ApiTraits<class nNIMSSAIL100:otNetApi>,class nNIMSSAIL100::AnalogRead,double>(Task task, tNumChannels channels, Int32 samplesPerChannel, tNumLines lines, Double timeout, Boolean interleaved) at NationalInstruments.DAQmx.Internal.AnalogMultiChannelReaderImpl.ReadMultiSample(Int32 samplesPerChannel) at NationalInstruments.DAQmx.AnalogMultiChannelReader.ReadMultiSample(Int32 samplesPerChannel) at Vibrant.Mechanics.Acquisitions.Devices.NationalInstruments44xx.OnStartAcquireFreeRun() in C:\Developer\Vibrant.Mechanics.Acquisitions\Devices\NationalIns
truments44xx.vb:line 638"
TargetSite: {Void nNIMSSAIL100.StatusObserverT<nNIMSSAIL100::ApiTraits<nNIMSSAIL100:otNetApi> >.CheckWithName(nNIMSSAIL100.StatusObserverT<nNIMSSAIL100::ApiTraits<nNIMSSAIL100:otNetApi> >*, nNIDMXS100.tCaseInsensitiveBasicString<unsigned short\,_STL::char_traits<unsigned short>\,_STL::allocator<unsigned short>\,nNIDMXS100::tLocaleConsideringWideStringComparitor\,nNIDMXS100::tLocaleConsideringWideStringCaseForcer>*)}
WatsonBuckets: Nothing
?ex.InnerException
Nothing
Both the Input & Output tasks use the same sample clock.
The otyher error came out when I attempted the same operation again,
"Internal Software Error occurred in DSA software. Please contact National Instruments Support. Task Name: OutputTask Status Code: -223026" {String}
String: "Internal Software Error occurred in DSA software. Please contact National Instruments Support. Task Name: OutputTask Status Code: -223026"
I'm not ure what the error codes -200106 or -223026 represent, or why NIDAQmx v9.80f0 is telling me that the reference clock is different betwen input channels of the InputTask.
Of note is that if I do not configure an OutputTask, then acquisition proceeds without error.
Any insight as to what is going on here? Tests that I might run?
TIA;
Patrick

Hello Pat,
The error code is pointing the property timing reference clock source, and according to your description since you are programming a synchronization it makes sense. So you are right in your last post and you should review how you are using that property according to the manual. The documentation for DSA devices point us to the NI Dynamic Signal Acquisition manual (page 2-22).
This should provide you examples:
Synchronizing Dynamic Signal Acquisition (DSA) Products with NI-DAQmx
Regards
Frank R.

Status 56 - IDOC with errors added

Hi everyone,
 I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "EDI: Partner Profile not available".
 but i had already created Partner profile in WE20.
Regards,
Varun Reddy.K

Hi Varun,
 The below link will help u in solving u r problem
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Just try follow the steps followed in above mentioned link
And also check u r RFC connection in TC "SM59".
Reward with ponits if helpful
Regards
Sai Ganesh

Idoc inbound error status code 56

Hi,
   when i am sending custom idoc from source system to destination , idoc sent successfully from source system .But in the receiver system idoc status code is 56 ( idoc with errors added) .
partner profile also available in the receiver system. How to solve the error.can any one pls give me the solution.
                                                                                Regards,
                                                                                Suhash.

Hi,
Check this link..[IDOC Status code 56 !!   |IDOC Status code 56 !!]
[Re: Status 56 - IDOC with errors added   |Status 56 - IDOC with errors added]
Edited by: Avinash Kodarapu on Mar 19, 2009 4:55 PM

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,
Chilanka

Hi,
>>>>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">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Status Code 56; Idoc is added with errors

Similar Messages

Maybe you are looking for