charm: unable to successfully complete import into production systems

[Former Member]

Hello SolMan Experts;

I have an issue while trying to set the final status (production) to all change documents within charm.

Here is a short description:

- status is set to "authorized for production"

- import is performed successfully into production

- when trying to set the final status "production", an error occurs

error is SOCM_ACTION_LOG009

description of the error is: Unable to successfully complete import into production system (but the import has been done successfully)

-

---

details on the error:

Unable to successfully complete import into production system

Message no. SOCM_ACTION_LOG009

Diagnosis

The system could not determine whether the production system has the correction, or at least one transport request was not imported into the production system.

System Response

The transaction is incorrect or the status has been reset by the system.

Procedure

You can try again to complete the import in the transaction by double-clicking the error message in the application log and then resaving the transaction. If the error message still appears, there is a technical problem.

Procedure for System Administration

Check the task list and the transport logs. If there was an import error which you have resolved, you can set the import status of the failed transport to "Repaired" in the task list with the "General Function" "Correct Import Errors Manually". You can then continue with your process.

-

---

It seems as solman is not able to see that the import was performed successfully.

This is happening for all transports, in all systems but I do not think this is linked to configuration since it is working fine in solman dev system.

Does anyone has an idea on how to solve this issue?

Thanks for your help!

Kr,

Alice

[fernando_rocha1]

Hi Alice,

See note 907768 and make sure you have applied all ChaRM required corrections related to you SP level.

It must solve the issue.

BR

Fernando

[Former Member]

All,

Issue is solved.

Our domain controller set up in stms was not supported as such by current version of SolMan SP23.

SAP consultants provided us the answer: Upgrade was needed or workaround provided by SAP.

Thanks,

Alice

[Former Member]

i have the same issue, can you please share what is the workaround provided by sap

[Former Member]

Hello all,

Unfortunatelly, after implementing the solution proposed by sap it is still not working.

(their identified rootcause was that we have in solution manager >> stms >> system overview >> one system ID for both domains abap and java foe each dual stack system meaning that solution manager was trying to read the import queue on basis of the system ID which led him to two possible systems and he picked the first one to check if import was in production and as such returned an error because he checked on the wrong import queue - java one instead of abap items).

Their proposed solution was to change set up of stms and smsy to have one system ID linked to one domain contorller for abap and another system id for the domain of java.

OR: this will be resolved by SolMan version 7.1).

Given that this is proposed solution is apprently not solving our issue, in case someone found a solution, please let me know.

Any idea or help would be highle appreciated.

Thanks,

Alice

[Former Member]

Hi Alice

Read sapnote 1426029 and add user parameter CHECK_NTIME _SOCM parameter value =9 if not then implement sap note and set =20

When we check this condition we are making a loop in this way:

do CHECK_NTIME_SOCM (5) times

do the check by rfc to the remote system ()

if the request is not imported, wait for 10 seconds

if the request is imported, exit the loop

enddo

I don´t recommend values biggers than 20 for this parameter CHECK_NTIME_SOCM, see note 1426029 for details.

So, with this parameter CHECK_NTIME_SOCM we can determine the time that this condition is going to wait to allow us to go on with the correction document or to show us an error if we can not confirm that the import is really not done in the managed system.

Sanjay