Normal Correction document is reset to Created by itself

Dear everyone:
We have configured ChaRM - Solution Manager 4.0 (SP9). The ChaRM works fine on Urgent Correction, but not for Normal Correction. The Status of (Normal) Correction document always reset back to Created. It does not want to stay as 'In development' status.
Here is the step I took to create new change document with a Subject : Normal Correction(maintenance).
I authorized the change document, then I choose Maintenance Cycle (Normal/Periodic Maintenance).
Next document / correction document -> 8000000196, Status: Created. I choose set in Development. - Status of correction document is: In Development
Next step, I choose Create Transport Request - transport request generated for document. Then all the sudden the status of correction Document is back to Created.
And I can not go to any where else....
Would anyone please help me out?
Thank you.
Kind regards,
Rudy

Hi Steven:
There are some actions are the detail -
Action 1: (yellow light) During Creation
detail: (green) check successful
Action 2: (yellow light) Check Consistency:
detail: (green) Check successful
Action 3: (red light) for Copy a Solution Manager Context:
detail: (green) date/time stamp
(green) Processing SOCM_COPY_CONTEXT is started.
(red) Action could not be successfully executed (no processing parameter)
The other one has yellow status, and the processing parameter shown as
--> No container is available, for application name CRM_ORDER, Action profile SDMI_Action
Action 4: (green) set to 'In Development' :
(green) Processing HF_SET_STATUS Is Started
(green) Action successfully completed
Action 5: (green) Create Transport Request:
(green) Processing HF_Execute_Action Is Started
(green) Request ID and Number created
(green) Action successfully completed
As soon as triggered Create transport, then the Document status back to 'Created', and I only have two choices in the action button ... set in Development or Cancel Procedure.
What would cause this issue ?
Thank you in advance.
Kind regards,
Rudy

Similar Messages

Reseting status of normal correction

Hello.
After update up to version ST 20 (SAPKITL430) one more error appear in system. After processing of any activity with normal correction and trying to save this document system resets status of correction to "Created". I have found coresponding SAP Note 919477, but it has't any correction instruction... Can you help me?
Edited by: Dmitry Udot on Sep 25, 2009 11:02 AM

Hehe... you are right.
First off I think it should be SDMI_ACTIONS not DMI_ACTIONS.
And yes, there should be some more instructions, hehe. Probably delete it (after making a screenshot).
The selected schedule condtion looks strange. Because as for what I can tell it says:
Set User Status to E0001 (new) when user status is not:
consolidated AND NOT productive AND new (consolidated and productive belong to SDMJ not SDMI, new fits to both)
OR
in developement (fits to SDMI and SDMJ)
So whenever you set (SDMI or SDMJ) to "in developement" it will be set back to E0001. Very strange.
Guess you may delete it or at least disable the action.
Regards

CR correction document status changes back to created

Hi Experts!
Does anyone of you know why in ChaRM CR Correction document the status of the document (controlled with Actions) switches back to "created" from status "In development". This switch happened to me several times when handling a normal correction and I don't know why it does that.
Usually I have done Action related task to the correction prior the status is swithced.
I've tried to look for a solution in the forum and in help docs but I haven't come accross any. Please don't get me wrong, I do get the full maintenance cycle working for normal corrections. This status change is more of an annoyance than an error.
We are using SolMan 4.0 SP09
Thankful for all hints I can get!
BR
Auli

I found a previous discussion from this forum with Avinash's advice to use note 919477. This is exactly what I was looking for.
I'm recording it here just in case anyone ever needs to solve this in the future.
BR
Auli

CHARM: Urgnt Correction Document is not created

Dear Experts,
I have copied SDCR to YDCR and kept all profiles as default namely:
1. Text Determination Procedure= SDCR0001
2. Partner Determination Procedure= SDCR0001
3. Status Profile= SDCRHEAD
4. Date Profile= SDCR_HEADER
5. Action Profile=SDCR
However, when I was trying to create an Urgnt Correction type of document, I could see that no such type of document was created to process it further after creating an initial document of YDCR and selecting Urgnt Correction (Maintenance) option from the subject drop down.
May any please tell me how I can diagnose this and solve my problem?
Please let me know if you need any more information.
Waiting for your kind replies.
Regards,
Faisal

