DEFINE VALUATION TYPE IN  MIGO TRANSACTION.

DEAR ALL,
pls. guide me how to define the valuation type in material master and basic criteria for it. as well as i want to define this valuation type in migo transaction also.
pls. reply as soon as possible.... its urgent.
bst rgds,
rajesh

Hi,
Refer below link;
[Split Valuation|http://www.sap123.com/showthread.php?t=29]

Similar Messages

  • Change valuation type in MIGO

    HI Everyone,
    While creating a GR with reference to PO it peak up the valuation type field bwtar from the EKPO table normally. In my scenario i'm getting BWTAR from table LIPS. I have used a BADI(MB_MIGO_BADI).
    But now when i post the goods in migo transaction it throws an error saying 'Material document data and PO data do not match (Valuation Type)' . That means it re-checks the entry from the PO which is different from the value which we got from LIPS and throws the error.
    The movement type is 101 for outbound delivery.
    The requirement is to allow the entry with different valuation type as that in PO.
    Could this be achieved?
    Any help would be great.
    Thanks & Regards,
    Satyam Bhardwaj

    It is not possible to change the valuation type in MIGO. Instead I restricted the user at the time of GI to enter different valuation type. If the valuation type he entered during GI is different than that in PO, i ammend the PO at database level and also note that mcha table also needs to be updated with same valuation type.
    Thanks for your replies.
    Regards,
    Satyam

  • How to populate Valuation type automatically in transaction MFBF.

    Hi ,
    I have activated split valuation for Externally procured and In house manufactured material.
    For externally procured material i am able to populate valuation type automatically while doing GR.
    Now i want to populate Valuation type automatically while doing GR through transaction MFBF.
    I am having field to put Valution type. But i want to populate it Auatomatically in that field.
    Please guide me.
    Regards,
    Amit

    you can try this. not sure will it work.
    in the config for split valuation (u must be knowing path in SPRO)
    choose local defination > choose your plant( if not maintain then mantian that)>click on local categories-->
    and there maintain your default valuation type for the DVT InhPr
    for your selected valuatiuon category.
    i hope this should work.
    Assumption:  You have only one valuation category.and valuation type.
    Regards,
    Pravin Mukkawar

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

  • Valuation Type Defaulted in Transaction

    Dear all,
    I have given valuation types,one for local purchase and other for abroad purchase.In my transactions PO or GR i need to mention the valuation types manually.There is possiblity of selecting wrong types also.
    Is there by any means the system itself take the right valuation type(local or import) based on the vendor location.
    Regards,
    Milton.I

    it can be done based on vendor contry key
    IN vendor master u give contry key
    say u r company is in IN india
    so any gr done for vender in india systenm will asign local purchase
    and purchase that is done other than india then import valuation type
    this can me achived onlyt by user exit in GR
    hope this helps u
    Reward accordingly

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

  • Badi for changing Stock type in MIGO transaction

    Hello ALL,
    IS there any BADI or EXIT for changing stock type in MIGO when we are doing GR against PO then we need to change the Stock type  to Unrestricted stock.
    Please let me know.Awarded if useful.
    Regards

    hi,
    Look into the BADI     MB_MIGO_BADI.
    or
    Exits:
    MBCF0009 Filling the storage location field
    MBCF0005 Material document item for goods receipt/issue slip
    MBCF0006 Customer function for WBS element
    MBCF0007 Customer function exit: Updating a reservation
    MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
    MBCF0002 Customer function exit: Segment text in material doc. item
    MBCF0011 Read from RESB and RKPF for print list in MB26
    Sirish

  • Defining output type to a transaction

    Hi friends,
    1) I have a transaction VF02.
    I have created two smartforms for this transaction.
    While issuing output in VF02. i can find only one output type RD00.
    i also want to include ZD00.
    2) is it possible to create our output types for any transaction. if yes , how to do it?
    thank you,
    kat.

    Hi,
    Is the out put types already available, if yes then just use VV31 to create new condition record for billing types and sales org.
    Alse you need to follow the below steps,
    SPRO-Sales & Distribution-> Basic Functions-> Output Control-> Output Determination-> Output Determination Using the Condition Technique-> Maintain Output Determination for Billing Documents-> Maintain Output Types, Maintain Access Sequences, Assign Output Types To Partner Functions, Maintain Output Determination Procedure, Assign Output Determination Procedures.
    Once it is done use VV31 to create condition record.
    Just an example below:
    Check this hope it helps, select the meduim 1 print instead of edi. hope it helps..STEP 1: Output Type Config
    Create Z810 output type with access sequence key Billing Type  Sales Org  Customer. Z810 is based on the SAP standard RD00.
    The following steps are executed in the IMG at the following path:Sales and Distribution -> Basic Functions -> Output Contrl -> Output Determination -> Output Determination Using the condition technique -> Maintain Output Determination for Billing Documents
    1.       Create Condition table (Tx: V/63)
    ·         Table 950
    ·         Description Bill.type / Sales org. / Bill to
    ·         Selected fields Billing type, Sales organization, Bill-to party
    2.       Maintain access sequence (V/54)
    ·         Access sequence ZEDI
    ·         Description Bill.type / Sales org. / Bill to
    ·         Access Table 950, Exclusive
    ·         Fields:
    o        FKART, KOMKBV3, FKART
    o        VKORG, KOMKBV3, VKORG
    o        KUNRE, KOMKBV3, KUNRE
    3.       Maintain output type (Tx: V/40)
    ·         Output type: Z810
    ·         Description: Invoice
    o        General data:
    §         Access sequence: ZEDI
    §         Check: Access to conditions
    o        Default Values:
    §         Time: 1
    §         Transmission medium: 6
    §         Partner function: BP
    ·         Processing routines:
    o        Medium: 6
    o        Program: RSNASTED
    o        Form routine: EDI_PROCESSING
    ·         Partner functions:
    o        Medium: 6
    o        Function: BP
    4.       Maintain Output Determination Procedure
    ·         Procedure: V10000
    ·         Control data: Insert step 11: Condition type: Z810 after RD00. No requirement
    5.       Assign output determination procedure (V/25)
    ·         Doc type: ZF1
    ·         Output procedure: V10000. Clear output type => Either RD00 or ZD00 can be used
    STEP 2: Condition Record (VV32)
    The table below shows the values for the condition records.
    ·         Part Fn: Partner function
    ·         Med: Transmission medium
    o        6 = EDI
    ·         Time
    o        Timing = 1 implies that a background job (running program RSNAST00) will process the output.
    o        Timing = 4 implies that the output will be created immediately on document save.
    Thanks & Regards,
    Nagaraj  Kalbavi

  • BATCH and VALUATION TYPE

    Dear All,
    Can anyone, please explain me clearly the difference between BATCH and VALUATION TYPE in MIGO and PO screen?
    What is the link between them ? pls explain in detail....
    Edited by: Raju on Nov 17, 2008 8:02 AM

    Hi,
    There's a link between both which is the indicator "Valuation type is set automatically". It can be set at the global or local (plant) valuation category.
    When you set this indicator, it means that each batch itself represents a valuation type (individual batch valuation). In other words, a valuation record is created automatically for each batch at Goods Receipt.
    -Edited-
    Example scenario:
    I activated batch management at plant level for material A and also activated split valuation. For this material, I produced the first batch (100pieces per batch) with certain characteristics. This batch is valuated at $100 per piece. I do a Goods Receipt against Production Order.
    Then my next production batch has better characteristics, so I wanted to valuate a piece slightly higher. With the indicator "Valuation type is set automatically", I can set a different price for this second batch during Goods Receipt from production (because a different valuation type is created for this).
    So I make use of batch management to manage my different sets of 100 pieces due to the slight different characteristics during each production run. I also make use of split valuation and the above indicator to valuate each batch separately.
    Hope this helps.
    Thanks
    Edited by: Han Lun Chan on Nov 17, 2008 9:59 AM

  • Archiving material master valuation type

    Hii ,
    I am trying to archive material master valuation type using SARA transaction   . Material is maintianed as FERT in system and we have created its valuation type as HM .  Now we are trying to archive this material master HM view .
    But it is throwing us error as :
    MBEW: 1501 HM Dependent batch stocks exist
    MBEW: 1501 HM dependent batch records exist
    We have checked stock in system .... No stock present (Tried  MMBE  , MC.9 , Table MBEW ) .
    How can I delete ths material master ? Where can I find stock ?
    Regards ,
    Pallavi .
    Edited by: Pallavi Deshpande on Jun 10, 2009 10:44 AM

    Hi,
    Archiving the Material Master
    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.
    A D V E R T I S E M E N T
      All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record. 
    You have to Flag the material master record for deletion. This is known as logical deletion. 
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
    Some of the archive error log message :-
    Costing data exists
    Use in routing
    Use in sales and distribution
    Use in bill of material
    Delivery exists
    Costing data exists
    Info record exists
    Purchase order exists
    The Archiving steps :-
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
    Thanks
    Prashanth

  • User-Exit in ME21 for Valuation Type

    Dear Sir,
    We are split valuation for the purpose to distinguish between Import Purchase vs Indigenous Purchases . Accordingly we have defined Valuation Types also .
    In ME21n we use differnt document type for Import & Domestic Purchases . We are looking for a User-Exit to have a functionality so that incase an Item in PO is classified as Split Valuation (as per Material Master) then Valuation Type must be automatically populated as per the criterion (say incase Document type is ZDOM then Valuation Class is "IND" and if Document Type is ZIMP then Valuation Class is "IMP") .
    Please guide me , how to address the above problem .
    Regards
    B Mittal

    Dear Mittal,
    You can use exit EXIT_SAPMM06E_012 --> ZXM06U43 , than add all needed logic there. u can take a little help from abbaper.
    Regards,
    w1n

  • User defined Catalog type u0093Su0094  - Valuation code field missing

    Hi Quality Experts,
    I have created a user defined catalog type in customization coping the catalog type 3.
    This is required for authorization purposes.
    Transaction Code : QS51.
    For system defined catalog type 3, in QS51 all fields are visible.
    Hence selection set can be created.
    For user defined catalog type S which is a copy of 3,
    for the same transaction code QS51 many field are hidden.
    Hence selection set can not be created.
    15 Columns are existing.
    S.No     System defined Catalog Type "3".     User defined Catalog Type "S".     Remarks
    1     Code Grouop     Code Grouop     OK
    2     Code                      Code                      OK
    3     Short Text for Code     Short Text for Code     OK
    4     Long Text for Code     Long Text for Code     OK
    5     Valuation Code     MISSING                     THIS FIELD IS MISSING
    6     Quality Score     MISSING                     THIS FIELD IS MISSING
    7     Posting Propasal UD     MISSING                     THIS FIELD IS MISSING
    8     Long Term Char.     MISSING                     THIS FIELD IS MISSING
    9     Stock Screen
                    Backgr.                    MISSING                     THIS FIELD IS MISSING
    10     Follow up action     MISSING                      THIS FIELD IS MISSING
    11     Short Text      MISSING                     THIS FIELD IS MISSING
    12     Changed By     Changed By     OK
    13     Changed On     Changed On     OK
    14     Created By     Created By     OK
    15     Created On     Created On     OK
    ===========================================================
    Total  7 fields are missing.
    SAP Version : SAP ECC 6.0
    Please guide.
    With Best Regards,
    Raghu Sharma.

    Hi
    when you have created new Catalog type by copying 3, did you check whether Selected Sets is flagged in the configuration?
    regards
    Srinivas

  • Define event types in Customizing and restart the transaction.

    how to define event to restart the transaction in BADI
    I have given error message in badi. it is giving
    No SAP Event Management communication for events; no event types def
        Message no. /SAPTRX/ASC084
    Diagnosis
        You have not defined event types for the business process types.
        therefore not possible to communicate event data to SAP Event
        Management.
    System response
        The communication of event data is aborted.
    Procedure
        Define event types in Customizing and restart the transaction.

    Hi Kevin,
    What DataSource does your testalias refer to?
    - If it is a custom DataSource, you must have created this custom DataSource also.
    - If it is the default DataSource, you shouldn't have this problem in general...
    In either case, you can try deploying your DataSource and/or DataSource alias together with your application:
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/07d2eeea3e0485e10000000a155369/frameset.htm
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/c82cd460a42e96e10000000a155369/frameset.htm
    I hope that helps!
    Regards,
    Yordan

  • Fields in MIGO - BATCH and Valuation Type

    Hi all,
    I would like to know the meaning of the following fields in MIGO.
    BATCH - Charg
    Valuation Type - Bwtar
    Which is the impact of each field?
    Should they have the same value in TRA MIGO?
    Which means that only the BATCH field is entered and the Valuation Type empty?
    Thanks you very much!!

    valuation type  comes into the game If a material is subject to split valuation.
    you can for example split the valuation based on origin, e.g. internal produced and external procured.
    this is more a financial thing.
    the batch is the level to segragate the stock of a material. e.g. each GR can be a new batch. so you can manage the stock by FIFO rules and by shelf life.  this is a logistics thing.
    Both can be used on their own, or together.
    if you want manage your materials by batches, but dont need split valuation, then you only have to take care about batch number, and the valuation type field in the batch record stays empty.
    if you manage material by batch and you use split valuation, then the split valuation type is a mandatory field in the batch record and you may have to enter batch and valuation type, but usually the valution type is defaulted from customizing.
    The tricky part is if you only use split valuation, because then the valuation type becomes the batch number. this is sometimes a bit confusing.

  • Valuation type to be copied in MIGO from STO

    Dear all
    I am creating a STO (doc. type UB) and i am entering a material with split valuation. I define the valuation type, but during the Goods Issue against the STO the valuation type is not copied.
    please let me notice, that i am using the STO scenario without deliveries etc. Just STO and Goods Issue in transit and then GR.
    BR

    Hi,
    Do refer the below OSS Notes,
    The valuation types in PO line item will be carried to receiving stock and not issuing stock..
    66953 - Stock transport order for split-valuated material
    801097 - Stock transport order with split valuation

Maybe you are looking for