Migo doubt

Hi All
i am doing MIGO for trading goods (HAWA) & operating Supplies getting errors as follows
1. Special G/L account indicator is not defined or in correct ?
while doing MRP for above material getting error as
2. automatic MRP not defined in your comapany code ?
thanks in advance to all

i am doing MIGO for trading goods (HAWA) & operating Supplies getting errors as follows
1. Special G/L account indicator is not defined or in correct ?
Make sure that for this mateial the valuation class has defined in the material master
while doing MRP for above material getting error as
2. automatic MRP not defined in your comapany code ?
Make sure that the MRP view is maintained for this material.
Both material type should be maintained for qty and value update in the Material type config.

Similar Messages

Doubt Regarding MIGO Transaction

Hi,
Where exactly the source code of MIGO transaction fills these two fields : BED , SED (Note: Under the Tab Excise Invoice).
Thanks & Regards,
Lakshmi.

ok

Doubt Regarding MIGO

Hi,
Where exactly the source code of MIGO transaction fills these two fields : BED , SED (Note: Under the Tab Excise Invoice). What are the Exact Tables in MIGO.
Thanks & Regards,
Lakshmi.

hi
u can get the detail in J_1IEXCDTL table ,
but its better to calculate this with help of condition type .
regards
digvijay rai

Doubt in MIGO user exit

Hi all,
my requirement is "whenever the user is performing the MIGO transaction and presses the post button,i have to populate all the values what ever the user is entering along with the MBLNR (material document number) field and also to populate somemore fields from 2 ztables and post it into IDOCs".
For this i have found the userexit which is MBCF0002.
Im getting all the fields values, what ever the user is entering but for the MBLNR (material document number) field its blank. The reason for this is , only after the successful movement of the material MBLNR field will be generated.
so ,
To be Reward all helpfull answers.
Regards.
Jay

Hi,
You need to use a user exit which is getting triggered only after material document no has been generated. You may use INCLUDE ZXMBCU01 of EXIT_SAPLMBMB_001. Please note that this exit is getting executed whenever a material document is generated by the system. Hence you need to check your specific tran code+reason code. Please also note that if at all you need to debug this exit, just put /h in command box just before pressing post & then settings---->update debugging shystem should give you the message update debugging has been switched on. You need to ensure this since it's a toggle.
I hope this helps,
Regrads
Raju Chitale

Doubt reg: MIGO GR/IR Reclass accounting entries

Hi ,
When MIGO is done , we have the below accounting entries.
Stock a/c - Dr
GR/IR clg a/c - Cr
On month end when we run F.19 , if MIGO is done and MIRO is not done,
the accounting entry is
GR/IR Adjustment a/c DR
GR/IR clg a/c - Cr
Is this correct?
Because the purpose of running F.19 is to reclassify the balances in GR/IR clg a/c to
GR/IR Adjustment a/c.
But as per the above entries, the GR/IR clg a/c, is credited twice.
Please explain, where I am getting the flow wrong.

Hi Rudra,
When MIGO is done , the below accounting entry is posted
Stock a/c - Dr
GR/IR clg a/c - Cr
Now, when you run F.19, then, based on whether the MIGO is done and IR is not done and IR is done but MIGO is not done, the entries would get posted.
Please remember, the entries are only mirror entries of GR/IR Account and no posting is made to GR/IR Account.
Note the scheme of entries below:-
Delivered but Not Invoiced:-
GR/IR Adjustment A/C..Dr
To Provision Account (GNB)
Invoiced but not yet Delivered:-
Claims A/C...Dr(BNG)
To GR/IR Adjustment A/c
The GR/IR Adjustment Account and GR/IR Account can be clubbed together in the FSV, so the effect gets nullified.. and the actual Claim or liability is shown in the specific GL's like provision (GNB) and Claims(BNG).
The entries also gets reversed the next month.. so this reclassification is for reporting purpose only. And then it is business as usual..
Hope this helps you..
Regards,
SAPFICO

Doubt in calltransaction in ALV

