Development of: SAP- XML IDOC Validation - Mapping - EDI-VAN

Hi ,
I am novice to SAP.
I would appreciate, if you would suggest best way to achieve following Scenario:
With Minimum Cost. No High Cost middleware products, beacuse we have only following two scenarios.
1. SAP -
> XML IDOC (SHPMNT01) Validation -
> MapTo- EDI 404_4010------> FTP Loation
2. SAP----
>XML IDOC ZSHPEXT1 Validation -
> MapTo EDI 204_4010 -
> VAN
A. XML IDOC ZSHPEXT1 Validation error send error message to SAP
B.SMTP- Email if there is IDOC validation error or error in message.
Just for information: We have ERPConnect.
Thank You,

Hi
Thanks for the answer.
Regarding the FM IDX_XML_TO_IDOC, I thing that I can't use it directly because I have to write a program, I have to read the Xml file (that is located in a special directory of the operative system) and then use the FM putting xml data in the XML_DATA import parameter.
It's correct?
Bye
Carlo

Similar Messages

Sap Xml Idoc Inbound in Sap

Hi all
If I have to receive an Edi message from an external system (for example an Invoice from a vendor), could I get in Sap an Idoc from a flat file formatted as a Sap Xml format?
As Sap Xml format I mean the same structure of an xml file generated in Sap to the Xml file port.
(The sap r/3 system is a Sap Enterprise version)
Thanks in advance
Bye
Carlo
Message was edited by: carlo pergola

Hi
Thanks for the answer.
Regarding the FM IDX_XML_TO_IDOC, I thing that I can't use it directly because I have to write a program, I have to read the Xml file (that is located in a special directory of the operative system) and then use the FM putting xml data in the XML_DATA import parameter.
It's correct?
Bye
Carlo

Map EDI messages to SAP iDocs

Hi all,
Is is possible to map EDI messages to SAP iDocs using Oracle Integration?
Thanks

Yes, OracleAS Integration has several components. One is called Integration B2B, which allow you to send and receive EDI messages. You can then pass this on either using Integration InterConnect or BPEL Process Manager to the SAP adapter which can talk to SAP systems using e.g. iDocs.

How to Push the into SAP ( XML data converted into IDOC )

Hi
i am getting XML file from Non SAP system.I need to push XML data into SAP on daily basis with out using XI as the middleware.
I know if i get text file will use BDC's or LSMW. But i am getting data in XML format and then i need to converted into IDOC format and stored in to sap data base tables.
Thanks for advance.
srini

Is the XML an IDOC-XML or custom XML that you need to post as an IDOC??
If it is IDOC-XML you need to defined XMLFile port to process the IDOC-XML without any mapping.
If it is a custom XML, parse the XML data into an internal table (as required) & continue with BDC or IDOC posting as you wish.
Check for XML parsing programs..
-Siva Maranani

Using PI to map IDoc BENEFIT3 to EDI 834

Has any used PI/XI to map IDoc BENEFIT3 to EDI 834? We are looking to use this approach but have had problems finding a standard map. You would think SAP would have one since they stand by their BENEFIT3 IDoc being sufficient to map to the 834. This will take forever to do it from scratch or even without an example. Help please.

Hi
You can do 1:n multimapping
in message mapping in messages tab ..add both the structures in target tab and do the mapping
and in operation mapping add both the message interface on the target side
PLease go through this blog
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

What is best way to connect a non-sap sys sending xml idocs to SAP system

Hi Can some one please guide as to what will be the best approach in connecting a NON SAP system to a SAP system.
The non sap system should not be connected to access real time data,it does not support RFC,it can send data in IDOC xml format and i think in teaxt files also.Also I dont think there is any EDI subsystem in place.
There has to be a periodic upload of material data from SAP /stock status/
then there will be incoming data into SAP for sales order/purchase order etc
What would be the best way to connect the two systems,IDOCs with partial EDI looks the best way ,but I am confused as to how will the XML IDOC be converted to normal IDOC and viceversa,how to handle the event triggering mechanism.
If someone has experience in such a scenario ,please help.
There is a option to update the database of the application through SQL also...

Hi,
Check this link.
Web Services from Function Module
it might help u.
Thanks.

Receive XML file from CIDX adapter and Post to SAP as IDoc using XI

I have scenario where we will receive the xml file from CIDX adapter. I need to take the xml from CIDX, do the Database Lookup and post it to SAP as IDoc.
Any technical documentaion or step-by-step process documents can be very helpfull to me, since I am new to XI
Thanks
SP

