Intercompany EDI error

Hi Friends,
I am facing a typical problem, our Intercompany billing is set where we have Customer and Vendor assigned in WEL1 (14 digit numbers), Configuration in FI/MM maintained, Partner Profiles (BP & VN) maintained, Port created and assigned to the Outbound partner profile with Message types and all the triggering parameters are set to immediate.
Now, despite of all the settings being in place, my Outbound IDOC gets to the Port (Status Green) but my inbound status is giving me a message
"EDI: Partner profile inbound not available"
I checked and re checked the config, and the tables, EDIDC, EDPP1, EDP21, EDP13, and find the partner profiles in place...but getting the errors.
Please let me know where else I need to look,
Thanks
Ravi

Friend,
I am not exagerating..I have Inbound Profile in place..I am breaking my head to see where it went wrong..
Need your help
Thanks

Similar Messages

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?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_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

ACH Edi error report

I am currently working on setting up ACH process for a client using the SAP's standard IDOC process. Once the bank receives the ACH Idoc, if there any errors such as vendor account number missing, they send an edi error file back. Client is asking if there a way to set up SAP to automatically reverse the payment for that particular vendor upon receiving the error file from the bank.
Please advice if anybody has experience with this scenario.

user3045615 wrote:
Returns: Error report - Connection reset by peer: socket write error when executing SQL script in an Oracle 12.1.0.2.0 Enterprise Edition database (residing on a remote Microsoft Windows x86 64-bit) user schema (datamart).
Initially, the error occured when the script attempted to compile a PL/SQL package body (1125 lines of code). Another script successfully compiled 4 larger PL/SQL package bodies (all exceed 1125 lines of code) in a different user schema (staging).
Now, the error occurs in staging user schema when calling a PL/SQL package.
Ray
Is GOOGLE broken for you?
sockets - What does "connection reset by peer" mean? - Stack Overflow
I am not convinced that your error has much, if anything, to do with Oracle.
In the future use COPY & PASTE so we can really see what you actually do & what the complete response is.

Determining which EDI Error Messages are related to "Tasks"

Our company uses EDI heavily and have many errors which our business community wiill process. I do not know how other companies are handling this "EDI workflow", but we do this through transaction PPOM. We have created an overall EDIORG organization along with positions for different areas of responsibility. We then need to assign the "appropriate tasks" to each position & also assign the correct position to the Partner profiles to ensure the correct people see the errors.
My question is how can II determine which "Tasks" are assign to the specific message errors that end up coming in? Most Tasks are by Idoc type --- do I just have to assume that any error related to that IDoc type would be covered?
Thanks so much for any input as to "Controlling the EDI Error processing" by business users!
Britte

Hi surya,
You are saying 1122124 is IDOC numner & its not relevant to this idoc.
What it means,can u explain??? Actually there will be a chance an IDOC can mapped to N no of documents. This mapping will done through a BADI internally.
Regards
KER

How to Identify EDI errors in inbound IDocu0092s?

hi,
I just want to know how to identify EDI errors in inbound IDocs?

Hi
Ref this links
http://www.hibcc.org/EBUS/editemplates.htm
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
/people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
With Seeburger we can conver to edi format to XML
seeburger doc
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Doc for Conversions-
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Thanx
Bommireddy.Sridhar

Task ALE/EDI: Error handl cannot be started immediately

When an IDOC is being created in SAP(3.1I) from an external system(Gentran GIS), it is added with errors status 56. The error text states as 'Task ALE/EDI: Error handl cannot be started immediately
'The task ALE/EDI: Error handl (no. TS00008068) cannot be started immediately by user GIS'.
Can anyone advise where the user 'GIS' need to be added to avoid getting that IDOC error

Hi Bhaskara,
This can be caused by several issues:
1. The user GIS has NO authorization to run workflows or to run this specific workflow task (TS00008068).
2. The user GIS has NO authorization to run function module EDI_ROLE_FOR_PROCESSING (or when running this function module it will return data in the ACTOR_TAB, which means that the workflow cannot be started by default users).
3. Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Post processing: permitted agent) an agent has been defined that will not resolve to the user GIS (and therefore this user is NOT allowed to do post processing).
Most likely issue 3 is here at hand. If this is the case, REMOVE the entry for the agent (or consider to setup an organisational unit/work center and make GIS a member).
The error, by the way, is an inbound processing error. It is possible that in the ALE layer something has not been defined properly.
Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Inbound options" and double-click on the entered Process code.
You must now check the entries here.
Example:
If you use an own function module (named in the Identification field) you must set the radio buttons to Processing with ALE service AND Processing by function module. The little button behind the identification field will show some details.
At least the detail fields (on tab IDoc) Object type, Start event and End event must be filled.
Default values for these are: IDOCAPPL (=Object type), INPUTERROROCCURRED (=Start event) and ERRORPROCESSCOMPLETD (=End event).
Of course within ALE you can define different types of process codes (what you like most for your specific handling).
Hope this helps you a bit on your way.
Regards,
Rob.

