EDI 824 mapping

Dear SAP Friends,
I am creating the specifications for EDI 824 Application Advice - Integrated Payables against our EDI 820 flat file send to bank for making payments through Checks, ACH and Wires.
Against our EDI 820 flat file bank will send us back EDI 824 flat file for the rejected payments.
I have to create a mapping method of EDI 824, and send to ABAPer to create a program for it. So that after uploading it in SAP it will make the readable file about what payments were rejected.
Does anyone have this kind of mapping document for EDI 824 format.
Thanks & Regards,
Paul

Hi,
Please check this links perhaps they may help.
http://www.erpgenie.com/sap/sapedi/templates/TXTRAW%20824%20map.xls
http://www.cn.ca/PDF/edi_824_implementation_guide.pdf
Regards,
Ferry Lianto

Similar Messages

EDI 824 Specifications

Dear SAP Friends,
I am creating the specifications for EDI 824 Application Advice - Integrated Payables against our EDI 820 flat file send to bank for making payments through Checks, ACH and Wires.
Against our EDI 820 flat file bank will send us back EDI 824 flat file for the rejected payments.
I have to create a mapping method of EDI 824, and send to ABAPer to create a program for it. So that after uploading it in SAP it will make the readable file about what payments were rejected.
Does anyone have this kind of mapping document for EDI 824 format.
Thanks & Regards,
Paul

Hi Paul,
Didn't get enough info on it, but I think these two links will somehow help you:
http://www.ediinformation.com/edi/edi.php
http://www.loweslink.com/llmain/pubdocuments/824FAQ.pdf
Reward if helpful. *
Regards,
Subhasha Ranjan

EDI 824

Hi,
Can anyone send me the flow or steps for EDI 824 transaction document....
Thanks,
Priya

Mirza,
Can you tell me how you were able to configure check management and then also create EDI 820 and 831 files? I can get one or the other, but not both using classic payment medium programs RFFOUS_C and RFFOEDI1.
We want to execute check issuance for payments but transmit via EDI to our bank for check printing and distribution.
Thanks

Biztalk EDI 856 Mapping H1 Segment

Hi,
I'm new to EDI 856 mapping in Biztalk. I have to map xml schema to EDI 856 XSD and generate a EDI file through biztalk.
I've 3 datasets (repeating nodes) in internal schema (shipment level, order level and item level) I have to map this data to EDI 856 in Biztalk mapping. But the complexity is i have to map all the data's with-in HL loop. I have to repeat HL loop thrice
for shipment level , order level , and item level and each time i should map data to different segments. (ex: i should have LIN segment only at item level).
My output should be like
<HL> --SHIPMENT LEVEL
<TD1></TD1>
<TD3></TD3>
<REF></REF>
<FOB></FOB>
<HL> -- ORDER LEVEL
<TD1></TD1>
<REF></REF>
<N1></N1>
<HL> --ITEM LEVEL
<LIN></LIN>
<SN1></SN1>
<TD></TD>
The problem i face is since i loop HL segment the N1 which should be present only at order level gets repeated at shipment and item level too. Please help me or suggest any study material , its urgent.
Thanks in advance..

Hi,
I can anyone help me to map a flat XSD to a structured XSD in biztalk mapping.
Incoming Schema
Record
<Shipmentdata>
<Shipmentdata1>
<Shipmentdata2>
<Orderdata>
<Orderdata1>
<Orderdata2>
<ItemData>
<ItemData1>
<ItemData2>
OutputSchema
<shipmentData>
<OrderData>
<ItemData>
My input schema is a flat one which i take from DB (ex: if there is 15 items in one shipment and 3 orders the xml will repeat 15 times with repeating data in shipment node and order node). I should convert it into a Structured XML with 3 level of hierarchy.
Please help with Biztalk mapper example. Thanks in advance.

EDI Message Mapping Names

Hi All,
Can I please have the EDI message mapping names for the following:
1)Tradacoms versions 8 and 9
Inbound:Source message type ORDHDR and the target is IDOC structure ORDERS05(Sales Order)
outbound: Source message Invoic02 Idoc and the target message type INVFIL
2)EDIFACT D96A:
Outbound:Source message Invoic02 Idoc and the target message type INVOIC
3)ENACOM:
Outbound: For Source message Invoic02 Idoc and the target message type INVOIC
Your help is much appreciated.
Cheers,
Smith

Hi,
DO u have BIC installed on ur PC. if u have then u could find out the mapping name for the BIC itself.
Mapping program name for example:
See_E2X_ORDERS_D9A is the mapping name for ORDERS message type.
Chirag

Implementing EDI 824 for 855

Hi,
I want to post an EDI 824(error IDOC) for 855 which is a PO acknowledgement. Now I have all validations in FM "IDOC_INPUT_ORDRSP" processing of 855 IDOC.
Now What all steps do i consider to convert the error 855 IDOC into 824 IDOC.
Thanks
Balu