Hi, i have doubt in calltransction in alv..In my report am using ALV grid display to display purchase order number , material docu number ..If i click on purchasing docu number it has to call transaction ME23N for the purchase order number that i have clicked and if i click material document number it has to call trainsaction MIGO for the corresponding material document number..Here i have done some coding plz correct me if iam wrong..
*& Report YCALLTRANSACTIONALV *
REPORT YCALLTRANSACTIONALV .
TYPE-POOLS: icon.
TYPE-POOLS: slis.
TABLES: vbak,vbap,vbep, makt,lips.
DATA: BEGIN OF gt_vbak OCCURS 0,
vbeln LIKE vbak-vbeln,
audat LIKE vbak-audat,
vdatu LIKE vbak-vdatu,
kunnr LIKE vbak-kunnr,
posnr LIKE vbap-posnr,
matnr LIKE vbap-matnr,
kwmeng LIKE vbap-kwmeng,
END OF gt_vbak.
DATA: BEGIN OF gt_vbep OCCURS 0,
vbeln LIKE vbep-vbeln,
wadat LIKE vbep-wadat,
END OF gt_vbep.
DATA: BEGIN OF gt_lips OCCURS 0,
vbeln LIKE lips-vbeln,
posnr LIKE lips-posnr,
lfimg LIKE lips-lfimg,
vgbel LIKE lips-vgbel,
vgpos LIKE lips-vgpos,
END OF gt_lips.
DATA: BEGIN OF gt_makt OCCURS 0,
matnr LIKE makt-matnr,
maktx LIKE makt-maktx,
END OF gt_makt.
DATA: gv_tab TYPE slis_tabname VALUE 'GT_REPORT'.
DATA: BEGIN OF gt_report OCCURS 0,
vbeln LIKE vbak-vbeln,
posnr LIKE vbep-posnr,
matnr LIKE vbap-matnr,
maktx LIKE makt-maktx,
kwmeng LIKE vbap-kwmeng,
vdatu LIKE vbak-vdatu,
lfimg LIKE lips-lfimg,
wadat LIKE vbep-wadat,
vgbel LIKE lips-vgbel,
icon TYPE icon-id,
tabcolor TYPE lvc_t_scol,
END OF gt_report.
DATA: gt_fieldcat TYPE slis_t_fieldcat_ alv,
 gs_fieldcat TYPE slis_fieldcat_ alv,
 gs_layout TYPE slis_layout_ alv,
 gt_events TYPE slis_t_event,
 gs_events TYPE slis_alv_event,