Dmitry,
Thank you very much for your kind reply. I did the same as you told here. However, still the problem is same. I first copied SDCR rule to YDCR then changed SDHF to YDHF and created a new Change Request Document. However, the YDHF type of document (Urgnt Correction (Maintenance)) is not being created.
May you please tell me if I missed any thing?
Also, once I authorize the change request, still the user status is same as "To Be Approved". It is not changing to "Authorized"
Regards,
Faisal
Edited by: Faisal Khan on Dec 27, 2010 8:28 AM

Normal Correction/Development Activity

i am creating Development(Implementation) type change request, , after setting the status of the Change Request In Development and created the transport request. after creating TR its status automatically resets to "CREATED" again and again each time i create transport request??
Plus if we have imported a TR once in QAS and reset the status to "In DEvelopment" and created new transport request , by again "Import Transport Request (Background) it will transport the new TR only??
For normal correction/Development Activity we ahve to import transport request manually from task list???
Thanks

Hi
This should slove your problem
Note 919477 - Normal correction reset to status "created"
santosh

Issue with normal correction.

Hello,
I am configuring ChaRM in SolMan system. I am able to perform the steps mentioned in the RKT. But currently I am facing 2 issues.
1. There is no action as "Create Change Request" in the support message. I can see only "Create Change Document". How can I get that action? What is the difference between a change request and chage document?
2. For normal correction (maintenance), once the message reaches the status "In developement", when I try to perform the action "Logon to the system", nothing is happening and I am getting successfull message saying "Action Logon to system performed immediately".
Please help me to solve these problems.
Thanks and Regards,
Rajeev.

Hi,
1. There is no action as "Create Change Request" in the support message. I can see only "Create Change docuement" How can I get that action? What is the difference between a change request and chage document?
you are correct only action is there create change document because first a change document is created for Change manager approval and after his approval and concern he create a type of correction ithen only u get the next doc.
2. For normal correction (maintenance), once the message reaches the status "In developement", when I try to perform the action "Logon to the system", nothing is happening and I am getting successfull message saying "Action Logon to system performed immediately".
Check your authorization to logon to that satellite system
Regards
Prakhar

Confirm Successful Test in Normal Correction (SDMJ)

Hello,
In normal correction (SDMJ) workflow, the action Confirm Successful Test is selected in the Development with Release phase of a project/maintenance cycle. The status of the Change document changes to Consolidated after that, and you then be able to move the cycle to Test phase.
How can we customise the standard workflow so that Confirm Successful Test is selected in the Test phase? This seems to make better sense.
I'd appreciate any help from any one of you who have done some customising to the SDMJ standard workflow. Many thanks in advance for your help.
BR Li

Hi Li,
I had the same dscussion with my customers more than once, it is hard to understand to perform the action "Confirm Successful Test" before Test phase.
You could add another status to SDMJ (or a copy of SDMJ, for instance ZDMJ) before Consolidated.
But we selected another option, by using test messages during test phase and therefore following SAP standard process. So, a developer confirms successful integration/unit testing after he finished his development/customizing activities in dev by changing the status to consolidated.
If some issues are detected in Test phase, we are using test messages to correct it. But you are right, at the end of test phase there is no additional status which says: all is fine, go ahead and move it to production. Only be checking that all Test messages are finished, the Production transport approver can be sure, all issues have been resolved.
But by adding another status, please consider this: You have to create a copy of SDMJ (ZDMJ). After this, all enhancements and changes to SDMJ delivered by SAP, you have to do manually for your new transaction type ZDMJ, otherwise you will not get the functionality. That's why I'd recommend to use SDMJ as delivered by SAP and also use Test messages during test phase.
Best Regards,
Holger Slomka

ChaRM Status being reset to Created

In partner determination I have setup Message Processor as a required field. In my ChaRM document, if the MP is not maintained and the document is saved, the status will be set all the way back to Created.
Any ideas?