Bala,
You need a custom IDOC,since SAP does not have any corresponding IDOC for 824 (App.Ack).
You can control the 824 by the output type control.
Hope this helps you.
Thank you.
Regards,
karun.M

EDI file Mapping.. problem with UNT segment..!!

Hi all,
Anyone who worked on EDI files, pls help me..
Doing Idoc to EDI scenario..
I done for all the mapping for all the fields except for the UNT segment and field D_0074
Here i need to provide no of segments in the EDI file...
like
*UNBUNOA:393777:ZZ93139:ZZ080108:09080+++1'
UNH0000016334368DESADV:D:01B:UN:EAN007'
BGM3510094147783+9'
DTM+137:200801080934:203'
DTM+11:200801080934:203'
DTM+17:200801100000:203'
ALI++168165'
RFF+ON:R-08007E'
DTM+171:20080107:102'
NADSU377996::92'
NADST9418GR::92'
CPS1+5'
PAC9+09::9'
MEAPDAAA+KGM:6306.628'
MEACTNPP+NAR:9'
CPS21+3'
PAC109::9F:CHEP'
MEAPDAAA+KGM:256.828'
PCI+33E'
GINAW393100471000832922'
LIN1+19310047208023:SRV'
QTY+12:44'
DTM+36:20090505:102'
CNT+2:2'
UNT240000016334368'
If you observe the above file which is my resultant file.. I need to count all the segments above UNT and pass the value( here total segments are 24) to D_0074 field .
Is it any way we can count all the segments.. and pass the value??
Kindly suggest me ..
waiting for your replys..
Regards
Seema.

Problem here is ..
They have created only SCv Seebutger_EDI_Adpater
but they haven't created for Seebutger_GENERIC_EDI ..
all those mappings will be under Seebutger_GENERIC_EDI .. which they haven;t installed..
thats the problem..
If any one has that UDF .. kindly let me know..
-Seema.

IDOC DELVRY05 TO EDI 856 - Mapping problem

Hi all,
i'm currently working on a outbound mapping with the delivery idoc (DELVRY05) and the EDI 856 (Advance Shipping Notice Definition)
The problem is that i can't map the items for every pack in the structure because the ocurrency doesn't match.
The EDI 856 has a segment called G_SHL (ocurrence 0.200000), that i replicated 4 times for shipping, order, pack and item data
And this segment has a subsegment called G_SHL/S_HL (ocurrence 0.1)
RESULT DESIRED GIVEN BY THE CLIENT: (1 pack/1item)
3     HL1*S~                        ======> S: shipping, 1 hierarchy)
4     TD1CTN251***G223.997*LB~
5     TD5*2ABFSM*CC~
6     REFBM003030987~
7     REFCN086044619~
8     DTM01120080128*180610~
9     DTM06720080204~
10     FOB*PP~
11     N1SFStiefel Labs~
12     N4DULUTHGA*30096~
13     HL21*O~ ======> O: order, 2 hierarchy, 1 was the previous hierarchy)
14     PRF*4064561~
15     HL32*P~ ======> P : Pack, 3 hierarchy, 2 was the previous hierarchy
16     MANGM00000734620052976193~
17     HL43*I~ ======> I: Item , 4 hierchay, 3 was the previous hierarchy
31     LIN*UP073462150651LT45X5147ND00145150605~
32     SN1*12EA~
33     DTM03620090930~
34     HL52*P~ ======> P : Pack, 5 hierarchy, 2 was the previous hierarchy
35     MANGM00000734620052975189~
36     HL65*I~ ======> I: Item , 6 hierchay, 5 was the previous hierarchy
37     LIN*UP073462150651LT45X5147ND00145150605~
38     SN1*12EA~
39     DTM03620090930~
40     HL72*P~ ======> P : Pack,7 hierarchy, 2 was the previous hierarchy
41     MANGM00000734620052975196~
42     HL87*I~ ======> I: Item , 8 hierarchay, 7 was the previous hierarchy
43     LIN*UP073462150651LT45X5147ND00145150605~
44     SN1*12EA~
45     DTM03620090930~
46     CTT*8~
47     SE479220014~
As u see, all packs belong to "2 hierarchy" (order), and items to their correposding pack
(has a comment, the "hierarchy number" is always given by a counter so u won't find the exact number again)
so, the client wants us to create an structure that is like this..
1º Pack
1º item
2º item
2º Pack
1º item
2º item
(the example has only one item, but they say that is going to be with many items)
- The problem is that the structure data of the Idoc doesnt match EDI 856 structure
E1EDL37 (0.99999) -
Pack data -
G_SHL (0.200000)
E1EDL37/E1EDL44 (0.99999) -
Item data -
G_SHL/HL (0.1) <====
i was doing different G_SHL for pack and items but that leaves me with a wrong structure, and with all the hierarchy data wrong for items (since the mapping can't see which item belong to his pack)
1º Pack
2º Pack
3º Pack
1º Item
2º Item
3º Item
- How can i map the structure Pack/item if in the idoc got too many item positions for only one EDI corresponding segment??
Thanks in advance!

Alains,
We have the same tear, pack and item problem with one of our customer in one of my project. To acheive this result with the standard schema is not possible because this is a custom one.
So I would suggest to change the schema in BIC like the occurrence and within the third G_SHL you should have S_HL and within this you should have a S_HL so that for every pack you will have multipe items.
The bottom line is to have the schema as required by your mapping. Once you change the schema deploy the maps in J2EE and use them else it will throw an error in RWB.
Regards,
---Satish

IDOC to EDI Seeburger Mapping Issue

Hi,
I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
As per my little knowledge i can understand that i need two step mapping:
1) IDOC XML to EDI XML
2) EDI XML to EDI
Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
Also i dont know how i can map the 2nd mapping.
when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
msg_PAYEXT_UN_D96A.xml
msg_XML_PAYEXT_UN_D96A.xml
XML_PAYEXT_UN_D96A.xsd
Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
Please experts reply soon as it is delaying my project
Regards,
Shradha

