Settlemnt Rule Error Chaos!!

Hi,
I have a Project pertaining to 2003 with a settlement rule error which has resulted in choas. There was a settlement rule error in 2002 and someone has tried to correct the error by adding new settlement rules - there are currently 58 rules to date! Production has run in all of the settlement rules. I now want to correct this rule in order to close the project and need to add a new rule (no 59). However when I try to insert an end date to no 58 I get a message that the start date of no 58 contradicts the close date of no 27. I've tried changing this end date but SAP won't let me use a prior date nor will it let me use a date after the start date of no 58. As I can't change the start date I am in the position where I can't move forward.  All help or suggestions will be greatly appreciated!!
Regards
Juliet

Hi,
Have experienced how messy and chaotic settlement rules can be. First, wish you all the best and hope you have a lot of patience.
As for my thoughts on this :
How long have you used the Settlement Rule No.58?, mean how many settlements have happened using this rule. If possible, reverse all of these settlements.
For. Ex. if Rule No.58 was used during the period 01/08 till 04/08 with a monthly settlement run. Then reverse all the 4 settlements, in which case the rule 58 can be modified or could even be deleted to recreate.
I know that this is not really a very good option considering that it is quite an old project spanning across fiscal years. But you could still reverse in the current period and resettle it after all the rules are set in order.
If you already have come up with something, please do share it.
Best of luck,
Chetan