Lookup in XI is used to call the target data storage system and get data from there to your mapping programme.
In XI you can do Lookup in Message Mapping, Java Mapping and in XSLT Mapping. Previously Lookup in XI was system dependent. But now what ever the system are i.e. SAP system or non-sap system(Oracle,MS SQL etc) lookup API are same.
Overview of Lookup
- Lookups are used to identify/request the data from mapping program.
- It interrupt the process and looking for data which was stored in target system.
- It get that data and comeback to process and continue with that data.
Types of Lookups in XI
- JDBC Lookup: JDBC lookup is used for accessing data from database (non SAP).
- RFC Lookup: RFC lookup is used for accessing the SAP Data.
- SOAP Lookup: SOAP lookup is used for accessing data from Webservice
Steps to perform Lookup in Mapping
Import package com.sap.aii.mapping.lookup.*;
Create connection to the target Database system.
// Determine communication channel created in ID
Channel channel = null;
channel = LookupService.getChannel("DB-SYSTEM-NAME","DB-CHANNEL-NAME");
// Get system accessor for the channel.
DataBaseAccessor accessor = null;
accessor = LookupService.getDataBaseAccessor(channel);
Build the Query String.
Getting Result
// Execute Query and get the values.
DataBaseResult resultSet = null;
resultSet = accessor.execute(Query);

ABAP Mapping XML-IDoc to Flat string: missing character of segement header

Hello folks!
I'm using an ABAP-Mapping in order to trasform an XML-IDOC to a flat string.
The implementation of the mapping is in accordance with the "HOW TO convert an IDoc-XML to ..."Basically it works fine except the following:
The following line shows one Segment of an IDoc. the control record is ok.
With '380' begins the payload of the segment. The part before includes the segment header,
which is 63 Bytes long, which is correct.
What we're missing, is the last character of the segement header:
ABAP-Mapping:
E1VDEWBGM                     01000000000325511200000020000000 380   5 (...)
BusinessConnector:
E1VDEWBGM                     010000000003255112000000200000001380   5 (...)
Again: the overall length of the segment is ok, but the '1' of the field hirarchie level is overwritten.
Any idea?

In that case you need to extend the trace file in the Visual Admin Console...
     Services
     Log Configurator
     Locations
     Choose the location (Java package) and the tracing level (severity)
(for example, com.sap.aii.adapter.file)
     Root Location > com > sap > aii > File
     Set the severity and choose Copy Severity to Subtree
Check the trace file to find the field erroring this way!

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

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

Mapping EDI 820 (remittance advice) to IDOC

Hi,
Can anyone give me the steps required to do a mapping of EDI 820 (Remittance advice) to IDOC? If you have the mapping already, can you send that to me at garapatic at yahoo.com

Hi Greetson,
    Before I posted information on this forum, I checked the web to see if I can look at any helpful stuff for this mapping and I could not find any.
   I tried to look for EDI EDIFACT stuff on the website for my mapping EDI vendor(Biztalk) and could not find any.
   Can you point me to specific websites which will be helpful to me? Or to any mapping document.
Thanks,
Nile

SAP XML and SAP IDOC XML

Hi Friends,
Can any one tell me what is the difference between SAP XML and SAP IDOC XML?
Regards,
Kumar

Hi,
Various XML standards are supported by SAP. It presents data according to an SAP specification either in IDoc-XML or BAPI-XML, the SAP XML extensions for IDocs and BAPIs. It uses preprepared representations of the SAP interfaces to XML Commerce Business Language (xCBL) messages to facilitate communication with the MarketSet marketplaces.
Messages are stored in a generic envelope. This envelope contains metadata that controls, among other things, the routing of the messages. SAP supports two different standards for these envelopes - Microsoft BizTalk and a format similar to Simple Object Access Protocol (SOAP). Packaging SAP BAPIs in a standard envelope offers several advantages, including direct processing of messages by external applications and a uniform system of error handling.
Regards'
Aashish Sinha
PS : reward points if helpful

Automate flat IDOC to XML IDOC using one interface

Hello all,
We are currently going through a migration process where XI will be replacing a legacy system. As part of our testing procedure, we are using historical data pairings from the legacy system and using an automated tool to compare if the interfaces we develop in XI match. The catch is we need the data that we are comparing in XML format for the automated tool to be able to do the comparison, and unfortunately the legacy data is a flat format. So now I would like to automate a way to convert this data to XML format.
Specifically for IDOCs, I would like to have an interface which picks up the flat files, transforms them to XML, and then drops them back into another file directory in the XML format. It would need to be able to pick up any kind of IDOC (given that XI has the metadata already imported), recognize what message type it is, then do the conversion.
I have been reading on SDN and found that there is a standard tool to do the conversion, but it appears it can only handle one kind of IDOC at a time, and it appears it only picks up one specifically named file at a time.
Has anybody tried to implement a scenario like this? Any help is appreciated (A walkthrough would be the best!).
Thanks in advance,
Mike