Shradha,
You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
You can have a look whether PAYEXT is there and would be useful
To start with
1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
2. You should also liase with your business partners to prepare an business rules and other conditions.
3.Also decide whether you are going to deliver it via AS2 communication or via VAN
4. Accordingly you need to configure the seeburger adapters.
5.The mappings provided to you are from XML to EDI and EDI to XML which is a second stage automatically done by seeburger once you specify the module steps in the comms channel.
I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
Regards
Krish

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

EDI 850 Mapping Clarification

Hello,
I have a requirement to Post EDI 850 Document to create Sales Orders in SAP. Currently, we are working on finalizing the mapping Document with the all the required fields that will be sent by the Customer.
Now, the query that the EDI Contact has is whether the data will be mapped to the E2EDKXX segments or E1EDKxx segments. Could some one provide some clarification regarding this? Even I would like to understand whether the EDI Person will map the data into E2 Segments and then when the IDoc reaches SAP, the data will be mapped in to E1 Segments. How does it work?
Please provide clarifications.
Regards,
Phani Prasad

>>Now, the query that the EDI Contact has is whether the data will be mapped to the E2EDKXX segments or E1EDKxx segments.
As I have seen, for Orders, the data should be in the E1EDKxx segment. However, this is a question for your SAP fucntional team to confirm what data are they expecting from third party.
>>EDI Person will map the data into E2 Segments and then when the IDoc reaches SAP, the data will be mapped in to E1 Segments.
This doesn't make much sense as the Order Idoc is standard one and moving data within segments shouldn't be required.
If you can't get clarifications from fucntionals, start with E1EDKxx. Also, check we60, we30 as mentioned to see what data should those segment have.
Regards,
Prateek Raj Srivastava

EDI IDOC mapping design

Hi all,
I was supposed to program a report to generate IDOCs. The EDI file format was given.
The segments in the IDOCs should be in the sequence of A, B, C. How can I map them into the sequence of B, C, A?
Is it mapped by the external software?
Thanks

IDoc-to-EDI mapping is usually handled by external software such as Sterling Commerce Gentran or GXS Application Integrator. Check with your company EDI folks they should churn this work in no time for you.

EDI 820 Mapping

Hi Guys,
Customer send send sall the payments to Locbox. The bank send EDI 820 file
Can you please send a sample mapping document for EDI 820 format to PEXR2002 idoc to Lockbox. My email [email protected]

Hi,
http://www.sapfans.com/forums/viewtopic.php?p=497781&sid=a3d0079130fe3ae
http://www.mail-archive.com/[email protected]/msg06108.html//www.mail-archive.com/[email protected]/msg06108.html
http://www.cn.ca/PDF/EDI_820_Guide.pdf
http://www.pfizer.com/business/edispecs/ap820ach.pdf
Hope this helps.
Thanks
NT

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

EDI - IDOC mapping question

Dear Experts,
For transformations between EDI and basic IDOC types, are there any off-the shelf (ready to use) options? If yes what are they? If not, what is the easiest way of mapping in between these structures?
Our setup involves Seeburger's AS2 adapter.
Thanks

Hi Aamir,
Thank you for your response.
We are working in an environment where we do not have any control over the setup. So I have a few follow up questions, answers to which would help me immensely.
1. I saw that there are a"few" mappings available for which both the EDI and IDOC versions differ from what we need. So, is there anyway to get an actual listing of all supplied mappings?
2. In case you have worked for a similar scenario, is it possible for you to share a sample mapping spreadsheet ?
Thank you,
N

EDI 824 mapping

Similar Messages

Maybe you are looking for