Posting Block in Migo transaction

Dear all,
please help me with this problem, I want user don't view price condition into migo transaction during a goods entry.
How must use authorization object or other strategies?
many thanks.
GV
Edited by: Gianluca Vinco on Oct 24, 2008 3:38 PM
Edited by: Gianluca Vinco on Oct 24, 2008 3:39 PM

not properly, we speak about purchase order data in "detail data" in migo.
About your note on migo_gr, in my system user that have migo_gr and go to "search PO" got error:
PO items rejected due to authorizations/selection
parameters
PO items rejected due to authorizations/selection parameters
if I block me23n I got this error message.
"Message no. ME422
Diagnosis
The selection of purchasing documents failed for the following reasons:
The system could not find any purchasing documents that matched the selection parameters and/or that can be used in this transaction
or
You do not have authorization to select purchasing documents.
Procedure
Choose different selection parameters
or
Ask for your authorization profile to be extended."
do you have updates about that?
Edited by: Gianluca Vinco on Oct 24, 2008 3:57 PM

Similar Messages

  • Service tax value required updating while posting GR in MIGO transaction

    Dear Friends,
    We have a following scenario where service tax value required updating while posting Goods Receipt MIGO transaction.
    1. Purchase Order created for first line item where Qty. 1 and Net Rate Rs.1000/- so total Gross value will be Rs.1000/- example Vendor XYZ
    2. Freight condition type maintained for the first line item for Rs.500/- and assigned to Transportation vendor ABC.
    3. When Goods Receipt Posted for the Material against PO first line item, the material value updates Rs.1500/- (Material value as 
        per PO + Freight Charges)
    4.  After posting GR while making Invoice verification through MIRO transaction against the PO GR/IR clearance will be done for 
        Material vendor XYZ. For transportation Vendor ABC Planned delivery cost indicator will be select and since service tax is
        applicable Service tax code will also select.
    Here the values of Service tax if the Material available in Stock it will be inventories. If stock consumed before making the Invoice verification for Transportation vendor ABC, then the Service tax values update to PRD account.
    We know that in PO, tax code can be select for first line item (Raw Material) Vendor XYZ and if transportation charge condition type maintained for same first line item and assigned to Vendor ABC and there is no provision to maintain Service tax. So the service tax will get inventories while posting Invoice Verification for the transportation vendor.
    We want the values of Service tax to update while posting Goods Receipt in MIGO transaction.
    Thanks & regards
    Dhanu

    hi,
    Please note at the time of MIGO Servecie tax value does not appear, it will appear at the tiem of Invoice only.
    Regards,
    Rama Mohan Bangaru

  • 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

  • Transfer posting against purchase order in MIGO transaction

    Dear all,
    How can we make the settings in MIGO transaction code for Transfer posting with reference to Purchase order.
    Other wise, i want to do the transfer posting of my goods to my sub contractor with refernce to PO number in MIGO Tcode
    Any config settings are required.
    Thanks & Regards,
    R.Saravanan

    As per SAP online help you have three options to post components to your SC vendor's special stock:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b906243ad11d189410000e829fbbd/frameset.htm
    You can provide components for existing purchase orders in the following ways:
    from the SC Stock Monitoring for Vendor list as a goods issue via Inventory Management
    from the SC Stock Monitoring for Vendor list as a delivery via Shipping
    from the Inventory Management menu
    If you read the instruction for the third option (first two is about ME2O), you will see it is speaking about MB1B and not about MIGO.
    1. From the Inventory Management menu, choose Goods movement ® Transfer posting.
    2. Enter the issuing plant and storage location. Choose Movement type ® Transfer posting ® Stck w. subcontract. ® From unrestricted. Enter the vendor and then choose Transfer posting ® Create with reference ® To purchase order.
    A dialog box appears in which you can enter up to 4 purchase orders.
    In MIGO you can choose only "A08" with "R02", "R08", "R09". "R01" is not allowed for "A08" in standard system.
    (Maybe it is possible but I do not know how...)
    Edited by: Csaba Szommer on Aug 5, 2010 11:54 AM
    Edited by: Csaba Szommer on Aug 5, 2010 11:54 AM

  • 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

  • In MIGO transaction Transfer posting user exist or BADI or Enhacements

    Hi Experts,
    Could you please help on this issue.
    My requirment is, In MIGO transaction code, Transfer Posting (i.e., Storage location) screen, in item level there is Transfer  posting tab  From and Dest two sub screens are there.
    if user enter material , plant and stoargae location in From side and that will be same maintain in Destination side.
    If any user will change in Destination level Material or Plant or Stoarage location, I need to populate the error message.
    Could you please tell me BADI or user exist or Enhacement for this requirment.
    I have serached in SDN and debug the transaction code MIGO. I didn't found user exist and enhacment.
    Thanks
    Srinu

    HI ,
    If i tried this Enhacment MB_MIGO_SC. I have put break point and it is not triggering, when i am saving/ Checking the postings in MIGO transaction code.
    Thanks
    Srinu

  • Posting block check in MI31 transaction

    Hi,
    I have done following steps -
    1. Create inv document using MI31 with posting block check box selected. Step OK.
    2. Doing 311 using MB1B - System prevents me from doing this movement. Step OK
    3. Doing MI04 Step OK
    4. Again doing 311 using MB1B - System prevents me from doing this movement, but with only one material.
    If I am trying with other material, after MI04, I am able to do movement type 311 move using MB1B.
    What is that it prevent me from doing 311 activity will that material after MI04?
    Any input is appreciated,
    Regards,
    Dipak

    not fully correct. the posting block is erased whenever you enter a count, it does not matter if your count matches with the book quantity or not.
    The purpose of the posting block is to prevent entering movements in SAP while a phyiscal inventory is active. This is only one side of the medal. The other side is your organisation of a physical inventory. Here you have to take the same measures, you need to prevent people from moving materials until you have finished your count.
    Once you enter the count, then SAP is just certain that the count has finished and the block is no longer needed.
    If you counted correctly, then you will not move more than you counted, hence you will not have any issue if you post the difference some days later.

  • Bapi for migo transaction

    i have created a bapi to upload data for MIGO transaction.. (GOODS RECEIPT-->PURCHASE ORDER)
    i am getting the error " stock posting is not possible for this material "'.
    when i create directly, it is posted.. while uploading through the program it shows the above error.
    please suggest if anyone knows....
    Thanks in advance,
    Dhivya N.

    *& Report  ZR_MIGO_UPLOAD
    *& package name : zabap
    *& transport request number : MIDK901443
    *& program to upload goods movement
    REPORT ZR_MIGO_UPLOAD.
    ***DATA DECLARATION***
    type-POOLs:  icon.
    TYPES: BEGIN OF TY_GR_PO,
            EBELN(10) TYPE c ,     "'PO NUMBEr
            EBELP(10) TYPE c,     "PO ITEM NUMBER
    *       LGOBE TYPE LGOBE,     "STORAGE LOCATION DESCRIPTION
            LGORT(10) TYPE c,     "STORAGE LOCATION
            XFELD TYPE c,     "ITEM OK
            GERNR(10) TYPE c,     "SERIALNUMBER
            END OF TY_GR_PO.
    DATA: TA_GR_PO TYPE TABLE OF TY_GR_PO,    "TABLE FOR GOODS RECEIPT PURCHASE ORDER
           WA_GR_PO TYPE TY_GR_PO.
    DATA: BLDAT TYPE BLDAT,     "DOCUMENT DATE
            BUDAT TYPE BUDAT,     "POSTING DATE
            WEVER TYPE WEVER.     "VERSION FOR PRINTING GR SLIP
    ***BAPI DECLARATION***
    DATA: BEGIN OF GM_HEAD OCCURS 0.                    "Material Document Header Data
             INCLUDE STRUCTURE BAPI2017_GM_HEAD_01.
    DATA: END OF GM_HEAD.
    DATA: BEGIN OF GM_CODE OCCURS 0.
             INCLUDE STRUCTURE BAPI2017_GM_CODE.          "Assign Code to Transaction for Goods Movement
    DATA: END OF GM_CODE.
    DATA: BEGIN OF GM_RET OCCURS 0.
             INCLUDE STRUCTURE BAPI2017_GM_HEAD_RET.       "Material Document Number/Material Document Year
    DATA: END OF GM_RET.
    DATA: BEGIN OF GM_ITEM OCCURS 0.
             INCLUDE STRUCTURE BAPI2017_GM_ITEM_CREATE.    "Material Document Items
    DATA: END OF GM_ITEM.
    DATA: BEGIN OF GM_SER OCCURS 0.
             INCLUDE STRUCTURE BAPI2017_GM_SERIALNUMBER.    "Serial Number
    DATA: END OF GM_SER.
    data: BEGIN OF ta_bapireturn OCCURS 0.
            INCLUDE STRUCTURE BAPIRET2.
    data: END OF ta_bapireturn.
    ***declaration of excel file handling table***
    FIELD-SYMBOLS: <fs> type any.    "field symbol for alsm_excel
    DATA: TA_EXCEL TYPE TABLE OF ALSMEX_TABLINE,  "table to contain excel sheet values
           WA_EXCEL TYPE ALSMEX_TABLINE.
    ***declaration of other parameters***
    data:       V_brow type i VALUE    2,    "BEGIN OF ROW
                 V_bcol type i value   1,     "BEGIN OF COL
                 V_erow type i value 65536,   "END OF ROW
                 V_ecol type i value 256.     "END OF COLUMN
    DATA:  V_sear type string,
            V_INDEX TYPE i,
            V_tabix type sy-tabix,     "current line.
            v_lines type i.          "total number of records
    DATA: DATE TYPE DATS.
    ***SELECTION SCREEN***
    ***SELECTION SCREEN DESIGN***
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP 3.
    PARAMETERS: zCODE(2) TYPE C MATCHCODE OBJECT H_T158G,
                 zrefdoc type REFDOC,
                 version type WEVER.
    SELECTION-SCREEN skip 5.
    PARAMETERS: p_file type ibipparms-path.
    SELECTION-SCREEN SKIP 3.
    SELECTION-SCREEN END OF BLOCK b1.
    ***SELECTION SCREEN VALUE REQUEST***
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
       CALL FUNCTION 'F4_FILENAME'                                    "f4 help for file name
         EXPORTING
           PROGRAM_NAME  = SYST-CPROG
           DYNPRO_NUMBER = SYST-DYNNR
           FIELD_NAME    = 'P_FILE'
         IMPORTING
           FILE_NAME     = P_FILE.
    ***SELECTION SCREEN EVENT***
    AT SELECTION-SCREEN.                                 "validation
       if p_file <> ''.
         V_sear = p_file.
         SEARCH V_sear for '.xls'.
         if sy-subrc <> 0.
           message 'please provide excel file. it is not valid' type 'E'.
         ENDIF.
       ENDIF.
    INITIALIZATION.
    *   DATE = '17.04.14'.
       GM_HEAD-PSTNG_DATE = SY-DATUM.
       GM_HEAD-DOC_DATE   = SY-DATUM.
       gm_head-pr_uname = sy-uname.
    ***START OF SELECTION***
    START-OF-SELECTION.
       gm_head-REF_DOC_NO = zrefdoc.
       gm_head-VER_GR_GI_SLIP = version.
       GM_CODE-GM_CODE = zCODE.
       PERFORM EXCEL_UPLOAD.
       PERFORM EXCEL_CONVERSION.
       PERFORM NO_RECORDS.
    END-OF-SELECTION.
       PERFORM BAPI_ASSIGNMENT.
       PERFORM BAPI_FM.
    *&      Form  EXCEL_UPLOAD
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM EXCEL_UPLOAD .
       CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
         EXPORTING
           FILENAME                = P_FILE
           I_BEGIN_COL             = V_BCOL
           I_BEGIN_ROW             = V_BROW
           I_END_COL               = V_ECOL
           I_END_ROW               = V_EROW
         TABLES
           INTERN                  = TA_EXCEL
         EXCEPTIONS
           INCONSISTENT_PARAMETERS = 1
           UPLOAD_OLE              = 2
           OTHERS                  = 3.
    ENDFORM.                    " EXCEL_UPLOAD
    *&      Form  EXCEL_CONVERSION
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM EXCEL_CONVERSION .
       if ta_excel is NOT INITIAL.
         sort ta_excel by row col.
         clear wa_excel.
         clear wa_GR_PO.
         LOOP AT ta_excel INTO wa_excel.
           move wa_excel-col to v_index.
           ASSIGN COMPONENT v_index OF STRUCTURE wa_GR_PO to <fs>.
           if sy-subrc = 0.
             move wa_excel-value to <fs>.
           ENDIF.
           at END OF row.
             append wa_GR_PO to ta_GR_PO.
             clear wa_GR_PO.
           ENDAT.
         ENDLOOP.
       else.
         MESSAGE 'no data for conversion' type 'I'.
       ENDIF.
    ENDFORM.                    " EXCEL_CONVERSION
    *&      Form  NO_RECORDS
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM NO_RECORDS .
       DESCRIBE TABLE ta_GR_PO LINES v_lines.
       if v_lines = 0.
         MESSAGE 'NO RECORDS TO UPLOAD' TYPE 'E'.
       ENDIF.
    ENDFORM.                    " NO_RECORDS
    *&      Form  BAPI_ASSIGNMENT
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM BAPI_ASSIGNMENT .
       IF TA_GR_PO IS NOT INITIAL.
         LOOP AT TA_GR_PO INTO WA_GR_PO.
           gm_item-PO_NUMBER = wa_gr_po-ebeln.
           GM_ITEM-STGE_LOC = WA_GR_PO-LGORT.
           GM_ITEM-PO_ITEM = WA_GR_PO-EBELP.
           GM_ITEM-NO_MORE_GR = 'X'."WA_GR_PO-XFELD'.
    *      GM_SER-SERIALNO = WA_GR_PO-GERNR.
           gm_item-NO_MORE_GR =  1.
           gm_item-ENTRY_QNT = 2.
           gm_item-MOVE_TYPE = 101.
    *      gm_item-MVT_IND = 'B'.
           gm_item-plant = 'P001'.
           gm_item-move_stloc = 'FG01'.
    *      GM_ITEM-SPEC_STOCK = 'K'.
           APPEND GM_ITEM.
           APPEND GM_SER.
         ENDLOOP.
        ELSE.
          MESSAGE 'DATA IS NOT UPLOADED' TYPE 'I'.
        ENDIF.
    ENDFORM.                    " BAPI_ASSIGNMENT
    *&      Form  BAPI_FM
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM BAPI_FM .
    CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
       EXPORTING
         GOODSMVT_HEADER               = gm_head
         GOODSMVT_CODE                 = gm_code
    *   TESTRUN                       = ' '
    *   GOODSMVT_REF_EWM              =
      IMPORTING
        GOODSMVT_HEADRET              = gm_ret
    *   MATERIALDOCUMENT              =
    *   MATDOCUMENTYEAR               =
       TABLES
         GOODSMVT_ITEM                 = gm_item
        GOODSMVT_SERIALNUMBER         =  gm_ser
         RETURN                        = ta_bapireturn
    *   GOODSMVT_SERV_PART_DATA       =
    *   EXTENSIONIN                   =
    if ta_bapireturn-type = 'S'.
         write:/ icon_green_light as icon,
                 'success: Material document',gm_ret-mat_doc,  'is created for the GOODS RECEIPT- po number : ', wa_gr_po-ebeln,
               / 'reason:' , ta_bapireturn-message.
    ELSEIF ta_bapireturn-type = 'E'.
         write:/ icon_red_light as icon,
                 'error: Material document',gm_ret-mat_doc , 'is not created for the GOOD RECEIPT- po number : ', wa_gr_po-ebeln,
               / 'reason:' , ta_bapireturn-message.
    ENDIF.
    ENDFORM.                    " BAPI_FM

  • Inserting/ deleting a line item in MIGO Transaction ( Goods Issue )?

    Hi,
    Can anyone help me with the logic for Inserting / deleting a line item in MIGO Transaction?
    Thanks,
    cs

    Hi
    The following user exits and badis for migo:
    Check the mb_migo_badi and check the method 'LINE_MODIFY' for u r purpose.
    For undestanding see the documentation of the badi and see the example implementation
    class: CL_EXM_IM_MB_MIGO_BADI
                                                                                    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    MB_CF001                                Customer Function Exit in the Case of Updating a Art. Doc.      
    MBCF0011                                Read from RESB and RKPF for print list in  MB26                 
    MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1      
    MBCF0009                                Filling the storage location field                              
    MBCF0007                                Customer function exit: Updating a reservation                  
    MBCF0006                                Customer function for WBS element                               
    MBCF0005                                Article document item for goods receipt/issue slip              
    MBCF0002                                Customer function exit: Segment text in article doc. item                                                                               
    Business Add-in                                                                               
    MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data                       
    MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check                       
    MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn                     
    MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data                             
    MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens                     
    MB_DOC_BADI_INTERNAL                    BAdIs when Creating an Article Document (SAP Internal)          
    MB_DOCUMENT_UPDATE                      BADI when updating article document: MSEG and MKPF              
    MB_DOCUMENT_BADI                        BAdIs when Creating an Article Document                         
    MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR                  
    MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7                 
    MB_CIN_LMBMBU04                         posting of gr                                                   
    MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables          
    ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL                        
    ARC_MM_MATBEL_CHECK                     Check Add-On-Specific Criteria for MM_MATBEL    
    If it is helpfu rewards points
    Regards
    Pratap.M

  • Authorization for cost center in migo transaction

    Dear Experts,
    I need to restrict the user by the cost center assigned to him in the migo transaction,
    i tried with these objects A_S_KOSTL, K_CSKS  and K_CCA. As per forum threads I  also maintained the  check in su24 , but still authorization is not happening.
    please let me know how to do it, is there any user exits to achieve .
    waiting for ur help.
    Thanks & regards,
    Reena...

    Reena,
    You can do teh followign , apart from others :
    1. Ask the business owner the values for teh objects...ofcourse explain to them what the objects are in plain lainguage.
    2. Then populate the values "accordingly"
    OR
    1.As an earlier post...trace teh user --on ST01 - here  again - you can give eiither wide access and trace teh path and then restrict ..or restriced acces and then each time a road block is hit ..analysi s and assign.
    BUT DONOT maintian SU24 to restrict acces !!

  • BADI or userexit for MIGO transaction

    hi All,
                  I have a requirement to enhance the MIGO transaction subscreen 304.
    In subscreen 304 there is only check box ITEM_OK.
    In the MIGO at the bottom of the screen ,whenver we click on item_OK check box and press enter, in the line item it will automatically checks.
    After the first check it has to get disabled in the screen.
    I am trying to find the BADI for this..still trying
    Please let me know how to achieve this functionality.

    Hi,
    Try below BAdi's :
    MB_MIGO_ITEM_BADI or
    MB_MIGO_BADI
    MB_DOCUMENT_BADI.
    Also these will be of help furthur.
    Enhancement/ Business Add-in Description
    Enhancement
    MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
    MBCF0011 Read from RESB and RKPF for print list in MB26
    MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0009 Filling the storage location field
    MBCF0007 Customer function exit: Updating a reservation
    MBCF0006 Customer function for WBS element
    MBCF0005 Material document item for goods receipt/issue slip
    MBCF0002 Customer function exit: Segment text in material doc. item
    Business Add-in
    MB_RESERVATION_BADI MB21/MB22: Check and Complete Dialog Data
    MB_QUAN_CHECK_BADI BAdI: Item Data at Time of Quantity Check
    MB_PHYSINV_INTERNAL Connection: Core Inventory and Retail AddOn
    MB_MIGO_ITEM_BADI BAdI in MIGO for Changing Item Data
    MB_MIGO_BADI BAdI in MIGO for External Detail Subscreens
    MB_DOC_BADI_INTERNAL BAdIs when Creating a Material Document (SAP Internal)
    MB_DOCUMENT_UPDATE BADI when updating material document: MSEG and MKPF
    MB_DOCUMENT_BADI BAdIs when Creating a Material Document
    MB_CIN_MM07MFB7_QTY Proposal of quantity from Excise invoice in GR
    MB_CIN_MM07MFB7 BAdI for India Version exit in include MM07MFB7
    MB_CIN_LMBMBU04 posting of gr
    MB_CHECK_LINE_BADI BAdI: Check Line Before Copying to the Blocking Tables
    ARC_MM_MATBEL_WRITE Check Add-On-Specific Data for MM_MATBEL
    ARC_MM_MATBEL_CHECK Check Add-On-Specific Criteria for MM_MATBEL
    hope this will help you.
    Regards,
    Kiran

  • ABAP DUMP While doing GI Through Zmovement type in MIGO Transaction

    Hi ,
    We have migrated from FM FBS to BCS from 12.01.2015.
    And we are using 101 profile with GR and IR update.
    We received blow ABAP Dump while doing the GI through MIGO Transaction.
    Can you please help on this.
    Dump detatils
    Category               ABAP Programming Error
    Runtime Errors         MESSAGE_TYPE_X
    ABAP Program           CL_BUAVC_ENTRY================CP
    Application Component  PSM-FM-BCS-AC
    Date and Time          13.01.2015 09:10:00
    Operating system..... "AIX 1 6, AIX 1 7"                                                      |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 0                                                                                    |
    |    EM...... 33518336                                                                             |
    |    Heap.... 0                                                                                    |
    |    Page.... 196608                                                                               |
    |    MM Used. 21989120                                                                             |
    |    MM Free. 3145840                                                                              |
    |User and Transaction                                                                              |
    |    Client.............. 256                                                                      |
    |    User................ "MM_BUX00_ZZ"                                                            |
    |    Language key........ "R"                                                                      |
    |    Transaction......... "MIGO_GI "                                                               |
    |    Transaction ID...... "54AEDD9E3EE60710E10080000A15C616"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "54B35F7088300910E10080000A15C616"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "CL_BUAVC_ENTRY================CP"                                       |
    |    Screen.............. "SAPLMIGO 0001"                                                          |
    |    Screen Line......... 18                                                                       |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" -                 |
    |     in "POST".                                                                                   |
    |    The main program was "SAPLMIGO ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 82                                  |
    |    of the (Include) program "CL_BUAVC_ENTRY================CM00J".                               |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   52|*--- method has provided some errors!):                                                     |
    |   53|                                                                                            |
    |   54|* Note 1499464:                                                                             |
    |   55|*      IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP'                              |
    |   56|*       mode_assert_dump = 'X' ) = 'X'.                                                     |
    |   57|      MOVE 'X' TO l_flg_dump.                                                               |
    |   58|*      ENDIF.                                                                               |
    |   59|                                                                                            |
    |   60|*--- Check if the entry buffer of the AVC ledger contains data records                      |
    |   61|*--- from previous COLLECT events:                                                          |
    |   62|      IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ).                    |
    |   63|*--- Sorry, must dump:                                                                      |
    |   64|        ASSERT ID buavc_group                                                               |
    |   65|               FIELDS c_avc_text 'POSTING_NOT_ALLOWED'                                      |
    |   66|               CONDITION l_flg_dump <> 'X'.                                                 |
    |   67|        IF l_flg_dump = 'X'.                                                                |
    |   68|          MESSAGE x002(buavc) WITH c_avc_text space                                         |
    |   69|                                   'POSTING_NOT_ALLOWED' space.                             |
    |   70|        ENDIF.                                                                              |
    |   71|      ENDIF.                                                                                |
    |   72|    ENDIF.                                                                                  |
    |   73|*----------------------------------------------------------------------                     |
    |   74|* Note 1666556:                                                                             |
    |   75|    IF me->g_commit_before_post EQ 'X'.                                                     |
    |   76|*--- An unauthorized COMMIT WORK occurred before calling this POST                          |
    |   77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and                        |
    |   78|*--- would thus create a database inconsistency!                                            |
    |   79|      MOVE 'X' TO l_flg_dump.                                                               |
    |   80|      IF l_flg_dump = 'X'.                                                                  |
    |   81|*--- Sorry, must dump (see note 1666556):                                                   |
    |>>>>>|        MESSAGE x002(buavc) WITH c_avc_text space                                           |
    |   83|                                 'INVALID_COMMIT' space.                                    |
    |   84|      ENDIF.                                                                                |
    |   85|    ENDIF.                                                                                  |
    |   86|*----------------------------------------------------------------------                     |
    |   87|                                                                                            |
    |   88|                                                                                            |
    |   89|*--- Call the POST method of the corresponding ledger instance:                             |
    |   90|    CALL METHOD l_f_avc_ledger-ref_ledger->post                                             |
    |   91|      EXPORTING                                                                             |
    |   92|        i_ref_appl_log = me->g_ref_appl_log                                                 |
    |   93|        i_doc_ref      = i_doc_ref.                                                         |
    |   94|                                                                                            |
    |   95|  ENDLOOP.                                                                                  |
    |   96|                      
    Thanks Advance.
    SAM

    Hi Sam,
    Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
    Regards,
    Prakash.

  • Excise Invoice tab In MIGO transaction code

    Hello
    Could any body suggest, In Excise Invoice tab In MIGO transaction code I am getting "06  No Excise Entry" no otehr fields are coming.? All options like
    01     Capture & Post Excise Invoice
    02     Refer & Post Excise Invoice
    03     Only Capture Excise Invoice
    04     Only Refer Excise Invoice
    05     Only Part1
    Should come. Infact in my SAND Box client it is o.k but with same setting Golden Client it is not coming.?
    Thanks & Regards
    Sudhansu

    Hi,
    These options are coming from Excise Group settings.
    Go to : SPRO-Logistics General-Tax on Goods movements-India-Basic settings-Maintain Excise Groups-in 'MIGO Settings' tab, select the check boxes, accordingly you will get the options in Excise Tab of MIGO screen.
    Hope this will resolve your issue.
    Regards,
    Gopi Chand

  • 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).

  • Account determination error when i do MIGO transaction

    Hi All,
    When i post MIGO transaction I get this error.
    ACCOUNT DETERMINATION FOR ENTRY INT BSX--3000 NOT POSSIBLE.
    Can anybody help me to resolve this issue.
    Regards,
    Srivatsan

    Hi,
    Transaction Event Key "BSX" is used for inventory posting.At the time of MIGO Stock/Inventory Account is debited.
    Please check your material code. As per the error message the valuation class for your material code should be 3000. Maintain appropriate GL account for Valuation Class 3000 in BSX key.
    Use T Code OBYC to view all the transaction event keys. Scroll down to BSX which might be 11 th in the list, and double click on it. You will find a combination of Valuation modifier, Valuation class and GL Account. Please mantain appropriate GL code against valuation class 3000.
    If you are not confident enough you can take the help of your MM consultant.
    Regards,
    Swapnil

