IDOCs

[Former Member]

hi friends,

as a functional consultant,

what kind of work am i expected to do on IDOCs.

i heard that, we need to go to BD 87 and check the idoc errors,

can some some one please let me know in details rhe procedure to follow.

thank you.

[sivaprasad_r]

Hi,

One more utility of IDOC is uploading of Legacy data with BAPI's.

If you are implementing Flexible Real Estate Management Module especially, you need to upload the data through LSMW using BAPI's. While the data is being uploaded throgh BAPI,s the system generates IDOC's for updating the relevant data Structure directly.

Thanks

Siva

[Former Member]

Hi:

IDocs are involved whenever SAP interacts with non-SAP system(s).

For example a company may use a third party/external application to manage their invoice payments. In this case the external application must have the database of the vendors that exist in SAP.

For this you have to set up distribution model in T-Code SALE > Modelling and Implementing Business Process > Maintain Distribution Model and Distribute views. What you are basically doing here is you have to define the sender system (SAP: in case the vendor master data is updated from SAP to the external application) and the receiver system (the external application). Similarly you will also have to define external application as sender system when Inovice comes from the external system to SAP. In this case SAP is a receiver system.

You also have to ensure that logical systems are defined for the above mentioned process. In the above scenario there are two logical systems SAP and external application. Each logical system is given a name, for example SAP:R3DCLNT and external system: EXTSYSTM

Next you need to create the message types (IDocs) in the distribution model. In this business process will require IDocs messages like CREMAS (update vendor master data in the external system) ORDERS (Purchase Order create sent to external app) ORDCHG (PO change sent to ext app), INVOIC (invoice that comes from the external application)

To ensure that the external application is updated continuously like changes in vendor master data, you need to maintain "change pointers"

CREMAS, ORDERS and ORDCHG are Outbound IDocs and they need to be defined in the partner profiles as well.

INVOIC in an Inbound IDoc which will also be defined in partner profiles.

You also have to define the RFC destinations to where the IDocs will go. Port number also have to be defined. This part is normally done by the basis person.

After an IDoc is created, it is typically sent to a middleware like SAPBC or TIBCO, which in turn interacts with the external application through XML (for example), there may be other formats too.

T-Code WE02/WE05 displays whether an IDoc is generated or not.

I have just tried to give you an overview of a relatively simple business scenario. The above mentioned scenarios may also involve other types of IDocs like credit memos, goods receipt etc.. For indepth info on IDoc check this out:

http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli

http://www.photographybykevin.net/sap/idoc_overview.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

Warning: It's very easy to get addicted to IDocs once you get a hang of it!

Have fun.

Assign points if info helps.

Vj