Sr. Number Management issue for movement type 281

Hi,
Background:
I have a Material "PART1" with Serial no. profile "0001" and relevant for "back flushing".
This profile "0001" has the below controls in config:
MMSL - Maintain goods receipt and issue doc. - 02 - Optional. We cannot maintain "03", since this Material is relevant for "back flushing".
SDLS - Maintain delivery - 03 - Obligatory
With this config Serial no. is optional for all the Receipts, Issues and Serial no. is required for Sales Delivery/PGI. PGI will not be able to post without entering Serial numbers. All these are working fine as expected.
Issue:
User creates Delivery through T.code  CNS0 for a network (Projects) for the same Material "PART1" and processing the PGI. During PGI, system is not stopping to post PGI without entering Serial numbers (Allowing to post PGI without Serial Numbers.), even though this Material has Profile "0001" - SDLS - Maintain delivery - 03 - Obligatory.
Movement type issued by system during network related delivery is 281.(No Special Stock).
During this PGI process System is considering this Business transaction similar to MMSL( Receipt/Issue ) instead of SDLS.
Options / Solution for this issue u2013 to make this specific MMSL movement type as Serial Number required:
We can maintain the Serialization Parameter in the below 2 steps specific Movement type(281).
1.Define flow type groups
u201C0001u201D  -  MMSL u2013 REQ u2013 03 (Obligatory)
2. Assignment of Movement Type Group to Movement Type
281 u2013 u201CREQu201D
With this Config I can able to get the error for the Delivery movement type 281 (GI to Network), if Serial Number is not entered in the Network delivery, which fixes the Issue.
I can able to process other receipts/issues (except 281) without Serial numbers, which is also OK.
But I can able to maintain the Back flush values u201C2u201D in Material master.
We can NOT able to create new Material with Back flush values u201C2u201D and Serial no. profile "0001".
We are having lot of materials with Back flush values u201C2u201D and Serial no. profile "0001". For existing Materials we are getting error u2013 Serial number Management is not possible with back flushing, whenever we change any Plant data in Material master.
Kindly provide the solution to fix this issue.
Let me know if you need more info .
In Config T.code u201COPT1u201D can we replace the movement type 281 with 601 to fix this issue, instead of the above config (Movement Type Group step 1 & 2) ?
Thanks,
Kumar Arcot

Hi Srinivas,
Thanks for the answer. It helped in solving the problem.
thanks,
Anjani.

