Execute Z* VMS action in DBM (/DBM/VSEARCH)

Hi Gurus,
i have a question to share with all of you, i created an Z* action in VMS so my question is... i want to execute this action in DBM (/DBM/VSEARCH) which configs should i have to do to reuse this acction Z* ?
i already did this config:
the action Z102 is a sales order.
but when i am in /DBM/VSEARCH and i populate the data,i execute but looking in the debugg looks like the program control in DBM lost the data.
thanks for your answers

Hi Sachin, thanks for answer,
the vehicle is this one
i will take this vehicle and execute Z102 via VMS (tx VELO)
successful
now i will reverse the Z102 and execute with the same customer and sales area via /DBM/VSEARCH
and the result has failed
as you see, there isn't problem with the matrix for my action Z102, i am thinking could be some part on abap code where sales area and customer are losing.
any help it will be apreciated .

Similar Messages

  • Create Billing tab is not found in /DBM/VSEARCH transaction

    Hi Experts,
    I have completed doing the PGI in New vehicle sales process. Later the step is Creating outgoing invoice for customer.
    I didnt find any  button in /DBM/VSEARCH transaction, for doing billing. How can i do the billing for the vehicles which i sold to the customers.
    I have maintained QOIV & QFOR in action controll determination.
    PFB attachment for the Vehicle order document which completed the PGI.
    Thanks,
    Nagaprasadreddy.

    Hi Joachim,
    Thanks for the inputs.
    I have already maintained the entries. PFB for the reference screenshots
    I did the PGI and the action is executed.
    Now i am doing the Invoice,
    I executed the action,
    Now in Vehicel history i cant see any actions executed for billing.
    Kindly let me know what could be the issue. Struggling from long time to resolve the issue.
    Thanks,
    Nagaprasad.

  • Error during Portal Setup: An error occurred while executing a custom action:_GrantLocalPermissionsToWCSAccount

    Error:
    Configure Portal Setup
    An error occurred while executing a custom action:_GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the correction are made, you can retry upgrade for this role.
    Errors in the Log:
    MSI (s) (38:14) [21:30:36:094]: NOTE: custom action _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
    CustomAction _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (38:94) [21:30:36:115]: User policy value 'DisableRollback' is 0
    MSI (s) (38:14) [21:30:36:094]: NOTE: custom action _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
    CustomAction _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (38:94) [21:30:36:115]: User policy value 'DisableRollback' is 0
    I cannot get past this error. I am running Sharepoint Foundation 2010 with Sp1. This is on a Windows Server 2008 R2 Server +Sp1.
    Any ideas?
    David Baur

    I finally figured this out, The issue was that I had put in the Self Service Portal Computer Name and Service account into the Service Manager SQL as SysAdmin, once I removed it flew through just fine.
    David Baur

  • Reinstalling SCSM 2012 SP1 -- installation fails on Finalize step "while executing a custom action:RollbackCleanup" -- absolutely stumped!

    I uninstalled a previous installation of SCSM 2012 in our lab environment because the person who installed it is didn't give anyone else permissions and they weren't available to make the change.  Since then, I've tried to install SCSM 2012 multiple
    times and it fails every time during the Finalize step with the error shown in the picture below.
    Things I've tried and double checked:
    I am running the install with a domain admin account
    I'm specifying a domain user service account during install which is local administrator on the machine
    I rebuilt the performance counters
    I'm running SQL 2k8 R2 SP2
    .Net 3.5.1 is installed
    I see the following message in the System Event Log during setup:
    Event 7036 - The System Center Data Access Service service entered the running state.
    Event 7031 - The System Center Data Access Service service terminated unexpectedly. 
    It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
    It appears as though this happens 18 times before the service is no longer restarted and is left terminated.
    Any thoughts or help on how to get this to work would be greatly appreciated!  Log excerpts are below as well as a link to the full log file at the end.
    Chris
    Errors in the log that make me go "hmm…" 
    I changed my domain and username in the logs to "DOMAIN" and "user" respectively. 
    MSI (s) (74!94) [10:29:06:718]: Note: 1: 2711 2: MOMServer
    Action start 10:29:06: _SetHealthServiceConfig.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMServer
    MSI (s) (74!94) [10:29:06:719]: Note: 1: 2711 2: MOMGateway
    SetHealthServiceConfig: Failed to get Feature State.. Error Code: 0x80070646. MOMServer
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway
    MSI (s) (74:04) [10:49:58:011]: Executing op: ActionStart(Name=_ExecuteSqlScripts,Description=Configuring Database,Template=[1])
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _MPProcessorDeferred, 9923,
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
    RegisterSdkSCP: Old serviceConnectionPoint found
    RegisterSdkSCP: Deleting existing serviceConnectionPoint
    RegisterSdkSCP: Warning: Dont have access to delete existing serviceConnectionPoint
    RegisterSdkSCP: Creating New serviceConnectionPoint
    RegisterSdkSCP: Adding ACL for current user: DOMAIN\account
    RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\SCSM Admins
    RegisterSdkSCP: Error: The object already exists.
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
    WaitForSDKServiceStart:Entering
    WaitForSDKServiceStart:Sleeping for SDK to start 0 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 10 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 20 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 30 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 40 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 50 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 60 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 70 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 80 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 90 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 100 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 110 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 120 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 130 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 140 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 150 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 160 seconds
    WaitForSDKServiceStart:Sleeping for SDK to start 170 seconds
    WaitForSDKServiceStart: SDK Service connect error, after 3 mins, fail this function
    MSI (s) (74:40) [10:56:20:397]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that
    handle.
    CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (74:04) [10:56:40:799]: Executing op: CustomActionRollback(Action=_RollBack_UninstallHealthServicePerfCountersForUpgrade.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3393,Source=BinaryData,Target=InstallHSPerfCounters,CustomActionData=C:\Program
    Files\Microsoft System Center 2012\Service Manager\)
    MSI (s) (74:38) [10:56:40:801]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI62BF.tmp, Entrypoint: InstallHSPerfCounters
    InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft System Center 2012\Service Manager\
    InstallHSPerfCounters: Installing agent perf counters.
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center 2012\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallHSPerfCounters: Failed to install agent perf counters. Error Code: 0x80070057.
    MSI (s) (74:04) [10:57:10:844]: I/O on thread 2752 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:844]: I/O on thread 4796 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:844]: I/O on thread 4928 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4612 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 884 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 2600 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 1884 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4872 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 3084 could not be cancelled. Error: 1168
    MSI (s) (74:04) [10:57:10:845]: I/O on thread 4920 could not be cancelled. Error: 1168
    MSI (s) (74!E0) [10:57:10:846]: Product: Microsoft System Center 2012 - Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with
    this package. The error code is 25211. The arguments are: -2147024809, The parameter is incorrect.,
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are: -2147024809, The parameter is incorrect.,
    CustomAction _RollBack_UninstallHealthServicePerfCountersForUpgrade.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 returned actual error code 1603 but will be translated to success due to continue marking
    MSI (s) (74:04) [10:57:17:154]: Note: 1: 1708
    MSI (s) (74:04) [10:57:17:154]: Product: Microsoft System Center 2012 - Service Manager -- Installation failed.
    MSI (s) (74:04) [10:57:17:155]: Windows Installer installed the product. Product Name: Microsoft System Center 2012 - Service Manager. Product Version: 7.5.2905.0. Product Language: 0. Manufacturer:
    Microsoft Corporation. Installation success or error status: 1603.
    Full log file:
    https://skydrive.live.com/redir?resid=F723C571E9E6D51F!1414&authkey=!ACisfvqIpGO_i7A

    Hello Christopher,
    I have recently worked in a case that had mostly the same errors:
    InstallHSPerfCounters: Installing agent perf counters.
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\HealthServiceCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft System Center\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallHSPerfCounters: Failed to install agent perf counters. Error Code: 0x80070057.
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 8152 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 9580 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 6008 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 2112 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 8252 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 12504 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 9548 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:586]: I/O on thread 11464 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 10616 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 8120 could not be cancelled. Error: 1168
    MSI (s) (A8:D4) [10:29:51:587]: I/O on thread 2424 could not be cancelled. Error: 1168
    MSI (s) (A8!D4) [10:29:51:587]: Product: Microsoft System Center 2012 R2 Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are:
    -2147024809, The parameter is incorrect.,
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211. The arguments are: -2147024809, The parameter is incorrect.,
    CustomAction _RollBack_UninstallHealthServicePerfCountersForUpgrade.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 returned actual error code 1603 but will be translated to success due to continue marking
    MSI (s) (A8:3C) [10:29:51:599]: Executing op: ActionStart(Name=_StopNamedServices_HealthService.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,Description=Stopping Health services,)
    MSI (s) (A8:3C) [10:29:51:603]: Executing op: ActionStart(Name=StopServices,Description=Stopping services,Template=[1])
    MSI (s) (A8:3C) [10:29:51:605]: Executing op: ServiceControl(,Name=W3SVC,Action=1,,)
    MSI (s) (A8:3C) [10:29:52:621]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,).
    - I was able to resolve it using the command  line LOTCTR /R
    - And restarting the IIS service using the command line tool IISRESET
    - After this command was successfully applied I have tried to install the Service Manager Portal without any errors.
    http://technet.microsoft.com/en-us/library/bb490926.aspx
    http://technet.microsoft.com/en-us/library/hh875560.aspx
    http://support.microsoft.com/kb/300956
    https://blogs.technet.com/b/yongrhee/archive/2009/10/06/how-to-rebuild-performance-counters-on-windows-vista-server2008-7-server2008r2.aspx
    Thank you very much
    Renato Pacheco

  • SCSM2012 Beta installation problem: An error occurred while executing a custom action:_PopulateUserRoles

    I'm installing the SCSM2012 Management Server
    component on a SQL dev box.  During the installation, the very last step (Import Management Packs) fails with this error:
    An error occurred while executing a custom action:_PopulateUserRoles
    This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the correction are made, you can retry upgrade for this role.
    I've already verified that the account I'm logged in with has SA access to the SQL database.  Windows 2008 R2 firewall is turned off.....
    Has anybody else run into this problem?

    I don't see anything indicative in the setup log.  The setup seems to get all the way to the part where it installs the management packs.  Then right after that is when the installation fails and it rolls back.
    From the setup log, towards the end:
    Property(S): ACTIONSUSER = NETWORK SERVICE
    Property(S): ACTIONSDOMAIN = NT AUTHORITY
    Property(S): ACTIONSUSER_FOR_DB = NETWORK SERVICE
    Property(S): ACTIONSDOMAIN_FOR_DB = NT AUTHORITY
    Property(S): SOURCEDIR = C:\SCSM\SCSM2012_Beta\Setup\Server\
    Property(S): SourcedirProduct = {295201AE-EAB6-416C-8252-7C065243EF55}
    Property(S): ProductToBeRegistered = 1
    MSI (s) (9C:54) [17:33:22:951]: Note: 1: 1708
    MSI (s) (9C:54) [17:33:22:951]: Product: Microsoft System Center Service Manager 2012 -- Installation failed.
    MSI (s) (9C:54) [17:33:22:959]: Windows Installer installed the product. Product Name: Microsoft System Center Service Manager 2012. Product Version: 7.5.1354.0. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status:
    1603.
    MSI (s) (9C:54) [17:33:23:010]: Deferring clean up of packages/files, if any exist
    MSI (s) (9C:54) [17:33:23:013]: MainEngineThread is returning 1603
    MSI (s) (9C:20) [17:33:23:061]: RESTART MANAGER: Session closed.
    MSI (s) (9C:20) [17:33:23:061]: No System Restore sequence number for this installation.
    === Logging stopped: 11/7/2011  17:33:22 ===
    MSI (s) (9C:20) [17:33:23:065]: User policy value 'DisableRollback' is 0
    MSI (s) (9C:20) [17:33:23:065]: Machine policy value 'DisableRollback' is 0
    MSI (s) (9C:20) [17:33:23:065]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (9C:20) [17:33:23:065]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (9C:20) [17:33:23:066]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (9C:20) [17:33:23:067]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (9C:20) [17:33:23:067]: Restoring environment variables
    MSI (s) (9C:20) [17:33:23:089]: Destroying RemoteAPI object.
    MSI (s) (9C:28) [17:33:23:089]: Custom Action Manager thread ending.
    MSI (c) (C8:B4) [17:33:23:144]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (C8:B4) [17:33:23:175]: MainEngineThread is returning 1603
    === Verbose logging stopped: 11/7/2011  17:33:23 ===

  • An error occurred while executing a custom action:_PopulateUserRoles

    I am trying to install Service Manager 2012 RTM onto a brand new server 2008r2. The purpose is to replace the other Data Management server that is giving me problems upgrading to service pack1. I go through the setup and connect to the SQL server and
    the database that has my existing DM. I am using the same credentials and everything is the same. It goes all the way to the end and I get an error :
    An error occurred while executing a custom action:_PopulateUserRoles
    This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the correction are made, you can retry upgrade for this roll

    After this error, I reran setup and used the domain admin account instead of the Service Manager Admins group I created in AD. The  error did not happen again, but I did get the "Setup cannot complete - RollbackCleanup"
    error. This was fixed by following this link: "http://www.cireson.com/scsm/scsm-an-error-occurred/" and this MS article: "http://support.microsoft.com/kb/922918/en-us".
    These are the steps (I had to create the DWORD 32 bit):
    Click Start, click Run, type regedit, and then click
    OK.
    Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    In the right pane, locate the ServicesPipeTimeout entry.
    Note  If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
    On the Edit menu, point to
    New, and then click DWORD Value.
    Type ServicesPipeTimeout, and then press ENTER.
    Right-click ServicesPipeTimeout, and then click Modify.
    Click Decimal, type 60000, and then click
    OK.
    This value represents the time in milliseconds before a service times out.
    Restart the computer.
    Hope this helps!
    BR,
    Robert
    Robert

  • CPS-Job - Reply on Console doesn't execute the chosen action

    Dear Developers
    We have a job chain in which we have as default postcondition "On Error
    Action CONSOLE RESTART". Now we have a step on status CONSOLE but a
    reply doesn't execute the chosen action. This is not the first time we
    experience this behaviour.
    Any ideas to solve that problem or any workaround?
    Regards,
    Stephan Gross, RAIcps
    Here our system info:
    DB-Version Info:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
    NLSRTL Version 10.2.0.4.0 - Production
    Redwood-Repository Info:
    JCS Object Database,7.0.3.33
    JCS Modules,7.0.3
    JCS PM4W,7.0.3
    JCS Redwood &module Module,7.0.2

    Hello Stephan,
    7.0.3.33 has a known issue where the reply of console is not always carried out.
    If this is the same issue as you are experiencing, then the issue is solved in patch 7.0.3.38.
    I would advise you to create an OSS message to have checked if this is indeed the same issue.
    Kind regards,
    Miek

  • Dynamic actions user execute the Hiring action, IT 0105 dynamically adjust

    Hello Any body can guid me for the below requirement..
    Whenever the user execute the Hiring action (action type: Z1-Hiring cPA) the system should adjust the infotype 0105 dynamically during executing the hiring process, in the same way the subtype (0010 : E-mail )for the userid in SAP HR should be adjusted.  The HR Services should not have to do this manually.
    The e-mail account can be composed from the fields first name, name prefix and birth name. The fields have to be separated by dots. When the name prefix contains more words they have to be separated by a dot.
    When company code is 003 the value email atthe rate xx.comhas to be adjusted at the end.
    When company code is 004 the value email atthe rate yy.com has to be adjusted at the end.

    Hello Donnie Freako
    Thanks for the the information, As i am a HR-ABAP consultent. I am not much femiler on this dynamic actions..
    for this case: the  DESCRIPTION:  In the dynamic module pool ZXXXM000 has to be changed. - so for this where exactly i need to check the transcation, i think its in SE51..
    please provide me the steps for the same... and if possible please provide the breaf detaild explination for the below code where exactly i need to place the below, i think we need to place this in T588Z table against fields and values and whatis the meaing of P and I and F and W .. as a technical person i dont know much about this please help me on the same..
    P PSPAR-MASSN=u2019Z1u2019
    P P0001-BUKRS=u2019003u2019
    I INS,0105,0010/D
    F Z_003_EMAIL (ZEMAIL)
    W P0105-USRID_LONG=RP50D-FIELD1
    P P0001-BUKRS=u2019004u2019
    I INS,0105,0010/D
    F Z_004_EMAIL (ZEMAIL)
    W P0105-USRID_LONG=RP50D-FIELD1
    clear explination would be appreciated

  • Any reason why my code isn't executing the "stop" action?

    Any reason why my code isn't executing the "stop" action?
    sym.getComposition().getStage().getSymbol("_001").$("_002").$("_003").bind('mouseenter',fu nction(e){
    e.preventDefault();
    $(this).unbind('mouseenter');
    sym.getComposition().getStage().getSymbol("_001").$("_002").$("_003").stop("over");
    See my file here http://twistedpancreas.com/edge/misc/dropDownNotWorking.zip
    The dropdown should change to orange when rolled over, but it's not
    Any help is appreciated.

    Thanks rhemanthkumar,
    so .$ should only be referenced in the last mention of a symbol, all others should be .getSymbol ?

  • Vms - actions

    hi,
    In VELO, we have done the follwoing actions succesfully
    1) CREA (vehile creation)
    2) ORD1 (create PO)
    However, while trying to perform GORE (Goods Receipt)sytem is giving error saying that action cannot be executed for these vehicles  . And  the log says Read Conguration.
    Did I miss any settings. Pls help.
    Regards,
    Student
    Edited by: STUDENT on Jul 31, 2009 3:06 AM

    Hi Student,
    it's a bit hard to say for sure what causes the problem without knowing more details but to me it seems quite likely that the vehicle's current status doesn't allow the execution of the action you selected. The fact that action GORE isn't offered when you're on the action tab indicates so.
    What I write here is based on this assumption.
    You need to check the primary and secondary status of your vehicle in the vehicle details. Then in customizing (transaction OVELO1), check if action GORE is relevant for the primary status, the secondary status or both. In standard, the action is only relevant for the primary status.
    You then can check, again in customizing (transaction OVELO11), what are the possible actions for the vehicle and what status is required for action GORE.
    In order to be able to execute an action, the action needs to be part of the matrix relevent for the vehicle (in this case, the matrix used as primary matrix, see transaction VELOS, needs to contain action GORE). The old status of in the matrix for action GORE needs to be the same as the current vehicle status.
    I hope most of this isn't new to you as this is the "core" of the VMS concept. In order to work with VMS, you need to be familiar with this concept.
    Here're links to the documentation, just in case: http://help.sap.com/saphelp_dimp50/helpdata/EN/95/47c83abc3c1a54e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_dimp50/helpdata/EN/a1/6dc33ac037b41de10000000a11402f/frameset.htm
    As I said, I'm not sure if my interpretation of what causes your problem is correct but what I've described above seems likely to me.
    Kind regards,
         Steffen

  • Short Dump while executing New Hire (action type) in PA40

    Hi All,
    i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         

    Hi,
    Error Log: Syntax error
    ""LV_LENGTH" has already been declared"
    please check LV_LENGTH variable declaration.
    It may be declared more once!

  • Runtime error while executing New Hire action in PA40

    Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         
      149
    * Wird mit Einfuehrung des Headerobjekts obsolet.                                          
      150
      PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                    
      151
        USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                    
      152
    ENDFORM.                                                                                   
      153
      154
    *       FORM RE588I                                                   *                    
      155
      156
      157
      158
    *  -->  T588I_DHDID                                                   *                    
      159
    *  -->  T588I_MOLGA                                                   *                    
      160
    *  -->  T588I_TCLAS                         

    Implement SAP Note 1004280.. your issue if fixed
    If your issue is resolved request you to close the thread or else free feel to touch base
    BR
    Anil

  • Error while executing Guided Procedures Action

    Hello,
    We are getting the following error when a user is trying to execute an Action in the Guided Procedures Process:
    "Cannot complete Action: Activity could not be read".
    What can be causing this?
    Any help would be highly Appreciated.

    Hello,
    This is more than likely due to an inconsistency of a GP object at database level. I suggest opening an OSS ticket as this would require detailed analysis.
    Thanks and best regards,
    Carl Connolly
    Senior Support Consultant - Netweaver Web Application Server
    AGS Primary Support, Global Support Centre Ireland
    Guided Procedures trouble shooting guide:
    www.sdn.sap.com/irj/scn/wiki?path=/display/JSTSG/%2528GP%2529Home

  • I can not execute a dynamic action if I execute a BI

    I am executing an infotype in Batch input with a call transaction and the dynamic actions don't work.
    Any ideas.
    Thank you.

    Unfortunetly dynamic actions (T588Z) are not called in batch input mode - that is standard SPA HR processing.
    The normal process is to create all the infotypes in the batch input program - even the ones that would be created by dynamic actions if running online in PA30/PA40
    hope that helps

  • Doubt in Execute Rule Set Action

    Hi,
    I have seen the following documentation in help doc regarding Execute Ruleset action
    'The Execute Ruleset and Execute Flow Ruleset rule script actions result in evaluating and executing another ruleset u2013 either a rete ruleset or a flow ruleset. This action is similar to invoking a ruleset, except that the current value of objects, including variable definitions, are available to the ruleset being invoked (instead of their initial values). If the invoked ruleset changes the value of any of the objects, these are reflected in the initial Flow Ruleset'
    I have a rule flow set invoking another rule set in its action script. I need to pass a variable defined in rule flow set to invoked rule set. I did this with following action
    Execute Ruleset RuleSet1 On var1.
    My doubt is how do i access this in invoked rule set? I didnt see this in invoked rule set.
    Regards,
    Dhana

    Hi Dhana,
    'The Execute Ruleset and Execute Flow Ruleset rule script actions result in evaluating and executing another ruleset u2013 either a rete ruleset or a flow ruleset. This action is similar to invoking a ruleset, except that the current value of objects, including variable definitions, are available to the ruleset being invoked (instead of their initial values). If the invoked ruleset changes the value of any of the objects, these are reflected in the initial Flow Ruleset'
    What we mean by the stmt above is - In case the action  "Execute Ruleset" or "Execute Flow Ruleset" is used, all those global definitions which are modified at the ruleset level will retain their changed value when the other ruleset is evaluated.
    This needn't be specifically mentioned using the "ON" option.
    This option is provided for a user to pass the current value of objects alone. "except that the current value of objects... are available to the ruleset being invoked"
    Your other question related to passing the variable definition created at the flow ruleset level, to be passed to the other ruleset - such a mapping is not yet possible. You will have to define this as a common(global) definition.
    Hope this clarifies your doubt.
    Best Regards,
    Arti

Maybe you are looking for