Hey Solmaniac,
could you please check table TSOCM_COND_MAPP in SM30.
If you find an entry for your specific status "FS in Progress" where you have a condition status transition = "NO_BUSINESS_PARTNER"
=> make sure that
1 - in column MT you have 'Error' and not 'Cancel'
2 - that column 'UsrSt' is empty
3 - save change
Redo your test (relaunch transaction crmd_order first) with only a normal correction AT YOUR SPECIFIC Status. If that works; don t forget to redo the same operations on all entries SDMJ OR ZDMJ - "NO_BUSINESS_PARTNER"
Hope it helps
Regards,
Khalil

Creation of New consistencycheck condition for Normal Correction

Hi,
We are using ChaRM normal correction to check the transport imported to production system we are using the check conditon 'PRODUCTION_IMPORT_OK' which is implemented in Class CL_SOCM_INSTANCE .
On similar base we wanted to create the condition of 'ZTEST_IMPORT_OK' for normal correction, but we are not able to find the Standard code written for condition PRODUCTION_IMPORT_OK.
If find this code we can make some adjustment in this code with BADI for consistency check to implement the new condition .
Is any one worked on this type of condition , your help will be appreciated.
Regards,
Amar Kamat

HI
Check if needed to assign any account key to this new condition type in your procedure if needed, then mantain the GL acc for the same.
If you are adding this condition type in your TAXINN procedure (assuming so) you need to create the condition type for the same by using trax FV11.
If you are adding your condition type in Pricing procedure then no ned to create the condition record.
Regards
Sujoy

Exit or Badi to block document after Reset Cleared Items in FF.5

Hi,
When you run FF.5 and some rejected documents are returned by the bank, I have to block the document after reset cleared items with a especific payment block key.
Anyone already done something similar?
Tks!

Hi Rao,
<b>Userexits</b>
VMDE0004     Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003     Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002     Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001     Shipping Interface: Error Handling - Inbound IDoc
V53W0001     User exits for creating picking waves
V53C0002     W&S: RWE enhancement - shipping material type/time slot
V53C0001     Rough workload calculation in time per item
V50S0001     User Exits for Delivery Processing
V50R0004     Calculation of Stock for POs for Shipping Due Date List
V50R0002     Collective processing for delivery creation
V50R0001     Collective processing for delivery creation
V50Q0001     Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT     Delivery: Item Status Calculation
V02V0004     User Exit for Staging Area Determination (Item)
V02V0003     User exit for gate + matl staging area determination (headr)
V02V0002     User exit for storage location determination
V02V0001     Sales area determination for stock transport order
<b>Business Add-in</b>
DELIVERY_ADDR_SAP     Address Change in Delivery Processing
DELIVERY_PUBLISH     Announcement of delivery data during database update
Reward pts if found usefull
Regards
Sathish

ChaRM: Some actions missing in the Correction Document?

Dear all:
I have followed all the tutorials about creating a charm, everything is fine but when handling the correction document I can never see in the action list the items "Logon to system" and "Complete development" (I can see al the other items though). Anyone has an idea about this? Where those actions come from?
Thank a lot in advance!!
Federico.

Hello Frederico,
These actions are PPF actions, they are assigned to an action profile and this action profile is assigned to the CRM transactions such as SDCR, SDHF, and so on. You can maintain that at SPPFCADM.
However, sometimes the basis PPF database tables are not completed updated during the activation of BC-set SOLMAN40_CHARM_BASICFUNC_001.
Our recommendation now is to reactivate the ChaRM BC-Sets, in order to recreate all entries missing. However, I have to remind you that if you have performed some customizing in ChaRM this will be overwritten.
So, if you agree with this statement, please reactivate the BC-Sets in this sequence:
SOLMAN40_CHARM_PROXYFACT_001
SOLMAN40_CHARM_BASICFUNC_001
SOLMAN40_CHARM_TRANSTYPE_SDMJ
Please check note 907768 that has informations about how to activate ChaRM BC-Sets.
Best Regards,
Fernando Rocha

Billing documents should not be created when it is not released to accounti

Hi SD gurus,
In some situation, billing documents are generated but it is not released to accounting which results in mismatch between FI value and SD value. We go to VFX3 and see the list of billing documents and take corrective action.
Our requirement is that the billing document should not be generated when system is not releasing this billing document to accounting.
Please suggest a solution for this.
Regards,
Senthil.

