Loss Management Loss Management
(transaction code /ISDFPS/MASS_LOSS) is a function for posting complete or partial mass losses that occur during transportation or in storage. In both cases, extensive follow-up activities can be required to clear losses caused when material is lost on a massive scale:
Determine the total loss if only part of the loss is known
Dispose of material that can no longer be used
Complete open documents from the procurement process
Replace material through new purchase orders
Create the corresponding accounting documents
Adjust the stock and transport information
Notify the persons involved (such as the demand planner or recipient)
Loss Management
offers a central point from which you can perform and monitor all follow-on actions caused by mass losses.
Note the following functional constraints:
You can clear losses from a
Warehouse Management System
(WMS) and
Logistics Execution System
(LES) for material that requires a serial number only if the serial number profile specifies serial number requirement at handling unit level. This is because you can manage serial numbers only with handling units in the WMS and LES.
With unpacked material or when saving serial numbers at delivery item level, the system can identify serial numbers only using the goods receipt document. As soon as additional goods movements have been carried out for the storage bin, unique identification is no longer possible.
You can post losses from transportations only if an inbound delivery exists.
For cross-system deliveries, the inbound delivery must exist in the receiving system.
You can trigger events in
Supply Chain Event Management (SCEM)
only using the Business Add-In
Adjust Loss Management
.
You must post losses in the corresponding system. Cross-system loss postings (for example, from an offline system to a central system) are not supported.
You must perform
Loss Management
in the system that contains the information about the warehouse structure. This means that you have to implement the function in the decentralized system when using a decentralized WMS and in the central system when using a central WMS.
You cannot change individual items manually (quantity changes) since the function is for mass processing.
In Customizing, you have to define the settings for posting losses. These settings include the movement type for scrapping, the cost center, and the data for the warehouse to which the material was originally to be posted.
In Customizing for
Defense Forces & Public Security
, choose
(view /ISDFPS/LOSS_CUS).
Starting with an initial object (such as a delivery or storage bin), all dependent objects related to the initial object are determined and displayed in a hierarchical tree structure with the lower and higher-level objects. You can explode the structure using the
Framework for Object Explosion
(FOX) and an explosion profile.
Below is an example for a shipment:
Shipment
-> Train
-> Freight container
-> Pallet
-> Material A
-> Material B
-> Material C
-> Material D
For stocks in a warehouse:
Stor. Loc.
-> Storage type
-> Storage bin
-> Material A
-> Material B
-> Material C
-> Material D
Based on an explosion profile that contains the parameters for a multi-level FOX structure explosion, you can make the selection for the materials to be scrapped using the following criteria:
Warehouse number
Warehouse number in combination with storage type
Shipment number
Delivery data for inbound or outbound delivery
Handling unit
Dynamic selection by object type (such as material, batch, force element) and corresponding object key (such as material or batch number)
Based on the selection criteria, the system displays a structured list in which you can select the losses to be posted. When you select a node, the system also selects all subordinate elements. When you deselect a node, the system deselects all the subordinate elements. You can save selected nodes by choosing the
Save
pushbutton.
By choosing
Post Loss
, you can post the relevant adjustments for the following masses losses:
Storage types and storage bins in WMS
Storage types and storage bins in LES
Inbound deliveries (stock in inventory management)
Inbound deliveries in WMS
Inbound deliveries in LES
Handling units
Parts of handling units (using transaction /ISDFPS/MASS_LOSS_HU)
A loss to be posted for a material is posted in the system as “scrapping.”
By choosing
Create PReq
, you can create a purchase requisition for the material lost (once for each item) to trigger the replacement process.
By choosing the
Display Log
pushbutton, you can display an application log in which all messages issued during the subsequent process are recorded.
If you use the
Supply Chain Event Management (SCEM)
application and have implemented the BAdI
Adjust Loss Management
, you can send a loss posting to SCEM by choosing the
Info
pushbutton.
You can also use transaction /ISDFPS/MASS_LOSS_HU to post partially scrapped handling units (HU) if these HUs were only partially lost. You define the selection here using the delivery data or by entering a handling unit directly. For the materials selected as lost, in a background step, the system first posts a goods receipt for the correct document update and then posts the scrapping for these materials. For the materials not selected, the system posts only a goods receipt.
You can use the Business Add-In (BAdI)
Adjust Loss Management
(/ISDFPS/BADI_LOSSMAN) to adjust
Loss Management
to meet your individual requirements.
With the relevant BAdI method, for example, you can:
Adjust the explosion result
Adjust the display list
Extend the field catalog
Create and send events in the
Supply Chain Event Management (SCEM)
application
Adjust the application toolbar
You can call this BAdI in Customizing for
Defense Forces & Public Security
by choosing:
(/ISDFPS/BADI_LOSSMAN).
For more information, see the BAdI documentation.
To call Loss Management from the SAP Easy Access menu, choose and then the following transactions:
/ISDFPS/MASS_LOSS:
Loss Management
/ISDFPS/MASS_LOSS_HU:
Scrapping of Partial HUs