Incident Management - changing doc-status after action SOCM_COPY_DOCUMENT

Hello,
in sppfcadm I've created a workflow handling new SAP-incidents. Everything works fine, but there's one problem: the user should have the possibility to create an urgent correction. With action SOCM_COPY_DOCUMENT the user can do this. After choosing this action and saving the support message, he can have a look with button [Document Flow] to the new generated document. In the new document everything is fine and all contents were correctly copied.
Problem: The status of the incident doesn't change, because the action SOCM_COPY_DOCUMENT only creats a new document. In a second step the system should automatical activate action "Sets user status according to container element USER_STATUS". But where can I do this? Adding a second "Method Call" in "Assigned Processing" in transaction SPPFDETCRM doesn't work. The system only calls the first method.
So, what I want to do is to combine two actions: "Create Change Document" + "Change Status of Document"
I would be grateful if somebody could give me advise.
Thanks,
Ralph

Hi,
Create your own PPF Action with the Coding of both actions and it should resolve your requirement. Only with customizing you would no reach what you want, you need ABAP to do this.
Regards
Abosi

Similar Messages

Change material status after creating SO

Hi Guru,
i have created a sales order with material 'DCC001'.
after creating the sales order the STATUS of material 'DCC001' should be 'Sales not allowed'.
but, when i am checking the status of that material, its showing blank in field 'X-distr.chain status' which is in tab 'Sales: sales org. 1'.
Please tell me how can i change the status after creating SO.
Thanks & Regards
Sohel

Please post in correct forum..

" Changed " Design Status after deployment involving two runtime reposiory

Hello everybody,
I'm experiencing severe metadata management problems in OWB 10.1.0.2.0.
When I deploy a mapping into the production runtime repository , it appears with a "changed" design status when I switch back to the development runtime repository.
If I can't rely on the design status it will be a nightmare to manage mapping delivery !
Anyone can share his experience about managing multiple runtime repository ?
Best regards,
Franck.

Hi Franck
Looking at your single design repository that deploys to two runtime repositories; I would say when you switch the runtime, it updates internally the default connected runtime for the mapping. As you will remember you can deploy straight from within the design browser if you have previously set the deploy mode. It will be updating this.
Not much you can do, except create a different design repository. It is somewhat poor I know. I raised a number of TARS on this myself. Perhaps they improved it in Paris (but I somehow doubt it.) Multiple database deployment configuration should be in there but so should real user based functional security and versioning(via the frontend without script repository hacks).
Too sum up, nearly all sites use the multiple design repository approach.
Regards,
Richard Harrison

Changing doc. type after creating a doc. type.

Hi Friends,
We are doing our time ageing from the time of creating the document in DMS. We created a document with particular doc. type wrongly, after two days we found that the DMS creation was done with wrong doc. type. In this how to transfer to new correct doc. Type, if we delete this & create a new we canu2019t get any info that it was created two days back.
We made Z report for this time ageing report.
Regards,
Sai Krishna

You cannot change the document type after the document has been created. The only way to do this would be with an enhancement and this would create major issues with the integrity of your system

Is it possible to change 'billing status' after making credit memo request?

Hi. This is Kwangkyun Choi from Samsung SDS in Korea as a SD system operator.
Our system can make billing documents from contract without making sales order and outbound delevey.
And the contract can use milstone billing.
When we make billing document using contract,
one of the milestone billing item's 'billing status' has been changed from A (Not yet processed) to C (Completely processed).
And also when we cancel the billing, the status has been changed from C to A.
BUT,
When I make CREDIT MEMO request referenced the billing document,
at that time the 'billing status' doesn't changed.
It was still 'C (Completely processed)'.
I want to change that value 'A'.
Is there any methods to solve this problem?
I couln't find any solution using customising IMG setting.
PLZ help to solve this problem.
Best Regards.
Edited by: Kwang-Kyun Choi on Oct 13, 2009 10:45 AM

Hello,
Let me clear my thought on this issue related to Billing Status of the Billing Docoument. You want to change the billing status of billing document to not yet processed after you have created a credit memo request. If this is the case then my explanation would be as :
when billing document is generated and then Accounting document is also generated, the billing status is fully completed. Nothing is rejected here nor nothing is left over. When you are creating a credit memo request, which is of course created with reference to Billing document then the billing status under no circumstances can change to "not yet processed" as the billing process is completed. Morever you are creating the credit memo request to adjust payment for the cusotmer.
Hope this helps to understand !!
Regards,
Sarthak

Change message status after release purchase order

Hi,
I'm a newbie in MM...
When a purchase order is created, the message status is not processed (yellow light) until the purchase order is released. Then the message is printed and the status changes to green light.
As far as I see, I can't find in the spro where is this customizing set or if there is a user-exit or badi for changing the message status depending on the release indicator.
Thanks in advance!
Jen