repid LIKE sy-repid.
DATA: gt_lines TYPE TABLE OF tline WITH HEADER LINE,
gv_name LIKE thead-tdname,
gv_fld(40),gv_ fval(50).
DATA: BEGIN OF gt_outlines OCCURS 0,
text TYPE tdline,
END OF gt_outlines.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-006.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_cust RADIOBUTTON GROUP rad1 USER-COMMAND ch DEFAULT 'X'.
SELECTION-SCREEN COMMENT 5(20) text-001.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_date RADIOBUTTON GROUP rad1 .
SELECTION-SCREEN COMMENT 5(10) text-002 .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-005.
SELECT-OPTIONS: s_sale FOR vbak-vbeln MODIF ID cus,
s_cust FOR vbak-kunnr MODIF ID cus.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-005.
SELECT-OPTIONS: s_sale1 FOR vbak-vbeln MODIF ID dat,
s_dat FOR vbak-audat MODIF ID dat.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN END OF BLOCK b3.
SELECTION-SCREEN BEGIN OF BLOCK b4 WITH FRAME TITLE text-007.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_clas RADIOBUTTON GROUP rad2 ."USER-COMMAND ch DEFAULT'X'.
SELECTION-SCREEN COMMENT 5(20) text-003.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_alv RADIOBUTTON GROUP rad2 ."USER-COMMAND ch DEFAULT'X'.
SELECTION-SCREEN COMMENT 5(20) text-004.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b4.
AT SELECTION-SCREEN.
CHECK sy-ucomm = 'CH'.
AT SELECTION-SCREEN OUTPUT.
IF p_cust = 'X'.
LOOP AT SCREEN.
IF screen-group1 = 'DAT'.
screen-active = 0.
ELSE.
screen-active = 1.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
ELSE.
LOOP AT SCREEN.
IF screen-group1 = 'CUS'.
screen-active = 0.
ELSE.
screen-active = 1.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
START-OF-SELECTION.
IF p_cust = 'X' .
CLEAR gt_vbak.
REFRESH gt_vbak.
SELECT avbeln aaudat avdatu akunnr bposnr bmatnr b~kwmeng
INTO TABLE gt_vbak
FROM vbak AS a INNER JOIN vbap AS b
ON avbeln = bvbeln
WHERE a~vbeln IN s_sale
AND a~kunnr IN s_cust.
ELSEIF p_date = 'X'.
CLEAR gt_vbak.
REFRESH gt_vbak.
SELECT avbeln aaudat avdatu akunnr bposnr bmatnr b~kwmeng
INTO TABLE gt_vbak
FROM vbak AS a INNER JOIN vbap AS b
ON avbeln = bvbeln
WHERE a~vbeln IN s_sale1
AND a~audat IN s_dat.
ENDIF.
PERFORM sel_data.
IF p_alv = 'X'.
PERFORM disp_data1.
ELSE.
PERFORM disp_data.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD gv_fld .
CASE gv_fld.
WHEN 'ICON_DISPLAY_ TEXT'.
PERFORM concate_text.
CLEAR gv_name.
CONCATENATE gt_report-vbeln gt_report-posnr INTO gv_name.
PERFORM read_text.
PERFORM write_text.
PERFORM disp_text.
WHEN 'GT_REPORT-VBELN' .
SET PARAMETER ID 'AUN' FIELD gt_report-vbeln.
CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN.
ENDCASE.
*& Form sel_data
FORM sel_data .
CLEAR gt_vbep.
REFRESH gt_vbep.
IF NOT gt_vbak[] IS INITIAL.
SELECT vbeln wadat FROM vbep INTO TABLE gt_vbep
FOR ALL ENTRIES IN gt_vbak
WHERE vbeln = gt_vbak-vbeln.
CLEAR gt_lips.
REFRESH gt_lips.
SELECT vbeln posnr lfimg vgbel vgpos FROM lips INTO TABLE gt_lips
FOR ALL ENTRIES IN gt_vbak
WHERE vgbel = gt_vbak-vbeln
AND vgpos = gt_vbak-posnr.
CLEAR gt_makt.
REFRESH gt_makt.
SELECT matnr maktx FROM makt INTO TABLE gt_makt
FOR ALL ENTRIES IN gt_vbak
WHERE matnr = gt_vbak-matnr.
ENDIF.
REFRESH gt_report.
CLEAR gt_report.
LOOP AT gt_vbak.
gt_report-vbeln = gt_vbak-vbeln.
gt_report-vdatu = gt_vbak-vdatu.
gt_report-posnr = gt_vbak-posnr.
gt_report-matnr = gt_vbak-matnr.
gt_report-kwmeng = gt_vbak-kwmeng.
CLEAR gt_vbep.
READ TABLE gt_vbep WITH KEY vbeln = gt_vbak-vbeln.
gt_report-wadat = gt_vbep-wadat.
CLEAR gt_lips.
READ TABLE gt_lips WITH KEY vgbel = gt_vbak-vbeln
vgpos = gt_vbak-posnr.
gt_report-lfimg = gt_lips-lfimg.
gt_report-vgbel = gt_lips-vbeln.
CLEAR gt_makt.
READ TABLE gt_makt WITH KEY matnr = gt_vbak-matnr.
gt_report-maktx = gt_makt-maktx.
CLEAR gt_report-icon.
PERFORM concate_text.
CLEAR gv_name.
CONCATENATE gt_report-vbeln gt_report-posnr INTO gv_name.
PERFORM read_text.
IF gt_lines[] IS NOT INITIAL.
gt_report-icon = '@0P@'.
ENDIF.
APPEND gt_report.
ENDLOOP.
ENDFORM. " sel_data
*& Form disp_data
FORM disp_data .
WRITE:/(8) 'orderno.',
(8) 'lineno.',
(11) 'mat.',
(27) 'matdes.',
(10) 'ord.qty',
(12) 'req.del.',
(10) 'del.qty',
(10) 'gidate',
(10) 'delno.'.
ULINE.
LOOP AT gt_report.
WRITE:/(8) gt_report-vbeln COLOR 6 HOTSPOT,
(8) gt_report-posnr ,
(8) gt_report-matnr,
(25) gt_report-maktx,
(11) gt_report-kwmeng,
(15) gt_report-vdatu,
(7) gt_report-lfimg,
(10) gt_report-wadat,
(10) gt_report-vgbel.
PERFORM concate_text.
CLEAR gv_name.
CONCATENATE gt_report-vbeln gt_report-posnr INTO gv_name.
PERFORM read_text.
IF gt_lines[] IS NOT INITIAL.
WRITE:120 icon_display_ text AS ICON HOTSPOT.
HIDE: gt_report-vbeln, gt_report- posnr.
ENDIF.
ENDLOOP.
ENDFORM. " disp_data
*& Form disp_data1
FORM disp_data1 .
DATA :
ls_tabcolor TYPE lvc_s_scol.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'VBELN'.
gs_fieldcat- hotspot = 'X'.
gs_fieldcat- seltext_l = 'ORDERNO'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'POSNR'.
gs_fieldcat- seltext_l = 'LINENO'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'MATNR'.
gs_fieldcat- seltext_l = 'MATNO'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'MAKTX'.
gs_fieldcat- seltext_l = 'MATDESCR'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'KWMENG'.
gs_fieldcat- seltext_l = 'ORDERQTY'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'VDATU'.
gs_fieldcat- seltext_l = 'REQ.DEL.DAT' .
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'LFIMG'.
gs_fieldcat- seltext_l = 'QTY.DEL'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'WADAT'.
gs_fieldcat- seltext_l = 'ISS.DATE'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'VGBEL'.
gs_fieldcat- seltext_l = 'DOUC.NO'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat- tabname = gv_tab.
gs_fieldcat- fieldname = 'ICON'.
gs_fieldcat- seltext_l = 'TEXT'.
gs_fieldcat- icon = 'X'.
gs_fieldcat- hotspot = 'X'.
APPEND gs_fieldcat TO gt_fieldcat.
gs_layout-coltab_ fieldname = 'TABCOLOR'.
gs_events-name = 'USER_COMMAND' .
gs_events-form = 'VAL'.
APPEND gs_events TO gt_events.
LOOP AT gt_report.
ls_tabcolor- fname = 'VBELN'.
ls_tabcolor- color-col = 4.
ls_tabcolor- color-int = 1.
ls_tabcolor- color-inv = 0.
INSERT ls_tabcolor INTO TABLE gt_report-tabcolor.
MODIFY gt_report.
ENDLOOP.
CALL FUNCTION 'REUSE_ALV_GRID_ DISPLAY'
EXPORTING
i_callback_program = sy-repid
is_layout = gs_layout
it_fieldcat = gt_fieldcat
it_events = gt_events
TABLES
t_outtab = gt_report.
ENDFORM. " disp_data1
*& Form READ_TEXT .
FORM read_text .
CLEAR gt_lines.
REFRESH gt_lines.
CALL FUNCTION 'READ_TEXT'
EXPORTING
id = '0002'
language = sy-langu
name = gv_name
object = 'VBBP'
TABLES
lines = gt_lines
EXCEPTIONS
id = 1
language = 2
name = 3
not_found = 4
object = 5
reference_check = 6
wrong_access_ to_archive = 7
OTHERS = 8.
IF sy-subrc <> 0.
ENDIF.
ENDFORM. " READ_TEXT
*& Form WRITE_TEXT.
FORM write_text.
REFRESH gt_outlines.
CLEAR gt_outlines.
CLEAR gt_lines.
LOOP AT gt_lines .
MOVE gt_lines-tdline TO gt_outlines- text .
APPEND gt_outlines.
ENDLOOP.
CLEAR gt_outlines.
ENDFORM. "WRITE_TEXT
*& Form VAL .
FORM val USING
user_command LIKE sy-ucomm
sel TYPE slis_selfield.
IF sel-fieldname = 'VBELN'.
SET PARAMETER ID 'AUN' FIELD gt_report-vbeln.
CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN.
ENDIF.
IF sel-fieldname = 'ICON'.
CLEAR gt_report.
READ TABLE gt_report INDEX sel-tabindex.
perform concate_text.
CLEAR gv_name.
CONCATENATE gt_report-vbeln gt_report-posnr INTO gv_name.
PERFORM read_text.
PERFORM write_text.
PERFORM disp_text1.
ENDIF.
ENDFORM. "val
*& Form disp_text
FORM disp_text .
CALL FUNCTION 'POPUP_WITH_ TABLE_DISPLAY_ OK'
EXPORTING
endpos_col = 50
endpos_row = 30
startpos_col = 20
startpos_row = 20
titletext = 'TEXT'
TABLES
valuetab = gt_outlines.
ENDFORM. " disp_text
*& Form disp_text1
FORM disp_text1 .
DATA: lt_fieldcat TYPE slis_t_fieldcat_ alv,
ls_fieldcat TYPE slis_fieldcat_ alv.
ls_fieldcat- fieldname = 'TEXT'.
ls_fieldcat- outputlen = 40.
ls_fieldcat- tabname = gt_outlines.
APPEND ls_fieldcat TO lt_fieldcat.
CALL FUNCTION 'REUSE_ALV_POPUP_ TO_SELECT'
EXPORTING
i_title = 'TEXT'
i_tabname = 'TLINE'
it_fieldcat = lt_fieldcat
i_callback_program = sy-repid
TABLES
t_outtab = gt_outlines.
ENDFORM. " disp_text1
*& Form concate_text
FORM concate_text .
CLEAR gv_name.
CONCATENATE gt_report-vbeln gt_report-posnr INTO gv_name.
PERFORM read_text.
ENDFORM. " concate_text
Thanks

