Reference document of migo transaction

hi,
can anybody tell me how i have to assign reference doument in migo transation?
like we gr against po with mvt. type 101.
now i have made another mvt type 901 by copying101.
my question is how it is decided which mov. type will activate when?
regards
jash

hi
both will be activated and its up to ur use u can use 101 or 901
now u can set ref doc for transaction and not for movement
spro>mm>inve mang>Settings for Enjoy Transactions>Settings for Goods Movements (MIGO)>Settings for Transactions and Reference Documents
her u have to activate the ref doc u need
hope it help
regards
kunal

Similar Messages

In Which Table I Will get Reference Document for MIGO Transaction

Hai Experts
In Which Table I Will get Reference Document for MIGO Transaction
Regards
Jagadish

Hi,
The 2 main tables for this MIGO Transaction are ,
MKPF - Header table
MSEG - Item table
Reference Document is XBLNR.
Regards,
Raj.

Problem in Posting Document through MIGO transaction

I am posting goods in MIGO transaction.When the goods are posted tables MSEG(Document Segment: Material) and table MKPF(Header Table for material) are getting updated for the new material.My requirement is to update the table QALS and QAVE with the new batch number getting updated in MSEG table.I have to fetch some data(Inspection Lot Number) from these tables.

Hi,
You can find data in these tables when quality checking is done, these needs to be set by functional consultants.
Chekc your process if any Inspection lots size is defined for each each goods movement at all, if not these tables will not be populated at all.
Regds,
Mano Sri

Hold document in MIGO

Hi,
I need a hold document in MIGO transaction(using HOLD button in MIGO). Anybody knows BAPI ou other way for to do this?
I didn't find any BAPI to do this.
Thanks.

Hi Rosa Maicon ,
Try using this bapi
BAPI_GOODSMVT_CREATE
Regards
Hiren K.Chitalia

Deliverables Reference Documents

Hi all,
Could any one please help me in finding out the reference documents for all the deliverables like Business Requirements document, Business process documents etc for iRecruitment and if possible other modules also. As we are implementing iRecruitment for the first time we dont have any reference documents.
Any suggestions are welcome.
Thanks & Regards,
Sreedevi.

Hi,
You can not change the reference documents in MIGO.
Regards,

Reference Document LFBNR in MIGO

Hi all,
Question.
When i enter materials with transaction MIGO the field "Reference Document" is completed with the some number of the material document but it some cases is not working like this.
The thing is that i´m using the same plant, storage location and movement type (101).
Anyone know why ???
Thanks !

Hi Dalmiro,
This is controlled by SPRO settings.
SPRO - MM - Inventory Management & Physical Inventory - Settings for Enjoy Transaction - Settings for Transactions and Reference Documents.
Regards,
Ramesh

Free item reference document number not populated in MIGO item screen

Hi
I have a requirement where in I would need to populate the reference document number in the MIGO item when I am cancelling a goods receipt in case of free items.
In standard SAP system we know that it would only be populated when GRbased IV is ticked in PO but in free item PO this is not ticked . So was enquiring if any body knows how we could populate the reference document number at GR cancellation in MIGO item level for free items .

Hi,
If you mean the field MSEG-SMBLN, then it is always populated at cancellation, no matter the GR-based IV flag.
BR
Raf

Migo reference document not appearing in miro for frieght conditions

Dear all,
I ahve done migo for a po and i have checked GR based invoice in PO.When i am doing MIRO i am not getting the migo reference number for frieght condition where as the migo reference number is appearing for base price.How to get that migo reference number for frieght conditions also.
thanks in advance
regards
vithal

Sometimes the the MIGO creator might have reversed the same. In such cases the reversal document may be with different number in the same series and both posted & reversed documents will not appear in MIRO. Since you might checking with posted document number, you are seeing the blank in MIRO. In such cases, just enter the PO number in MIRO, give date & reference number press Show PO structure button in the left corner. You will find the following screen
Expand the required once. The following screen appears. In this both positive & negative numbers with same reference & document type appearing are the reversed documents.
Hope this is clear

