Required Start date in Notification

Hi All,
Maint order is assigned as a call object for a maint plan. After scheduling the maint order is generated with the basic date as per the planned date in maint plan. But the notification generated along with the order has the required start date same as that of the notification generated date (due to call horizon) instead of the planned date in maint plan. Kindly give me the config steps to set the notification reqd start date as per the planned date in maint plan.

Hi Pushpa,
Thx.,
I had done that.
But i'm getting it right only when the priority in maint plan is not selected.
If priority is selected then i'm getting it wrong...
Kindly revert back !
Prabhu

Similar Messages

  • QM_Control on Required start date in quality notifications

    Dear QM experts,
    Requirement is,
    For Q2 notification type the entries in required start date filed (QMEL-STRMN) to be restricted in such a way so that user can not do entry for last month.
    Foe example,
    1.     Today is June 12, 2009. If a user is creating Q2 notification today he/she may change the required start date in the past but not before 1st June 2009.
    2.     User should be in a position to enter back date in required filed only for the current month
    3.     The concept is just similar to period closing activities.
    I tried through SPRO-Quality Management-Quality notifications-Notification creation u2013Notification types-Define screen templates-Field Selection: General Screens. Here there is facility to make the field grey, hide or required. One of the limitations is that this is client level setting.
    Can the requirement be mapped for particular plant and for perticular notification type?
    Thanks is advance
    Best Regards,
    Anand Rao

    Dear Anand
    Here are some of the thoughts. Please check and then come back with your feedback
    1) Make Priority button mandatory for Q2 notification .VIQMEL-PRIOK. You can do only for Notification type Q2 by using the influencing fields
    2) Make required date in grey so that no changes can be done . do this notification Q2
    2) Maintain QM priorities SPRO >Quality Notifications > Notification Processing>Response Control> Define Priorities
    3) Maintain Priorities in the QM priority in the same config
    When you set the priority in the notification required from and end date is updated in the system automatically
    4) Use this exit QQMA0018  Deadline setting based on entered priority  to make sure that always the date doesnt fall on past date
    Hope this gives some idea
    Regards
    gajesh

  • Required start date in a services purchase requisition. How?

    When hiring equipment (eg. a tower wagon), it is required to specify in the purchase requisition on what date the equipment needs to be available and on what date the equipment needs to be picked up again. So basically, the required start and end date of a service need to be captured in the purchase requisition (and copied to the PO and subsequently sent to the vendor).
    The end date of the service is already recorded in the delivery date field. The start date can be entered in the item text.  But since it is required to report on the start date of services, it is desirable to record the start date in a separate field in the purchase requisition. This way a list could be created with all the equipment that should have been made available by the vendor on a certain date.
    Does anybody have any good suggestions on how to make such a 'required start date' field available? N.B. To make things more complex, the requisitions are raised in Plant Maintenance, so ideally the start date would be filled from the PM-order too.

    The validity dates in the PO are maintained at header level. The required start and end date for an equipment should be maintained on item level, as there can be multiple items in one PO each with different start and end dates.
    Also, the validity end date in the PO has the functionality that "No further service entry sheets can be created after this date." It is very common that a Service entry sheet is raised after the hire period is ended.
    So using the validity dates in the PO is not a good option.

  • Malfunction start date in preventive notification

    Hi all
    I have created one notification type of preventive to capture weekly preventive maintenance & scheduled the maintenance plan.When notification is generated on due date  & I am opening the notification by t-code IW22 or IW28, system is taking malfunction start date field as system date.I have activated the "scheduling overview" tab of this notification type to know required start date(planned date) of the notification.How can I avoid the malfunction start date to be populated ? as my users get confusion due to this date?Why this date is coming by default as system date?
    rgds
    rajib

    Hi,
    This malfunction date/time will always be set as default to current date when the notification is created. Even if you were to set it empty via a exit, it will get populated when notification is loaded via IW22. An option would be to hide these fields for your preventative notification type. Make settings via OIAL with influence on notification type.
    -Paul

  • How to display absence start date and end date in workflow notification?

    Hi,
    I would like to display the absence start date and end date at
    1) Subject of workflow email notification/worklist notification OR/AND
    2) Content of workflow email notification/worklist notification.
    Appreciate if anyone can advise on this as this information is very crucial to our client.
    Thank you.
    Regards,
    Shiau Chin, Teo

    1) Subject of workflow email notification/worklist notification OR/ANDyou have to customize the subject of notification message. You can find the message using following query.
    SELECT message_type, message_name
       FROM wf_notifications notif
      where notification_id = <your notification>;> 2) Content of workflow email notification/worklist notification.
    its already there I think.

  • WO basic start date - requirement date

    Good morning folks,
    Would anyone be able to shed some light on any config that would be suitable for the following:
    The materials are assigned to a task list that is then assigned to a plan.  That plan is then scheduled and the work orders are generated.
    When the materials are added to the work order their requirement date is automatically assigned as the work order basic start date - can this requirement date be pulled from the scheduled dates instead?
    The problem is that the material may not be required at the beginning of the WO, so the defaulted basic start date of the WO would not be the way forward.
    Thanks
    Mantas

    hi Mantas
    you can set in scheduling parameters with following possibilities
    <b>Path Plant maintenance and customer service->Maintenance and service order->scheduling->set scheduling parameter</b>
    1)The basic dates are adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
    2)The basic dates are not adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
    3)The basic dates are adjusted and the dependent requirements are scheduled for the order basic start date.
    4)The basic dates are not adjusted and the dependent requirements are scheduled for the order basic start date.
    so when you add the components you have to assign the operations,after selecting the operation you can change the operation date, after you change the operation dates,the material scheduled dates will be changed to the operation date
    (using the option <b>1</b>)
    regards
    thyagarajan

  • Set the dependant requirement dates to be scheduled to order start date

    Dear Experts,
    The components have been assigned to the relative operations in the routing.
    During the lead time scheduling, is it possible to set all the required date of the components to the order start date instead of the operation start date? How to configure?
    Thanks,
    Dawson

    Hi,
    In lead time scheduling, the precise production times, that is, the target start date and the target finish date, are specified for materials that are produced in-house. Capacity Requirements are also created during lead time scheduling and the date that the components must be provided is also determined.
    You have maintained the following parameters for lead time scheduling in Customizing for MRP by choosing Define scheduling parameters for planned orders:
    Parameters for determining the routing
    Parameters that determine if and how scheduling is carried out
    Parameters that indicate if and how basic dates are to be adjusted
    Then
    You have assigned a scheduling margin key in the material master record.
    You can define the scheduling margin key in Customizing for MRP by choosing Define floats (scheduling margin key).
    If You Assign BOM components to the first Operation then all the components are provided on the Basic start date of the production considering all the floats
    OR
    In a situation where different operations are assigned with different BOM components then  we define Lead time off set(+ve on u2013ve value) to have material provision on the basic start date of production order
    pavan

  • Error: "Depreciation start date required in old assets data (please enter)"

    When , I use transaction AS91 , for an asset , with book depreciation key  = 0000, the system shows this error:"Depreciation start date required in old assets data (please enter)",
    somebody could help me with this please?

    Check if the depreciation start date has got populated in the tab for depreciation areas in AS91.
    Usually this gets populated based on capitalization/creation date.If not then try to enter this manually.
    Thanks and regards
    Kedar

  • Basic start date & Basic finish date based on Priority

    Dear Experts,
    When I am creating Notification & selecting Priority, System gives pop-up “do you want to specify new dates?” If I select yes system automatically change required start & required end based on Priority.
    Now my question is do we have same functionality for Maintenance order as priority field is available there (If we are directly creating a MO)?
    Even if we are creating WO from notification, required start & end dates copies to Basic start & Basic finish but if we change priority then no change in basic start & finish dates. Why?

    Greetings Parag,
    You may select the Priority in the initial screen of IW31 and the dates will shift accordingly, if you maintained the Relative Start &/or Relative End in
    SPRO > Plant Maintenance > Maintenance Processing > Maintenance & Service Orders > General Data > Define Priorities > Define Priorities for Each Priority Type
    If you want to change date based on Priority on the Order header screen, it's not possible in the standard to my knowledge, but you may easily develop an enhancement utilizing the user exit
    IWO10012 Maintenance order: Priority handling on central header
    or
    IWO10009 PM Order: Customer Check for 'Save' Event

  • Restriction of Validity start date in Scheduling agreement

    Hi,
    I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting  back  validity start date in the header of Scheduling agreement (me32l)
    What can be the possible reason.
    Regards
    Sachin

    Hi,
    I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
    Laufzeitbeginn in der Vergangenheit -
        IF ekko-kdatb < sy-datlo.
          MESSAGE w170 INTO gl_dummy.
          mmpur_message 'W' '06' '170' '' '' '' ''.
    Please consul your ABAP Team on this to change it to Error.
    But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
    Regards
    Chandra Shekhar

  • Change in start date of tax depreciation not for posting in mid of year

    Hi Experts,
    Tax depreciation area is not for posting. The fiscal year is from Jan to Dec. I want to calculate tax depreciation from May 2011 based on Net Book Value of tax depreciation as on 30.04.2011. But once I change the start date of tax depreciation in asset master to 01.05.2011, the system ignores the previous depreciation so I am not getting the NBV of tax depreciation of 30.04.2011.
    Is any setting is required to get this. I can not do changes in posting rules since this tax depreciation is not for posting any thing.
    The fiscal year 2010 is closed and NBV of tax depreciation as on 31.12.2010 of one asset is 80000, If I change the start date of tax depreciation from 1.1.2011 then system correcly take NBV of 31.12.2010 for further depreciation calculation. But if i change the start date of depreciation in between of year the system is calculating depreciation based on NBV of 31.12.2010 but ignores the tax depreciation from 1.1.2011 to 30.04.2011, which I previously run using AFAB.
    Need your assistance to know is it feasible to do this.
    Thanks and Regards,
    Harshad

    Hi Harshad
    The behaviour of the system is very much correct, it is designed to behave that way...
    One, you should not have changed the dep start date....
    two, NBV in SAP is always taken to be NBV @ the start of the year....
    The best wayout I can suggest here is, if you are on EhP4 and EA-FIN active
    a. Change the Dep Key in the asset... You can maintain Time Dependant Dep Terms in asset master i.e. Dep Key X from Jan-Apr and Dep Key Y from MAy onwards
    b. This will however, calculate dep based on NBV at the start of the year, but based on new useful life
    c. Considering your eg: The system is posting more depreciation i.e. 5333 instead of 5155.... So, calculate this amount outside the system and post a Manual Write up ABZU inorder to reduce the Dep and increase the NBV
    Even if you are on not on EhP4, you can follow the same approach as above.... i.e.
    a. Change the Dep Key in asset master.... This will throw up new dep figure, on the basis of New Useful life and NBV at the start of the year
    b. Post a write up from ABZU....
    No need to do Asset to asset transfer in my opinion
    Only diff between EhP4 and Non EhP4 is that the differential depreciation would be lesser if you are on EhP4... i.e. instead of 5333 now, system may throw up depreciation amount of 5666.. So, you may need to post write up of 5666-5155
    br, Ajay M

  • Change in start date of tax depreciation in mid of year

    Hi Experts,
    Tax depreciation area is not for posting. The fiscal year is from Jan to Dec. I want to calculate tax depreciation from May 2011 based on Net Book Value of tax depreciation as on 30.04.2011. But once I change the start date of tax depreciation in asset master to 01.05.2011, the system ignores the previous depreciation so I am not getting the NBV of tax depreciation of 30.04.2011.
    Is any setting is required to get this. I can not do changes in posting rules since this tax depreciation is not for posting any thing.
    The fiscal year 2010 is closed and NBV of tax depreciation as on 31.12.2010 of one asset is 80000, If I change the start date of tax depreciation from 1.1.2011 then system correcly take NBV of 31.12.2010 for further depreciation calculation. But if i change the start date of depreciation in between of year the system is calculating depreciation based on NBV of 31.12.2010 but ignores the tax depreciation from 1.1.2011 to 30.04.2011, which I previously run using AFAB.
    Need your assistance to know is it feasible to do this.
    Thanks and Regards,
    Harshad

    Hi Harshad
    The behaviour of the system is very much correct, it is designed to behave that way...
    One, you should not have changed the dep start date....
    two, NBV in SAP is always taken to be NBV @ the start of the year....
    The best wayout I can suggest here is, if you are on EhP4 and EA-FIN active
    a. Change the Dep Key in the asset... You can maintain Time Dependant Dep Terms in asset master i.e. Dep Key X from Jan-Apr and Dep Key Y from MAy onwards
    b. This will however, calculate dep based on NBV at the start of the year, but based on new useful life
    c. Considering your eg: The system is posting more depreciation i.e. 5333 instead of 5155.... So, calculate this amount outside the system and post a Manual Write up ABZU inorder to reduce the Dep and increase the NBV
    Even if you are on not on EhP4, you can follow the same approach as above.... i.e.
    a. Change the Dep Key in asset master.... This will throw up new dep figure, on the basis of New Useful life and NBV at the start of the year
    b. Post a write up from ABZU....
    No need to do Asset to asset transfer in my opinion
    Only diff between EhP4 and Non EhP4 is that the differential depreciation would be lesser if you are on EhP4... i.e. instead of 5333 now, system may throw up depreciation amount of 5666.. So, you may need to post write up of 5666-5155
    br, Ajay M

  • 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

  • Job SM:SYNCHRONIZE USER DATA FOR NOTIFICATION canceled

    Dear SAP Guru,
    The BG job SM:SYNCHRONIZE USER DATA FOR NOTIFICATION is canceled every day and it´s
    generating shortdump. Our system is SAP EHP1 for SAP Solution manager.
    SAP ABA and SAP BASIS components are release 701 level 3.
    ST is release 400 level 19
    ST-PI is release 2008_1_700 level 1
    ST-A/PI is release 01L_CRM570
    Pls look on this shortdump.
    Runtime Errors         RAISE_EXCEPTION*
    Date and Time          22.03.2010 06:50:11
    |Short text                                                                                |
    |    Exception condition "CUSTOMIZING_NOT_FOUND" raised.                                           |
    |What happened?                                                                                |
    |    The current ABAP/4 program encountered an unexpected                                          |
    |    situation.                                                                                |
    |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                                                                                |
    |    A RAISE statement in the program "SAPLDSWP_UTILITY" raised the exception                      |
    |    condition "CUSTOMIZING_NOT_FOUND".                                                            |
    |    Since the exception was not intercepted by a superior                                         |
    |    program, processing was terminated.                                                           |
    |                                                                                |
    |    Short description of exception condition:                                                     |
    |                                                                                |
    |                                                                                |
    |    For detailed documentation of the exception condition, use                                    |
    |    Transaction SE37 (Function Library). You can take the called                                  |
    |    function module from the display of active calls.                                             |
    |    -                                                                                |
    |How to correct the error                                                                          |
    |                                                                                |
    |    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:                                                                                |
    |                                                                                |
    |    "RAISE_EXCEPTION" " "                                                                         |
    |    "SAPLDSWP_UTILITY" or "LDSWP_UTILITYU19"                                                      |
    |    "DSWP_GET_GLOBAL_CUSTOMIZING"                                                                 |
    |                                                                                |
    |    or                                                                                |
    |                                                                                |
    |    "SAPLDSWP_UTILITY" "CUSTOMIZING_NOT_FOUND"                                                    |
    |                                                                                |
    |    or                                                                                |
    |                                                                                |
    |    "RDSWP_NM_SYNC_USER_DATA " "CUSTOMIZING_NOT_FOUND"                                            |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                |
    *|   
    |System environment                                                                                |
    |    SAP-Release 701                                                                               |
    |                                                                                |
    |    Application server... "crsgrant"                                                              |
    |    Network address...... "10.128.32.175"                                                         |
    |    Operating system..... "Windows NT"                                                            |
    |    Release.............. "5.2"                                                                   |
    |    Hardware type........ "2x Intel 801686"                                                       |
    |    Character length.... 8 Bits                                                                   |
    |    Pointer length....... 32 Bits                                                                 |
    |    Work process number.. 13                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                |
    |    Database server... "CRSGRANT"                                                                 |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "SM1"                                                                      |
    |    Database user ID.. "SAPSM1"                                                                   |
    |                                                                                |
    |    Terminal.......... " "                                                                        |
    |                                                                                |
    |    Char.set.... "Czech_Czech.28592"                                                              |
    |                                                                                |
    |    SAP kernel....... 701                                                                         |
    |    created (date)... "Apr 12 2009 22:43:15"                                                      |
    |    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                              |
    |    Database version. "OCI_10201_SHARE (10.2.0.4.0) "                                             |
    |                                                                                |
    |    Patch level. 39                                                                               |
    |    Patch text.. " "                                                                              |
    |                                                                                |
    |    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."                |
    |    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...... 4181184                                                                              |
    |    Heap.... 0                                                                                |
    |    Page.... 24576                                                                                |
    |    MM Used. 873664                                                                               |
    |    MM Free. 170296                                                                               |
    |User and Transaction                                                                              |
    |                                                                                |
    |    Client.............. 001                                                                      |
    |    User................ "SOLMAN"                                                                 |
    |    Language key........ "E"                                                                      |
    |    Transaction......... " "                                                                      |
    |    Transactions ID..... "C27635DF574FF121B0470050569757E9"                                       |
    |                                                                                |
    |    Program............. "SAPLDSWP_UTILITY"                                                       |
    |    Screen.............. "SAPMSSY0 1000"                                                          |
    |    Screen line......... 6                                                                        |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLDSWP_UTILITY" - in                              |
    |     "DSWP_GET_GLOBAL_CUSTOMIZING".                                                               |
    |    The main program was "RDSWP_NM_SYNC_USER_DATA ".                                              |
    |                                                                                |
    |    In the source code you have the termination point in line 22                                  |
    |    of the (Include) program "LDSWP_UTILITYU19".                                                  |
    |    The program "SAPLDSWP_UTILITY" was started as a background job.                               |
    |    Job Name....... "SM:SYNCHRONIZE USER DATA FOR NOT"                                            |
    |    Job Initiator.. "SOLMAN"                                                                      |
    |    Job Number..... 00104000                                                                      |
    Have you some solution or advice?
    Best Regards
    Jakub

    Please could you check the following ?
    - Please ensure that the latest version of note 1172948 has been implemented
    - Please follow the recommendation in note 1314587.
    - Check table 'DSWPGLOBALCUSTOM' and ensure that the entry 'DTMLOG' is available.  Create the entry if missing.
    These procedures will solve this issue.

  • 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

Maybe you are looking for

  • Exception only occuring during stress test

    We are trying to get ready to release a beta version of the software I'm working on.. so part of getting ready for that was to try set up some stress tests and hit the server with multiple requests for the same page.... Not sure exactly how many it i

  • Positioning of Screen

    I have a little card game, when I run it the screen is in the top left hand corner of the screen? Is there any way I can make it start in the middle of the screen? Thanks, Johnny C

  • How to compile COM 1 data with LabVIEW?

      I have a device connected to my COM 1 port. How do I input data with that into labVIEW? The program that comes with it is really elementary, it only shows me the data that the comes straight from the device, no analysis.  Its like labVIEW and MAX d

  • As i was using my iphone, it suddenly turned off and it wont come back on. what is the best solution for my problem?

    As i was using my iPhone, it suddenly shut off without being shut off by anyone.i tried to turn my iPhone back on several times and nothing has worked. what could be the problem?

  • Workflows are not working with UAG

    Dear Support, I've developed a SharePoint Designer 2010 platform based workflow which contains 2 stages. First stage contains 'Start Feedback Process' whereas the next stage contains 'Start Approval Process'. The workflow runs manually. The workflow