on 02-07-2006 9:01 PM
Hi ,
When I am trying to post vendor data into R/3 system from flat file, I got an error in R3 System as
"IDoc: 00000000000525200 Status: IDoc with errors added"
"EDI : Partner profile not available"
Please advice
Thnx
Andy
Hi Andy,
Make sure that you have partner profile defined in the backend R/3 system with inbound parameters for the message type CREMAS. Use Tr.code We20 to define this.
Rgds,
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pls maintain the partner profile entries in WE20 for the values in control record of the created IDOC...
Open the IDOC in WE02, check the control record values for sender system and sender type...
In WE20, for this sender system, maintain the inbound parameters for the vendor master IDOC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andy,
Adding to the pose by Renijith, Each Idoc structure will have Control Record, Data record and status record.
The control record is represented by segment "EDI_DC40" with the values for message type, idoc type, sender port,sender partner, receiver port and receiver partner and so on.
You have to provide these values in the "EDI_DC40" segment of your mapping when you checked the option "Apply control record values from Payload" in the Idoc Communication Channel.
Hi Andy,
it is not a question on what you did in mapping (disable control record) it is a question on how ALE works in SAP. Every IDoc does need to have a control record. There is no way to send an IDoc into SAP without a control record. What happens if you disable that in the mapping: XI will automatically create it for you based on your configuration. Refer to SAP note 720245 IDoc adapter: Outbound control record generation for more information on which values XI will put in there.
Best regards
Christine
Hi Andy,
When you disable the EDI_DC40 field, the Idoc Adapter constructs the Control record based on the info from SLD.
Please follow the below steps to make your scenario to work.
In XI
1)Define the Logical System for the Sender Business System in SLD.
2)Make sure this infomation about LS shows up in the "Adapter Specific Identifiers" of the Business System in XI Configuration. If not, Clear the SLD Cache and try it again.
In R/3
1)Define the logical system in the R/3 using Tr.code BD54.
2) Maintain the Partner Profile for this Logical system using TR.Code WE20 and define inbound parameters for the message type CREMAS.
Try sending the message again.
Hope this helps.
Rgds,
Sam Raju
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.