topic Re: Outbound in Application Development and Automation Discussions

Outbound

Former Member — Wed, 12 Mar 2008 10:56:57 GMT

Hi Experts,

I dont have any idea abt Outbound.

Could anybody guide me reg.g Outbound.

and cud u giv the small example prog .

Regards

Ashok

Re: Outbound

Former Member — Wed, 12 Mar 2008 11:06:38 GMT

Hi,

I presume you want to know about outbound idocs.Refer to the details below:

Creating and processing IDocs is primarily a mechanical task, which is certainly true for most interface programming. We will show a short example that packs SAP R/3 SAPscript standard text elements into IDocs and stores them.

Outbound IDocs from R/3 are usually created by a function module. This function

module is dynamically called by the IDoc engine. A sophisticated customising

defines the conditions and parameters to find the correct function module.

The interface parameters of the processing function need to be compatible with a

well-defined standard, because the function module will be called from within

another program.

IDoc inbound functions are function modules with a standard interface, which will

interpret the received IDoc data and prepare it for processing.

The received IDoc data is processed record by record and interpreted according to

the segment information provided with each record. The prepared data can then be

processed by an application, a function module, or a self-written program.

The example programs in the following chapters will show you how texts from the

text pool can be converted into an IDoc and processed by an inbound routine to be

stored into another system.

The following will give you the basics to understand the example:

SAP R/3 allows the creation of text elements, e.g. with transaction SO10. Each

standard text element has a control record which is stored in table STXH. The text

lines themselves are stored in a special cluster table. To retrieve the text from the

cluster, you will use the standard function module function READ_TEXT . We

will read such a text and pack it into an IDoc. That is what the following simple

function module does.

If there is no convenient routine to process data, the easiest way to hand over the

data to an application is to record a transaction with transaction SHDB and create a

simple processing function module from that recording.

Outbound routines are called by the triggering application, e.g. the RSNAST00

program.

Inbound processing is triggered by the central IDoc inbound handler, which is

usually the function module IDOC_INPUT . This function is usually activated by

the gatekeeper who receives the IDoc.

Outbound is triggered by the application.

Inbound is triggered by an external event.

The most difficult work when creating outbound IDocs is the retrieval of the application data which needs sending. Once the data is retrieved, it needs to be converted to IDoc format, only.

Each R/3 standard text element has a header record which is stored in table STXH.

The text lines themselves are stored in a special cluster table. To retrieve the text

from the cluster, you will use the standard function module function

READ_TEXT.

The program below will retrieve a text document from the text pool, convert the text

lines into IDoc format, and create the necessary control information.

The first step is reading the data from the application database by calling the

function module READ_TEXT.

Our next duty is to pack the data into the IDoc record. This means moving the

application data to the data part of the IDoc record structure EDIDD and filling the

corresponding segment information.

Finally, we have to provide a correctly filled control record for this IDoc. If the IDoc routine is used in a standard automated environment, it is usually sufficient to fill the field EDIDC-IDOCTP with the IDoc type, EDIDC-MESTYP with the context

message type and the receiver name. The remaining fields are automatically filled

by the standard processing routines if applicable.

Inbound processing is basically the reverse process of an outbound.. The received IDoc has to be unpacked, interpreted and transferred to an application for further processing.

The received IDoc data is processed record by record and data is sorted out according to the segment type.

When the IDoc is unpacked data is passed to the application.

Finally the processing routine needs to pass a status record to the IDoc processor.

This status indicates successful or unsuccessful processing and will be added as a

log entry to the table EDIDS.

The status value '51' indicates a general error during application processing and the

status '53' indicates everything is OK.

Example Code:

This is an individual coding part where you need to retrieve the information from the database and prepare it in the form the recipient of the IDoc will expect the data.

Read data to send :

The first step is reading the data from the database, the one you want to send.

FUNCTION Y_AXX_COOKBOOK_TEXT_IDOC_OUTB.

*"----

""Lokale Schnittstelle:

*" IMPORTING

*" VALUE(I_TDOBJECT) LIKE THEAD-TDOBJECT DEFAULT 'TEXT'

*" VALUE(I_TDID) LIKE THEAD-TDID DEFAULT 'ST'

*" VALUE(I_TDNAME) LIKE THEAD-TDNAME

*" VALUE(I_TDSPRAS) LIKE THEAD-TDSPRAS DEFAULT SY-LANGU

*" EXPORTING

*" VALUE(E_THEAD) LIKE THEAD STRUCTURE THEAD

*" TABLES

*" IDOC_DATA STRUCTURE EDIDD OPTIONAL

*" IDOC_CONTRL STRUCTURE EDIDC OPTIONAL

*" TLINES STRUCTURE TLINE OPTIONAL

*" EXCEPTIONS

*" FUNCTION_NOT_EXIST

*" VERSION_NOT_FOUND

*"----

CALL FUNCTION 'READ_TEXT'

EXPORTING

ID = ID

LANGUAGE = LANGUAGE

NAME = NAME

OBJECT = OBJECT

TABLES

LINES = LINES.

now stuff the data into the Idoc record format

PERFORM PACK_LINE TABLES IDOC_DATA USING 'THEAD' E_THEAD.

LOOP AT LINES.

PERFORM PACK_LINE TABLES IDOC_DATA USING 'THEAD' LINES.

