2009 Oct 09 1:07 PM
Dear experts ,
we have a scenario in spare parts operations , recording of lost sales . Best example is ..non aviability of material at delars end and which to be recorded , against customer . This part is new to dealership also means dealer dont have master for this part.
How to record this lost sales with reason ... part is not aviable, part is damaged, part not found etc.
At the end of month parts department abel to genrate a part number list with its prices and its sumation to know exact figure of lost sales.
Kaustubh
2009 Oct 12 1:54 PM
Hi Kaustubh,
In my opinion the best is to use the item reject functionality which is part of the DBM delivery. With that function the rejection reason will be stored on item level and the item is not longer relevant for that order. Via an own report or an own SAP Query you can create a list with several information.
Regards
Wolfgang
2009 Oct 16 6:41 AM
Thanks Wolfgang ,
i have tried with it , problem is with reject item action is , any one can change the " status reject item " in to approve the item.
can we control the authorisation based on " reject item status " and " approv item status "
regards,
Kaustubh
2009 Oct 16 9:21 AM
Hi,
The standard authorisation checks do not cover the rejection functionality however you could easily create your own object and perform a check within a BAdI or custom action.
There are a number of ways you can do this technically - one solution would be to copy the ITEM_REJECT action and perform a custom check on the setting of a rejection indicator within the execution BAdI. Alternatively you could remove the ITEM_REJECT function from the item screen and have your own screen to capture/set the rejection code and record additional information such as a follow up date, reason why the customer didnu2019t want the item etc
In my experience I have found that it isnu2019t the technical aspect of something like this that is the challenge but functionally and from a business perspective defining at what stage something constitutes a lost part sale.
Regards, David
2009 Oct 21 9:55 AM
Hi Kaustubh,
to enable a simple authority check you can use the existing authority object /DBM/ORDER.
The following fields can be used to check the authorization:
Activity
Plant
Sales Organization
Distribution Channel
Order Type
Action in Order Control
Division
If this is not enough you can create an own prepare implementation to check additional thinks and decide if the user is allowed to execute the action. To copy a standard action is not recommended because in that case you are responsible for that copied code and all changes what SAP delivers are not implemented automatically.
Regards
Wolfgang
2009 Oct 21 10:41 AM
Hi wolfgang,
thanks for object for order , but if i created a order and saved with item reject status .
Some one may able to open it from edit mode and change the status " item approve "
i understand those item reject and approv are item level DBM actions only correct if i am wrong ?
can i restrict that ITEM APPROVE status to be non executable with proper authorisation ?
its a specific authorisation with this item approve push button.
Regards,
Kaustubh
2009 Oct 21 12:32 PM
Hi Kaustubh,
I don't know the action ITEM_APPROVE because it's not a standard action. But I expect that all these process steps are actions. If this is the case then you can use the authority object /DBM/ORDER to create a role that defines the validity of an action.
For example:
Order Type 2000
Action in Order Control ITEM_UNREJECT
Activity
Division *
Sales Organization *
Distribution Channel *
Plant 0001
That defines that the action ITEM_UNREJECT is allowed within the plant 0001 and the order type 2000. That role you can assign later to a user.
Regards
Wolfgang
2009 Nov 09 5:49 AM