topic Re: Help in IDOC_INPUT_ORDERS Function module in Application Development and Automation Discussions

Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 08:13:05 GMT

Hi,

I am writing a program to generate an IDOC using IDOC_INPUT_ORDERS Function module .

But I am a little confused as to what has to be passed as input_method,mass_processing which are the import parameters of this function-module .

If anyone has a sample code program using function module IDOC_INPUT_ORDERS , please could you share it with me .

Regards,

Sushanth H.S.

Re: Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 08:24:59 GMT

Hi Sushanth,

IDOC_INPUT_ORDERS is a posting program.

This program uploads the idic to the database table.

Thatis it converts the idoc format to the SAP format.

I have created a sample posting program.

Please go through it.

&----

*& Report Z_FI_UTIL_EXCEL2GL_POSTING *

*& *

&----

*& *

&----

REPORT Z_FI_UTIL_EXCEL2GL_POSTING.

include <icon>.

*/ =================================================================== *

CONSTANTS: on VALUE 'X',

off VALUE ' ',

tabx TYPE X VALUE '09',

c_e1bpache08 TYPE edilsegtyp VALUE 'E1BPACHE08',

c_e1bpacgl08 TYPE edilsegtyp VALUE 'E1BPACGL08',

c_e1bpaccr08 TYPE edilsegtyp VALUE 'E1BPACCR08'.

TYPES: BEGIN OF t_tab_index,

from TYPE i,

to TYPE i,

END OF t_tab_index.

data : tab type c.

DATA:

e1bpache08 LIKE e1bpache08,

e1bpacgl08 LIKE e1bpacgl08,

e1bpaccr08 LIKE e1bpaccr08.

DATA: g_subrc TYPE subrc.

DATA: g_file TYPE string.

DATA: g_segname TYPE edilsegtyp.

DATA: g_sdata TYPE edi_sdata.

DATA: g_first_doc.

DATA: i_dataf TYPE char2000 OCCURS 900 WITH HEADER LINE,

i_dataf_doc TYPE char2000 OCCURS 50 WITH HEADER LINE.

DATA: g_tab_index TYPE t_tab_index OCCURS 100 WITH HEADER LINE.

DATA: i_accountgl TYPE bapiacgl08 OCCURS 100 WITH HEADER LINE,

i_curramnt TYPE bapiaccr08 OCCURS 100 WITH HEADER LINE,

i_return TYPE bapiret2 OCCURS 10 WITH HEADER LINE,

g_docheader TYPE bapiache08.

*/ ======================== SELECTION ================================ *

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-010.

PARAMETERS: excelf TYPE file_name LOWER CASE

DEFAULT 'C:\my_excel_file.txt'.

SELECTION-SCREEN END OF BLOCK b1.

*/ =========================== CORE ================================== *

START-OF-SELECTION.

*/ Call text File with GUI_UPLOAD

g_file = excelf.

CALL FUNCTION 'GUI_UPLOAD'

EXPORTING

filename = g_file

FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = ' '
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
IMPORTING
FILELENGTH =
HEADER =

TABLES

data_tab = i_dataf

EXCEPTIONS

file_open_error = 1

file_read_error = 2

no_batch = 3

gui_refuse_filetransfer = 4

invalid_type = 5

no_authority = 6

unknown_error = 7

bad_data_format = 8

header_not_allowed = 9

separator_not_allowed = 10

header_too_long = 11

unknown_dp_error = 12

access_denied = 13

dp_out_of_memory = 14

disk_full = 15

dp_timeout = 16

OTHERS = 17

IF sy-subrc <> 0.

write: / Text-032.

stop.

ENDIF.

*/ Initialisation

write tabx to tab. " required as of ABAP 610 split cannot

*/ have mixed char and byte types

CLEAR g_tab_index.

REFRESH g_tab_index.

*/ how to process several doc : detecting docs in i_dataf

g_first_doc = on.

LOOP AT i_dataf.

CLEAR: g_segname, g_sdata.

SPLIT i_dataf AT tab INTO g_segname g_sdata.

CHECK: g_segname = c_e1bpache08,

sy-tabix > 1.

*/ 1st document

IF g_first_doc = on.

g_tab_index-from = 1.

g_tab_index-to = sy-tabix - 1.

APPEND g_tab_index.

*/ Next Documents

ELSE.

g_tab_index-from = g_tab_index-to + 1.

g_tab_index-to = sy-tabix - 1.

APPEND g_tab_index.

ENDIF.

g_first_doc = off.

ENDLOOP.

*/ Last doc.

g_tab_index-from = g_tab_index-to + 1.

g_tab_index-to = sy-tfill.

APPEND g_tab_index.

*/ Process documents.

loop at g_tab_index.

clear i_dataf_doc.

refresh i_dataf_doc.

append lines of i_dataf from g_tab_index-from

