Enrollment - Coverage Start Date issue

Hi All,
I am facing an issue in Selfservice, where an employee can login to SSHR to insert a life event, process it and make Enrollments.
There is one Life Event - Gain Dependent - Child, when an employee adds a dependent - Child he needs to insert the life event and on Processing it he can makes the enrollments and then save them.
On doing so the Coverage Start Date for the Benefits is coming up as Today's date (assuming if the employee makes enrollments Today).
But keeping the same setup if we Process the Life Event and make Enrollments from Oracle Forms the Coverage Start Date is coming up as 1st of the current Month, which is the actual date that should be coming up as per the Fast Formula logic.
Due to the wrong Coverage Start Date, Rate Start is also getting wrongly popualted and hence employees are losing the Dollars...
Is there any way by which this can be fixed or this is an issue with Selfservice that the what the Logic FF has cannot be used in selfservice.
Anyone having any idea on this, please reply ASAP as this is the Show Stopper issue.
Thanks
Shivam.

Hi Shivam,
You have mentioned previously that Ct. is triggering the Gain Dep. LE by adding a new dependent child. This means that the person already had a life event in started status which enabled the Family Member page and allowed the user to add a dependent.
If so, then there might be a Collapsing Logic defined between the Current LE[Say New Hire or Open] and the Gain Dependent. [I have seen this setup with most of the Ct.'s].
So, there is a good chance that instead of the Gain Dependent, the Current LE will be reprocessed and hence is taking the setup of Current LE instead of GD.
You can confirm the LE processed in the Current Benefits page.
Regards,
Aneesh N

Similar Messages

Plan Enrollment Coverage End date

There is a plan , which has following Enrollment coverage Start date and Coverage end date code resp. ( in Plan enrollment requirements)
Enterable and 1 Day Before Event.
The plan needs to be explicitly enrolled to thru ESS.
There is a reqmt such that when employee enters end date it should be such that only sysdate or later date should be allowed to be entered. So we may need to change the above setup.This has to be acheived in configuration only.
Kindly help.
Thanks,
Sush
Edited by: user10714306 on Aug 14, 2009 6:02 AM

Hi,
To drop the plan off employees, you have to process life event for them. If it's part of the annual process, then the enrollments will drop when the open enrollment is processed. Alternately, you will have to process an "Admin" life event for these employees.
If you are using unrestricted processing, then use admin or open to achieve the same.
IF the changes are just in dev environment, I suggest removing the plan year periods from the plan instead of making it inactive. processing life events is still necessary. Plans made inactive cannot be reverted back and so, should be done as a last resort.
Regards,
Vinayaka

Incorrect Coverage Start Dates

During Open Enrollment, there was an error in our set ups for our STD plan and now several employees have incorrect coverage start dates and incorrect original enrollment dates for the plan. There are over 1000 employees affected by this error so manually overriding the dates isn't a popular option to fix this problem. Is there an API that might be useful for correcting these dates ? Any other thoughts ?
Thanks in advance for your help !
Jeff

Hi
You can review the below Metalink Note -
*Oracle Human Resources Management Systems (HRMS) Benefits Enrollment Conversion [ID 365034.1*], search '
To Create or Update Enrollments' in the Doc of this Notes.
Please let me know if you face any issue or need any informatoin, will be glad to help you.
HTH
Gaurav

Converting Coverage Start Date during OAB Conversion for current elections

We have a requirement to convert the coverage start date of current elections in the Legacy System to OAB.
We are using 'BEN_ELECTION_INFORMATION.ELECTION_INFORMATION_W' api to convert current enrollments and is passing the actual coverage start date of the current enrollments to the parameter 'p_enrt_cvg_strt_dt' in this API. We have an administrative Life Event configured in OAB for converting the current enrollments with Assigned Life Event date as '29-JUN-2010' . After the Conversion API is executed for all the Enrollment records the coverage Start Date is set to '29-JUN-2010', which is not the requirement.
We also tried using the APIs 'BEN_PRTT_ENRT_RESULT_API.UPDATE_ENROLLMENT' and 'BEN_PRTT_ENRT_RESULT_API.UPDATE_PRTT_ENRT_RESULT', but they behave the same manner as 'the Legacy System to OAB. We are using 'BEN_ELECTION_INFORMATION.ELECTION_INFORMATION_W'.
Please let us know which API would allow us to convert the current elections without changing the actual coverage start date from the Legacy System.

I did run the default enrollment process, but nothing happens. I tried this with the Assign on Default check box checked and unchecked. Here is what I have setup for the enrollment details on this plan:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Program Enrollment Requirements > General > Plan
Method: Automatic
Enrollment: Current, Keep Only; New, Can Choose
Default Enrollment:
- Code: Rule
- Rule: DEV_X
- Assign on Default: Checked
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I removed the eligibility profile from the plan and it will default when running the participation process, however that does not solve the problem. I even rewrote the rule to include plan id, but that did not work either. The employee needs to be enrolled automatically when they select a given plan. Because the person is not eligible for the plan until after they select it, OAB will not know that the person is eligible until the participation process is run.
The only thing I can think is to have a separate life event that triggers at the end of the enrollment period, but I haven't figured how to do that yet. And it still doesn't quite solve the problem completely, as will be the case when enrollments are made after the enrollment period, i.e. corrections.

Advanced Benefits:Dependent Coverage Start Date

Hi,
I have a an employee with the following life events.
Intially the Employee has Employee Only Option
1) 28-Feb-2010 -- New Child --> Emp+Children --> Child Cvg Start Date --28-Dec-2010
2) 01-JAN-2011 -- Open --> Emp+ Children --> Emp CVg Start Date -- 01-Jan-2011 and Dep Cvg Start Date 01-jan-2011
3) 01-APr-2011 -- Marriage --> Emp+Family --> The Cvg start date of the Child is Changed to 01-APr-2011 and the Employee CVG start date also changed to 01-apr-2011
I am curious to find why did the child coverage start date changed to 01-APr-2011 and we have added spouse only in the marriage life event and changed the
option from Emp+Children to EMp-Family
Thanks for any input.
regards,
A

