Inbound EDI LIS Invoice

Hello - We currently bring in Basic type invoic02, message type invoic and FM DOC_INPUT_INVOIC_MM to bring in vendor invoices into LIS/AP. We have Config setting of 4 (MRMKORR) for tolerance processing of the invoice - but this is not happening - all invoices, regardless of the tolerance - are being blocked...any ideas?

Hi,
thse are the avaialbe function modules for invoice.
IDOC_INPUT_INVOIC_FI
IDOC_INPUT_INVOIC_MM
IDOC_INPUT_INVOIC_MRM
Regards,
Nagaraj

Similar Messages

How to configure inbound EDI invoice

Hi all,
Can any one provide me the steps to configure inbound edi invoice.
Regards,
Marella.

Hi Arif, yes I did read that one.
after reading that I got those doubts.
In general, please help me to have a clear understanding in the following points.
We have 4.6c.
Please see my quries below and help me.
SAP Tax codes
Can an inbound MM invoice contain items belonging to different POs?
Can the tax codes be different for different items in the same invoice?
How to get tax codes for invoice items? Do we take these from the corresponding item in the PO? or from material master or from vendor master or some where else?
What will be the tax code at the invoice header level?
Regards,
Marella.

EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

Hi,
We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification. When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)? because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received.
The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation. The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
We havd SAP version ECC 6.0
I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this? and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

Hi ,
You can use the program RBDMANI2 which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
We had the same scenario and we have scheduled this program as a daily job at night .
Regards,
Hari.

Processing options for EDI vendor Invoices

I'm trying to get a better understanding of what my options are for processing EDI vendor invoices and would appreciate some help. I'm using message type INVOIC02 with process code INVL and in configuration I've set the processing option in table T076S to 4 (tolerence corresponding to online processing). When an invoice fails either the vendor specific tolerance check or the payment blocking checks the invoice gets parked with error status 3. This is behaving as I would expect. The issue I have is the price on the parked invoice is the price from the PO and not the price from the EDI segment. Is there anyway to change this? This makes it difficult to analyze the cause of the error without going back to the Idoc segments. I've tried playing with the other processing options but they also enter the PO price in the parked invoice. If it's not possible to change this are there any tricks that i'm missing that can help the users analyze the cause of the errors without going back into the idoc?
thanks,

If anyone has any expierence with this, I would appreciate any advice you may have.
thanks,

Inbound EDI 852

Can anyone of you please tell me about the inbound edi 852?
What would the IDoc file look like? What are the mandatory fields and what values should go in there etc...
Also , what transaction or tables are being accessed in SAP to post this data.
Your help is much appreciated.

Hi Sara,
In the E1ADRM1 segment, what values should we get?
The values should be 'WE' for customer and 'LF' for supplier.
Also where r the checks performed ? VOE2 , VOE4 ?
The data check is performed in FM IDOC_INPUT_PROACT.
Do you have any sample Idoc file for inbound 852?
Sorry, I don't have any IDoc sample. But you can use WE19 (Test tool) to simulate the IDoc and try to process using standard FM IDOC_INPUT_PROACT.
Again, hope this will help to start with.
Regards,
Ferry Lianto

Inbound EDI multiple customers using 1 partner profile

I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
Thanks, Mart

Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
Cheers, Paul.

EDI vendor invoice and account invoice

can u please explain me
1.EDI Vendor Invoice
2.Account Invoice

EDI Vendor invoice is nothing but the LIV or FB60 invoice posted using EDI that is IDocs...
and account invoice u can say FB60 invoices, that is they are posted only in accounting. they do not have a purchase order or a gr..
Regards
Anantha

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

Tax Jurisdiction code for EDI Incoming invoice