Reference Documents not display in MIGO

In some MIGO Documents Numbers the Reference Document (LFBNR) has not been display but its picks from the sap itself.
I have made the MIGO & MIRO ACCOUNTING DOCUMENTS REPORT in which i pick the data from EKBE. I used the following feilds:-
EKBE (LFBNR)
EKBE (LFGJA)
But for some MIGO documents in which the reference document is not been display has not update the values in this field so anybody tel me why its not updated??
Thanks,
Sumit.

Hi Sumit ,
EKBE-LFBNR will be updated only if any reversal documents are created .
regards
Prabhu

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

How to provide document attachment (DMS) functionality in MIGO transaction

Dear All,
How can I provide the document attachment functionality (Document will be stored in content DMS server)
in MIGO Transaction.
The same functionality provided by SAP in ME21n, ME22n Transactions.
In ME21n user can upload any type of document related to line item wise and that document can we view/ modify from ME22n as well as from DMS side ( T.code - CV02n).
can anybody help me that how can i provide same functionality in MIGO transaction.
Regards,
Priya

Hi,
here is a sample of GETDETAIL2. Hope it helps.
image from DMS System
check this as well:
aRs - even with DMS, there can be ATTA's requiring BAPI_REL_GETRELATIONS
I guess the Ted Mentioned here is you:
aRS:: Bookmark this thread! (LOIO's and PHIO's for DRAW att's (Vijay too!)
Best regards.
Edited by: pablo casamayor on Jul 29, 2008 8:14 AM
Edited by: pablo casamayor on Jul 31, 2008 3:53 PM

Document date&Posting date Validation In MIGO Transaction

Hi,
I need to control document date should not be in future date comparing to posting date and should not be past date comparing to PO date in MIGO transaction.Pls suggest.
Regards
Mani

Dear Mani,
Goto Spro
Materials Management -> Inventory Management and Physical Inventory -> Define Attributes of System Messages
Goto Settings for System Messages and select
Version 00
Application area -- M7
Messages no -- 088 -- Document date lies in the future. (Check your entry)
Convert in Error Massage.
Regards,
PK

Short Dump in MIGO transaction

When executing the transaction MIGO the transaction ends with the short dump as follows.
is it because of SAPNOTE 385830 ?
short text of error message : GET_SYTEM_BUSINESS_ERROR An error occurred while determining the business system ( No_business_system)
Technical information of error message
messgae class 00
number 001
variable 1 GET_SYTEM_BUSINESS_ERROR An error occurred while
variable 2 determining the business system ( No_business_system)
T CODE : migo
PROGRAM : SAPLMBWL
sceen no saplmigo 0001
screen line 18
the dump occurs at the line marked with -
>.
function mb_post_goods_movement.
""Local Interface:
*" IMPORTING
*"     VALUE(XBLNR_SD) OPTIONAL
*" EXPORTING
*"     VALUE(EMKPF) LIKE EMKPF STRUCTURE EMKPF
   data: l_mem_id(10) type c.                                   " 641365
Wurde zuvor eine Lieferung erzeugt, so ist kein MB_POST... nötig "HUM
   check not xdeliv = x.                                            "HUM
Control posting for external WM: Exit if BFWMS = 1 (Create delivery)
   check not mkpf-bfwms = 1.                                     "357661
   read table xmseg index 1.
   if not sy-subrc is initial.
     message a260.
   endif.
   if xmkpf-mblnr is initial.
     message a260.
   endif.
   xcommit = x.                                             "Performance
   if not xblnr_sd is initial.
     xmkpf-xblnr    = xblnr_sd.
     xmkpf-le_vbeln = xblnr_sd.                                 "XAN-SPM
     modify xmkpf index 1.
   when a goods movement for an inbound or outbound delivery is posted
   directly from VL31N/ VL01N, XBLNR is not yet known when we call
   CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
   BKPF as well. There is no other way to forward XBLNR to FI as not
   every document is posted by MB_CREATE -> a new function module in
   MBWL for transferring the information, called by FI, meant to load
   the complete function group for all MBxx postings when this isn't
   required (Performance). Would be the better way to transport the
   information after switching off MBxx in later release.
   corresponding IMPORT ... FROM MEMORY ... can be found in
   AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
     l_mem_id = 'MKPF-XBLNR'.                                   " 641365
     export xblnr = xblnr_sd to memory id l_mem_id.             " 641365
   endif.
   if xmkpf-xabln is initial.                               "note 434093
       call function 'MB_XAB_NUMBER_GET'.                   "note 434093
   endif.                                                   "note 434093
enhancement-point mb_post_goods_movements_01 spots es_saplmbwl static.
$$-Start: MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement 26 dimp_general_saplmbwl.    "active version
data: l_statics_lock type c.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement-point mb_post_goods_movements_02 spots es_saplmbwl.
$$-Start: MB_POST_GOODS_MOVEMENTS_02----
$$
enhancement 25 dimp_general_saplmbwl.    "active version
read table xvbfa index 1.
if sy-subrc is initial and
   g_vbtyp_v = '7'.
   perform get_mdiff_kenz(sapmm07m) changing l_statics_lock.
endif.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_02----
$$
   call function 'MB_CREATE_MATERIAL_DOCUMENT_UT'
        exceptions
          error_message = 4.
As soon as we have started to put things into UPDATE TASK, we must
ensure that errors definitely terminate the transaction.
MESSAGE A is not sufficient because it can be catched from
external callers which COMMIT WORK afterwards, resulting in
incomplete updates. Read note 385830 for the full story.
   if not sy-subrc is initial.
message id sy-msgid type x number sy-msgno with            "385830
                 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MESSAGE A263.
   endif.
Optische Archivierung
Spaete Erfassung mit Barcode
Redesign of barcode handling -> note 780365
perform barcode_update(sapmm07m) using xmkpf-mblnr
                                         xmkpf-mjahr
                                         barcode.
move-corresponding xmkpf to emkpf.
call function 'MB_MOVEMENTS_REFRESH'
    exceptions
      error_message = 4.
   move-corresponding xmkpf to emkpf.
   call function 'MB_MOVEMENTS_REFRESH'
        exceptions
          error_message = 4.
   if not sy-subrc is initial.
     message id sy-msgid type x number sy-msgno with             "385830
                sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   MESSAGE A261.
   endif.
   perform buchen_initialisieren(sapmm07m).
   clear emkpf-subrc.
clear global fields when COMMIT WORK                     "Performance
   if not sy-oncom = p.
     perform clear_xcommit on commit.
   else.
     perform clear_xcommit.              "if this FB is called on commit
   endif.
   perform clear_xcommit on rollback.                       "note 303392
endfunction

hi
check SAP Note 556000 - Short dump due to note 385830
Summary
Symptom
   Consider the subsequent note 561872 !                             *
You want to post a goods receipt for a reference document (for example purchase order, delivery ...). The checks do not cause any error. Nevertheless, the system generates a short dump which is deliberately triggered by note 385830.
One known scenario is a stock transfer process via a delivery: You have entered a stock transport order assigned to a sales order and post a goods receipt for the delivery via transaction MIGO. The sales order must be in valuated. The material to which postings are to be made is valuated separately and to be handled in batches. And the batch, which was assigned via the delivery, already exists with a valuation type in the receiving plant which is different from the one specified in the purchase order.
Other terms
MB_CREATE_GOODS_MOVEMENT, MIGO, MCHA, BWTAR.
Reason and Prerequisites
Prerequisites: see above. This is a program error.
Solution
Implement the attached program corrections.
Then implement the subsequent note 561872.
After the implementation of the note, checks are carried out in the program flow - if a batch and a valuation type were entered for a goods movement (for instance with reference to the purchase order or delivery) - on whether the assignment of the batch and valuation type is correct.
regards
KI

Saving custom fields to MSEG added in additional TAB in MIGO transaction

Hi Experts,
I am facing an issue with an enhancement in MIGO transaction for which i need help. I have gone through several threads with similar issues but none of them have solved my issue. I have worked around with all BADIs of MIGO and user exits available but to no avail so I am posting a new thread.
The requirement is pretty straight forward of adding a custom TAB in item details section of MIGO transaction. I have done that using BADI: MB_MIGO_BADI, method PBO_DETAIL. I created a screen with my custom fields and passed them in this method. The TAB appears as expected with all the fields. The custom fields are in MSEG table which has been enhanced and it needs to be updated with the user values on the screen.
The issue creeps in when there are multiple materials in the purchasing document and user works around with them. Say he clicks on the second material and in the custom TAB changes its details in custom fields. Now he clicks on the fourth material and changes its details. Continues this for all the materials in random order. How do i identify in my custom screen [developed separately and called in PBO_DETAIL of the BADI] which details belong to which material or line number. The only way to do it is by using the purchasing order number and line item number. These are not available in my custom screen and needs to be exported from somewhere and imported there. I have not been able to identify the point where export can be done.
Can anyone help me out with this problem? Either the point where export can be done or any other way of identifying the link between the line number / material number and the custom field details entered by the user.
Thanks,
Ritvik

Hi Ritvik,
you will not need it.
The item methods will process exactly the item what the addional item data are related to. In PBO_DETAIL and PAI_DETAIL, use parameter I_LINE_ID for the item reference.
Note: Not only read SCN etc, also the parameters desciption of the methods used.
Regards,
Clemens

Regarding - add a new field in migo transaction

Hai guys,
i need to add one field in MIGO transaction, can u pls tell me the step by step procedure for adding the new field in migo transaction.
Regards,
N.selvamuthukumar.

Hi Selvamuthu,
It is possible using the BADI MB_MIGO_BADI to add Additional tabs in header and/or item as required
MB_MIGO_BADI -> BAdI in MIGO for External Detail Subscreens
See the documentation below...........
With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the interface of the goods movements transaction ( MIGO) with additional tabstrip controls for the detailed information (detail tabstrips) and header information (header tabstrips). It is possible for an external application
to display an additional detail tabstrip with own subscreen (max. 10 lines) in MIGO
to display an additional header tabstrip with own subscreen (max. 3 lines) in MIGO
The program name, screen number and tab page text can be determined dynamically. Different screens can therefore be controlled according to the mode (for example, change mode, display mode, goods receipt, goods issue).
To read the complete documentation --go to se18 --click on BADI -- enter -- MB_MIGO_BADI----Display
inside click on "DOCUMENTATION" button and there is a complete documentation step by step
in addition to it ...--go to se18 --click on BADI -- enter -- MB_MIGO_BADI----Display ->
on the top menu -> "GOTO" -> sample code -> "Display"
in will get the "methods" tab..see the description
Initialization and Registration of Ext. Detail Screens
PBO of Detail Screen
PAI of Detail Screen
Add / Change a Line (GOITEM)
Delete a Line (GOITEM)
MIGO Reset (Delete All Internal Data)
Post Goods Movement
Check Item Data of Goods Movement
Mode of Transaction MIGO (Action / Reference Document)
Status Information and Header Data
Save Held Data
Load Held Data
Delete Held Data
PBO of Header Screen
PAI of Header Screen
Check Header Data of Goods Movement
Publish Item Data After Processing
sample code is given in these methods..so when we create a custom badi implementation of our own go to the sample code and copy the required code in the corresponding methods as required
double click on the method..for eg:IF_EX_MB_MIGO_BADI~PBO_HEADER in the sample code to see code....in this particular method we can see how method calls an external program and screen to create a new tab in MIGO...use code from mainly the following to get a new header/item tab
PBO of Header Screen
PAI of Header Screen
PBO of Detail Screen
PAI of Detail Screen
Pls take some time to analyse the code or flow but we can have the tabs in the header/item level
Hope it helps
Regards
Byju

Reference document of migo transaction

Similar Messages

Maybe you are looking for