Steps for configuring Outbound Idoc OILSHI01

Question

Hi experts,
    can anybody tell me the steps how to configure an Outbound IDOC.
    It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
    if not anything else will also do.
    Kindly give me steps in detailed. Since i have never done this. Including 
    distribution modle (BD64). in which case it generates the Automatic Partner
    profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Answer 1

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your  business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc. 
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
     a. trigger the idoc on saving the doucment.  this triggers idoc as soon as you save the idoc.
     b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
     c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM