Runtime error while calling BAPI_PO_CREATE1

[Former Member]

Hi All,

While calling the BAPI_PO_CREATE1 we are getting runtime error in our program.

This following error is coming in an standard include program called by BAPI.

"Type "/BEV1/NE_ITEM_PO" is unknown".

Here i am providing the details from Runtime Errors analysis.

Trigger Location of Runtime Error

Program /BEV1/CL_IM_NE_ME_PROC_PO=====CP

Include /BEV1/CL_IM_NE_ME_PROC_PO=====CM002

Row 11

Module type (METHOD)

Module Name IF_EX_ME_PROCESS_PO~OPEN

Line SourceCde

1 METHOD if_ex_me_process_po~open.

2

3 * Check whether Empties Management is active

4 CHECK is_empties_management_active( im_check_instance = mmpur_no ) =

5 mmpur_yes.

6

7 * Action only if not in display mode

8 IF im_trtyp <> gc_trtyp_disp.

9

10 * Instantiate Dependent Item Calculator

-> CREATE OBJECT gref_dic_po

12 EXPORTING

13 im_header = im_header.

14

15 ELSE.

16

17 CLEAR gref_dic_po.

18

19 ENDIF. " im_trtyp <> gc_trtyp_disp

20

21 ENDMETHOD.

Please give your valuable suggestions to overcome the error.

Regards,

Vinod

[Former Member]

Hi,

Please check in service market place for the relevant notes.

Possibly the support pack has not been applied correctly or a note has been applied incorrectly.

Regards,

Ankur Parab

[Former Member]

hai vinod as ur getting in standard program

just tryy to search a note for the same

may be u find some note for the same

afzal;

[Former Member]

Hi,

Please check in service market place for the relevant notes.

Possibly the support pack has not been applied correctly or a note has been applied incorrectly.

Regards,

Ankur Parab

[Former Member]

Hi Vinod,

While calling the BAPI - BAPI_PO_CREATE1, are you passing the following

For eg:

If you are filling the item details (POITEM), You need to pass the parameter POITEMX = 'X'

Likewise POSCHEDULE, You need to pass the corresponding parameter POSCHEDULEX = 'X'

Hope it helps!

Regards,

Sandhya

[Former Member]

Solved,some configuration problem in MM Empties Management check was causing the problem.