Hello skk
Here is a sample report performing the required task using OO-means. I think you will agree that the OO-based approach is much simpler and easier to understand than the FM-based approach.
The screen '0100' has the following flow logic without any dynpro elements:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
*& Report ZUS_SDN_ALVGRID_EVENTS
REPORT zus_sdn_alvgrid_events.
DATA:
gd_okcode TYPE ui_func,
gt_fcat TYPE lvc_t_fcat,
go_docking TYPE REF TO cl_gui_docking_container,
go_grid1 TYPE REF TO cl_gui_alv_grid.
DATA:
gt_knb1 TYPE STANDARD TABLE OF knb1.
PARAMETERS:
p_bukrs TYPE bukrs DEFAULT '1000' OBLIGATORY.
* CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
 CLASS-METHODS:
 handle_hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid
 IMPORTING
 e_row_id
 e_column_id
 es_row_no
 sender.
ENDCLASS. "lcl_eventhandler DEFINITION
* CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_hotspot_click.
* define local data
 DATA:
 ls_knb1 TYPE knb1,
 ls_col_id TYPE lvc_s_col.
 READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row_id-index.
 CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
 CASE e_column_id-fieldname.
 WHEN 'KUNNR'.
 SET PARAMETER ID 'KUN' FIELD ls_knb1-kunnr.
 SET PARAMETER ID 'BUK' FIELD ls_knb1-bukrs.
 CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
 WHEN 'ERNAM'.
