on 12-06-2012 11:04 AM
Hi,
I came across an issue where even though the status of serial number is ECUS, the stock information data still consists of data such plant, unrestricted stock etc.
When I checked the history of the serial number, I am able to see the delivery note to which this was assigned. but I am not able to see the PGI document details.
when analyzed further it is observed that system posted the PGI w/o the serial number, but update the status to ECUS.
I am not able to understand why system has not copied the serial number which was in the delivery note to the PGI-material movt document.
can any one help me understanding the root cause
Hi Guys,
Any inputs on this issue as this needs to be addressed on priority to the client?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you help us with following details to understand your current serial number process? Which will guide us to assist you effectively.
- Whether you have CS/PM configuration in place for serial number?
- In serial number profile, is Serial Number with/without equipment requirement?
- Also, can you let us know the movement type used for PGI?
If CS/PM configuration in place for serial number, then please check the Serialization Attributes for Movement Types.
Regards,
JP
Hi JP,
I am not sure what config you are referring by "CS/PM configuration in place for serial number"
Now to answ to your 2nd ques: Yes serial number is with equipment requirement
And for the 3rd one, we are using Z01-customized movt copied from 601
Also can guide with the spro path to check the Serialization Attributes for Movement Types.
Thanks & Regards,
Hi JP,
thanks a lot for your reply.
Below are the details you asked for,
In Serial Number profile:
Stock Check = 2-Inconsistencies in stock data->Error
And for Usage:
MMSL, PPSF, QMSL,SDCC, SDCR procedures have 03 - obligatory
PPAU, SDLS, SDRE have 02- optional
Also in your previous you were asking about Serialization attributes for movement types
Here in flow group GR is defined for another serial number profile, but the same was assigned to movt type Z01
Thanks
I feel Serialization attributes for movement types can be an issue:
It should be:
Define flow type groups
SerialNoProfile | Procd | Sno-MovemntType Group | SerUsage | EqReq |
---|---|---|---|---|
0002 | MMSL | GI | 03 | 02 |
Assignment of Movement Type Group to Movement Type
Mtype | SpecStock | Movmt ind. | Receipts | Consumption | Sno-MovemntType Group |
---|---|---|---|---|---|
601 | L Goods movement for delivery note | Normal receipt | No consumption | GI | |
601 | L Goods movement for delivery note | Normal receipt | E Sales order | GI | |
601 | L Goods movement for delivery note | Normal receipt | P Project | GI | |
601 | L Goods movement for delivery note | Normal receipt | V Consumption | GI | |
601 | E | L Goods movement for delivery note | Normal receipt | No consumption | GI |
601 | E | L Goods movement for delivery note | Normal receipt | E Sales order | GI |
601 | E | L Goods movement for delivery note | Normal receipt | P Project | GI |
601 | E | L Goods movement for delivery note | Normal receipt | V Consumption | GI |
601 | K | L Goods movement for delivery note | Normal receipt | No consumption | GI |
601 | K | L Goods movement for delivery note | Normal receipt | E Sales order | GI |
601 | K | L Goods movement for delivery note | Normal receipt | P Project | GI |
601 | K | L Goods movement for delivery note | Normal receipt | V Consumption | GI |
601 | Q | L Goods movement for delivery note | Normal receipt | No consumption | GI |
601 | Q | L Goods movement for delivery note | Normal receipt | P Project | GI |
As it's related to goods issue, it ought to be GI not GR.
Further check in table EQSE - Serial Number Records, whether you can see Material Doc.(WABELN) for your serial number(SERNR).
Any change to config will reflect in new documents.
Hope that helps.
Regards, JP
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
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.