EDI Error in intercompany vendor invoice for Argentina

Hello.
While issuing and RD04 message for an inter-company customer in Argentina I received error 8A551: Format of reference document number is invalid., as in the attached file; the RD04 message is sent OK but the iDoc fails in 51 status.
What is the segment/field where reference number is expected? In analysis mode in we05 the segment indicated, E1EDS01 010 Segment 000088 has no field to enter any reference...
One FI consultant mentioned that this check-up is due to FI document determined during iDoc processing: RE checks the reference number format and we should change it, is there a way to do that through configuration?
I would like to keep this process as much "automated" as possible, for instance it would be better to have the vendor invoice created but parked pending the proper reference number.
All inputs are welcome, thank you in advance.

Thank you Patra, your suggestion can be implemented and I'm pursuing this path.
This may take up to 1 week to become available in the productive environment so meanwhile I'm also looking to an alternate way to "fix" that. One feasible method suggested by an FI consultant is to change the FI invoice type determined by the system, form RE to a different one.
Any idea of how can I do that?
Thank you.

Intercompany EDI processing

Hi,
Dear all in my inter company I assigned out put type RD04 and partner profile is maintain for both outbound and inbound processing when I save then it process properly and give IDOC number
But when try to check status with WE02 it shows error as
A company code cannot be determined for LI 0000050100
Message no. FD006
Diagnosis
The system cannot determine the relevant company code since the allocation of the data transferred in the invoice is missing in Financial Accounting customizing.
The company code can be determined outside of the system and be put into the intermediate document (for example, from the EDI subsystem). Then the company code must be put into the E1EDK14 segment and ORGID field and the value "011" used as the qualifier.
Procedure
Determine the company code for LI 0000050100 in Financial Accounting customizing.
Also I had maintained copany code data where i asigned partner type LI >> VENDOR CODE >> comapny name >> CoCode
But still facing error
Where as when read help on this it state that if you determining data from outside system from E1EDK14 & value 011 and also if you maintained in SD intercompany billing >> Automatic Posting To Vendor Account (SAP-EDI)
THEN YOU NEED NOT TO MAINTAIN IN FI
When I removed from SD then out put is not excepting in invoice give error maintain partner profile for EDI
What is missing out ???
Kapil

Hi,
Here I found that support package for SAP_APPL should be SAPKH60016
Where as in my system it is
SAP_APPL - 600 - 0007 - SAPKH60007 - Logistics and Accounting
If my basis apply correction note will it become up to 16 ?????????????
Kapil

Tax conversion during Intercompany EDI (RD04 output)

We have a situation where there is an intercompany billing from company A to B - both of them are in different countries and hence follow different tax codes.   The RD04 output posts the AP document in company code B with a different tax code.    We have checked OBCD, and this does not carry any relevent config.    What else governs this conversion ?
Many thanks,
Sanker

Hi E_Hinojos and all,
I went to CUNI again and under ALE/EDI, the field was already populated with EA. The solution was that I just need to check the "Primary" box under that field and the error message went away.
Now, I'm getting a new error message after simulating the IDOC again in WE19:
IDoc number            0000000000198023
Direction              2     Inbound
Status                 51    Application document not posted
G/L account 191100 requires a valid tax code
Message no. FS214
Diagnosis
The master record of account 191100 requires you to enter a valid tax code in each item for this account in company code 0001.
System Response
Error message
Procedure
Enter a valid tax code.
I've already maintain transaction OBCD with input tax codes but I'm not sure whether I did it correctly. I'd like to know how the system would know which tax code to take or choose from OBCD table? The GL 191100 under transaction FS00 allows input tax codes only.
Any suggestion would be appreciated.
Thanks.
Edited by: Steven Khoo on Feb 18, 2011 4:16 PM
Edited by: Steven Khoo on Feb 18, 2011 5:17 PM
Edited by: Steven Khoo on Feb 19, 2011 12:45 AM

EDI Error : "Number assignment for ML document is incorrect"

Hi All,
We are getting the below error in EDI invoice generation.
"Number assignment for ML document is incorrect".
We have checked the number range for Material Ledgers. And the status is fine.
We are using EDI for Inbound invoice creation.
Can any body please guide us to solve this issue?
Regards
RS