Thanks giri.
For the following reasons, the billing documents are not released to accounting.
1. If the user wrongly chosen the billing type for the delivery.
2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
Hope this will be suffice to understand my issue and suggest a suitable solution.
Points will be rewarded.
Regards,
Kumar.

Current Proccesor in normal correction activity

Dear all helpers.
Please, what is actual role for Current processor in activity normal correction? Is it developer? Or is it simple the one, who proccess the activity NOW, I this role is changing during life cycle of correction? My concern is, that there is possibility to choose developers and other roles at the sheet partners.
Thank you for explanation.
Many thanx
Petr

hi Petr,
there are indeed different way to interpret this. It can be a "current processor" whaterer the function behind or the "main processor", in this case this is fixed.
The fact that by default prompt to become the processor each time someone enters the document shows that SAP has chosen a moving value there.
In our company we have choosen a fixed value. This is the one doing the actual change. (customizing or development)
The other partner functions are well defined (like IT operator,...) and these partners are playing their role depending on the correction status.
Both approach are valid for me
best regards
Xavier

DOC should be a normal Word document and we should be able to define the header style

Hi Team,
We are facing a issue with the pre assigned headers assigned by Adobe acrobat Pro Xl.
Our actual requirement is as follows:
1. As we convert a PDF to DOC there shouldn't be any pre assigned headers (header levels defined).
2. DOC should be a normal Word document and we should be able to define the header style.
We have tried working out on the same but nothing is going our way.
We tried couple of step which are as follows:
1. Deleting pre assigned TAG's.
2. Clearing headers with the help of Touch Up Reading Order Tool (TURO).
Request you to kindly revert on the same.

1. As we convert a PDF to DOC there shouldn't be any pre assigned headers (header levels defined).
You cannot control how Acrobat creates the word file.
2. DOC should be a normal Word document and we should be able to define the header style.
The word file is a normal Word document file. You may wish it was designed for it to be easiest to edit. Acrobat is making a Word file to most reliably resemble the original pdf file. I have no trouble creating any header style I want. The text in the header frequently consists of text boxes. Acrobat does this to insure accurate representation of the pdf file.

Normal Correction flow & Transport of copies

Hi,
I am performing following steps for Normal Correction. But when I first time schedule the imoprt job, nothing is moved to Quality system.
u2022     Action u2018Set to In developmentu2019. Status changes to u2018In Developmentu2019.
u2022     Perform action u2018Create Transport Requestu2019. Transport Request (ID6K900342) created.
u2022     Change the Maintenance Cycle phase to u2018Development with Releaseu2019
u2022     Developer completes the work & releases the Task in satellite system
u2022     Action: u2018Test Transportu2019. Creates Transport of copies (ID6K900344)
u2022     Schedule the import job. ( But after executing also nothing will be moved to Quality)
u2022     Action: u2018Complete Developmentu2019. System creates another new Transport of copies (ID6K900347) for Original Request.
u2022     Schedule the Import job. ( But after executing also nothing will be moved to Quality)
What could be the reason. both the TP copies are in queue only, nothing is moved to quality.
Regards
PK

Hi PK,
Let me try to explain:
NC => 80000001
1. Create TR
XXXK0001 (Original TR)
2. "Test Transport" or "Complete Development"
XXXK0001 (Original TR) -> still not released
XXXK0002 (ToC- copy of XXXK0001)-> is created in DEV
3. Import TRs to QAS (from task list)
XXXK0001 (Original TR) -> still not released
XXXK0002 (ToC) -> is moved to QAS
4. Now the changes are in QAS, but is not placed in the PRD import queue. So, you can test it with no risk.
5. If you have problem, go back to 'In development'
Correct the problem in XXXK0001
and go to step 2 again.
6. If the changes are OK in QAS
- Select 'successful tested'
XXXK0001 (Original TR) -> is released
7. Import to QAS
XXXK0001 imported in QAS and automatically placed in PRD import queue.
8. Import to PRD
The ToC is used to avoid import an inconsistent TR into PRD system, because once it has been imported in QAS, the same will be available to import into PRD, without any test.
BR
Fernando

Normal Correction document is reset to Created by itself

Similar Messages

Maybe you are looking for