Hi Jen,
Complete the condition record, for example, like this:
- Transaction: MN04
- Output Type: NEU
- Choose third option: Purchasing Output Determination Document Type
- Document Type: NB
- Function: VN (Vendor)
- Medium: 1 (Print output)
- Date/Time: 4 (Send immediately (when saving the application))
Select the line and press button "Communication". Complete the output device and mark the option "Print immediately"
So, when the PO is created the system generates the message with yellow status. Then, when the PO is released, the message status will be green
Regards,
Fernando

How to change the status of an incident, after it is "Confirmed"

Hi, I'm new to ITSM and the client asking me how he can change the status of an incident, after he change it to "Confirmed". Is there a way to change the status of an incident after it is set to "Confirmed"? Or can I change the configuration of the Status field to allow that change?
Thank you

hi
I dont think, you can reopen the confirmed ticket by standard, but please try with the report CRM_SOCM_SERVICE_REPORT.
if not try with the status profile customization, remove the FINI settings from the confrimed status also change the highest and low values also accordingly.
please try.
Thanks
Jansi

Back dated action which is changing the status ' inactive'

hi friends,
my requirement is as below :
i want to insert back dated action which is changing the status as inactive ( currently he is active) .
System is not accepting to insert it and giving the message "   future action exists,check the status"
So for that first i am deleting all future actions and inserting the current action(which is changing status) and after inserting back all the deleted actions.
But the problem is as per the latest records in IT0000 it is showing currently the employee is in 'active' status(as we have inserted back the deleted records).
But i want to make him into 'inactive' status after the current action( which is changing status as inactive) is inserted.
This is my urgent requirement . an anybody respond to this immeadately.
waiting for ur reply.
thanks in advance.

Hi Gajesh,
                 The process is as follows :
1) During Calibration of a product,depending on the technician's User decision , 3 follow up actions are created.
2) Each follow up action has one FM associated with it, which is customised in      SPRO > Display IMG > Quality Management > Quality Inspection > Inspection Lot Completion > Define follow-Up Action .
3) In the first case ( first Follow up action when the inspection is successful) the first FM is triggered. In this FM we have to perform the following steps :
                               a) Determine the Maintenance Order and the equipment.
                               b) Incase both are available, status of equipmnt should be changed to 'A',
                                   Maintenance Order should be changed to 'Technically completed' and
                                   Maintenance Notification to 'Notification Completed' .
If you need further info pls let me know.
Thanks,
Vasuki

Changing the status of Equipment in a follow up action

Hi All,
           I have a requirement in which a function module will be triggered for a particular Follow up action.
In this FM we have to determine the equipment and the Maintenance Order , if both are available , status of the equipment
should change to 'A' , status of maintenance - order = 'Technically completed' and Maintenance Notification = 'Notification Completed' .
How can this be done.? I am able to change the status of Maintenance order and notification but can anyone help me in
determining the equipment and changing its status to 'A'. ?
Thanks in advance.
Vasuki

Hi Gajesh,
                 The process is as follows :
1) During Calibration of a product,depending on the technician's User decision , 3 follow up actions are created.
2) Each follow up action has one FM associated with it, which is customised in      SPRO > Display IMG > Quality Management > Quality Inspection > Inspection Lot Completion > Define follow-Up Action .
3) In the first case ( first Follow up action when the inspection is successful) the first FM is triggered. In this FM we have to perform the following steps :
                               a) Determine the Maintenance Order and the equipment.
                               b) Incase both are available, status of equipmnt should be changed to 'A',
                                   Maintenance Order should be changed to 'Technically completed' and
                                   Maintenance Notification to 'Notification Completed' .
If you need further info pls let me know.
Thanks,
Vasuki

Minimum steps required for Change Management and Incident management

Hello experts,
Does anyone have a check list of the absolute minimum steps required for getting Change Management and Incident management functioning in Solution Manager.
I just need it to function with creating changes and incidents and be able to assign them, change their status and close them.
The purpose is to get an idea if this is something for us to use. If we then find it useable, then we will go for a full scale implementation using official guides, education etc.
I just need an absolute minimum guide for demonstrating the functions, and if you guys have any recommendations, things we should pay special attention to or other experiences feel free to tell me.
Thanks in advance.
Regards,
Kenneth

Hi,
There are a number of Blogs in the SDN about Charm and ServiceDesk, explaining first steps and more.
Check these to start:
http://wiki.sdn.sap.com/wiki/display/SM/ChangeRequestManagement
The Complete ChaRM Solution
Change Request Management scenario: Usual questions and known errors
First steps to work with Change Request Management scenario in SAP Solution Manager 7.0
Regards,
Jan

Mail Notification after changing the status

