IDOC creation after the creation of a purchase ord...

Application Development Discussions

Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.

Hi everybody,

I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,

Santosh.

SAP Managed Tags:
ABAP Connectivity

2 REPLIES 2

hi santosh kumar,

Creating an IDoc Segment WE31:

The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.

We will define a structure to send a text from the text database.

Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a

single segment structure. The thus defined IDoc segment is then created as a data

dictionary structure. You can view the created structure with SE11 and use it in an

ABAP as any TABLES declaration.

To demonstrate the use of the IDoc segment editor we will set up an example, which

allows you to send a single text from the text pool (tables STXH and STXL) as an

IDoc. These are the texts that you can see with SO10 or edit from within many

applications.

We will show the steps to define an IDoc segment YAXX_THEAD with the DDic

structure of THEAD.

To facilitate our work, we will use the "copy-from-template-tool", which reads the

definition of a DDIC structure and inserts the field and the matching definitions as

rows in the IDoc editor. You could, of course, define the structure completely

manually, but using the template makes it easier.

The tool in release 4.0b lets you use both DDIC structures or another IDoc segment

definition as a template.

The thus created structure can be edited any time. When saving, it will create a data

dictionary structure based on the definition in WE31. The DDIC structure will retain

the same name. You can view the structure as a table definition with SE11 and use it

in an ABAP the same way.

Defining the Message Type (EDMSG)

The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.

Imagine the situation of sending a purchase order to a supplier. When the IDoc with

the purchase order reaches the supplier, it will be interpreted as a sales order

received from a customer, namely you.

Simultaneously you want to send the IDoc data to the supplier's warehouse to inform

it that a purchase order has been issued and is on the way.

Both IDoc receivers will receive the same IDoc format; however, the IDoc will be

tagged with a different message type. While the IDoc to the supplier will be flagged

as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc

sent to the warehouse should be flagged differently, so that the warehouse can

recognize the order as a mere informational copy and process it differently than a

true purchase order.

The message type together with the IDoc type determine the processing function.

The message types are stored in table EDMSG.

Defining the message type can be done from the transaction WEDI

EDMSG: Defining the message type (1)

The entry is only a base entry which tells the system that the message type is

allowed. Other transactions will use that table as a check table to validate the entry.

IT is as shown .

EDMSG: Defining the message type (1):

The entry is only a base entry which tells the system that the message type is

allowed. Other transactions will use that table as a check table to validate the entry.

Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.

Requirement:

Processing:

The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.

sampl code:

REPORT Z_EDI_FILE_LOAD_STATUS_REPORT .

*----

Staus Report for Inbound IDOCs ( Sales Orders )

*----

Program : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By : www.rmtiwari.com

*----

TABLES : EDIDC.

*----

ALV stuff

TYPE-POOLS: SLIS.

DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,

GS_LAYOUT TYPE SLIS_LAYOUT_ALV,

GT_SORT TYPE SLIS_T_SORTINFO_ALV,

GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.

DATA : BEGIN OF T_REPORT OCCURS 0,

IDOC_NO TYPE EDI_DOCNUM,

IDOC_DATE TYPE SY-DATUM,

IDOC_TIME TYPE SY-UZEIT,

SORDER_NO TYPE VBELN,

STP_NO TYPE KNA1-KUNNR,

STP_NAME(35) TYPE C,

STP_PHONE(12) TYPE C,

PO_NO(15) TYPE C,

STATUS TYPE C,

S_TEXT(70) TYPE C,

ERROR(70) TYPE C,

END OF T_REPORT.

PARAMETER--

selection-screen begin of block date with frame title TEXT-S01.

select-options: UDATE for EDIDC-UPDDAT

default SY-datum obligatory, "Changed On

UTIME for EDIDC-UPDTIM . "Changed Time

selection-screen end of block date.

----

INITIALIZATION.

START-OF-SELECTION.

PERFORM SHOW_STATUS_REPORT.

&----

*& Form alv_grid

&----

text

----

--> p1 text
< -- p2 text

----

FORM ALV_GRID.

IF GT_FIELDCAT[] IS INITIAL.

PERFORM FIELDCAT_INIT.

PERFORM LAYOUT_INIT.

PERFORM SORT_INIT.

ENDIF.

PERFORM GRID_DISPLAY.

ENDFORM. "alv_grid

&----

*& Form layout_init

&----

FORM LAYOUT_INIT.

GS_LAYOUT-ZEBRA = 'X'.

GS_LAYOUT-CELL_MERGE = 'X'.

GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.

GS_LAYOUT-NO_VLINE = ' '.

GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.

ENDFORM. " layout_init

&----

*& Form fieldcat_init

&----

FORM FIELDCAT_INIT.

DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.

CLEAR LS_FIELDCAT.

LS_FIELDCAT-FIELDNAME = 'IDOC_NO'.

LS_FIELDCAT-KEY = 'X'.

LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.

LS_FIELDCAT-OUTPUTLEN = 10.

Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.

LS_FIELDCAT-INTTYPE = 'N'.