Mike,
What version of PI will you be using? PI 7.11 can now auto-convert Flat File IDocs to XML IDoc and vice versa.
Here is the documentation:
http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm (flat to XML)
http://help.sap.com/saphelp_nwpi711/helpdata/en/74/a45bc07e2043fb9b63295229178903/frameset.htm (XML to flat)
I have not tried this personally, but seems like you might be able to use a "File to File" scenario with no mapping, and use the "IDOCFlatToXmlConvertor" Module in your File Adapter Comms Channel and it may just work, giving you files that are the IDoc XML version of the flat file it is reading. It looks like it does an RFC call to the back-end SAP system where the IDocs are originally from (or could be any system as long as you know the IDocs in there are identical), and reads the IDoc metadata (which has always included flat file field offsets for each IDoc Segment Field), and applies that either to convert from flat file IDoc to XML IDoc, or XML IDoc to flat file IDoc.
It does mention that there is a limitation that there can only be one IDoc in the source flat file - could be a problem if you have many in one file, which is pretty typical.
Regards,
Brendan

Difference btw idoc ale and edi

Hi all,
I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
Also do send some materials for the same.

Hi,
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
IDOC:
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
[http://www.sappoint.com/presentation.html]
[http://www.allsaplinks.com/idoc_search.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.erpgenie.com/sapedi/idoc_abap.htm]
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
[Re: How to create IDOC;
Check below link. It will give the step by step procedure for IDOC creation.
[http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
ALE/ IDOC
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
go trough these links.
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[www.sappoint.com]
--here u can find the ppts and basic seetings for ALE
[http://sappoint.com/presentation.html]
[www.sapgenie.com]
[http://www.sapgenie.com/ale/index.htm]
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
RFC:
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
check out the following link it might help you
[http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
EDI:
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
[http://www.erpgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
[ALE / IDOC / RFC / EDI]
[SAP ABAP and EDI/ALE/IDOC]
[Re: IDOC/BAPI/ALE/EDI]
Regards,
Dhruv Shah

SAP XML Parser

Hi,
Can anyone tell me how the SAP XML Parser works in Abap?
And how to use it?
Thanks & Regards,
Jeba.

hi jeba,
Prior to SAP ERP 6.0 Enhancement Package 2 (EhP2), loading data for Central Contractor Registration (CCR) was a two-step process: data was first read from a flat file and preloaded into SAP tables, then a separate program was executed to create or update vendor master records by means of CREMAS05 iDoc. When EhP2 is installed, new CCR programs (FMFGCCR_CREATE and FMFGCCR_UPDATE) can be customized by means of an enhancement implementation to access CCR data in real time for example, using Point-to-Point or XI interface with the CCR server (see the documentation and sample implementation classes for enhancement spot FMFG_CCR_PROCESS).
New CCR create/update programs available in EhP2 receive and process CCR data which includes creating and updating SAP vendor master records based on the provided mapping of CCR fields into SAP vendor master fields as well as creating/updating records in the SAP CCR tables. Design of the main program RFFMCCRVENDORCREATE01 is independent of the data source and of the method of processing the data. Default method of creating CCR records in SAP is defined by the default implementation of Enhancement Spot FMFG_CCR_VENDOR_MAINTAIN - FMFG_CCR_VENDOR_MAINTAIN_IMPL and is based on the method call to method MAINTAIN of vendor master class interface VMD_EI_API.
The data source as well as mapping from the data source to SAP CCR table fields and SAP vendor master fields is completely customizable and has to be defined in a custom implementation of Enhancement Spot FMFG_CCR_PROCESS.
We deliver two sample implementations for a CCR interface: one is based on SAP Exchange Infrastructure (XI) and one is a Point-to-Point (P2P) interface. You can define other data sources, such as a flat file or an RFC call to another system, yourself.
The XI sample solution includes XI interface with XML based mapping for Request and Response messages to and from the CCR server. The SAP CCR create/update program calls a proxy method, which is automatically generated based on the CCR XML schema used in XI, to request and receive CCR data through the XI middleware. Use of XI allows interfacing with additional systems as part of the CCR interface as well as provides extensive XML parsing, mapping, validation, and error handling features. Setting up XI based interface requires some minimal XI configuration and implementation of the XI based sample BAdI implementation CL_FMFG_CCR_PROCESS_SAMPLE for enhancement spot FMFG_CCR_PROCESS.
The P2P sample solution defines a P2P interface directly between the ERP layer and the CCR server by means of an HTTP communication protocol. This method might be more appealing to the customers who cannot use XI in their SAP landscapes. Here all XML mapping and parsing are defined in the custom implementation of the method GET_DATA.
New CCR Tables
The following new CCR tables were introduced in EhP2
●      FMCCRVENDOR_HDR (CCR Vendor Header)
●      FMCCRVENDOR_CORP (CCR Vendor Corporate Information)
●      FMCCRVENDOR_GS (CCR Vendor Goods and Services)
Table FMCCRTVENDOR is not populated by the new CCR programs.
Please reward if helpful.

Development of: SAP- XML IDOC Validation - Mapping - EDI-VAN

Similar Messages

Maybe you are looking for