Dear All,
We had configured the Service Desk in Solution Manager.But the requirement is when we change the status of the request (Suppose from New to In Process or from In process to Proposed Solution, there has to Mail Notification which is sent to the user, who has raised the issue.Due to which it helps to not to monitor continuously about the issue logged by him.
Kindly Suggest how to trigger the mail automatically after the issue status changes.
Eagerly waiting for the positive response.
Regards,
Amit

Hi,
You may have to do some Coding for this.

CHARM: two Change Managers in an solution manager - SDMN user statuses

Hi to all
I'm trying to handle two change Managers in the one CHARM client , each of them has own project and own system landscape for which he is responsible. I'm trying to restrict them, with well known charm authorizations of Change Manager, in a way that each of them should be able to handle just his own project and project assigned SDMN transaction type.
So far I've managed to restrict Change Manager to just one Task list with the authorisations object B_SMAN_WPL but this authorizations object is related just to the SDMN Task list but not to the User statuses of the SDMN transactions type!!
If you will restrict Change Manager role just to one task list (for example M*11) with the above auth. object (B_SMAN_WPL) it will be able to handle just this task through the SDMN drop down actions task "Go To Task List" no others task list should be usable. So in this case your Change Manager is restricted to just one Task list. Thanks to "B_SMAN_WPL"!!
But
....if the same Change Manager should go to edit the new SDMN transactions (for example with the task list M*22) , Change Manager should not be able to edit/change, the Task list itself (he is restricted by B_SMAN_WPL ), but it should be able to change User Status of corresponding SDMN! - To Move phases back and forth!?? How Come?
How can we restrict Change manager to be able to handle just SDMN - which belongs to the certain project that is defined inside of authorization object S_PROJ_GEN.?
waiting for SDN response )

I've just returned from the Hyperion conference here in South Africa. In one of the papers presented a BI consultant was using dynamically updated MaxL scripts to update dimensions and members within them. She had developed a VB front-end with MS Excel as the back-end. She was using the excel to pass parameters to the MaxL scripts and so controlling what was being updated on the model. The VB front end only allowed certain dimensions to be updated.Regards,Fraser

Can i Change/Update the Lead Status using Action profile of Activity.

Hi,
I have created one Lead, and on the basis of Qualification level action triggers and Ativity getting generated.
I want to know that it is possible by using functions(Action Profile/conditions) in activity, If i change the status reason of Activity (as Accepted) Earlier Leads status would change.(as Close)
Please resolve with solution.
Regurds,
Dipesh.

Hi Dipesh,
What I understand is, u wish to change the status of preceding lead transaction when the activity status reason is changed to accepted.
1. This functionality can be achieved using ORDER_SAVE Badi. This Badi implementation shall check the activity reason changed to accepted, if yes, read the doc flow, get the lead transaction and change its status to close.
2. As per my knowledge use of action profiles and conditions will not be helpful in this case.Else, create an action definition as Activity reason changed, put a condition which like Activity reason= Accepted.
In the action definition Processing type use method call.
Here u will have to create a new implementation of the BADI of action profile, and put the same logic as stated in point 1.
But in think implementing point 1 should be easier.
Wish the information is useful.
Regards,
Shalini Chauhan

PLM7.02: Status & Release Management/ Status and Action Management

Hello,
                I´d like to know if anybody worked with Status & Release Management. And has some example to how we can customize: SAM (Status and Action Management) in “Define Status Scheme” transaction.
                How it´s works the relationship with: Status: Attributes, Status: Field values, Scheme Definition, Attributes: Definition.
                I´ll appreciated if you could give me a simple example of this functionality.
                Thanks in advance.
                Best Regards from Brazil.
                Rodrigo Arai