Similar Messages

  • Goods Issue for Movement Type 281

    Hi,
    Can anyone suggest me how to use MB_CREATE_GOODS_MOVEMENT to post goods for Mvmt Type 281.
    Please give me Sample data as i'm getting errors with data.
    Thanks in Advance,
    Anjani.

    Hi Srinivas,
    Thanks for the answer. It helped in solving the problem.
    thanks,
    Anjani.

  • BAPI to reverse Goods Issue for movement type 601

    Hi Everyone,
    Does anyone know of any BAPI that could be use to reverse Goods Issue for Movement type 601?
    I tried using BDC of transaction VL09 and was able to reverse the GI document successfully but the return message type was 'E' with unreadable message -
    Tabelle 'E' enth#t keinen Eintrag f# 'Ch 004 &'
    When I tried using BAPI_GOODSMVT_CANCEL, I get the error message 'E M7 130 Material document cannot be processed'.
    Best Regards,
    Junwen

    hi, Junwen!
    the following code works pretty well:
          fp_vbeln = vbeln_val.
          fp_budat = budat_val.
          fp_tcode = 'VL09'.
          fp_vbtyp = 'J'.
          CALL FUNCTION 'WS_REVERSE_GOODS_ISSUE'
            EXPORTING
              i_vbeln                         = fp_vbeln
              i_budat                         = fp_budat
            I_COUNT                         =
            I_MBLNR                         =
              i_tcode                         = fp_tcode
              i_vbtyp                         = fp_vbtyp
            TABLES
              t_mesg                          = it_mesg
           EXCEPTIONS
             error_reverse_goods_issue       = 1
             OTHERS                          = 2.
    luck.

  • MIGO - GR - Others -- Serial Number Not saved for Movement Type : 561

    Hello,
    I am trying to post good receipt-other ( for movement type 561) using MIGO transaction. I have specified all required data.
    Also depending on the item qty., I entered serial number in serial number tab.
    Its creating document successfully. However if I try to display same document using MIGO, serial number is missing.
    I tried to debug the code and I realized its not saving serial number itself.
    For other movement type its creating document with correct serial number.
    If I repeat same process using same data using transaction MB11 its posting successfully and I can see serial number using MIGO transaction as well.
    One more thing which I've noticed is when I post document using MIGO, Account assignment details are missing. However with MB11 I can see account assignment data too.
    Would be really appreciated if someone can help me on this.  I dont know If I'm missing any configuration part here.
    Thanks & Rgds,
    Nilesh

    Any help Experts?
    Nilesh

  • Post Goods Issue for movement type 351

    Hi experts,
    I need to perform a post goods issue for the movement type 351.
    which bapi we need to use? is it going to be "BAPI_GOODSMVT_CREATE" or something else.
    What are the information that we require other than movement type for performing post goods isue?
    Any pointers on this will be highly appreciated.
    Regards,
    Sajith

    Hi ,
    Thanks man.. Then where should I do that.
    Idoc is PORDCR102. Message type is PORDCR1.
    My requirement is to create a STO first in the user exit EXIT_SAPL2012_001 and then to perform a Post goods issue in the user exit EXIT_SAPL2012_003.
    Can u please explain it.
    Regards,
    Sajith

  • Issue with Return Delivery for movement type 262

    Hi,
    I have got a strange issue, the user is trying to do a MIGO Return Delivery for a material document using movement type 262, this he claims has been doing it for many materials. However when i go to the MKPF table i see the transaction Code field to be MIGO_GI for all the material documents for which he claims to have done return delivery. But under this transaction code we have only 4 options - Display, Issue, Cancel and Remove from storage.
    Now when he tries to do the return delivery for movement type 262 he get an error message "Check table T156N: entry RL 262  does not exist" , but this has been very well maintained in the table.
    Can you please let me know -
    If it is possible to do a return delivery for a movement type 262?
    If yes how to address the above error encountered.
    Thanks in advance
    Sachin

    Hi Sachin,
    If you think of return delivery to vendor with or w/o PO reference you can use movement types 161, 122, 124 as default settings.
    Movement type 261 means withdrawal against production order and its reverse is MVT 262. The latter can be used e.g. via MB1A (or you can make storno of a confirmation by 261).
    Are you sure your user is using the correct terminology ('return delivery')? Please check the material documents he/she claims to have booked as return delivery. (in MB51 you can get a list of all material movements of MVT 261 that belong to 'your user' and after that you can open the material document and check through which transaction the booking was made.)
    BR
    Csaba

  • BAPI_GOODSMVT_CREATE for movement type 161, issues in PO creation

    Hello Gurus,
    I am using movement type 161 with BAPI_GOODSMVT_CREATE in order creating a vendor PO based on the goods receipt posted with the BAPI.
    It works fine, nevertheless due to business requirements, I need to apply the following changes:
    - in SAP standard the order type is NB by default but in our case I would like to force another order type using the same range that NB. I guess this could be done by activating exit ZXM06U17 (MM06E003). Does someone could confirm it?
    - in our process, the purchasing group is not maintained at vendor level (LFM1-EKGRP) but as this field is mandatory in the PO creation and as this data can not be maintained in BAPI_GOODSMVT_CREATE, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
    - furthermore, our specific PO type should have a specific account assignement EKPO-KNTTP instead of the default value U, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
    Kind regards
    Chris

    Hi Priya,
    Just want to share with your guys how to fit this error in BAPI_GOODSMVT_CREATE.
      For movement type 161 of PO return you have to pass movement type 101 instead of 161
    goodsmvt_item-bwart = 101. After that standard function will determine 101 to 161 automatically and
    post that material doc.
    NOTE:
      In my case
      It just heppen only the FIRST time that you do movement with PO Return wich is needed to pass
    101 in stead of 161 but after that you can pass 161 the system will continue process correctly.
    Hope it help.
    Sayan.

  • Hide/Suppress Cost center field in MIGO and MB1A for movement types 551&552

    Hi All,
    Can anybody tell me how to suppress or hide the cost center field in MIGO or MB1A for movement types 551 and 552?
    I did below settings and it worked fine for only MB1A and for MIGO still it is showing cost center field.
    IMG > Materials Management > Inventory Management and Physical Inventory >Goods Issue/Transfer posting > Define screen layout > select movement type to change the option.
    Also I did gothrough the settings for Enjoy transaction (MIGO) there we have only option to make fields either  "Required entry" or "Optional entry" and we don't have an option to hide/suppress.
    Please advise or help me .
    Thanks in advance!
    Regards,
    Praveen

    Hi
    The cost center field is a required field in mvt type 551 as you are scrapping materials, some cost center will need to take the cost of this operation.
    Anyway, you first need to make the field as optional for example, before you move.
    One option is that you create a screen variant in Tcode SHD0 for MB1A, where 551 is setup as constant (with content) , and mark Cost center as invisible and assign this screen variant to a transaction in SE93.
    regards
    Sidi

  • Account modification key for movement type 643

    Hello Experts,
    I am reaching out to you today as I am in need of some info on Account assignment for Goods issue process. I looked at transaction OMWN or OMJJ for movement type based settings. I am running a business process ' Intercompany stock transfer order'. Goods issue movement on delivery reads 643(Goods issue for cross company), which is picking 'Account modification key' VAX.
    My requirement was how do I force system to pick VAY for 643 without overwriting VAX with VAY in OMWN transaction. Also there are several possibilities listed out for movement 643 alone. Appreciate if you could briefly tell me how system determines other parameters such as 1) Special stock indicator 2)Consumption posting 3) Value string & 4)Counter to determine 'Account modifier' in the customizing table V_156X_KO for Intercompany movement type 643.
    Additional info: Trigger is Stock tarnsfer order type NB. Subsequent process is VL10B for Delivery creation using type NLCC  and Intercompany invoice(IV) for shipping the goods to ordering company code. Then in the receiving company MIGO or goods receipt with reference to outbound delivery and fianlly MIRO or Invoice verification.
    Regards
    SG

    Valuation Structure
    Data on a material is valuated using the following structure:
      Valuation area
      Valuation class
      Valuation category
      Valuation type
      Material type
      Movement type
    Valuation Area
    Organizational level at which material valuation is carried out. You can define a valuation area as
    follows:
      Valuation area = company code
    All stocks of a particular material in this company code are valuated together.
      Valuation area = one plant
    The stocks of a particular material in this individual plant are valuated together. Stocks in
    other plants are not included in this valuation area.
    You define in Customizing the level at which valuation should take place.
    Valuation Class
    You group together different materials with similar properties into valuation classes so that you
    do not have to manage a separate stock account for every material.
    The following table contains examples of possible valuation classes:
    Valuation class Description
    3001 Colors
    3002 Paints
    3030 Operating supplies
    3100 Trading goods
    Which valuation class a material can be assigned to depends on the material type. You can
    define the following assignments in Customizing:
      All materials with the same material type are assigned to just one valuation class.
      Different materials with the same material type are assigned to different valuation classes.
      Materials with different material types are assigned to a single valuation class.
    MM - Material Price Change (MM-IV-MP) SAP AG
    Valuation Structure
    10 April 2001
    A material is assigned to a valuation class in the material master record. The system checks
    whether the material type allows the material to be assigned to the valuation class specified.
    The system refers to the valuation class of a material to determine which stock account to post to
    when a posting is made for this material.
    Valuation Category
    Criterion according to which split valuation is carried out:
      Procurement
    You can valuate a material differently depending on whether it is manufactured in-house
    or procured externally.
      Origin
    You can valuate a material differently depending on where it comes from (such as home
    or abroad).
      Status
    You can valuate a material differently depending on its status (such as new, used,
    repaired).
    You define the valuation categories in Customizing. A material is assigned a valuation category
    in the material master record.
    Valuation Type
    The valuation type specifies the individual characteristic of the valuation category, such as
    internal or external, in the case of Procurement. Within the valuation category Origin, you can
    define the different countries as the valuation types. You define valuation types in Customizing.
    You first determine all the valid valuation types for a valuation category.
    You define in the material master record which valuation types are allowed for a particular
    material. For every material subject to split valuation, you must enter all the valuation types
    allowed in the material master record.
    Material Type
    You assign every material to a material type when you create it. Examples of material types in
    the standard system include raw materials, operating supplies and finished products.
    The material type controls the properties of a material and which data must be maintained for the
    material. The following control features are important for valuation:
      Is the material managed by quantity?
      Is the material managed by value?
      Which price control type may be used for the material?
      Which valuation class can the material be assigned to?
    The system administrator can create or change material types in Customizing.
    Movement Type
    For every material movement, there is a movement type in the SAP System. The movement type
    controls the properties of the movement, for example, which entries you must make when
    SAP AG MM - Material Price Change (MM-IV-MP)
    Valuation Structure
    April 2001 11
    entering a material movement, and which updates are carried out when the movement is posted.
    The following control features are important for valuation:
      Does the material movement cause the quantity to be updated?
      Does the material movement cause the value to be updated?
      Does the material movement lead to postings in Accounting?
      Is the material movement relevant for LIFO/FIFO valuation?
    The system administrator can create or change movement types in Customizing.

  • Fld selection for movement type 601/ act 425000

    hi all
    When i try to do PGI for delivery, i am getting given below error.
    "Fld selection for movement type 601/ act 425000 differs for customer goods movement (015)" Please guide me to solve this issue. Rgds
    Madhavan

    Dear Madhavan,
    For mvt type 601,in OMJJ, customer field is set as optional.
    You can check this in OMJJ - mvt type 601 - field selections - Material management.
    Check in FS00 - the field status group assigned to GL account - 40005900, then open the attributes of that field selection group in OBC4, check customer field is suprresed.
    You can change either (suggest to check with FI consultant to change in field status group).
    Alternatively you can go to t/code se38 & run RM07CUFA program with variants to compare these two settings and make necessary changes.
    Hope this could help you resolve this issue. TQ
    rgds,
    nema

  • Create storage location automatically for movement type 261

    Hi Experts,
    Currently we're inprocess of implementing "create storage location automatically" for reservation, and I've done with the configuration for both reservation side (Define Default Values) and movement type side (GI/transfer posting - Create Storage Location Automatically).
    For movement type 201, new storage location successfully extended/created using T-Code MB21 (Create Reservation). But we found an error message while conducting the same thing for movement type 261 (which only can be created using T-Code IW31 (Create material reservation form Work Order).
    Did we missed any required configuration? Pls kindly advice on what we should do.
    Thanks a lot. Really appreciate the prompt response.
    Rgds,
    MD

    Here's the current situation,
    We configured the plant/storage view (SPRO), most of materials already extended to desired plant and storage location. Commonly, we can extend or create any materials for certain plant and/or storage location by maitain material master data (using T-Code MM01).
    Recently, we develop the additional configuration to activate "automatic create storage location" for reservation, aligning with the movement type for Goods Issue (201,221,261,301,etc).
    Let's say we have material number 123456789 and currently assigned to plant YYYY, but not extended to storage location XXXX. By performing T-Code MB21 (create reservation) with movement type 201 inputted, the respective material (123456789) is automatically created for the XXXX storage location.
    But the above condition is not effected while performing the same thing using T-Code IW31 (create material reservation via Work Order) with movement type 261 (GI for Order).
    Any idea to perform create storage location automatically while creating reservation for movement type 261? is there any possible configuration or procedure to be added?
    Thank you

  • Mov type 281 W

    Hi,
    The Goods Issue movement type 281 with special stock indicator W (Consumption for network from unrestricted project) is missing from standard solution. Does anyone know the reason?
    What will be the consequences if I create one? I would like to know any technical constraint or logical reason not to create this.
    Any details on this will be highly appreciated.

    Spe Stock ind W is assign to consignment for customer not Consumption for network from unrestricted project in the std system

  • Error during search for movement type (953)

    Hi All,
             When I'm trying to issue goods to an internal order, I get the below error
    Error during search for movement type (953)
    The explanation is as follows
    The movement type of the warehouse system and certain parameters are assigned to each movement type of the inventory management system
    In this case no movement type of the warehouse management system was assigned to the inventory management movement type used by the paramaters enclosed in parantheses in the eror message.
    Is there some config missing in this case?? Please let me know how to overcome this error
    Regards,
    Ashwin

    when you create new movement types in MM, then you certainly have to create WM movement types too, if you want use the new movement types to post at a warehouse managed storage location.
    This customizing needs to be done in IMG > LE > WM > Activities > transfers >  define movement types
    and
    IMG > LE > WM > interfaces > inventory management > define movement types

  • Field Selection error for movement type and G/L account

    I am currently experiencing a field selection error between movement type 601 and G/L account 7140000.  The problem field is 'Segment'.  This field is set to required for the G/L account, but it is hidden for the movement type 601. This inconsistency causes an error when posting the goods movement. According to business requirement the field must be required for the G/L account, therefore we must make this field optional for the movement type.
    However, in configuration the field segment does not appear for the movement type 601. Therefore it can not be changed to optional.
    Does anyone know a workaround other than making this field optional for the G/L account because the business requirement is to have this field as required?????
    Many Thanks

    Hi,
    On the Error message detail, system will guide you to the Configuration details for Field settings for Movement type & Account, please get in touch with your FI consultant, to make the Field selection for the account similr to that of your movement type, this is a very common issue.
    Regards
    Chandra Shekhar

  • Error in MB1C but works perfectly in MIGO for movement type 501.

    Hi
    I get an error in MB1C but works perfectly in MIGO for movement type  501
    here is the error Account 353300 requires an assignment to a CO object.
    I know for this if we add the co object in OKB9 it works.
    But my question is - how it works in MIGO transaction but throws an error in MB1C
    Any idea ? has any one faced this kind of an issue ? Please let me know.
    Thanks
    Dkmurthy

    Hi
    Are the entires same in both the transactions? Means did you check 353300  GL was hit when you posted through MIGO?
    Check in FS00 - for GL account 353300 - under bank/interest tab - double click on field status variant -> under Additional account assignments - CO object is ticked as mandatory?
    Thanks

Maybe you are looking for

  • Error when moving multiple emails from one account to another

    I have an IMAP account for one of my emails. I have recently changed web hosting and so changed this to a POP account. I don't want to lose all my emails, which is what happened to another one of my accounts when the web hosting was changed. So have

  • "Download Files"procedure not working in duplicate app/shows page not found

    Hello, I have created an application using the "Download files" procedure described in "How to Upload and Download Files in an Application" chapter of the APEX "Advanced Tutorials." It works just fine on the one server, however, when I exported the a

  • Problem in Database Configuration Assistant

    I did install successfully oracle9i(9.2.0) database program install Step but "Configuration Tools" Step is not work - Copying databases Files - oK. - Initializing database -ok. - creating and starting Oracle instance - still progress and it could not

  • SAP ABAP HR Consultants Openings  Sydney and in India

    Hi Sapians, Promentor Consulting is a Bangalore based HR consultants providing complete HR solutions to IT & Non IT clients across India & Abroad. One of our client is in need for SAP ABAP HR Consultants for thier Sydney office.  The consultants who

  • Primary Key for Read Only Entity Beans In EJB 3.0

    Hi, I have checked the spec for ejb 3.0 which mentions that, there is no common standard for the vendor to implement the Read only Entity Beans. My question over here is how it is implemented in OC4J?? Do we need to specify a primary key attribute in