Hi,
We have implemented EDI incoming invoice using INVOIC02. The process code is INVL.The invoice is to be posted against a Purchase Order line item. It is noticed that the EDI invoice is not getting the Tax Jurisdiction code from the Purchase Order line . Instead the Tax Juridiction code is copied from the company code. However when we post the invoice manually using MIRO , then the Tax Juridiction code is copied from the Purchase Order. We understand that the system should take the Tax Jurisdiction code from the Purchase Order even for EDI invoices. Is it compulsory that we have to use the user exit EXIT_SAPLMRMH_014 in order to populate the Tax Jurisdiction code field TXJCD from the Purchase Order line? or is there any config required to enable the transfer of Tax Juridication code from the Purchase Order? In transaction OBCE there is a config to transfer the tax jurisdiction code supplied by the external vendor. If we do not check that box , then system is supposed to get the tax jurisdiction code from the Purchase Order.
Thanks
Sukumar

The issue is resolved through OSS Note 506343. In the standard R/3 system, the tax jurisdiction code can't be written to invoice via EDI and only the Ship To Plant's Tax Jurisdiction Code is written to the invoice.
Regards
Sukumar

Unable to process inbound EDI docs from TP-multiple Host ID's,1 transaction

Issue:
Unable to process inbound EDI documents from trading partners
(Same doctype and revision, but diff receiver ID’s for host)
Host: ISA ID’s are HOSTA, HOSTB
Transaction: X12, 210, 5010
Trading Partner A: sends EDI document with these values
Interchange Sender ID: TPA
Application Sender's Code: TPA
Interchange Receiver ID: HOSTA
Application Receiver's Code: HOSTA
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner A : Process_210_Initiator It has
Interchange Sender ID as TPA
Interchange Receiver ID as TPA
Application Sender's Code: TPA
Application Receiver's Code: TPA
This creates a Process_210_Responder for HOST
It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code: HOSTA
Application Receiver's Code: HOSTA
Validated Agreement and deployed, Result is success and everything works fine until here
Note: B2B validates taking everything from Process_210_Initiator except the Interchange Receiver ID that it gets from the Process_210_Responder
New Trading Partner B also sends us an X12, 210, 5010 but he uses Receiver ID as HOSTB
Trading Partner B: sends EDI document with these values
Interchange Sender ID: TPB
Application Sender's Code: TPB
Interchange Receiver ID : HOSTB
Application Receiver's Code: HOSTB
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner B : Process_210_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code: TPB
Application Receiver's Code: TPB
This doesn’t create a new Process_210_Responder for HOST It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code : HOSTA
Application Receiver's Code : HOSTA
Validated Agreement and deployed, Result the document fails with error
Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid
Upon looking at the log file it fails, as the Interchange Receiver ID in data is HOSTB where as in Process_210_Responder it is setup as HOSTA
Work Around that we tried, but could not succeed
Create a new business action called Process_210_HOSTB, created a new Document Protocol Revision X12_5010_HOSTB,Created a doc type 210 version 5010 under that
Used this new Business action for Trading Partner B so the new setups look like this
Business action : Process_210_HOSTB
Operational Capability for Trading Partner B : Process_210_HOSTB_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code : TPB
Application Receiver's Code : TPB
This creates a new Process_210_HOSTB_Responder for HOST It has
Interchange Sender ID as HOSTB
Interchange Receiver ID as HOSTB
Application Sender's Code : HOSTB
Application Receiver's Code : HOSTB
Validated Agreement, but could not deploy as I was getting AIP-11016 SQL error , may be integrity constraint issue
Note: I was able to deploy this agreement if I change the Document Type from 210 to something else like 210_new, but since the document is EDI I can’t have the Document Type as anything except 210

