Comparision of 2 IDocs
Hi all,
I would like to compare the segment contents of 2 outbound IDocs. In my case, I can see from table EDID4 that both the IDocs have equal number of segments (almost 150). Could anyone suggest me how I can do this.
Regards
Murthy
Hi Murthy,
Perhaps you can use FM IDOC_READ_COMPLETELY to get both IDoc segments.
Then you can compare the return table paremeters INT_EDIDD.
Regards,
Ferry Lianto
Similar Messages
-
Price comparision report through transaction ME49
Hi Exports,
I am new in abap report enhancement. I am working as a implementation project, here i have add some more fields and generate report.
Report details:
Transaction ME49-- Price Comparision report
Here i have add one Remarks fields related to Vendor and report will be generated and remarks values will display .
Please helps me and guide me how to do this tasks.
If you have code for this , please send me this mail id: [email protected]
Advance thanks you.
Regards,
JnanaIf you are goint with user exit check
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Transaction Code - ME49 Price Comparison List
Exit Name Description
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
No of Exits: 35
Rewards if useful...............
Minal -
Performance BAPI vs. IDoc
Hello,
i don't now if this is the correct forum for my question, but i also don't know which i have to take instead of this.
I have the following problem. At the moment i try to compare the BAPI and the IDoc interface with regard to performance and speed. I write a test program in C# with the SAP .NET Connector 1.0.2 and send the same data with both interfaces and measure the time the transmission needs.
My results are confusing me. IDocs are faster than BAPI, only a little bit, but they are faster. Could this be?? It seems illogical to me because i know IDocs itself use that BAPI during data processing. How can IDocs be faster in this case? Or is it only a bug in my program? I didn't find it so far. Where can i find more information about that thing (comparision between IDoc and BAPI)?Hello,
IDOC processing is usually an asynchronous process inside R/3. A successful call to the method SAPIDocSender.SubmitIDoc just means that the IDOC has been successfully transferred to the target SAP system and the corresponding processing has been triggered, but not necessarily tells if the IDOC processing has been successfully started or completed.
As explained above, the result you got is actually not so "illogical", because you are probably comparing IDOC's part time to BAPI's total time.
From the viewpoint of performance and speed, calling a BAPI directly should be always faster than calling the same BAPI indirectly through IDOC/ALE.
Regards,
Guangwei -
Logical System in IDOC-XI scenario
Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz. -
Hi All,
I am using SAP MII 12.1.5 Build 87.
I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.
We are able to send iDoc from SAP but we are not able to receive same in MII.
Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.
Following are the log details for SAP MII Logger as well as SAP NW Log.
SAP NW Log:
Error processing JRA IDOC message
SAP MII Log:
Error processing JRA IDOC message
Error processing JRA IDOC message [server=xxx, client=xxx]
[EXCEPTION]
java.lang.NullPointerException
at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
at $Proxy943.onMessage(Unknown Source)
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Please help me out on this issue.
Regards,
Manoj Bilthare
Edited by: Manoj Bilthare on May 19, 2010 12:57 PMHi Manoj,
Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
If this doesn't help you,please try restarting your server again.
How about the credential editor have you configured this as well?
Regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM -
Open Sales orders through IDOC
Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
AnandhHi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh -
Scheduling Agreement with Delivery Schedule using Idoc messages
Hi all,
Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
Thank you
Regards
SubhaHi ,
The Field
LABKY : Delivery schedule key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0393. external length : 000001
Regards
Seegal -
Invoice and delivery notes - idocs..
Hello SD experts,
I am new to SD.
Can any one tell me what is the invoice. I mean
what are the table AND transaction codes I have to go and check ?
What are delivery notes ?
My functional consultant is telling that
there is a consolidated invoice and there are 2 delivery notes that are being combined for this invoice. The invoice # is 6016186004
For DN# 6073107044 there is a VICS BOL that was passed back that is = 04000000000016146
6073107045 there is a VICS BOL that was passed back that is = 04000000000016023
and he wants to know how the program selects which VICS BOL fields in IDOC. He gave me to use IDOC #77122253 in quality system for testing.
In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
If so then what are the I need to give
Output application (is it V1 or MR ?)
Output type ??hi ..
Please refer below..
for invoice , tables: VBRK and VBRP
AND transaction codes : VF01 to 03.
What are delivery notes ?
after goods issue, we need to issues delivery note to customer.
In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
you need to go to VL70 or you can process with RSNAST00.
Output application type : V2
Output type : LD00
Regards
Venkat.. Ananth Technologies -
Error Posting IDOC: need help in understanding the following error
Hi ALL
Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
where SAP_050 is the RFC destination created to post IDOCs
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated.............Thank you!Hi Patrick,
Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
Also Refer this Note 747322
Regards,
Prakash -
Error while executing a JDBC to Idoc scenario : No standard agreement found
Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
RaviHi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka -
Getting an error "Customer could not be determined" for IDOCs in SCM 7.0
Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.Hi Ranjini,
Please look into the following
1) Customer master data is fully maintained
2) Customer number ranges are fully defined in customisation
3) Customer address details are maintained
4) Is there any special characters used while defining customer data or customer
number like $, #,[ etc.,?
5) Customer int models are active in SCM side prior to IDOC processing (including
customer, demand, stocks etc)
Please confirm your findings
Regards
R. Senthil Mareeswaran. -
Error in creation of PurOrd IDoc
Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada GalindoHi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
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)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji -
Error while updating the status record of IDOC in SAP
Hi All,
I am facing this problem. I have done outbound processing and IDOC was sent successfully from SAP to EDI system and it was processed in EDI and now EDI system wants to send the status back to SAP with a status message and the status number that we are using is '24' and we have mapped all the fields in the status table EDIDS and made sure that EDI system sends all those and I think Counter field can not be determined by EDI system so EDI system used the counter '1' since it can not determine how many counters are already there in SAP and unless we pass the value to this counter field we were getting the error. After passing all the values the status of the IDOC is updated with the status '00' instead of '24' and we do not know why it is happened and I would like to know how SAP converts the status record that is received from the EDI system.
Please let me know how the status record will be translated into SAP from EDI system and I ahve followed basically EDIDS structure and the IDOC status is updating in SAP but with wrong status number and the alignemnt also missing in SAP fields like if I give some text in the EDI it is splitting and storing in 2 fields.
Please help me in this and I think I have explained the problem in a detail manner.
Thanks,
Ramesh.Hi Naresh,
Thanks for the reply and my question is since EDI system is able to send the status back to SAP from EDI system and only problem is it is updatinf the status wrong and I have checked the EDIDS table also and the entry is creating with another counter and please confirm me that it is because of EDI does not support the status record update so that I can confirm to the client that there is nothing wrong in the way SAP functions and EDI system can not update the status code in the SAP.
Thanks,
Ramesh. -
Help in creation of XML file for IDOC postings
Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
SriniHello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto -
Issue:Creation of Extended iDOC data entries in receiving system.
Hi all,
I have extended standard IDOC MATMAS05 for classification view.I am receiving the data successfully on recewing side.And i have done coading in user exit to store data in database table inside
IDOC_INPUT_MATMAS01- function module.
When i execute the BD10 from sending sytem and view the idoc at receiving end from WE05 i can see the idoc but when i try to see the material i cant see the classification(extended) view in mm03.Rest of the views are created .When i execute the idoc from WE19 ,Classification(extended) view gets created.
Please guide me so that the CLASSIFICATION view get automatically created in receiving system without using WE19.
Thanks.Yes i used this function module-
CALL FUNCTION 'BAPI_OBJCL_CREATE'
EXPORTING
objectkeynew = objectkeynew1
objecttablenew = 'MARA'
classnumnew = wa_classnumnew1
classtypenew = z1sklart-klart "classtypenew1
status = '1'
STANDARDCLASS =
CHANGENUMBER =
keydate = sy-datum
NO_DEFAULT_VALUES = ' '
IMPORTING
CLASSIF_STATUS =
TABLES
ALLOCVALUESNUM =
allocvalueschar = allocvalueschar2[]
ALLOCVALUESCURR =
return = return1
*WAIT UP TO 1 SECONDS.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'
IMPORTING
RETURN =
Please explain me how to maintain the Views Status at MARA general info segment level.
Maybe you are looking for
-
PS Script to find the list of users and the groups in a Workgroup server
Hi There, could you please explain on how to get a complete list of local users and local groups in a "Workgroup" server to which they belong to using Powershell. I'm able to get the users list but couldn't find any help in finding the script to find
-
Need help: GUI_DOWNLOAD and tab-separated in between fields.
hello everyone, this is the layout of the interface that i created: sy-title total records processed: XX total records failed: XX summary of the error pernr<tab>name<tab>error message<tab>otherfieldshere i wanted the error log to be saved lo
-
Hi ! It takes a long time (can be up to more than 10 min) for my Sports Tracker to get a signal from GPS. I wonder if it has to do with the setting "GPS Filtering" ? But there is no help for ST. I wonder where I can get the manual ? And what
-
Installed and used Gravity (once after installing-...
Installed and used Gravity (once after installing-) but not able to find in menu/prog. manager? Ovi Store says it is installed but now nowhere to be found on the 5230. Help please - this is a really cool app. that I am keen to keep using.
-
Vista, PSE 11, Epson R3000
After printing a picture, cannot print a second picture. Message:"There was an error opening your printer. Printing functions will not be available until you have selected a printer and reopened any documents" This does not occur with PSE 9