EDI 821 Idoc mapping

We have EDI 821 from bank for the vendor payment, Can any one help me provideing IDoc Structure for that..or any suggestion? msg type we r planning to use is PEXR2002. My e-mail is ramnivi yahoo
Is there any other message types avilable for this maping please let me know.
Thank you

Dear Satish,
The thing here is the EXIDV field has to be mapped to another values based on a condition. which is different from the previous one. which i did for ZE1EDL37.
the value is getting supressed. there is an if condition whose output has to be given to the destination field. the values are coming till that IF. they r getting supressed there.
the node (header) id getting duplicated but the fields inside it are not getting duplicated.
Message was edited by:
somayajula yashwanth

Similar Messages

EDi to IDOC mapping

HI,
i need to map an EDI to an IDOC. the number of times a particular field occurs in the EDI structure, the same number of times the corresponding group of values has to be created in the IDOC.
i am getting the source node but not the fields inside it.
eg:
G_SHL
---S_HL
D_735 (value = P)
G_SHL
---S_HL
D_735 (value = P)
Output structure :
ZE1EDL37
EXIDV
the root node (ZE1EDL37) is getting created two times (if D_735 occurs 2 times) but the field inside it (EXIDV) is not gettting created the second time.
thanks in advance,
yash.

Dear Satish,
The thing here is the EXIDV field has to be mapped to another values based on a condition. which is different from the previous one. which i did for ZE1EDL37.
the value is getting supressed. there is an if condition whose output has to be given to the destination field. the values are coming till that IF. they r getting supressed there.
the node (header) id getting duplicated but the fields inside it are not getting duplicated.
Message was edited by:
        somayajula yashwanth

EDI to IDOC mapping with MII

Hi,
is it possible to map edi document to IDOC with MII?
Thanks.