Maybe you are looking for

  • Set Document Name

    Hi guys I'm using VS + C# for my Add-on I create my new document by this code: Document myDocument = myVisioApplication.Documents.Add("MyTemplateFile.vst"); and it create new document for me but the default name of this document is Drawing1.vsdx , Dr

  • Same BO is getting invoked for Pur. Order, Schedule Agreement and Contract

    Hi All, My Scenario is like this: For Purchase order, Scheduling Agreement and for Contract the Release Statergy are same. For these three scenarios i have created 3 different workflow templates. My Purchase order workflow is working fine. My problem

  • Is there metadata of any kind on an export file that shows me the project file from where it was created?

    Is there any way in looking at the meta data of a .MOV exported from Final Cut 7 that allows me to see what the project file was? I have this exported file, but I can't locate the original project file from where it was from. Was hoping there would b

  • Chart - Adjust X-axis label orientation

    I have Crystal Xi version 11.0.0.1282. The labels on my X-Axis are oriented 45 degrees diagonally. Can this be modified? Thanks, Art

  • MapServer is not ready. Please try again later

    Hi I've been using MapViewer successfully in development but now i'm moving to production on a Solaris server and am having some trouble. The OC4J server is 9.0.3.1 and the mapviewer is the latest off of OTN. It deploys fine and the "welcome" page ap