to g_tab_index-to

to i_dataf_doc.

perform process_document.

endloop.

END-OF-SELECTION.

*/ =========================== ROUTINES ============================== *

----

FORM process_document *

----

........ *

----

FORM process_document.

*/ Clearing Memory

CLEAR: g_docheader, i_accountgl, i_curramnt, i_return, g_subrc.

REFRESH: i_accountgl, i_curramnt, i_return.

*/ Checking i_dataf_doc

*/ Mapping dataf => Bapi structures & internal tables

CLEAR g_subrc.

CATCH SYSTEM-EXCEPTIONS conversion_errors = 1.

LOOP AT i_dataf_doc.

CLEAR g_sdata.

SPLIT i_dataf_doc AT tab INTO g_segname g_sdata.

CASE g_segname.

*/ HEADER

WHEN c_e1bpache08.

PERFORM do_split_ache08.

MOVE-CORRESPONDING e1bpache08 TO g_docheader.

IF e1bpache08-doc_date IS INITIAL.

CLEAR g_docheader-doc_date.

ENDIF.

IF e1bpache08-pstng_date IS INITIAL.

CLEAR g_docheader-pstng_date.

ENDIF.

IF e1bpache08-trans_date IS INITIAL.

CLEAR g_docheader-trans_date.

ENDIF.

*/ Account GL

WHEN c_e1bpacgl08.

PERFORM do_split_acgl08.

MOVE-CORRESPONDING e1bpacgl08 TO i_accountgl.

IF e1bpacgl08-pstng_date IS INITIAL.

CLEAR i_accountgl-pstng_date.

ENDIF.

APPEND i_accountgl.

*/ Account Currency & Amounts

WHEN c_e1bpaccr08.

PERFORM do_split_accr08.

MOVE-CORRESPONDING e1bpaccr08 TO i_curramnt.

APPEND i_curramnt.

*/ kick the line if segment name not filled

WHEN space.

*/ Other names => Bad file structure !

WHEN OTHERS.

g_subrc = 2.

ENDCASE.

ENDLOOP. " i_dataf_doc

ENDCATCH.

*/ erreur d'affectation

IF sy-subrc = 1 OR

NOT g_subrc IS INITIAL.

perform message_output using on.

exit.

ENDIF.

*/ Calling the BAPI

CALL FUNCTION 'BAPI_ACC_GL_POSTING_POST'

EXPORTING

documentheader = g_docheader

IMPORTING
OBJ_TYPE =
OBJ_KEY =
OBJ_SYS =

TABLES

accountgl = i_accountgl

currencyamount = i_curramnt

return = i_return

EXTENSION1 =

LOOP AT i_return WHERE type CA 'AE'.

g_subrc = 1.

EXIT.

ENDLOOP.

IF NOT g_subrc IS INITIAL.

perform message_output using on.

ELSE.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING
WAIT =
IMPORTING
RETURN =

perform message_output using off.

ENDIF.

ENDFORM.

&----

*& Form do_split_ACHE08

&----

text

----

--> p1 text
<-- p2 text

----

FORM do_split_ache08.

CLEAR e1bpache08.

SPLIT g_sdata AT tab INTO

e1bpache08-obj_type

e1bpache08-obj_key

e1bpache08-obj_sys

e1bpache08-username

e1bpache08-header_txt

e1bpache08-obj_key_r

e1bpache08-comp_code

e1bpache08-ac_doc_no

e1bpache08-fisc_year

e1bpache08-doc_date

e1bpache08-pstng_date

e1bpache08-trans_date

e1bpache08-fis_period

e1bpache08-doc_type

e1bpache08-ref_doc_no

e1bpache08-compo_acc

e1bpache08-reason_rev

ENDFORM. " do_split_ACHE08

&----

*& Form do_split_ACGL08

&----

text

----

--> p1 text
<-- p2 text

----

FORM do_split_acgl08.

CLEAR e1bpacgl08.

SPLIT g_sdata AT tab INTO

e1bpacgl08-itemno_acc

e1bpacgl08-gl_account

e1bpacgl08-comp_code

e1bpacgl08-pstng_date

e1bpacgl08-doc_type

e1bpacgl08-ac_doc_no

e1bpacgl08-fisc_year

e1bpacgl08-fis_period

e1bpacgl08-stat_con

e1bpacgl08-ref_key_1

e1bpacgl08-ref_key_2

e1bpacgl08-ref_key_3

e1bpacgl08-customer

e1bpacgl08-vendor_no

e1bpacgl08-alloc_nmbr

e1bpacgl08-item_text

e1bpacgl08-bus_area

e1bpacgl08-costcenter

e1bpacgl08-acttype

e1bpacgl08-orderid

e1bpacgl08-orig_group

e1bpacgl08-cost_obj

e1bpacgl08-profit_ctr