Currently there is example available.
In the thread [can MII read edifact|Re: can MII read edifact?; Jeremy mentioned an idea which may be interesting for you. Have a look at the following Wikipedia article about [XML/EDIFACT|http://en.wikipedia.org/wiki/XML/EDIFACT]. Use case 1 proposes to use a converter build a XML file from the original Edifact message. Then you can process that XML with MII.
Maybe this helps.
Michael

820 EDI to IDOC mapping

I am working on converting a inbound EDI 820 document to a SAP IDOC, PEXR2002. If anyone has any info as to where I can obtain a sample layout. Please let me know. Thanks!

Hi All,
If the source is an EDI and not an XML then you need an Adapter third party adapters from Seeburger are Provided for EDI integartions with SAP-XI.
Go to Following Links::
When we are integrating the EDI with XI we need seeburger Adapters
See the below links
/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
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
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
The complete installation manuals can be supplied by the seeburger vendors.
the adapter specific installations you can find in those manuals
Once a Seeburger sender adapter will pick the data from the EDI file's location it will have a seeburger provided map (Name will be addaed in the module of the Sender AS2 adapter)
Ask me if you need more details
Please provide forum points if find use full
regards
Piyush

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

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

PositivePay interface- EDI 828 / EDI 821

Hi Friends,
We are implementing check issued/check paid process. We are using webmethod as middle layer. The format be are sending to the bank is EDI 828 and receiving with EDI 821 format.
Can any one help in finding the IDOC and message available in ECC6 and mapping required?
Suggestions are appreciated and will be rewarded with points.
Thanks in advance.
Regards,
Harish

Hi Auro,
Thanks for the response. If you have , can you please send me the mapping document.
Regards,
Harish,
munigala_in (at) yahoo.com
or
harish.munigala (at) gmail.com

Seeburger EDI to IDoc

Hi,
The actual payload is not getting generated in the EDI to IDoc scenario.
The acknowledgment is getting generated.
What could be the possible error?

Anu,
is your mapping determined automatically or are you explicitly stating the mapping name in your
module configuration?
If you set mappingName to Auto BIC tries determine the correct mapping by looking at the
the UNH segments, e.g. UNH1ORDERS:D:97A:AA'. If your mapping has been labeled
differently in the Mapping Designer, for instance E2X_ORDERS_UN_D97A the system
won't be able to find the mapping and therefore you won't get any payload.
As I suggested before try using the parameter u2018logAttIDu2019 Value u2018ConverterLogu2019 in your
module chain that will most likely tell you what the problem is.
Sven
Edited by: Sven Buttler on Jul 9, 2010 10:26 AM

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

IDoc mapping for VMI

Hello,
We'd like to store the idoc data extracted from EDI 852 inbound transaction in an infocube for DP. SAP Note 154604 suggests that trx <b>/sapapo/map_tser</b> can be used for specifying the infocube.
However, in SCM 4.1, this trx has a field for PA only, not infocube. I was wondering how to pull the data into infocube.
Any suggestions would be appreciated.
Thank you,
Malli

Hello,
     I'm afraid that i can not help you.
      I am witting you because i am trying to get information about VMI/ SMI implementation, for ex. IDOC mapping, best practices, etc.
      I will be appreciate if you can provide me this information.
Thanks&Rgds
Angélica

Regarding EDI----XI----IDOC

Hi All,
I have One Requirement here is that
My Client's Customer will send EDI Formated Data (ANSI Type ) to Client. That Data has to be Posted into SAP R/3 Database. So here We are Using XI For that .
Can Any One Explain me what could be the Scenario here And
How to Handle this ANSI Data Format.
Regards
Babu

Hi
Scenario is EDI-XI-IDOC
Data Will come in the Form of ANSI
1) I Will Use IDOC Adapter in the Receiver End
2) For Sender Side Which Adapter I Need to Use & How to do the Conversion From ANSI Format to XML ??????
Can You Provide Any Real time Scenario Or Any thing Which meets this Requirement.
I am Still in Confusion How this ANSI Data Will be Converted into XML Either it Can Happen in Seburger Adapter OR in XI Also
Can You Expalin me How this Conversion in Detailed
>>>>>>>>>>>>>>>>
if you are getting the data in the format like ANSI then you have to first create the XML message with the help of the BIC mapper.
the BIC mapper is basically used to convert the EDI message into the XML message. to convert the EDI message into XML message ypu have to create the mapping using the option createE2xmapping in the BIC mapper.
the mapping that will be generated using the BIC mapper have to be deployed on the server.
and in the adapter you have to used the same mapping name that you have deploy on the XI server in the module tab of the adapter.
if you still face the problem please reply me back.
Thanks
Rinku

Idocs mapping in FICO

can anybody guide me how to map idocs in FICO

hi
http://help.sap.com/erp2005_ehp_03/helpdata/EN/1a/0e34f0539911d1898b0000e8322d00/frameset.htm
http://help.sap.com/search/search_overview.jsp
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sap-img.com/abap/reads-an-existing-idoc-and-dispays-the-contents-in-a-spreadsheet-format.htm
nagesh

EDI 821 transmission - URGENT

Hi Gurus,
I am struggling to find the Basic IDoc type, message and process code used for EDI 821 (Income Asset Offset) Outbount Transaction.
Please respond if anyone knows about it.
Thanks in advance.

Hi,
Please use message type FINSTA and IDoc type FINSTA01.
Regards,
Ferry Lianto

In EDI to IDOC or Idoc to EDI can we go for Dynamic recevier determination

Hi all
I am doing an EDI to IDOC scenario involving SEEBURGER( AS2) adapter .can we go for extended receiver determination
Regars
Saurabh

Saurabh,
You can not use Extended Receiver Determination coz AS2 connection is like point-to-point connection which requires AS2 id of both sender and receiver. Therefore you can not use the Extended receiver determination.
Reagrds,
Sarvesh

ALE, EDI and IDOCS

Hi
I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
Thanks in Advance.
Sudhi

Hi Sudhi
You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
Also some Education Partners of SAP give courses. Some info about these will also be there...
Regards...
*--Serdar

EDI 821 Idoc mapping

Similar Messages

Maybe you are looking for