IDOC Function Modules?

[Former Member]

Hi.

Can anyone please tell me about the FM's "EDI_PARTNER_APPL_READ_OUT" and "EDI_VIEW_READ"

used in an outbound process to get the active segments.?

I mean when and why do we use these FM's?

Thanks

[Former Member]

Hi,

EDI_PARTNER_APPL_READ_OUT

_________________________

This is to read the partner profiles for a given partner and message type.

EDI_VIEW_READ

______________

This function module can be used to read the attributes and syntax of an IDoc view. The attributes of the IDoc view contain the description of the IDoc view, as well as the assigned basic type, the assigned extension and the assigned logical message. In addition, parameters can be used to control whether the development class is also read and whether authorization checks take place. The syntax table PT_SYNTAX is maintained with the IDoc segments contained in the view (positive logic).

(From the function module documentation)

I am not sure if these are explicity used in custom programming. To me these are internally used by the standard SAP programs to trigger the outbound idocs.

Regards,

Ravi

Note : Please mark the helpful answers

[Former Member]

Hi,

EDI_PARTNER_APPL_READ_OUT

Read partner profile for one partner (outbound parameters)

EDI_VIEW_READ

just check the FM documentaiton..

FU EDI_VIEW_READ

____________________________________________________

Text

Read attributes and syntax for view

Functionality

This function module can be used to read the attributes and syntax of an IDoc view. The attributes of the IDoc view contain the description of the IDoc view, as well as the assigned basic type, the assigned extension and the assigned logical message. In addition, parameters can be used to control whether the development class is also read and whether authorization checks take place. The syntax table PT_SYNTAX is maintained with the IDoc segments contained in the view (positive logic).

Example

Scenario: using IDoc views in outbound processing:

data: l_ediview like edview-ediview,

l_edk13 like edk13,

l_edp13 like edp13,

lt_viewsyntax like viewsyn occurs 0 with header line.

• Fill edk13 structure to read the partner profile

perform fill_edk13 using l_edk13.

• Read the partner profile

call function 'EDI_PARTNER_APPL_READ_OUT'

exporting

rec_edk13 = l_edk13

importing

rec_edp13 = l_edp13

exceptions

others = 1.

• Determine the IDoc view which is used

l_edview = l_edp13-ediview.

• Fill the IDoc segments with application data

if l_ediview is initial.

• If no IDoc view is used, fill all segments

...

else.

• An IDoc view is used

• Read the syntax of the IDoc view

call function 'EDI_VIEW_READ'

exporting

pi_view = l_ediview

pi_check_authority = 'X'

pi_read_devc = ' '

tables

pt_syntax = lt_viewsyntax

exceptions

others = 1.

• Only fill segments from table lt_viewsyn

....

endif.

Parameters

PI_VIEW

PI_CHECK_AUTHORITY

PI_READ_DEVC

PE_ATTRIBUTES

PT_SYNTAX

Exceptions

OBJECT_NOT_FOUND

DB_ERROR

NO_AUTHORITY

Function Group

EDIM

Regards

vijay

[Former Member]

Hi Vijay..

Thanks for your answer

But can you please tell me what exactly do we mean by an IDOC view?

[Former Member]

HI

GOOD

EDI_PARTNER_APPL_READ_OUT

Reads EDP13 for a specific partner. The partner status must be set to “active”.

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.

THANKS

MRUTYUN