- Sap Serial Number Management .ppt
- Sap Serial Number Management Configuration
- Sap Sd Serial Number Management
Sap Serial Number Management .ppt
Sap Serial Number Management Configuration
Serial Number Management (LO-MD-SN) SAP AG Serial Number Profile 6 April 2001 Serial Number Profile Definition A group of data, summarized by a four-digit identification code, that defines the conditions and business procedures involved when assigning serial numbers to items of material. Dec 18, 2012 In Quality Management, results recording can be done against each serial number and while taking usage decision, posting will be done for the material against the serial number. Serial Number profile: Serial number profile four-digit key it defines how and under which conditions a serial number is assigned for a particular material. History of all inventory management transactions related to this serial number are visible by hitting the 'History' button Setting up - Configuration IMG Menu: Sales and Distribution Basic Functions Serial Numbers Determine Serial Number Profile - tcode OIS2 For every profile, one needs to specify the area in SAP where it will be used and how it will be used. Serial number usage: 01 - None 02 - Optional 03 - Obligatory 04 - Automatic Equipment required indicates if a equipment is. SAP serial numbers functionality helps managing serialized stock. It is mainly focused on tracking of inventory. Serial number is the number which is assigned apart from the material number in SAP MM in order to differentiate between individual pieces and other material items. MM Inventory Management Add comment 10 10000 characters needed characters left characters exceeded. Serial Number Management (LO-MD-SN) Serial Number Profile: Working With Serial Numbers: Serial Number Master Record: Creating Master Records for Serial Numbers: Serialization Data in the Piece of Equipment: Maintenance of Configuration Data.
Sap Sd Serial Number Management
We are currently in discussions as to whether to roll out SAP-WM or ask our logistics partner to implement their own system and interface with IDocs.
From a project team perspective the preference is for SAP-WM. However we store high value equipment that we track by serial number. In a number of our processes a specific serial number will be allocated to an order and as such we want to specifically pick that serial number and therefore need to know where it is in the warehouse.
HUM functionality seems overly complex and I'm not sure it even fulfills this need so we are currently proposing the following. Interested in if anyone has any alarm bells that say don't do it...
* Use the certificate number field ZEUGN to store our serial number
* Extend the field from 10 to 18 characters to cope with the length of the serial number and match the data length from SER01, SER02 including all structures and screen displays (its only on four tables and less than 100 structures and screens)
* When generating the TO have a section of custom code that checks if the material being picked is serial number controlled if a serial number has been provided in the delivery and find that quant in the warehouse and use that instead rather than the quant that would have been selected by the FEFO rules
* Amend MIGO to populate the serial numbers received into the certificate numbers in the transfer requirement so that the serial numbers are in the certificate numbers from the start of the process
I guess my main concern is changing the length of a SAP standard field. I seriously doubt however that this field would ever be amended by SAP. We are on 4.7 - does anyone on 6.0 know if ZEUGN is still 10 Char?
Any views appreciated,
Steve.