e1bpacgl08-part_prctr

e1bpacgl08-wbs_element

e1bpacgl08-network

e1bpacgl08-routing_no

e1bpacgl08-order_itno

ENDFORM. " do_split_ACGL08

&----

*& Form do_split_ACCR08

&----

text

----

--> p1 text
<-- p2 text

----

FORM do_split_accr08.

data: l_filler(100).

CLEAR e1bpaccr08.

SPLIT g_sdata AT tab INTO

e1bpaccr08-itemno_acc

e1bpaccr08-curr_type

e1bpaccr08-currency

e1bpaccr08-currency_iso

e1bpaccr08-amt_doccur

e1bpaccr08-exch_rate

e1bpaccr08-exch_rate_v

l_filler

ENDFORM. " do_split_ACCR08

&----

*& Form message_output

&----

text

----

--> p1 text
<-- p2 text

----

FORM message_output using if_error.

data: l_message(200),

l_return type i.

format color 1.

skip.

write: / text-020, g_tab_index-from,

text-021, g_tab_index-to.

skip.

if if_error = on.

write: / icon_red_light as icon, text-030 color 6.

else.

write: / icon_green_light as icon, text-031 color 5.

endif.

describe table i_return lines l_return.

if l_return is initial.

write: / text-032.

endif.

loop at i_return.

CALL FUNCTION 'FORMAT_MESSAGE'

EXPORTING

ID = i_return-id

LANG = sy-langu

NO = i_return-number

V1 = i_return-MESSAGE_V1

V2 = i_return-MESSAGE_V2

V3 = i_return-MESSAGE_V3

V4 = i_return-MESSAGE_V4

IMPORTING

MSG = l_message

EXCEPTIONS

NOT_FOUND = 1

OTHERS = 2

check sy-subrc = 0.

write: / l_message.

endloop.

ENDFORM. " message_output

Tell me ur mailid. I will sen u more.

<b>Please reward if helpful.</b>

Re: Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 08:43:06 GMT

Hi Shori,

Thanks for showing your interest in helping me .

What i actually need is a program which uses the function-module IDOC_INPUT_ORDERS .I want to know what has to be given as values to the input parameters INPUT_METHOD and MASS_PROCESSING .

Also, I want to see how the tables IDOC_CONTRL,IDOC_DATA and IDOC_STATUS are being populated .

My mail-ID is Sushanth_hs@mindtree.com.You can send it to this mail address .

Regards,

Sushanth H.S.

Re: Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 09:02:31 GMT

Hi Sushanth,

There is no need for such a program.

If you want to see how the tables IDOC_CONTRL,IDOC_DATA and IDOC_STATUS are being populated.

Then go to WE19 ( idoc testing). and fill the necessary fields there ( the reference data you can take from an existing idoc.) and execute that in debugging mode.

Re: Help in IDOC_INPUT_ORDERS Function module

former_member404244 — Wed, 26 Sep 2007 09:10:31 GMT

Hi,

Please go through the below link for more information..

http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/content.htm

inorder to see the idoc data u have to use WE19 tcode.u have to specify teh sender and reciver information and populate the segments with ur values..Then press on Inbound function module in the application tool bar ,then give the FM "IDOC_INPUT_ORDERS",then choose the check box "CALL IN DEBUG MODE" and then choose the radio button "In foreground" and then press enter..it will take u to the FM and now u can see the values.

Regards,

Nagaraj

Re: Help in IDOC_INPUT_ORDERS Function module

varma_narayana — Wed, 26 Sep 2007 09:12:49 GMT

Hi...

Generally in the Inbound partner profile for message type ORDERS we have to assign the Process Code ORDE which points to this FM IDOC_INPUT_ORDERS. So this FM will be automatically called and the IDOC is posted in Database.

But what is the purpose of calling this from a program . can u verify that..?

<b>reward if Helpful.</b>

Re: Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 09:17:48 GMT

Dear Mandeep,

My requirement is that there are certain conditions have to be followed before posting the IDOC using function-module IDOC_INPUT_ORDERS .

For example,in the case of field BELNR under segment E1EDK01 ,it has to be checked first in table T9AGH.If it is existing,then we must add 10000000.

Secondly ,in segment E1EDK14 ,there are diff values of QUALF and ORGID in this segment .

So to meet these requirements,I am developing a program to generate an IDOC using the function module IDOC_INPUT_ORDERS Function module .But before that the tables int_edidd and int_edidc have to be populated .

Regards,

Sushanth H.S.

Re: Help in IDOC_INPUT_ORDERS Function module

Former Member — Wed, 26 Sep 2007 10:36:08 GMT

Hi,

For your requirement, you have to find the enhancement points in the FM and write you logic there.

If you are unable to find the enhancement points at the position you want then you have to go with copying the entire FM into a new Z function moudle.

The first approach is recommended.