* SET PARAMETER ID 'USR' FIELD ls_knb1-ernam.
* NOTE: no parameter id available, yet simply show the priciple
 CALL TRANSACTION 'SU01' AND SKIP FIRST SCREEN.
 WHEN OTHERS.
* do nothing
 ENDCASE.
* Set active cell to field BUKRS otherwise the focus is still on
* field KUNNR which will always raise event HOTSPOT_CLICK
 ls_col_id-fieldname = 'BUKRS'.
 CALL METHOD go_grid1->set_current_cell_via_id
 EXPORTING
 is_row_id = e_row_id
 is_column_id = ls_col_id.
ENDMETHOD. "handle_hotspot_click
ENDCLASS. "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
SELECT * FROM knb1 INTO TABLE gt_knb1
 WHERE bukrs = p_bukrs.
* Create docking container
CREATE OBJECT go_docking
 EXPORTING
 parent = cl_gui_container=>screen0
 ratio = 90
 EXCEPTIONS
 OTHERS = 6.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Create ALV grid
CREATE OBJECT go_grid1
 EXPORTING
 i_parent = go_docking
 EXCEPTIONS
 OTHERS = 5.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Set event handler
SET HANDLER:
 lcl_eventhandler=>handle_hotspot_click FOR go_grid1.
* Build fieldcatalog and set hotspot for field KUNNR
PERFORM build_fieldcatalog_knb1.
* Display data
CALL METHOD go_grid1->set_table_for_first_display
 CHANGING
 it_outtab = gt_knb1
 it_fieldcatalog = gt_fcat
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Link the docking container to the target dynpro
CALL METHOD go_docking->link
 EXPORTING
 repid = syst-repid
 dynnr = '0100'
