Inbound EDI 820

Hi Guys,
What is the relevant SAP tables that holds Inbound EDI 820 (PEXR2002) in SAP. Your help is highly appreciated....

[Does this posting help?|IDOCS;

Similar Messages

EDI 820 mapping into SAP

Hi
Can any one give me the step-by-step approach in mapping the EDI 820 (both Inbound steps and Outbound steps) into SAP standard functionality ?
Thanks
Maruthi Ram

Hello Maruthi
[http://edi.stylusstudio.com/msg013304.htm]
Hi Jeff-
It is a message type PAYEXT (REMADV), the i-Docs are PEXR2001 and
PEXR2002.
Best Regards,
Mike Kelly
----- Original Message -----
From: "Jeff Garwick" < To: < < < Sent: Wednesday, 16 February, 2005 05:04 PM
Subject: [EDI-L] SAP transaction set / EDI 820
What is the SAP transaction set that supports an inbound EDI 820
payment/remittance advice?
Thank you,
Jeff Garwick
Bourns, Inc.
Please use this input as starter for your own detailed search and let us know if you have found an appropriate solution.
Regards
Uwe

FDM_AUTO_CREATE for EDI 820 Deposits

Hi Experts
We are using the EDi 820 from the customer directly for the Incoming payments and credit memo (Deductions taken by them).
The transactions failed in the EDI 820 inbound process will be run through the post processing in FB01 and F-28.
Still we are going to have the transactions from EDI 820 which can not be matched to the corresponding invoice number because the customer provides their own credit memo reference num.
After few days can we take above finally failed transactions and create them as Dispute cases in FDM_AUTO_CREATE instead of the manually via F-28 or FB01.
FDM_AUTO_CREATE runs for the Automatic incoming payments and Open items options.
Which method or option is to be selected in it and what are the input selections to be used for EDI 820 failed transactions.
Please advise accordingly.
Thanks
Regards,
Meenakshi.N

Hi Mark,
Thank you very much for your response.
However as I mentioned, some disputes were created for this customer in the same batch job. So I dont think the customer could be locked for any reason.
If I try to run FDM_AUTO_CREATE in the foreground in the test mode for this particular document, it does propose to create a dispute case for this line item.
So not sure why this document could have missed in the batch job.
Thanks
Krishna

EDI 820 EDI to XML conversion error

Hi Experts,
We have configure EDI 820 Inbound Scenario in our system. The incoming EDI 820 file is not getting converted in XML from EDI. I try to convert it into XML in BIC Mapping Designer but it is displaying the below error message.
"Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[326]: the found segment
ENT is not in the message description.
DESCRIPTION: InhouseDocReader Error: The Segment
ENT is missing in the message description. Check your file."
Please find below the EDI file.
"ISA*00* *00* *12*123456789 *01*111122233 *140317*1432*U*00401*120000004*0*T*>~GS*PO*123456789*111122233*20140317*14315990*4*X*004010~ST*820*0001~BPR*I*264.9*C*CHK~REF*IA*6400900~REF*CK*7896883~DTM*097*20080811~N1*PE*COMPANY ABC~N3*21 PENN PLAZA*SUITE 909~N4*NEW YORK CITY*NY*10001~
ENT*1~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195112**137.33*137.33~REF*PO*008471856056~DTM*003*20080711~ENT*2~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195040**162.38*162.38~REF*PO*008471852792~DTM*003*20080711~ENT*3~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0194903**104.8*104.8~REF*PO*008471816334~DTM*003*20080711~ENT*4~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195039**137.33*137.33~REF*PO*008471846520~DTM*003*20080712~ENT*5~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0047997934**-224.54*-224.54~REF*RZ*0004891~DTM*003*20080807~ENT*6~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0084791384**-52.4*-52.4~REF*RZ*8471700434~DTM*003*20080807~SE*39*0001~GE*1*4~IEA*1*120000004~"
Can anyone let me know what could be error is?
Regards
Faisal

Dear Abdul,
I copied the file from your posting into a text-file and tried to convert it with my 820 BIC-Mapping.
I just had to make two modifications:
- add some spaces so that the Sender/Receiver fields in the ISA segement were 15 fields long
- remove a "space" before ENT*1, but this space might also just have been there because of how you posted the content into this posting.
After I had made this small changes the file could be translated perfectly fine with the mapping
See_E2X_ANSIX12_820_V4010
So it looks like eitehr your settings are not correct in the channel (e.g. a wrong mapping is used) or the file has been modified manually (with some additional blanks, CRLF, etc...)
Regards
Stefan

Usage of inbound EDI payment advice

Hello experts,
I'm asked to implement an inbound payment advice / remittance advice via EDI using VDA 4907. I dived into the SAP help for this as well as into many discussions in this forum but I'm still unsure about the underlying concept as intended by SAP. My understanding is that the remittance advice closes the gap between a large single incoming payment and potentially many open items, thus clearing the open items and the payment.
Can someone please let me know if this understanding is correct?
How does this two-sided clearing process work?
Thanks in advance and best regards,
Christoph

Hi Abdul,
Currently I am working on EDI 820. I have really no clue how to configure this functionality.
I have done research but I couldn't manage to get enough material on this.
Since you have already worked on this using all your expertise I would appreciate if you could send some require material or info on the same.
Regards,
Victor

Is there a way for EDI 820 (remittance advice) to identify proforma invoice

Hi,
We have certain customers who pay by proforma invoices. These customers send remittances through EDI 820 which we create as payment advice in SAP. When the cash comes in, the payment advice is not being applied since the document number has the proforma invoice and in FI, the proforma invoice is not stored anywhere.
Proforma invoice in our case is a consolidated billing document that is not passed onto FI. Any thoughts to have the payment advice apply when the cash comes in even though the customer pays by proforma?

Hi,
We have certain customers who pay by proforma invoices. These customers send remittances through EDI 820 which we create as payment advice in SAP. When the cash comes in, the payment advice is not being applied since the document number has the proforma invoice and in FI, the proforma invoice is not stored anywhere.
Proforma invoice in our case is a consolidated billing document that is not passed onto FI. Any thoughts to have the payment advice apply when the cash comes in even though the customer pays by proforma?

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

Creation of EDI 820 for outgoing payments in SAP

Hi Experts,
We have a requirement where in we need to create an outgoing payment file in EDI820 with in SAP.
We basically need to create specifications in EDI820 format for the bank to print checks and make wires and EFT payments.
That EDI820 file will be created at the time of Automatic Payment Run(F110).
Right now our client is sending a flat file to external service provider and they are creating EDI820 files and sending to the banks. Going forward the services of this service provider will be decommissioned and an EDI820 file is to be generated in SAP and sent to the bank via SWIFT Net.
Bank has provided us a sample file and file format for EDI820. This file format contains ST, BPR, RMR, REF etc records. There records have different codes and qualifiers.
As far as we have analyzed, there are no standard SAP programs that can generate flat file in the EDI 820 format. Therefore we are heading towards developing a Z program for creating an EDI820 format.
We are facing problem in mapping this file with SAP fields. We need to know how exactly we can map this file in SAP so as to create a program to generate EDI820. If anybody has had a similar requirement (for creating outbound EDI820 in SAP) and can provide us some lead, it will be greatly helpful for us.
Thanks in advance for the help!

Have you worked on this requirement?
Could you please provide step by step instructions to configure and the high level process?

Creation of EDI 820 fromat for outgoing payments in SAP

Hi Experts,
We have a requirement where in we need to create an outgoing payment file in EDI820 with in SAP.
We basically need to create specifications in EDI820 format for the bank to print checks and make wires and EFT payments.
That EDI820 file will be created at the time of Automatic Payment Run(F110).
Right now our client is sending a flat file to external service provider and they are creating EDI820 files and sending to the banks. Going forward the services of this service provider will be decommissioned and an EDI820 file is to be generated in SAP and sent to the bank via SWIFT Net.
Bank has provided us a sample file and file format for EDI820. This file format contains ST, BPR, RMR, REF etc records. There records have different codes and qualifiers.
As far as we have analyzed, there are no standard SAP programs that can generate flat file in the EDI 820 format. Therefore we are heading towards developing a Z program for creating an EDI820 format.
We are facing problem in mapping this file with SAP fields. We need to know how exactly we can map this file in SAP so as to create a program to generate EDI820. If anybody has had a similar requirement (for creating outbound EDI820 in SAP) and can provide us some lead, it will be greatly helpful for us.
Thanks in advance for the help!

The program that sends the flat file should give you all the necessary fields, selection criteria, etc. If the third-party constructs EDI820 from it, then there is enough data in that file for you to add steps to create an 820.
So, I'd start with the existing program, a particular outbound file and a copy of the 820 file created from it (if that can be obtained) and figure out how the intermediary converted the data to the correct format. Piece of cake, right?

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.

Mapping with EDI 820

Hi Friends,
Please help me to find these fields to map from SAP to EDI 820 (Positive pay).
Where can I find these fields in SAP to get populated for the payment run.
Our Company name:
Our Bank Name:
Our Bank Key:
Check Lot number:
Check number:
Many Regards,
Sim

-Company Name Chek field BUTEXT in table T001
-BANKK and BANKA for bank key and name in table BNKA
-STAPL and CHECT for check lot number and check number in table PCE.
Regards,
Bharat

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.

Mapping from PEXR2002 iDoc to EDI 820

We are planning to use XI to map from the payment advice (PEXR2002) iDoc to EDI 820.
We have 2 options: (1) Use XI and an EDI adapter (e.g. Seeburger); or (2) Use XI's own mapping functionality.
If you have done iDoc to EDI mapping with either of the above 2 options, please briefly advise about your experiences and how much efforts it took to develop the mapping.
Thank-you
Bac Quan

Hi Bac,
Although it is possible to create an EDI message in an XI mapping (or XSLT), this is not very nice. The use of an EDI adapter (iWay or SeeBurger) is strongly recommended.
The other way around (rom EDI to XML) is hardly feasiable without an EDI adapter. Although I haven't worked the SeeBurger adapter, it looks quite nice.
Kind regards, Guy Crets

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

Posting Incoming payment through EDI 820

Hello,
I am trying to set up EDI 820. I want to post incoming payments through EDI 820.
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMC
I have been testing using test tool all my idocs are failed. The error which I am getting is - "customer/vendor could not be determined for intermediate document".
Please suggest me how to fix this error. Is this related to FI config settings or ALE setting error.
Thanks & Regards,
Victor

Even i faced the same error while posting the EDI820. Then i corrected the errror by maintaining the segement E1EDKA1
Field name : PARVW , Value: AG
Field name : Name1, Value : Vendor number at customer location
And also the segment E1EDKA1
Field name : PARVW , Value: BE
Field name : Name1, Value : Vendor number at customer location
this should help you
IF E1EDPA1-PARTN IS INITIAL.
        IF E1EDPA1-NAME1 IS INITIAL.
*-- keine Daten uebermittelt => Fehler
          PERFORM STATUSFELDER_FUELLEN
                  USING FEHLER_BEI_UEBERGABE
                        MSG_WARNING
                        MESSAGE_ID
                        MUSS_FELD_FEHLT
                        'NAME1'
                        'E1EDPA1'
                        SY-REPID
                        'E1EDPA1_MOVES'
                        'NAME1'
                        SEGNUM
                        DOCNUM.
        ELSE.
          SCHLUESSEL = E1EDPA1-NAME1.
        ENDIF.
      ELSE.
        SCHLUESSEL = E1EDPA1-PARTN.
      ENDIF.
      IF NOT SCHLUESSEL IS INITIAL.
        PERFORM PARTNER_TABELLE_LESEN
                USING SCHLUESSEL PARTNERNUMMER
                      PARTNERART HILF_BUKRS.
You can also populate E1EDPA1-PARTN instead of NAME1 to find the account.

Inbound EDI 820

Similar Messages

Maybe you are looking for