ABAPer responsibility in Interface and Incoming Idocs

Hello All,
Could any body please explain me what is ABAPers responsibilitis in Interfaces and Incoming Idocs.
Case: We are getting an idoc(inbound) in our system to create sales order so please let me know in this case what would be my roles and responsibilities as an abaper in detail..
Thanks to reply at the earliest..
If you would like to share some documents then here is my email id: [email protected]
Thanks,
Devasing.

Hi,
An ABAPers role in this case could be incase any enhancements are needed, this is if all the settings for the ALE are going to be handled by an ALE consultant.
In this case if some consumization needs to be done like enhancing the existing IDOC for creating a sales order, then an ABAPer would come into picture.
Thanks & Regards,
Vanita M.

Similar Messages

INTERFACE AND EVENTS IN ABAP OO

Can some one explain me the real time need with example for use of interfaces and events in abap objects
(asking interface and events along doesnt mean that i am relating them).
<removed_by_moderator>
Pankaj Giri
Edited by: Julius Bussche on Jul 14, 2008 1:36 PM

Events :
Technically speaking :
" Events are notifications an object receives from, or transmits to, other objects or applications. Events allow objects to perform actions whenever a specific occurrence takes place. Microsoft Windows is an event-driven operating system, events can come from other objects, applications, or user input such as mouse clicks or key presses. "
Lets say you have an ALV - An editable one ...
Lats say - Once you press some button you want some kind of validation to be done.
How to do this ?
Raise an Event - Which is handled by a method and write the validation code.
Now you might argue, that I can do it in this way : Capture the function code - and call the validate method.
Yes, in this case it can be done.. But lets say .. you change a field in the ALV and you want the validation to be done as soon as he is done with typing.
Where is the function code here ? No function code... But there is an event here - The data changed event.
So you can raise a data changed event that can be handled and will do the validation.
It is not user friendly that you ask the user to press a button (to get the function code) for validation each time he enters a data.
The events can be raised by a system, or by a program also. So in this case the data changed event is raised by a system that you can handle.
Also, Lets say on a particular action you want some code to trigger. (You can take the same example of validation code). In this case the code to trigger is in a separate class. The object of which is not available here at this moment. (This case happens very frequently).
Advantage with events : Event handlers can be in a separate class also.
e.g : In the middle of some business logic .. you encounter a error. You want to send this information to the UI (to user - in form of a pop up) and then continue with some processing.
In many cases - A direct method call to trigger the pop up is not done. Because (in ideal cases) the engine must not interact with UI directly - Because the UI could be some other application - like a windows UI but the error comes from some SAP program.
So - A event is raised from the engine that is handled in the UI and a pop up is triggered.
Here -- I would have different classes (lets say for different Operating Systems). And all these classes must register to the event ERROR raised in application.
And these different classes for different Operation systems will have different code to raise a pop-up.
Now you can imagine : If you coded a pop-up for Windows (in your application logic) .. it will not work for Mac or Linux. But of you raise a event.. that is handled separately by a different UI classes for Win, Linux or Mac they will catch this event and process accordingly.
May be I complicated this explanation .... but I couldn't think of a simpler and concrete example.
Cheers.
Varun.

SAP IDOC's, interfaces and BAPI's

Hi i am new to SD, can anyone give me documentation or reading material for SAP IDOC's, interfaces and BAPI's .
Help would be greatly appreciated.
Thanking you

Hi Reddy,
Very general question, I don't think you will find the answer in one document.
BAPIs are normal function modules, with predefined input and output structures to perform standard business transactions.
IDOCs are standardised interface documents to transfer data.
Once the IDOC is read, it almost always calls a BAPI to perform the business transaction.
Therefore start with reading about BAPIs since you will definately have to master those when starting to work on interfaces.
There are hundreds of BAPIs so best is to start with a specific process, example sales order create or material master create.
Try transaction BAPI, this lists most of the BAPIs and contains excellent documentation.
Thanks for your points,
Filip

How to Identify incoming and outgoing IDOC in the system for last one year.

Dear All,
How to Identify incoming and outgoing IDOC in the system for last one year.
Regards
Ashok

Dear Anindya,
I used WE05 the result by giving direction outbound.Then on created field i put the value date.I m getting the output in the no of idoc number.
This is only the way to identify?
Thnx
Ashok
Edited by: ashok singh on Oct 22, 2009 8:40 AM

Difference between PI/XI interface and ABAP interface

Hello Experts,
We are in the process of identifying interfaces for our current client. I am looking for some documentation or any specific information that will help me to differentiate between SAP PI interface and ABAP Interface. Basically I want to know what are the advantages of PI interface over ABAP interface. What is better? and why?
Any information would be of great help. Thanks.

PI (versus point to point ABAP) advantages are:
1)     Centralized control over data security
2)     More effective (centralized) interface failure monitoring and resolution
3)     Elimination of redundant development and maintenance costs

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Messages get lost between IE and AE (IDoc to SOAP - Async)

Dear Experts,
in a IDoc to SOAP (Async) scenario a message was not transferred. I could not see any error message in RWB or ABAP Monitoring. When I enter RWB, the column engine is "Integration Engine" and the status is "Successful". At the same time other message with the same message interface were transmitted and they have engine "All" and status "Successful".
Why was this message not passed on to Adapter Engine? How can I restart the processing, so that the message is transfered?
Best regards,
David

