"No valid settlement date could be determined"

When trying to create partial settlement we are getting the error "No valid settlement date could be determined"

Already you opened a similar thread on 6th and closed as Unanswered.  Check here
["No valid settlement date could be determined"|"No valid settlement date could be determined";
Now you have opened a new thread which could have been avoided by changing the status of the above thread.  Anyway, though lot of notes are there, you can have a look at the following notes:-
=> Note 75778 - Consulting/troubleshooting for rebate processing
=> Note 105681 - Consulting: New rebate procedure
=> Note 1065418 - Incorrect date calculation within rebate processing
G. Lakshmipathi

Similar Messages

  • Rebates" No valid settlement date could be determined"

    When trying to create partial settlement we are getting the error "No valid settlement date could be determined"

    Already you opened a similar thread on 6th and closed as Unanswered.  Check here
    ["No valid settlement date could be determined"|"No valid settlement date could be determined";
    Now you have opened a new thread which could have been avoided by changing the status of the above thread.  Anyway, though lot of notes are there, you can have a look at the following notes:-
    => Note 75778 - Consulting/troubleshooting for rebate processing
    => Note 105681 - Consulting: New rebate procedure
    => Note 1065418 - Incorrect date calculation within rebate processing
    G. Lakshmipathi

  • "could not determine central location: use "-enginehome" to set manually"

    We are trying to install "as_xellerate_id_prov_853". But when I try to run "install_server.sh" on the linux m/c, it gives the error:
    "not a valid identiferrt: 'PATH
    could not determine central location: use "-enginehome" to set manually".
    Please give me some inputs to solve the issue.
    Thanks

    Anyone?

  • Settling Rebate Agreements with Validity Start Date not Start of the Month

    Hello Experts,
    I am currently trying to settle a rebate agreement with validity dates November 20, 2011 to December 31, 2011. However, after the credit memo is created, I noticed that the Service rendered date is today's date, but I expected it to be the same as my Settlement Date = November 30, 2011 (a month-end). Please advise if this is normal. If not, please advise how to correct the automatic entry of dates.
    Thanks,
    M

    Hi
    Kindly let us know what is the rebate agreement type that has been used for which you are facing problem and for which rebate agreement type you are getting the month end date.Check wheather scale basis is B(Value scale) has been maintained or not for the rebate agreement for which you are getting problem.So check the differences between the two rebate agreement types.As The service rendered date of the invoice line item is used to determine the validity of a rebate condition record
    Regards
    Srinath

  • Could not create a valid GL date rejection for PA transactions to GL

    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    Praveen

    Praveen Bharadwaj wrote:
    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    PraveenPlease see these docs.
    PAGGLT, PASGLT gives 'Could Not Create A Valid GLDate', even when GL data is re-open. [ID 330874.1]
    PRC: Interface Labor Costs to GL (PALDLC) Will Not Interface, CDL.Batch_Name Is Null [ID 437301.1]
    PALDLC and PASDUC Error - Could Not Create A Valid GL Date For Provider [ID 338330.1]
    Distribute Labor Cost Exception-Could Not Create A Valid GL Date [ID 418675.1]
    PAXACCPB - PRC: Create Accounting Gets Error 95325 Gl Date Not An Open Or Future Enterable Period [ID 951452.1]
    Thanks,
    Hussein

  • IPhone nike+ Sync - Data Could Not Be Validated By Server

    Hi
    I have been using my iPhone 3GS with cardio equipment at my local gym (TechnoGym Vario Series) which has built in docks that among other features, store workout data to the iPhone to sync with nike+. This had been working perfectly since I started using it last month.
    In the past week I have been unable to sync any of my past 6 sessions to nike+ because I get the following error message:
    "Your workout data could not be sent to nike.com because the data could not be validated by the server."
    I understand how to access the xml files on the device and force a re-synchronisation by moving them to the "latest" folder, but the error message persists and none of my past 6 workout sessions will sync with nike+.
    I have tried to sync the data on 2 different machines, one Windows 7 64-bit and the other Windows XP 32-bit but exactly the same error occurs. Both are running iTunes 9 which I suspect may have been what has broken this feature?
    I really hope I can find a solution to this problem and would be grateful for any help. I am happy to provide any information required including copies of the xml files affected.
    Many thanks.

    Hi
    I have had this response from nike plus and this cleared the error when uploading my runs.
    Sometimes it happens that the iPod register the runs as already uploaded,after a not succesful uplaod.
    Then the only way to upload them again is the following.
    First you need to enable to view hidden files ( Control-panel >Folder Options>enable to view hidden files.)
    1. Dock your iPod nano and allow iTunes to launch. Select your iPod from the device tree on the left-hand side of the screen in iTunes.
    2. On the Summary page, make sure that "Enable disk use" is selected.
    3. From your Start menu, navigate to Start > All Programs > Accessories > Windows Explorer. (Please note that this program is not the same as Internet Explorer, the web browser.)
    4. In Windows Explorer, click Tools > Folder Options and select the View tab. Make sure that "View hidden files and folders" is selected.
    5. Find your iPod nano in the device list under "My Computer." It will appear as an external drive; mine, for example, is Drive E, and it's labeled "Your iPod." Yours should have a similar name. Click on it.
    6. Navigate your iPod nano's folders as follows: iPod_Control > Device > Trainer > Workouts > Empeds. In the Empeds folder, you'll see one or more subfolders with alphanumeric filenames. These filenames correspond to your Nike+ sensors. Explore the folders until you locate the one containing the runs you'd like to manually re-upload. They'll probably be in the "synched" folder within your most recent sensor's folder.
    !!!!!!!!!!!Important ,you need to delete the settings.plist file in the sensor folder which stores your login information to make sure for next time you will upload to the correct profile
    7. Drag and drop each run folder you'd like to manually re-upload from "synched" to "latest."
    8. Eject your iPod nano and close iTunes.
    9. Dock your iPod nano and allow iTunes to launch. Your run data should upload
    Hope this helps.
    C

  • Error: "substitution/validation could not determined" in LAE (FILA)

    Hey, I am trying to simulate a process in the SAP Lease Account Engine (FILA) under transaction FILAEXAM. The system displays the following error message:
    Classification: Validation/substiution could not be determined
    Message no. FILAE604
    Diagnosis
    The system could not determine the check rule for validation/substitution for Lease Accounting.
    Procedure
    Check Customizing for the assignment of check sequences and check steps.
    I already tried everything in customizing (IMG->Financial Accounting->Lease Accounting-> Specifications for Controlling Processing->Financing Classification) to fix this error, but the error always remains.  Can anyone help?

    I don't know where to customize the check sequences. I already checked customizing under "Value Determination Using Substitution", "Financing classification", and "Validation", but the error always remains.
    Are there no Lease Accounting experts at all who can help me?

  • Preference determination threshold value valid to date

    Hi All,
    We have an issue with Preference threshold value valid to date for many materials. As per our understanding the threshold value to date should be 31.12.9999 for all materials, but many materials valid to date is ended with 3rd Aug 2011. We are not very sure how the system determined valid to date as 3rd Aug 2011 instead of 31.12.9999 for specific materials.
    Many C-LTVD's status is negative instead of positive due to wrong valid to date. The issue is in production system, not able to correct already issued C-LTVD's since revocation is not possible from negative to positive. Planning to re-issue manually prepared C-LTVD's to customer for impacred part numbers.
    Any idea what is teh root cause behind setting up the threshold value valid to date as 3rd Aug.
    Regards,
    Lakshmikanth

    Hi Jasmit,
    The issue not resolved yet, no idea what happend in the system for to date of threshold value validity.
    We provided report to list out of such part numbers and rectified manually.
    Thanks
    Lakshmikanth

  • The Organizational Data could not be determined. Inform system admin

    Hello All,
    I am able approve PO from EBP, but getting this error 'The Organizational Data could not be determined. Inform system admin' when trying to appove PO from Universal Work List (portal) or when I try to open the work item via Busines Workplace (SAP GUI). Can anybody tell me if there is any config missing? or any suggestions to resolve this issue.
    Any kind of help appreciated and rewarded.
    Thanks,
    Shekar

    Hi Chandra,
    Please check the Purchasing Organization and Purchasing Group in PO if they are not populated then this error is triggered. Please also check the user settings whether Purchasing organization information is maintained or not.
    Regards,
    Ravi G

  • Valid settlement rules

    We received a request from the business to block time entry charges for WBS with C* status. Also, block time
    charges for PM order and Network order if their settlement receiver WBS is in C* status.
    I was trying to find a transaction or functionality in SAP that will provide me all valid settlement rules (senders and receivers) in a given project.
    Before users can charge labor time to a charge object 'orders' (PM or network orders), validity of the settlement rules need to be checked. If there's a valid settlement rule, the status of the settlement receiver will be checked to determine if time entry for the charge object can be allowed.
    Basically, what I'm looking for is anything that will give me the valid settlement rules of the settlement receiver given a specific period or date.

    Hi
    Even though system allows you to specify the percentage in PM order ,it will not allow you to settle the cost.Just execute the settlement process KO88 and check
    regards
    thyagarajan

  • Valid to dates on KONH table not matching the dates in A* tables- SD pricin

    We have an issue in our KONH/A* tables. Please review the data below:
    A583: ( This is for a Z condition type ZCTR)
    MANDT KAPPL KSCHL  VKORGAU MATNR                DATBI      DATAB      KNUMH                                                                               
    028   V     ZCTR   0006    000000000000031886   03/31/2006 01/01/2006 0071519869
    028   V     ZCTR   0006    000000000000031886   06/30/2008 03/02/2008 0071519869
    KONH
    MANDT KNUMH  DATAB      DATBI    
    028   0071519869 01/01/2006 12/31/9999
    If you look in VK13, for this ZCTR record/material you will see the following dates.  We can see that two records have the same KNUMH , is this a SAP bug?
    Also what is the difference in dates in KONH and A* tables ? I see that the valid from dates match but the valid to date in KONH is the valid to date of the last record in the A table.                                                                           
    MANDT KAPPL KSCHL  VKORGAU MATNR                DATBI      DATAB      KNUMH                                                                               
    028   V     ZCTR   0006    000000000000031886   03/31/2006 01/01/2006 0071519869
    028   V     ZCTR   0006    000000000000031886   12/31/2007 03/13/2007 1032266853
    028   V     ZCTR   0006    000000000000031886   03/01/2008 01/01/2008 1061605348
    028   V     ZCTR   0006    000000000000031886   06/30/2008 03/02/2008 0071519869
    028   V     ZCTR   0006    000000000000031886   12/31/9999 07/01/2008 1093084511

    Thanks for putting so much thought into this, but I still fail to see the advantage/reason of maintaining the original dates in KONH if the new dates are prior to the original date ( in case of valid to). We always have the change log to determine the origibal dates with which the record was created.
    Thanks for all the responses.
    The duplicate KNUMH is causing the issue for us:
    A583: ( This is for a Z condition type ZCTR)
    MANDT KAPPL KSCHL VKORGAU MATNR DATBI DATAB KNUMH
    028 V ZCTR 0006 000000000000031886 03/31/2006 01/01/2006 0071519869
    028 V ZCTR 0006 000000000000031886 06/30/2008 03/02/2008 0071519869
    As you can see two records have the same KNUMH. We were trying to run archiving for condition records and came across an issue.
    As there is a duplication of KNUMH ( which is wrong) the program does not pick up the 2006 record . This is because it considers the 2008 record to be compared against the residency date and skips the older one too. We tried changing the validity dates of the 2008 record to an older date so that both are within the residency date. This is how the records looks now :
    028 V ZCTR 0006 000000000000031886 06/30/2005 03/02/2005 0071519869
    028 V ZCTR 0006 000000000000031886 03/31/2006 01/01/2006 0071519869
    KONH
    Cond.record no. Usage Table Application Condition type Valid From Valid To
    0071519869 A 583 V ZCTR 03/02/2005 12/31/9999
    Once we did this the archiving program was able to pick this record up.
    Has any one faced this issue before? Is this a known SAP issue ? I could not find any OSS for this.
    Edited by: harikrishnan balan on May 28, 2009 11:03 PM

  • Table to find BOM valid-till-date

    Hi Friends,
      I have to check the vality of BOM components,  through transaction CS03 i could able to see the Valid-till-date and i need to check the same in my code.
    Looked into following tables, thre is a field valid-from-date(DATUV) but i'm not getting field Valied-to-date(DATUB).
    MAST Material to BOM Link
    EQST Equipment to BOM Link
    STAS BOMs header
    STKO BOM header
    STPN BOM follow-Up control
    STPO BOM item
    STPU BOM sub-item
    STST Standard BOM link
    STVB Bills of material - Serialisation of posting
    STZU Permanent BOM data
    Can any one please help me.
    Thanks in advance.
    /Kiran

    Hi kiran,
    I think the Valid-to-date is in table AEEF-DATE_HI which can be linked with the BOM Header table STKO by field AENNR. Try this.
    Otherwise you can also get the Date using the FM CS_BOM_EXPLOSION....
    Use it as follows;
    CALL FUNCTION 'CS_BOM_EXPLOSION'
    EXPORTING
    AUMNG = 0
    CAPID = ' '
    DATUV = DATVAL "valid-from date
    EHNDL = '1'
    MKTLS = 'X'
    MEHRS = 'X'
    MMORY = '1'
    MTNRV = MATNR
    STLAL = LAL "like mast-stlal default '1'
    STLAN = LAN "like mast-stlan default '2'
    SVWVO = 'X'
    VRSVO = 'X'
    WERKS = WERKS
    mmaps = 'X'
    IMPORTING
    TOPMAT = STARTMAT "includes structure CSTMAT
    TABLES
    STBD = TBD "includes structure CSXDOC
    STBE = TBE "includes structure CSXEQUI
    STBK = TBK "includes structure CSXKLA
    STBM = TBM "includes structure CSXMAT
    STBP = TBP "includes structure CSXGEN
    STBT = TBT "includes structure CSXTDL
    EXCEPTIONS
    ALT_NOT_FOUND = 1
    CALL_INVALID = 2
    MISSING_AUTHORIZATION = 3
    NO_BOM_FOUND = 4
    NO_PLANT_DATA = 5
    NO_SUITABLE_BOM_FOUND = 6
    OBJECT_NOT_FOUND = 7
    CONVERSION_ERROR = 8
    OTHERS = 9.
    After the function call you will get the Valid to Date(DATEUB) from table STBP.
    Hope this Helps you...
    Regards
    Karthik D

  • No value could be determined for variable (Material)

    Hi,
    I have Planning filter where im restricting the Material with a Zvariable. This is a Customer Exit variable. This works fine in development but throws me error No value could be determined for variable (Material) in QA system.
    Could some one help me in resolving this in
    Thanks

    either your code is wrong or you just have no data.
    debug the code, check if you do have the desired data according to your code.
    regards
    Cornelia

  • Could not determine value for variable 0P_FVAEX (or 0P_CTPCA)

    I get the below error while accessing a query on the planning Info Cube. I used the SAP Exit variable Most Current Data (Transactional InfoCube) (0S_RQTRA) in the query for the Characteristic - Request ID (0REQUID) to extract the data from the yellow request too.
    I do not use the below variables as in the below eror in my query at all. Please assist.
    Diagnosis
    This error diagnosis is specific only to the variables 0P_FVAEX or 0P_CTPCA !
    Termination message BRAIN 632 appears:
    Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).
    System Response
    1.     Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA
    With queries from the CO application, both SAP-Exit-Variables look for an entry for 'controlling area'. With this controlling area from the selection screen, the SAP-Exit-Variables program reads the attributes for InfoObject 0CO_AREA (controlling area).
    With queries from the FI application, the SAP Exit Variable 0P_FVAEX looks for an entry for 'company code'. With this company code from the selection screen, the SAP Exit Variables program reads the attributes for InfoObject 0COMP_CODE (Company Code).
    0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries). 0P_CTPCA determines the currency type of the profit center local currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.

    Hello,
    you need to take a closer look at your query. Somewhere you used one of the 0P_* exit variables, which work only for controlling related InfoCubes. Use your own variables.
    Regards,
    Marc
    SAP NetWeaver RIG

  • Error Message : " No value could be determined for Customer Exit Variable "

    Hello BI Experts ,
    I have created a "ZYTD_PERIOD" Customer Exit Variable  Interval  Mandatory and ready for input check mark removed.
    The reference character is '0FISCPER' .
    I want to have YTD figures when the user enter single Fiscal Year Period for variable 0P_FPER.
    So I have written below code in SE37 : EXIT_SAPLRRS0_001 and include program : ZXRSRU01
    ==================================================================
      case i_vnam.
                  WHEN 'ZYTD_PERIOD'.
                  IF I_STEP = 2.
                  LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
                  CLEAR L_S_RANGE.
                  L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
                  L_S_RANGE-LOW+4(3) = '001'.
                  L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
                  L_S_RANGE-SIGN = 'I'.
                  L_S_RANGE-OPT = 'BT'.
                  APPEND L_S_RANGE TO E_T_RANGE.
                  EXIT.
                  ENDLOOP.
                  ENDIF.
    ===================================================================
    After that I use this 'ZYTD_PERIOD' variable in the query .
    Also I have used the variable 0P_FPER in another structure.
    When I execute the query by entering the value of 0P_FPER as 010.2009 or any other value ,
    I am getting below error message ,
    *No value could be determined for variable ZYTDPERIOD*_
    Below is details of this Error message ,
    Note that I have proper Master and Text data for 0CO_AREA and 0COMP_CODE loaded into BI.
    =======================================================================
    Diagnosis
    This error diagnosis is specific only to the variables 0P_FVAEX or 0P_CTPCA !
    Termination message BRAIN 632 appears:
    Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).
    System Response
    1. Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA
    With queries from the CO application, both SAP-Exit-Variables look for an entry for 'controlling area'. With this controlling area from the selection screen, the SAP-Exit-Variables program reads the attributes for InfoObject 0CO_AREA (controlling area).
    With queries from the FI application, the SAP Exit Variable 0P_FVAEX looks for an entry for 'company code'. With this company code from the selection screen, the SAP Exit Variables program reads the attributes for InfoObject 0COMP_CODE (Company Code).
    0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries). 0P_CTPCA determines the currency type of the profit center local currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.
    2. Cause of Error
    The attributes for the controlling area (InfoObject 0CO_AREA) or company code (InfoObject 0COMP_CODE) were not loaded into the BW system, or the attributes for the controlling area are not active in the BW system.
    Check whether this is the cause of the error in your BW system. Display the contents of table /bi0/mco_area or /bi0/mcomp_code using transaction se16.
    Application CO:
    Check whether the attributes 'fiscal year variant' (field FISCVARNT) and 'profit center local currency currency type' (field CURTP_PCA) are filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant in the OBJVERS = 'A' is empty, then the error is with variable 0P_FVAEX. If the currency type of the profit center's local currency in OBJVERS = 'A' is empty, then the error is with variable 0P_CTPCA.
    Application FI:
    Check whether or not the attribute 'fiscal year variant' (field FISCVARNT) is filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant is empty in OBJVERS= 'A', then the error is with variable 0P_FVAEX.
    Procedure
    Using InfoSource 0CO_AREA, load the attributes for the controlling area or company code into your BW system.
    Afterwards, activate the attribute changes in your BW system. To do this, use transaction rsa1, path 'Tools > Hierarchy/Attribute changes', functions button 'InfoObject list'. Choose InfoObject 0CO_AREA or 0COMP_CODE from this list, and activate the attribute changes.
    =====================================================================================
    Is there any special settings needed before writing BEx Customer Exit ?
    I have already created a project in CMOD and assinged a proper RSR00001
    and EXIT_SAPLRRS0_001 and project is active.
    Any help please ....
    Regards ,
    Amol

    My Code is as below ,
              case i_vnam.
                  WHEN 'ZYTD_PERIOD'.
                  IF I_STEP = 2.
                  LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
                  CLEAR L_S_RANGE.
                  L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
                  L_S_RANGE-LOW+4(3) = '001'.
                  L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
                  L_S_RANGE-SIGN = 'I'.
                  L_S_RANGE-OPT = 'BT'.
                  APPEND L_S_RANGE TO E_T_RANGE.
                  EXIT.
                  ENDLOOP.
                  ENDIF.
                  ENDCASE.

Maybe you are looking for