Hi Srikanth,
The document types are assigned to the Parnter. But how will it be related to the Material Ledger.
We are getting the error while number assignment for Material Ledger Document.
Did we miss any settings are missing related to Material Ledger?
Regards
RS

EDI Error : Condition EDI1 is not allowed as item condition

Hi EDI Gurus,
Right now I am getting the error while creating a Sales order through IDoc.
"Condition EDI1 is not allowed as item condition"
Clarify a few things to me:
1. Where to pass the Customer Expected Price on the IDoc.
2. How to maintain pricing Condition EDI1. (If it is necessary for processing of sales order)
Please clarify these two things.
Thanks,
Matt

I ran V/O8 transaction. There were a bunch of procedures listed in it.
I was not sure which procedure I should look for EDI1 pricing condition.
I checked RVAA01 (Standard) - there are two conditions EDI1 and EDI2.
I am not sure what I should do. Whether they are already configured or not I am not sure.
If they are already configured, why is it giving error in EDI process.
MxG,
Please enlighten me.
Thanks,
Matt

Intercompany EDI

Automatic posting to vendor account (SAP-EDI),
Scenario: We are able to post the Intercompany IDOC.
Company Code 1 sells to Company code 2.
Sale order is created in Company code 1 , Delivery is done and Intercompany Billing doc is generated and IDOC is getting created Successfully.
Requirement:
Sale order line item Account Assignment has Profit Segment - Subproduct line and Sales District ( Characteristic field of COPA).
User wants the Same Subproduct line and Sales District at Sale order of Comapny code 1 in Vendor Invoice of Company Code 2 ( after IDOC creation).
ie., Transfer of Profit Segment info from Customer invoice into the Vendor invoice.
We have Checked with User Exits- EXIT_SAPLIEDI_002 and EXIT_SAPLIEDI_001 from Enhancement project FEDI0001.
Function Module : IDOC_INPUT_INVOIC_FI.
We did not find the solution
Can you provide your inputs.
Thanks

Hi Gurus,
Any inputs Pls.
Thanks

Invoice EDI error : EDI: Partner profile inbound not available

Hi EDI experts ,
We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound). We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
Logical system ( BD54)
ECC system - EDACLNT112,
PI systems u2013 IDACLNT210
Third party u2013 LSMINCOM
Port ( WE21)
IDACLNT510 : For PI with RFC destination IDACLNT510
Partner ( WE20)
LSMINCOM : (Partn.Type LS)
Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
Here PO Creation is working fine . IDoC of PO outbound message have below details :
Recipient information:
Port :     IDACLNT510 (Logical system & Port created in WE21 )
Partner Number : LSMINCOM   ( Logical system and Partner created in WE20)
Partn.Type : LS
Function : LS
Sender information:
Port : SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
Partn.Type : LS
Partner Role :Blank
Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
EDI: Partner profile inbound not availableMessage no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/LSMINCOM/LS//INVOIC///X/
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
Procedure
Please check the inbound partner profiles.
Execute function
I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
Thanks
NAP

Narendra,
Please advice what was the solution.

EDI error

Hi Guru's
We setup a trading partner to send messages using AS2.We are getting the error for incoming payload. we have verified the payload with our ecs file using the data analyzer in the B2B document editor. But the same payload gives error message in the b2b log and does not get processed.
B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
     at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
     at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:310)
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2387)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1263)
     at oracle.tip.adapter.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:161)
     at oracle.tip.transport.basic.HTTPReceiver.sendRequest(HTTPReceiver.java:431)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
     at sun.rmi.transport.Transport$1.run(Transport.java:148)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
     at java.lang.Thread.run(Thread.java:534)
Please help us in resolving the issue. The trading partner is using Gentran as B2B server
Regards
Sahil

GOOD NEWS -
There is setting in Oracle Integration B2B Engine for Preprocessing.
The issue with carriage return in the payload received from the Trading Partner - EDI 850 has new line charaters and fails to recognise the Document Protocol Identification.
We had a support case opened on this and following is the recommendation -
Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
oracle.tip.adapter.b2b.edi.enablePreprocess = true
Make sure there are no spaces after this setting.
This was done and the issue was resolved. Following is the additional DEBUG log that we noticed once this setting was turned on.
2007.06.06 at 11:55:24:466: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2007.06.06 at 11:55:24:467: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor enter
2007.06.06 at 11:55:24:468: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor edi = X12
2007.06.06 at 11:55:24:873: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument preprocess result =
Sharath

Intercompany EDI error

Similar Messages

Maybe you are looking for