Sled/BBD

Hello,
When i do a goods receipt with migo (in development) for not batch-managed ingredients i see 2 boes in the folder material:
Date of manufacture and SLED/BBD
When i do the same in our production system i don't see them. I am looking where this is set up but i don't find it. The field selection for the migo in customizing is the same.
Kind regards,
Bert

Hi all,
I found the problem myself.
You can fill in Rem. shelf life in the info rcord also.
This caused the extra fields.
All thanx for the help.
Kind regards,
Bert

Similar Messages

  • Inbound Delivery (DESADV): How to transmit SLED/BBD and Manufacture Date?

    Hello
    We have another challenging task to solve. Here is the scenario (SAP Release ERP 6.0):
    One Lindt company (supplier) sends an outbound DESADV IDoc to another Lindt company (Purchaser). Here the inbound DESADV should create an inbound delivery. Finally, the inbound delivery is replicated to the external WHS partner who does the Goods Receipt against this inbound delivery.
    The outbound DESADV contains all logistical data including SSCC. In particular, the batches have a manufacture date (LIPS-HSDAT) and a SLED/BBD (LIPS-VFDAT).
    SLED = Shelf Life Expiration Date
    BBD = Best-Before Date
    In the outbound DESADV the SLED/BBD is mapped by default into segment E1EDL24/VFDAT. For the manufacture date we implemented an user-exit.
    How does the inbound delivery look like? The batch number appears as "Vendor batch". The SLED/BBD does NOT show up even though the inbound DESADV contains the date in E1EDL24/VFDAT. This inbound DESADV did NOT contain any controlling segment E1EDL19. Adding this segment (QUALF = 'VDT' = Shelf Life Expiration or Best-Before Date) had no effect.
    Here is my assumption why the SLED/BBD does not show up in the inbound delivery created by the inbound DESADV:
    Because we do not yet have the "real" batch (just the "Vendor batch") the system ignores any SLED/BBD. As soon as the external WHS partner sends the GoodsReceipt message (as inbound WHSCON ) the inbound delivery is updated with the "real" batch as well as the SLED/BBD.
    QUESTIONS:
    (1) Why does the SLED/BBD not show up in the inbound delivery created by an inbound DESADV?
    (2) Do we need another user-exit to map the manufacture date into the inbound delivery?
    Once again thank you for sharing your time and expertise with us.
    Regards
       Uwe

    Apply SAP Note
    Note 1576788 - Transfer of exp. date
    (IDOC_INPUT_DESADV1) to inb. delivery
    Here are the correction instructions for your reference:
    =========================================
    FORM DESADV_IDOC_PARSE
    Delta001Context Block 
            IF NOT t_dlgn-vbelv IS INITIAL.
              t_dlgn-posnv = s_dl24-posex.
            ENDIF.
    Delete Block 
            mv s_dl24-brgew t_dlgn-brgew.
    Insert Block 
            mv s_dl24-vfdat t_dlgn-vfdat.                         "n_1576788
            mv s_dl24-brgew t_dlgn-brgew.
    Have fun!
    - Joemil

  • SLED/BBD in UD

    Dear All,
    During Usage Discision what is the purpose of SLED/BBD Date?
    Will it affect any inventory or any other transaction?
    Thanks in advance,
    Nirav

    You can change the shelf life date in the UD but the next inspection date is calculated from the date of the UD.
    I should have been a bit more clear on that comment.  The next inspection date is calculated form the production date when the material is received.  I was referring to the 09 inspection lots when I made the above statement. From an 09 inspection lot, the next inspection date is calculated from the date the UD is made.  Not from the last inspection date.
    FF

  • SLED - Mandatory in MIGO for Batch Materials

    Dear Gurus,
    I want to make SLED field mandatory in MIGO.For that , i have changed in OMJ5 and now SLED is mandatory in MIGO.
    But my requirement is , i want SLED mandatory only for BATCH materials.Now its asking mandatory for without batch materials also.
    Can u plz tell me, how to do that.
    thx in adv............

    HI,
    Do the following step.
    1. Goto Tcode OMJX - select SLED/BBD and double click and select req.
    2. T-code OMJ5 select movement type and select "Enter and check" (1) option
    3. Goto MM02 and select "Plant data / stor 1 " view
         tick the "Batch management" where is applicable batch and enter min. Rem. shelf life and total shelf life
         untick the "Batch management" where is not applicable batch and remove min. Rem. shelf life and total shelf life
    Try this it will be resolved your problem.
    Regards,
    PK.

  • WM - Report for stock with storage time

    Hi Guru,
    How can I get a report with material_name, quantity, and their storage time?
    e.g. part A putaway on 2008/1/1,  100 EA
    The report will show:
    material    Qty          storage time
    part A     100 EA     (2008/12/10 - 2008/1/1)
    We want to find out the stock which have a long storage time - dead stock.
    Thanks,

    Hi,
    Information that comes from WM can be misleading. Even if you have the stock long ago, WM movements may happen within the WH for that material (and this does not mean IM movement but the quant-data in WM may change).
    I think you should consider the use of dead stock and slow moving stock reports (MC46 , MC50). MC.A report can also be used to get information on goods movements.
    Of course, depending on your WM strategy and processes you can extract the necessary information. E.g. in LX02 you can see the GR date, SLED/BBD, the already mentioned last movement, last removal, etc - check the layout.
    Regards,
    Csaba

  • Error: LK047 Material movement could not be posted in the system via IDOC

    I am trying to create an article document (goods movement doc) for an already created purchase order.
    but this is via an IDOC (WMMBXY). after filling the data in WE19, i shoot the idoc in to the system. in we02 i get the following error message: LK047 Material movement could not be posted in the system . Can someone please help.
    the following fields are filled:
    Segment: E1MBXYH
    Document date        20091124
    Posting date         20091124
    Reference            9999999999
    Doc.Header Text      POS/1110
    Transaction code     MB01
    USNAM                user12
    Segment: E1MBXYI
    Processing ind.      1
    Material             832924
    Plant                1110
    Movement Type        101
    Debit/Credit     +
    Currency             EUR
    Qty in un.entry      250
    Unit of Entry        PAK
    Qty OPUn             90
    OrdPriceUnit         KG
    Purchasing Doc.      9100000141
    Item                 1
    Profit Center        11090
    G/L Account          22706
    Movement Type        101
    SLED/BBD             20091231

    Hello Shankar,
    Glad to hear from you!
    In your question, please make sure you use leading zeros for the MATNR field.  In header segment field E1MBXYH-BKTXT, we use header text. Hope you are using inbound posting function L_IDOC_INPUT_WMMBXY.
    Please try with this and it works for us.
    Thanks a lot,
    Venu

  • GR posting date is being considered as Shelf life expiry date

    Following settings made in material master:
    In Purchasing view: Batch management check box ticked.
    In Plant data / stor.1 view: (Shelf life data): Max storage period is 1, Time unit: YR
    Min remaining shelf life:1, Total Shelf life: 365, Period Ind for SLED: D
    Following data entered in GR:
    Document date: 10.03.2011, Posting date:10.03.2011
    In batch management tab of GR: Date of Manufacturing is :01.12.2010, SLED/BBD is appearing as 01.12.2011
    While taking shelf life report (on 12.03.2011) for the said material following output is displayed:
    Remaining shelf life             SLED / BBD
    -2 days                                10.03.2011
    In  batch display (MSC3N) Shelf life exp. date is appearing as 10.03.2011 where as in GR document it is showing as 01.12.2011.
    Kindly help where is the problem.
    regards,

    Hi,
    It is interesting.
    I understood the problem but for getting solution, you have to get ABAPeru2019s help. 
    In calculation in report, the report date 12.03.2011(DD.MM.YYYY) is taken by system as 03.12.2011(DD.MM.YYYY) and SLED is as per GR document 01.12.2011(DD.MM.YYYY). So 1-3= -2 days. Now, for calculating SLED date, system is deducting 2 days (or you can say adding -2) in report date 12.03.2011 (DD.MM.YYYY). So this is 10.03.2011.
    So in batch display (MSC3N), it is showing calculated date 10.03.2011.
    Please explain it to ABAPer & debug it, you will get solution.
    Before that try one thing. Check your user profile for date format. If it is MM.DD.YYYY, change it to DD.MM.YYYY, or vice versa. Then take report again , also check in MSC3N.
    BR.

  • Scenario - plz suggest how to move fwd

    Scenario:
    When we do GR , for a Batch i want to track the  Expiry date , manufacturing date, GR date, Shell life etc.
    eg medicines will come in huge qty in batch and we need to track it all .
    please suggest

    Thius is the report : The material got expired by 7 MONTHS. It is fine and Ok . But i want to know , a report with material will expiry on 10 months 2011.
         Material           Material description                     Plnt SLoc
            RSL        SLED/BBD    Batch      Unrestr.-use stock BUn
         9100000030         DOME TRADING                             KLP1 RSL1
             7- Months 21.04.2010  21                        33  EA
    9100000030
                                                             33  EA
    Total
                                                             33  EA
    Hope you understand

  • Status 51 -- Error: LK047 Material movement could not be posted in the sys

    I am trying to create an article document (goods movement doc) for an already created purchase order.
    but this is via an IDOC (WMMBXY). after filling the data in WE19, i shoot the idoc in to the system. in we02 i get the following error message (status 51): LK047 Material movement could not be posted in the system . Can someone please help.
    the following fields are filled:
    Segment: E1MBXYH
    Document date 20091124
    Posting date 20091124
    Reference 9999999999
    Doc.Header Text POS/1110
    Transaction code MB01
    USNAM user12
    Segment: E1MBXYI
    Processing ind. 1
    Material 832924
    Plant 1110
    Movement Type 101
    Debit/Credit +
    Currency EUR
    Qty in un.entry 250
    Unit of Entry PAK
    Qty OPUn 90
    OrdPriceUnit KG
    Purchasing Doc. 9100000141
    Item 1
    Profit Center 11090
    G/L Account 22706
    Movement Type 101
    SLED/BBD 20091231

    Hello Shankar,
    Glad to hear from you!
    In your question, please make sure you use leading zeros for the MATNR field.  In header segment field E1MBXYH-BKTXT, we use header text. Hope you are using inbound posting function L_IDOC_INPUT_WMMBXY.
    Please try with this and it works for us.
    Thanks a lot,
    Venu

  • Multiple Shipping notifications (Inb.Dlv) created via message type DESADV

    Hello All,
    I'm working on implementing the below SAP Standard process for my client. Version is SAP 4.7. The below process has to be implemented for different legal entities working on Same SAP environment.
    PO -> SO (Created via IDoc) -> Outbound Delivery -> Inbound Delivery (Shipping Notification) -> Invoice -> Invoice reciept.
    Most of the process are working, but facing few challenges while creating a shipping notification via message type DESADV and Basic type DESADV01 genereated out of Output type LAVA from Outbound delivery.
    I'm using 2 IDoc types to create Shipping notification via Outbound delivery and defined as below
    Outbound Process: Message type DESADV and Basic type DESADV01 with Process code SD05 for Customer (KU)
    Inbound Process: Message type DESADV and Process code DESA for Logical system (LS)
    I'm facing the following issues with respect to above process
    01) We need to update Batch Details like batch number, Date of Production, SLED/BBD in Shipping notification (Inb. Dlv) as Batches Instead of vendor batch
    02) When Outbound delivery has multiple line items, it is creating Multiple Shipping notifications (Shipping notifications for each line item). PO has
    As per the the threads posted here, I understand that for 01) We need to modify the Outbound IDoc FM "IDOC_OUTPUT_DESADV01" & Inbound IDoc FM "IDOC_INPUT_DESADV". But any idea, which Enhancements i have to use to fill the data?
    Also on point 02) i think, it should be a SAP standard to create a single Shipping notifications for all line items in the outbound delivery instead of each for line item. But in case if it is not a standard process, can any one tell me which user exits / enhancements to use to achieve the desired functionality.
    Appreicate your early response
    Thanks in advance
    Regards,
    Pradeep

    Hi,
    Why have you pasted Deepak Kumar's program into this forum?
    Regards,
    Nick

  • Batch splits in deliveries

    Hi all,
    I have to modify an FM to extract the SLED/BBD (expiry date) based on material and batch number, and move it to an IDoc segment. In addition i need to take into account batch splits in which case the earliest SLED/BBD will be moved to an IDoc segment.
    My question is given a delivery were can i check if a batch split occurred? And were will i find the different batches if a batch split indeed occurred?
    For the deliveries in which no batch split occurred i will be extracting the data from table LIPS.

    Hi Joseph,
    Not exactly.
    If the field value LIPS-UECHA is '000000' or the same line item number (let say '000010', in this case both the line item number (LIPS-POSNR) & LIPS-UECHA will be same)), then consider this line item as the master.
    Then chk whether any line item in lips with the same vbeln and LIPS-UECHA = '000010' (in this case LIPS-POSNR will have a different value as per the customization, normally in many cases it will be like 009000, 009001... or 000011, 000012...). If exists, then that line item have the batch split and get all the above line items.
    For instance, let say
    for line item ... 000010 will have 2 batch split with each 10 qty for the document number X, then in the lips you have 3 line items as below:
    LIPS
    VBLN        POSNR      LFIMG    UECHA
    X               000010      0            000000 (or 000010 which can be configured)
    X               000011      10          000010
    X               000012      10          000010
    Regards,
    Selva K.

  • Shortfall of 181 days against remaining shelf life in current item(18Month)

    Hi All,
             When performing a GR for PO, where purchase info record was maintained with minimum remaining shelf life of 18 M. On performing the GR, system throws up an error message 'Shortfall of 181 days against remaining shelf life in current item(18Month)', when the production date was entered 07/27/2009. What does this error message mean and how is the 181 days calculated ?
    Regards,
    PSS

    >
    PSS wrote:
    >When performing a GR for PO, where purchase info record was maintained with minimum remaining shelf life of 18 M. On performing the GR, system throws up an error message 'Shortfall of 181 days against remaining shelf life in current item(18Month)', when the production date was entered 07/27/2009. What does this error message mean and how is the 181 days calculated ?
    First understand concept of minimum remaining shelf life.
    Minimum shelf life does not has direct relation with info record. It comes from/ system calculate it based on Material master --> Plant data/ storage 1 --> Field name: "Minimum rem. shelf life". It shows - Minimum amount of time for which the material must keep upon GR for the goods receipt to be accepted by the system.
    In Material master --> Plant data/ store 1 --> Field name: "Total shelf life".  It shows - "Period for which the material will keep in total, that is, from the date of production to the shelf life expiration date"
    Now at the time of GRN once you enter Date of manufacture then base on material master --> total shelf life system will calculate "SLED/ BBD".
    Based on this calculation system through this message of "shortfall of 181 days".
    If you still have confusion please let me know what you have entre in material master --> for minimum rem. shelf life & total shelf life. So I can reply you with exact calculation.
    Hope this helps.
    Thanks!!!

  • QA11...Inspection Lot Stock Posting *RQEVA-SGTXT01*

    Hi All,
    In QA11, on the inspection Lot Stock tab, i m posting some qty for restriction, scrap n all...
    i want to know where the item text (RQEVA-SGTXT01)is stored for this..  on which table this is stored..???
    Thanks n Regards
    Aravindh Mani

    Thanks For ur Reply.
    U r talking about the Long Text of Usage Decisions...
    But i want to know the text typed in "To Be Posted" Under "Inspection Lot Stock" tab.
    U can Post the Quantity for
    To scrap             0.000
    To sample usage      0.000
    To blocked stock     0.000
    To new material      0.000
    To reserves          0.000
    Return Delivery      0.000..
    While posting every Qty a Small window Appears and asks for
    Reason for Mvmt
    Text   (this is the text we enter) ..... i want to know where this text is stored
    SLED/BBD ...(some date format)
    Hope u understand my requirement..
    Thanks n Regards
    Aravindh Mani
    Edited by: Aravindh Mani on Jul 17, 2009 12:16 PM

  • QM Daimonds

    can any body help
    I developing one ALV Report  for raw materials, in raw materials all are  managed batches,so after completion of resultrecording in usage decision i enter the  the sled/bbd date.same  date i want to  report  but there is no related table any body done this thing help which table ur suggested  to developer.

    hI
    can you not use
    MB5m or BMBC ??
    Regards
    Suit

  • Err. during GRN

    Hi,
    I'm getting err. message during making GRN against PO no.
    Err. are
    1. batch xxxxx has already been posted in stock
    2.batch xxxxx has already been posted in stock
    3.Shortfall of 56 days against SLED in current item (20.05.2008)
    Kdly any guide me to over come this.
    thks & regards,
    G

    in my GR
    initally for one item
    date -f maf. = 10.05.2008
    SLED/BBD = 13.05.2008
    and other not mentioned anything
    it tried by changed the SLED date as 10.08.2008
    it gives err. like-
    SLED of batch xxxxxxx (13.05.2008) does not match the SLED of the current item (10.08.2008)

Maybe you are looking for