Skip to Content

Inbound delivery created as E stock Based on UD code - LOBM_UDCODE

Hello Experts ,

We are using batch classification for SF materials and doing inspection of that SF material .

LOBM_UDCODE is added into batch classification ,

with current landscape we have S41709 ECC , EWM (9.5) system in place.

Issue i am facing is to move stock with STO ( type UBR ) of SF material from one plant to another plant .

-Material - M1 is having batch B1 with inspection lot and we make usage decision for lot and it has updated classification char. LOBM_UDCODE.

-this material after having UD in PLANT 1 need to move to PLANT 2 under STO -type UBR .

-To support UBR STO type we are changing batch B1 stock type to unrestricted and batch status is restricted so it can be determined and can be delivered.

-in STO , under delivery tab , the receiving stock type is mentioned as Q stock ( as i need to receive stock as Q stock under receiving plant for this batch )

- OBD created for STO - PGI is completed.

- now at the time of IBD system is moving the stock as Q but also with special indicator as E , which is stopping to create IBD with EWM.

Note - the Material M1 ,batch B1 is not special stock ,it is normal MTS material .

if i remove the UD code by MSC2N from batch class , then it allows to receive as normal stock but batch class is having ud code , it receives as E stock

i am not sure why system has determined and updated special indicator in IBD for STO based on UD code under LOBM_UDCODE ??

Can anybody help to figure out what is the issue while receiving stock as E stock ?

I have attached both images .


sto-image.png (275.6 kB)
ibd-image.png (264.2 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Jan 24 at 03:32 PM

    Interesting. No idea. :-(

    But you wrote a great question with proper detail and explanation! This is not seen very often!

    My thoughts on this:

    - Are you running any industry specific SAP solution? Like Pharma, Mining, Aerospace? If so, you might find a user exit or enhancement has been activated by the "solution" and it is triggering this.

    - I know of no impact the LOBM_UDCODE has on any functionality. My understanding has always been that it is for information only and can be used by the customer how ever they want. For instance, setting up batch selection strategies for customers. I give those with a GRADE1 UD to some customers, GRADE2 UD to others, etc. etc....

    But as far as I know, SAP in standard out-of-the-box vanilla SAP, the LOBM_UDCODE has no SAP provided impact on other areas. So I would definitely be looking for some type of enhancement or user exit.


    Add comment
    10|10000 characters needed characters exceeded

  • Jan 29 at 05:42 AM

    Thanks Craig , i am checking if any user exit is having code for such a behavior.

    I will update with my findings for this issue .

    Craig if you have time , can you share your comment about another issue i am facing with QM and EWM integration , it will be great help .

    Thanks ,


    Add comment
    10|10000 characters needed characters exceeded