Thank you for your answers:
@ Divyesh:
I can't resend the message. It does not have an error status. It says "Successful", although it only can be seen in Integration Engine, not Adapter Engine. There are not SM58 errors.
@ Krish:
In ABAP Monitoring all steps were performed as expected. Before and after this message some other messages with the same message interface were transmitted and they are visible in ABAP Monitoring, Inegration Engine and Adpater Engine.
@Hareenkumar:
In SAP everything looks like expected.
The only difference between this message and other messages sent at the same time (which were transmitted correctly) is that in RWB Message Monitoring (Component: Integration Server) the Engine is "Integration Engine" instead of "All". And the message is not visible when you select for component "Adapter Engine".
Do you have another idea?
Thanks in advance,
David

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Multimapping synchronous webservice and async idoc

Experts,
I have a scenario where the sender is webservice (soap) and receiver is IDOC (async) + SOAP (sync)
When a webservice sends order to PI, i need to create an idoc in SAP as well as send back response message to webservice. (webservice is expecting to send data using the response payload)
We have to generate few values from the request and manipulate them (using message mapping) and send response back. (similar to sync webservice interface)
What is the best way to achieve this? can we integrate both async and sync interface in one interface without using BPM?
Map 1 -> SOAP <-> PI <-> IDOC
Map2 -> SOAP <-> PI <-> SOAP
Best Regards,
Pavan

However if i do make use of BPM then the idoc that will be returned from SAP to PI will be different since the same idoc
cannot send data back.
No problem if the sending and receiving IDOCs are different. The only thing that you need to take care is the IDOC_Request and IDOC_Response should have one field which contains the same value....for correlation in the BPM.
Is there a way we can setup some sort of correlation to make sure that the new idoc that is triggered after the sales order
creation is indeed related to the one that is sent from PI initially.
As mentioned above the IDOC that BPM sends and receives (from ECC) should have a field which has same value.
Regards,
Abhishek.

Interface and SAP system issue

hi Experts
Scenario : We have External system (Interface) and SAP system. GR usually done in External system for stock materials PO , then it will transfered and updated in SAP system thro IDOC daily bases.
And then in SAP ,Zreport is there to find out any discrepancy in stocks(Between Extrnl and SAP system).
Problem: They had done GR in external system and they had transferred to SAP throu IDOC. (This usually bieing processed for 1000 of materials.
Now for some materials its showing discrepancy error in Zreport eventhough the SAP system got updated on stocks throu IDOC from external system. ( Not for all materials only for very few case).
So any experts has come across this kind situation in thier experiance .. how to solve this ??
Note : If any Bacth job is being done in background in SAP after updation the stocks in SAP system throu IDOC. How to find out the batch job in back groud ???
Thanks

hii
Thanks for ur response.
I did't mention in previous message, IDOC got posted in SAP system perfectly without any error . (I have cross checked IDOC).
But after idoc posting in SAP system , the Zreport getting updated , so here is my confusion and doubt.
Where there can be any system in background to update stocks in Zreport from SAP system. Is it possible to find from our side batch job has being processed between standard SAP and Zreport .
There is any way to find ???
Thanks

Incoming IDOC error

Hi All,
When i tried to post a incoming IDOC which will result in a BDC session and we post the IDOC as a accounting document, iam getting a Error message of Post document ( screen not found ) with a status 51, Can any of you let me know about this error, will reward with points for answers.

Hi
May be the BDC session is not recorded well, check the program again.
May be the code added in the program is relating to the screen which is not available at the time of document posting ( these screen numbers will be diferent for each window/pop up window - like seperate screen number possible of additional information screen, profitability segment screen, other information screen, etc.) check the same with ABAPer
VVR

Sales Process And EDI Idocs Integration

Hi Friends,,
Good Day To You All !!!!
Please enhance my knowledge with your valuable reply.
I am new to ABAP and would like to learn the following .
1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
2 . Idocs - Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
I need the above information to get a clear picture of the process taking below.
What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
And the idocs update the corresponding status in Siebel .
I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
Thanks.
With regards,
Learner .
Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

Hello,
         If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
            The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
     All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
Hope it was clear enough.
Thanks and Regards,
Venkat Phani Prasad Konduri

Request iDoc and status iDoc correlation

Hello,
I have a strange problem.
In my XI 3.0, I have an iDoc2iDoc interface which used to work fine, until I installed patch level 14.
Now, when the acknowledgement (ALEAUD) comes back into my R/3 system, the iDoc system does not recognize it as a response for a specific request iDoc I've sent, but as an ordinary inbound iDoc.
After a short investigation, I found out that the iDoc number is not correlated, it seems like a problem in the iDoc adapter in the XI, that does not translate the iDoc number of the target system back into the iDoc number of the original system.
Has anyone met with this kind of problem ? any solutions ?
Thank you,
Elad.

Hi Anand.
All of the partner profile and iDocs configuration are complete and correct.
I'll try to be a bit more specific:
Local R/3 sends iDoc MATMAS through XI 3.0 and receives ALEAUD iDoc as an applicational acknowledgement.
For the R/3 to be able to correlate between the inbound ALEAUD and the outbound MATMAS the iDoc system uses a field containing the iDoc number.
The problem is that ALEAUD has the number generated by the remote system and the MATMAS has the number of my local system, the XI is suposed to translate the remote iDoc number back to the local iDoc number.
I hope it's clearer now, and that someone can help.
Thank you,
Elad.

Re-send incoming IDOC

Hi,
we created own IDOC type and input function module to create Sales orders from interface data: Incoming file data are converted to IDOCS, IDOC_INBOUND_SINGLE saves IDOCS.
Is there a way to re-route IDOCs to outbound?
The background is that we have one system to receive interface data. They have to be converted to 'order' idocs. But the IDOCS have to be processed in different systems. Will an IDOC saved with FM IDOC_INBOUND_SINGLE be an outbound one if we fill the control structure pi_idoc_control_rec_40 accordingly with destination system?
Thanks for any hints!
C.

I had an other similar thread answering the question

ABAPer responsibility in Interface and Incoming Idocs

Similar Messages

Maybe you are looking for