IDoc Views

IDoc types can be used for more than one message, which means that they can be used for more than one business process. This has the result that they generally get more segments than needed by the application. To improve performance when you generate the IDoc, you can use views to make sure that only those segments relevant for the business process are filled with data. Therefore, views are only significant for outbound IDocs.

The application must support this function. The program which writes the application data in the IDocs must carry out the following tasks:

• Determine from the partner profiles whether a view exists. To determine this, the function module EDI_PARTNER_READ_OUTGOING is called.

• Query, which segments belong to the view. The function module EDI_VIEW_READ is called once, which returns the segments in a table.

• Query, whether the current segment should be maintained in the current view. The table returned by EDI_VIEW_READ is used.

For a list of IDoc Interfaces that support IDoc views, see SAPNet Note 185445.

You must have IDoc development authorization (authorization object S_IDOCDEFT, for example in the role SAP_BC_SRV_EDI_DEVELOPER) before you can define a view.

1. To define a view, choose the ALE customizing transaction  SALE  Model and Implement Business Process  Configure Master Data Distribution  Specify Scope of Data to be Distributed  IDoc Views  (WE32). Enter a name for the view and choose .

2. On the next screen, assign a message type (logical message) and a basic type to the view, and possibly an enhancement as well. This assignment is checked in the partner profiles.

3. Position the cursor on a segment, which is to be included in the view. Choose . The following segments must be included in the view:

   • Qualified segments

   • Mandatory segments

4. Save your entries.

5. In the partner profiles ( general outbound processing), enter the view for the corresponding combination of partner and message.