Skip to Content

Issue in Serial number profile (URGENT)

Sir,

A material code code was created initially with a serial no profile XXXX, afterwards it was changed to YYYY, some prodction orders and GR has taken place with serial no profile XXXX. After changing the profile to YYYY, while doing Goods Issue for this material in MIGO , i am receiving the error message as follows

"Difference in object list header data: 261 previously / 321 new"

Also while doing Goods Receipt for the same material with reference to PO , i am receving the following error message

'

"Difference in object list header data: 101 previously / 321 new"

Unable to do GR and GI for this material , my serializing procedure for the profile "YYYY" in OIS2 is as follows

Procd Description Ser usage Eq.Req

MMSL Maintain goods receipt and issue doc. 02 01

PPAU Serial numbers in PP order 02 01

PPRL PP order release 04 01

PPSF Serial nos in repetitive manufacturing 03 01

QMSL Maintain inspection lot 02 01

SDAU Serial numbers in SD order 01 01

SDCC Completness check for delivery 02 01

SDCR Completion check IR delivery 02 01

SDLS Maintain delivery 02 01

SDRE Maintain returns delivery 02 01

How to solve the issue and what configurations shold i do for solving this issue

Kindly solve the issue

J.Balakrishnan

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Nov 06, 2012 at 12:26 PM

    We recently experienced this and the trouble shooting was as follows:

    This IO 308 error happens only for Serialised components in MIGO and does not allow any serialised components to be posted further. However we can do the posting through MB31 for instance for these components.

    Reason (Note: One of the reason and not the only reason) for the error being a component was initially with a Serialised profile and an obligatory serial number usage for MMSL procedure and later on the profile had been removed/changed. Later while doing a GI for the component the error comes up.

    Trouble shooting:

    An entry of the table SER03 exists with MBLNR = $ instead of an actual material document number. We must also change the temporary material document number in the field SER03-MBLNR to the actual material document number.

    The SER03 table has the Time and Date captured for the material movements. Pick up the date/time from this table and go to MKPF table and for this date/time we should be able to pick up the material document and then manually update the SER03 table.

    SAP recommends us to apply note Note 1602965 to prevent future errors of this sort.

    Apply the SAPnote to prevent the error of this sort after updating SER03 entry manually as above.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi, Have you updated the MBLNR value in SER03 table with the right one referenced from MKPF table? (Merely deleting the $ symbol will not help).

      To repeat the info, From SER03 table pick up the date/time and go to MKPF table and find the MBLNR. Populate the MBLNR in SER03 against the $ value which is there currently. This procedure will allow further Serial components to be posted using MIGO txn.

      Have seen you raising a query on JIT call summarization months back (hopefully it is you i presume) and can infer that you use ECC 6.0 with EhP5. The note mentioned 1602965 is applicable for your release. After implementing this note we have observed that any changes to the material's serial number profile at a later point of time do not cause this error again.

  • author's profile photo Former Member
    Former Member
    Posted on Nov 06, 2012 at 11:37 AM

    Hi Bala,

    I see the error has been created because of the missing data in this table. Try and see if it makes sense to you.

    T377X - Documents Allowed for Serial Number Management (IMG table)

    SER01 - Document Header for Serial Numbers for Delivery (Transparent table)

    In the table T377X,

    the field Object list header SER05 ( Document Header for Serial Numbers for PP Order )

    which is assigned to the field PPC1 ( serial procedure ) is not able to create an entry in the table SER01.

    This serial number profile and the Stock with serial will give you pain long way if do not remove the root cause immediately. It will be good if you can stop trying GR

    1. Reverse the confirmation

    2. Reverse the Goods Movement

    3. Check the Cost Balance in the Production Order is ZERO

    4. TECO the Order

    5. Remove the Serial Number Profile from the Workscheduling view of Material Master

    6. Re-create the Production Order and go ahead with the Process

    In your case if the stock is posted, Remove the Stock first by using MI10 and movement type 702. Once the Stock with Serial numbers are removed, the field should allow you to delete the profile of serial number

    http://scn.sap.com/docs/DOC-27498

    Check & revert.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 06, 2012 at 11:59 AM

    Dear Bala,

    Check whether OSS 734758 can help you in resolving this issue,

    Symptom

    You use Transaction MIGO to post a goods movement in which serial numbers are involved.
    In subcontract orders, the following symptoms have been noticed:

    • The posting fails with an incorrect error message concerning serial numbers, for example:
      • M7175 "Maintain serial numbers for total quantity",
        • IO304 "Only &2 serial numbers entered instead of &1",
          • IO308 "Difference in object list header data: &1 previously / &2 new"
          • The posting was successful, but the link of the serial numbers to the corresponding material document line is not correct. As a resutl, the system displays no serial numbers or the serial numbers of a different item when you display the serial numbers of a document item.

          In other postings, the following symptoms have been noticed:

          • After the posting, the master data of the serial number has changed. It was overwritten with data of a different serial number from the material document. This may affect, for example, the master batch of the serial number.

          Reason and Prerequisites

          The problem is caused by a program error and by Note 558991.

          Solution

          Use Transaction SE11 to add the following field to structure IMSEG2:
          Structure IMSEG2
          Component Component type
          ...
          XLBTYPE MIGO_LBITEM

          Activate the structures and implement the attached corrections.

          Regards

          Mangalraj.S

          Add a comment
          10|10000 characters needed characters exceeded

        Before answering

        You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
        You must be Logged in to submit an answer.

        Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.