Ramesh,
Sorry for the delay , but this was the first thing I tried and it didn't work, I tried again just to be sure, it didn't work I am getting this error
When group Receiver ID didn't match
"Validation of Group parameters failed. Please verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in B2B"
In addition, when Interchange Receiver ID did not match
"Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid"
Here is the log file extract
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@12d8ecd
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1fa5e5e
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@497062
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 60DD87849FFE4147BFCEB66842A33298-26-1-4
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsOptFileBlob
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsFileBlob
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber sName = Interchange, controlNumber = 210011217
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber return = true
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {156BEDFC-931E-4923-840D-3AC0BAB670F2} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1b5c22f
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupReceiverID, val = [STMSLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupSenderID, val = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [GroupReceiverID] value = [STMSLCY] param = [SLCY] Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {6EE88EFC-B084-4FA8-8EE8-8C7BD397E9F1} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:073: Thread-10: B2B - (DEBUG) iAudit report :
Error Brief :
5082: XEngine error - Guideline look-up failed.

Inbound EDI Issue

Hi Experts,
We are using SAP PI 7.0 with AS2 System (Seeburger) in Quality System to exchange EDI Documents with our Customers and 4PL partners. We are able send EDI Documents (Outbound) to our partners successfully but facing issues related to Inbound EDI Documents (Incoming) i.e., when customers/4PL Partners are trying to send the EDI Documents it is not reaching to our Test System.
We thought it could be Web Dispatcher issue and restarted it but that didn’t solve the issue. In XI system no changes have been made in IR and ID. Below is the error message our partner is getting while sending the EDI Documents.
Response: "400 Connection Failed (VLProxy.java.net.ConnectException: Connection timed out: connect)"
Result "Error""400 Connection Failed (VLProxy.java.net.ConnectException: Connection timed out:connect)" Source file not deleted
Your Help is highly appreciated.
Regards
Faisal.

Hello Abdul,
I have to agree with Harish regarding the Connection Timeouts. To verify if the incoming AS2 requests reach the AS2-Server or already have some issues on network-level, I would recommend to take a look at the AS2-Trace (and set the trace-level to debug)
Attached a quick description to setup the Logging...
Easy Log Configuration - How To Guide for Seeburger Adapters
Some question to consider would also be:
Did it work before and suddenly stopped working or are you just setting up this connection initially ?
Are other partners able to send to your system ?
Kind Regards
Stefan

Non PO Charges through EDI Incoming Invoice

Hi
I would be very thankful if somebody can answers these questions. I am designing EDI based invoice LIV.
1) Is it possible to post some charges in invoice which are without PO reference.Is it possible to post these kind of charges with EDI message INVOIC01 or we have to post through FI posting.? or we need to use INVOIC02
2) If possible through EDI in which segment of IDOC we will enter these charges with amt I am not able to find out the segment I tried in EIEDP01 but failed
3)Also is it possible to post credit memo also with EDI?
Thanks
[email protected]

try out with segment E1EDP05.

Mass delete the parked EDI LIV invoices

Hey Guys:
I want to Mass delete the parked EDI LIV invoices. I have implemented note <b>971193 - FIPP: Mass deletion of parked documents</b> which is pulling data from FBV0...which is not the place where parked EDI LIV invoices are in.
I have found a table RBKP which is having my parked LIV invoices document numbers.
Can some of you give me a solution from where exactly we can mass delete these parked LIV invoices which have not touched the F1 yet.
Thanks
Gitaa

Have you tried Mir4

Issue with inbound EDI idocs

Hi
we are receiving inbound EDI idocs throgh third party. Third party received EDI file having 5000 transactions .
It was transalated same number of idocs text document and posted in SAP. But after 4 hours same file processed in SAP.
Third party saying they sent only once .
Is there any way in SAP file placed two times or one time .
Any table stores this information . we are using TRFC port . I know EDIF12 table but it was not used here.
Any clue on this.
Thanks

HI
ANY Clue on this issue

EDI incoming invoice error M8 755 Enter a tax code in item...

All,
Can anyone tell me where I should look to resolve this issue? I'm trying to post an EDI incoming invoice for a PO. The PO has an tax code on the line item being invoiced.
Thanks
Sandra

Let me get into a little more detail. We have EDI incoming invoices working properly in our production environment. It is unlikely our mapping or our customization is incorrect. It is possible that something has been changed with customization but I have already looked there and did not see anything of concern.
I'm doing testing in our test environment using WE19, and I'm getting this error message although the idoc I create is similar to examples in production and the PO is also similar to what is in production.
I was hoping that someone had experienced a similar issue and would be able to point me in a direction that I have not already looked.
Regards,
Sandra

Inbound EDI LIS Invoice

Similar Messages

Maybe you are looking for