on 11-06-2012 11:15 AM
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
Also while doing Goods Receipt for the same material with reference to PO , i am receving the following error message
'
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
User | Count |
---|---|
109 | |
15 | |
10 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.