Charm Question

[Former Member]

I am busy with a charm implementation for a customer in SA. They have specific requirements in regards to approvals on their different landscapes. They dont want to use the normal correction in charm because of the project phase's. So I am going to make a copy of the urgent correction trans type SDHF and add in additional actions and status to meet their requirements. I would just like to know if it is possible to have multiple so called "urgent corrections" linked to one incident? And if this is possiable how will the import of transports work?

[Former Member · Accepted solution]

if it is possible to have multiple so called "urgent corrections" linked to one incident? And if this is possible how will the import of transports work?

I cannot tell you if you can create multiple urgent corrections for the same incident for sure since I have not tried it ever, but this is what I think, you can have multiple Urgent corrections per change request, they will all be imported individually. And also you can have multiple change requests per Incident.

[Former Member · Accepted solution]

I dont see how you can have multiple urgent corrections linked to a cr because as i understand it is that you have one correction linked to one cr. Because after you Approve the cr then it goes into status Approved and you cant do anything else on the cr thats why a correction gets created and all tasks after cr approval is done on the correction.

[Former Member · Accepted solution]

Hi Santosh,

With the standard change request you are correct that you cannot create a urgent correction from the request when it is approved, but you can configure the request to enable you to create a correction message.

With the standard support message in 7.0 you can create multiple change requests from one incident. You can also change which follow-on document is created from a support message, and change the follow-on document depending on the subject field.

I would question the approach you are describing because I would be concerned about how the organisation can ensure that the transport landscape is consistent.

Also you should remember that in 7.1 you have different transaction types, so the more specialised transaction types that are created in 7.0 the more work it will be to upgrade.

Good luck!

Rich Labib

[Former Member · Accepted solution]

Hi Santosh,

As standard it is not possible, in our implementation we got around this by creating an additional custom container ZDHF (as well as ZLFN) that acts as container for just change requests ZDCR without link to Support Noritication. That way we could managed multiple change requests that were related.

I would question why you are only using Urgent and not Normal changes however.

Paul

[Former Member · Accepted solution]

Hi Paul

The reason i am only using urgent correction is simply because that the client does not want to go and change the phases of the project i.e Dev w/o release, Dev with release and so forth. They also have different approvals for each landscape which i am building in additional status and actions.

Santosh

[Former Member · Accepted solution]

Solved