* CONTAINER =
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* ok-code field = GD_OKCODE
CALL SCREEN '0100'.
END-OF-SELECTION.
*& Module STATUS_0100 OUTPUT
* text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
* text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
 WHEN 'BACK' OR
 'END' OR
 'CANC'.
 SET SCREEN 0. LEAVE SCREEN.
 WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form BUILD_FIELDCATALOG_KNB1
* text
* --> p1 text
* <-- p2 text
FORM build_fieldcatalog_knb1 .
* define local data
DATA:
 ls_fcat TYPE lvc_s_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
 EXPORTING
* I_BUFFER_ACTIVE =
 i_structure_name = 'KNB1'
* I_CLIENT_NEVER_DISPLAY = 'X'
* I_BYPASSING_BUFFER =
* I_INTERNAL_TABNAME =
 CHANGING
 ct_fieldcat = gt_fcat
 EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_fcat INTO ls_fcat
 WHERE ( fieldname = 'KUNNR' OR
 fieldname = 'ERNAM' ).
 ls_fcat-hotspot = abap_true.
 MODIFY gt_fcat FROM ls_fcat.
ENDLOOP.
ENDFORM. " BUILD_FIELDCATALOG_KNB1
Regards
Uwe

MIGO Is mandatery in Credit memo in 3rd party ?

Dear SD Experts ,
i know the 3rd party processing But i have One Doubt please explain me
2 Steps we have to do In Third part return process.
link tells
http://scn.sap.com/thread/987949
1 Flow to bring the stock from Customer is
va01 return order ( W/O Ref) --vl01n- Ref deli---MIGO ---VF01 ( Credit memo with ref to Return delivery )
2 Flow to Send the stock from company to vendor
ME21N( Ret PO )-- MIGO---MIRO ( Credit memo with ref to Ret po )
i know this flow is Right to credit memo in 3 Rd party But in both cases MIGO IS Mandatory or not ?
Second thing is TASG Is item category For credit memo in third party ..i have checked in VOV7
But i didnt understand this where i will insert /
Thanks a lot

Dear Madhuri ..
You mentioned is How to bring stock From Customer and sending to vendor Right
This is special process
Coming to TASG Item category , i have to tell you How credit memo is created in Third party process
I Am telling as per My knowledge
Now create credit memo ....Create credit memo Req ( G2) with ref to Invoice not with Third party sales order
While maintaining in VF01 Maintain Billing type G2S Only Not G2
Coming to TASG Item cat in copy control we have to make Between TAS --TASG Item category level In the Sales document type to Billing document type source and Target doc.
Dear Mentors please Tell me if i am wrong .
Thanks a lot

MRP Indicator check box in MIGO

Dear All,
While capturing Excise Invoice during Goods Receipt (T.Code: MIGO), in Excise Invoice tab of MIGO screen- there is a button for " More Data". After clicking that button and in the 'Miscellaneous' tab , there is a MRP Indicator check box.
Please let me know when we need to flag MRP Indicator check box.My doubt is in which scenario, we need to flag that check box.
Regards,
Phani