Similar Messages

  • Import rules, error message "Invalid system"

    Hi,
    When importing rules under Rule Architect - Import rules, error message "VBS is invalid system" . In the configuration tab we have system  and System Name defined as VBS, test connection successful.
    Why is it giving an error message VBS is invalid system? Please advise.
    Thanks,
    Sri

    Hi,
    Is it rule import after taking an export from other system? In that case, make sure destination system name doesn't contain any space in it.
    Also, make sure text and auth Objects are uploaded for VBS system before doing rules import.
    Regards,
    Sabita

  • SAP BPC 7.5 NW business rules error

    Hi,
    I am facing business rules error in BPC 7.5 NW SP 01 client. When i click on any business rules for ex- carry forward rules to fill in the information, it's giving error like " Application has genarated an exception that could not be handled" Process id = 10x104c (4172) Thread id = 0x1170
    No recent changes happend in the servers. Any suggestions plz.

    Hi,
    I am facing business rules error in BPC 7.5 NW SP 01 client. When i click on any business rules for ex- carry forward rules to fill in the information, it's giving error like " Application has genarated an exception that could not be handled" Process id = 10x104c (4172) Thread id = 0x1170
    No recent changes happend in the servers. Any suggestions plz.

  • Work order SETTLEMENT RULE Error

    Workflow Work order SETTLEMENT RULE Error, but settlement is done no problem in updation. But notification error there.
    Notification of completion cannot be generated
    Problems occurred when generating a mail
    Error '9' when calling service 'SO_OBJECT_SEND'
    Error handling for work item 000112476185
    Work item 000112476185: Object 000020154849 method UPDATESETTLEMENTRULE cannot be executed
    Call transaction was canceled.
    No errors occurred -> Details in long text
    No errors occurred -> Details in long text
    Please advice what could be the reason this error.
    Best Regards,
    Prabhakar

    Message no. WL821
    Message no. FD009
    Message no. WL863
    Problems occurred when generating a mail
    Message no. SWF_RUN534
    Error handling for work item 000133673828
    Message no. SWF_RUN630
    Error '9' when calling service 'SO_OBJECT_SEND'
    Message no. SWF_RUN535
    Thanks,
    Prabhakar

  • Net bridge design rule errors

    Multisim 10.1.197 and Ultiboard 10.1.197
    I could not get a net bridge to work in a Ultiboard layout, so I tried in a simplified circuit:  
    In Multisim, place a connector with several pins, for example HDR1X10.
    Place a DGND and GROUND. Connect the first to pin 1. Connect the second to pin 5.
    Transfer to Ultiboard
    Rotate HDR1X10 so the pins numbers increment left to right  
    Place traces on the top layer so the pads of a net bridge connects one trace to another 
    Place a net bridge, picking GND and 0 (also tried 0 and GND)
    This gives Design Rule Errors:
       Unused pin is connected to NET = GND
       Unused pin is connected to NET = 0  
    Is there a work around?  
     Ray

    I am having the  same problems.  This is a very important feature that needs to work since there is no proper work around.  This is always the case when there are ananlog and digital grounds that need to be kept separate, but also need to be connected somwhere in a very controlled fashion.  I've followed the instructions exactly but what I get is a net bridge with no nets assigned to it's terminals.  You can connect it up but you get the DRC errors as stated earlier.
    This can be manually fixed by going into the  netlist editor and selection each of the nets to be connected and adding on pin from the net bridge to each (NB1, pin _).  This removes the DRC error and everything is happy.
    The only problem is when you forward annotate again you lose the NB pin assignments and you have to edit the netlist again.
    I tried a part in MS with the net bridge as the footprint, but UB will not impor the net bridge when you do that.  To get around that I have a 'netconnect' part with just two dots and a silkscreen box around it.  This can be placed where you want the bridge and will import each time.  This is just a marker wheer you want the bridge to be.  You still have to place the bridge manually and edit the netlist to fix the DRC error.
    This is a bug.  I should be able to assign the netbridge as the footprint of an MS symbol and have it come in with the right netlist connections when I forward annotate.   Alternatively, the netbridge assignments should be made to stick when the netlist is imported again.
    David B

  • How do we use Data rules/error table for source validation?

    How do we use Data rules/error table for source validation?
    We are using OWB repository 10.2.0.3.0 and OWB client 10.2.0.3.33. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
    I reviewed the posting
    Re: Using Data Rules
    Thanks for this forum.
    I want to apply data rules to source table/view and rule violated rows should go to defined error table. Here is an example.
    Table ProjectA
    Pro_ID Number(10)
    Project_name Varchar(50)
    Pro_date Date
    As per above posting, I created the table in object editor, created the data rule
    NAME_NOT_NULL (ie project name not null). I specified the shadow table name as ProjectA_ERR
    In mapping editor, I have projectA as source. I did not find error table name and defined data rules in table properties. It is not showing up the ERR group in source table
    How do we bring the defined data rules and error table into mapping?
    Are there any additional steps/process?
    Any idea ?
    Thanks in advance.
    RI

    Hi,
    Thanks for your reply/pointer. I reviewed the blog. It is interesting.
    What is the version of OWB used in this blog?
    After defining data rule/shadow table, I deployed the table via CC. It created a error table and created the all the source coulmns in alphabatical order. If I have the primary key as 1st coulmn (which does not start with 'A') in my source, it will apprear middle of of columns in error table.
    How do we prevent/workaround this?
    If I have source(view) in sch A, how do we create Error table in Sch B for source(view)?
    Is it feasible?
    I brought the error table details in mapping. Configured the data rules/error tables.
    If I picked up 'MOVE TO ERROR' option, I am getting "VLD-2802 Missing delete matching criteria in table. the condition is needed because the operator contain at least one data rule with a MOVE TO ERROR action"
    On condition Loading - I have 'All constraints' for matching criteria.
    I changed to "no constraints' still I get the above error.
    If I change to 'REPORT' option instead of 'MOVE TO ERROR' option, error goes off.
    Any idea?
    Thanks in advance.
    RI

  • Validation Rule Error :Invalid Member Name In Lookup ({|0|}) value

    We defined fdm validation rule as follows.
    |Actual, April, 2010, YTD, ENTITY CURRENCY, Mumbai, TotalAssets, [NONE], [NONE], [NONE], [NONE], [NONE]|-|Actual, April, 2010, YTD, ENTITY CURRENCY, Mumbai, TotalLiabilities, [NONE], [NONE], [NONE], [NONE], [NONE]|= 0
    After testing the above rule definition, it gives below error message.
    Err = Invalid Member Name In Lookup ({|0|}) value in ID indicates invalid member)
    Scenario: ACTUAL [1]
    Year: 2010 [2010]
    Period: APRIL [83886080]
    View: YTD [2]
    Entity: MUMBAI [7]
    Parent Entity: MUMBAI [7]
    Value: ENTITY CURRENCY [-1]
    Account: TOTALASSETS [150]
    ICP: [NONE] [-1]
    C1: [MISSING_VALUE] [-1]
    C2: [NONE] [0]
    C3: [NONE] [0]
    C4: [NONE] [0]
    Lookup Error (2)
    Err = Invalid Member Name In Lookup ({|0|}) value in ID indicates invalid member)
    Scenario: ACTUAL [1]
    Year: 2010 [2010]
    Period: APRIL [83886080]
    View: YTD [2]
    Entity: MUMBAI [7]
    Parent Entity: MUMBAI [7]
    Value: ENTITY CURRENCY [-1]
    Account: TOTALLIABILITIES [-1]
    ICP: [NONE] [-1]
    C1: [MISSING_VALUE] [-1]
    C2: [NONE] [0]
    C3: [NONE] [0]
    C4: [NONE] [0]
    Also we could see in the Expression after lookup substitution (scratch pad): we are getting 0-0=0.
    Please provide you inputs.

    I have not looked closely, but C1 is showing as "Missing Value". Have you checked to see if [None] is a valid member for the account you have selected (TotalLiabilities)?

  • GRC10- HR Trigger BRF+ rule error

    Hi,
    We are facing an error in HR trigger. The BRF+ is configured as per the note Note 1591291 - GRC 10.0 - HR Trigger configuration.
    The BRF+ rule has decision table which satisfies the condition for new hire. The infotype: 0105 and subtype: 0001
    After the new hire event the trigger is activated in GRC system but the log gives a following error Message:
    Error occurred during the processing of Rule 'Rule_1'
    Error occurred during the processing of Loop 'Loop_1'
    Error occurred during the processing of Rule 'Rule_2'
    Error occurred during the processing of Decision Table 'Decision_Table_HR'
    No match found for the given context (DECISION_TABLE_HR)
    Rules are not satisfied for Employee ID 00000019
    The rules configured are as per the SAP guide.
    1.     How do you analyze the error in the BRF+ rules
    2.     Have anyone come across similar situation
    Regards,
    Prasad Chaudhari

    Hi Prasad
    I am also getting the same error. I have configured the decision table exactly as per the SAP note, and even simplified my rules to only include the CREATE function.
    My SLG1 log picks up the same error.
    Did you find a fix for this on your side ?
    Please help.
    Rgrds
    Sameel

  • Update Rule error while loading the data

    Hello All,
    I tried to do the init load for the datasource 2LIS_02_VAKON (Sales Document Condition), But it error's out in the Update rule saying:
    Short text: Error when generating the update program
    Long Text:  Diagnosis
         An error occurred during program generation for InfoSource 2LIS_11_VAKON
         and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
         rules.
    Procedure
         Check and correct your update rules and then generate the update program
         again. You can find help on the error in the error log.
    The update rule looks very fine. I even deleted it and re created, but no success..... Please give me your thoughts abt it..... Any suggestions will be great for me.....

    Hello Gokul,
    I could'nt see any analyse button in RSMON. This is the only error message I could get from the Process monitor:
    Short text: Error when generating the update program
    Long Text: Diagnosis
    An error occurred during program generation for InfoSource 2LIS_11_VAKON
    and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
    rules.
    Procedure
    Check and correct your update rules and then generate the update program
    again. You can find help on the error in the error log.
    Do you expect something else ? Also I went through your OSS note, they are asking to apply support pack 18. Is this a serious issue to apply SP? Because in Quality and Prod it loads fine......
    Please let me know your idea

  • Settlement rule error

    Hi,
    I am facing as issue while settling costs to internal order. The system is giving warning message "Enter a percentage, equivalence number, or amount"
    Diagnosis
    You have entered at least one distribution rule which contains neither a percentage nor an equivalence number nor an amount.
    Procedure
    For each distribution rule, you must enter either a percentage, an equivalence number or an amount.
    Alternatively, and depending on the situation and how you want the system to behave, one of the following is possible or required:
    You want to enter the percentage, equivalence number or amount later.
    You can ignore this warning.  However, you should check that the appropriate values are entered before settlement.
    You want to enter a percentage, an equivalence number, or an amount. However, the relevant field will not accept input, or is not displayed.
    Go to the settlement profile you are using and check that one of "Percentage settlement", "Equivalence numbers", or "Amount settlement" has been switched on.  You can find out which settlement profile you are using from the "Parameters" section of the screen in settlement rule maintenance.
    (Press F5 to proceed to customizing.)
    You receive this message other than in settlement rule maintenance - for example, when saving an order or a WBS element.
    Go to settlement rule maintenance and check the individual distribution rules.
    This error is coming only from past one week. Any pointers towards the resolution/ or the reasons for the error will be highly appreciated.
    Regards,
    S.Sumana

    Hi,
    On further analysis, we found that there was a settlement (in KO03) that took place without specifying percentage or equivalence amount. Is there anything that can be done like reverting the settlement so that this message doesnot appear.
    Regards,
    S.Sumana

  • Exceptions in Substep:Rules Error

    Hi Friends,
    I am new to this portal and I seek you guys help to resolve the below error its very urgent.
    I have encountered an error while updating the data from PSA to Infocube i.e. Purchasing Data Cube 0PUR_C01 from the Data Source 2LIS_02_ITM in R3 extraction.
    The Error is-
    "Exceptions in Substep: Rules".
    "Messages for 101 data records saved: request is RED according to configuration."
    "Processing Terminated."
    Data Package2: Errors during processing.
    "RSDS 2LIS_02_ITM........."
    :Error- Messages for 60 records saved:request is Red according to configuration."
    Updating to Infocube 0PUR_C01
    "Error while updating to target 0PUR_C01(type Infocube)"
    "Messages for 41 data records saved:request is Red according to configuration."
    "Processing Terminated".
    The above in RED is the entire error.
    When I explored the error message to see the long text then following was appeared---
    " Run time error while executing rule-->see long text RSTRAN 301"
    Diagnosis
    An error occurred while executing a transformation rule: The exact error message is:
    The argument 'X' can not be interpreted as a number.
    The error was triggered at the following point in the program: GPCRTJMK2HFEFVHGT8LWAALN9K1    734
    System Response
    Processing the data record has been terminated.
    Procedure
    The following additional information is included in the higher-level node for the monitor:
    - Transformation ID
    -  Data record number of the source record.
    - Number and name of the rule which produced the error.
    Procedure for System Administration.
    Kindly anybody can help me out to resolve the above error and explain why this error occurred.
    Thanks
    Prasad

    Hi Prasad,
    This clearly says that error is in Routine in the transformation.
    Can you check the any routines maintained in the transformation? The issue is that some logic is performed in the routine and exceptions are not handled in it properly.
    Go to SE38 tcode and display program 'GPCRTJMK2HFEFVHGT8LWAALN9K1' and go to line 734. This should give you a hint of ABAP code which is not handled properly.
    Let me know your findings and then we can have further look.
    Thanks
    Amit

  • While creating Update rules -"Error Info source does not exist"

    While creating an update rule I am getting an error that Info source doesnot exist though the inf source is active.
    here is error:
    No communication structure exists in version  abc...   A
    Message no. RSAU251
    Diagnosis
    In order to be able to maintain the update rules an active communication structure must be available.
    Procedure
    This error message can have two causes.
    No active communication structure exists.
    Activate the communication structure in the Data Warehousing Workbench.
    No communication structure exists for the InfoSource.
    Create a communication structure in the Data Warehousing Workbench for the InfoSource.
    <<text removed>>
    Thanks,
    Vasu
    Edited by: Matt on Apr 26, 2010 9:31 AM

    Hi Vasu,
    as it clearly shows below message
    No communication structure exists for the InfoSource.
    Create a communication structure in the Data Warehousing Workbench for the InfoSource.
    Create an info source first and assign it to your datasource and map the fileds in transfer rules and activate it.
    Then try to create the update rules between your target and info source.
    Hope this helps.
    Regards,
    Reddy

  • Transformation Rule: Error while loading from PSA to ODS using DTP

    Hi Experts,
    I am trying to load data from PSA to ODS using DTP. For about 101 records I get the following error:
    "Runtime error while executing rule -> see long text     RSTRAN     301"
    On further looking at the long text:
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        Overflow converting from ''
        The error was triggered at the following point in the program:
        GP4808B5A4QZRB6KTPVU57SZ98Z 3542
    System Response
        Processing the data record has been terminated.
    Procedure
          The following additional information is included in the higher-level
         node of the monitor:
         o   Transformation ID
         o   Data record number of the source record
         o   Number and name of the rule which produced the error
    Procedure for System Administration
    When looking at the detail:
    Error Location: Object Type    TRFN
    Error Location: Object Name    06BOK6W69BGQJR41BXXPE8EMPP00G6HF
    Error Location: Operation Type DIRECT
    Error Location: Operation Name
    Error Location: Operation ID   00177 0000
    Error Severity                 100
    Original Record: Segment       0001
    Original Record: Number        2
    Pls can anyone help in deducing and pointing this error to the exact spot in the transformation rule
    Thanks & Regards,
    Raj

    Jerome,
    The same issue.
    Here are some fields which are different in terms of length when mapped in transformation rules
    ODS                    |Data Source
    PROD_CATEG     CHAR32           |Category_GUID      RAW 16
    CRM_QTYEXP     INT4          |EXPONENT      INT2
    CRM_EXCRAT     FLTP16          |EXCHG_RATE     Dec 9
    CRM_GWEIGH     QUAN 17, 3     |Gross_Weight     QUAN 15
    NWEIGH          QUAN 17, 3     |Net_Weight     QUAN 15
    CRMLREQDAT     DATS 8          |REQ_DLV_DATE     Dec 15
    The difference is either some dats field are mapped to decimal, or the char 32 field is mapped to raw 16 OR Calweek, Calmonth is mapped to Calday
    Both mostly all the ods field size is greater than the input source field.
    Thanks
    Raj

  • Error while validating Business Rule (Error Cause: nativeGetNewTLA Rule)

    Hi, I am receiving an error while validating business rules
    An error occurred in: Rule:HypLive.Plan1.Product Interest
    A validation error was received from the Planning server 'http://abc:8300/HyperionPlanning/servlet/HspAppManagerServlet?appname=HypLive'.
    'Error:
    Error Cause: nativeGetNewTLA Rule HypLive.Plan1.Product Interest'.

    Are you able to validate the rule in EAS (or Calc Manager)?
    Normally nativeGetNewTLA Rule is followed by out of memory errors like java.lang.OutOfMemoryError,
    Increase the heap size to 1024, re start Planning and try validating it again.
    Cheers..!!

  • Duplicate Facts found : Business Rule Error

    Hi ,
    I am trying to invoke the bunisess rules in loop, that means it has call the business rules decision service several times,
    from BPEL, In BPEL it loops correctly and first time it gives proper results , when looping second time I am getting
    the following error, I am not getting proper clue anywhere for this, plz chck this and let me know the solution for this
    asap. Thank you very much in advance.
    **ERROR**
    /xmlns.oracle.com/CheckXXX_BPEL/DecisionService_CheckXXX_PL">Error while executing a rule session unit of work, duplicate facts found.
    The rule session CheckXXX_BPEL:270012 failed because duplicate fact objects of the fact po.rules.BRSXXXValidation exists, cant identify which one to take.
    Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
    </ns0:errorMessage>
    </ns0:errorInfo>
    </part></operationErroredFault>

    Hi
    Please note that you create rules using some facts . Those rules gets executed whenever it encounters those facts, intern they create more facts. These new facts generated as a result of executing the first rules, can be used in next rule and so on.... So, rules create facts, and those facts will willl fire new rules.
    The issue you have is due to having duplicate facts created and the rule not coded properly.
    You may refer : C.6 How Do I Correctly Use an RL Language Cross Product? in http://download.oracle.com/docs/cd/B31017_01/web.1013/b28965/faq.htm
    Hope this helps!
    Cheers
    Anirudh Pucha

Maybe you are looking for