ENDLOOP.

ENDFUNCTION.

Converting Data into IDoc Segment Format :

The physical format of the IDocs records is always the same. Therefore, the application data must be converted into a 1000 character string.

Fill the data segments which make up the IDoc :

An IDoc is a file with a rigid formal structure. This allows the correspondents to

correctly interpret the IDoc information. Were it for data exchange between SAPsystems only, the IDoc segments could be simply structured like the correspondent

DDIC structure of the tables whose data is sent.

However, IDocs are usually transported to a variety of legacy systems which do not

run SAP. Both correspondents therefore would agree on an IDoc structure which is

known to the sending and the receiving processes.

Transfer the whole IDoc to an internal table, having the structure of EDIDD :

All data needs to be compiled in an internal table with the structure of the standard

SAP table EDIDD. The records for EDIDD are principally made up of a header

string describing the segment and a variable length character field (called SDATA)

which will contain the actual segment data.

FORM PACK_LINE TABLES IDOC_DATA USING 'THEAD' E_THEAD.

TABLES: THEAD.

MOVE-CORRESPONDING E:THEAD to Z1THEAD.

MOVE ‚Z1THEAD’ TO IDOC_DATA-SEGNAM.

MOVE Z1THEAD TO IDOC_DATA-SDATA.

APPEND IDOC_DATA.

ENDFORM.“

Fill control record :

Finally, the control record has to be filled with meaningful data, especially telling

the IDoc type and message type.

IF IDOC_CONTRL-SNDPRN IS INITIAL.

SELECT SINGLE * FROM T000 WHERE MANDT EQ SY-MANDT.

MOVE T000-LOGSYS TO IDOC_CONTRL-SNDPRN.

ENDIF.

IDOC_CONTRL-SNDPRT = 'LS'.

Trans we20 -> Outbound Controls muss entsprechend gesetzt werden.
2 = Transfer IDoc immediately
4 = Collect IDocs

IDOC_CONTRL-OUTMOD = '2'. "1=imediately, subsystem

CLEAR IDOC_CONTRL.

IDOC_CONTRL-IDOCTP = 'YAXX_TEXT'.

APPEND IDOC_CONTRL.

Thanks,

Sandeep.

Re: Outbound

Former Member — Wed, 12 Mar 2008 11:07:53 GMT

hi,

Below is a sample outbound IDOC generation program.

to extract two fields from a Z table - 'zvista_pm_t' . This table has to be created in ur R/3 system.

REPORT zgbsend_idoc .

CONSTANTS: c_mestyp TYPE edidc-mestyp VALUE 'ZVISTAPM',

c_doctyp TYPE edidc-idoctp VALUE 'ZVISTAPM01',

c_segnam TYPE edidd-segnam VALUE 'Z1VISTAPM'.

DATA: i_zvista_pm TYPE ZVISTA_PM_T OCCURS 6000,

i_edidc TYPE edidc OCCURS 0,

i_edidd TYPE edidd OCCURS 0,

wa_zvista_pm TYPE zvista_pm_t,

wa_edidc TYPE edidc,

wa_edidd TYPE edidd,

wa_z1vistapm TYPE z1vistapm,

v_occmax TYPE idocsyn-occmax,

v_nbseg TYPE i.

CLEAR wa_zvista_pm.CLEAR wa_edidc.

Save the message type and the basic IDoc type* in the control segment

MOVE c_mestyp TO wa_edidc-mestyp.MOVE c_doctyp TO wa_edidc-idoctp.

*Retrieve the maximum number of segments in the basic IDoc type

SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.

Save the whole ZVISTA_PM_T table content in the I_ZVISTA_PM internal table.

SELECT * from zvista_pm_t into corresponding fields of table i_zvista_pm.

*Create a data segment for each line of I_ZVISTA_PM

LOOP AT i_zvista_pm INTO wa_zvista_pm.

MOVE-CORRESPONDING wa_zvista_pm TO wa_z1vistapm.

CLEAR wa_edidd.

MOVE c_segnam TO wa_edidd-segnam.

MOVE wa_z1vistapm TO wa_edidd-sdata.

APPEND wa_edidd TO i_edidd.

CLEAR wa_zvista_pm.

CLEAR wa_z1vistapm.

ENDLOOP.

*Count the number of data segments

DESCRIBE TABLE i_edidd LINES v_nbseg.

IF the NUMBER of DATA segments EXCEEDS the MAXIMUM* allowed NUMBER, then edit a message in the spool,* then display an error message (quit the program)

if v_nbseg gt v_occmax.

WRITE:/ text-003, v_occmax.

MESSAGE 'Data Segments exceeds its maximun number' type 'E'.

ENDIF.

CALL the idoc creation function

call function 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

master_idoc_control = wa_edidc

TABLES

communication_idoc_control = i_edidc

master_idoc_data = i_edidd

EXCEPTIONS

error_in_idoc_control = 1

error_writing_idoc_status = 2

error_in_idoc_data = 3

sending_logical_system_unknown = 4

OTHERS = 5.

If there was an error, display a message (quit the program)

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

*End of Program*

below check the link.

[IDOC creation Inbound and Outbound|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/step%2bby%2bstep%2bprocedure%2bfor%2bcreation%2bof%2bidoc]