Dear Piyush,
Tnx for ur solution.
Scenario-1: MIGO done & MIRO not done:
MRP indicator flagged:
In this case, the value of the material will be the Basic material price minus the Excise duty amount. ( For eg: material base value =Rs. 1000; BED= Rs. 160, E. cess=32 & SHE cess= 16). The total valuated stock will be Rs.792.
MRP indicator NOT flagged:
In this case, the value of the material will be the Basic material price.( For eg: material base value =Rs. 1000; BED= Rs. 160, E. cess=32 & SHE cess= 16). The total valuated stock will be Rs.1000.
Scenario-2: MIGO done & MIRO done:
MRP indicator flagged:
In this case, the value of the material will be the Basic material price. ( For eg: material base value =Rs. 1000; BED= Rs. 160, E. cess=32 & SHE cess= 16). The total valuated stock will be Rs.1000. (the ED amount of (1603216) will be debited to material value while doing MIRO poting.
MRP indicator NOT flagged:
In this case, the value of the material will be the Basic material price.( For eg: material base value =Rs. 1000; BED= Rs. 160, E. cess=32 & SHE cess= 16). The total valuated stock will be Rs.1000.(Rs. 1000/- debited to material account while doing MIGO itself) .
Concludingly, I want to know in what scenario we will flag the MRP Indicator. Please note that I am aware of the trading scenario also.
Regards,
Phani

Problem in Posting of GR for Subcontracting PO Through MIGO

Hi All,
When I am posting 101 through MB01 for Subcontracting PO The system is creating three line items in Material Document( 101, 543 & 545 ) which is correct.
But if i am doing the same through MIGO it is posting three line items as (101, 543 & 543) - Which is wrong.
I am using SAP R/3 4.7.
Please let me know if there is any OSS note to fix this.
Thanks a ton in advance.
-Nirupam

Hi,
I can't belive it....543 is showing Credit indicator and 545 is showing debit indicator. Which is perfect. So, when we receive a subcontracting PO, if at all there is any byproduct that is going to be received, it has to be either debit or credit (only one way) whether we receive from MB01 or MIGO. If you see 545 in MB01 that means, you are receiving by-products along with ....However, in MIGo you are showing only 543 (consumption of components).....Are you missing any by-products comingup in mIGO? Is the PO the same you are using in both MB01 and mIGO....very minimal differences in terms of functionality we may encouner between these two transactions but I strongly doubt about posting two different movements types for exactly the same data....I am not doubting you; just curious to work on such problem. Please cross verify again and let me know.
Regards

Change G/L account in MIGO

Hi experts,
Could you help me in a couple of doubts?
How could we change the G/L account in the goods receipt item (using MIGO tcode) to balance account if in the purchase doc item is an expense account? Is there any BADI, exit, customizing,...? I couldn't find anything.
If we cancel a material document which had created a FI document posted to a balance account, we need to create a CO document too for adjusting the commitment, how is it possible? There should be an enhacement to allow it, but I couldn't find it.
Many thanks for your help!

1. You can not change G/L account in MIGO.
If you want to change G/L account in MIGO, You have to change the account assgnment G/L account field in the relevant purchase order. Then post goods receipt using MIGO transaction.
2. When a posting is made to balance sheet account in FI, there may not be any CO document. Hence no need post a document in controlling.
If at all you want post any document using the Corresponding Cost Element(G/L account in FI) use transaction KB11N. But we use this transaction to post Expenses/Costs only.
Because you are asking for posting of Balance sheet account you might have assigned Internal order or WBS element in your original G/L account line items. If you reverse a FI document with IO or WBS element assinment a controlling document is automatically arised when reverse the original FI document.
Prasad

No Commercial Invoice pop-up in MIGO for depot

Hi,
I am doing a MIGO for Imports in depot,but there is no commercial invoice pop-up appearing.
I did the following:
Checked the tax procedure ,created the required condition types for Ecess and SHEcess which were missing.
Created condition records with zero tax code for the condition types
Maintained in the relevant condition types in tax defaults
Again made a new PO.Put values of all the import duties.
Here my client has CVD and Add Customs inaddition to BCDs.So only two conditions will come other exicse.This is according to the new amendment.
After doing all this still I am not getting a commercial invoice pop-up in MIGO.
System :ECC 6.0 patch:20
I have a doubt with tax excise defaults.
Becuase even if I try to make an excise invoice through J1IG , it says no entries found in table J_1IEXCDEF.
Please let me know the correct entries for this table and also if any dependency is there.
CVD Condition type:JCV1
Add Duty:JADC
BED:JMX1
ECS:JEC2
SHECESS:JHX1

Hi
This popup comes only for import PO. The vendor in these import PO have the import pricing procedure(std or z copy of std)
It seems you are using std import pricing procedure or a copy of that for your domestic vendor.
You should use only std domestic pricing procedure or a copy of that for your domestic vendors
And if this is not the case then there is a bug in your system. Raise OSS to SAP

Reg: Base value in Excise tab in MIGO for imports po

Hi All.
I have a doubt how is the base value claculated in excise tab while doing MIGO for imports PO does this value is picked up from the materila master ?!!!1
regards,
Abilash V

hi
for import MIGO u r entering the doc no of excise (miro doc )
using this system calculates the base value in MIGO
when u do MIGO for imports at start only system will ask u for doc no of MIRO
regards
KI

Aacquistion value is negative in area 01(migo)

Hai Experts,
While cancelling the material document in migo I am getting an error "acquisition value is negative in are 01".I have checked in OAYZ and "Define how depreciation areas post to general ledger",there it is positive if i change it will work but what is my doubt is why is that negative value appearing because amount ill not be changed.So what will be the solution i can suggest.
Thanks in Advance

Hi Pavi,
Do not change setting at the depreciation area level...
follow below steps...
1. Use transaction OAYZ, choose Asset Class and double click on Depreciation Area and check which Layout has been assigned to the active depreciation area.
2. Use transaction AO21, choose the layout assigned in step 1 and go into Field group rules. Make the field "Negative Value" optional and select fields Class, MnNo. and Sbno. Save settings.
3. Use transaction AS02 and enter the Asset you are reversing MIGO for, go to depreciation area and double click on one of the active depreciation area and select the field "Negative Value". Repeat this process for all active depreciation areas for the asset.
Done.
Regards,
Chintan Joshi

Storage bin in MIGO

Hi everybody,
in MIGO we should record data not only in field <storage location> but also for the <storage bin>. This field is not beeing displayed in MIGO. Any suggestions for development?
Afterwards the recorded data for storage bin should be visible in Stock overview (i.e. MMBE).
Best regards
Joerg

Hi Rajesh,
Can U clar my doubts & Procedure for the fallowing Issues.. Im MM consultant . and now Im working on WM also.
1 ) is it possible to Auto Allocation of Storage Bins for Recieving Goods..?
2 )is it possible to Auto Conversion if Quantities in to Pallets
3 ) is it possible to Put away for Stocking Items beased on Category ( exp. expity date , Manufacturing date like )
4 ) Delivery Link for picking slip with Gate pass.

PS : If anybody have any presentaion on WM Pls send to [email protected]
Waiting for your reply
Thnx & Reg,
Pavan G Kulkarni

Status check on MIGO while doing GR from PO

Hi Team,
How to remove/ deactivate status check maintained on MIGO while doing GR from PO
Thanks

Not sure exactly what is causing it but I doubt that this is an SAP problem.
The error message you are getting has only the word TEST in it and the message number starts with a Z. SAP doesn't start their message numbers with Z. It is used for customer objects. This tells me that the message you are seeing is a custom one someone in your company has created and is causing to display. Chances are it is being used in a user exit as part of development. If this is in your production system, I would say you have a problem as a TEST message like that shouldn't show up. It should either be a real message with additional information or it should have been removed before moving to production.
I would have a developer run this in debug. Chances are you'll find a user exit in use that is causing this.
FF

Migo doubt

Similar Messages

Maybe you are looking for