Hi Shivam,
You have mentioned previously that Ct. is triggering the Gain Dep. LE by adding a new dependent child. This means that the person already had a life event in started status which enabled the Family Member page and allowed the user to add a dependent.
If so, then there might be a Collapsing Logic defined between the Current LE[Say New Hire or Open] and the Gain Dependent. [I have seen this setup with most of the Ct.'s].
So, there is a good chance that instead of the Gain Dependent, the Current LE will be reprocessed and hence is taking the setup of Current LE instead of GD.
You can confirm the LE processed in the Current Benefits page.
Regards,
Aneesh N

BG_ABSENCE_DURATION FF start date issue

Hi
I have created BG_ABSENCE_DURATION fast formula with the effective start date as "01-DEC-2009" by mistake. It has to be from 01-JAN-2001. If I try to delete the existing one, it is showing message that, you cannot delete the Quickpaint Type fast formula. How could I change the effective date of this fast formula to 01-JAN-2001 ?
Thanks in advance.

Update the Effective Start Date from the backend.
Or you will need to delete the Formula from backend. You need to clear following tables.
FF_COMPILED_INFO_F
FF_FDI_USAGES_F
FF_FORMULAS_F_TL
FF_FORMULAS_F

"The end date can't be set to occur before the start date" issue

I have a subscribed calendar that draws from data in a Filemaker database. In all of these records, the start date & end date are the same. When I try to refresh the description, it fails with a "NSCocoaErrorDomain / error 1560" error, and the console log shows "The end date can't be set to occur before the start date."
Well, it doesn't occur before the start date. It's the same as the start date. I can work around this by setting my Filemaker database to add a day to the end date, but that's a clunky solution.
Anyone else run into anything like this?
(iCal 4.0.3 and OS X 10.6.4, btw)

It may not be the same problem, but the message was the same (end date...etc). I tore my hair out at the time trying to solve it. It was on my fathers computer. Everything appeared to be correct and consistent. What solved it was logging into MobileMe/account/personal info/time zone, where I found the time zone was wrong. I can't remember the detail now but at the time it seemed like a third place where time had to be correct. Worth your checking there anyway.

Suspended coverage start date

Hi All ,
I have a requirement where I have to start the suspended coverage (after certificaton is provided) . The coverge should start from 1st of next month (month after certification is provided) . I tried putting the unsuspended code(First of Month After Completed) in the "Coverage restrictions" screen in "Plan Enrollment requirements" . However is does not work and coverage does not start from 1st of next month .
Can someone please let me know , if I am something here . Any replies are appreciated .
Thanks

Hi,
if it's not first of month, then what is it getting to ?

Issue on Ordinary Depreciation Start Date and Disposal of Asset

Hi All.
I am facing the following the issues.
Fiscal Year is from July - June
First Problem: Company acquired the asset Vehicle on 26.Dec.2008. System proposes Ordinary Depreciation Start Date as 01.Jan.2009 rather then proposing Ordinary Depreciation Start Date as 01.Dec.2008.
Since depreciation for previous year has been posted the client later found out that instead of calculating depreciation for 7 months depreciation was only calculated for 6 months. I tried to manually change the dep. start date but the system doesnot update the previous years values, it's still calculating depreciation for 6 months and not 7 months. Is there anyway in updating the previous fiscal years depreciation values.
2nd Problem: I created a test case scenario today i.e. 16.09.2009 by creating and capitalizing an asset vehicle. Once I capitalized the asset the system automatically proposed the start date as 01.10.2009 and not 01.09.2009 which is what i require. What setting do i need to check or maintain in order to solve this issue because the user does not want to manually change the date each time an asset is created.
3rd Problem: Similar to this now when client disposes of an asset suppose on 10.Feb.2009 (FY2009). The system calculates depreciation till the month in which disposal takes place (February), the client does not want this, their requirement is that depreciation should be calculated one month before disposal takes place i.e. in this case Dep should be calculated till Month of January.
Your assistance will be highly appreciated.
Mohammed Ali Khan.

Hello Khan,
The depreciation start date will get determined based on the period control method assigned to depreciation key,
Period control methods are defined in transaction code : OAVH
In period control method we will mention the depreciation start date for acquisition, additions and also depreciation end date for disposals, retirements.
SAP has given some default period control keys. If any of these are not suitable to your requirement you can create on your own period control methods.
THanks
Sai

Issue with Ord Start Date

Hi,
I am having issue with Ord Start Date.
When i create XYZ Asset now when i do the acquasation for that new asset. Example: Using FB01 i enter todays date and i do the posting.
Now when i go to DEP Area TAB for the DEP Key (M200) - The Ord Dep Start Date is 15 Dec 2010.
For this DEP Key Period Control Methods (T code - AFAMP) - Acquisation Entered is ( 6 that is - at the start of year) and the Period Control is ( T code - OAVS) (4 that is - First year convention at half year start date).
Our client is using the fiscal year as 1 June 2010 to 31 May 2011.
So when i do acquistion for the asset as per the period contol the Ord Dep Start Date should be 1 Dec 2010, but here it is talking 15 Dec 2010.
Why is system talking 15 days more.
Regards.

Hi
Which Fiscal year variant are you using??
Did you maintain it in OAVH? Copy the existing entry in OAVH for K4 to your Fisc Yr var and try again
And also, 04 does not figure for Acquisitions in AFAMP under 0004.... Whatever you specify in OAVH must also be a part of AFAMP
Regards
Ajay M
Edited by: Ajay Maheshwari on Oct 28, 2010 2:31 PM

Start Date,End Date prompt issue

Hi
I have a problem for prompts related to start Date and End Date selection i.e
Start Date                   End Date
01-Jan-2007                 31-Jan-2007
01-Jul-2008                  31-Jul-2008
The issue is if the user select the Start Date from a list of values(prompt) the End Date LOV's should appear only from its related Start Date i.e
If Start Date is selected as 01-Apr-2007 then End Date LOV's should start only from 30-Apr-2007
and the End Date LOV's should be seen only for the next 12 months i.e only till 31-Mar-2008
Please suggest me how I can resolve this prompt issue

hi there,,
you can not do that at the prompt form
coz every prompt is independent from the other.
good luck
Amr

Process/Production Order WIP Reverse on Month starting date with postiing d

Hi Experts,
Is it possible to reverse the WIP of Production/Process Order at month starting date eg. 01/07/09. Posting date & Document date should be: 01/070/09.
In my current project production is batch management system. Some of the batches start at month ending days (Eg. 29/06/09) for we calculated WIP at dated: 30/06/09.
My Client wants to reverse that WIP next day, month starting hours Eg. 01/07/09 but while reversing the WIP system is posting the WIP reversing doc. posting date is 31/07/09.
Same batch which started production on 29/06/06 is closed at 03/07/09 as well as goods received same date. FG Stock A/c updated in accounting books.
At the same day If I print my trail balance system showing the Stock value double (WIP stock as well as FG stock)
First Month
Eg. Process Order WIP at 30/06/09                              : 50000/-INR
Second Month
      WIP Reversal Posting date:31/07/09 by system     : 50000/-INR
      FG Stock received at 03/07/09                               : 50000/-INR
If I Print Trail Balance on 03/07/09 system shows        : 1, 00, 000/-INR (based on Posting date)
Which is wrong..
Please tell me the way for Change the Posting date of WIP reverse document. OSS guys are replying as consulting issue.
I am waiting for your valuable reply.
Thanks & regards
Bhagiradha

In KO88, CO88 Select Menu bar Extras-> Posting date
Enter Posting and execute
Thanks for Rajesh (SAP Labs)
Thnaks & Regards
Bhagiradh

Can i restrict apple mail client from downloading all emails...and allow it to pick a start date for gmail mail to sync? i am flooded with old emails, thousands on them ...eating hard drive space of my macbook pro and un necessary overhead

can i restrict apple mail client from downloading all emails...and allow it to pick a start date for gmail mail to sync? i am flooded with old emails, thousands on them ...eating hard drive space of my macbook pro and un necessary overhead

The genius bar technicians can check your MBP for possible hardware problems and specific software issues that you may have. The diagnosis will be free. Any extensive repairs will not be free.
If you have minor software problems, you essentially will have to deal with them yourself. Examine these two comprehensive documents for possible problem definition and solutions. If you encounter problems that you are unable to cope with, start a new discussion and there will be persons willing to assist you in solving them.
https://discussions.apple.com/docs/DOC-3521
https://discussions.apple.com/docs/DOC-3353
Ciao.

Fiscal year variants in co.code have inconsistent start date.Msg no AC531

Hi Experts
We went with 24 periods after Go live. I am trying to assign the TAX basis fiscal year variant(TX) at Depreciation area level. But it's not letting to add with the following error message.
Fiscal year variants in co.code have inconsistent start date
Message no. AC531
Diagnosis
The first day of the fiscal year for variant TX (24periods) in company code in Asset Accounting differs from the first day of the fiscal year for variant D1(12 periods) in General Ledger Accounting.
However, both variants must have the same start and end date! Only the periods within the fiscal year can be different in the two variants.
Please guide me how to fix this error message.
Thanks in advance
Meenakshi.N
Edited by: Meenakshi.Nakshatrula on May 3, 2010 5:45 AM

Hi,
Message no. AC531 says:
The first day of the fiscal year for variant K4 in company code in Asset
Accounting differs from the first day of the fiscal year for variant NL
in General Ledger Accounting.
However, both variants must have the same start and end date! Only the
periods within the fiscal year can be different in the two variants.
The error is described in note 844029 :-
In the NewGL in Asset Accounting, it is still not possible for
depreciation areas to have fiscal year variants with different start and
finish dates. If you try to assign a fiscal year variant to an area,
whereby the fiscal year variant infringes this restriction, the system
issues error message AC 531.
Regards Bernhard

Error while starting data loading on InfoPackage

Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors         MESSAGE_TYPE_X
Date and Time          19.01.2009 14:41:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
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
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
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 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop.      " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id    = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount        = l_s_rsbatchheader-jobcount
320
jobname         = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others          = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list           = l_t_server
327
exceptions
328
no_server_list = 1
329
others         = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME' field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host   = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc    = l_subrc
346
wp_index = l_wp_index
347
wp_pid   = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no           = l_wp_index.
352
l_s_rsbatchheader-ts_start        = l_tstamps.
353
l_s_rsbatchheader-uname           = sy-uname.
354
l_s_rsbatchheader-module_name     = l_module_name.
355
l_s_rsbatchheader-module_type     = l_module_type.
356
l_s_rsbatchheader-pc_variant      = i_pc_variant.
357
l_s_rsbatchheader-pc_instance     = i_pc_instance.
358
l_s_rsbatchheader-pc_logid        = i_pc_logid.
359
l_s_rsbatchheader-pc_callback     = i_pc_callback_at_end.

Hi,
i am also getting related this issue kindly see this below short dump description.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
What can you do?
    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
    Short text of error message:
    Variant RSPROCESS0000000000705 does not exist
    Long text of error message:
     Diagnosis
         You selected variant 00000000705 for program RSPROCESS.
         This variant does not exist.
     System Response
     Procedure
         Correct the entry.
    Technical information about the message:
    Message class....... "DB"
Number.............. 612
    Variable 1.......... "&0000000000705"
    Variable 2.......... "RSPROCESS"
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
    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 701
    Application server... "CMCBIPRD"
    Network address...... "192.168.50.12"
    Operating system..... "Windows NT"
Release.............. "6.1"
    Hardware type........ "16x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "CMCBIPRD"
    Database type..... "MSSQL"
    Database name..... "BIP"
    Database user ID.. "bip"
    Terminal.......... "CMCBIPRD"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 9 2012 23:43:54"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 196
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 16384
MM Used. 2143680
MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
    Language Key........ "E"
Transaction......... " "
    Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
System.............. "BIP"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron without reply and transactional (emode 0, imode
     0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 75
    of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line SourceCde
   45         l_t_info        TYPE rs_t_rscedst,
   46         l_s_info        TYPE rscedst,
   47         l_s_mon         TYPE rsmonpc,
   48         l_synchronous   TYPE rs_bool,
   49         l_sync_debug    TYPE rs_bool,
   50         l_eventp        TYPE btcevtparm,
   51         l_eventno       TYPE rspc_eventno,
   52         l_t_recipients TYPE rsra_t_recipient,
52 l_t_recipients TYPE rsra_t_recipient,
53         l_s_recipients TYPE rsra_s_recipient,
54         l_sms           TYPE rs_bool,
55         l_t_text        TYPE rspc_t_text.
56
57   IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59     CALL FUNCTION 'RSPC_PROCESS_FINISH'
60       EXPORTING
61         i_logid       = i_logid
62         i_chain       = i_chain
63         i_type        = i_type
64         i_variant     = i_variant
65         i_instance    = i_instance
66         i_state       = i_state
67         i_eventno     = i_eventno
68         i_hold        = i_hold
69         i_job_count   = i_job_count
70         i_batchdate   = i_batchdate
71         i_batchtime   = i_batchtime
72       EXCEPTIONS
73         error_message = 1.
74     IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77     ELSE.
78       EXIT.
79     ENDIF.
80   ENDIF.
81 * ==== Cleanup ====
82   COMMIT WORK.
83 * ==== Get Chain ====
84   IF i_chain IS INITIAL.
85     SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86            WHERE log_id = i_logid.
87   ELSE.
88     l_chain = i_chain.
89   ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92   DO.
93     CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94       EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru

Enrollment - Coverage Start Date issue

Similar Messages

Maybe you are looking for