Hi Rodrigo,
in a nutshell:
- you can define status network based on objects (w.g. material)
- Define Attributes: you can define attributes like DELETION_ALLOWED or LOCKED_FOR_CHANGE and you can implement preconditions in custom classes when should it happen
- Define Status Field: you can define some fields which are related to the status. e.g. in recipe management RCP_USAGE
- Status: you can define the different statuses (e.g. in process, completed..) with attributes
- Scheme Definition: you can define the logic between statuses. E.g. you would like to swith from status In Process to Completed and from New to In Process. Then switching from New to Completed is not possible for the user.
- Subobject Type Scheme only applied if you have subobjects
here you can find the customizing documentation, there are some examples as well:
Define Status Scheme
Use
In this Customizing activity, you define statuses and status schemes for object types and corresponding attributes.
For each status, you can define which attributes are allowed to be set for an object with this status assigned.
The status scheme defines the initial status and the possible transitions from one status to another.
Activities
You define status schemes as follows:
1. Select the required object type and enter the following:
a) An identifier
b) An object type class (Note: this class should implement the interface class)
c) A subobject type search help
The search help provides a list of all possible subobject types. This feature enhances the usability while maintaining status schemes at subobject-type level.
d) If the
Status
tab page shall be visible on the PLM Web UI, select the
Status Tab
checkbox
Status and action management is a reusable object. It has been modeled as a dependent object. The prerequisites to enable status and action management for any new objects are:
Add the Status and Action Management tab page on the UI.
Enable the Status Tab checkbox in this Customizing activity.
2. Select the required object type and define the following attributes for it:
a) An object type
b) An attribute identifier
c) An attribute description
d) An attribute type
e) Select a precondition class (Note: This class should implement the '/PLMB/IF_SAM_PRECONDITION' interface)
3. Define the technical status field name.
When you change the object status, the system updates the technical status field names to the new values made in these settings.
4. Select object type and define corresponding statuses.
a) Select the status and define the corresponding object type, an identifier, description, and status icon.
Note:
You cannot define new statuses for materials and material BOMs. For these objects, all values should be transferred from the back-end system.
You can import the status values from the back-end system as follows:
b) Select the object type that represents a material or a MatBOM.
c) Select
Status
in the dialog structure.
d) Choose the
New Entries
pushbutton.
e) Choose the
Import Status
pushbutton.
Note
The system imports the following status values into SAM:
For material: the
X-plant matl status
(cross-plant material status)
For MatBOM: the header status
Although you cannot change the imported value for a material or a MatBOM, you can change its name and description to conform to SAM terminology.
You can differentiate between the following cases for objects whose status values are imported from the back-end system:
The object was not created on the PLM Web UI, but in the back-end system; no SAM status scheme or status was assigned, but a status value was set in the back-end system.
If you assign a SAM status scheme to this object later on that contains the equivalent imported status values, the SAM status value is set accordingly, even if any precondition check results of the SAM status scheme may exist.
The object was created in the back-end system or on the Web UI and a SAM status scheme is assigned to the object on the PLM Web UI.
If the corresponding status value is changed in the back-end system, then existing SAM preconditions for this status transition and allowed status transitions are checked. If the preconditions are not fulfilled, a message is raised and the new status cannot be saved.
5. Specify which attributes are allowed for each object type when the chosen status is set.
a) Select a status and open the
Attributes
screen.
b) Choose an object type.
c) Choose an attribute.
6. Define whether values from other technical fields are affected by setting this status.
a) Select a status and open the
Field Values
screen.
b) Select an object type.
c) Select a technical field name.
7. Specify the status scheme. The status scheme defines the initial status and status transition for the object type. For example, below is a list of standard status schemes defined for iPPE object types.
Assembly Header - PLM_PPEAH
Assembly Item - PLM_PPEAI
Product Item Variant - PLM_PPEPIV
Product Variant - PLM_PPEPV
You can also create schemes for the object type as follows:
a) Specify an identifier and description for the status scheme and set one of the statuses defined above as the initial status.
b) Select the status scheme and open the
Transitions
screen. Enter all possible status transitions by specifying the source (
Status From
) and target status (
Status To
c) Select the
Long Text
checkbox if you want the system to open the long text editor on the
Status
tab in the PLM Web UI. You can use the long text editor to create notes for this transition.
8. Define the scheme at subobject-type level by entering following parameters:
a) Object type
b) Subobject type (You can choose from the list of subobject types you have specified when defining the search help in step 1)
Alternatively, you can define a default status scheme that is automatically displayed on the
Status
tab.
The following statuses are included in the standard delivery:
10 - In Work
20 - For Approval
LINKED_DIR
LINKED_MAT
LOCKED_FOR_CHANGE
REPLACE_PH_ASSEMBLY (only in the PLM_PPEAI assembly item and the PLM_PPEPIV product item variant)
30 - Released For Planning
LOCKED_FOR_CHANGE
40 - Released
RELEASED
SUB_ITEM_STATUS
The following status transitions are possible:
FROM
TO
Long Text checkbox (dialog box for notes)
10
20
20
30
30
40
20
40
20
10
X
30
10
X
40
10
X
More on SAP help:
Status and Action Management on the Web UI - SAP Library
Best regards
Tamas

Incident management and Critical Master data table change management.

Dears,
I need to configure Incident management and Critical Master data table change management on our solman 7.0 server.
I want to know how many days should be required for this activity and please share documents.
Shivam

Hi,
I faced a similar situation,
I tried all the possible ways like activating InfoObject manually, Through an activation program of aggregates,
Also ran RSRV check which was showing no negative results.
I raised an OSS note for the same but after that when SAP returned back the process chian ran again as it is a daily load which activated the record in 'M'.
I ask you to wait till the next process chian run, and try all possible ways to activate.
If it is not corrected then raise an oss to SAP.
Thanks & Regards,
Vishnu

Incident Management - changing doc-status after action SOCM_COPY_DOCUMENT

Similar Messages

Maybe you are looking for